dbTalk Databases Forums  

DTS Package fails when run as a job (not usual permissions issue)

microsoft.public.sqlserver.dts microsoft.public.sqlserver.dts


Discuss DTS Package fails when run as a job (not usual permissions issue) in the microsoft.public.sqlserver.dts forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
Aardvark
 
Posts: n/a

Default DTS Package fails when run as a job (not usual permissions issue) - 04-08-2005 , 03:50 PM






Hello,

At first this situation is going to sound like other problems posted,
but please stick with me...

I have a DTS package which runs fine when I run it from EM. However,
when I run it as a job it fails on the one and only ActiveX script in
the package.

The ActiveX script shouldn't be relying on any kind of user security,
so I don't think that this is the usual issue of a change in security
context (at least not in an obvious way). The ActiveX task has its
workflow driven by another ActiveX script, which is where the error is
occurring. Here is a simplified version of that code:

-----------------------------------------------------
Const SET_GLOBALS = "DTSStep_DTSDynamicPropertiesTask_1"

Function Main()
Dim oPkg

Set oPkg = DTSGlobalVariables.Parent

If (oPkg.Steps(SET_GLOBALS).ExecutionResult =
DTSStepExecResult_Failure And _
oPkg.Steps(SET_GLOBALS).ExecutionStatus =
DTSStepExecStat_Completed) Then
Main = DTSStepScriptResult_ExecuteTask
Else
Main = DTSStepScriptResult_RetryLater
End If

Set oPkg = Nothing
End Function
-----------------------------------------------------

The IF statement is actually much more complex and uses the results of
many tasks in the package, but this should give you the general idea.
The workflow script does nothing else. The ActiveX script sets some
global variables based on step statuses, but that's it. Since the job
is failing so quickly, I'm fairly certain that it is never trying to
run that code and that the error is in the workflow script.

I also had the DBA (in the sysadmin role) for this server take
ownership of my job and try to run it, but that didn't work either.

Finally, even though I have a value filled in for the error log file,
the file is never created when I get this error. If I run the package
manually and get a different error, the error log file is created
without a problem.

The error that I see in the job is:
"Executed as user: langroup\srv_mssql_pxy. The step did not generate
any output. Process Exit Code -1073741819. The step failed."

Sometimes it will include a longer error description that mentions the
ActiveX script with the same process exit code.

Thanks for any help that you can give me on this one!

Thanks,
-Tom.


Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.