June 30, 2014 at 2:46 pm
I am trying to deploy my SSIS package from my Windows 7 64-bit development machine to a Windows Server 2008 R2 server. The package now includes a Attunity Oracle connection that works fine on the dev box. Both the dev box and the server have the same 32-bit and 64-bit Oracle clients installed. I have deployed and run the package on the server successfully before I added the Oracle connection.
Now when I try to deploy I get a fail with the message:
Failed to deploy project. For more information, query the operation_messages view for the operation identifier '10194'. (Microsoft SQL Server, Error: 27203)
When I query the view I get:
Failed to deploy the project. Fix the problems and try again later.:Unable to create the type with the name 'MSORA'.
Any idea what the problem might be?
Thank you!
June 30, 2014 at 3:10 pm
Just to state the obvious, but have you deployed the Attunity connectors on the Win 2008 box?
We have these working in our environment but I do remember it being a bit fiddly. For example, BIDS is a 32-bit application, so when running in interactive mode, you're running the 32-bit version of Attunity, but if you've deployed to a live server and are running from an Agent job (and haven't clicked the 32-bit runtime checkbox) then it will be looking for the 64-bit version.
There is also a prerequisite as I remember:
Microsoft Visual C++ 2008 SP1 Redistributable Package (x64)
http://www.microsoft.com/en-us/download/details.aspx?id=2092
July 1, 2014 at 7:37 am
You got it Grasshopper! I guess I thought those bits would be wrapped up in the SSIS package. Once I installed them on the server I could deploy.
Now however, I see that the Attunity connector requires SQL Enterprise edition! I have developers on my dev box so it worked. The server is standard edition so does not work. Ugh!!!
Thanks for your help!
Jonathan
July 1, 2014 at 7:51 am
jonathan.matt (7/1/2014)
Now however, I see that the Attunity connector requires SQL Enterprise edition! I have developers on my dev box so it worked. The server is standard edition so does not work. Ugh!!!
I ran into the same thing. Frustrating 🙂
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
July 1, 2014 at 8:02 am
Yes and it is not made clear on the Attunity site. It may be buried somewhere but I don't see it.
December 23, 2014 at 7:03 am
Thats very strange, I have an Enterprise Edition on a 64 bit Windows 2012 Server Standard Edition, and I get the following error:
Failed to deploy project. For more information, query the operation_messages view for the operation identifier '80
April 17, 2015 at 11:18 am
Did you figure out how to get it to work?
May 3, 2015 at 6:29 pm
I had a similar error:
Failed to deploy project. For more information, query the operation_messages view for the operation identifier '192473'
So I ran the following SQL:
SELECT [message]
FROM [SSISDB].[internal].[operation_messages]
where [operation_id] = 192473
Which returned:
Failed to deploy the project. Fix the problems and try again later.:Unable to create the type with the name 'MSORA'.
Installing the Attunity drivers via the MSI corrected this.
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply