December 2, 2012 at 6:25 am
Okay - I'm running a dev instance on Windows 7 - which when I build, I added attunity 1.2, and then attunity 2.0 connectors.
Our production machine is Exchange 2003 - which won't install Attunity 2.0. When I port a package - it basically rejects the connectors because they've been built with Attunity 2.0 rather than 1.2
I've removed Attunity 2.0 from the dev machine and Programs just shows Attunity 1.2
Everything works fine on the development box - but still when I port to Production, I get the same error. The only solution I've found is to remove all the Oracle destinations from the package and add them back on the production server. This is a real pain.
Any suggestions - unfortunately my development box has regedit disabled - I guess the administrastors don't trust us developers 🙁
Just out of interest, for those suffering the same problem, I have figured out a work around which saves me re-specifying the destinations. Use notepad to edit the package and find all the connections which use Attunity and look for version="3". Changing this to version="2" seems to do the trick. I know it's a bodge.....
December 8, 2012 at 4:55 am
:blush:
You know there are times you just wished you'd never asked something.
Anyway - the deinstall worked fully - apologies to Attunity. It eventually transpired that the production machine wasn't running Attunity 1.2 ( although I had been assured it was). In actual fact, it was running 1.1 - upgrade that to 1.2 and every was hunky dory.
Morale - don't trust Tech Support 🙂
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply