June 15, 2009 at 5:56 am
I've created a package that runs amongst other things an Execute Process Task. Running the package in development mode from my own pc it runs through fine apart from the execute process task. I think this has to do with permissions etc which is why I thought I'd leave this testing of the execute process until I'd deployed it on to the server (It fails with error code -532459699 on my development pc). The process should only take a couple of minutes to run but the package looks like (from running a trace) that it hangs when it gets to the process and doesn't do anything. I may need to narrow my sql trace down a bit as I can't find the action that starts up the process in there (not a sql trace expert). Can anyone give me any pointers as to how to work out why this stops processing please?
June 15, 2009 at 6:12 am
It would help if you explained what you are running using the Execute Process Task. This is usually an external program such as a command line zip program or ftps program (two examples from my own environment).
June 15, 2009 at 6:27 am
Sorry, it's an executable program written in vb.net with a command line parameter. I set using a configuration file the location of the exe, the command line parameter and the working directory. Unfortunately, I wasn't the author of this program so I had to work out what the success value was so as to set the FailTaskIfReturnCodeIsNotSuccessValue field. Found on a website a script I could run to ascertain this and the value was 0. Set these accordingly on the execute process task, and on testing it on my development pc I get the exit code listed before, so thought, if the deployed one would fail I would get a similar exit code but I don't know what, if any, there is. The package is written such that, if an error is returned from the process i.e. return code is not 0, then an email is sent. Doesn't do this though.
June 15, 2009 at 6:38 am
Curiously by the way, I've got it to work another way but it's more a cheat than anything. The executable is currently set to run from a windows scheduled task. Putting c:/windows/system32/SCHTASKS.EXE in the executable field of an execute process with /RUN /TN "name of the scheduled task" in an execute process task configuration, the executable works. Shouldn't really have to resort to this though, so would prefer it to work directly from the executable.
June 15, 2009 at 7:02 am
Just also found out that if I run the process from the scheduled task and change the executable name to include the unc path i.e. \\server name\c$\ instead of c:\ which I have placed in the configuration file to make the process more portable, I get an open file - security warning dialog box pop up saying "the publisher could not be verified. Are you sure you wish to run this software?" when referring to schtasks.exe. Could this be a similar issue to my actual executable and the package hangs as it's waiting for someone to click Run?
June 15, 2009 at 7:18 am
Possibly. I'll have to look at our processes at work when I get a chance. We are having SharePoint Development training all this week, so I may be slow on getting this.
IIRC, we had to use local directories when calling the executables not UNC's.
The task that runs our FTPS process has to use all local directories, requiring that we make any necessary changes to that piece while actually remoted in to the server where it runs. A big pain in the ***, but you do what you gotta do.
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply