Mp Msi Error 1603
Contents |
(עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) Home2012Previous VersionsLibraryForumsGallery Ask a question Quick access Forums home Browse fatal msi error - mp.msi could not be installed forums users FAQ Search related threads Remove From portlweb msi exited with return code 1603 My Forums Answered by: MP.Msi exited with return code 1603 System Center
Mpmsu
Configuration Manager > Configuration Manager 2007 General Question 0 Sign in to vote Hi Team, I am trying to
Pmsi
install the MP site system role but i get an erron in log (MPSetup) <03-12-2010 13:09:02> ======== Installing Pre Reqs for Role SMSMP ========<03-12-2010 13:09:02> Found 1 Pre Reqs for Role SMSMP <03-12-2010 13:09:02> Pre Req MSXML60 found.<03-12-2010 13:09:02> MSXML60 already installed (Product Code: {0A869A65-8C94-4F7C-A5C7-972D3C8CED9E}). Would not install again.<03-12-2010 13:09:02> Pre Req MSXML60 is already installed. Skipping it.<03-12-2010 13:09:02> ======== Completed Installion of Pre Reqs for Role SMSMP ========<03-12-2010 13:09:02> Installing the SMSMP<03-12-2010 13:09:02> Passed OS version check.<03-12-2010 13:09:02> IIS Service is installed.<03-12-2010 13:09:02> No versions of SMSMP are installed. Installing new SMSMP.<03-12-2010 13:09:02> Enabling MSI logging. mp.msi will log to C:\Program Files\Microsoft Configuration Manager\logs\mpMSI.log<03-12-2010 13:09:02> Installing C:\Program Files\Microsoft Configuration Manager\bin\i386\mp.msi CCMINSTALLDIR="C:\Program Files\SMS_CCM" CCMSERVERDATAROOT="C:\Program Files\Microsoft Configuration Manager" USESMSPORTS=TRUE SMSPORTS=80 USESMSSSLPORTS=TRUE SMSSSLPORTS=443 USESMSSSL=TRUE SMSSSLSTATE=63 CCMENABLELOGGING=TRUE CCMLOGLEVEL=1 CCMLOGMAXSIZE=1000000 CCMLOGMAXHISTORY=1<03-12-2010 13:09:19> mp.msi exited with return code: 1603<03-12-2010 13:09:19> Backing up C:\Program Files\Microsoft Configuration Manager\logs\mpMSI.log to C:\Program Files\Microsoft Configuration Manager\logs\mpMSI.log.LastError<03-12-2010 13:09:19> Fatal MSI Error - mp.msi could not be installed
on the new ConfgMgr 2012 server. During the prerequisite check an error was seen that the management point couldn't been installed: Client version on management point computer. After removing the ConfigMgr 2007 agent, the error message was gone, and installation went fine (I thought). Bad part is, still no management point was installed after setup. The following lines were seen in mpsetup.log: -mp.msi exited with return code: 1603 -Backing up C:\Program Files\Microsoft Configuration Manager\logs\mpMSI.log to C:\Program Files\Microsoft Configuration Manager\logs\mpMSI.log.LastError https://social.technet.microsoft.com/Forums/systemcenter/en-US/13eb57b6-15df-49a1-b52d-789ebf9d15fb/mpmsi-exited-with-return-code-1603?forum=configmgrgeneral -Fatal MSI Error - mp.msi could not be installed. I did a manual installation with the comment mention in the logfile: mp.msi CCMINSTALLDIR="C:\Program Files\SMS_CCM" CCMSERVERDATAROOT="P:\Program Files\Microsoft Configuration Manager" USESMSPORTS=TRUE SMSPORTS=80 USESMSSSLPORTS=TRUE SMSSSLPORTS=443 USESMSSSL=TRUE SMSSSLSTATE=0 CCMENABLELOGGING=TRUE CCMLOGLEVEL=1 CCMLOGMAXSIZE=1000000 CCMLOGMAXHISTORY=1 but this failed to compile on "CcmExec_Global.mof". After running ccmclean.exe (SMS 2003 toolkit) a WMI repair was done. After that (manual) http://henkhoogendoorn.blogspot.com/2015/07/fatal-msi-error-management-point-could.html installation went fine again! The following lines were seen in mpsetup.log now: -SMSMP already installed. Upgrading/Reinstalling SMSMP-New SMSMP is the same product code. This is a minor upgrade. -mp.msi exited with return code: 0-Installation was succesful. Happy with this easy solution! :-) Overview: Technical Reference for the Prerequisite Checker in Configuration Manager Posted by Henk Hoogendoorn at 12:59 PM Email ThisBlogThis!Share to TwitterShare to FacebookShare to Pinterest Labels: 1603, Client version on management point computer, Fatal MSI Error, mp.msi, mp.msi could not be installed, mp.msi exited with return code: 1603 2 comments: Fernanda ReisDecember 7, 2015 at 8:28 PMI ran ccmclean.exe and so, after that, ran manually (as administrator) the mp.msi (the entire command that appears on mpsetup.log) - however, at the end of installation, I get this error: "Setup was unable to create the Internal virtual directory CCM_Incoming - The error code is 800CC801" - I wonder if you could help me on it. ReplyDeleteRepliesHenk HoogendoornDecember 8, 2015 at 10:36 PMAs of right now, the easiest way to resolve this issue is to r
SoftwareAsset | Installed Software with Labels and Last UsageAsset | Intune DevicesAsset | Windows 10Configuration Manager | ApplicationsConfiguration Manager | CollectionsConfiguration Manager | Software UpdatesDashboard | DeviceDeployment | ApplicationsDeployment | PackagesDeployment | Software UpdatesSystem Health https://www.systemcenterdudes.com/sccm-2012-management-point-error-1603/ | Configuration Manager ClientSystem Health | Distribution PointsSystem Health | Software UpdatesBundlesAsset http://robotarchive.blogspot.com/2015/01/sccm-2012-r2-install-of-management.html | ReportsConfiguration Manager | ReportsDeployment | ReportsSoftware Updates | ReportsSystem Health | ReportsAll GuidesAll ReportsSCD CompleteTechNetDelete all collections older than x days for a specific folder in SCCMMultilingual User Interface Pack kit for hardware inventory in SCCM 2012Set of Operational SCCM CollectionsConsultingTeamAccountCheckoutPurchase HistoryTerms & Conditions msi error SeriesAsset IntelligenceMobile Device Management with IntuneSCCM 2012 R2SCCM Current BranchGuidesDistribution Point InstallationInternet Based Client ManagementMobile Device ManagementSCCM InstallationReportsAsset | HardwareAsset | Installed SoftwareAsset | Installed Software with Labels and Last UsageAsset | Intune DevicesAsset | Windows 10Configuration Manager | ApplicationsConfiguration Manager | CollectionsConfiguration Manager | Software UpdatesDashboard | DeviceDeployment | ApplicationsDeployment | PackagesDeployment | Software UpdatesSystem mp msi error Health | Configuration Manager ClientSystem Health | Distribution PointsSystem Health | Software UpdatesBundlesAsset | ReportsConfiguration Manager | ReportsDeployment | ReportsSoftware Updates | ReportsSystem Health | ReportsAll GuidesAll ReportsSCD CompleteTechNetDelete all collections older than x days for a specific folder in SCCMMultilingual User Interface Pack kit for hardware inventory in SCCM 2012Set of Operational SCCM CollectionsConsultingTeamAccountCheckoutPurchase HistoryTerms & Conditions PowershellSCCM 2012 Management Point Error 1603Benoit Lecours11th February 2014 1We have recently experienced a SCCM 2012 management point error 1603.Scenario :Installing a new MP gives an error 1603SCCM 2012 R2Windows 2012 R2The first thing to check is the MPSetup.log, you can see the error 1603 but you have not much information about what's the problem really is. You have to dig deeper in the MPMsiLog.LastError to see the root cause.As you can see the error is cause by a previous version of the client being installed on the server. My environment had SCCM 2007 configured with the client push so my 2007 client was installed.I've removed the client using ccmsetup
You open up the SCCM Console and go to Monitoring > System Status > Site Status you see a red alert symbol next to the Management Point. To further confirm the failed install check you open up (%installdirectory%/Microsoft Configuration Manager/Logs/MPSetup.Log) and encounter a number of error messages including, "Fatal MSI Error - mp.msi could not be installed" You may also encounter "mp.msi exited with return code 1603" in the MP.msi.log You may also open up IIS. You may then notice that it's missing the vast majority of theusualsccmentries under Default Web Site: Cause: When the server was built the old SCCM 2007 installed a client onto the server. Even if you already uninstalled the client, there's a good chance that some of the components of the client are still hanging around in the wmi repository. This will interfere with the MP installation to the extent that it will fail. Solution: Option A Remove the MP from SCCM 2012. Uninstall the 2007 SCCM client by opening an elevated command prompt, navigating to the C:\windows\ccmsetup folder and then entering ccmsetup.exe /uninstall. Reinstall the MP on SCCM 2012. Option B Time to fully clear down the wmi repository of any traces of the old sccm client. Remove the MP from SCCM 2012. Open up Powershell in an elevated command prompt and enter the following command: Get-WMIObject -namespace "root" -query "SELECT * FROM __Namespace where name = 'ccm'" | remove-wmiobject Once this has finished running, reinstall the MP on SCCM 2012. Keep an eye on the install process by opening the MPmsi.log and MPsetup.log. It should run with only a few IGNORE errors. When it has finished, open up IIS and confirm that all the rest of the SCCM entries haveappeared: Option C The nuclear option. Rebuild the sccm server and make damn sure the SCCM client from the old 2007 environement doesn't get installed. This may mean disabling client push in 2007, disabling the install of client install in the build task sequence, building the client in a block GPO OU - whatever you need to do just make sure it never has the 2007 client installed! Posted by Robot at 03:43 Email ThisBlogThis!Share to TwitterShare to FacebookShare to Pinterest 1 comment: dagtiqueg9 April 2015 at 10:09Faced this exact issue, spent days trying to resolve - fully clearing all traces of ccm from the wmi repository via powershell (option B) finally did the trick for me - THANK YOU :)ReplyDeleteAdd commentLoad more... Newer Post Older Post Home Subscribe to: