Re: IIS5 Visual Basic.net 2003 - Internal Server Error
From: David Wang [Msft] (someone_at_online.microsoft.com)
Date: 12/31/04
- Next message: David Wang [Msft]: "Re: localhost is all that will work"
- Previous message: Robert B. Phillips, II: "Problems with Anonymous Access"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 30 Dec 2004 20:14:32 -0800
The error sounds like it is not with IIS but an application running on IIS,
like ASP.Net.
You'll want to enable custom errors to get more details and go from there.
Depending on your configuration, there can be millions of ways why it works
on their local machines but not your server, so it's not interesting/easy to
start from that perspective. Start with the actual error and work back to
the cause. Then, make sure you have appropriate processes such that
developer server and your actual server match in configuration and security
settings so that you don't have to do this in the future.
-- //David IIS http://blogs.msdn.com/David.Wang This posting is provided "AS IS" with no warranties, and confers no rights. // "Bob Smith" <BobSmith@discussions.microsoft.com> wrote in message news:706AF852-39A1-49BF-A2B8-5D2366025F9B@microsoft.com... Thanks David, The Developers are in the VS Developers group, they are also able to publish to the server successfully. In IIS Administator I can see the published application on the remote IIS server. The problem is however when they try to browse to the application through IE using http://TestServer/dev/testapp.rem?wsdl they do not get the same XML view as browsing on their local machines (http://LocalHost/dev/testapp.rem?wsdl). Instead the "Server encounded an internal error" message is displayed. Any ideas what might cause that? "David Wang [Msft]" wrote: > Change the ASP.Net custom error setting in machine.config . This setting has > nothing to do with custom errors in IIS. > > If the developers are not part of "VS Developers" group or local > administrators on the web server, they can't publish to the remote web > server (without twiddling more ACLs, anyway). > > -- > //David > IIS > http://blogs.msdn.com/David.Wang > This posting is provided "AS IS" with no warranties, and confers no rights. > // > "Bob Smith" <BobSmith@discussions.microsoft.com> wrote in message > news:E270B9B3-0401-4F78-A8A3-9D590DBC3F63@microsoft.com... > Thanks for the reply. I have turned off friendy error messages in IE and get > the "Server encountered an internal error. To get more info turn on > customErrors in the server's config file." message. > > How do I turn on customErrors in IIS5? when I edit the Web.Config to include > <system.web> > <customErrors mode="Off"> > </customErrors>I get the error below from IE > </system.web> > > Line 28: Add <error> tags for each of the errors you want to > handle. > Line 29: --> > Line 30: <customErrors mode="RemoteOnly" /> > Line 31: > Line 32: <!-- AUTHENTICATION > > > > "Kristofer Gafvert" wrote: > > > Hello, > > > > It would help to get a complete error message. Have you tried to follow > > the error message you get, and turn on customErrors (temporarily)? > > > > Have you checked the Event Log? It might tell you something. > > > > Please also disable "Show Friendly HTTP Error messages" in your > > browser.[1] > > > > I cannot give you better help, because everything else would be a guess. > > > > > > [1] > > In Internet Explorer, click Tools->Internet Options. > > Click on the Advanced tab. > > Uncheck "Show Friendly HTTP Error messages". > > > > > > -- > > Regards, > > Kristofer Gafvert > > www.ilopia.com > > > > Bob Smith wrote: > > > > > I was wondering if anyone could help me with an issue I'm having on a > > > remote IIS5 machine and Microsoft dot net. > > > > > > Configuration > > > 1, IIS5 > > > 2, Microsoft Front Page Extensions > > > 3, Microsoft Dot Net Framework 1.1 > > > 4, Visual Studio dot net (Server Components) > > > > > > Problem > > > When the developers publish applications to the IIS server clients > > > are unable to access these applications, they get an > > > error 500 > > > "Server encountered an internal error. To get more info turn on > > > customErrors in the server's config file." > > > > > > http://TestServer/dev/testapp.rem?wsdl > > > > > > however the application works fine on the developers web server. > > > > > > Does anyone know what could cause this? > > > > > > Thanks > > > > >
- Next message: David Wang [Msft]: "Re: localhost is all that will work"
- Previous message: Robert B. Phillips, II: "Problems with Anonymous Access"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
