The SMS_HIERARCHY_MANAGER component of Systems Management Server 2003 may log Event ID 3304 and the following error message in the System event log: “Cannot update the Sites table, try this later”

View products that this article applies to.

SYMPTOMS

In Microsoft Systems Management Server 2003, the SMS_HIERARCHY_MANAGER component may log Event ID 3304 in the System event log. An error message that resembles the following is logged together with this event:

Cannot update the Sites table, try this later.

Additionally, an error message that resembles the following is logged in the Hman.log file:

9/26/2005 2:23:29 PM Site site_code in Sites table: Site status = 1, Detailed status = 1
9/26/2005 2:23:29 PM Processing site control file: Site site_code File C:\SMS\inboxes\hman.box\VST1CK7O.CT2
9/26/2005 2:23:29 PM Update the Sites table: Site=site_code Parent=parent_site_code
9/26/2005 2:23:29 PM *** IF NOT EXISTS (select SiteCode from Sites where SiteCode = 'site_code') insert into Sites (SiteCode, SiteName, ReportToSite, Status, DetailedStatus, TimeStamp, SomeId, SiteType, BuildNumber, Version, SiteServer, InstallDir, TimeZoneInfo) values ("site_code", "site_name", "", 1, 1, 0, "", 2, 3174, "2.50.3174.1018", "server_name", "C:\SMS", "00000168 0000 000A 0000 0005 0002 0000 0000 0000 00000000 0000 0004 0000 0001 0002 0000 0000 0000 FFFFFFC4")~ ELSE update Sites set SiteCode = "site_code", SiteName = "site_name", ReportToSite = "", Status = 1, DetailedStatus = 1, TimeStamp = 0, SomeId = "", SiteType = 2, BuildNumber = 3174, Version = "2.50.3174.1018", SiteServer = "server_name", InstallDir = "C:\SMS", TimeZoneInfo = "00000168 0000 000A 0000 0005 0002 0000 0000 0000 00000000 0000 0004 0000 0001 0002 0000 0000 0000 FFFFFFC4" where SiteCode = "site_code"
9/26/2005 2:23:29 PM *** [42000][0][Microsoft][ODBC SQL Server Driver][SQL Server]Cannot load the DLL smsxp.dll, or one of the DLLs it references. Reason: 126(The specified module could not be found.). : xp_SMS_notification
9/26/2005 2:23:29 PM Cannot update the Sites table, try this later
9/26/2005 2:23:29 PM STATMSG: ID=3304 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_HIERARCHY_MANAGER" SYS=server_name SITE=site_code PID=1960 TID=3400 GMTDATE=Mon Sep 26 19:23:29.430 2005 ISTR0="BF4" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0

In some situations, the SMS Services may fail to start and return error 1053:

The service did not respond to the start or control request in a timely fashion.

Additionally, you may see information that resembles this in the application event log:

10/2/2008 1:55:54 PM 1 0 1023 Perflib N/A <SiteServer> SMS_SOFTWARE_INVENTORY_PROCESSOR
10/2/2008 1:55:54 PM 1 0 1023 Perflib N/A <SiteServer> SMS_SOFTWARE_METERING_PROCESSOR
10/2/2008 1:55:54 PM 1 0 1023 Perflib N/A <SiteServer> SMS_STATUS_MANAGER
10/2/2008 1:55:54 PM 1 0 1023 Perflib N/A <SiteServer> SMS_DISCOVERY_DATA_MANAGER
10/2/2008 1:55:54 PM 1 0 1023 Perflib N/A <SiteServer> SMS_EXECUTIVE
10/2/2008 1:55:54 PM 1 0 1023 Perflib N/A <SiteServer> SMS_INVENTORY_DATA_LOADER
10/2/2008 1:55:54 PM 1 0 1023 Perflib N/A <SiteServer> SMS_LAN_SENDER
10/2/2008 1:55:54 PM 1 0 1023 Perflib N/A <SiteServer> SMS_SCHEDULER
10/2/2008 1:55:54 PM 1 0 1023 Perflib N/A <SiteServer> SMS_SOFTWARE_INVENTORY_PROCESSOR
10/2/2008 1:55:54 PM 1 0 1023 Perflib N/A <SiteServer> SMS_SOFTWARE_METERING_PROCESSOR
10/2/2008 1:55:54 PM 1 0 1023 Perflib N/A <SiteServer> SMS_STATUS_MANAGER

Back to the top

CAUSE

Typically, this issue occurs if one or more Microsoft C Runtime Library files or Microsoft Foundation Class Library files are missing or are not registered. Specifically, a missing Msvcr70.dll file is known to cause this issue.

Note The Msvcr70.dll file is a Microsoft Visual C Runtime Library file.

Many Microsoft and third-party programs use Microsoft C Runtime Library files and Microsoft Foundation Class Library files. If you remove a program that uses one of these files, the uninstall program may prompt you to remove the file. This issue may occur if the uninstall program does not detect that other programs use the file.

Back to the top

RESOLUTION

To resolve this issue, make sure that the Msvcr70.dll file exists in the %Windir%\System32 folder. If the Msvcr70.dll file does not exist in this folder, copy a version of the file from the SMS\Bin\i386\System32 folder to the %Windir%\System32 folder. Then, register the file by typing the following command at a command prompt:

regsvr32 msvcr70.dll

Note If you receive a "DllRegisterServer entry point was not found" error message when you run this command, you can safely ignore it.

Make sure that the following Microsoft C Runtime Library files and Microsoft Foundation Class Library files are also installed in the %Windir%\System32 folder.

Note These files are located in the SMS\Bin\i386\System32 folder.

Mfc42.dll
Mfc42u.dll
Mfc70.dll
Mfc70u.dll
Msvci70.dll
Msvcirt.dll
Msvcp50.dll
Msvcp60.dll
Msvcp70.dll
Msvcr70.dll
Msvcrt.dll
Msvcrt20.dll
Msvcrt40.dll

If one or more of these files are missing from the in the %Windir%\System32 folder, copy them from the SMS\Bin\i386\System32 folder. Then, register the files by running the regsvr32 command at a command prompt.

Important If you replace or register any of these files, you must restart the SMS_EXECUTIVE service. To do this, follow these steps:

Click Start, point to All Programs, click Systems Management Server, and then click SMS Administrator Console.
In SMS Administrator Console, expand Site Database (SiteCode - SiteName), expand Tools, right-click SMS Service Manager, and then click Start SMS Service Manager.
In SMS Service Manager, expand SiteCode, and then expand Components.
Locate and then click SMS_HIERARCHY_MANAGER.
In the results pane, click SMS_HIERARCHY_MANAGER, and then click the Query icon.
On the menu bar, click the Stop icon, and then click the Start icon.
When the SMS_HIERARCHY_MANAGER component restarts, check the Hman.log file. Make sure that the error message that is mentioned in the "Symptoms" section is not logged in this file.