Re: SMS_MP_CONTROL_MANAGER msg id 5436

From: Darren (DSlaughter_at_mrpricegroup.com)
Date: 07/26/04


Date: Mon, 26 Jul 2004 05:21:12 -0700


>-----Original Message-----
>"Darren" <DSlaughter@mrpricegroup.com> wrote in message
news:<128401c46f03$99a2e0f0$a301280a@phx.gbl>...
>> Hi
>>
>> I have installed a Windows 2003 Server, with IIS 6,
BITS,
>> SQL 2000 SP3 and SMS 2003 as a Primary Site in a
Native
>> AD 2003. I have also configured it to be the CAP, SLP,
>> and MP, but I continue to receive Message ID 5436
errors
>> under the SMS_MP_CONTROL_MANAGER component under Site
>> Status.
>>
>> I have restarted the SMS Agent Host, W3SVC, and have
>> verified that the SMS machine account, and SMS Service
>> Account have Administrator priviledges on the server.
>>
>> The schema has been extended into Active Directory.
>>
>> I fear that these errors are the cause for why the
>> clients are not getting installed as Advanced Clients,
or
>> being assigned to the site code...
>>
>> Under MPMSI.log I get:
>>
>> MSI (s) (C0:64): Product: SMS Management Point --
>> Installation operation completed successfully.
>>
>> Under MPCONTROL.log I get lots of:
>>
>> STATMSG: ID=5436 SEV=E LEV=M SOURCE="SMS Server"
>> COMP="SMS_MP_CONTROL_MANAGER" SYS=HYMONIX SITE=MRP
>> PID=396 TID=3208 GMTDATE=Wed Jul 21 06:30:15.282 2004
>> ISTR0="Unauthorized" ISTR1="" ISTR2="" ISTR3=""
ISTR4=""
>> ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9=""
NUMATTRS=0
>> $$<SMS_MP_CONTROL_MANAGER><Wed Jul 21 08:30:15.282
2004
>> South Africa Standard Time><thread=3208 (0xC88)>
>> Http verification .sms_aut failed with status code
401,
>> Unauthorized $$<SMS_MP_CONTROL_MANAGER><Wed Jul 21
>> 08:40:15.235 2004 South Africa Standard
Time><thread=3208
>> (0xC88)>
>>
>> Under MPSETUP.log I get:
>>
>> MP.MSI could not be installed. The return code was 1618
>> Installing the MP
>> Passed OS version check.
>> IIS Service is installed.
>> Management Point already installed
>> Installation was successful
>>
>>
>> Any help would be appreciated!
>=========================================================
==============
>Hi Darren,
>
>I was also facing this issue (Http verification .sms_aut
failed with
>status code 401, Unauthorized - 5436 for the MP) on our
SMS 2003
>Primary Site.
>
>Note, this error is different from other 5436 errors
I've seen posted
>here, in that the code is "Unauthorised" as opposed
to "not found".
>
>I have just completed resolution and can suggest you
review the
>following:
>
>Can you receive a successful result for the
>"http://servernanme/sms_mp/.sms_aut?mplist" (minus
quotes) command, on
>that server? The successful result being a blank screen.
>
>If not, then you will need to ensure that access rights
for the
>following accounts are set correctly:
>
>IUSR_COMPUTERNAME
>IWAM_COMPUTERNAME
>IIS_WPG
>NETWORK SYSTEM
>LOCAL SYSTEM
>
>This information can be located in the IIS 6.0 help
files (iismmc.chm
>specifically) by entering "IUSR_computername"
and "IWAM_computername"
>(minus quotes) into the help file search function.
>
>Alternately, you can read Chapter 18 "Managing a Secure
IIS 6.0
>Solution" document from the Microsoft IIS 6.0 website,
which details
>user rights assignment necessary for IIS 6.0 to run,
NTFS file
>permissions also set when running IIS, and registry
permissions that
>are required for running IIS.
>
>Cheers, from a NOW happy SMS2003 admin!!
>
>regards,
>Sheree Smallman
>.
>

Hi Sheree

Thanks for the solution, but I am still getting the same
errors. I do get a blank screen when
accessing "http://servername/sms_mp/.sms_aut?mplist" but
the message errors are still coming in.

I have contacted our Microsoft Support Technician, and
this is what he suggested:

<I need you to check your perms on these folders:
 
<sms\ccm\incoming; sms\ccm\outgoing, sms_ccm
 
<You need to make sure the correct IUSR and IWAM accounts
<have permissions. If you could get screens of these
<perms I could compare them to mine. This should fix up
<the 5436 <errors. If not we will continue to check it
<out.
 
<You also need to check out the following article to make
<sure your IIS defaults are correct.
 
<812614 - Default Permissions and User Rights for IIS 6.0
<http://support.microsoft.com/default.aspx?scid=kb;en-
<us;812614

<297519 - Server Application Error "The server failed to
<load application"
<http://support.microsoft.com/default.aspx?scid=kb;en-
<us;297519

I have gone through each of the MS KB articles above and
applied all the suggested permissions, but still no luck.

Regards



Relevant Pages

  • Re: SMS_MP_CONTROL_MANAGER msg id 5436
    ... > verified that the SMS machine account, ... > Installation operation completed successfully. ... Can you receive a successful result for the ... This information can be located in the IIS 6.0 help files (iismmc.chm ...
    (microsoft.public.sms.admin)
  • Re: Installing MPs on Win2k3 DCs and the IIS_WPG Group
    ... Did you try posting to the IIS ... SMS 2003 Technical FAQ: ... > When installing IIS6 for the proxy MP on the DC's I have found that the ... > NTFS and registry permissions using the group it created. ...
    (microsoft.public.sms.setup)
  • Re: Q: access of local "Users" group to web content directories.
    ... The default installation of Windows 2003 server gives the "Users" group ... When IIS is installed with either volume on inetpub, ... example of permissions not being as pessamistic as they should be. ...
    (microsoft.public.inetserver.iis)
  • RE: MP Control Manager detected MP is not responding to HTTP requests
    ... If this is a standard IIS installation on Windows 2003 then ... there are some configuration changes you need to make for SMS 2003 to work. ... and Getpolicy.dll are enabled on the IIS security page. ...
    (microsoft.public.sms.setup)
  • RE: SP1 has Broken Web Reporting
    ... i would try to redo your DCOMCNFG launch and access permissions first. ... > reporting site in IIS Manager, ... > uninstalling and reinstalling the reporting point (and giving it different ... What parts of SMS would need to be reinstalled, ...
    (microsoft.public.sms.admin)

Loading