I setup SMS 2003 in a test lab
environment with the following - Server Windows 2000, SQL 2000, SMS 2003.
I followed the procedure to setup a standard SMS site, but once installed, I get
errors in the Component Manager, and cannot discover any clients on the domain:
Component Status
Warning
SMS_SITE_COMPONENT_MANAGER
Warning
SMS_HIERARCHY_MANAGER
Critical
SMS_MP_CONTROL_MANAGER
EventViewer Error: (one of many)
The SMS_SERVER_BOOTSTRAP_SERVER2003 service entered the stopped state.
Any clues?
Contributed By: Luke Packard [MS]
Are the Site Component Manager and Hierarchy Errors about failing to publish
in AD? If so, it's likely either a permissions issue or your schema isn't
updated. Check out this article for info schema extension and AD publishing:
http://www.myitforum.com/articles/8/view.asp?id=6324
MP Control Manager and Site Component Manager
errors could indicate the MP was not successfully installed. What are the
particular status messages in this case and do they give a clue of what the
problem could be? Here are some things to check if your MP is not installing
- The SMS Service account must have
administrator rights to the MP
- Verify you have IIS installed and running on
the MP
- Verify that the DTS Service is enabled on
the MP
- Verify that the Task Scheduler is enabled on
the MP.
- Verify that the Windows Management
Instrumentation service is running on the MP.
- Verify that the SMS Agent Host service is
running on the MP.
- Verify that the World Wide Web Publishing
Service is running on the MP.
- Verify default web site is started on the
MP.
|
 |
To see other SMS
2003 Troubleshooting FAQs click here. |
|
