|
Hello All, I am using SQL Anywhere 12 for my internal testing development, I am facing with: iAnywhere.Data.SQLAnywhere.SAException: Unable to start specified database: server exit code 322 at iAnywhere.Data.SQLAnywhere.SAConnection.Open() after it ran for 2 or 3 days .. what happen with this?.. what should I do? I am using DBSRV with the following parameters in my ODBC settings dbsrv12.exe -m -q -c 50p -x tcpip -m |
|
Re: the following parameters in my ODBC settings dbsrv12.exe -m -q -c 50p -x tcpip -m Please explain what you mean by ODBC settings? Are you referring to the START(LINE) parameter? What does -q do for you? All I see is an "About SQL Anywhere" dialog and the server does not create a console window (I can't locate any documentation on a -q server option). Try removing the -q so that there is a console window. Also try the -zr request level log options and -o logging to an output file. On the client side, try using the LOGFILE connection parameter. How frequently do you see the "exit code 322"? If you are using STARTLINE, try starting the server from the command line using the same options first (rather than having the client application launch the server). Hi.. yes, I am refering to Start Line parameter, I will try what you suggested .. get back to you soon.. Q: How frequently do you see the "exit code 322"? --> after my app ran for 2 or 3 days..
(10 Oct '14, 00:22)
510
Replies hidden
1
For 2 or 3 days? You are starting the server after waiting 2 or 3 days? Does your application start and stop the server on demand? Or are you actually starting the server after your application has been running for 2 or 3 days?
(10 Oct '14, 08:48)
JBSchueler
Also, which exact version and build of SQL Anywhere 12 (for the server and the ADO.NET Provider) are you using?
(10 Oct '14, 15:57)
Jeff Albion
Comment Text Removed
No.. I meant after my app ran for 2 or 3 days then then the problem occurs.. Sorry to make you confusing..
(10 Oct '14, 23:25)
510
|
"server exit code 322" is an extremely rare and undocumented error message. A Google search turns up only one other occurrence, almost exactly the same wording, but (alas) no solution, just a suggestion "call tech support":