What happens if you try to run it an HOUR later instead of a DAY later?
If the failure happens ALWAYS on the second run time, then you probably have
some sessions left open and that is the reason it is failing.
If it runs fine the second, third, fourth, etc time ON THE SAME DAY, but
ALWAYS fails on DAY TWO, then it is dependant on the date change.
Not having specifics of the process limits responses. Hopefully these
suggestions will get you thinking about narrowing down the reason for the
failure.
Good luck!
--
Todd C
[If this response was helpful, please indicate by clicking the appropriate
answer at the bottom]
[quoted text, click to view] "H Jackson" wrote:
> When I first create a package that contains an Execute Process task which runs a batch file, it runs without any errors. But if I run the same package a day later, it fails with the following error: Error: 0xC0029151 at Extract Discoverer Data, Execute Process Task: In Executing C:\ora\bat\NetDirectMain.bat at "", The process exit code was 1 while the expected was 0.
>
> If I run the batch file form the DOS prompt it runs correctly.
>
> If I create a new package and use an Execute Process task and run the same batch file, it works! But like I said, if I run the new package a day later, well, it fails again :(
>
> Any idea on what the problem could be?
>
> Thanks in advance,
>
> H
>
> From
http://www.developmentnow.com/g/103_0_0_0_0_0/sql-server-dts.htm >
> Posted via DevelopmentNow.com Groups
>
http://www.developmentnow.com
Hi Todd,
Thanks for responding.
After reading you response I do some more testing and this is what did. I opened the same package up again and tried to see if it still didn't work and it didn't, so I deleted the Execute Process task and recreated it again and if still didn't work. I then closed the project and closed SSIS. Then I went back into SSIS and opened the same package again and then placed a new Execute Process Task in the package, this time it worked. Without closing the package and SSIS I re-ran the task again and it worked once again, wow. Then I closed the package and SSIS and re-opened it again, this time I got the same error message :(
As a test I placed Pause statments in my batch file to see what error were being displayed on the DOS screen. The message that it said was "My batch file name is not recognized as an internal or external command, operable program or batch file. I did some research on the error and it said to place quotes around my file name, which I did, but I'm still getting the error.
Oo
_
From
http://www.developmentnow.com/g/103_2007_9_0_0_1017525/SSIS-Execute-Process-Task.htm Posted via DevelopmentNow.com Groups
