No, the process never starts. We did a new release from another PC (which
we expect to be identical) and the process does not get stuck and
everything works as expected. doh :(
On Sun, Sep 8, 2013 at 9:25 AM, Wallace Turner <wallace.tur...@gmail.com>wrote:
> is the process you're starting still running ie can u see it in task
> manager
>
>
> On Sat, Sep 7, 2013 at 4:59 PM, Corneliu I. Tusnea <corne...@acorns.com.au
> > wrote:
>
>> Hi,
>>
>> I have a website that is running some background tasks as separate
>> executables with Process.Start.
>> This has been working like this for a long time. However recently on one
>> of the servers this stopped working and the Process.Start call blocks
>> without ever returning.
>> There is no exception there is nothing in the event logs.
>> The user running the app pool has rights to the folder and can execute
>> the process correctly (i tried this with Run As on behalf of the app pool
>> user and it works).
>>
>> Thoughts? I really didn't feel like doing some production debugging on
>> Saturday night ... so maybe someone has a brilliant idea.
>>
>> Regarding code, it's just the most basic Process.Start possible:
>> var processStartInfo = new ProcessStartInfo(Executable, arguments)
>> {
>> CreateNoWindow = true,
>> WorkingDirectory = Folder,
>> UseShellExecute = true,
>> };
>>
>> var process = new Process
>> {
>> StartInfo = processStartInfo,
>> EnableRaisingEvents = true
>> };
>> process.Exited += process_Exited;
>> process.Start();
>>
>> Thanks,
>> Corneliu.
>>
>>
>
