Please be aware that the SAP SQL Anywhere Forum will be shut down on August 29th, 2024 when all it's content will be migrated to the SAP Community.


I have some clients running on ASA9 server, and one problem is in bothering. Whenever there are two (or more) simultaneous login requests via JDBC, any of the requests returns a JZ00L exception. I confirmed this behavior in the lab, wrote a program that performs infinite connections to the database, and when I fire the second instance of the program, the JZ00L error is generated in one of the running instances. Is this the expected behavior? Is there a way to resolve this situation?


asked 21 May '19, 14:39

DRauber's gravatar image

accept rate: 0%

closed 23 May '19, 13:48

It is unlikely that is expected behavior. It would be helpful to see the message and SQLWarning as those would provide more context to the problem encountered.

(21 May '19, 15:23) Chris Keating

This is the database log:

Unable to initialize NT performance monitor data area; server startup continuing
Adaptive Server Anywhere Network Server Version

Now accepting requests
Login procedure (ID: 758) caused SQLSTATE '42W18'!
Login procedure (ID: 758) caused SQLSTATE '23W01'!

and the java output:
Connection 26 - 2019-05-21T19:41:40.358Z 2019-05-21T19:41:40.375Z PT0.017S
Connection 27 - 2019-05-21T19:41:40.375Z 2019-05-21T19:41:40.395Z PT0.02S
Connection 28 - 2019-05-21T19:41:40.400Z 2019-05-21T19:41:40.424Z PT0.024S
Connection 29 - 2019-05-21T19:41:40.428Z 
SQL exception : java.sql.SQLException: JZ00L: Login failed.  Examine the SQLWarnings chained to this exception for the reason(s).
SQL State     : JZ00L
Error Code    : 0
SQL exception : java.sql.SQLWarning: ASA Error -103: Invalid user ID or password
SQL State     : 01000
Error Code    : 4002
SQL exception : java.sql.SQLWarning: ASA Error -103: Invalid user ID or password
SQL State     : 01000
Error Code    : 4002
Exception in thread "main" java.lang.NullPointerException
        at conectador.Conectador.main(
(21 May '19, 15:45) DRauber

What is your connection string? Are you autostarting the database or server?

(21 May '19, 16:43) Mark Culp
Replies hidden

Connection String is:

Class.forName("com.sybase.jdbc3.jdbc.SybDriver"); DriverManager.getConnection("jdbc:sybase:Tds:", uid, pwd);

No, the server is started by:

dbsrv9 -nTest C:\Tmp\Compras.db


(22 May '19, 06:34) DRauber

The question has been closed for the following reason "The question is answered, right answer was accepted" by DRauber 23 May '19, 13:48

"Login procedure (ID: 758) caused SQLSTATE '<sqlstate>'!" is not a SQL Anywhere message. Your database must have a custom login procedure that is encountering errors. The errors reported were SQLState 42W18 is User '%1' has the row in '%2' locked and SQLSTATE 23W01 is Primary key for table '%1' is not unique: Primary key value ('%2'). Does that custom login procedure when it encounters an error cause the error SQLE_INVALID_LOGON to be reported? The login_procedure database option should point to the procedure that is used at login and can be used to determine if there is a custom login procedure.

permanent link

answered 22 May '19, 09:11

Chris%20Keating's gravatar image

Chris Keating
accept rate: 32%

converted 24 May '19, 03:11

Volker%20Barth's gravatar image

Volker Barth

Thank you! You're absolutely right, problem is with the login trigger.

(23 May '19, 13:47) DRauber

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here



Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text]( "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Question tags:


question asked: 21 May '19, 14:39

question was seen: 1,866 times

last updated: 23 May '19, 13:48