2009-04-02 18:05:39 UTC
for the 4 years I've been at this company.
Our application is installed with a system DSN that points directly to the
database file. I can use the application just fine and I can go into ODBC
and do a test connection just fine (we have connect info in the DSN, let's
not get into why that's bad, I know).
When I try to connect via ISQL or Sybase Central, I select the ODBC DSN
option and select it from the browse list, then hit connect. I get: Could
not connect. Database server not found. Ensure server name is spelled
correctly and the database has been started. Mind you, I have not messed
with any other settings in the connect window. Under the database tab,
start database is checked as well it is checked in the DSN. The details on
the error give me:
[Sybase][ODBC Driver][Adaptive Server Anywhere]Unable to connect to database
server: Database server not found
Now if I launch our app (which uses the SAME DSN) the database starts up.
With the app running (and the db started) I can then connect with ISQL
without having touched anything else. One of the other developers is not
having this issue, he can connect right up with the database without
starting it ahead of time. Comparing our PATH and environment variables, I
can't see anything different.
Searching the groups didn't find me anything that seemed relevant. What
could I have possibly damaged that is causing the system to fail to start
This is 8.0.1 Build 2600 running on WinXP SP2