Weird error during replication initialization - column contains type date, unsupported on the target server.

  • I have a typical sql server 2008 r2 enterprise install on server A. I also have a cluster, B, with two nodes using sql server 2008 r2 enterprise. I'm trying to establish replication from the instance on server A to the clustered instance on B. During the initialization process, the snapshot agent errors out with the following message:

    "Column DateInactivated in objected [mytablename] contains type Date, which is not supported in the target server version, SQL Server 2005."

    Um, what? I'm not using SQL Server 2005 at all here. Anyone seen this before?

  • you sure you're not running sql 2005?

    select @@version on both instances return a 9.0by any chance?

    [font="Times New Roman"]There's no kill switch on awesome![/font]
  • Yes, I'm sure.

  • do you have any 2005 instances in your environment? Could you have set up your subscription to the wrong server by mistake (have similar looking server/instance names).

    I've seen these errors in the past a few times when running a view from a 2008R2 instance which connects to a 2005 instance and got the same error. In this instance I had to cast the date to a datetime.

    Not that I don't believe you bud, but never known sql to lie about the target version... personally....

    [font="Times New Roman"]There's no kill switch on awesome![/font]
  • Yeah, which is why I said "weird error" not just "error" 🙂 No 2005 anywhere.

  • can u post up the full version numbers of the publisher, distributor (if not a local) and the subscriber? i.e 11.0.3128 - can see what sp and cu you're on

    [font="Times New Roman"]There's no kill switch on awesome![/font]
  • 10.50.1617 - single instance

    10.50.1600 - cluster

    I'm updating the cluster right now with the hotfix just to make sure that isn't the problem, though I have a hard time believing that it is.

  • i don't think this makes a difference but is the compatibility level of the subscriber database set to 2005? I did a brief test on my local machine by setting a 2012 DB to 2005 compatibility level but it worked ok....

    [font="Times New Roman"]There's no kill switch on awesome![/font]
  • Hmm. Oddly, the publisher is set to 2005 compatability mode. Weird. I didn't create this database, so I"ll have to check with the DA to see if he was trying to do something in particular here. I just set it to 2008 compatability, restarted the snapshot agent, and now it's delivering everything. Bizarre.

  • Phew - glad we got there - was starting to run out of ideas!

    [font="Times New Roman"]There's no kill switch on awesome![/font]
  • hahah...thanks for the assist.

Viewing 11 posts - 1 through 10 (of 10 total)

You must be logged in to reply to this topic. Login to reply