SCM V2 install on Windows 7 x64 failing
-
19 septembrie 2011 12:49
I am trying to install SCM v2 on a stand alone laptop with no internet connection and it continues to fail with errorCode= 1603. under the application log I get error for MsiInstaller "product: Microsoft Security Compliance Manager -- Error 25158. Error Code: 5000. Failed to execute SQL script.
During installation I select "one of the existing SQL instances" and select localhost\MSSQLSERVER. The MSSQLSERVER process in running in services...
Any help appreciated!
Toate mesajele
-
21 septembrie 2011 15:01Really??? No help???
-
21 septembrie 2011 17:35ProprietarTiger, I apologize but I haven't had to troubleshoot any installation issues with SCM over the past year, I'm trying to get one of the testers to respond.
Kurt Dillard http://www.kurtdillard.com -
21 septembrie 2011 17:56
Please look at the SCM installer log files at
C:\Users\<User Name>\AppData\Local\Temp\SCM Installer Logs 2011-08-15_153751. This folder will have 3 files SCMsetup.log, SCmSetupmsi.log.
Please look at the SCMSetupmsi.log and it will have error code. Please look and you should be able to move forward.
if you still have problem. Please email the log files to SecwishM@microsoft.com.
Thanks for using SCM.
-
23 septembrie 2011 12:46Thanks for the assistance. After reviewing the log and confirming that it was an SQL access issue I gave it a little more thought. I do already have SQL installed but it was installed by another program so I believe that the user that SCM was trying to install the sql instance with couldn't use the current one. Long story short I used the installer to launch another SQL server instance and all is well.
-
26 octombrie 2011 08:35
Just ran into the same issue while trying to install SCM v2 on Windows 7 x64 and trying to use an already existing SQL Server 2008 Express installation on the machine.
The error messages in the SCM installer log files hinted at the installation scripts not being able to find the specified database server while trying to use the Named Pipes transport.
So I went into the SQL Server Configuration Manager and enabled the "Named Pipes" protocol (per default, a SQL Server 2008 Express installation seems to only have "Shared Memory" enabled here). After that, the installation completed sucessfully.
- Editat de mhu0815 26 octombrie 2011 08:36
-
26 octombrie 2011 15:26ProprietarNice, thanks for sharing this solution!
Kurt Dillard http://www.kurtdillard.com -
2 noiembrie 2011 14:22This worked for me also, thanks