Replication error misleading: You cannot create a publication from server '<server name>' because the server is too old. - by Robert L Davis

Status : 

  Won't Fix<br /><br />
		Due to several factors the product team decided to focus its efforts on other items.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.


8
0
Sign in
to vote
ID 586246 Comments
Status Closed Workarounds
Type Bug Repros 1
Opened 8/13/2010 10:01:58 PM
Access Restriction Public

Description

I accidentally remoted into a machine running Windows 2003 SP2/SQL Server 2005 SP2. From there I connected to a Windows Server 2008 R2/SQL Server 2008 SP1 machine via SQL Server Management Studio.

When I tried to expand the Local Pulbications and Local Subscriptions node under Replication in Object Explorer, I got the following error:

Operation not supported on version 10.0. (Microsoft.SqlServer.SqlEnum)

I decided to try right-clicking on the Local Publications node and creating a new publication. When I clicked on New Publication, I got this even more confusing error:

You cannot create a publication from server '<server name>' because the server is too old.


I verified that the server was SQL Server 2008 SP1 (10.0.2531). I quickly discovered my mistake and the error then made sense, but it is very misleading. The error states that the "Server" is too old, when in fact, it was the version of SSMS that was too old. Before I discovered my error, I thought I might end up having to uninstall and reinstall SQL which would be a major headache because we had just migrated to the new server in production.

If someone encounters this scenario, they might end up going down a bad road before they figure out their error. I am not able to test if this problem still exists for SQL Server 2008 SSMS because SQL 11 is not out yet. If the problem still exists in SQL 2008, it would be nice to fix it before the next major vesion is released.
Sign in to post a comment.
Posted by Will Reynoldson on 8/3/2015 at 7:21 AM
Useful to fix this, I wasted some time trying to work out how the server could be "too old"
Posted by Robert L Davis on 3/10/2011 at 6:46 PM
Understood. Agree that it's not high priority. Thanks for the response.
Posted by Jean-Yves [MSFT] on 10/29/2010 at 3:57 PM
Hi Robert,

thanks for taking the time to share your feedback, this is really important to us.
I agree the supportability could be improved in this area.
Unfortunately this does not meet the bar for now. We will revisit the decision if more customers vote for the issue.

Best regards
Jean-Yves Devant
Program Manager (Replication/CDC/CT)
SQL Server Engine Team