Showing posts with label sp3. Show all posts
Showing posts with label sp3. Show all posts

Monday, March 19, 2012

dts package runs ok but job fails

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.
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:

dts package runs ok but job fails

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: 450
0
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: 450
0
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/d.../>
ew_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 o
n
> the package name in EM and clicking on "Package Logs..." Goto the last on
e
> on the list (more than likely "Version 1") and expand it. Open the last o
ne
> 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 kno
w
> more, check out this link:
> http://msdn.microsoft.com/library/d...
view_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 t
he
> 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, you
r
> 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 ther
e.
> I'd still suggest turning logging on your package on. This gives much mor
e
> detailed errors than the abbreviated errors given by the Job History viewe
r.
> 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. Grea
t
> development tool. You can always turn it back off and can always delete t
he
> 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 t
o
> just paste my code in there so it will save). Now select it all in notepa
d
> 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 year
s.
> 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:
>

Tuesday, February 14, 2012

dts import agent

Hi group
I want to copy a DB from one Sql Server 2000 SP3 to antother Sql 2000 Sp3.
Im using the DTS Import agent in Enterprise manager. After a few minutes
Ive got an error Message telling me that the copy process failed.
The Log file of the Enterprise Manager is empty. Any Idea what happened? The
Database has a size of 900 Mb, is that a problem?
Is there another solution to copy the db?
Backup and than restore is not possible because the database I want to copy
use replication.
Any ideas?
thx for any help
BjrnBjrn,
I don't follow why backup and restore is prevented in your situation by the
presence of replication (publisher or subscriber should be fine) - can you
explain more.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com|||Hi Paul
I have tried it.
I have build a new DB on my destination Sql Server. Than I have restored the
Databse.
Now I have a dead Databse. Enterprise Manager displays the Icon in grey not
in yellow and behind the Database Name is "loading" written.
I cant delete it, I cant show any properties nothing.
regards
Bjrn
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> schrieb im Newsbeitrag
news:eTNFzlCyGHA.4912@.TK2MSFTNGP03.phx.gbl...
> Bjrn,
> I don't follow why backup and restore is prevented in your situation by
the
> presence of replication (publisher or subscriber should be fine) - can you
> explain more.
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
>|||I think this is not related at all to replication - I'd guess that you have
restored the database using no_recovery.
Try running "restore database yourdbname with recovery".
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com|||Hey Paul
Thx for your help.
I dont know what is different but now I have a working restored DB.
regards
Bjrn
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> schrieb im Newsbeitrag
news:u0Y7eFGyGHA.4092@.TK2MSFTNGP04.phx.gbl...
> I think this is not related at all to replication - I'd guess that you
have
> restored the database using no_recovery.
> Try running "restore database yourdbname with recovery".
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
>
>
>

dts import agent

Hi group
I want to copy a DB from one Sql Server 2000 SP3 to antother Sql 2000 Sp3.
I´m using the DTS Import agent in Enterprise manager. After a few minutes
I´ve got an error Message telling me that the copy process failed.
The Log file of the Enterprise Manager is empty. Any Idea what happened? The
Database has a size of 900 Mb, is that a problem?
Is there another solution to copy the db?
Backup and than restore is not possible because the database I want to copy
use replication.
Any ideas?
thx for any help
BjörnBjörn,
I don't follow why backup and restore is prevented in your situation by the
presence of replication (publisher or subscriber should be fine) - can you
explain more.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com|||Hi Paul
I have tried it.
I have build a new DB on my destination Sql Server. Than I have restored the
Databse.
Now I have a dead Databse. Enterprise Manager displays the Icon in grey not
in yellow and behind the Database Name is "loading" written.
I can´t delete it, I can´t show any properties nothing.
regards
Björn
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> schrieb im Newsbeitrag
news:eTNFzlCyGHA.4912@.TK2MSFTNGP03.phx.gbl...
> Björn,
> I don't follow why backup and restore is prevented in your situation by
the
> presence of replication (publisher or subscriber should be fine) - can you
> explain more.
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
>|||I think this is not related at all to replication - I'd guess that you have
restored the database using no_recovery.
Try running "restore database yourdbname with recovery".
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com|||Hey Paul
Thx for your help.
I don´t know what is different but now I have a working restored DB.
regards
Björn
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> schrieb im Newsbeitrag
news:u0Y7eFGyGHA.4092@.TK2MSFTNGP04.phx.gbl...
> I think this is not related at all to replication - I'd guess that you
have
> restored the database using no_recovery.
> Try running "restore database yourdbname with recovery".
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
>
>
>

DTS Horror in SP3, SQL Server 2000

Has anyone found problems with transforming data from a SQL (Server) source to flat files, only starting with SP3?

We've got a problem which we thought was due to editing SP1 created packages with SP3 applied to the client, but we've narrowed it down to it being SP3 specific.

Basically we have done the following:
1. Create a new DTS package on a local server (Enterprise Manager - Data Transformation Services, Local Packages, right click, New Package)
2. Create a source connection, setting the Data Source to MS OLEDB Provider for SQL Server. Leave the server as local, and select a database. NT Authentication was used for the sample. Set it to a small table on the same SQL Server box as the DTS package is being created on. Use the whole table as the source, don't specify a query.
3. Create a destination file on the local box, and set its location to c:\testDTS.txt. Leave the file format settings at their default.
4. Click on Task menu... Transform Data Task... and select Source Connection and Destination Connection.
5. Double click on the Data Transformation task to set the column mappings.
6. Leave the source settings at their default (select a different table if the first one is too big to export)
7. Click on Destination tab and Click on the Populate from Source button, followed by the Execute button.
8. Click on the Define Columns button
9. After a few seconds, an MMC error is displayed, which is repeatable every time this procedure is followed.

Further investigation has shown that SP1 packages do not seem to exhibit this behaviour, unless they are being edited by a client that has SP3 applied.

The database software is SQL Server 2000 Developer Edition with SP1 applied.
The OS is Windows XP Professional with SP1.

Any feedback from others with this fault would be much appreciated, but I can't believe given the simplicity of the test that someone has not already encountered this since the release of SP3. I've built literally hundreds of DTS packages, but have only encountered this problem with SP3.A fix for this problem has been found. Although slightly different to the one we experienced, the problem is described at :
http://support.microsoft.com/default.aspx?scid=kb;en-us;814113

...and the hotfix for it can be downloaded at : http://www.microsoft.com/downloads/details.aspx?familyid=9814AE9D-BD44-40C5-ADD3-B8C99618E68D&displaylang=en

Hope this helps anyone else out there who has expereienced the same issues with the DTS GUI.

(With thanks to Paul Hiom at RHI/CSC in Birmingham for help with this).:)