Help Center/ Cloud Bastion Host/ FAQs/ Troubleshooting/ SSO O&M Faults/ Failed to Call the Database Client When Logging In to the Database Using the SSO Tool
Updated on 2026-07-30 GMT+08:00
Failed to Call the Database Client When Logging In to the Database Using the SSO Tool
Symptoms
When the SSO tool is used to log in to the database, the database client fails to be invoked. The following error message may be displayed:
- JRE is missing in the operating environment.
- Check the LocalAgent service.
- Other messages
Possible Causes
The image version corresponding to the process or listening port is incorrect.
Solution
- Check whether the following main process exists:
- Instances earlier than V3.3.56.0: YabLocalAgent.exe process
- Instances of V3.3.56.0 or later: LocalAgent.exe process
- Check whether the port for the YabLocalAgent or LocalAgent process is listened on and whether there is port conflict on the O&M PC.
- For instances of versions earlier than V3.3.56.0, run the following command (the port is 7001):
netstat -ano |findstr 7001
- For instances of version V3.3.56.0 or later, run the following command (the port is 9010):
netstat -ano |findstr 9010
- For instances of versions earlier than V3.3.56.0, run the following command (the port is 7001):
- If there is a port conflict, run the following command to check the process that occupies the port:
tasklist|findstr "{Process ID obtained by running the netstat command}"
Parent topic: SSO O&M Faults
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
The system is busy. Please try again later.
For any further questions, feel free to contact us through the chatbot.
Chatbot