[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 4525
  • Last Modified:

Sybase ODBC probs

I am using Patterson Dental's Eaglesoft program that uses a sybase database.  I am frequestly getting ODBC errors that read :

sybase)(odbc driver)(adaptive server anywhere) unable to connect to database server: specified database is invalid.

I also get other errors that are similar.  
I am using XP SP2 and windows small Buisness server with ISA.  I have put the EagleSoft in as an exemption on the ISA firewall clients, turned off all power management (set it to always on) and checked the DSN, they look fine.

ANy ideas?

  • 3
1 Solution
Jim P.Commented:
Do you have the database installed as a service and always up?
bwalker9Author Commented:
The company did the install, but I assume so.  Should I check under services and "database name"?  If that is not it what else could be going on?
Jim P.Commented:
Check the services -- It may say something like "Adaptive Sever Anywhere -- DBName".

Also go into regedit, and dump the ODBC key for the the database.  Make sure that you take out/mask the password.
You don't say exactly what ODBC driver you're using, or what Sybase database you're trying to connect to, but the error is fairly straightforward:

ODBC thinks you asked to connect to a particular database, yet the server you connected to doesn't have that database.

If you're connecting to Sybase ASE, we would check the databases in the server.

If you're connecting to Sybase ASA or Sybase IQ, even though the server and the database are kinda the same thing, it's possible for them to be named differently. You might think you're connecting to one when you should be connecting to the other, etc.

I guess either way we need to know exactly what Sybase product (and version) you're trying to connect to, because then we can give you more specific guidance as to how to check the server and database names, and how to set those correctly in your ODBC connection.

If your ODBC data source is a User DSN, drop it and recreate it as a System DSN. Some applications have problems with User DSNs as they're visible only to the Windows user profile that created them.

Hope that will answer your query.

Chetan Sachdeva
Jim P.Commented:
No objections.

Featured Post

Hire Technology Freelancers with Gigs

Work with freelancers specializing in everything from database administration to programming, who have proven themselves as experts in their field. Hire the best, collaborate easily, pay securely, and get projects done right.

  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now