Environment
LDMS 9.5 SP1 with LDMO 9.5
Scope
This document is intended for advanced troubleshooting any connection issues between AOD/CSA/LDMS/LDMO.
Problem
You are unable to validate "test" connections from AOD
You are unable to launch AOD from the LDMS Core Server
Solutions
The below items all need to be in place for proper communication to occur between AOD & LDMS:
1. The CSA needs to be configured in the LDMS Core Server with the correct hash (see below)
2. The Hash needs to match in the following locations:
a. The \ldlogon folder of the cores (.0 file)
b. The protect.ini file in the \Shared Files\Keys folder on the core
3. The CSA Connection Table should show you the connect info for the core(s) that are properly communicating
4. The CSA Core Certificate page should show you your core with the correct hash
5. The certificate that IIS is using should be the same one that your core is using
6. The thumbprint for this certificate needs to match the "encryptionCert" and "STSCert" key values in the web.config file from the \STS folder of the core
Note: You will need to use www.base64decode.org to decode/encode the thumbprint
***If you are still having problems then please refer to the Troubleshooting LDMO document for details on logging options***
The following logs could be useful in diagnosing issues;
-BrokerService Log
-STSDLL log
-Console log
-Any Mobility or LDMO log
-IIS logs