Comments
Sort by recent activity
AHA!!! I changed the username in Machine.config to SYSTEM instead of ASPNET, and it works great now... Here's the snippet in case anyone else needs to see it...
<processModel
enable="true"
timeout="Infinite"
idleTimeout="Infinite"
shutdownTimeout="0:00:05"
requestLimit="Infinite"
requestQueueLimit="5000"
restartQueueLimit="10"
memoryLimit="60"
webGarden="false"
cpuMask="0xffffffff" userName="SYSTEM"
password="AutoGenerate"
logLevel="Errors"
clientConnectedCheck="0:00:15"
comAuthenticationLevel="Connect"
comImpersonationLevel="Impersonate"
responseDeadlockInterval="00:07:00"
maxWorkerThreads="20"
maxIoThreads="20"
/>
Thanks for your help, your profiler is Awesome! I have tried about 7, and yours is the only one that is even remotely helpful! / comments
AHA!!! I changed the username in Machine.config to SYSTEM instead of ASPNET, and it works great now... Here's the snippet in case anyone else needs to see it...
<processModel
enable="true"
timeout=...
Brian, I do have an ASPNET user, and I know that that damn ASPNET user has been a problem in the past. Pardon my ignorance, but how does the ANTS Profiler find out who the ASPNET user is in machine.config? That would give me a great start. I went ahead and made sure that the ASPNET account had full permissions on the HKEY_USERS hive. I know that we've had some strange things happen that were "fixed" when we manually set permissions in the registry, but that was a year ago - its a little fuzzy unfortunately! Thanks for your quick response last time, by the way. / comments
Brian,I do have an ASPNET user, and I know that that damn ASPNET user has been a problem in the past. Pardon my ignorance, but how does the ANTS Profiler find out who the ASPNET user is in machine....