RE: MP Installation problems

Tech-Archive recommends: Fix windows errors by optimizing your registry

Hi

I've now managed to get the MP installed by removing the site server as an
MP, running the
ccmclean /mp and then reassigning the siter server as an MP. Running the
MPTroubleshooter tool
against the site it now returns success for everything except the testing
mpcert http.

I've tried a lot of the stuff suggested already on other posts like
uninstalling and reinstalling IIS,
permissions etc but still can't get it to work.

If anyone has come across this before and managed to resolve it any help
would be appreciated.

Steve



"Steve" wrote:

Hi,

We have just carried out an upgrade to SMS 2003 SP1 from SMS 2.0 SP5 and we
are having problems with the installation of the management point on the SMS
site server.

I have attached at the bottom of this post the mpsetup.log and the mpmsi.log
files. We are running SMS 2003 SP1 on a Windows 2003 server box in a AD
environment. The schema has been extended and we are not running advanced
security.

Any help on this would be appreciated.

Steve

MPSetup.log

<06-17-2006 17:36:56>
====================================================================
<06-17-2006 17:36:56> MP Setup Started....
<06-17-2006 17:36:56> Parameters: D:\SMS\bin\i386\MPsetup.exe /install
/siteserver:xxx-xxxx-xxx
<06-17-2006 17:36:56> Installing the MP
<06-17-2006 17:36:56> Passed OS version check.
<06-17-2006 17:36:56> IIS Service is installed.
<06-17-2006 17:36:56> No versions of MP are installed. Installing new MP.
<06-17-2006 17:36:56> Enabling MSI logging. MP.MSI will log to
D:\SMS\logs\MPMSI.log
<06-17-2006 17:36:56> Installing D:\SMS\bin\i386\mp.msi
CCMINSTALLDIR="D:\SMS_CCM" CCMSERVERDATAROOT="D:\SMS" USESMSPORTS=TRUE
SMSPORTS=80 CCMENABLELOGGING=TRUE CCMLOGLEVEL=1 CCMLOGMAXSIZE=1000000
CCMLOGMAXHISTORY=1
<06-17-2006 17:37:04> Unknown error code: 455929
<06-17-2006 17:37:04> [17:37:04] @@ERR:25001
<06-17-2006 17:37:04> Setup failed due to unexpected circumstances
The error code is 80004005
<06-17-2006 17:37:05> MP.MSI exited with return code: 1603
<06-17-2006 17:37:05> Backing up MPMSI.log to D:\SMS\logs\MPMSI.log.LastError
<06-17-2006 17:37:05> Fatal MSI Error - MP.MSI could not be installed.

============================================================================================================================

MPMSI.log

=== Verbose logging started: 17/06/2006 17:36:56 Build type: SHIP UNICODE
2.00.3790.00 Calling process: D:\SMS\bin\i386\MPsetup.exe ===
MSI (c) (24:8C): Resetting cached policy values
MSI (c) (24:8C): Machine policy value 'Debug' is 0
MSI (c) (24:8C): ******* RunEngine:
******* Product: D:\SMS\bin\i386\mp.msi
******* Action:
******* CommandLine: **********
MSI (c) (24:8C): Client-side and UI is none or basic: Running entire install
on the server.
MSI (c) (24:8C): Grabbed execution mutex.
MSI (c) (24:8C): Cloaking enabled.
MSI (c) (24:8C): Attempting to enable all disabled priveleges before calling
Install on Server
MSI (c) (24:8C): Incrementing counter to disable shutdown. Counter after
increment: 0
MSI (s) (64:6C): Grabbed execution mutex.
MSI (s) (64:54): Resetting cached policy values
MSI (s) (64:54): Machine policy value 'Debug' is 0
MSI (s) (64:54): ******* RunEngine:
******* Product: D:\SMS\bin\i386\mp.msi
******* Action:

=== Logging started: 17/06/2006 17:36:57 ===
MSI (s) (64:54): Machine policy value 'DisableRollback' is 0
MSI (s) (64:54): User policy value 'DisableRollback' is 0
MSI (s) (64:54): Doing action: INSTALL
Action start 17:36:57: INSTALL.
MSI (s) (64:54): Running ExecuteSequence
MSI (s) (64:54): Doing action: SystemFolder
Action start 17:36:57: SystemFolder.
Action ended 17:36:57: SystemFolder. Return value 1.
MSI (s) (64:54): Doing action:
WindowsFolder.3643236F_FC70_11D3_A536_0090278A1BB8
Action start 17:36:57: WindowsFolder.3643236F_FC70_11D3_A536_0090278A1BB8.
Action ended 17:36:57: WindowsFolder.3643236F_FC70_11D3_A536_0090278A1BB8.
Return value 1.
MSI (s) (64:54): Doing action:
SystemFolder.3643236F_FC70_11D3_A536_0090278A1BB8
Action start 17:36:57: SystemFolder.3643236F_FC70_11D3_A536_0090278A1BB8.
Action ended 17:36:57: SystemFolder.3643236F_FC70_11D3_A536_0090278A1BB8.
Return value 1.
MSI (s) (64:54): Doing action:
SystemFolder.12C909B6_5F69_4C4D_8EC3_C225C1607933
Action start 17:36:57: SystemFolder.12C909B6_5F69_4C4D_8EC3_C225C1607933.
Action ended 17:36:57: SystemFolder.12C909B6_5F69_4C4D_8EC3_C225C1607933.
Return value 1.
MSI (s) (64:54): Skipping action: CcmAutoDetect (condition is false)
MSI (s) (64:54): Doing action: LaunchConditions
Action start 17:36:57: LaunchConditions.
Action ended 17:36:57: LaunchConditions. Return value 1.
MSI (s) (64:54): Skipping action: CcmSwitchToRepairMode (condition is false)
MSI (s) (64:54): Doing action: AppSearch

Action start 17:37:04: CcmRegisterWmiMofFilesInit.
MSI (s) (64:54): Creating MSIHANDLE (488) of type 790542 for thread 1364
MSI (s) (64:50): Invoking remote custom action. DLL:
C:\WINDOWS\Installer\MSI27F.tmp, Entrypoint: CcmRegisterWmiMofFilesInit
MSI (s) (64!74): Creating MSIHANDLE (489) of type 790541 for thread 2676
MSI (s) (64!74): Creating MSIHANDLE (490) of type 790531 for thread 2676
MSI (s) (64!74): Closing MSIHANDLE (490) of type 790531 for thread 2676
MSI (s) (64!74): Creating MSIHANDLE (491) of type 790531 for thread 2676
MSI (s) (64!74): Note: 1: 2753 2:
PolicyAgentProvider_dll.A6940213_CD40_4753_8BA2_E803376DECC3
MSI (s) (64!74): Closing MSIHANDLE (491) of type 790531 for thread 2676
MSI (s) (64!74): Creating MSIHANDLE (492) of type 790531 for thread 2676
[17:37:04] ERROR: Failed to resolve path to PolicyAgentProvider.dll
MSI (s) (64!74): Closing MSIHANDLE (492) of type 790531 for thread 2676
MSI (s) (64!74): Creating MSIHANDLE (493) of type 790531 for thread 2676
MSI (s) (64!74): Creating MSIHANDLE (494) of type 790531 for thread 2676
[17:37:04] @@ERR:25001
MSI (s) (64!74): Closing MSIHANDLE (494) of type 790531 for thread 2676
Error 25001. Setup failed due to unexpected circumstances
The error code is 80004005
MSI (s) (64!74): Product: SMS Management Point -- Error 25001. Setup failed
due to unexpected circumstances
The error code is 80004005

MSI (s) (64!74): Closing MSIHANDLE (493) of type 790531 for thread 2676
MSI (s) (64!74): Closing MSIHANDLE (489) of type 790541 for thread 2676
MSI (s) (64:50): Closing MSIHANDLE (488) of type 790542 for thread 1364
Action ended 17:37:04: CcmRegisterWmiMofFilesInit. Return value 3.
MSI (s) (64:54): Machine policy value 'DisableRollback' is 0
MSI (s) (64:54): Note: 1: 1402 2:
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (s) (64:54): Note: 1: 1402 2:
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (s) (64:54): No System Restore sequence number for this installation.
MSI (s) (64:54): Unlocking Server
Action ended 17:37:04: INSTALL. Return value 3.
Property(S): UpgradeCode = {ABD0F60F-1622-4311-8989-106B60D784FF}
Property(S): SourceDir = D:\SMS\bin\i386\
Property(S): TARGETDIR = D:\SMS_CCM\
Property(S): ALLUSERS = 1
Property(S): ErrorDialog = ErrorDialog
Property(S): ProductName = SMS Management Point
Property(S): ProductCode = {A61F02C7-CE80-4941-8E5D-900804DAF6DE}
Property(S): PackageCode = {9DBE3E38-EEB2-4A3A-A013-4C195634AC37}
Property(S): Manufacturer = Microsoft Corporation
Property(S): ProductVersion = 2.50.3174.1015
Property(S): ProductLanguage = 1033
Property(S): SystemFolder = C:\WINDOWS\system32\
Property(S): Redist.51D569E3_8A28_11D2_B962_006097C4DE24 =
C:\WINDOWS\system32\
Property(S): MS.51D569E3_8A28_11D2_B962_006097C4DE24 = C:\WINDOWS\system32\
Property(S): System.51D569E3_8A28_11D2_B962_006097C4DE24 =
C:\WINDOWS\system32\
Property(S): wbem.3643236F_FC70_11D3_A536_0090278A1BB8 =
C:\WINDOWS\system32\WBEM\
Property(S): WindowsFolder.3643236F_FC70_11D3_A536_0090278A1BB8 = C:\WINDOWS\
Property(S): SystemFolder.3643236F_FC70_11D3_A536_0090278A1BB8 =
C:\WINDOWS\system32\
Property(S): Q321856_W2K_ActionText = Updating Operating System
Property(S): Q321856_W2K_ActionData = Q321856
Property(S): Q321856_WXP_ActionText = Updating Operating System
Property(S): Q321856_WXP_ActionData = Q321856
Property(S): Q322850_WXP_ActionText = Updating Operating System
Property(S): Q322850_WXP_ActionData = Q322850
Property(S): CcmCreateWmiNamespaces =
CCM,Framework_Wmi.A6940213_CD40_4753_8BA2_E803376DECC3
CCM\Policy,Framework_Wmi.A6940213_CD40_4753_8BA2_E803376DECC3
Property(S): CcmCreateWmiNamespacesRollback =
CCM,Framework_Wmi.A6940213_CD40_4753_8BA2_E803376DECC3
CCM\Policy,Framework_Wmi.A6940213_CD40_4753_8BA2_E803376DECC3
Property(S): CcmRemoveIISVirtualDirectories = SMS Management Point
TRUE
80
SMS_MP,,D:\SMS_CCM\SMS_MP,N
BEGIN PROPERTY
AccessExecute
boolean
true
AccessRead
boolean
false
AppIsolated
long
1
AppPoolId
string
SMS Management Point Pool
AuthAnonymous
boolean
t
rue
ContentIndexed
boolean
false
EnableDefaultDoc
boolean
false
EnableDirBrowsing
boolean
false
AuthNTLM
boolean
false
END PROPERTY
BEGIN SCRIPTMAP
sms_pol

0
GET,HEAD
SMS_MP
sms_aut

0
GET,HEAD
SMS_MP
ccr

0
SMS_POST
SMS_MP
stat

0
SMS_POST
SMS_MP
END SC
RIPTMAP

CCM_Outgoing,,D:\SMS\CCM\Outgoing,N
BEGIN PROPERTY
AccessExecute
boolean
false
AccessRead
boolean
true
AppIsolated
long
1
AppPoolId
string
CCM Server Framework Pool
AuthAnonymous
boolean
true
ContentIndexed
boolean
false
EnableDefaultDoc
boolean

false
EnableDirBrowsing
boolean
false
END PROPERTY
BEGIN SCRIPTMAP
END SCRIPTMAP

CCM_Incoming,,D:\SMS\CCM\Incoming,Y
BEGIN PROPERTY
AccessExecute
boolean
false
AccessRead
boolean
false
AppIsolated
long
1
AppPoolId
string
CCM Server Framework Pool
AuthAno
nymous
boolean
true
ContentIndexed
boolean
false
EnableDefaultDoc
boolean
false
EnableDirBrowsing
boolean
false
END PROPERTY
BEGIN SCRIPTMAP
END SCRIPTMAP


Property(S): CcmRemoveIISApplicationPools = CCM Server Framework Pool
BEGIN PROPERTY
WamUserName
string
IWAM
LogonMethod
long
1
AppPoolIdentityType
long
3
END PROPERTY
.

Relevant Pages

  • MP Installation problems
    ... are having problems with the installation of the management point on the SMS ... MSI: Grabbed execution mutex. ... MSI: Doing action: INSTALL ...
    (microsoft.public.sms.setup)
  • Re: Upgrading SPS 2003 to MOSS 2007 problem
    ... We had an SPS 2003 server that we moved to new ... I'm logged in and running the install as our sharepointadmin domain ... useFailoverPartner, Boolean& failoverDemandDone, String host, String ... owningObject, SqlConnectionString connectionOptions, String ...
    (microsoft.public.sharepoint.windowsservices)
  • Installation operation failed: event ID 11708
    ... Microsoft SQL Server Desktop Engine -- Installation operation failed. ... when i try to install the msde by using SqlSetup.exe and use the verbose logging flags ... MSI: Executing op: ... MSI: Invoking remote custom action. ...
    (microsoft.public.sqlserver.msde)
  • Re: New Windows 2003 Cluster - MSI īs are not applied
    ... The assignment of application Previous Versions Client from policy ... The install of application Previous Versions Client from policy ... I have taken a brand new msi, which was not install in the past on this ... moved on the new file server, no more MSI are not applied. ...
    (microsoft.public.windows.group_policy)
  • SBS installation errors
    ... "An error occurred while copying files for the Server ... "MSI: Target path resolution complete. ... G:\Program Files\Microsoft Windows Small Business ... Action ended 15:58:51: INSTALL. ...
    (microsoft.public.windows.server.sbs)