none
SCM 3.0 Installation Database Failure RRS feed

  • Question

  • First post so hello everyone.

    Now to business. I'm having a fatal installation issue trying to install SCM 3.0 onto a Windows 7 64 bit PC.

    As this PC had VS2010 and some SQL database items I first tried the "Use existing instance" option. This failed ultimately with a 1603 error. Then I tried the "Create a new instance". This took a slightly longer but ulimately failed in the same way.

    Today I've downloaded SQL Express 2012 and installed that. So I now have a Server named MSQLSERVER1 and I can pick this in SCM's installer and use the "Use existing instance" option (Safe in the knowledge that nothing else is using this DB.)

    This time the installer runs for much longer and the progress bar gets all the way accross once and nearly all the way accross again. Hoiwever in the end it still dies with 1603.

    I've tracked down the log file and the salient bit is I guess ...

    SearchRegKeyForSqlServer: STARTED.
    SearchRegKeyForSqlServer: Got instance's name. MSSQLSERVER1
    GetSqlInstanceRegNodeName: Loop opening registry key that contains the SQL instance registry IDs.
    GetSqlInstanceRegNodeName: Opening registry key. SOFTWARE\Microsoft\Microsoft SQL Server\Instance Names\SQL
    GetSqlInstanceRegNodeName: First registry key open failed; trying non-redirected key. Error Code: 0x80070002.
    GetSqlInstanceRegNodeName: Opening registry key. SOFTWARE\Microsoft\Microsoft SQL Server\Instance Names\SQL
    GetSqlInstanceRegNodeName: Success opening registry key; reading node ID registry value. MSSQLSERVER1
    GetSqlInstanceRegNodeName: Successfully read instance's registry node ID. MSSQL11.MSSQLSERVER1
    SearchRegKeyForSqlServer: Successfully determined instance is installed.
    ExecuteSqlScripts: Custom Action Data. DBMASTER    localhost\MSSQLSERVER1    master    1    C:\Program Files (x86)\Microsoft Security Compliance Manager\    C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER1\MSSQL\Data    C:\Users\Public\Microsoft\Security Compliance Manager    Custom    MasterScript    C:\Program Files (x86)\Microsoft Security Compliance Manager\Xtrans.sql
    ConnectDatabase: server Name before checking for Default Inatance . localhost\MSSQLSERVER1
    ConnectDatabase: server Name . localhost1
    ConnectDatabase: database Name . master
    ConnectDatabase: Failed to initialize database connection. Error Code: 0x80004005. . Additional Error Description : SQL Server does not exist or access denied.
    CheckDatabaseExists: ConnectDatabase returned error. Error Code: 0x80004005.
    ExecuteSqlScripts: Failed to locate database. Error Code: 0x80004005. master
    CustomAction _ExecuteSqlScripts returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
    Action ended 10:15:33: InstallFinalize. Return value 3.
    SearchRegKeyForSqlServer: STARTED.
    SearchRegKeyForSqlServer: Got instance's name. MSSQLSERVER1
    GetSqlInstanceRegNodeName: Loop opening registry key that contains the SQL instance registry IDs.
    GetSqlInstanceRegNodeName: Opening registry key. SOFTWARE\Microsoft\Microsoft SQL Server\Instance Names\SQL
    GetSqlInstanceRegNodeName: First registry key open failed; trying non-redirected key. Error Code: 0x80070002.
    GetSqlInstanceRegNodeName: Opening registry key. SOFTWARE\Microsoft\Microsoft SQL Server\Instance Names\SQL
    GetSqlInstanceRegNodeName: Success opening registry key; reading node ID registry value. MSSQLSERVER1
    GetSqlInstanceRegNodeName: Successfully read instance's registry node ID. MSSQL11.MSSQLSERVER1
    SearchRegKeyForSqlServer: Successfully determined instance is installed.
    DropDatabase: Custom Action Data. DBMASTER    localhost\MSSQLSERVER1    master
    ConnectDatabase: server Name before checking for Default Inatance . localhost\MSSQLSERVER1
    ConnectDatabase: server Name . localhost1
    ConnectDatabase: database Name . master
    ConnectDatabase: Failed to initialize database connection. Error Code: 0x80004005. . Additional Error Description : SQL Server does not exist or access denied.
    DropDatabase: ConnectDatabase returned error. Error Code: 0x80004005.
    MSI (s) (98!54) [10:17:28:837]: Product: Microsoft Security Compliance Manager -- Error 25157. Failed to drop database. Error Code: -2147467259 ([DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied.).

    Error 25157. Failed to drop database. Error Code: -2147467259 ([DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied.).
    CustomAction _RollBack_CreateDatabase returned actual error code 1603 but will be translated to success due to continue marking
    Action ended 10:17:29: INSTALL. Return value 3.
    Property(S): DiskPrompt = Microsoft Security Compliance Manager Installation [1]

    I've used the Sql Server Configuration Manager to look at the db and confirm that its running OK.

    I've looked at the Network and Client Protocols and made sure that Shared Mem, Named Pipes & TCPIP are all enabled.

    All to now avail. So now having spent the best part of a day on just trying to install it let alone use it I'm having major doubts about this product so any ideas greatly appreciated.

    Tuesday, May 21, 2013 10:45 AM

All replies

  • Might I be right in thinking that these x log lines are odd ...

    DropDatabase: Custom Action Data. DBMASTER    localhost\MSSQLSERVER1    master
    ConnectDatabase: server Name before checking for Default Inatance . localhost\MSSQLSERVER1
    ConnectDatabase: server Name . localhost1

    I've found a few refs to logs like this on the net and the 3rd line looks unusual in that its just removed "\MSSQLSERVER"

    from the 2nd line. All the samples I've found have the last line with a format like the 2nd line.

    (Note MS's mispelling of Instance with Inatance if your searching. )

    Tuesday, May 21, 2013 2:08 PM
  • ... and now I find that the following interactive sql

    sqlcmd -S localhost\MSSQLSERVER1

    connects just fine. So I'm even more convinced that what I see in the log file indicates that the SCM installation is getting confused. Now I'm off for the night in the hope that some of you bright sparks on the other side of the pond will wake up soon and tell me whats wrong!

    PS If anyone else knows that there's a better forum to post on then please tell me.

    Tuesday, May 21, 2013 3:27 PM