server application unavailable 3

[drew10]

I wrote an app on my local machine, and now I am trying to upload it to a remote machine. I run through the new website wizard to create the site in iis, but when I attempt to view it, I receive an error message that the server application is unavailable. I think it has something to do with making the directory into an application. When I right click on the directory in iis, it doesn't give me the option to create an application. Any help would be greatly appreciated!
Thanx,
Drew

 

[drew10]

I found a solution. It told me to change the user in the machine.config file from machine to system. I did this, and now everything seems to be working just fine. Does anyone know if this change opens security holes in the server? If anyone can explain what occurs when you change the user in the machine.config I am very interested.
Thanx,
drew

 

[link9]

asp.net has a nearly infinite amount of power over your server. By default, permissions to wield these powers are not given.

By running aspnet processes under the system account, you are giving many of those permissions.

if you read this article:

http://support.microsoft.com/default.aspx?scid=kb;en-us;Q315158

it will give you instructions on how to setup a separate account, and to give that account the proper permissions for asp.net to run under it.

That's what I would suggest. Although after a re-boot, "log on as a batch job" permission will have to be reset each time in the local security policy settings of the machine.

It's a pain, but given how widely known this problem is, I'm sure there are ppl out there who would exploit it if you have it running as system.

paul

 

[drew10]

Yet another star for you! Thanks for the help.

 

[jfrost10]

This post saved my teams @$$es today. Thanks Paul, yet another star for you man.

D

 

[rox2002]

I began experiencing this "server application unavailable" problem 2 days ago on an environment (w2k pro) that was previously working fine for several months. I made some code changes, compiled, got an "internal compiler error", tried unsuccessfully to determine what code changes caused that, rebooted the machine. After the reboot, I could compile OK, but starting the app (debug or not) yields the big red message in the browser.

I have tried all the recovering asp.net config suggestions posted on this thread with no change. Aspnet_regiis -i, setting machine.config user to "SYSTEM", none of this works.

I am not getting any messages in my event log. Is there something I need to configure to get detailed messages from aps.net in the event log?

Any ideas? Please?
thanks.

 

[rox2002]

OK, I finally fixed this by installing VS.Net service pack 2.

thanks,
Rocky