I had the same problem when installing on a 2003 Server. I found a lot of suggestions on the net that did not work, but I came accross this fix from larry on mcse. Thare are 3 solutions all solving the problem with IIS6 using the NETWORK SERVICE user instead of the ASP.NET user as in IIS5. I used #3 as I still wanted to take advantage of the application pooling in IIS6
1.Change IIS Isolation Mode Setting:
Right click on "WebSites" under IIS 6.0 and choose properties. Then Click to open the "Service" tab. Check the chekcbox labelled "Run WWW service in IIS 5.0 isolation mode.". Click OK and then restart IIS. This will allow your app to run in IIS 5.0 mode. You may still have to grant the ASP.NET read permissions to the same reg key mentioned in #3.
2. Change IIS Application Pool Setting:
Click on Application Pools under IIS. Right click on the "DefaultAppPool". Choose properties. Go to the "Identity" tab, and change the Predefined value to "LocalSystem". CLick Yes on the warning and Click OK. 3. Change Registry setting: Go to "HKEY_LOCAL_MACHINE\System\CurrentCOntrolSet\EventLog". RIght click on "eventLog" and choose "permissions". Click on the "Advanced" tab below. This will open the "Advanced Security settings for event log" dialog box. Click on the "Add" button in the "Permissions" tab. This will open the "Select USer or Group" dialog box. Click "Advanced" button and find the
"NETWORK SERVICE" account. Select this account and click on OK. Confirm the account by clicking OK on the "Select User or Group" dialog box. This will
open the "Permission entry for event log" dialog box. Check on the "Set Value" and "Create SUbkey" items and click on OK. Now confirm on all the
underlying dialog boxes by clicking on OK.
Cheers,
Adam