Connect:Direct® Web Services Troubleshooting
ChangeDatabasePassword-0.1.jar
and
./startWebserviceZLinux.sh
have changed to
ChangeDatabasePassword.jar
and ./startWebservice.sh
respectively.Problem | Possible Cause | Solution |
---|---|---|
Connect:Direct Web Console fails to load | Cookies disabled in your browser settings and/or browser's local storage is persistent. | Enable browser cookie, local storage, clear the cache, and reload the page. |
Upgrade fails |
A previous attempt to uninstall Connect:Direct version was unsuccessful. |
Cleanup the registry settings in the .com.zero.registry.xml:
|
Connect:Direct Web Console fails to load | Web Services is not accessible | Ensure firewall rules have been added for inbound and outbound connections between Web Services and Connect Direct Server. Firewall rules must allow inbound connections to the specified Web Services port. Connect Direct server must also have its API port open for web service. |
Connect:Direct Web Services is not accessible | A network or firewall restriction | Ensure firewall rules are added on all the machines hosting Connect:Direct server(s). |
Connect:Direct server stops with the following error message:
CD
server is in stop state . |
|
Ensure that the Connect:Direct Server is running and verify:
|
Web Admin user account is locked. |
|
Execute the Password Reset utility,
ResetDefaultCDWSAdminPassword . For more information see, Password Reset for a Web Administrator. |
Certificate-based authentication fails | This possibly occurred due to domain name and the Subject Alternative Name (SAN) or common name mismatch of the SSL certificate. |
|
Reference to PostgreSQL database may remain in the Registry after Connect:Direct Web Services for Windows is successfully uninstalled. |
|
|
All services were up and running but unable to access Connect:Direct Web Console. | This possibly occurred due to firewall settings. The settings are blocking connection attempts to Web services application. | Contact your system administrator. |
Connect:Direct Web Services fails to start after installation/upgrade is
complete. Upon inspecting the RESTful APIs logs the following error is displayed: org.postgresql.util |
This issue possibly occurs when you're executing PostgreSQL password reset procedures for Connect:Direct Web Services running zLinux and AIX platforms. |
|
The default PostGreSQL password is changed in the Connect:Direct Web Services configuration settings. The modified password must also be updated for this user in PostgreSQL. | See, Reset PostgreSQL Database connection password procedure using default password described here, PostgreSQL database Password management. | |
Reset PostgreSQL Database using old password. | Follow Reset PostgreSQL Database connection password procedure using old password described here, PostgreSQL database Password management. | |
Change PostgreSQL Database in case of forgotten password | Follow Reset PostgreSQL database connection in case of forgotten password described here, PostgreSQL database Password management. | |
Unable to import Connect:Direct z/OS certificates through Web Services. |
|
For a binary key certificate in Base64 ASN.1 DER format, follow the steps below
convert the binary certificate into a base64 encoded PKCS12 ASCII key certificate:
|
Webservices did not come up after installation/ upgrade and after inspecting
{Install_dir}/PostgreSQL/postgres/12-pgdg/bin/64/postgres -V throws following
error:
|
Postgres installation failed due to an incompatible libxml. |
Postgres12.4 requires a specific version of There are 2 ways to resolve this:
Once the compatible library is in place, follow these steps:
|
Webservices did not come up after an upgrade from 6.0.0.5 to 6.1 or above. Upon inspecting the
|
CDWS uses 'sed' to manipulate the truststore path. If it is not installed, you can witness this error. |
Remove the '\' characters from .hidden file and restart the webservices. |