When I try to install my SQL Server 2008 R2, it keeps getting stuck at SqlEngineDBStartConfigAction_install_configrc_Cpu64
I found in other issues that I should kill the msiexec process but I can't find it.
What should I do? Thank you
Wasted couple of days on this, that is untill I found this thread:
This simple solution worked for me.
Simply change the account name to Authority/System.
This should work for 2008 as well.
Hope this helps!
Related
I don't know why I am getting this error on my machine while installing SQL Server. I have tried installing 2008, 2012, 2014 versions but getting same error again and again. I have checked control panel to find any files of previous SQL server but nothing is there. Can any one guide me about this error. I have already wasted lot of time to solve this issue. Thanks in advance.
here below link explain error details
https://www.mssqltips.com/sqlservertip/4276/sql-server-setup-error--there-was-an-error-generating-the-xml-document-error-code-0x84b10001/
https://support.microsoft.com/en-us/help/2379466/fix-0x84b10001-error-code-sql-server-2008-or-sql-server-2008-r2-setupm
Check whether the installation path is too long or has many spaces.
I'm trying to install SQL Server 2014 but it stays in the same spot (Install_VCRuntime_Cpu32_Action) for hours. It's already the third time I'm trying to install so I don't know what else to do.
SQL Server 2014 Installation
I observed this very same issue in one of my colleague's windows 10 box with SQL Server 2014 Enterprise installer as well. As mentioned in this MS connect bug you can try either of the below mentioned options:
As mentioned by KevinMS in comments tab :
I used task manager and killed the Windows Installer instances,
clicked Retry and the installation completed. What a beat down.
You can kill the Windows Installer process as shown below:
As mentioned by Jonathan Dyke in workarounds tab:
It's fixed!
http://support.microsoft.com/kb/2820068
I tested this solution with 2014 express and can confirm that using
/SkipInstallerRunCheck works as advertised. The installer no longer
goes into an endless loop when it can't shut down msiserver.
For my colleague who was facing this issue with SQL Server 2014 setup, solution # 1 above worked.
Regarding SQL Server 2017 : My colleague faced exactly same issue on SQL Server 2017 also. We didn't see the "Windows Installer" app in processes tab on his machine. So we went with solution # 2 i.e. launch the installer as Setup.exe /SkipInstallerRunCheck and it worked for him. While running from PowerShell console the command looks like .\Setup.exe /SkipInstallerRunCheck.
I had this same issue on SQL express 2014. When I went to check there was indeed a Windows Installer running. I killed that process & SQL proceeded to install just fine.
Found this here:
https://community.spiceworks.com/topic/483582-ms-sql-2014-install-freezing
I have heard other developers (i.e., not db administrators) complain over the years about the complexity of getting SQL Server installed and configured properly. I installed SQL Server 2014 about six months ago for a project that I'm no longer working on. I tried installing 2008 R2 with a named instance for a new project but something went wrong and I now have an inaccessible instance. My instinct is to remove everything and to just start fresh. Is this the right instinct?
If it is the right instinct, any advice on how to fully, fully, fully uninstall all instances of SQL Server? Seems every time I try to do so, there are some bits and pieces left behind and that gets me wondering if those leftover bits are causing trouble for subsequent re-installs.
If this is not the right instinct, please set me straight. I'm hoping that all of the answers will not be "db administrators are paid to be good at this so go find one." Of course, this is probably the best and most accurate response; but I would also like to solve my problem so if this is your response then I would be grateful if you could point me to a reliable, on-demand SQL Server admin service that I can consult to get this right -- I'm happy to pay for some high quality and efficient help.
Thanks for any advice.
Bob
If you are having problems accessing the server it's a good instinct to remove the name instance and install a new one. The reason you could not access the name instance could be compatibility problem b/n sql2014 and SQL 2008R2 or configuration problem. why do you really want to install SQL 2014 instead of sql2008? my be it's better to install SQL 2014 name instance.
please look at this link to remove the name instance SQL 2008.
http://thoughtsonopsmgr.blogspot.com/2012/10/how-to-remove-sql-server-instance-from.html
I discovered that SQL Server 2008 R2 isn't supported on Windows 10: https://support.microsoft.com/en-us/kb/2681562
So I uninstalled everything related to 2008 (which required a couple of reboots and further uninstall attempts) and then uninstalled everything I could find for 2014... and then I reinstalled 2014 from scratch... and I'm golden.
I have been trying to install SQL Server 2008 R2 and I get the following error
MOF Syntax Error.
And it happends when it gets to the "provider_Cpu32_WMI something.."
Does anyone know how I can fix this, I have tried the whole day with no luck..
Things I have tried,
Manually uninstalling SQL Server 2008 R2 by using Add/Remove Programs, deleting folders, deleting registry keys, etc....
I checked on google and many people had have problems with this... but I have tried it all with no luck.
Thank you in advance
Have you tried a slipstream install that has the CUs? I bet all the money in my pockets (25 cents mind you) that this will resolve the issue.
I previously had sql server 2005 express and uninstalled it.. I also uninstalled any vs related programs and installed visual web developer 2008 express edition with SP1. now that I am trying to install sql server 2008, I am seing error messages like no other and leave that alone without any suggestions..
the latest one which I could not come to a proper solution on the internet is;
consistency validation for sql server registry keys error which suggests
"The SQL Server registry keys from a prior installation cannot be modified. To continue, see SQL Server Setup documentation about how to fix registry keys.
as you might have guessed nothing so informative in the documentation... Also, when I try to delete any sql server related registry key, it does not let me. (yes I stopped all the related services..)
anybody here that can be of any assistance?
You can try with this procedure :
Stop all SQL Server Services
Remove all SQL Server Services with sc delete servicename
Control Panel - Add/Remove Programs - Select and Remove all Microsoft
SQL Server programs
Open regedit and remove all SQL Server folders in this registry key: HKEY_LOCAL_MACHINE/ SOFTWARE/MICROSOFT
Remove SQL Server folders from Program Files directory
Reboot
This procedure should resolve the issue, i've resolved with this procedure ...
i found this to happen if you had an add-in for SSMS installed which hasn't been uninstalled before ssms was uninstalled.
You may need to change the permissions on the relevant registry keys using regedt32 first so that you can then delete the keys via normal regedit
Well actually, I believe, one should not go through such mess in order to accomplish a simple task like this. In the end, I ended up formatting my PC and re-installing SQL Server.
I know this is an old question and you already said in comments that you reformatted the machine. However, I just ran into this exact message and wanted to share my solution because it was so easy, but the error message didn't help at all!
I was using the wrong installation package. I had a 64-bit Intel Windows 7 computer and I was trying to use the x86 version of SQL Server 2008. Once I found the correct version (x64) I did not get this error and the install proceeded normally.
I had a similar problem because I still had some remnants of SQL Server 2005 left - not the services, it was some parts of the IDE. Anyway, to resolve it I used the option to upgrade (sorry, I can't remember the exact option just now). After running the upgrade portion, which took a few minutes, I could then run the full install with no problems.