No takers on this one I see. No problem, I think I figured it out.

After changing the userName in the machine.config, you have to do an IISRESET from a command window. At least it works on my machine, I need to verify that on a machine that had the problem to begin with.

Anyway, for any lurkers on this thread, I just want to mention that this should NOT be done on a production web server. We have simply made it easier for our developers by not making them have to add a new source key to their EventLog registry every time they develop a new app (which would be the correct way to do it).

~~Bonnie



>We are in the process of getting a lot of developers in the corporate office up to speed on .NET ... almost all of them have absolutely no experience with it.
>
>A member of our team put together a document about how to install the various things needed (.NET, SQL 2005, etc.) and all the developers followed this doc. (unfortunately, there were lots of missing pieces, but that's another story <g>)
>
>Anyway, one thing that most of them can't get past is the permissions needed for allowing writing to the system's EventLog for server-side components (anything that errors out on the server-side of the WebService calls). Some have problems with it, others don't. It's hard for me to trouble-shoot because I'm not having a problem with it. Gary and I spent two days at the corporate office last week giving some of the developers a quick training on architecture (and it was waaaaay too much information for most of them <g>).
>
>Most of the time, changing the userName to "SYSTEM" in the processModel tag of the machine.config (in the C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\CONFIG folder) seems to work. But apparently not for everyone.
>
>Is there something else we should be looking at to tweak?
>
>TIA,
>~~Bonnie