v1.0 get "SERVER APPLICATION NOT AVAILABLE"

[hoster]

Installed the new .net sdk and get "SERVER APPLICATION NOT AVAILABLE" when trying to run my .net pages. I checked the event viewer and it said that aspnet_wp.exe couldnt load because of a username and password setting in the processModel were incorrect or something. I uinstalled and reinstalled beta 2 and now it works. I tried installing the redistribution package I guess thats asp.net without the sdk. Same stuff. Any ideas on why this might be happening?By default ASP.NET runs the ASP.NET worker process using a<BR>non-adminitrative windows account called "ASPNET". This restricts what<BR>an ASP.NET application can do on a machine -- and requires<BR>administrators to explicitly grant security permissions. <BR><BR>However, on Windows Domain Controller machines (this includes the<BR>Windows Small Business Server product) the ASPNET account cannot be used<BR>-- since non-administrative local accounts cannot be created and used<BR>(the security policy of a Windows Domain Controller machine prevents<BR>this). <BR><BR>If you attempt to use the default ASPNET account when running an ASP.NET<BR>page on a Windows Domain Controller, the worker process will fail to<BR>start -- most likely with an error message similar to the one below: <BR><BR> "aspnet_wp.exe could not be launched because the username and/or<BR>password supplied in the processModel section of the config file are<BR>invalid"<BR><BR>To fix this, it is necessary to configure ASP.NET to instead use the<BR>LocalSystem account after setup. This is done by modifying the<BR><processModel> tag within the Machine.Config configuration file<BR>installed in the below location:<BR><BR> c:WindowsMicrosoft.NetFrameworkV1.0.3705ConfigMach ine.Config<BR><BR>By default you will find that the <processModel> configuration tag has a<BR>"userName" attribute set to the value: "MACHINE". Changing this value<BR>to "SYSTEM" will cause ASP.NET to instead use the LocalSystem account<BR>when executing. This account *does* have permission to run on Windows<BR>Domain Controllers.<BR><BR>After making the change to the Machine.Config XML file, save it, and<BR>then restart IIS (iisreset). ASP.NET will then be using the LocalSystem<BR>account to run its worker process, and ASP.NET will function fine on<BR>domain controllers.<BR>Thanks.