Hi

I am trying to install SCCM 2012 sp1 with a remote sql 2012 server.

during setup when I enter the SQL name i hit next and then I get this error.

"Configuration Manager requires Microsoft SQL Server 2008 SP2 with Cumulative update 9 or higher, Microsoft SQL Server 2008 SP3 with Cumulative update 4 or higher, Microsoft SQL Server 2008 R2 SP1 with Cumulative update 6 or higher or Microsoft SQL Server 2012 with Cumulative update 2 or higher,"

I installed SQL sp1 and CU3 as well. but still the same error.

please assist

thanks

troy

• Edited by tamimh Monday, January 06, 2014 6:37 PM

Do you have any other instances on that SQL 2012 server? Maybe you have installed service pack and CU3 on wrong instance?

Can you post back the version number of your SQL server?
https://support.microsoft.com/kb/321185

For example:
Method 1: Connect to the server by using Object Explorer in SQL Server Management Studio. After Object Explorer is connected, it will show the version information in parentheses, together with the user name that is used to connect to the specific instance of SQL Server.

Additionally, the account you are using to run setup must be a sysadmin in that SQL Instance and be a local admin on the system hosting that SQL Instance.

Hello and thanks for replying

There are no other instances on the SQL machine. only SQLINST1 service is in services.msc.

I also verified it with a DBA.

The version of SQL is 11.0.3349.0 AKA - SQL Server 2012 Service Pack 1 CU3.

I am performing the installation with a domain admin which is also a sysadmin on the SQL server.

Is the DB on a non-default instance and/or listening on a non-default port?

Hi,

1. If you use default instance, please do not fill in the instance name.
2. You could use telnet sqlserver 1433 to verify the connection and port.

Hi all

The SQL is listening on an alternate port. I use SQL alias to direct the connection on the correct port.

Another thing I forgot to say is that on the same SQL server I have SCOM already installed.

So to eliminate this as a problem, I installed a fresh SQL server and directed the installation to the new server, the setup was fine.

That means that to System center products cannot be installed on the same SQL instance.

am I correct?

I don't think there is a technical enforcement of using separate instances but it certainly is a good idea.

I don't think SQL aliases are supported by ConfigMgr and may be the actual source of the issue.

You have to use a dedicated instance for ConfigMgr.

Hi

I am using SQL alias on 3 other environments and it works fine.

I cant see any other way to make SCCM talk to SQL on a different port.

That's what the SQL Browser is for on the SQL Server: to direct client requests for non-default instances of SQL to the proper port.

Also, I know ConfigMgr doesn't support dynamic ports -- not sure if you are using static or dynamic but its worth pointing out.

Im using a static port. Our policy forbid using the default 1433 SQL port so I have to use a different port.

Alias works just fine.

Thanks for your answer.

troy

Our policy forbid using the default 1433 SQL port so I have to use a different port.

Total side comment: what a stupid policy.

As for aliases, maybe so, but that doesn't make them supported or the preferred choice.

And for your problem, you said "I am using SQL alias on 3 other environments and it works fine." Does that mean 3 other *ConfigMgr* environments?