April 13, 2004 at 3:15 pm
I was hoping someone can give me some insight on how 'local packages' work in DTS. Are they run/stored on the PC that you create them or the server itself? One of the developers came to me and said they were trying to debug an ActiveX script task in their DTS job that's stored in the 'local package' area. They were getting file access errors and other problems when they tried to execute that step. Then they came back and said that if they logged onto the server that housed that instance, went back to their desk, and ran the step it now worked. Once they logged out of the server, it stopped working again. To me it shouldn't matter if the server is logged in or not. Would someone please explain why this could be happening?
Thanks,
Jen
April 14, 2004 at 9:21 am
Local packages are stored in SQL Server, not on a client PC. Does the ActiveX task use a file whose file path is designated with a mapped drive rather than a UNC path? If so, the developer running the package step from his PC may not have the same mapping.
Greg
Greg
April 14, 2004 at 10:18 am
Thanks Greg for your response. As far as I know, the file path is UNC, but I'll check the package and see what the mapping is.
Jen
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply