Identity Bridge Connection Troubleshooting

Bridge Connections Down/Failing Troubleshooting
**This is troubleshooting for Rapid Identity Cloud tenants only.

• Common Errors:
• errorMessage : Unable to establish a connection to LDAP
• ERROR isFile(): org.apache.commons.vfs2.FileSystemException: Could not determine the type of file
• Bridge connection test failed. Failed to establish a connection over the bridge.
• ERROR openADConnection(): An error occurred while attempting to connect to server bridge
• Your Action Sets that are setup for your bridge will also begin to fail.
• ERROR: Uncaught error while processing System.ComponentModel.Win32Exception (2): The system cannot find the file specified.
• No “HeartBeat” for Bridge at all (It will tell you the last heartbeat connected to bridge).

**The best thing to do is to go into the tenant and do a test on the bridge and as your troubleshooting follow the steps below.

Steps to Troubleshoot errors with Bridge:

• Check to make certain the chisel.exe file is in the proper location/directory, within the drive you have saved all Identity Automation files to. For example if that is the C:\ drive your path will look something like this C:\Program Files\Identity Automation\Identity Bridge Agent\chisel.exe. You are searching for the chisel.exe file to make certain that it is in the proper place.
• Your firewall would be the next place to make sure that there has been an exception setup for the above file. Chisel.exe file should never be quarantined by your anti-virus nor your firewall and the best practice is to actually whitelist this traffic or create an exception for it within both applications.
• There are many firewall and antivirus applications with different ways to set up the exclusions and/or whitelisting. Looking up the application for instruction is the best answer for the how to on the exclusions.
• Right click on the taskbar and go to the task manager. Check and make certain that within the task manager that the chisel.exe file is running.
• Go into your Windows search and pull up services.msc. Within the services manager stop the Identity Bridge Agent service and restart it.
• Look into port * For the Identity Bridge to work the port 443 must be open. Restart the server as the last hing that you try prior to opening a case with Identity Automation.