Version issues?

• NicHopper

  SSCrazy Eights

  Points: 9090

  More actions

  September 3, 2014 at 3:32 am

  #397289

  Hi,

  I wondered if anyone can help me out with this.

  We have two servers (A & B), A is running SQL 2005 and our new server B is running SQL 2012. We have a scenario where server A kicks off a job, the job has one step in it which calls a package on server B. The job is failing with the following error message;

  "Could not load package "\MSDB\Folder 1\The Package" because of error 0xC00160AA. Description: Connect to SSIS Service on machine "Server B" failed: Class not registered ."

  My thoughts are that server A (2005) can't call packages on server B (2012) due to the versions, I wondered if anyone had ever come across anything similar or knew how to resolve this.

  Our potential workaround for this will be to move the package from server B and put it on server A so the job is just running the package locally but I want to try and understand the issue and see what my options are on this one.

  Any help is appreciated.

  Thanks,

  Nic

  Check out my blog http://www.sqlservercentral.com/articles/Best+Practices/61537/

• michal.lisinski

  SSCertifiable

  Points: 7201

  More actions

  September 4, 2014 at 4:07 am

  #1743131

  Hi

  Let me clarify, you run the job on server A (SSIS instance) that calls the package on sever B.

  It will be a bit more time consuming to rewrite the package for 2005 version, if there's SQL Agent running on server B, you can play with job.

  Thanks

  Mike