Answered by:
Failed to get Service Pack version for SQL Server

Question
-
Hi,
I am using SCCM 2012 R2. Windows 2012 R2. SQL Server STD 2012 x64 with SP2.
There are a CAS site.
I need to install a Primary site. The primary site database must be in a remote SQL Server.
At installing the Primary site (join to an existing hierarchy), I get the following error(ConfigMgrSetup.log):
Failed to get Service Pack version for SQL Server <RemoteSQLServer.mydomain.net>
CWmiRegistry::WmiOpen: Failed to read key SOFTWARE\Microsoft\Microsoft SQL Server\Instance Names\SQL on RemoteSQLServer.mydomain.net
The above registry path exists at SQL Server that hosts the CAS database:
But not exists at problematic SQL Server:
There were no problems at installing the remote SQL Server.
The question is:
How to fix lost registry portion at problematic SQL Server?
Thanks in advance!
Friday, October 24, 2014 8:59 PM
Answers
-
Jason's got it. Your second screenshot doesn't look right. There are no installed SQL instances. You should re-install SQL.
This is how it should look for a default installation
Gerry Hampson | Blog: www.gerryhampsoncm.blogspot.ie | LinkedIn: Gerry Hampson | Twitter: @gerryhampson
- Marked as answer by SCCMadmin09 Tuesday, October 28, 2014 8:19 PM
Saturday, October 25, 2014 11:44 AM
All replies
-
That's a question for a SQL forum. Reinstallation is probably the answer though. Are you sure a full server of SQL Server was installed on the remote system?
Jason | http://blog.configmgrftw.com | @jasonsandys
- Proposed as answer by Gerry HampsonMVP Saturday, October 25, 2014 11:42 AM
Friday, October 24, 2014 9:47 PM -
Jason's got it. Your second screenshot doesn't look right. There are no installed SQL instances. You should re-install SQL.
This is how it should look for a default installation
Gerry Hampson | Blog: www.gerryhampsoncm.blogspot.ie | LinkedIn: Gerry Hampson | Twitter: @gerryhampson
- Marked as answer by SCCMadmin09 Tuesday, October 28, 2014 8:19 PM
Saturday, October 25, 2014 11:44 AM -
Thanks to all of you for your help.Tuesday, October 28, 2014 8:19 PM
-
Thanks to all of you for your help.
That does not help others that might find this thread. How did you solve it?Torsten Meringer | http://www.mssccmfaq.de
Tuesday, October 28, 2014 8:42 PM -
The above environment is from a client.
I suggested format remote SQL Server for Primary site database (prior unjoin from domain, delete computer object from AD) and install SQL Server again at the same server.
Regards.
- Proposed as answer by TorstenMMVP Tuesday, October 28, 2014 9:35 PM
Tuesday, October 28, 2014 9:18 PM