Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Can't call an SSIS package from a Service

Status
Not open for further replies.

DCML

Programmer
Jan 5, 2009
1
GB
Can anyone help me?

I have a service set up to run overnight. This service is an executable, compiled from a C# source, which is attempting to call an SSIS package.

This package is attempting to read in data from three different databases on other servers and import that data into a third database held locally. These databases require SQL Server authentication to access.

When I run the SSIS package directly, it works fine. But when I set it up to run from the service if fails to connect to the first database.

I get the following error message:
SSIS Package SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80004005.
An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80004005 Description: "Login failed for user ''. The user is not associated with a trusted SQL Server connection."

I'm guessing it's some kind of permissions issue, but I've tried various things and nothing works. Does snyone out there have any suggestions?
 
It's probably your ProtectionLevel setting on your package. My guess is that you have it set to one of the EncryptWithUserKey settings. And your service is running under a different account. You could either choose not the save the sensitive data and use a configuration file to store the passwords in clear text, or you can encrypt the sensitive data with a password. I haven't yet used the ServerStorage option for ProtectionLevel, although someone else may be able to offer some insight on that.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top