July 7, 2004 at 1:55 am
I have a strange problem with a Scheduled Package and need some serious help.
I have a DTS Package that works just fine. I can start it with Execute Package and everything works just fine.
I create a Job via "Scheduled Package".
When i try to Start my Job it fails with following message.
Executed as user: DOMAIN\sqladmin. ...ng...
DTSRun OnStart: DTSStep_DTSTransferObjectsTask_1
DTSRun OnProgress: DTSStep_DTSTransferObjectsTask_1; Scripting objects for Transfer; PercentComplete = 0;
ProgressCount = 0 DTSRun OnError: DTSStep_DTSTransferObjectsTask_1, Error = -2147024891 (80070005)
Error string: Access is denied. Error source: Microsoft Data Transformation Services (DTS)
Package Help file: sqldts80.hlp Help context: 1100
Error Detail Records: Error: -2147024891 (80070005); Provider Error: 0 (0)
Error string: Access is denied. Error source: Microsoft Data Transformation Services (DTS) Package
Help file: sqldts80.hlp Help context: 1100 Error: -2147024891 (80070005); Provider Error: 0 (0)
Error string: Access is denied. Error source: Microsoft Data Transformation Services (DTS) Package
Help file: sqldts80.hlp Help context: 5700 Error: -2147467259 (800040.
The step failed.
July 7, 2004 at 5:06 am
Check the following:
1. Make sure the account that the sql server agent is running under has sufficient priveleges to perform the dts task.
2. Make sure any paths to files are through a mapped drive rather than the full unc path.
3. Run dcomcnfg.exe and add the SQL Service account to Default Access Permissions under Default Security tab.
July 7, 2004 at 5:20 am
July 7, 2004 at 5:28 am
Can you please let us know what the step is supposed to do so we can help you diagnose the problem?
Good Hunting!
AJ Ahrens
webmaster@kritter.net
July 7, 2004 at 6:20 am
July 7, 2004 at 7:26 am
The error message is screaming permission problems.
Check that the account that sql server is running under can select from table A and insert into table B.
If this works, divide the package into two and see whether either or both fall over and post back.
July 7, 2004 at 7:59 am
It is up and running.
The problem as I understand was that SQL Server and Agent was running with an account (sqladmin) instead of localsystem. Even thow sqladmin was admin and owner with rights to do more or less everything on all servers, the permission problem occured.
Thanks for input and info.
July 7, 2004 at 8:16 am
Glad it helped. I have had the same sort of error messages for a couple of dts jobs in the last month all down to conflicting permissions.
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply