Sybase Business Intelligence Solutions - Database Management, Data Warehousing Software, Mobile Enterprise Applications and Messaging
Sybase Brand Color Bar
delete

Search for    in all of Sybase.com
view all search results right arrow
  blank
 
 
 
 
 
 
 
 
 
 
Support > Technical Documents > Document Types > Technote > Diagnosing SQL Anywhere ODBC Client/Server Connect...

Diagnosing SQL Anywhere ODBC Client/Server Connection Problems

This documents discusses common ODBC connection issues with Adaptive Server Anywhere
 
RSS Feed
 
 
 

Quick Checks

  • Specify the database server name in the ODBC data source and not the computer name
  • The start line should be left blank in the ODBC data source
  • In the data source if this is a server/client connection, specify the database server name and the database name (if multiple databases on server)
  • If using TCP/IP check that the client and server can ping each other. You can do this from a dos prompt entering ping <server_ip>
  • Try mapping a drive to the server and transferring a file
  • If multiple network cards exist on the server or client and you are working with TCP/IP specify host=<server_ip> and myip=<local_ip> on the server and client
  • If you are working with IPX, the server address can be found by displaying verbose output on the server with the -z switch. You may need to convert the address from hex to decimal. The format of the host address is network/node
  • Going through a firewall? Modify the firewall so it does not filter the UDP on a single port
  • The default port for ASA is 2638. You may want to try specifying a different port in some cases.

Determining the Database Server Name

dbsrv6 c:\path\dbfile.db
database server name = dbfile

dbsrv7 c:\path\dbfile.db -n database_name
database server name = database_name

dbsrv8 -n server_name c:\path\dbfile.db
database server name = server_name

dbsrv6 -n server_name c:\path\dbfile.db -n database name
database server name = server_name

Common Error Messages

Unable to Initialize requested communication links
Probable cause: wrong server name specified
Resolution:

  • Check machine name vs. database server name
  • Check network protocol under network tab
  • Add network parameters such as host=<server_ip>;myip=<local_ip>;dobroadcast=no in different combinations

Connection failed: request to start/stop database denied
Probable cause: wrong database name specified
Resolution:

  • Check on server startup to see if the database has been renamed with a -n following the database file.

Connection failed: database engine not running
Probable cause: client cannot find server
Resolution:

  • TCP/IP check that client can ping server and server can ping client. If not then it is a networking problem
  • In your ODBC configuration under the network tab select network protocol. In the space following the protocol enter host=xxx.xx.xx.xx which may help the client to find the server. If this doesn't help try adding host=xxx.xx.xx.xx;dobroadcast=no;myip=xxx.xx.xx.xx

Server not found
Probable cause: wrong database name specified or client cannot find server
Resolution:

  • Verify that the database server is running
  • Specify the database server name and not the machine name of the server
  • Use the same protocol on the server and the client
  • If using TCP/IP check that client can ping the server and that the server can ping the client. If not then it is a networking problem
  • In your ODBC configuration under the network tab select the network protocol.
  • In the space following the protocol enter host=<server_ip> which may help the client to find the server.
  • If this doesn't help try adding host=<server_ip>;dobroadcast=no;myip=<local_ip>
  • Debug/Verify specific communication protocol set-up (IPX TCP/IP NetBIOS NetDG)

Port dll not found
Probable cause: dbport6.dll is not in the path, or it may be finding an older version
Resolution:

  • Add Adaptive Server Anywhere to your path
  • If working on win95 or win98 edit your autoexect.bat to include ASA in the path
  • On WINNT under the Control Panel and the System folder add ASA to the path

Too many connections to database
Probable cause: The database server has not been licensed
Resolution:

  • Try running dblic against dbsrv6 / dbsrv7 / dbsrv8. For information on parameters to specify enter dblic at a dos prompt or see doc 47921 for more information.
  • Check the number of users connected to the server. You may want to purchase additional seats.
  • Check the number of connections your application is making

Still Cannot Connect to Database Server?

Other Resources:


 

DOCUMENT ATTRIBUTES
Last Revised: Sep 15, 1999
Product: SQL Anywhere
Technical Topics: Connectivity, SQL Anywhere, Troubleshooting
  
Business or Technical: Technical
Content Id: 47961
Infotype: Technote
 
 
 

© Copyright 2014, Sybase Inc. - v 7.6 Home / Contact Us / Help / Jobs / Legal / Privacy / Code of Ethics