WMI Issue on Site Server

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance



Hi,

I have single site hosted on a site Server with SQL Database of a different
Server. Everything runs on Windows 2003 Server SP1, and SQL Version is SQL
2000 SP4. SMS 2003 SP1.

I'm getting SMS Message ID 4963 and 1020 errors in the MP_Control_Manager
component every hour. When I connect to SMS Service Manager, I get an error
stating "The Specified Server is not an SMS Site Server"

4963 message reads:

MP Control Manager detected MPsetup has failed to create the CCM_Incoming
Virtual Directory.

Possible cause: The IIS IWAM account has expired, been disabled, or has
invalid or too restrictive logon hours. You may verify this information by
running the net user command line for the IWAM account. (i.e.: "net user
IWAMMachineName)
Solution: Use the output to verify that the account is enabled, and logon is
possible during the time of installation. Note: You can use "net user" to
modify the account properties.

Possible cause: The IIS IUSR account has expired, been disabled, or has
invalid or too restrictive logon hours. You may verify this information by
running the net user command line for the IUSR account. (i.e.: "net user
IWAMMachineName)
Solution: Use the output to verify that the account is enabled, and logon is
possible during the time of installation. Note: You can use "net user" to
modify the account properties.

Possible cause: The Default Web Site is disabled in IIS.
Solution: Verify that the Default Web Site is enabled, and functioning
properly.

For more information, refer to Micrsoft Knowledge Base article 838891.

1020 message reads:

SMS Site Component Manager failed to reinstall this component on this site
system.

Solution: Review the previous status messages to determine the exact reason
for the failure. SMS Site Component Manager will automatically retry the
reinstallation in 60 minutes. To force SMS Site Component Manager to
immediately retry the reinstallation, stop and restart SMS Site Component
Manager using the SMS Service Manager.

I have followed the guidance in KB838891 and have followed through the steps
in "Troubleshooting Management Points for SMS 2003". This was all working
successfully up until last week.

When I try to connect to WMI on the site Server, using WBEMTEST tool, I get
the following error on attempting to connect to the root\sms namespace:

0x8004100e Invalid Namespace.

It appears my WMI installation is corrupted somehow. How can I repair this?

Thanks

John


.



Relevant Pages

  • Re: Discovery problem
    ... I've also discovered another strange thing: if I change the SMS Service ... Of course, the account is not disabled, it does have administrative rights ... Due to an OS error, the SMS Site Component Manager is marked ...
    (microsoft.public.sms.setup)
  • [NT] Security considerations to keep in mind when using Site Server 3.0
    ... Site Server version 3.0 Commerce Edition ... LDAP_Anonymous user account, which is used by the included LDAP service. ... A valid NT user account is required to upload ...
    (Securiteam)
  • Re: SMS_MP_CONTROL_MANAGER
    ... Advanced SMS client. ... Retrieval & Evaluation Cycle and Machine Policy Retrieval ... >I have that account in the proper group and it is not ... >>ACLd with needed rights on the site server. ...
    (microsoft.public.sms.setup)
  • Re: Active Directory
    ... >>> our site with a Central Site Server and several secondary site servers ... >>> Directory System Group Discovery enabled, ... > Any idea which account we should deny access to as we have tried the ... It depends, if you are using SMS 2003 Advanced security, it will be the ...
    (microsoft.public.sms.setup)
  • Re: MSSecure.cab
    ... My Sync Host is my Site Server. ... to the SMSCliToknAcct& local account. ... Data Source directory and the package object. ...
    (microsoft.public.sms.admin)