Re: SMS 2003 SP1 MP Error 5436 Hell
- From: "toby@xxxxxxxxxxxxxxxx" <toby@xxxxxxxxxxxxxxxx>
- Date: 21 Jan 2006 15:12:10 -0800
Thank you, thank you, thank you for posting this!
It was _exactly_ what I needed. Too bad I didn't find it an hour and a
half earlier, but I would probably have struggled for another hour and
a half before calling Microsoft, and then spent at least half an hour
getting to a technician, etc., etc., so you've probably saved me at
least three hours of pain!
To ensure that others can find it using the same searches I tried
initially, here are the error messages that you may see as
symptomology):
[13:56:23] @@ERR:25006
Setup was unable to create the Internet virtual directory CCM_System
The error code is 80020009
MP.MSI exited with return code: 1603
If you see these, definitely give Jake's solution a try!
--Toby Ovod-Everett
Jake wrote:
> Hello -
>
> I had this error and spent 2 days with MS support. What resolved this for
> me was actually an IIS fix. I uninstalled the MP and during reinstallation,
> I was getting errors and the installation failed with a specific error code
> 80020009 listed in the MPSETUP.LOG on the site server. We tried several
> things to correct the 5436 error, including removing the MP, removing IIS,
> reinstalling IIS, and reinstalling the MP several times. As I said above,
> after doing this a few times, I could not reinstall the MP due to the
> 80020009 error. MS recommended doing the steps below and this fixed the
> issue of 5436 and 80020009.
>
> According to MS, 5436 usually is indicative of Sql permissions errors. From
> the site server ensure that there is connectivity back to the sql server. I
> did get some scripts from MS that tested this connectivity and it worked
> fine. Run the pre/post MP troubleshooter from the site server having issues
> and make sure you note any errors there. I was consistently getting failures
> on the MPList portion, with an internal server error 500. This is what led
> the MS tech to the IIS metabase file.
>
> From MS Support:
>
> On the Site Server having the MP issues:
>
> 1. Ensure that ASP is ALLOWED by clicking on the Web Service Extensions and
> looking in the right hand pane.
>
> 2. Back up system32\inetsrv\metabase.xml
>
> 3. In the IIS admin console, configure IIS to allow direct editing of the
> metabase
> - Select the server and "Enable Direct Metabase Edit"
>
> 4. Open system32\inetsrv\metabase.xml in for example notepad, locate the
> WebSvcExtRestrictionList section and move "0,*.exe" and "0,*.dll" to the top
> of the
> list. Example:
>
> WebSvcExtRestrictionList="0,*.dll
> 0,*.exe
> 0,C:\WINDOWS\system32\inetsrv\httpodbc.dll,0,HTTPODBC,Internet Data
> Connector
> 0,C:\WINDOWS\system32\inetsrv\ssinc.dll,0,SSINC,Server Side Includes
> 0,C:\WINDOWS\system32\inetsrv\asp.dll,0,ASP,Active Server Pages
> 1,C:\WINDOWS\system32\bitssrv.dll,0,BITSEXTS,BITS Server Extensions
> 1,C:\WINDOWS\system32\inetsrv\httpext.dll,0,WEBDAV,WebDAV
> 1,d:\sms_ccm\ccmisapi.dll,0,CCM_ServerFramework,CCM_ServerFramework"
>
> 4. Retry the MP installation.
>
> When SMS adds file extensions to the metabase, it calls AddExtensionFile for
> each
> file it needs to add. Typically, this function should add the entry at the
> bottom
> of the exiting list in WebSvcExtRestrictionList. However, it appears that
> sometimes
> the order of the entries is "shuffled" around for yet an unknown reason.
> When this
> happen, you run into this problem.
>
>
>
>
> "Byron" wrote:
>
> > For the life of me, I can't seem to understand why my newly SMS 2003 SP1 site
> > server which is installed on Windows 2003 SP1 continues to generate Error
> > 5436. I have troubleshot this issue using Microsoft Technet documents,
> > myitforum.com articles, and combed blogs/threads related to this issue for
> > guidance. What's really weird is that I was experiencing problems testing
> > the MP through the browser by going to the following:
> >
> > http://MP_name>/sms_mp/.sms_aut?mplist
> > http://MP_name>/sms_mp/.sms_aut?mpcert
> >
> > After enabling the Allow clients to transfer data to this virtual directory
> > under the Default Web Site, BITS Server Extension tab. I was able to
> > successfully access both links without a problem. Then I ran the MP
> > Troubleshooter (Post Installation check) in the SMS 2003 Toolkit 2. I am
> > still receiving 2 failures that my site server is unable to access the above
> > links. Why am I still receiving failures and error 5436 messages?
.
- References:
- RE: SMS 2003 SP1 MP Error 5436 Hell
- From: Jake
- RE: SMS 2003 SP1 MP Error 5436 Hell
- Prev by Date: RE: SMS Reporting Point - Page Cannot Be Found
- Next by Date: Re: enabled client push installation not working
- Previous by thread: RE: SMS 2003 SP1 MP Error 5436 Hell
- Next by thread: Re: Primary Site Install Problem
- Index(es):
Relevant Pages
|
