November 21, 2010 at 2:14 am
We have a package working perfectly. Because of space constraints we get New server with same configuration. We changed the connection to new server. from then we are getting Error: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. he AcquireConnection method call to the connection manager "Server" failed with error code 0xC0202009. There may be error message posted before this with more information on why the AcquireConnection method call failed.
we tried all option like enabling the Delay validation =”True” and Retain same connection = “True”. But no luck.
can any one suggest is there any other options to look?
Its very urgent....
November 22, 2010 at 11:23 am
First of all, those two options - DelayValidation and RetainSameConnection - have nothing to do with connection problems, so it's normal they don't solve your problem 🙂
How do you configure your package (and more specific, your connections)?
My guess the package is still looking for the old server.
ps: it's better to post your question and its details in the body, not in the topic title or subtitle. When someone reads your topic, they can't read the full title no more.
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
November 23, 2010 at 3:01 pm
If you copied the packages across, rather than deploying them, you have to understand that the server refers to the connections as GUIDs, not as 'names'. The GUIDs are unique to each server, so whatever the GUID is for connection A on the old server, will most likely NOT be the same for connection A on the new server.
Solution: DEPLOY the SSIS packages onto the new server.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply