RE: IIS config problem with MP - msg 5436
From: Marge E (MargeE_at_discussions.microsoft.com)
Date: Mon, 7 Mar 2005 11:59:03 -0800
I am in the process of reinstalling the MP so I can't use the tool yet. But
when I try to install the MP, I receive the following error:
SMS Site Component Manager failed to install this component, because it
either can't find or configure Internet Information Services Background
Intelligent Transfer Service (BITS) Server Extensions.
Possible cause: Background Intelligent Transfer Service (BITS) is not
installed or running.
Solution: Use Add/Remove Programs to install Background Intelligent Transfer
Service (BITS) .
Possible cause: SMS Site Component Manager does not have sufficient access
rights to administer and configure Background Intelligent Transfer Service
(BITS) on this site system.
Solution: Verify that the Site System Connection accounts are properly
configured to allow SMS to administer the site system.
SMS Site Component Manager cannot install component SMS_MP_CONTROL_MANAGER
until Background Intelligent Transfer Service (BITS) is installed and
configured correctly. Refer to your SMS documentation or the Microsoft
Knowledge Base for further information.
BITS is installed. I'm not sure what account I should be looking at and
what permissions it needs?
"Marge E" wrote:
> We recently had to uninstall and reinstall IIS on our management point. Now
> I am not getting updated inventory. The IIS logs look like they are unable
> to talk to the MP. And I am getting the following error in my site status.
> MP Control Manager detected MP is not responding to HTTP requests. The http
> error is Unauthorized.
> Possible cause: MP service is not started or not responding.
> Solution: Manually restart the SMS Agent Host service on the MP.
> Possible cause: IIS service is not responding.
> Solution: Manually restart the W3SVC service on the MP.
> Possible cause: MP encountered an error when connecting to SQL Server.
> Solution: Verify MP can connect to the SQL server and has sufficient access
> rights to the SQL server site system.
> Possible cause: The Default Web Site is disabled in IIS.
> Solution: Verify that the Default Web Site is enabled, and functioning
> Any ideas?