July 12, 2004 at 8:15 pm
Hi All,
I have a DTS package which suddenly started to fail! The DTS package contains initial steps which delete a mapped drive and then remap it. From what I can see (via windows explorer) this mapping occurs, but the job does not proceed to the next step because the Process Return Code is 0, instead of the specified 2.
Any ideas would be much appreciated!
Thanks
Terry
July 15, 2004 at 8:00 am
This was removed by the editor as SPAM
July 20, 2004 at 9:22 pm
To extend this further....The DTS contains three 'Execute Process Tasks'. The first one performs the task 'net use j: /d'(to ensure that the J drive is not currently mapped). This is followed by a 'net use j: \\Server\folder'. The DTS then goes of and does some processing with the outcome being an output file on the mapped J drive. The final task in this DTS is the third 'Execute Process Task' which deletes the mapped drive.
As stated previously, the problem seems to be that the incorrect status code is being returned (0 instead of 2). So I did a bit of testing and modified the status code back to 0 for each of the Execute process tasks. When I then run the job by manually executing it I received a dos prompt with the message 'There are open files and/or incomplete directory searches on the connection to J:. Is it ok to continue disconnecting and force them closed<Y:N>:' If I type in 'Y' then the DTS job proceeds as normal. But if I try and run the task again then I get the opposite message to my original post ie Return code of 2 does not match specified code of 0.
Any suggestions?
Thanks
October 15, 2004 at 9:30 am
Hi,
First time participation!
I have a similar problem.
For what I was able to find, this may have to do with the fact that the user running the DTS doesn't have permissions to access the file although the user who created the DTS is able to run it.
Try setting the return code of the task to the value DTS is expecting.
Cheers
NAbreu
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply