Hi, I am not sure about what the message means, but personally would check the following.
Can you ping/access the Remedy server from the ADDM server. Does the user the CMDB sync is configured with in ADDM have necessary privileges in Remedy (you can check by logging to Remedy as that user and checking if you can access CMDB and the BMC.ADDM dataset). Finally, turn on logging on the Remedy server and try to identify what commands are issued by ADDM to see where the issue might be. There are also logs on the ADDM side that might shed some light. Hope the above helps. Jiri Pospisil Remedy Specialist, IT Production [cid:[email protected]] [cid:[email protected]] From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Kathy Morris Sent: 02 October 2012 21:04 To: [email protected] Subject: ADDM to CMDB ** Hi, We are trying to synch ADDM 8.2 into the CMDB 7.6.4. We created the BMC.ADDM dataset, added the CMDB server to the /etc/hosts file and restarted the services. The test connect from ADDM to the CMDB fails. Error displays: 32 VM for an atrium connection. The connection test failed. Dataset not found. The dataset BMC.ADDM is the configured dataset and shows in the CMDB dataset tables. Does anyone know what is causing this connection from ADDM to the CMDB to fail? _attend WWRUG12 www.wwrug.com ARSlist: "Where the Answers Are"_ A copy of the LCH.Clearnet e-mail disclaimer can be found at: www.lchclearnet.com/disclaimer/email LCH.Clearnet Limited, Registered Office: Aldgate House, 33 Aldgate High Street, London EC3N 1EA. Recognised as a Clearing House under the Financial Services & Markets Act 2000. Reg in England No.25932. LCH.Clearnet SA, Siège Social, 18 rue du Quatre Septembre, 75002 Paris, Chambre de Compensation conformément au Code Monétaire et Financier. _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"
<<inline: image001.jpg>>
<<inline: image002.gif>>
