Showing posts with label causes. Show all posts
Showing posts with label causes. Show all posts

Sunday, March 25, 2012

ActiveX Script Running DTS Causes Error

Hello All,

I have an ActiveX script that runs DTS pachkages. In the event that a package fails I want to display the error message. I found the following code (in bold) for doing this but I keep getting an error message as follows.

Type mismatch 'oSoStep.GetExecutionErrorInfo'

All help appreciated.

Thanks, Gary

Could you post your code?
Jason
|||For Each oStep In oPkg.Steps
If oStep.ExecutionStatus = DTSStepExecStat_Completed Then
If oStep.ExecutionResult = DTSStepExecResult_Failure Then
oStep.GetExecutionErrorInfo lErrNum, sSource, sDescr
msgbox(sDescr)
End If
End If
Next

Saturday, February 25, 2012

account change causes DTS package jobs fail

DTS packages and jobs are created as domain administrator accounts
"\\ourdomain\administrator". For some reasons (separate database
account from network account), we switched to new domain administrator
account called "\\ourdomain\sqladm" as SQL Server, service startup
account. Some DTS jobs stop running. In DTSs, server connection uses
NT default acccount. Does anyone know what is going on here? Do I have
to change the DTS owmers to "\\ourdomain\sqladm"? or I have to change
all server connection in DTS packages as SQL account connection?
Thanks in advance.You should not need to change the ownereship of the DTS package. What is
the startup account for SQL Server Agent. It controls the execution of
jobs. Log in as the SQL Server Agent startup account on the server itself
and run the DTS packages that fail form Enterprise Manager. If they fail
there too, it could be a permissions problem with the account.
Rand
This posting is provided "as is" with no warranties and confers no rights.

account change causes DTS package jobs fail

DTS packages and jobs are created as domain administrator accounts
"\\ourdomain\administrator". For some reasons (separate database
account from network account), we switched to new domain administrator
account called "\\ourdomain\sqladm" as SQL Server, service startup
account. Some DTS jobs stop running. In DTSs, server connection uses
NT default acccount. Does anyone know what is going on here? Do I have
to change the DTS owmers to "\\ourdomain\sqladm"? or I have to change
all server connection in DTS packages as SQL account connection?
Thanks in advance.
You should not need to change the ownereship of the DTS package. What is
the startup account for SQL Server Agent. It controls the execution of
jobs. Log in as the SQL Server Agent startup account on the server itself
and run the DTS packages that fail form Enterprise Manager. If they fail
there too, it could be a permissions problem with the account.
Rand
This posting is provided "as is" with no warranties and confers no rights.

account change causes DTS package jobs fail

DTS packages and jobs are created as domain administrator accounts
"\\ourdomain\administrator". For some reasons (separate database
account from network account), we switched to new domain administrator
account called "\\ourdomain\sqladm" as SQL Server, service startup
account. Some DTS jobs stop running. In DTSs, server connection uses
NT default acccount. Does anyone know what is going on here? Do I have
to change the DTS owmers to "\\ourdomain\sqladm"? or I have to change
all server connection in DTS packages as SQL account connection?
Thanks in advance.You should not need to change the ownereship of the DTS package. What is
the startup account for SQL Server Agent. It controls the execution of
jobs. Log in as the SQL Server Agent startup account on the server itself
and run the DTS packages that fail form Enterprise Manager. If they fail
there too, it could be a permissions problem with the account.
Rand
This posting is provided "as is" with no warranties and confers no rights.