|Product:||Windows Operating System|
|Message:||The server service configuration was invalid but system recovered.|
This rule generates an alert any time a service attempts to start up with an invalid configuration. In this case, the alert has warning-level severity, denoting that while the service’s configuration was detected as invalid, the service was still able to start successfully. However, the service may not be running in the desired configuration.
This alert occurs when the service’s configuration parameters in the registry are invalid. Possible causes include:
The first step in resolving this alert is to determine which service generated it.
To determine the service name refer to the description of the alert. This description contains the following information:
The %1 and %2 parameters of the event listed above will be populated in the actual alert description. The first part of the second parameter (%2) is the name of the service.
Once the service name has been determined, the parameter that is incorrectly configured can be determined through the first parameter (%1).
After the service and parameter names are known, the support engineer should attempt to determine if the service configuration parameters can be modified through a user interface that the application provides. If so, this is the best way to fix the configuration. In some cases the configuration must be changed to an alternate configuration and then updated to the desired configuration before the correct settings can be configured.
If a user interface is not provided, the support engineer may choose to modify the relevant parameter directly. This is performed in the following registry location and requires advanced knowledge of the parameter configuration options. HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\%ServiceName\Parameters\%Parameter Name%
If these options do not help to resolve the issue, contact the application vendor for support.
For more information about Event ID 2506, see Knowledge Base article 238316, “Event ID 2506 When You Start Windows 2000” at http://go.microsoft.com/fwlink/?LinkId=28607. See also Knowledge Base article 289683, “INF: NoRemapPipes Error Message Occurs in System Log when You Use SQL Server 2000 on a Windows 2000 cluster,” at http://go.microsoft.com/fwlink/?LinkId=28609.