I assume you're talking about the "owner" of the job, right? If so, then I did give it a domain account.
"DOMAIN/USER"
Thanks!
Main Topics
Browse All TopicsOne of my clients has a scheduled job that runs a DTS package every day. Recently the job began failing. I set up error logging on the DTS package, and have included the error below.
I have tried running the DTS package manually, and it worked fine. I also manually started the SQL job, and it ran fine. It only fails when the job runs automatically at it's scheduled time.
The DTS package exports a file to a folder on a mapped network drive. The connectivity between the local computer and the mapped network drive seems to by fine.
Around the same time that this started failing the in-house IT guy said that he removed some old/unused users from the network. I noticed that one of those users was the owner of the DTS package and the SQL job. I tried changing the owner to an admin user that I knew existed, but it still failed. I also tried giving the "everyone" group full control permissions on the export folder.
Here's the error message recorded in the DTS log file... Any help would be greatly appreciated. Thanks!
**************************
The execution of the following DTS Package succeeded:
Package Name: DataQuickExport
Package Description: Compile and EMail DataQuick Request
Package ID: XXXXXX
Package Version: XXXXXX
Package Execution Lineage: XXXXXX
Executed On: XXXXXX
Executed By: XXXXXX
Execution Started: 8/14/2008 2:16:00 PM
Execution Completed: 8/14/2008 2:16:13 PM
Total Execution Time: 13.047 seconds
Package Steps execution information:
Step 'DTSStep_DTSDataPumpTask_1
Step Error Source: Microsoft Data Transformation Services Flat File Rowset Provider
Step Error Description:Error opening datafile: The system detected a possible attempt to compromise security. Please ensure that you can contact the server that authenticated you.
Step Error code: 80004005
Step Error Help File:DTSFFile.hlp
Step Error Help Context ID:0
Step Execution Started: 8/14/2008 2:16:00 PM
Step Execution Completed: 8/14/2008 2:16:13 PM
Total Step Execution Time: 13.047 seconds
Progress count in Step: 0
Step 'DTSStep_DTSSendMailTask_1
Step 'DTSStep_DTSActiveScriptTa
**************************
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
"The DTS package exports a file to a folder on a mapped network drive."
I was actually wrong when I said that it wrote to a mapped network drive. It's NOT using a mapped drive. It's actually using a path like this:
\\COMPUTERNAME\folder\fold
Is that ok to use?
Also, something else to keep in mind... this DTS package has been working for several years. There have been no changes to the package, and it just stopped working earlier this week.
We finally got it to work. It turned out that there was already a user logged into that machine, and when the SQL Agent tried to log in as a different user to run the job, the server wouldn't allow it.
So, we just set the SQL Agent to use the same user that was already logged in, and everything worked fine after that.
Thanks for your help!
If someone has a better explanation, then I'd love to hear it.
I just know that the logged in user was different than the SQL agent user, and when we changed the SQL agent user to be the same as the logged in user, everything started working again.
It was actually one of our techs that fixed it, so I just gave the explanation that he gave me.
>>I just know that the logged in user was different than the SQL agent user, and when we changed the SQL agent user to be the same as the logged in user, everything started working again.<<
You have answered your own question: The original SQL Server Agent service startup account did not have the correct permissions to all the reources it needed. When you changed the account to one that did (as we have been telling you from the start) all was well.
Business Accounts
Answer for Membership
by: zwseemmPosted on 2008-08-14 at 15:34:10ID: 22234886
Make sure the job start\s with a domain account and not a local account.