K2 Blackpearl 4.6.8 issues with MSMQ and workspace issue

  • 12 February 2015
  • 3 replies
  • 3 views

Badge

Hi Team,

I am unable to install K2 Blackpearl 4.6.8 on Windows Server 2012 data center (on Winows Azure VM). I have the issue with MSMQ and K2 Workspace installation.

MSMQ error: Object owner was invalid: For Example, MQCreateQueue is failed because the Queue Manager object is invalid

<< I followed all the instructions provide by K2 >>

K2 Workspace Issue:

Error: Cannot add duplicate collection entry of type 'add' with unique key attribute 'value' set to 'NTLM'

" C:Program Files (x86)K2 blackpearlWebServicesK2Apiweb.config"

The same issue is there for rest of the web services.

 

Please help.

 

with best regards,

Madhusudhan

madhusudhan.hk1@wipro.com

 

 


3 replies

Badge +12

Hi there,


 


In regards to the MSMQ error you are facing this may be due to two causes both related to not being able to query
active directory to get information about the public queue:


 


You can get around this by doing the following:


 


- trying to perform operations between machines that are in different forests without domain-domain trusts.
- the system clocks on the sending machine and the domain controller are out of sync (not the clocks on the sending machine and the receiving
machine.


 


You can check out the link for more information on this from this link: http://microsoft.public.msmq.programming.narkive.com/Gwja5hv5/object-owner-was-invalid-for-example-mqcreatequeue-failed


 


In regards to the workspace issue, this may be cause by an IIS setting. Please the check the following document to better assist you:


 


http://support.microsoft.com/kb/949349?wa=wsignin1.0


 


I hope this helps


 


Kind regards,


 


Percy

Badge +10

If for some reason you can't get MSMQ working with Active Directory you can try setting it to work with a private queue:

 

http://help.k2.com/kb000198

 

 

Badge +10

Vinay,

 

Check your web config for the <add value="NTLM" /> line, and remove it.

 

13512i85AD629481A503BB.png

 

Remove that line, and try re-running the analysis/doing a "repair all".  That should resolve the conflict.  The issue is typically exactly what the error message describes, the script will not allow something such as:

 

<add value="NTLM" />

<add value="NTLM" />

 

Therefore, removing the line, and letting the script re-add it, should fix that portion of things.

Regards,

 

Mike

Reply