Microsoft KB Archive/267889

= SMS: SMS_EXECUTIVE Service Not Installed During Setup =

Article ID: 267889

Article Last Modified on 10/27/2006

-

APPLIES TO


 * Microsoft Systems Management Server 2.0 Standard Edition
 * Microsoft Systems Management Server 1.2 Standard Edition

-



This article was previously published under Q267889



IMPORTANT: This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows Registry



SYMPTOMS
After you successfully complete a Systems Management Server (SMS) site setup, the SMS Site Component Manager may not install the SMS_EXECUTIVE service. If logging is enabled for the SMS Site Component Manager, the Sitecomp.log file may log the following error message:

Could not install the performance counters.  Installation failed and will be retried in the next polling cycle. 

In some cases, the SMS Site Component Manager log may not show an error. However, the SMS Site Component Manager stops running after approximately two minutes and a CrashDump folder is created in the \SMS\Logs folder. The Crash.log file in the CrashDump folder may report the following information:

EXCEPTION INFORMATION

Time = MM/DD/YYYY HH:MM:SS.xxx

Service name = SMS_SITE_COMPONENT_MANAGER

Thread name = SMS_SITE_COMPONENT_MANAGER

Executable = E:\SMS\bin\i386\sitecomp.exe

Process ID = 220 (0xdc) Thread ID = 221 (0xdd) Instruction address = 5f4039e4

Exception = c0000005 (EXCEPTION_ACCESS_VIOLATION)

Description = &quot;The thread tried to read from the virtual address FFFFFFF4 for which it does not have the appropriate access.&quot;

Raised inside CService mutex = No

CService mutex description = &quot;&quot;



CAUSE
This issue can occur if the Perfc009.dat and Perfh009.dat files that are located in the \Winnt\System32 folder have been corrupted or are missing. If these files are not available, the following registry setting may be deleted or disabled (grayed-out):

HKEY_LOCAL_MACHINE\Software\Microsoft\WindowsNT\CurrentVersion\Perflib\009



RESOLUTION
To resolve this problem, obtain the latest service pack for Systems Management Server version 2.0. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

288239 SMS: How to Obtain the Latest Systems Management Server 2.0 Service Pack



WORKAROUND
WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

To resolve this issue, modify the Perflib registry key.

IMPORTANT: This article contains information about editing the registry. Before you edit the registry, make sure you understand how to restore it if a problem occurs. For information about how to do this, view the &quot;Restoring the Registry&quot; Help topic in Regedit.exe or the &quot;Restoring a Registry Key&quot; Help topic in Regedt32.exe.

The following steps can be used to correct the Perflib key.

Note: These steps would wipe out all performance counters, and enable only the NT counters that are installed with the operating system.
 * 1) Stop the Site component Manager.
 * 2) Expand perfc009.da_ and perfh.009.da_ from an NT4 Server source to \winnt\system32 as perfc009.dat and perfh009.dat respectively You can expand these files from a command prompt by typing either

expand perfc009.da_ perfc009.dat

-or-

expand perfh009.da_ perfh009.dat


 * 1) In HKEY_LOCAL_MACHINE\Software\Microsoft\WindowsNT\CurrentVersion\Perflib, set the value of Last Counter to 0x736 and Last Help to 0x737


 * 1) The Perflib\009 key should now be re-populated. Run performance monitor and verify that NT counters are available.
 * 2) Restart the SMS Site Component Manager. It should successfully re-install the SMS Executive.



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Systems Management Server 2.0 Service Pack 3. 

MORE INFORMATION
The following sitecomp.log sample shows the error in context:

Installing component SMS_EXECUTIVE... STATMSG: ID=1014 SEV=I LEV=M SOURCE=&quot;SMS Server&quot; COMP=&quot;SMS_EXECUTIVE&quot; SYS=SMSTEST SITE=T00 PID=147 TID=43 GMTDATE=Mon Jul 03 11:25:24.500 2000 ISTR0=&quot;&quot; ISTR1=&quot;&quot; ISTR2=&quot;&quot; ISTR3=&quot;&quot; ISTR4=&quot;&quot; ISTR5=&quot;&quot; ISTR6=&quot;&quot; ISTR7=&quot;&quot; ISTR8=&quot;&quot; ISTR9=&quot;&quot; NUMATTRS=0 The &quot;D:\WINNT&quot; directory has 1540472832 bytes free out of 2146764800 total bytes. The component is being installed on the site server, no files need to be installed in the &quot;D:\SMS&quot; directory because the files are already there. 4456402 bytes are required in the &quot;D:\WINNT&quot; directory for this component's files. Installed file D:\WINNT\system32\smsmsgs\srvmsgs.cmd. Installed file D:\WINNT\system32\smsmsgs\climsgs.cmd. Installed file D:\WINNT\system32\smsmsgs\provmsgs.cmd. All files installed. Starting bootstrap operations... Installed service SMS_SERVER_BOOTSTRAP_SMSTEST. Starting service SMS_SERVER_BOOTSTRAP_SMSTEST with command-line arguments &quot;T00 D:\SMS /install D:\WINNT\system32\smsmsgs\srvmsgs.cmd&quot;...  &quot;D:\WINNT\system32\smsmsgs\srvmsgs.cmd /install /siteserver:SMSTEST&quot; executed successfully on server SMSTEST. Bootstrap operation successful. Starting service SMS_SERVER_BOOTSTRAP_SMSTEST with command-line arguments &quot;T00 D:\SMS /install D:\WINNT\system32\smsmsgs\climsgs.cmd&quot;...  &quot;D:\WINNT\system32\smsmsgs\climsgs.cmd /install /siteserver:SMSTEST&quot; executed successfully on server SMSTEST. Bootstrap operation successful. Starting service SMS_SERVER_BOOTSTRAP_SMSTEST with command-line arguments &quot;T00 D:\SMS /install D:\WINNT\system32\smsmsgs\provmsgs.cmd&quot;...  &quot;D:\WINNT\system32\smsmsgs\provmsgs.cmd /install /siteserver:SMSTEST&quot; executed successfully on server SMSTEST. Bootstrap operation successful. Deinstalled service SMS_SERVER_BOOTSTRAP_SMSTEST. Bootstrap operations completed. RemoveBrokenPerfCounterStringsFromRegistry: ERROR: Could not read the &quot;HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Perflib\009&quot; registry key on server &quot;SMSTEST&quot;. GetLastError returned 122: The data area passed to a system call is toosmall. InstallPerformaceObjectsForComponentIntoRegistry: ERROR: Could not read the &quot;HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Perflib\009&quot; registry key on server &quot;SMSTEST&quot;. GetLastError returned 122: The data area passed to a system call is toosmall. Could not install the performance counters. Installation failed and will be retried in the next polling cycle. Additionally, text similar to the following may exist in the smsexec.log CInterthreadQueueSource::InitializePerfObj: ERROR: Could not initialize the &quot;SMS In-Memory Queues&quot; performance counters. WARNING: The &quot;SMS In-Memory Queues&quot; performance counters will not be monitorable.

Additional query words: prodsms

Keywords: kbtshoot kbbug kbconfig kbfix kbserver kbsetup kbsitecomp kbsms200presp3fix KB267889

-

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

© Microsoft Corporation. All rights reserved.