Identity Synchronization 1.0/AD - MQClient failure

Question

After what appears to have been a successful install of Sun ONE Directory Server 5.2 and Sun ONE Synchronization Server for Windows 1.0 on an S9 system (fully patched), attempts to link users with the idsync linkusers command results in what appears to be a missing message queue failure being flagged.
Specifically, the command invoked is:
./idsync linkusers -h s3.sso.isdintegration.com -p 389 -D "cn=Directory Manager" -w sun123 -s dc=sso,dc=isdintegration,dc=com -q sun123 -f../samples/IlodeLinkUsersIntegrate
The response echoed to the console is:
Operation is started. Enter 'c' to cancel.
MQClient failed due to a Java Message Service error.
CNN101/error.log reports:
[20/Jul/2004:15:11:29.767 -0400] SEVERE 10 CNN101 s3 "Failed to establish a connection to the Sun ONE Message Queue Broker because of a JMSException: javax.jms.JMSSecurityException: [C4035]: Forbidden."
and cli/error.log reports:
[20/Jul/2004:15:28:21.570 -0400] INFO 10 "Log opened. Identity Synchronization for Windows build 2003.328.0933. Java runtime version is 1.4.2_04."
[20/Jul/2004:15:28:24.899 -0400] INFO 10 "Log opened. Identity Synchronization for Windows build 2003.328.0933. Java runtime version is 1.4.2_04."
[20/Jul/2004:15:28:32.308 -0400] SEVERE 11 s3 "Failed to establish a connection to the Sun ONE Message Queue Broker because of a JMSException: javax.jms.JMSSecurityException: [C4035]: Forbidden."
[20/Jul/2004:15:28:32.390 -0400] SEVERE 10 s3 "MQClient failed due to a Java Message Service error."
The message service appears to be operational (I can stop and start it with /etc/init.d/imq
A Google search for JMSSecurityException: [C4035] notes that this error is flagged if a non-existant queue is forbidden from being created. The 64K$ question is... what queue is missing? plus... what have I failed to do to insure its existance?
Thanx in advance -
-Darren-

Answer 1

HI Toph_TF....
During our Windows Synchronization build we experienced the exact same MQClient error and found a resolution which may help you:
under the following directory:
var/imq/instances/psw-broker/props there is a file called config.properties
under this file are domain references which could be the root cause of your problem. In our case we did a re-install of Identity Synchronization for Windows but changed domains from abc.dce.company.com to abc.hji.company.com.
Because we didnt obliterate the var/imq directory during a reinstall, the above file was the source of our MQClient Java failure.
To cure the issue we modified the config.properties where references to the old domain occurred. Additionally we deleted all the messages in the following directory:
/var/imq/instances/psw-broker/filestore/message
and cleared up the information in the following file
/var/imq/instances/psw-broker/filestore/destination
Hope this help!