Deployed sybase probe but it crashes and we cannot successfully configure a connection to the Sybase database server instance. Connection test threw an error ending in: ...The parameter %1! cannot be NULL
- sybase probe configuration
- UIM 8.5.1
- Sybase ASE v16.0 PL01
- sybase probe v4.31
When configuring a connection, ensure that the name defined in the sql.ini file matches with the server name. The server name IS case sensitive. Use the same name when creating the connection to a Sybase instance using the sybase probe. To identify the instance name, check the sql.ini file on the Sybase ASE server.
To run the command from the cmd line on the local robot to confirm you can connect->
ISQL -S server -D database -U user -P password should work fine when executed to connect to the Server.
The sybase probe has the following prerequisites for installation.
Libraries and Variables: The probe requires the following library configurations: libstdc++ 5 library must be present on the robot platform.
Sybase libraries and environment variables must be set in the system path. For more information, see the Configure Sybase Library Path section.
Software: Sybase OCS client 15.x, ASE 15.x, or ASE 16.
Advanced Monitoring: Sybase Monitoring Server or Monitoring Tables must be installed and enabled.
Sybase: Sybase Monitoring Server must be up and running.
Adaptive Server Enterprise 15.7: The property net password encrypt must be updated to a value 2 to enable the encrypted communication between the probe and the Sybase database server.
1. Deselect Advanced Monitoring and Encryption since as of version 4.2 onward, the probe does not support Advanced monitoring using Monitoring Server. This is because the Monitoring Server is not a part of the Adaptive Server Enterprise version 15.7 and later.
Servername in the IM GUI for the sybase probe MUST be configured using the correct instance name (as per the sql.ini file on the Sybase Database Server) so that should be checked to confirm. No port was specified in the Server name field just the instance name.
2. In this particular case, once we edited the Sybase connection setup and specified the correct 'Server name' as the Sybase instance name (re-confirmed via the contents of the sql.ini file), then the connection test completed successfully.