Overview
When connecting to Bizagi’s ODS service, especially from a SQL Server Management Studio, refer to the following error codes for possible solutions within this troubleshooting guide.
Prerequisites and instructions are described at ODS Operational Data Store.
Error codes and known issues
1.Error Message: Server connection error (SQL Error: 53). The route was not found.
Solution: Verify that Server Name is spelled correctly. Validate that no characters have been omitted during typing or that there are no improper spaces between characters.
2.Error Message: Server connection error (SQL Error:18456). Login failed for the entered user.
Solution: Verify that the username and password entered in Login and Password (respectively) are correct. Validate the correct use of capital letters and spaces.
3.Error Message: Error accessing BD master (Error 916).
Solution: Verify that the exact name of the Database has been entered correctly (use of capital letters and spaces).
4.Error Message: Connection error at login time (error 0) with a specific message.
Solution: Verify that the Trust server certificate checkbox is checked.
5.Error Message: IP address does not have access to the server.
If the message shown below appears when connecting to the server, the IP address from which you want to connect to the server does not have access authorization.
Solution: You must validate:
•Check with your contact person if the IP address from which you wish to access may be authorized to access the server. If yes, you must verify the IP address is added to the Whitelist.
•Validate whether you should access through a VPN. This in order to use an authorized IP address to connect to the server.
6.Error Message: "Unable to establish connection: Cannot open server requested by the login."
If you are attempting to connect to ODS through the IP address (e.g. whenever the ODS is requested to be accesible as private endpoint through VPN), then the following error is shown:
Solution: For this, verify that you entered the DBserver name and that the DNS maps the IP address to the DBserver name.
Tips to verify your IT prerequisites in terms of access
1.To validate that the DNS resolution is OK for access to ODS, either through a public endpoint or a private endpoint (via VPN), open a DOS console and perform an nslookup towards the ODS server:
nslookup [db_server_name]
The IP address that it resolves must reflect that the access is sought by public or private endpoint, according to its setup.
Validate with your IT team if that IP resolves as expected.
|
Verify that the address in outbound public facing IP address, IPv4 is correct. You can check this by using What's my IP? or similar web pages. |
2.To validate that port 1433 and general outbound access through your corporate firewall is OK, whether through a public endpoint or a private endpoint (via VPN), open a DOS console and perform a telnet to the ODS server through port 1433:
telnet [db_server_name] 1433
A successful telnet is resolved as follows:
Last Updated 10/24/2024 5:05:59 PM