Kbase P135374: ODBC clients cannot connect to a database because no _sqlsrv2 processes can be spawned
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
6/1/2010 |
|
Status: Verified
SYMPTOM(s):
ODBC clients cannot connect to a database because the broker is rejecting the connection.
Error "broker rejects connection" trying to connect via ODBC
ODBC connection fails with:
[DataDirect][ODBC Progress OpenEdge Wire Protocol driver][OPENEDGE]Broker rejects connection.
Database log shows erro 8839
No SQL servers are available. Try again later. (8839)
ODBC connection fails with:
[DataDirect][ODBC Progress OpenEdge Wire Protocol driver][OPENEDGE]Broker rejects connection.
Server's received count <n> does not equal client(<n>)'s send count <n>. (1055)
unable to find _sqlsrv2 processes associated with this database
None of the PIDs (Process IDs) for the servers seen in promon are associated with _sqlsrv2 processes.
Default configuration for this database indicates that only 4 servers can be started for this database.
Only 4 default (_mprosrv) server processes were started for the database.
FACT(s) (Environment):
Multiple brokers are being started for the database.
Database is being started via the Progress Explorer utility
Is able to connect ODBC clients to sports2000 database without errors.
promon dbname -> R&D -> Servers shows all PIDs for servers started for the database
All Supported Operating Systems
OpenEdge 10.x
CAUSE:
The conmgr.properties is not properly configured for the correct number of servers that need to be started for this database. By usig the default database configuration of maximum servers of 4 or using insufficient maximum servers prevents the secondary login broker from started any _sqlsrv2 processes as ODBC clients attempted to connect to the database.
FIX:
Modify the default configuration for the database to accurately reflect the total number of servers that will be needed for the database. The formula is # of servers for primary and secondary login brokers + 1 for the secondary login broker itself.