Kbase 580: How to debug "no server available" error
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
5/10/1998 |
|
How to debug "no server available" error
900531-jao02
INTRODUCTION: Date Last Modified: 5/01/93
============= JPL
This Product Services Technical Support Knowlegebase entry details the
causes of LAN network error 12 which indicates that there is no server
active for the database you are trying to access. It also explains the
network changes you can make to resolve the problem.
PROGRESS ERROR NUMBER: ERROR TEXT: ERROR TYPE:
====================== =========== ===========
None There is no server for this DOS LAN
database error number 12. Network
Unable to contact server.
OS2 LAN
Network
POSSIBLE CAUSE OF ERROR:
========================
This error indicates one of the following problems:
1. The database engine has not been started.
2. The database engine is no longer running.
3. An incorrect database server name was used when starting the
client.
4. A network adapter has not logged the SPX server name.
5. On token ring networks, the default number of IPX sockets or SPX
sessions are all in use.
6. The database name and -S startup are case sensitive. The same
case must be used on both the server startup and client startup.
DOES ERROR INDICATE CORRUPTION: IF SO, WHAT TYPE:
=============================== =================
No N/A
CORRECTIVE MEASURES:
===================
1. Check the status of database engine.
2. Check that IPX.COM has been loaded.
3. Reset the workstation and rerun IPX.COM.
4. Check that the correct server name was specified when starting the
client.
5. For Token Ring networks try the following:
On the database server and all the workstations create a SHELL.CFG f
files that contains:
IPX SOCKETS = 40
SPX CONNECTIONS = 30
Note: You must placethe SHELL.CFG file in the same location as the
IPX.COM.
6. Case is the same for the database name and -S startup.
ONLINE PROCEDURES OR UTILITIES:
===============================
TESTSV (For NetBIOS users) - Tests Server
TESTCL (For NetBIOS users) - Tests Client
TESTSV -N SPX (For SPX users) - Tests Server
TESTCL -N SPX (For SPX users) - Tests Client
Invoke these tests on the server and all workstations simultaneously.
By increasing the number of messages that are sent during the test you
should be able to narrow down which workstations are having the
problem. These tests are described in the Preparing to Use LAN PROGRESS
section of the Environments Guide (for PROGRESS Version 5) or System
Administration Guide One: Environments (for PROGRESS Version 6).
REFERENCES TO WRITTEN DOCUMENTATION:
====================================
Environments Guide -- Preparing to Use LAN Progress (PROGRESS
Version 5)
System Administration Guide One: Environments (PROGRESS
--Chapter on PROGRESS and DOS LANS Version 6)
Progress Software Technical Support Note # 580