March 26, 2010 at 4:39 am
Hi.
I did have SQL Express 2008 SP1 on my development box, which runs windows 7. This was all find and dandy and everything worked fine.
I then wanted to install SQL 2008 Developer Edition so that I could do some SSIS work. This failed dismally to install. I then detached my SQL Express databases and uninstalled the partially-installed SQL 2008 (some features went on, Database Services ddint) and SQL Express. Both products failed to un-install, giving errors deleting an assembly. I eventually just manually deleted the assembly and the uninstall worked for both.
So now I tried a fresh install of SQL 2008 Developer Edition. Again, it failed. I got all sorts of different errors trying it with both installed, but now I just get the same error over and over in the error log:
Error: Action "SqlEngineDBStartConfigAction_install_configrc_Cpu32" failed during execution.
In the SQL Error log, I get:
2010-03-26 09:18:44.13 spid7s Error: 15209, Severity: 16, State: 1.
2010-03-26 09:18:44.13 spid7s An error occurred during encryption.
Even though SQL isn't really installed yet.
The other weird thing is that I don't get prompted that I can't run it without installing SQL 2008 SP1. I did get that prompt when I installed Express.
So, given that I can't install SQL at all now, does anyone know how I can fix this?
Thanks.
April 8, 2010 at 4:30 am
Here is a solution for this.
This failure often is caused by a system or domain policy removing the SeDebugPrivelege security privilege from the administrator account running setup. Verify that the account running has this privilege.
The AccessChk tool will print all privleges for an account (http://technet.microsoft.com/en-us/sysinternals/bb664922.aspx) by running:
accesschk.exe -a <Domain>\<Account> *
Alternatively, we can check this through your group policy editor as mentioned below:
Open Group Policy...
Start | Run | Type: gpedit.msc | OK |
Navigate to
Computer Configuration\Windows Settings\Security Settings\Local Policies\User Rights Assignment\Debug programs
The account through which we are trying to run the setup should be here ( besides the local admin on that machine). I included that here, restarted the server ( this is mandatory, gpupdate /force will not work) and ran the setup and it was successful this time.
SQL Server 2008 setup needs this privilege to start up the SQL Server process and listen to an event that signals back to setup that SQL Server successfully started.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply