Welcome to the Blogcast Repository Sign in | Join | Help
Search BlogCastRepository.com for:
in Search

245 BlogCasts in The BlogCast Repository!

MP errors: Failed to query website and not responding to HTTP requests.

Last post 12-05-2006 9:32 PM by ArmandC. 12 replies.
Page 1 of 1 (13 items)
Sort Posts: Previous Next
  • 10-09-2006 6:14 PM

    MP errors: Failed to query website and not responding to HTTP requests.

    I have a new install of SMS 2003 that I'm trying to get up and running.  SP2 has been applied and it's running on a Windows 2003 Std. Server.  I cannot get any clients to register, however due to the Management Point errors I'm receiving.

    Using the MPTroubleshooter, all the pre-installation tests pass with no problem; however, I get 2 errors when running the post-installation tests:
    1)  Testing MPLIST HTTP request functionality - Failed - Failed to query web site:  http://NAME:80/SMS_MP/.sms_aut?MPLIST
    2)  Testing MPCERT HTTP request functionality - Failed - Failed to query web site:  http://NAME:80/SMS_MP/.sms_aut?MPCERT

    Additionally, in the SMS Admin Console under Site Status -> 001 - Company -> Component Status -> SMS_MP_CONTROL_MANAGER, I get the error "MP Control Manager detected MP is not responding to HTTP requests.  The http error is Service Unavailable."

    I have removed the MP, uninstalled IIS, rebooted, reinstalled IIS with all components, and reinstalled the MP to no avail.

    Any ideas are GREATLY appreciated!

    Thanks,
    Chris

    • Post Points: 20
  • 10-09-2006 6:41 PM In reply to

    Re: MP errors: Failed to query website and not responding to HTTP requests.

    On the MP, verify the install of the MP was successful by reading the MPSetup.log file. Once the setup is a success, you should see HTTP 200 success messages in the mpcontrol.log file. Either log giving you problems?
    Brian S. Tucker
    The Blogcast Repository - MCSE, MCDBA & MCT
    • Post Points: 20
  • 10-10-2006 9:19 AM In reply to

    Re: MP errors: Failed to query website and not responding to HTTP requests.

    Brian,
    Thanks for the reply.  Below is an excerpt from the MPSetup.log file.  It shows that MP installed correctly:

    <10-09-2006 16:50:18> MP Setup Started....
    <10-09-2006 16:50:18> Parameters: C:\SMS\bin\i386\MPsetup.exe /install /siteserver:VULCAN
    <10-09-2006 16:50:18> Installing the MP
    <10-09-2006 16:50:18> Passed OS version check.
    <10-09-2006 16:50:18> IIS Service is installed.
    <10-09-2006 16:50:18> Management Point already installed (Product Code: {391CC246-8659-4973-ABAC-DB4654431DF9}).  Upgrading/Reinstalling MP
    <10-09-2006 16:50:18> New Management Point is the same product code.  This is a minor upgrade.
    <10-09-2006 16:50:18> Enabling MSI logging.  MP.MSI will log to C:\SMS\logs\MPMSI.log
    <10-09-2006 16:50:18> Installing C:\SMS\bin\i386\mp.msi REINSTALL=ALL REINSTALLMODE=vmaus CCMINSTALLDIR="C:\SMS_CCM" CCMSERVERDATAROOT="C:\SMS" USESMSPORTS=TRUE SMSPORTS=80 CCMENABLELOGGING=TRUE CCMLOGLEVEL=1 CCMLOGMAXSIZE=1000000 CCMLOGMAXHISTORY=1
    <10-09-2006 16:52:57> MP.MSI exited with return code: 0
    <10-09-2006 16:52:57> Installation was successful.

    Below is an excerpt from the mpcontrol.log file.  I do not ever receive any HTTP 200 success messages:

    SMS_MP_CONTROL_MANAGER received START notification. SMS_MP_CONTROL_MANAGER 10/9/2006 4:53:06 PM 2660 (0x0A64)
    CWmi::Connect(): IWbemServices value is 0x189527c SMS_MP_CONTROL_MANAGER 10/9/2006 4:53:06 PM 2660 (0x0A64)
    CMPControlManager::ReadConfigurationSettings(): Periodic Interval is 1800000 SMS_MP_CONTROL_MANAGER 10/9/2006 4:53:06 PM 2660 (0x0A64)
    CMPControlManager::ReadConfigurationSettings(): WINS Interval is 14400000 SMS_MP_CONTROL_MANAGER 10/9/2006 4:53:06 PM 2660 (0x0A64)
    MPStart(): ReadConfigurationSettings() returned 0x0. SMS_MP_CONTROL_MANAGER 10/9/2006 4:53:06 PM 2660 (0x0A64)
    ReadMPDwordSettings(): RegQueryValueExW() failed for MPHealthCheckIntervalInSeconds 2 SMS_MP_CONTROL_MANAGER 10/9/2006 4:53:06 PM 2660 (0x0A64)
    ReadMPDwordSettings(): RegQueryValueExW() failed for MPHealthCheckTimeoutInSeconds 2 SMS_MP_CONTROL_MANAGER 10/9/2006 4:53:06 PM 2660 (0x0A64)
    ReadMPDwordSettings(): RegQueryValueExW() failed for MPHealthCheckStatusMessageIntervalInSeconds 2 SMS_MP_CONTROL_MANAGER 10/9/2006 4:53:06 PM 2660 (0x0A64)
    MPStart(): CreateThread() succeeded with id 0xdc4. SMS_MP_CONTROL_MANAGER 10/9/2006 4:53:06 PM 2660 (0x0A64)
    ------ RegisterForNotification(): Registering again! ------- SMS_MP_CONTROL_MANAGER 10/9/2006 4:53:06 PM 2660 (0x0A64)
    MPStart(): Registered for Notifications. SMS_MP_CONTROL_MANAGER 10/9/2006 4:53:06 PM 2660 (0x0A64)
    MPStart(): Read all MP Settings. SMS_MP_CONTROL_MANAGER 10/9/2006 4:53:06 PM 2660 (0x0A64)
    CWmi::Connect(): IWbemServices value is 0x189527c SMS_MP_CONTROL_MANAGER 10/9/2006 4:53:06 PM 2660 (0x0A64)
    CMPControlManager::WriteToCCMSettings(): WMI Connection established. SMS_MP_CONTROL_MANAGER 10/9/2006 4:53:06 PM 2660 (0x0A64)
    CMPControlManager::WriteToCCMSettings(): Successful. SMS_MP_CONTROL_MANAGER 10/9/2006 4:53:06 PM 2660 (0x0A64)
    RegisterWithWINS: Registering the WINS name MP_001          ... SMS_MP_CONTROL_MANAGER 10/9/2006 4:53:06 PM 2660 (0x0A64)
    RegisterWithWINS: EnumerateLANAs() returned 0x0 SMS_MP_CONTROL_MANAGER 10/9/2006 4:53:06 PM 2660 (0x0A64)
    RegisterWithWINS: ResetAll() returned 0x0 SMS_MP_CONTROL_MANAGER 10/9/2006 4:53:06 PM 2660 (0x0A64)
    NetBIOS_AddName(): LocalName: MP_001           LanaNumber: 3 SMS_MP_CONTROL_MANAGER 10/9/2006 4:53:06 PM 2660 (0x0A64)
    RegisterWithWINS: NetBIOS_AddName(LANA=3) returned 0x0 SMS_MP_CONTROL_MANAGER 10/9/2006 4:53:06 PM 2660 (0x0A64)
    MPStart(): RegisterWithWINS() returned 0x0 SMS_MP_CONTROL_MANAGER 10/9/2006 4:53:06 PM 2660 (0x0A64)
    Successfully Registered for IP Address Change notifications. SMS_MP_CONTROL_MANAGER 10/9/2006 4:53:06 PM 2660 (0x0A64)
    MPStart(): RegisterForIPAddressChangeNotification() returned 0x0 SMS_MP_CONTROL_MANAGER 10/9/2006 4:53:06 PM 2660 (0x0A64)
    SMS_MP_CONTROL_MANAGER successfully STARTED. SMS_MP_CONTROL_MANAGER 10/9/2006 4:53:06 PM 2660 (0x0A64)
    ******************************************************************************** SMS_MP_CONTROL_MANAGER 10/9/2006 4:53:06 PM 2660 (0x0A64)
    ------ MPNotifyThreadRoutine(): Got a change Notification! ------- SMS_MP_CONTROL_MANAGER 10/9/2006 4:53:07 PM 3524 (0x0DC4)
    ------ RegisterForNotification(): Registering again! ------- SMS_MP_CONTROL_MANAGER 10/9/2006 4:53:07 PM 3524 (0x0DC4)
    MPNotifyThreadRoutine(): HandleMPRegistryChanges() returned 0x0 SMS_MP_CONTROL_MANAGER 10/9/2006 4:53:07 PM 3524 (0x0DC4)
    ------ MPNotifyThreadRoutine(): Got a change Notification! ------- SMS_MP_CONTROL_MANAGER 10/9/2006 4:54:23 PM 3524 (0x0DC4)
    ------ RegisterForNotification(): Registering again! ------- SMS_MP_CONTROL_MANAGER 10/9/2006 4:54:23 PM 3524 (0x0DC4)
    MPNotifyThreadRoutine(): HandleMPRegistryChanges() returned 0x0 SMS_MP_CONTROL_MANAGER 10/9/2006 4:54:23 PM 3524 (0x0DC4)
    ------ MPNotifyThreadRoutine(): Got a change Notification! ------- SMS_MP_CONTROL_MANAGER 10/9/2006 4:54:23 PM 3524 (0x0DC4)
    ------ RegisterForNotification(): Registering again! ------- SMS_MP_CONTROL_MANAGER 10/9/2006 4:54:23 PM 3524 (0x0DC4)
    MPNotifyThreadRoutine(): HandleMPRegistryChanges() returned 0x0 SMS_MP_CONTROL_MANAGER 10/9/2006 4:54:23 PM 3524 (0x0DC4)
    Http verification .sms_aut (port 80) failed with status code 503, Service Unavailable SMS_MP_CONTROL_MANAGER 10/9/2006 5:03:06 PM 3524 (0x0DC4)
    Http verification .sms_aut (port 80) failed with status code 503, Service Unavailable SMS_MP_CONTROL_MANAGER 10/9/2006 5:13:06 PM 3524 (0x0DC4)
    STATMSG: ID=5436 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_MP_CONTROL_MANAGER" SYS=VULCAN SITE=001 PID=1792 TID=3524 GMTDATE=Mon Oct 09 22:13:06.859 2006 ISTR0="Service Unavailable" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_MP_CONTROL_MANAGER 10/9/2006 5:13:06 PM 3524 (0x0DC4)
    Http verification .sms_aut (port 80) failed with status code 503, Service Unavailable SMS_MP_CONTROL_MANAGER 10/9/2006 5:23:06 PM 3524 (0x0DC4)
    Http verification .sms_aut (port 80) failed with status code 503, Service Unavailable SMS_MP_CONTROL_MANAGER 10/9/2006 5:33:06 PM 3524 (0x0DC4)
    Http verification .sms_aut (port 80) failed with status code 503, Service Unavailable SMS_MP_CONTROL_MANAGER 10/9/2006 5:43:06 PM 3524 (0x0DC4)
    Http verification .sms_aut (port 80) failed with status code 503, Service Unavailable SMS_MP_CONTROL_MANAGER 10/9/2006 5:53:06 PM 3524 (0x0DC4)
    Http verification .sms_aut (port 80) failed with status code 503, Service Unavailable SMS_MP_CONTROL_MANAGER 10/9/2006 6:03:06 PM 3524 (0x0DC4)
    Http verification .sms_aut (port 80) failed with status code 503, Service Unavailable SMS_MP_CONTROL_MANAGER 10/9/2006 6:13:06 PM 3524 (0x0DC4)

    Thanks for any help you can provide!

    Chris


    • Post Points: 20
  • 10-10-2006 11:12 AM In reply to

    Re: MP errors: Failed to query website and not responding to HTTP requests.

    Brian S. Tucker
    The Blogcast Repository - MCSE, MCDBA & MCT
    • Post Points: 20
  • 10-10-2006 1:41 PM In reply to

    Re: MP errors: Failed to query website and not responding to HTTP requests.

    Brian,
    Thanks for the reply.  I read the link you sent and I confirmed that the IWAM account is part of the IIS_WPG group and I also used regedit to check the permissions on the HKLM\SYSTEM\ControlSet001\Services\W3SVC key.  The IIS_WPG group already had read permissions.  Just for testing purposes, I also assigned read permissions to the IWAM account.

    I've rebooted the box and run the MP troubleshooter again; the same 2 errors appear.

    Any other thoughts/ideas???  I do appreciate it ...

    Chris Odom

    • Post Points: 5
  • 10-11-2006 1:15 PM In reply to

    Re: MP errors: Failed to query website and not responding to HTTP requests.

    I thought I'd share another related error message to see if it might help find an answer.

    In the server's "system event log," the following error appears:
    The identity of application pool 'SMS Management Point Pool' is invalid, so the World Wide Web Publishing Service can not create a worker process to serve the application pool.  Therefore, the application pool has been disabled.

    I have no doubt this is tied directly into why I can't get my MP and IIS to work.

    Thanks,
    Chris

    • Post Points: 20
  • 10-11-2006 2:34 PM In reply to

    Re: MP errors: Failed to query website and not responding to HTTP requests.

    I just had a MP go out today. I did the same steps you mentioned to uninstall, but I also tend to delete the Inetpub folder and all contents after the uninstal. Reboot, install IIS and related components. It came back up for me. Try doing another uninstall and delete ALL the folders and files for IIS.
    Brian S. Tucker
    The Blogcast Repository - MCSE, MCDBA & MCT
    • Post Points: 20
  • 10-11-2006 4:00 PM In reply to

    Re: MP errors: Failed to query website and not responding to HTTP requests.

    I uninstalled the MP, rebooted, uninstalled IIS, rebooted, totally deleted the inetpub directory, rebooted, reinstalled IIS with all components selected, rebooted, and reinstalled the MP.

    After checking the MPSETUP log file, I confirmed that the MP had been successfully installed.  I went ahead and rebooted again.  I then opened the MP Troubleshooter and the same 2 errors occured.  I then checked the system's event log and had these two entries:

    The identity of application pool 'SMS Management Point Pool' is invalid, so the World Wide Web Publishing Service can not create a worker process to serve the application pool. Therefore, the application pool has been disabled.

    A failure was encountered while launching the process serving application pool 'SMS Management Point Pool'. The application pool has been disabled.

    I just don't get it.  I thought perhaps SMS 2003 would be easier to get up and going than SMS 2.0, but I'm getting quite frustrated with it...

    Thanks,
    Chris

    • Post Points: 20
  • 10-11-2006 4:20 PM In reply to

    Re: MP errors: Failed to query website and not responding to HTTP requests.

    • Post Points: 20
  • 10-12-2006 9:55 AM In reply to

    Re: MP errors: Failed to query website and not responding to HTTP requests.

    Brian,

    Thanks for the links.  I too have been searching the Internet for help and never came across the groups in your links...fantastic!

     

    Well...I agree that it appears to be an IIS permissions issue, but I just can't seem to figure it out.  I thought we'd discovered the solution in the first link (making the IWAM account a local admin), but that didn't work either.

     

    I also uninstalled and deleted everything (IIS and MP) and then reinstalled IIS, made the IWAM an admin, reinstalled the MP, and then the same errors occurred.

     

    Very strange...I'll keep looking as well...

    Chris

    • Post Points: 5
  • 10-12-2006 11:02 AM In reply to

    Re: MP errors: Failed to query website and not responding to HTTP requests.

    Okay...very strange, but somehow I'm down to only one error.  The only portion not working now is the MPCERT.

    Strange...

    Chris

    • Post Points: 20
  • 11-27-2006 7:39 AM In reply to

    Re: MP errors: Failed to query website and not responding to HTTP requests.

    Chris,

      I don't know if you've fixed this issue yet, or gave up on it, but I had the exact issue you had, word for word. I worked about 2 weeks trying everything I could to figure it out. I uninstalled/reinstalled the MP, reinstalled IIS, and made sure that everything was working properly, but nothing I tried worked. The fix for my problem was a problem with the IUSR account that IIS was using for the virtual directory. Check the local group policy of your MP, and see if the Guests group is added to the Deny access to this computer from the network User Right Assignment. If so, check to see if the account that your SMS_MP virtual directory uses is a part of that group. If it is, remove it from the group, force an update of your group policies, and restart the IIS services. Once that's done, check to see if you receive errors again when you run MP troubleshooter or check component status in SMS Admin console.

    Hope this helps.

    Joie

    "Since 1982"
    Joie
    • Post Points: 20
  • 12-05-2006 9:32 PM In reply to

    • ArmandC
    • Top 500 Contributor
    • Joined on 09-15-2006
    • Seattle
    • Posts 2
    • Points 25

    Re: MP errors: Failed to query website and not responding to HTTP requests.

    I had the exact same problem but solved it last night. I had tried everything; uninstalling the MP, IIS, ran CCMClean /all, even went so far as to completely de-install the secondary site. But even after all that I did a reinstall from scratch and STILL got the same error. I found the following error in my System Event log:

    The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID

    {A9E69610-B80D-11D0-B9B9-00A0C922E750}

     to the user servername\IWAM_servername SID (S-1-5-21-xxxxxxxxx-xxxxxxxxxxxx-xxxxxxxx-1011).  This security permission can be modified using the Component Services administrative tool.

    So turns out the IIS Admin service DCOM object did not have the correct perms. Looking at another functioning secondary site MP I saw that the Authenticated Users group must have the allow Local and Remote Activation perms on the IIS Admin Service. Once I added Authenticated Users and granted those right I bounced IIS and POOF everything is now working as expected...

    I have another secondary site to install as well so I checked after installing IIS prerequisites and sure enough the IIS Admin service DCOM object has the AUthenticated Users group listed with the Launch Local & Local Activation perms. Now I'm not sure if those are installed that way by default but I also already had the Adv Client installed as well but I doubt that had any affect on the IIS install. So My guess is this is a IIS installation bug and not really related to SMS. I plan to confirm using a virtual server that has neither IIS or the Adv Client installed...Hope this helps...

    -Armand

    • Post Points: 5
Page 1 of 1 (13 items)