locked
Error re-installing MS-DPM-2010 using its own instance of SQL-Server-2008 RRS feed

  • Question

  • On our backup server running windows 2008 server r2 and sql-server-2008-r2. This instance of sql-server 2008 among other things houses config data and databases for HP Data Protector Notebook Extension.

    As a test we installed MS-DP-2010 on the same machine and started to run backups with ten laptops as to getting the feel for this backup solution. As we were not completly happy with this first test-setup od DPM-2010 - we un-installed the the DPM-2010-server - we scrapped and removed all the DPM-created volumes to recover all the un-allocated space. On the RAID-5 volume we use for data backup.

    However re-installing DPM-2010 fails with the following error ID: 4310 - and the following error messages:

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

    From the --> summary.log file:  Log with failure:              C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120308_125412\sql_rs_Cpu64_1.log

    From the --> sql_rs_Cpu64_1.log:  MSI (s) (20:6C) [15:35:51:439]: Specified instance {2453DBC8-ACC4-4711-BD03-0C15353AA3D8} via transform :InstID01.mst;:InstName01.mst is already installed. MSINEWINSTANCE requires a new instance that is not installed.
    MSI (s) (20:6C) [15:35:51:439]: MainEngineThread is returning 1639

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

    How can I get around the fact there is an already existing instance  -->  :InstID01.mst;:InstName01.mst   --> thats stopping us from completing the re-install.

    I would not like to mess with the existing Sql-Server 2008 install/instance since this one houses the major backup info for our laptop

    Cheers:  Max!

    Thursday, March 8, 2012 8:09 PM

Answers

  •  

    Hello,

    Please run the following command and then try to run DPM setup again:

    msiexec /I {2453DBC8-ACC4-4711-BD03-0C15353AA3D8} REMOVE=ALL

    Hope this helps.

    Regards,

    Alberto Morillo
    SQLCoffee.com

    • Proposed as answer by Iric Wen Monday, March 19, 2012 8:51 AM
    • Marked as answer by Iric Wen Thursday, March 22, 2012 8:12 AM
    Friday, March 9, 2012 1:44 AM
  •  

    Hello Max,

    This will remove the orphan MSI. Nothing else.

    Hope this helps.

    Regards,

    Alberto Morillo
    SQLCoffee.com

    • Proposed as answer by Iric Wen Monday, March 19, 2012 8:51 AM
    • Marked as answer by Iric Wen Thursday, March 22, 2012 8:12 AM
    Saturday, March 10, 2012 3:15 AM

All replies

  •  

    Hello,

    Please run the following command and then try to run DPM setup again:

    msiexec /I {2453DBC8-ACC4-4711-BD03-0C15353AA3D8} REMOVE=ALL

    Hope this helps.

    Regards,

    Alberto Morillo
    SQLCoffee.com

    • Proposed as answer by Iric Wen Monday, March 19, 2012 8:51 AM
    • Marked as answer by Iric Wen Thursday, March 22, 2012 8:12 AM
    Friday, March 9, 2012 1:44 AM
  • Max here!

    Thanks for the tip - but what exactly does this above command do?

    Could you please provide a bit more details please

    Whats your rationale behind suggesting I run the command?

    Sorry to sound overly cautious - but I feel loathe to risk destroting anything more than I already have - lols.

    Cheers;  Max!

    Friday, March 9, 2012 8:42 PM
  •  

    Hello Max,

    This will remove the orphan MSI. Nothing else.

    Hope this helps.

    Regards,

    Alberto Morillo
    SQLCoffee.com

    • Proposed as answer by Iric Wen Monday, March 19, 2012 8:51 AM
    • Marked as answer by Iric Wen Thursday, March 22, 2012 8:12 AM
    Saturday, March 10, 2012 3:15 AM