I have VC installed on a Windows 2003 domain member server. On the same server, I have SQL Server 2005 Integration Services with the Native SQL Client installed. I have 2 locally stored DTSX packages (file system) that I want to execute passing trusted domain credentials. I can run both packages using the local SQL Server Management Console logged on with Windows Integrated security no problem. When I try to run them in VC I get this...?

The package source is a flat file.
The package destination is a different serverf that hosts the DB.

I know this is simple authentication stuff but don't know what to try next.

Note.....User should read AB\SYSSQL...... ABSQL04$ is machine name of the server.

The SSIS Execution failed

Number of warnings: 0
Number of errors: 4
Error (0):SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80040E4D.
An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80040E4D Description: "Login failed for user 'AB\ABSQL04$'.".

Error (1):Failed to acquire connection "DestinationConnectionOLEDB". Connection may not be configured correctly or you may not have the right permissions on this connection.

Error (2):SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80040E4D.
An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80040E4D Description: "Login failed for user 'AB\ABSQL04$'.".

Error (3):Failed to acquire connection "DestinationConnectionOLEDB". Connection may not be configured correctly or you may not have the right permissions on this connection.

From, GetErrorValues (0)

Thanks

I assume that you use a Credential on the SSIS Task that matches the user you are logged in as?

---

Found some further information on this page: http://support.microsoft.com/kb/918760 

---

yes.....logged on to server as domain account AB\SYSSQL...When I fire up the SQL Server Management Console(connect to local integration services)..I use the same credentials and can run the SSIS package interactively with no problem.

I am talking about the Credential in VisualCron, the first select box in the SSIS Task. It should be set to the same user as the one you are logged in as. You need to do this AND set the the other properties.

---

It is...same account...what other properties are you referring to...?

Thanks for the image. Just a quick test. What if you:

1. stop the VisualCron service
2. Change the user name of the service to that local account that you were logged in as
3. start the service
4. edit the task and select "No Credential"
5. Run the Task again

---

I'll try that...but I was able to sucessfully send a query through VC to a DB on the SQL Server as well as run a job from the MSDB using the SQL TASK......may be tomorrow I'll work in the SSIS more...

By running the service under that account, I was able to run the ssis package......I would rather not have to do that.....but for now that will work.
Thanks

Then it might be as simple as you have entered the wrong password - hence the "Login failed" message. Can you verify that you can use the Credential for access a UNC path on that Server? Please test this:

1. change back to service running as SYSTEM
2. add a text file on AB server
3. Create a file read task that tries to read this file with this Credential

If file is succesfully read then we will investigate further otherwise it is a problem with username/password.

---

I made sure I re-entered them....BTW it is a Domain Admin account with FULL rights to back-end SQL abd the server running Integration Services. I do get this when package executes....mean anything to you...?

CancelEvent = 2640
ContainerStartTime = 3/4/2009 1:26:50 PM
CreationDate = 12/30/2008 1:04:03 PM
CreatorComputerName = JTIPP-VISTAPC
CreatorName = AB\jtipp
ExecutionInstanceGUID = {2E90FBEA-6DA6-4D69-BA3C-0A9EC11456A3}
InteractiveMode = False
LocaleID = 1033
MachineName = ABSQL04
OfflineMode = False
PackageID = {2EC10095-E70F-4805-9196-8442179F10E2}
PackageName = SourceFile
StartTime = 3/4/2009 1:26:50 PM
UserName = AB\syssql
VersionBuild = 3
VersionComments =
VersionGUID = {B2A504AE-3F7F-4342-A143-350FBCBCBD66}
VersionMajor = 1
VersionMinor = 0

No, it does not mean anything special to me.

It would still be interesting if you could test the File Read Task.

---