Hey Tim,
How are you doing on this issue, does the suggestion in my last reply helps
a little? If there're anything else we can help, please feel free to post
here.
Regards,
Steven Cheng
Microsoft Online Support
Get Secure!
www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)
--------------------
X-Tomcat-ID: 58332852
References: <F3**********************************@microsoft.co m>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_0001_340FBD5E"
Content-Transfer-Encoding: 7bit
From:
st*****@online.microsoft.com (Steven Cheng[MSFT])
Organization: Microsoft
Date: Wed, 30 Nov 2005 02:47:16 GMT
Subject: RE: The page cannot be displayed instead of exception
X-Tomcat-NG: microsoft.public.dotnet.framework.webservices
Message-ID: <f4**************@TK2MSFTNGXA02.phx.gbl>
Newsgroups: microsoft.public.dotnet.framework.webservices
Lines: 178
Path: TK2MSFTNGXA02.phx.gbl
microsoft.public.dotnet.framework.webservices:1287 1
NNTP-Posting-Host: TOMCATIMPORT1 10.201.218.122
Hi Tim,
Welcome to webservice newsgroup.
From your description, one of your ASP.NET webservice can work well (can
view error info when turn off customErrors...), but always return "page can
not be displayed..... error when move to a deployment server, yes?
As for the <customErrors mode="Off" .../>, it only ensure that when there
is unhandled exception occurs in ASP.NET runtime, it'll be displayed on the
web page with detaield error info... However, since the ASP.NET web
application will recieve request from client browser , then IIS server and
finally the asp.net pipeline ... , there could have some exception or
error occur before the ASP.NET runtime handle the request, in such cases,
the error info can not be captured by customErros page.....
So for general troubleshooting, I would suggest first try putting a normal
HTML page in your asp.net app's virtual dir and visist it to see whether we
can view it correctly(see IIS works well or not...). Also, the IIS log
under %windows% \system32\logfiles is another thing we can check , please
also have a look to see whether there is error entry mapped to your request
to the webservice...
If there're anything unclear or any other findings, please feel free to
post here.
Thanks,
Steven Cheng
Microsoft Online Support
Get Secure!
www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)
--------------------
Thread-Topic: The page cannot be displayed instead of exception
thread-index: AcX1Be33Va/v5g4zTAKlrUb66ZKjMg==
X-WBNR-Posting-Host: 192.76.82.90
From: =?Utf-8?B?VGltIFJleW5vbGRz?= <ti**********@online.nospam>
Subject: The page cannot be displayed instead of exception
Date: Tue, 29 Nov 2005 08:57:06 -0800
Lines: 16
Message-ID: <F3**********************************@microsoft.co m>
MIME-Version: 1.0
Content-Type: text/plain;
charset="Utf-8"
Content-Transfer-Encoding: 7bit
X-Newsreader: Microsoft CDO for Windows 2000
Content-Class: urn:content-classes:message
Importance: normal
Priority: normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
Newsgroups: microsoft.public.dotnet.framework.webservices
NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGXA01.phx.gbl!TK2MSF TNGXA03.phx.gbl
microsoft.public.dotnet.framework.webservices:1286 4
X-Tomcat-NG: microsoft.public.dotnet.framework.webservices
Team,
When my web service throws an exception and I am debugging on my PC - I get
the exception back in my browser fine. My web.config shows <customErrors
mode="Off"/> and this is working well.
However, when I test this web service on the deployment server, I only get
'The page cannot be displayed' instead of the exception. That is when I
call
the web service on the deployment server locally or remotely. The
web.config
on the deployment server also has <customErrors mode="Off"/>.
Please advise as to why I am not seeing the exception info on the
deployment
server even though <customErrors mode="Off"/>. Not only can I not get it
remotelyi, I can't get it locally.
THank you,
Tim
