Kbase 21011: Possible Causes of Error 8842 When Using the SQL-92 Server
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
3/17/2003 |
|
SUMMARY:
This solution outlines some possible causes and corrections for error 8842:
14:40:56 BROKER 0: Could not spawn a SQL server. (8842)
EXPLANATION:
The error happens when a client attempts to connect to the database using the SQL-92 server.
SOLUTION:
-- Apply patch 9.1B14 or above on Windows platforms.
The errors you might see in the database log file are:
14:36:56 SERVER : Unable to attach shared memory
sharemem.d.prowin95.91b.wrk.sports91b.0, error 123. (1720)
14:36:56 SQLSRV2 1: Failure during dsmUserConnect (-1)
14:40:56 BROKER 0: Could not spawn a SQL server. (8842)
BROKER 0: Created shared memory with segment_id: 10027008 (9336)
SQLSRV2 1: SQL Server 9.1b.08 started, configuration:
"sports2000.virtualconfig"
SERVER : The shared memory is version 9052; expected 9050 (1178)
SQLSRV2 1: Failure during dsmUserConnect (-1)
BROKER 0: Could not spawn a SQL server. (8842)
-- For remote clients, modify the maximum number of servers (-Mn) that
a database broker can start. Increasing -Mn start-up parameter
could resolve the errors.
NOTE: For SQL-92 database servers, there is a limit of one client
per server. Suggested value:
-Mn = Maximum 4GL servers + Maximum SQL-92 clients + 1
References to Written Documentation:
PC-related fixed bugs: 20010403-006 and 20010328-013.