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.

 All Forums
 SQL Server 2008 Forums
 SSIS and Import/Export (2008)
 Weird Error at Integration Services Project

Author  Topic 

shacky
Starting Member

16 Posts

Posted - 2011-01-18 : 04:10:33
Hi Team,

I am currently facing this weird error with an integration Services Project. i have created 2 packages, each has a transfer sql server object task.

Before i applied the service packs, I was able to transfer data from sql 2008 to sql 2000. However, after i applied the service pack, I started to get "unable to connect to server <Servername>" on one of the packages.

The weird problem i am facing is, one package worked while the other does not work. Both packages are identical, the only difference is that i am transferring data to different databases.

Package 1[Working] originally faced the same problem after the service pack installation but the issue was resolved after doing a restart as the local sql server did not even appear in the server list. Currently, Package 1 is able to transfer data to the other server.

Package 2[Not Working] is using the same connection method as Package 1 but i always get the above error message on the destination server.

Can someone help me out with this weird problem? I have tried restarting both pc's but the error is still there. Thanks.

Lumbago
Norsk Yak Master

3271 Posts

Posted - 2011-01-18 : 05:07:22
Have you tried to open the SSIS package in bids and verified that the connection is working?

- Lumbago

My blog (yes, I have a blog now! just not that much content yet)
-> www.thefirstsql.com
Go to Top of Page

shacky
Starting Member

16 Posts

Posted - 2011-01-23 : 23:35:24
Hi Lumbago,

Thanks for your reply. The connection has been used by other packages and there were no problems so far. I found out that the cause of the problem is due to security on the package. If i set it to DontSaveSensitive, I will get that error mentioned earlier. But when i set it back to EncryptSensitiveWithUserKey, it worked again.
Go to Top of Page
   

- Advertisement -