locked
MP install error 1603 with error of MP higher version already installed. RRS feed

  • Question

  •  

    Had to do site reset.  After site reset, MP stopped working. MPControl.log shows that the SMS_MP_CONTROL_MANAGER was deinstalled during the site reset. Then the reset looks like it tried to reinstall the MP because a  day later I saw that the MPControl.log stopped having logged info the time of the reset and the mpMSI.log had a current day and time when I looked at log files.  The MP still showed as being an installed site component in the Admin Console.

     

    I thought maybe the issue was the admin console showed the MP as being installed could be the issue.  I deleted the MP role. Actually rebooted the SCCM server then – just so the MP would stop trying to reinstall and then in the SCCM Admin console I added the MP role to the SCCM server.  The SCCM tried to install the MP with the following command line as stated in the MPSetup.log –

    Installing C:\Program Files (x86)\Microsoft Configuration Manager\bin\i386\mp.msi CCMINSTALLDIR="C:\Program Files (x86)\SMS_CCM" CCMSERVERDATAROOT="C:\Program Files (x86)\Microsoft Configuration Manager" USESMSPORTS=TRUE SMSPORTS=80 USESMSSSLPORTS=TRUE SMSSSLPORTS=443 USESMSSSL=TRUE SMSSSLSTATE=0 CCMENABLELOGGING=TRUE CCMLOGLEVEL=1 CCMLOGMAXSIZE=1000000 CCMLOGMAXHISTORY=1

     

    The MP install gives a 1603 error

    <03-23-2008 20:35:31> mp.msi exited with return code: 1603

    <03-23-2008 20:35:31> Backing up C:\Program Files (x86)\Microsoft Configuration Manager\logs\mpMSI.log to C:\Program Files (x86)\Microsoft Configuration Manager\logs\mpMSI.log.LastError

    <03-23-2008 20:35:31> mp.msi exited with return code: 1603

     

    Basically the install thinks there is a newer version MP installed. I rolled back off man hotfix just incase it change the SCCM version and checked the registry for the version and it is correct.

     

    If I run the commandline above from command prompt, I get message box that states-

    "Windows installer could not be accessed. This could happen if Widows is running in safe mode or Windows Installer is not correctly installed." 

     

    The latest version of windows installer but it is already installed and I can install other apps with windows installer with no issues. I tried cliclean with additional steps of cleaning registry.  Still mp install always gives the same error.

     

    I’ve search several SCCM/SMS newsgrops and could not find any related issue other than a 1603 error for MP virtual directory being created or BITS not installed.  That’s not the case here.

     

    So my questions to you are

    ·         Have you heard/seen this issue before and know how to resolve.

    ·         I want you to confirm my assumption that I can just save the current db; deleted SCCM and reinstall; attach saved DB and install MP hoping that is would not be an issue any longer.   The clients should be able to remain on the desktops and find the site after it is reinstalled, right?

    Tuesday, March 25, 2008 6:05 PM

Answers

  • The Admin UI doesn't show current states of the site roles, only that the role is assigned to that server.

     

    As Torsten explained, look for the entry Return Value 3 in the MPMSI.log file.  Just above that line you'll see what the actual error code is that is causing the failure.

     

    Your assumption of being able to save the db, delete the site, then reinstall and reattach to the db is incorrect.  Follow the information here: http://technet.microsoft.com/en-us/library/bb680456.aspx

     

     If after following the Backup & Restore process you still run into a problem, please let us know.

    Wednesday, April 9, 2008 8:07 PM

All replies

  • Examine mpmsi.log for details. Search for "return value 3". The cause of the problem should be logged just above this line.

    And your assumption is wrong. It's not sufficient to just back up the database. You also need some registry keys and files. The "Backup ConfigMgr Site Server" takes care of all this for you.  

     

    Wednesday, March 26, 2008 7:37 AM
  • Hi,

     

    You only need to have the registry and files for a complete site restore. A database backup can be effective if you have a database corruption.

     

    Regarding the MP problem, you can also run the mp.msi by hand to see any error information during the installation process.

     

    Regards,

     

    Jannes Alink

    Avanade /systems.solutions.success/from Accenture & Microsoft

     

    Wednesday, April 2, 2008 8:33 PM
  • The Admin UI doesn't show current states of the site roles, only that the role is assigned to that server.

     

    As Torsten explained, look for the entry Return Value 3 in the MPMSI.log file.  Just above that line you'll see what the actual error code is that is causing the failure.

     

    Your assumption of being able to save the db, delete the site, then reinstall and reattach to the db is incorrect.  Follow the information here: http://technet.microsoft.com/en-us/library/bb680456.aspx

     

     If after following the Backup & Restore process you still run into a problem, please let us know.

    Wednesday, April 9, 2008 8:07 PM