Here’s a new Knowledge Base article we published. This one talks about an issue where a System Center Service Manager installation fails with a SQL version related error message.
While either installing a fresh copy of System Center 2012 Service Manager or while upgrading, you receive the following error message after specifying the SQL server to host the Service Manager database:
The SQL Server name is not running version SQL Server 2008 SP2 or SQL Server 2008 R2. Please update it to the newest version and retry.
NOTE The server in question already has SQL 2008 R2, SP2 or higher installed.
This can occur if there is an issue with the SQL MOF file.
To resolve this issue, recompile the MOF:
1. Open a command prompt with Administrator rights on the SQL server where you want to install the Service Manager databases.
2. Change to the following directory:
C:\Program Files (x86)\Microsoft SQL Server\100\Shared>
3. Once at this location execute the following command:
The successful completion of the above command should generate output similar to the following:
Microsoft (R) MOF Compiler Version 6.1.7600.16385 Copyright (c) Microsoft Corp. 1997-2006. All rights reserved. Parsing MOF file: sqlmgmproviderxpsp2up.mof MOF file has been successfully parsed Storing data in the repository... Done!
Once complete, restart the Service Manager installation.
For the most current version of this article please see the following:
22719717 - System Center Service Manager installation fails with SQL version related error
J.C. Hornbeck | System Center & Security Knowledge Engineer
Get the latest System Center news on Facebook and Twitter:
App-V Team blog: http://blogs.technet.com/appv/ ConfigMgr Support Team blog: http://blogs.technet.com/configurationmgr/ DPM Team blog: http://blogs.technet.com/dpm/ MED-V Team blog: http://blogs.technet.com/medv/ Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/ Operations Manager Team blog: http://blogs.technet.com/momteam/ SCVMM Team blog: http://blogs.technet.com/scvmm Server App-V Team blog: http://blogs.technet.com/b/serverappv Service Manager Team blog: http://blogs.technet.com/b/servicemanager System Center Essentials Team blog: http://blogs.technet.com/b/systemcenteressentials WSUS Support Team blog: http://blogs.technet.com/sus/
The Forefront Server Protection blog: http://blogs.technet.com/b/fss/ The Forefront Endpoint Security blog : http://blogs.technet.com/b/clientsecurity/ The Forefront Identity Manager blog : http://blogs.msdn.com/b/ms-identity-support/ The Forefront TMG blog: http://blogs.technet.com/b/isablog/ The Forefront UAG blog: http://blogs.technet.com/b/edgeaccessblog/
This error can occur when configuring Reporting Services in the DW installation if the SSRS instance has an underscore in the name...
Please report this as a bug...
+1 on the underscore bug; wasted about 2 hours until I found this post.
Yes... it was the underscore that screwed up the install. Thanks a bunch underscore guy!