July 14, 2012 at 5:31 pm
Hi all.
I'm having trouble installing SQL 2k8 R2 Ent on a Windows Server 2008 R2 box. This box had 2k8 express, 2k8 web edition and 2012 R0. Since an upgrade failed, I removed all 3 and attempted to do a fresh install but ran in to a new problem.
The initial error mentioned something about reporting services files and database still being on the server. A google search mentioned removing these manually, which I did. But as soon as I did that, rebooted and attempted another install, I ran in to a different problem.
When I run setup.exe, it launches to the initial screen and I click "New installation or add features to an existing installation" and the installation starts. As soon as the installation finishes installing the set-up files, the install window closes and I'm back to the installation center window that originally opens when you run setup.exe. No error, just appears to close the current attempt at installation.
I checked my setup bootstrap/log files and there are numerous text files in this folder but nothing jumps out as a straight "error" or "cancelling setup". Below is the only thing that may relate to an error and it's the end of the file named "Detail_ComponentUpdate.txt".
Copying the files from the DVD to the hard drive yielded the same results. I uninstalled everything and manually cleared the install directory. I also tried the upgrade option. I deleted what registry keys I could find relating to SQL Server. Still no luck although these files installed fine on another server.
Any ideas?
Thanks,
Mark
2012-07-15 19:02:17 Slp: C:\Users\Administrator\Desktop\SQL Server 2008 R2\x64\FixSqlRegistryKey_x86.exe exit code: 0
2012-07-15 19:02:17 Slp: Completed Action: FixSqlRegistryKey, returned True
2012-07-15 19:02:17 Slp: ----------------------------------------------------------------------
2012-07-15 19:02:17 Slp: Running Action: PostMsiTimingConfigAction
2012-07-15 19:02:17 Slp: The object state property 'workflow' is null/empty.
2012-07-15 19:02:17 Slp: Error: Action "PostMsiTimingConfigAction" failed during execution.
2012-07-15 19:02:17 Slp: Completed Action: PostMsiTimingConfigAction, returned False
2012-07-15 19:02:17 Slp: Completed Action: ExecuteStandardTimingsWorkflow, returned True
2012-07-15 19:02:17 Slp: ----------------------------------------------------------------------
2012-07-15 19:02:17 Slp: Running Action: ExecuteCloseWorkflow
2012-07-15 19:02:17 Slp: Workflow to execute: 'CLOSE'
2012-07-15 19:02:17 Slp: ----------------------------------------------------------------------
2012-07-15 19:02:17 Slp: Skipping Action: ProduceStatusLogs
2012-07-15 19:02:17 Slp: Action is being skipped due to the following restrictions:
2012-07-15 19:02:17 Slp: Condition "Is the datastore flag /Scenario/GlobalFlags/AreProductFeaturesSupported set" did not pass as it returned false and true was expected.
2012-07-15 19:02:17 Slp: ----------------------------------------------------------------------
2012-07-15 19:02:17 Slp: Running Action: FinalizeProgressStatus
2012-07-15 19:02:17 Slp: Completed Action: FinalizeProgressStatus, returned True
2012-07-15 19:02:17 Slp: ----------------------------------------------------------------------
2012-07-15 19:02:17 Slp: Running Action: RebootMessageAction
2012-07-15 19:02:17 Slp: Completed Action: RebootMessageAction, returned True
2012-07-15 19:02:17 Slp: ----------------------------------------------------------------------
2012-07-15 19:02:17 Slp: Skipping Action: FinishPage
2012-07-15 19:02:17 Slp: Action is being skipped due to the following restrictions:
2012-07-15 19:02:17 Slp: Condition "Is the user's scenario set to EditionUpgrade" did not pass as it returned false and true was expected.
2012-07-15 19:02:17 Slp: ----------------------------------------------------------------------
2012-07-15 19:02:17 Slp: Skipping property RequireMode of class: StopAction
2012-07-15 19:02:17 Slp: Input of property will not be set due to the following failed restriction(s):
2012-07-15 19:02:17 Slp: Condition "Is the user's scenario set to ComponentUpdate" did not pass as it returned true and false was expected.
2012-07-15 19:02:17 Slp: ----------------------------------------------------------------------
2012-07-15 19:02:17 Slp: Running Action: CloseUI
2012-07-15 19:02:17 Slp: Stop Action
2012-07-15 19:02:17 Slp: Completed Action: CloseUI, returned True
2012-07-15 19:02:17 Slp: Completed Action: ExecuteCloseWorkflow, returned True
2012-07-15 19:02:17 Slp: ----------------------------------------------------------------------
2012-07-15 19:02:17 Slp: Running Action: PassPidBackFromComponentUpdate
2012-07-15 19:02:17 Slp: Pass the flag CuPidDisplayed to the main setup
2012-07-15 19:02:17 Slp: ENU value specified, trying to pass the value to main setup
2012-07-15 19:02:17 Slp: PID value specified, trying to pass the value to main setup
2012-07-15 19:02:17 Slp: SQMREPORTING value is specified in CU workflow, trying to pass the value to main setup
2012-07-15 19:02:17 Slp: Completed Action: PassPidBackFromComponentUpdate, returned True
2012-07-15 19:02:19 Slp:
2012-07-15 19:02:19 Slp:
2012-07-15 19:02:19 Slp: ----------------------------------------------------------------------
2012-07-15 19:02:19 Slp:
2012-07-15 19:02:19 Slp: Setup result: 0
July 31, 2013 at 4:09 am
We are facing same issue... Did you get the fix?
Hemant Patel
August 6, 2013 at 9:29 am
The most reliable fix is to reinstall Windows.
You may be able to get things working by hacking the registry, but you will probably take longer to get things working with this approach than with re-installing Windows. Also, if you reinstall Windows you know you have a stable and repeatable starting point if you ever need to rebuild the server.
Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.
When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply