![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
When trying to install SQL2008 R2 Developer Edition x64 on Windows 7 x64, I am getting an Error: 2010-06-12 22:05:40 Slp: ------------------------------------------------------------ 2010-06-12 22:05:40 Slp: C:\tmp\sql\x64\FixSqlRegistryKey_x86.exe exit code: 0 2010-06-12 22:05:40 Slp: Completed Action: FixSqlRegistryKey, returned True 2010-06-12 22:05:40 Slp: ---------------------------------------------------------------------- 2010-06-12 22:05:40 Slp: Running Action: PostMsiTimingConfigAction 2010-06-12 22:05:40 Slp: The object state property 'workflow' is null/empty. 2010-06-12 22:05:40 Slp: Error: Action "PostMsiTimingConfigAction" failed during execution. This workstation also has VS2010 installed, and SQL 2008 and VS2010 have been uninstalled, still getting the same error. Without rebuilding the workstation, what am I missing? |
#3
| |||
| |||
|
|
William F. Kinsley (bacardi (AT) noemail (DOT) nospam) writes: When trying to install SQL2008 R2 Developer Edition x64 on Windows 7 x64, I am getting an Error: 2010-06-12 22:05:40 Slp: ------------------------------------------------------------ 2010-06-12 22:05:40 Slp: C:\tmp\sql\x64\FixSqlRegistryKey_x86.exe exit code: 0 2010-06-12 22:05:40 Slp: Completed Action: FixSqlRegistryKey, returned True 2010-06-12 22:05:40 Slp: ---------------------------------------------------------------------- 2010-06-12 22:05:40 Slp: Running Action: PostMsiTimingConfigAction 2010-06-12 22:05:40 Slp: The object state property 'workflow' is null/empty. 2010-06-12 22:05:40 Slp: Error: Action "PostMsiTimingConfigAction" failed during execution. This workstation also has VS2010 installed, and SQL 2008 and VS2010 have been uninstalled, still getting the same error. Without rebuilding the workstation, what am I missing? Good question. Setup errors can be very difficult to understand. Is this your own machine at home? Or is it a machine at work, where a sysadmin may have set some evil group policy? Do the dashes indicate that you have edited out some parts? Are you sure that there is nothing of interest there? You could submit a bug report on http://connect.microsoft.com/sqlserver/feedback and be sure you include all the log files from the setup. Don't expect an instant answer, but you should hear something in a week. -- Erland Sommarskog, SQL Server MVP, esquel (AT) sommarskog (DOT) se Links for SQL Server Books Online: SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx SQL 2000: http://www.microsoft.com/sql/prodinf...ons/books.mspx . |
#4
| |||
| |||
|
|
I submitted the report with log files. -- -------------------------------------- William F. Kinsley Sr. Design Engineer NextGen Healthcare Info. Sys. Inc "Erland Sommarskog" wrote: William F. Kinsley (bacardi (AT) noemail (DOT) nospam) writes: When trying to install SQL2008 R2 Developer Edition x64 on Windows 7 x64, I am getting an Error: 2010-06-12 22:05:40 Slp: ------------------------------------------------------------ 2010-06-12 22:05:40 Slp: C:\tmp\sql\x64\FixSqlRegistryKey_x86.exe exit code: 0 2010-06-12 22:05:40 Slp: Completed Action: FixSqlRegistryKey, returned True 2010-06-12 22:05:40 Slp: ---------------------------------------------------------------------- 2010-06-12 22:05:40 Slp: Running Action: PostMsiTimingConfigAction 2010-06-12 22:05:40 Slp: The object state property 'workflow' is null/empty. 2010-06-12 22:05:40 Slp: Error: Action "PostMsiTimingConfigAction" failed during execution. This workstation also has VS2010 installed, and SQL 2008 and VS2010 have been uninstalled, still getting the same error. Without rebuilding the workstation, what am I missing? Good question. Setup errors can be very difficult to understand. Is this your own machine at home? Or is it a machine at work, where a sysadmin may have set some evil group policy? Do the dashes indicate that you have edited out some parts? Are you sure that there is nothing of interest there? You could submit a bug report on http://connect.microsoft.com/sqlserver/feedback and be sure you include all the log files from the setup. Don't expect an instant answer, but you should hear something in a week. -- Erland Sommarskog, SQL Server MVP, esquel (AT) sommarskog (DOT) se Links for SQL Server Books Online: SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx SQL 2000: http://www.microsoft.com/sql/prodinf...ons/books.mspx . |
#5
| |||
| |||
|
|
Any resolution on this, I'm getting the same error when I try to do an unattended install. |
#6
| |||
| |||
|
|
Dan S (Dan S (AT) discussions (DOT) microsoft.com) writes: Any resolution on this, I'm getting the same error when I try to do an unattended install. I would suggest that you post a bug to https://connect.microsoft.com/SQLServer/feedback/ Make sure to include logs, as described in the comment from Microsoft in this bug: https://connect.microsoft.com/SQLSer...03/cant-start- sql-server-2008-r2-database-engine If it is urgent, you are better off opening a case with Microsoft. -- Erland Sommarskog, SQL Server MVP, esquel (AT) sommarskog (DOT) se Links for SQL Server Books Online: SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx SQL 2000: http://www.microsoft.com/sql/prodinf...ons/books.mspx . |
![]() |
| Thread Tools | |
| Display Modes | |
| |