Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
deal11deal1
Starting Member
34 Posts |
 Posted - 2011-08-22 : 16:58:38
|
| Hello everyone,I came across a issue today related to SSIS that has never seen y me so hopefully some one form might have a solution for this.I have SSIS packages running on the server that use configuration files for connections.for some reason last week the packages start failing with the error"SIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER"we tried many thing but didn't work finally i just restarted the SSIS services again and every thing worked fine.now today the same issues came again, i applied the same solution and it worked.what could be the long term solution to this so the packages wont fail.what the reason that the connection to the configuration file gets broken down and a restart of the services corrects it.and how can fix it so the packages wont fail.Hope some one can help me. |
|
|
yosiasz
Master Smack Fu Yak Hacker
1635 Posts |
Posted - 2011-08-22 : 18:23:59
|
| after you restarted the ssis service did the ssis package run manually or scheudle? what security credentials is the job/ssis package running under? If you ran it manually and it worked it could have run with elevated credentials like yours.If you don't have the passion to help people, you have no passion |
 |
|
|
deal11deal1
Starting Member
34 Posts |
Posted - 2011-08-23 : 11:54:31
|
| the ssis packages after the re-start runs manually but by the diffrent team. and the packages run through service account.i am thinking may be there is some process or anti virus scan that runs through the folder where the configuration files are located at and may be that breaks the connection.any one has a better idea.Thanks for the response.with Regards |
|
|
|
|
|
|
connection SSIS congiguration file beaks down