JSI Tip 10444. A SCM (Service Control Manager) event cannot be logged in the System event log on Windows Server 2003?

After applying SP1 (Service Pack 1) to Windows Server 2003, and running Sysprep.exe or Dcpromo.exe on the Windows Server 2003 SP1 computer, SCM cannot log events in the System event log.

This behavior will occur if the logged on console user is not the same user that registered the WMI (Windows Management Instrumentation) repository, or is not registered in the WMI repository.

To workaround this behavior:

1. Insure that the AT Service Account is the System Account:

            A) Open a CMD.EXE window.

            B) Type %SystemRoot%\explorer.exe ::\{20D04FE0-3AEA-1069-A2D8-08002B30309D\}\::\{21EC2020-3AEA-1069-A2DD-08002B30309D\}\::\{D6277990-4C6A-11CF-8D87-00AA0060F5BF\} and press Enter.

            C) Using the Advanced menu, press AT Service Account.

            D) Check System Account and press OK.

2. Using AT2.bat, type AT2 Tp2 and press Enter.

3. Type AT %Tp2% /i mofcomp %windir%\system32\wbem\scm.mof and press Enter. This will recompile the Scm.mof file in two minutes, using the System Account context.

4. Close the CMD.EXE Windows.

Hide comments


  • Allowed HTML tags: <em> <strong> <blockquote> <br> <p>

Plain text

  • No HTML tags allowed.
  • Web page addresses and e-mail addresses turn into links automatically.
  • Lines and paragraphs break automatically.