java.sql.SQLException:Jz00L:Login failed.
20 August, 2010
Hi,
We are tyring to connect to a Sybase ASA database with 10000 as its port and phoenix as its database name. We can ping or telnet the host IP and its port and the username and password is correct but we always came up with an error that says "java.sql.SQLException:JZ00L:Login failed. Examine the SQLWarnings chained to this exception for the reason(s)."
I attached the screenshots below and the Yellowfin Log file.
What could be the reason for this error and do you have and suggestions on how we can solve this problem?
Thanks,
Albert
We are tyring to connect to a Sybase ASA database with 10000 as its port and phoenix as its database name. We can ping or telnet the host IP and its port and the username and password is correct but we always came up with an error that says "java.sql.SQLException:JZ00L:Login failed. Examine the SQLWarnings chained to this exception for the reason(s)."
I attached the screenshots below and the Yellowfin Log file.
What could be the reason for this error and do you have and suggestions on how we can solve this problem?
Thanks,
Albert
Hi Albert,
Unfortunately the log file does not contain any clues as to why it might be failing. The fact that it's a login error implies that it can reach the database okay, and that the user name & password are incorrect, or some sort of permission settings are blocking it. The default username for Sybase ASA is 'dba', but you state the username and password are right, so I'm not sure what I can do to help.
If possible try connecting to the same database using the same username & password so we can narrow down the source of the problem.
Unfortunately the log file does not contain any clues as to why it might be failing. The fact that it's a login error implies that it can reach the database okay, and that the user name & password are incorrect, or some sort of permission settings are blocking it. The default username for Sybase ASA is 'dba', but you state the username and password are right, so I'm not sure what I can do to help.
If possible try connecting to the same database using the same username & password so we can narrow down the source of the problem.