Microsoft KB Archive/247852
Article ID: 247852
Article Last Modified on 10/27/2006
- Microsoft Systems Management Server 2.0 Standard Edition
This article was previously published under Q247852
Certain configuration changes that you specify in the Systems Management Server (SMS) Administrator console may take longer to become effective than you expect. For example, when you create a new collection, the collection members may not show up immediately as you expect.
When this behavior occurs, the Smsdbmon.log file records the following information and stops logging:
This behavior can occur if the SMS extended stored procedure on the SQL server does not connect to the SQL Monitor service.
Make sure that the SMS_SQL_MONITOR service is running and that the MSSQLServer service runs under the system account or with an account that has administrative rights on the SQL server.
The Trigger Manager thread of the SMS SQL Monitor service component is responsible for notifying other SMS components of database changes. This service allows for an almost instantaneous response to create, update, or delete requests, or to any of a number of other SMS processes such as collection updates. To inform Trigger Manager of specific database events, the xp_SMS_NOTIFICATION SMS extended stored procedure is run by SQL triggers installed by SMS. This extended stored procedure connects to the named pipe that Trigger Manager created. If it cannot connect to the named pipe, SQL Monitor is not informed of database changes and does not create notification files for the various SMS threads.
The SMS extended stored procedure runs in the context of the MSSQLServer service. If the service does not have administrative rights on the SQL server, xp_SMS_NOTIFICATION does not connect to the named pipe.
Additional query words: prodsms smsxp.dll smsxp70.dll
Keywords: kbprb KB247852