SQLAny8 - Central and ISQL do not start database

[Tom]

I have no idea what I broke or changed because this setup has been working
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

Error code=-100

SQL state=08001

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
the database?

This is 8.0.1 Build 2600 running on WinXP SP2

Thanks

["Nick Elson [Sybase iAnywhere]" <@@elson@@@com@>]

It almost sounds like you are getting some
preference setting overridding the DSN
behaviour. There are some 'dot' files in your
"Documents and Settings" directory that may
be playing a role here.

In your
C:\Documents and Settings\<username>\

directory you will see a number of files starting
with a '.' (dot). You could try (temporarily) moving
all of those out of there and seeing if that helps
[stopping scjview and dbisql first] any. I am
suspicious your servernName and DSN list in
'.jlogon' are actually slightly different than you
need. There may be many other .*preferences*
and .*settings* entries that my also be playing a
factor here, so you will have to play around a
bit to figure out which is the culprit.

If that fails to resolve this issue, try clearing the
ASA.ini file off the system entirely.

There may be something broken in you default
connection profiles, prefilled connection dialog
fields (that may merge) and something in you
Network and Advance tabs. Also look at
connection profiles.

good luck

Post by Tom
I have no idea what I broke or changed because this setup has been working
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
[Sybase][ODBC Driver][Adaptive Server Anywhere]Unable to connect to
database server: Database server not found
Error code=-100
SQL state=08001
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
the database?
This is 8.0.1 Build 2600 running on WinXP SP2
Thanks

[Tom]

Nick, that did the trick.

I moved out all the "." files, ran iSQL, got into the database, then
replaced any "." files that had not been re-created. After that I tried
getting in again and did so just fine.

Thanks, I don't believe I'd ever have found that.

Post by "Nick Elson [Sybase iAnywhere]" <@@elson@@@com@>
It almost sounds like you are getting some
preference setting overridding the DSN
behaviour. There are some 'dot' files in your
"Documents and Settings" directory that may
be playing a role here.
In your
C:\Documents and Settings\<username>\
directory you will see a number of files starting
with a '.' (dot). You could try (temporarily) moving
all of those out of there and seeing if that helps
[stopping scjview and dbisql first] any. I am
suspicious your servernName and DSN list in
'.jlogon' are actually slightly different than you
need. There may be many other .*preferences*
and .*settings* entries that my also be playing a
factor here, so you will have to play around a
bit to figure out which is the culprit.
If that fails to resolve this issue, try clearing the
ASA.ini file off the system entirely.
There may be something broken in you default
connection profiles, prefilled connection dialog
fields (that may merge) and something in you
Network and Advance tabs. Also look at
connection profiles.
good luck

Post by Tom
I have no idea what I broke or changed because this setup has been working
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
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.
[Sybase][ODBC Driver][Adaptive Server Anywhere]Unable to connect to
database server: Database server not found
Error code=-100
SQL state=08001
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
the database?
This is 8.0.1 Build 2600 running on WinXP SP2
Thanks

[m***@gmail.com]

You are a life saver. Google comes through once again. I was having the exact same issue as the original poster and was dead in the water. Thanks again!

Post by "Nick Elson [Sybase iAnywhere]" <@@elson@@@com@>
It almost sounds like you are getting some
preference setting overridding the DSN
behaviour. There are some 'dot' files in your
"Documents and Settings" directory that may
be playing a role here.
In your
C:\Documents and Settings\<username>\
directory you will see a number of files starting
with a '.' (dot). You could try (temporarily) moving
all of those out of there and seeing if that helps
[stopping scjview and dbisql first] any. I am
suspicious your servernName and DSN list in
'.jlogon' are actually slightly different than you
need. There may be many other .*preferences*
and .*settings* entries that my also be playing a
factor here, so you will have to play around a
bit to figure out which is the culprit.
If that fails to resolve this issue, try clearing the
ASA.ini file off the system entirely.
There may be something broken in you default
connection profiles, prefilled connection dialog
fields (that may merge) and something in you
Network and Advance tabs. Also look at
connection profiles.
good luck

Post by Tom
I have no idea what I broke or changed because this setup has been working
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
[Sybase][ODBC Driver][Adaptive Server Anywhere]Unable to connect to
database server: Database server not found
Error code=-100
SQL state=08001
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
the database?
This is 8.0.1 Build 2600 running on WinXP SP2
Thanks