Executed as user: COLUSSUS\sqlserveragent. ...DTSStep_DTSActiveScriptTask_1
DTSRun OnError: DTSStep_DTSActiveScriptTask_1, Error = -2147220482
(800403FE) Error string: Error Code: 0 Error Source= Microsoft
VBScript runtime error Error Description: Permission denied: 'CreateObject'
Error on Line 76 Error source: Microsoft Data Transformation
Services (DTS) Package Help file: sqldts80.hlp Help context: 4500
Error Detail Records: Error: -2147220482 (800403FE); Provider
Error: 0 (0) Error string: Error Code: 0 Error Source= Microsoft
VBScript runtime error Error Description: Permission denied: 'CreateObject'
Error on Line 76 Error source: Microsoft Data Transformation
Services (DTS) Package Help file: sqldts80.hlp Help context: 4500
DTSRun OnFinish: DTSStep_DTSActiveScriptTask_1 Error: -2147220440
(80040428); Provider Error: 0 (0) Error string: Package failed
becau... Process Exit Code 1. The step failed.
The line in the code is: set fsObj =
CreateObject("Scripting.FilesystemObject")
The user "COLUSSUS\sqlserveragent" is in the admin group but I even gave
that specific user security rights to read and execute to the entire drive
but I still get the error.
Any ideas?
Thanks,
Dan D.
If I were you, I'd install SP4 first. I had a similar problem. Tasks
worked, ran, but at the very end of package execution it just dropped off
the end of the package code and crashed. SP4 fixed my problem. You might
have a different problem and you can find more by opening your package and
going into "Package Properties." Goto the "Logging" tab and turn on
logging. Run the task as normal and then open the log by right clicking on
the package name in EM and clicking on "Package Logs..." Goto the last one
on the list (more than likely "Version 1") and expand it. Open the last one
listed and see if any particular task failed with an error. If no tasks
actually failed, then SP4 is probably the only thing that will fix it. If a
task did fail, read the error and either post it here or fix it yourself.
Scott
"Dan D." <DanD@.discussions.microsoft.com> wrote in message
news:AC07DDED-9AF4-481B-A896-4417800A9E4D@.microsoft.com...
> Using SS 2000 SP3. I get this error message:
> Executed as user: COLUSSUS\sqlserveragent.
> ...DTSStep_DTSActiveScriptTask_1
> DTSRun OnError: DTSStep_DTSActiveScriptTask_1, Error = -2147220482
> (800403FE) Error string: Error Code: 0 Error Source= Microsoft
> VBScript runtime error Error Description: Permission denied:
> 'CreateObject'
> Error on Line 76 Error source: Microsoft Data Transformation
> Services (DTS) Package Help file: sqldts80.hlp Help context:
> 4500
> Error Detail Records: Error: -2147220482 (800403FE); Provider
> Error: 0 (0) Error string: Error Code: 0 Error Source= Microsoft
> VBScript runtime error Error Description: Permission denied:
> 'CreateObject'
> Error on Line 76 Error source: Microsoft Data Transformation
> Services (DTS) Package Help file: sqldts80.hlp Help context:
> 4500
> DTSRun OnFinish: DTSStep_DTSActiveScriptTask_1
> Error: -2147220440
> (80040428); Provider Error: 0 (0) Error string: Package failed
> becau... Process Exit Code 1. The step failed.
> The line in the code is: set fsObj =
> CreateObject("Scripting.FilesystemObject")
> The user "COLUSSUS\sqlserveragent" is in the admin group but I even gave
> that specific user security rights to read and execute to the entire drive
> but I still get the error.
> Any ideas?
> Thanks,
> --
> Dan D.
|||Dan:
BTW, your sqlserveragent has way too many privaledges. If you want to know
more, check out this link:
http://msdn.microsoft.com/library/de...rview_6k1f.asp
Scott
"Dan D." <DanD@.discussions.microsoft.com> wrote in message
news:AC07DDED-9AF4-481B-A896-4417800A9E4D@.microsoft.com...
> Using SS 2000 SP3. I get this error message:
> Executed as user: COLUSSUS\sqlserveragent.
> ...DTSStep_DTSActiveScriptTask_1
> DTSRun OnError: DTSStep_DTSActiveScriptTask_1, Error = -2147220482
> (800403FE) Error string: Error Code: 0 Error Source= Microsoft
> VBScript runtime error Error Description: Permission denied:
> 'CreateObject'
> Error on Line 76 Error source: Microsoft Data Transformation
> Services (DTS) Package Help file: sqldts80.hlp Help context:
> 4500
> Error Detail Records: Error: -2147220482 (800403FE); Provider
> Error: 0 (0) Error string: Error Code: 0 Error Source= Microsoft
> VBScript runtime error Error Description: Permission denied:
> 'CreateObject'
> Error on Line 76 Error source: Microsoft Data Transformation
> Services (DTS) Package Help file: sqldts80.hlp Help context:
> 4500
> DTSRun OnFinish: DTSStep_DTSActiveScriptTask_1
> Error: -2147220440
> (80040428); Provider Error: 0 (0) Error string: Package failed
> becau... Process Exit Code 1. The step failed.
> The line in the code is: set fsObj =
> CreateObject("Scripting.FilesystemObject")
> The user "COLUSSUS\sqlserveragent" is in the admin group but I even gave
> that specific user security rights to read and execute to the entire drive
> but I still get the error.
> Any ideas?
> Thanks,
> --
> Dan D.
|||There's only one step in the package. I know what and where the error is I
just don't know how to fix it.
Dan D.
"Wm. Scott Miller" wrote:
> If I were you, I'd install SP4 first. I had a similar problem. Tasks
> worked, ran, but at the very end of package execution it just dropped off
> the end of the package code and crashed. SP4 fixed my problem. You might
> have a different problem and you can find more by opening your package and
> going into "Package Properties." Goto the "Logging" tab and turn on
> logging. Run the task as normal and then open the log by right clicking on
> the package name in EM and clicking on "Package Logs..." Goto the last one
> on the list (more than likely "Version 1") and expand it. Open the last one
> listed and see if any particular task failed with an error. If no tasks
> actually failed, then SP4 is probably the only thing that will fix it. If a
> task did fail, read the error and either post it here or fix it yourself.
> Scott
>
> "Dan D." <DanD@.discussions.microsoft.com> wrote in message
> news:AC07DDED-9AF4-481B-A896-4417800A9E4D@.microsoft.com...
>
>
|||I realize this but since the problem is permissions I was trying to get the
job to run and then worry about cutting back permissions.
Thanks,
Dan D.
"Wm. Scott Miller" wrote:
> Dan:
> BTW, your sqlserveragent has way too many privaledges. If you want to know
> more, check out this link:
> http://msdn.microsoft.com/library/de...rview_6k1f.asp
> Scott
> "Dan D." <DanD@.discussions.microsoft.com> wrote in message
> news:AC07DDED-9AF4-481B-A896-4417800A9E4D@.microsoft.com...
>
>
|||OK. Create a new package. Put an ActiveX script object in it and paste the
following code into it:
--Begin Copy--
'************************************************* *********************
' Visual Basic ActiveX Script
'************************************************* ***********************
Option Explicit
Function Main()
Dim oFileSystem
Set oFileSystem = CreateObject("Scripting.FileSystemObject")
Set oFileSystem = Nothing
Main = DTSTaskExecResult_Success
End Function
--End Copy--
Now try to run this package as you did the first. Did it run? If so, your
76th line of code is not the problem and it is a problem somewhere else in
the code. If it fails, try to get it to run using various computers (your
desktop, server, etc.) and user ids (Administrator, your id, Agent id, etc).
Let me know how it goes. You can also open up the registry and search for
the phrase "Scripting.FileSystemObject" on the server to see if it is there.
I'd still suggest turning logging on your package on. This gives much more
detailed errors than the abbreviated errors given by the Job History viewer.
I use it on most packages that I schedule as jobs. That way I can get
detailed errors and exactly where in the package a failure occurred. Great
development tool. You can always turn it back off and can always delete the
logs if you wish.
Scott
"Dan D." <DanD@.discussions.microsoft.com> wrote in message
news:9BBEF554-FC57-4AA0-89A8-1A3CB520BF36@.microsoft.com...[vbcol=seagreen]
> There's only one step in the package. I know what and where the error is I
> just don't know how to fix it.
> --
> Dan D.
>
> "Wm. Scott Miller" wrote:
|||That was a good suggestion. You were right about the error message being
misleading. The script you sent ran fine.
I have logging turned on for all of our packages but the message is
essentially the same. Here it is:
Step Error Source: Microsoft Data Transformation Services (DTS) Package
Step Error Description:Error Code: 0
Error Source= Microsoft VBScript runtime error
Error Description: Permission denied: 'CreateObject'
Error on Line 76
Step Error code: 800403FE
Step Error Help File:sqldts80.hlp
Step Error Help Context ID:4500
I'll get the programmer to build the code one piece at a time so we can find
out where the error is really happening.
Thanks for your help.
Dan D.
"Wm. Scott Miller" wrote:
> OK. Create a new package. Put an ActiveX script object in it and paste the
> following code into it:
> --Begin Copy--
> '************************************************* *********************
> ' Visual Basic ActiveX Script
> '************************************************* ***********************
> Option Explicit
> Function Main()
> Dim oFileSystem
> Set oFileSystem = CreateObject("Scripting.FileSystemObject")
> Set oFileSystem = Nothing
> Main = DTSTaskExecResult_Success
> End Function
> --End Copy--
> Now try to run this package as you did the first. Did it run? If so, your
> 76th line of code is not the problem and it is a problem somewhere else in
> the code. If it fails, try to get it to run using various computers (your
> desktop, server, etc.) and user ids (Administrator, your id, Agent id, etc).
> Let me know how it goes. You can also open up the registry and search for
> the phrase "Scripting.FileSystemObject" on the server to see if it is there.
> I'd still suggest turning logging on your package on. This gives much more
> detailed errors than the abbreviated errors given by the Job History viewer.
> I use it on most packages that I schedule as jobs. That way I can get
> detailed errors and exactly where in the package a failure occurred. Great
> development tool. You can always turn it back off and can always delete the
> logs if you wish.
> Scott
> "Dan D." <DanD@.discussions.microsoft.com> wrote in message
> news:9BBEF554-FC57-4AA0-89A8-1A3CB520BF36@.microsoft.com...
>
>
|||I know this sounds crazy, but humor me. Cut your ActiveX script in its
entirety to notepad. Save your package without anything in it (may have to
just paste my code in there so it will save). Now select it all in notepad
and copy and paste it back. Does it run? If so, somehow in writing, you
got a special character embeded in the ActiveX script task. If not, it is
an actual coding error. I've had this happen twice to me so far in 5 years.
Scott
"Dan D." <DanD@.discussions.microsoft.com> wrote in message
news:9C7F17A5-3A3E-4465-9A4E-B66B8D215B2D@.microsoft.com...[vbcol=seagreen]
> That was a good suggestion. You were right about the error message being
> misleading. The script you sent ran fine.
> I have logging turned on for all of our packages but the message is
> essentially the same. Here it is:
> Step Error Source: Microsoft Data Transformation Services (DTS) Package
> Step Error Description:Error Code: 0
> Error Source= Microsoft VBScript runtime error
> Error Description: Permission denied: 'CreateObject'
> Error on Line 76
> Step Error code: 800403FE
> Step Error Help File:sqldts80.hlp
> Step Error Help Context ID:4500
> I'll get the programmer to build the code one piece at a time so we can
> find
> out where the error is really happening.
> Thanks for your help.
> --
> Dan D.
>
> "Wm. Scott Miller" wrote:
|||Good try but no cigar.
Same error.Dan D.
"Wm. Scott Miller" wrote:
> I know this sounds crazy, but humor me. Cut your ActiveX script in its
> entirety to notepad. Save your package without anything in it (may have to
> just paste my code in there so it will save). Now select it all in notepad
> and copy and paste it back. Does it run? If so, somehow in writing, you
> got a special character embeded in the ActiveX script task. If not, it is
> an actual coding error. I've had this happen twice to me so far in 5 years.
> Scott
> "Dan D." <DanD@.discussions.microsoft.com> wrote in message
> news:9C7F17A5-3A3E-4465-9A4E-B66B8D215B2D@.microsoft.com...
>
>
|||Too bad. One should always try the easy fix first.... :-) Only other
suggestion is the cut and paste line by line or block by block and see which
paste causes the problem then go from there. That will at least give you a
clue where to look.
Good luck on fixing the task,
Scott
"Dan D." <DanD@.discussions.microsoft.com> wrote in message
news:328C5286-92B5-4290-9C3E-FE9FD45974D6@.microsoft.com...[vbcol=seagreen]
> Good try but no cigar.
Same error.> --
> Dan D.
>
> "Wm. Scott Miller" wrote:
No comments:
Post a Comment