Troubleshooting Concurrency Issues
This section provides errors that you may encounter when using the concurrency feature as well as possible solutions.
Note: There are additional steps that you may need to perform when implementing concurrency:
- Before installing an update, back up the *.config files.
- If you are using the Cobra installer to perform an upgrade of a machine with the Cobra Gateway Service, stop the service before installing the update and start it afterwards to avoid having to restart the machine.
- Related Topics:
- Use the Process Queue Manager form in PM Compass to Check Job Status
When one or more jobs on the Process Queue Manager form in PM Compass show a failed status, it means that the process was not able to successfully complete. - The server was unable to process the request due to an internal error
If the error "The server was unable to process the request due to an internal error." displays, it means that the Cobra Gateway encountered issues when connecting to one of the Cobra Web Service instances. Use the Gateway's debug log file to see the specific error. - There was no endpoint listening at http://<machine>:<port>/CobraWebService/service that could accept the message
If you encounter the error "There was no endpoint listening at http://<machine>:<port>/CobraWebService/service that could accept the message", it is possible that one of the Cobra Web Service's addresses is not working properly. Use the Gateway's debug log file to see the specific error. - The encryption type requested is not supported by the KDC
Cobra Web Service with Windows authentication requires encryption algorithms. If the service account that you created for the Cobra Web Service is not properly configured to support these algorithms, the Cobra Web Service log will display the following error: "System.ComponentModel.Win32Exception: The encryption type requested is not supported by the KDC."
Parent Topic: Integration Errors