Re: ASP.Net 1.1, Win 2003, IIS6, System.Diagnostics.Process, run notep
- From: "Joe Kaplan \(MVP - ADSI\)" <joseph.e.kaplan@xxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 14 Mar 2006 15:19:49 -0600
Try filemon and regmon to see if you are getting some sort of access denied
when attempting to execute that. You can set them to filter on w3wp.exe.
This is way I am usually most successful when trying to track down
permissions problems (although it does not always work).
Joe K.
<jeanbdenis@xxxxxxxxx> wrote in message
news:1142369233.923071.102700@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
I am amazed how stuborn this thing is.. the worker proce is running as
network service. still can't get anywhere with this
.
- Follow-Ups:
- References:
- Re: ASP.Net 1.1, Win 2003, IIS6, System.Diagnostics.Process, run notep
- From: jeanbdenis
- Re: ASP.Net 1.1, Win 2003, IIS6, System.Diagnostics.Process, run notep
- From: Dominick Baier [DevelopMentor]
- Re: ASP.Net 1.1, Win 2003, IIS6, System.Diagnostics.Process, run notep
- From: jeanbdenis
- Re: ASP.Net 1.1, Win 2003, IIS6, System.Diagnostics.Process, run notep
- Prev by Date: Re: ASP.Net 1.1, Win 2003, IIS6, System.Diagnostics.Process, run notep
- Next by Date: Re: ASP.Net 1.1, Win 2003, IIS6, System.Diagnostics.Process, run notep
- Previous by thread: Re: ASP.Net 1.1, Win 2003, IIS6, System.Diagnostics.Process, run notep
- Next by thread: Re: ASP.Net 1.1, Win 2003, IIS6, System.Diagnostics.Process, run notep
- Index(es):
Relevant Pages
|