SMS: SQL Monitor Does Not Create Notification Files After You Install Service Pack 5 (821599)
The information in this article applies to:
- Microsoft Systems Management Server 2.0 SP5
SYMPTOMSAfter you install Systems Management Server (SMS) Service Pack 5 (SP5), you may notice that the SMS SQL Monitor
service (Smsdbmon.exe) does not continue to create notification files in the site server's inboxes. This problem affects operations in SMS that depend on these types of notification files. Some of the most common symptoms are: - Packages are not copied to Distribution Points.
- Advertisements are not offered to SMS clients.
- Manual collection updates do not affect the collection membership.
For example,
if you right-click a collection in the SMS Administrator Console, and then select All Tasks/Update Collection Membership,
SMS SQL Monitor typically creates a notification file named CollectionID.UDC in the
SmsRootFolder\Inboxes\Colleval.box folder. However, if Service Pack 5 is installed, SMS SQL Monitor may not create the file. This notification file instructs SMS Collection Evaluator to re-evaluate the collection members. Without the notification file, the collection is not refreshed until the next collection update cycle. CAUSEThis problem occurs because, in SMS Service Pack 5, the SMS SQL Monitor service restricts write access to the named pipe it uses for communicating with the SQL Server. Specifically, it includes only the Administrators group and the Local System account. If the MSSQLServer service runs with an account that is not part of the Administrators group or the Local System account, SQL Server cannot notify SMS SQL Monitor that it must create a notification file.RESOLUTIONA supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Systems Management Server service pack that contains this hotfix. To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site: Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.The English version of
this fix for SMS 2.0 Service Pack 5 (SP5) sites has the file attributes (or
later) that are listed in the following table. The dates and times for these
files are listed in coordinated universal time (UTC). When you view the file
information, it is converted to local time. To find the difference between UTC
and local time, use the Time Zone tab in the Date and Time
tool in Control Panel.
Date Time Version Size File name Platform
--------------------------------------------------------------------
25-Feb-2003 17:10 2.0.1493.5135 100,768 Smsdbmon.exe X86
25-Feb-2003 17:10 2.0.1493.5135 4,207,568 Smsprov.dll X86
Note Because of file dependencies, the most recent hotfix or feature
that contains these files may also contain additional files. How to Install the HotfixUsing the Hotfix InstallerNote This method is only for Intel-based computers. - Create a folder in a location that is accessible to your SMS site servers.
- Copy the SMS2.0-KB821599-spx-x86-enu.exe update file (where
x
is the service pack version) and platform folders to the new folder. Arrange the folder structure so that the update file is located one folder above the platform folders.
- From each of the primary and secondary SMS site servers in your environment, log on with an account that has administrator credentials.
- Quit the SMS Administrator console, if it is running.
- Run SMS2.0-KB821599-spx-x86-enu.exe, and then follow the instructions in the wizard.
Manually Updating the SMS Site Server- Create a folder in a location that is accessible to your SMS site servers.
- Copy the platform folders that contain the hotfixed files to the new folder.
- From each of your primary and secondary SMS site servers in your environment, log on to your site server by using an account with administrative credentials.
- Quit the SMS administrator console.
- Stop all the SMS services and the
Windows Management service.
Note With WMI build 1085, the service name has changed to "Windows Management Instrumentation". - In the SmsRootFolder\Bin\Platform folder, run the following command:
-
Copy the updated files from the disk or network share to the SMS installation folder:
- SmsRootFolder\Bin\Platform\smsdbmon.exe
- SmsRootFolder\Bin\Platform\Smsprov.dll
- In the SmsRootFolder\Bin\Platform folder, run the following command:
-
Restart the SMS services and the Windows Management service.
Note With WMI build 1085, the service name has changed to "Windows Management Instrumentation".
- Perform a site reset. To do this, click
Start, point to Programs, point to
Systems Management Server, click SMS Setup, click Next, click Next again, and then click
Modify or reset the current installation.
Additional Installation Information
To update remote site computers such as an SMS SQL monitor or an SMS provider that is not located on the site server, use the appropriate method.
Manually Updating a Remote SMS Provider ServerNote Before you install this hotfix on your SMS provider server, you must install it on the SMS site servers in your environment.
-
At the SMS Provider server, stop the following services:
- SMS_SQL_MONITOR_SERVERNAME
-
Windows Management
Note With WMI build 1085, the service name has changed to "Windows Management Instrumentation".
- In the SmsRootFolder\Bin\Platform folder, run the following command:
-
Replace the following files in the SmsRootFolder\Bin\Platform folder
with the versions from the hotfix:
- SmsRootFolder\Bin\Platform\smsdbmon.exe
- SmsRootFolder\Bin\Platform\Smsprov.dll
- In the SmsRootFolder\Bin\Platform folder, run the following command:
-
Restart the following SMS Provider services:
- SMS_SQL_MONITOR_SERVERNAME
-
Windows Management
Note With WMI build 1085, the service name has changed to "Windows Management Instrumentation".
Manually Updating a Remote SMS SQL Monitor ServerNote Before you install this hotfix on your SMS SQL Monitor Server, you must install it on the SMS site servers in your environment.
-
At the SMS SQL Monitor Server, stop the SMS_SQL_MONITOR_SERVERNAME service.
-
Replace the following files in the SmsRootFolder\Bin\Platform folder
with the versions from the hotfix:
- SmsRootFolder\Bin\Platform\smsdbmon.exe
- SmsRootFolder\Bin\Platform\Smsprov.dll
-
Restart the SMS_SQL_MONITOR_SERVERNAME service.
STATUS Microsoft
has confirmed that this is a problem in the Microsoft products that are listed
at the beginning of this article.
WORKAROUNDTo work around this problem, configure the MSSQLServer service to run with an administrator account or the Local System account.
Modification Type: | Minor | Last Reviewed: | 6/5/2006 |
---|
Keywords: | kbHotfixServer kbQFE KB821599 |
---|
|