SQL Server Version Error After Upgrade to GP 2015 R2

(0) Share

Report

Posted on by Community Member

Hi,

I am performing a test upgrade from GP 2010 to GP 2015 R2 with SQL Server 2014. Everything is working on the server and I am able to use the GP Utilities to create new databases and other tools, I am able to log into GP with no issues.

I installed GP 2015 R2 to a workstation with Windows 7 Pro. When I run the GP Utilities after installing, I get this version error:

"Your current SQL Server is not a supported version.

Req: Microsoft SQL Server 11.0

Act: Microsoft SQL Server 2005 R2 (RTM) - 10.50.1617.0

You need to upgrade to SQL Server 11.0 before continuing."

I have set the compatibility level of all the databases to SQL Server 2014 (12.0), and even tried to change it to SQL Server 2012 (11.0) and still cannot get beyond this error on the workstation.

Any ideas?

*This post is locked for comments

I have the same question (0)

All responses (3)

Answers (0)

Richard Wheeler 75,848 Moderator on at

Like (0)

Report

Did you create a package file to install GP 2015 R2? I would start by checking to insure that the ODBC DSN connection that you create is pointing to the 2014 instance of SQL and not the old 2005 instance of SQL. On your server do you have multiple instances of SQL? Log into SSMS for SQL 2014 and make note of the full instance name.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Richard, you're exactly right! There is a mix up with the DNS. Not sure but the name is resolving to the old server. When I set the ODBC to use the IP address instead, then it points to the correct server with the updated information. It took me a while to figure that out but it was an interesting one!

Thanks for your input.

Was this reply helpful? Yes No
Suggested answer

Beat Bucher GP Gee... 28,058 Moderator on at

Like (0)

Report

Rukia,

This is an old know problem happening quite often when customers are migrating from one SQL server to a new one... My suggestion : use a DNS alias to point to your new server and create your ODBC entries by using the DNS Alias... this way you'll never have to upgrade/change the ODBC entry to point to a new server.. just make sure your DNS alias points to the proper server..

Also, make sure the client workstation have the latest SQL client run-time files installed to connect to SQL 2014, as this might not be supporting older 'SQL clients' from 2005.

Was this reply helpful? Yes No