Microsoft KB Archive/914716

= The event log fills with exception error messages beginning with SQL_ERROR when you start the Groove Enterprise Relay Server for the first time =

Article ID: 914716

Article Last Modified on 4/6/2006

-

APPLIES TO


 * Groove Enterprise Relay Server
 * Groove Enterprise Relay Server 2.5
 * Groove Enterprise Relay Server 3.0
 * Groove Enterprise Relay Server 3.1

-



SYMPTOMS
When you start the Groove Enterprise Relay Server for the first time, the event log fills with exception error messages. The first exception error message that is logged is the following SQL_Error exception error message:

\Include\SqlUtil.h(251) SQL_ERROR returned SQLSTATE: 22002;



CAUSE
This issue occurs because there is a problem with the configured Microsoft SQL Server database.



MORE INFORMATION
If you configure the ODBC interface to use a non-existent SQL Server database instead of the correct relaydir database, the Enterprise Relay Server will not shut down after the first error is logged.

Enterprise Relay Server will continue to try to run, and it will log hundreds of unhandled and translated error messages in the event log. The first error messages that are logged are as follows:

\Include\SqlUtil.h(251) SQL_ERROR returned SQLSTATE: 22002;

Native Error: 0; Diagnostic Message: [Microsoft][ODBC SQL Server Driver]Indicator variable required but not supplied SQLSTATE: 42000;

Native Error: 2812; Diagnostic Message: [Microsoft][ODBC SQL Server Driver][SQL Server]Could not find stored procedure 'dbo.groove_register_node'. GCSQLException caught: reasonCode = 0;

Additional query words: TCN-01014

Keywords: kbtshoot kbprb kbexpertiseinter KB914716

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.