Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / ASP.NET / General / June 2007

Tip: Looking for answers? Try searching our database.

Any change I make to web.config gives server application unavailable error!

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Andy - 08 Jun 2007 09:14 GMT
If I open, edit and save the web.config file directly on the
webserver,  the
web server becomes unavailable. When I reset IIS, I get the 'Server
Application Unavailable' message appear for that web site. The change
being
made was minor, and worked locally.

Restarting IIS or the server has no affect.
Deleting the Temporary ASP.NET files has no effect.

The only way to resolve it is to create an identical web site in IIS,
pointing to exactly the same code, with the revised web.config.

This has happened to me twice now.

I am using Windows Server 2003 Web Edition and asp.net 1.1.

Any ideas? Thanks!
Alexey Smirnov - 08 Jun 2007 09:22 GMT
> If I open, edit and save the web.config file directly on the
> webserver,  the
[quoted text clipped - 14 lines]
>
> Any ideas? Thanks!

maybe something with permissions on the web.config file?
Shane Bauer - 08 Jun 2007 14:11 GMT
Hello andy,

Do you have access to the Event Viewer? If so, there should be a message
detailing the problem.

Shane

> If I open, edit and save the web.config file directly on the
> webserver,  the
[quoted text clipped - 12 lines]
>
> Any ideas? Thanks!
bruce barker - 08 Jun 2007 16:03 GMT
most likely you have pages that reference each other without explicit
reference directive on the page. during the local compile, if they are
compiled in the same batch ok, else fail. this is because asp.net
compiles several pages into the same dll (a batch), so pages that end up
in the same batch can reference each other. if they end up in different
dlls they can not unless an explicit reference is specified.

you should check the application log to see the actual error.

-- bruce (sqlwork.com)

> If I open, edit and save the web.config file directly on the
> webserver,  the
[quoted text clipped - 14 lines]
>
> Any ideas? Thanks!
Andy - 12 Jun 2007 09:39 GMT
Thanks everyone.

There is nothing in the Application Log at all unfortunately

I do have 2 aspx pages that reference the same code behind page -
would that have an effect?

Bruce could you elaborate on your suggestion, it sounds like a
possibility..

I have inherited this site, and although it is substantially better
than it was, there is still some unusual stuff going on!

> most likely you have pages that reference each other without explicit
> reference directive on the page. during the local compile, if they are
[quoted text clipped - 25 lines]
>
> > Any ideas? Thanks!

Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.