Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
elomon
Starting Member
37 Posts |
Posted - 2003-11-19 : 10:46:33
|
| I have a long running DTS package that consists of several ActiveX tasks. The job runs several times a day and fails once a day, every day. I am having trouble getting access to the error that is generated. The job history is generic, saying "Error string: ActiveX Scripting encountered a Run Time Error during the execution of the script. " There is no mention what that Run Time error is, just that one occurred.I have tried logging the execution to a text file but that only shows the same info: an error occurred but no mention of what the error is.I have also turned on logging of the package to SQL Server. In the msdb db, I've looked at sysdtspackagelog, sysdtssteplog and sysdtstasklog. The tables show an error occurred but nowhere does it show the actual error.Any ideas on how to trap the exact error that is being generated? I thought and right-click executing the package, but the package runs for close to two hours. |
|
|
Stoad
Freaky Yak Linguist
1983 Posts |
Posted - 2003-11-19 : 12:26:50
|
| sub main()on error resume next.... .... ....if err.Number<>0 thenSet fso = CreateObject("Scripting.FileSystemObject")Set tso = fso.OpenTextFile("d:\my.txt", 8)tso.WriteLine Err.Descriptiontso.CloseSet tso = NothingSet fso = Nothingend ifend sub |
 |
|
|
elomon
Starting Member
37 Posts |
Posted - 2003-11-19 : 12:35:15
|
| Right! Thanks. |
 |
|
|
|
|
|