SP1 to R2 Upgrade - The installed Version of SQL Server is not supported for the operational database

Question

Hello, 
Am trying to upgrade a SCOM SP1 environment to SCOM R2( 3 MGT servers, 1 GW and 2 Web console boxes )
The prerequisites are failing and it is stating the following ; 
Operational Database SQL Version Check - The installed Version of SQL Server is not supported for the operational database
Data Warehouse  SQL Version Check - The installed Version of SQL Server is not supported for the data warehouse
The SQL servers are running SQL 2012 SP1 64 Enterprise, which is compatible.
All other pre-upgrade tasks have been done. 
Help appreciated! 

Answer 1

I'm having the exact same issue, I believe. I think that Tubble has problem with SCOM 2012. Not 2007.
I've checked the compatibility list for both SCOM 2012 SP1 and R2. All newer Windows Server and SQL versions are supported. We're running the SQL 2012 SP1 x64 Standard edition on a Windows Server 2012 Standard.
I even tried to move the database from SQL 2012 to an older SQL 2008 R2, but that's not supported either. Only upgrading. Not downgrading.
So, I started checking the opsMgrSetupWizard.log file for clues. And the error message was there as well. But the reason why it says not supported is that it can't get the info about the OS version, so I guess it assumes the OS version is to low. The RPC
service can not be reached.
[10:29:11]: Error: :GetRemoteOSVersion(): Threw Exception.Type: System.Runtime.InteropServices.COMException, Exception Error Code: 0x800706BA, Exception.Message: The RPC server is unavailable. (Exception from HRESULT: 0x800706BA)
[10:29:11]: Error: :StackTrace: at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)
at System.Management.ManagementScope.InitializeGuts(Object o)
at System.Management.ManagementScope.Initialize()
at System.Management.ManagementObjectSearcher.Initialize()
at System.Management.ManagementObjectSearcher.Get()
at Microsoft.EnterpriseManagement.OperationsManager.Setup.Common.SetupValidationHelpers.GetRemoteOSVersion(String remoteComputer)
[10:29:11]: Debug: :IsSQLOnAValidComputer: remote OS version string was null or empty.
[10:29:11]: Error: :Error:IsValidSQLVersionCheck: SqlServer OS version is too low.
[10:29:11]: Debug: :**************************************************
[10:29:11]: Error: :<![CDATA[CheckPrerequisites: Logic Type:and IsValidOMDBSQLVersionCheck: 2]]>
[10:29:11]: Error: :
[10:29:11]: Error: :CheckPrerequisites: OMDBSqlVersionCheckTitle: Failed
[10:29:11]: Error: :
[10:29:11]: Debug: :**************************************************
[10:29:33]: Error: :GetRemoteOSVersion(): Threw Exception.Type: System.Runtime.InteropServices.COMException, Exception Error Code: 0x800706BA, Exception.Message: The RPC server is unavailable. (Exception from HRESULT: 0x800706BA)
[10:29:33]: Error: :StackTrace: at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)
at System.Management.ManagementScope.InitializeGuts(Object o)
at System.Management.ManagementScope.Initialize()
at System.Management.ManagementObjectSearcher.Initialize()
at System.Management.ManagementObjectSearcher.Get()
at Microsoft.EnterpriseManagement.OperationsManager.Setup.Common.SetupValidationHelpers.GetRemoteOSVersion(String remoteComputer)
[10:29:33]: Debug: :IsSQLOnAValidComputer: remote OS version string was null or empty.
[10:29:33]: Error: :Error:IsValidSQLVersionCheck: SqlServer OS version is too low.
[10:29:33]: Debug: :**************************************************
So, in our case this was just a FW that was blocking some high ports between management server and SQL. I believe TCP port 135 also needs to be open.
Let's hope this fixes your issue as well, Tubble.
Have a great day!