>On Oct 1, 2008, at 9:02 AM, Bert van Oort wrote:
>
>> I'm trying to write a program that calls the svn client to do a
>> checkout, using the ExecuteProcess win32 api call. This program works
>> fine when executed locally but when executed from the scheduler van
>> Business Objects 6.5 the svn execution fails with exit code 128 and
>> output " (8)" (without the double quotes, ofc). With verbose off the
>> svn output is empty.
>
>I suspect you're not capturing the stderr output in your script, only
>the stdout output. Look at stderr to see what error is occurring.
First, thanks for your suggestion. The program captures the output via
pipes and used the DuplicateHandle winapi function to create a handle
from StdOut for StdErr. So I suppose both child handles write to the
same pipe. To test this I added " 2>&1" to the commandline to redirect
stderr output to stdout, but the output did not change.
To test if another error did change the output I changed the password on
the commandline and the exitcode did not change. I tried to execute a
batch file with "C:\Windows\System32\cmd.exe /C C:\test.bat" and it
failed too with exitcode 128. So it doesn't have anything to do with the
svn client.
Then I found this article:
http://support.microsoft.com/default.aspx?scid=kb;en-us;184802
Seems a security issue. This now seems logical to me as it runs
correctly stand alone but fails from the scheduler wich is a kind of
service. Maybe the program is started from the service with limited
rights and the console I try to start with CreateProcess from the
program inherits those limited rights and therefore fails.
Back to the drawing board :-)
Kind regards,
Bert van Oort
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-10-03 00:45:18 CEST