March 29, 2011 at 4:11 am
I'm having endless frustration trying to install (or re-install, to be a bit more accurate) SQL2008R2 Dev on Windows7 (32-bit)
Process:
Uninstall previous installations of SQL2005 and SQL2008.
Reboot PC.
Start the setup as Administrator - OK
Select "New Installation" - OK
Setup Support Rules - Pass OK
Product Key - OK
Install Setup Support Files - No obvious errors reported (although the window disappears very quickly)
I'm now returned to the main "SQL Server Installation Center" window, and nothing else happens. The SQL folders have been created under Program Files, and log files are present, but no services have been installed.
The logfiles are rather lengthy and voluminous to include here, but in the Detail_ComponentUpdate log I notice the following entries:
2011-03-29 10:50:43 Slp: ----------------------------------------------------------------------
2011-03-29 10:50:43 Slp: Skipping Action: ScheduleUpgradePackageInstallActionsAction
2011-03-29 10:50:43 Slp: Action is being skipped due to the following restrictions:
2011-03-29 10:50:43 Slp: Condition "Is the datastore flag /Scenario/GlobalFlags/EnableSxSUpgrade set" did not pass as it returned false and true was expected.
2011-03-29 10:50:43 Slp: ----------------------------------------------------------------------
2011-03-29 10:50:43 Slp: Skipping Action: ScheduleConfigAction
2011-03-29 10:50:43 Slp: Action is being skipped due to the following restrictions:
2011-03-29 10:50:43 Slp: Condition "Is the datastore flag /Scenario/GlobalFlags/EnableExternalMsiConfiguration set" did not pass as it returned false and true was expected.
2011-03-29 10:50:43 Slp: ----------------------------------------------------------------------
2011-03-29 10:50:43 Slp: Skipping Action: NotifyProgressCountDisplay
2011-03-29 10:50:43 Slp: Action is being skipped due to the following restrictions:
2011-03-29 10:50:43 Slp: Condition "Is the user's scenario set to ComponentUpdate" did not pass as it returned true and false was expected.
2011-03-29 10:50:43 Slp: Completed Action: ExecuteScheduleActionsWorkflow, returned True
2011-03-29 10:50:43 Slp: ----------------------------------------------------------------------
2011-03-29 10:50:43 Slp: Running Action: ExecuteStandardTimingsWorkflow
2011-03-29 10:50:44 Slp: Workflow to execute: 'STANDARDTIMINGS'
2011-03-29 10:50:44 Slp: ----------------------------------------------------------------------
2011-03-29 10:50:44 Slp: Skipping Action: ValidationTimingConfigAction
2011-03-29 10:50:44 Slp: Action is being skipped due to the following restrictions:
2011-03-29 10:50:44 Slp: Condition "Is the datastore flag /Scenario/GlobalFlags/EnableExternalMsiConfiguration set" did not pass as it returned false and true was expected.
2011-03-29 10:50:44 Slp: ----------------------------------------------------------------------
2011-03-29 10:50:44 Slp: Skipping Action: SaveConfigurationFile
2011-03-29 10:50:44 Slp: Action is being skipped due to the following restrictions:
2011-03-29 10:50:44 Slp: Condition "Is the datastore flag /Scenario/GlobalFlags/IsUserVisibleScenario set" did not pass as it returned false and true was expected.
2011-03-29 10:50:44 Slp: ----------------------------------------------------------------------
2011-03-29 10:50:44 Slp: Skipping Action: UpdateLicenseFile
2011-03-29 10:50:44 Slp: Action is being skipped due to the following restrictions:
2011-03-29 10:50:44 Slp: Condition "Do any product features match one of the expected scenarios" did not pass as it returned false and true was expected.
2011-03-29 10:50:44 Slp: ----------------------------------------------------------------------
2011-03-29 10:50:44 Slp: Running Action: PreMsiTimingConfigAction
2011-03-29 10:50:44 Slp: The object state property 'workflow' is null/empty.
2011-03-29 10:50:44 Slp: Error: Action "PreMsiTimingConfigAction" failed during execution.
2011-03-29 10:50:44 Slp: Completed Action: PreMsiTimingConfigAction, returned False
2011-03-29 10:50:44 Slp: ----------------------------------------------------------------------
2011-03-29 10:50:44 Slp: Skipping Action: CachePatchPackage
2011-03-29 10:50:44 Slp: Action is being skipped due to the following restrictions:
2011-03-29 10:50:44 Slp: Condition "Is the datastore flag /Scenario/GlobalFlags/EnableSlipstream set" did not pass as it returned false and true was expected.
2011-03-29 10:50:44 Slp: ----------------------------------------------------------------------
2011-03-29 10:50:44 Slp: Running Action: InitializeMsiAction
2011-03-29 10:50:44 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine
2011-03-29 10:50:44 Slp: Sco: Attempting to open registry subkey SOFTWARE\Microsoft\NET Framework Setup\NDP\v2.0.50727
2011-03-29 10:50:44 Slp: Attempting to pause the 32 bit ngen queue for x86
2011-03-29 10:50:44 Slp: ngen command to be used from .Net Framework Directory: C:\Windows\Microsoft.Net\Framework\v2.0.50727
2011-03-29 10:50:44 Slp: Microsoft (R) CLR Native Image Generator - Version 2.0.50727.4927
2011-03-29 10:50:44 Slp: Copyright (c) Microsoft Corporation. All rights reserved.
2011-03-29 10:50:44 Slp: The .NET Runtime Optimization Service is started and paused.
2011-03-29 10:50:44 Slp: Completed Action: InitializeMsiAction, returned True
2011-03-29 10:50:44 Slp: ----------------------------------------------------------------------
I've tried renaming the old program files folders before installing, in case anything in there was causing it to skip a step, but I'm completely stumped. I've never had such trouble installing SQL before.
Has anyone else had similar problems?
Any assistance greatly appreciated.
April 4, 2011 at 5:22 am
What edition of Windows 7 is this? (Home Basic/Home Premium/Professional/Ultimate)
Thanks & Regards,
Nakul Vachhrajani.
http://nakulvachhrajani.com
Follow me on
Twitter: @sqltwins
April 4, 2011 at 5:58 am
Looks like it is trying to upgrade an existing installation, instead of performing a fresh install.
Maybe some dirty registry keys?
-- Gianluca Sartori
April 5, 2011 at 11:52 am
This is Windows 7 Pro
April 8, 2011 at 8:30 am
Did you check the Windows 7 equivalent of add/remove programs to verify that no version of SQL Server 2008 R2 is listed for uninstall? If there are any SS2008R2 entries, uninstall them from outside the SQL environment to clean the machine. Simply deleting directories does not work.
Alternatively, you could try to 'update' an existing installation - even if you end up not choosing anything to update, it may reset your update flag without mucking around in the registry.
Unfortunately, I'm still working off of my Windows 2000 machine, so I can't experiment with Win7 myself...
April 8, 2011 at 8:41 am
Hi Steve,
Yes - I did try all those things.
- Completely uninstalled 2008R2 and re-installed it. This failed as above.
- Completely uninstalled 2008R2 and tried to replace it with 2008 (same problem)
- Completely uninstalled both 2008R2 and 2008 and installed 2005. This 2005 install worked beautifully.
I would try to upgrade this to 2008R2, but frankly I can't be bothered now that I've got a working client that lets me do the things I want.
I'm leaving the complany shortly in any case (no connection to the install problems! :0) )so this really isn't a priority for me any more.
Thanks to all those who've offered suggestions.
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply