Kbase P150211: Getting error 8933 when trying to run sqlexp to connect to a database on the same machine
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
24/07/2009 |
|
Status: Unverified
SYMPTOM(s):
Getting error 8933 when trying to run sqlexp to connect to a database on the same machine
Error: <command name | SQL Exception message>. (8933)
sqlexplorer.exceptions showing error: Broker fails to find a server available for connecting.
Database has a maximum number of servers configured for 10.
promon dbname and looking in R&D and then Status and Servers shows that there are 10 servers spawned already when the client is attempting an ODBC connection.
Database is not making use of multiple login brokers to service 4GL and SQL users.
FACT(s) (Environment):
Trying to connect on the same machine where the database is being spawned.
Hostname being using in -H parameter is valid.
Service name being specified for -S is valid.
Can connect 4GL clients using the -H and -S parameter without receiving errors.
Appropriate licenses on the machine to support SQL92 client access
All Supported Operating Systems
OpenEdge 10.1B
CAUSE:
The database server has exhausted the number of servers that the database is configured for. The 10 servers that were spawned are _mprosrv processes. These processes do not handle SQL clients. SQL92 clients need to connect to an _sqlsrv2 process. The database broker is unable to spawn an _sqlsrv2 process due to having already exhausted the total number of servers that the broker can spawn.
FIX:
Configure the database to support multiple login brokers. 1 broker to handle 4GL clients and another to handle SQL92 clients. See solution: P7843, "How to set up a secondary login broker for SQL-92 connections for Progress 9.1D and above" for additional information on how to spawn multiple brokers.