IIS Problem ...

  • Thread starter Thread starter fripper
  • Start date Start date
F

fripper

I posted this problem a couple of days ago but felt I might have better luck
re-stating the problem.

Apparently I messed up IIS (v. 5) somehow because I am suddenly unable to
load web forms! A simple example will help.

I created a simple web project [WebTest] that contains two simple forms ...
WebForm1 and WebForm2. WebForm1 has a button which when clicked simply does
a Response.Redirect("WebForm2.aspx"). When I run the program and click the
button I get "The page cannot be found ... Error 404" message. WebForm2 is
clearly there ... in the same folder that contains WebForm1. I have
developed a number of simple web apps over the past couple of years and have
never run into this problem; although I don't think I have tried this since
installing SP2.. IIS is installed and appears to be OK. Using debug mode I
was able to ascertain that Server.MapPath is correct ... its value is
"c:\inetpub\wwwroot\WebTest"; WebTest is the folder that contains
WebForm1.aspx and WebForm2.aspx.

Now, when I click on a button (as I understand it) the page does a
round-trip to the server and back; I am getting the 404 Error on the reload
of WebForm1 on the return trip I presume. I have determined that the web
site [WebTest] containing WebForm1 and WebForm2 allows the aspx extension.

I do not want to reinstall IIS because I understand that it should be
installed before .Net ... and I do not want to risk uninstalling and then
re-installing .Net.

I have developed a number of web apps and IIS has been a huge help as I
debug these apps before deploying them to the ASP server I use; I have never
had any difficulty with it. I suspect that I did something to IIS to cause
this but I cannot fathom what that might be ... I haven't messed around with
it at all.

If anyone has suggestions for what might be causing this problem I would
appreciate it. Might SP2 be the culprit?

Thanks for any advice you can give me.








I must have done something that has suddenly caused me to be unable to load
a new web form when developing web apps. Simple example: WebForm1 has a
button which when clicked simply does a Response.Redirect("WebForm2.aspx").
When
I run the program and click the button I get "The page cannot be found"
message. WebForm2 is clearly there ... in the same folder that contains
WebForm1. I have developed a number of simple web apps over the past couple
of years and have never run into this problem; although I don't think I have
tried this since installing SP2.. IIS is installed and appears to be OK.
Using debug mode I was able to ascertain that Server.MapPath is correct ...
its value is "c:\inetpub\wwwroot\WebTest"; WebTest is the folder that
contains WebForm1 and WebForm2.
 
Interesting app.

If you are at the browser, and you simply enter the url for WebForm2.aspx, I
assume that it appears, right? (I do have to start with the obvious
question... sorry about that).

OK. when you click the button, the system posts back to the WebForm1 form.
It will execute the Redirect. This sends an HTTP header back to the browser
indicating the redirect. The browser then issues a new GET request against
the new page. Your 404 may be coming from this new request. It may not be
from the form postback. That's why I asked if WebForm2.aspx is available
from the browser.

The server logs on the web server should tell you if both the form postback
and the subsequent GET were received by the web server. That may help.

This is an odd problem. I haven't seen this.

By the way, you can reinstall IIS if you thing that will fix it, and then
follow the instructions here:
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q306005

Good luck,
--- Nick

fripper said:
I posted this problem a couple of days ago but felt I might have better luck
re-stating the problem.

Apparently I messed up IIS (v. 5) somehow because I am suddenly unable to
load web forms! A simple example will help.

I created a simple web project [WebTest] that contains two simple forms ....
WebForm1 and WebForm2. WebForm1 has a button which when clicked simply does
a Response.Redirect("WebForm2.aspx"). When I run the program and click the
button I get "The page cannot be found ... Error 404" message. WebForm2 is
clearly there ... in the same folder that contains WebForm1. I have
developed a number of simple web apps over the past couple of years and have
never run into this problem; although I don't think I have tried this since
installing SP2.. IIS is installed and appears to be OK. Using debug mode I
was able to ascertain that Server.MapPath is correct ... its value is
"c:\inetpub\wwwroot\WebTest"; WebTest is the folder that contains
WebForm1.aspx and WebForm2.aspx.

Now, when I click on a button (as I understand it) the page does a
round-trip to the server and back; I am getting the 404 Error on the reload
of WebForm1 on the return trip I presume. I have determined that the web
site [WebTest] containing WebForm1 and WebForm2 allows the aspx extension.

I do not want to reinstall IIS because I understand that it should be
installed before .Net ... and I do not want to risk uninstalling and then
re-installing .Net.

I have developed a number of web apps and IIS has been a huge help as I
debug these apps before deploying them to the ASP server I use; I have never
had any difficulty with it. I suspect that I did something to IIS to cause
this but I cannot fathom what that might be ... I haven't messed around with
it at all.

If anyone has suggestions for what might be causing this problem I would
appreciate it. Might SP2 be the culprit?

Thanks for any advice you can give me.








I must have done something that has suddenly caused me to be unable to load
a new web form when developing web apps. Simple example: WebForm1 has a
button which when clicked simply does a Response.Redirect("WebForm2.aspx").
When
I run the program and click the button I get "The page cannot be found"
message. WebForm2 is clearly there ... in the same folder that contains
WebForm1. I have developed a number of simple web apps over the past couple
of years and have never run into this problem; although I don't think I have
tried this since installing SP2.. IIS is installed and appears to be OK.
Using debug mode I was able to ascertain that Server.MapPath is correct ....
its value is "c:\inetpub\wwwroot\WebTest"; WebTest is the folder that
contains WebForm1 and WebForm2.
Click to expand...
 
I am able to load WebForm2 if I manually enter the url in the browser's
address box. Server log shows that the problem is on the postback of
WebForm1. The GET for WebForm2 does not appear. Here are the relevant
entries:

00:28:58 10.0.1.5 GET /WebTest/WebForm1 200
00:29:00 10.0.1.5 GET /<Rejected-By-UrlScan> 404

They don't tell me WHY it was rejected by UrlScan.

Guess I better plan to reinstall IIS ... will do so this evening.

Thanks, Nick


Nick Malik said:
Interesting app.

If you are at the browser, and you simply enter the url for WebForm2.aspx,
I
assume that it appears, right? (I do have to start with the obvious
question... sorry about that).

OK. when you click the button, the system posts back to the WebForm1
form.
It will execute the Redirect. This sends an HTTP header back to the
browser
indicating the redirect. The browser then issues a new GET request
against
the new page. Your 404 may be coming from this new request. It may not
be
from the form postback. That's why I asked if WebForm2.aspx is available
from the browser.

The server logs on the web server should tell you if both the form
postback
and the subsequent GET were received by the web server. That may help.

This is an odd problem. I haven't seen this.

By the way, you can reinstall IIS if you thing that will fix it, and then
follow the instructions here:
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q306005

Good luck,
--- Nick

fripper said:
I posted this problem a couple of days ago but felt I might have better luck
re-stating the problem.

Apparently I messed up IIS (v. 5) somehow because I am suddenly unable to
load web forms! A simple example will help.

I created a simple web project [WebTest] that contains two simple forms ...
WebForm1 and WebForm2. WebForm1 has a button which when clicked simply does
a Response.Redirect("WebForm2.aspx"). When I run the program and click the
button I get "The page cannot be found ... Error 404" message. WebForm2 is
clearly there ... in the same folder that contains WebForm1. I have
developed a number of simple web apps over the past couple of years and have
never run into this problem; although I don't think I have tried this since
installing SP2.. IIS is installed and appears to be OK. Using debug mode
I
was able to ascertain that Server.MapPath is correct ... its value is
"c:\inetpub\wwwroot\WebTest"; WebTest is the folder that contains
WebForm1.aspx and WebForm2.aspx.

Now, when I click on a button (as I understand it) the page does a
round-trip to the server and back; I am getting the 404 Error on the reload
of WebForm1 on the return trip I presume. I have determined that the web
site [WebTest] containing WebForm1 and WebForm2 allows the aspx
extension.

I do not want to reinstall IIS because I understand that it should be
installed before .Net ... and I do not want to risk uninstalling and then
re-installing .Net.

I have developed a number of web apps and IIS has been a huge help as I
debug these apps before deploying them to the ASP server I use; I have never
had any difficulty with it. I suspect that I did something to IIS to cause
this but I cannot fathom what that might be ... I haven't messed around with
it at all.

If anyone has suggestions for what might be causing this problem I would
appreciate it. Might SP2 be the culprit?

Thanks for any advice you can give me.








I must have done something that has suddenly caused me to be unable to load
a new web form when developing web apps. Simple example: WebForm1 has a
button which when clicked simply does a Response.Redirect("WebForm2.aspx").
When
I run the program and click the button I get "The page cannot be found"
message. WebForm2 is clearly there ... in the same folder that contains
WebForm1. I have developed a number of simple web apps over the past couple
of years and have never run into this problem; although I don't think I have
tried this since installing SP2.. IIS is installed and appears to be OK.
Using debug mode I was able to ascertain that Server.MapPath is correct ...
its value is "c:\inetpub\wwwroot\WebTest"; WebTest is the folder that
contains WebForm1 and WebForm2.
Click to expand...
Click to expand...
 
Ahhh ... the plot thickens! After poking around some more on this problem I
found two log files ... urlscan.log and the logfile in
C:\WINNT\system32\Logfiles\W3SVC1. The second of these shows the entries:

22:23:21 127.0.0.1 GET /WebTest2/WebForm2.aspx 200
22:23:23 127.0.0.1 GET /<Rejected-By-UrlScan> 404

and the urlscan file shows:

[12-01-2004 - 17:23:23] Client at 127.0.0.1: Sent verb 'POST', which is not
specifically allowed. Request will be rejected.

[I guess the W3SVC1 logfile uses GMT and the urlscanlogfile uses local time]

Now, I went to the urlscan.ini file and from what I can ascertain POST is an
allowed verb ... as are GET, HEAD and DEBUG.

I will end this message with a complete listing of the .ini file.

Any advice as to why the postback is not working would be appreciated.
Thanks.


[options]
UseAllowVerbs=1 ; if 1, use [AllowVerbs] section, else use
[DenyVerbs] section
UseAllowExtensions=0 ; if 1, use [AllowExtensions] section, else
use [DenyExtensions] section
NormalizeUrlBeforeScan=1 ; if 1, canonicalize URL before processing
VerifyNormalization=1 ; if 1, canonicalize URL twice and reject
request if a change occurs
AllowHighBitCharacters=0 ; if 1, allow high bit (ie. UTF8 or MBCS)
characters in URL
AllowDotInPath=0 ; if 1, allow dots that are not file
extensions
RemoveServerHeader=0 ; if 1, remove "Server" header from response
EnableLogging=1 ; if 1, log UrlScan activity
PerProcessLogging=0 ; if 1, the UrlScan.log filename will contain
a PID (ie. UrlScan.123.log)
AllowLateScanning=0 ; if 1, then UrlScan will load as a low
priority filter.
PerDayLogging=1 ; if 1, UrlScan will produce a new log each
day with activity in the form UrlScan.010101.log
RejectResponseUrl= ; UrlScan will send rejected requests to the
URL specified here. Default is /<Rejected-by-UrlScan>
UseFastPathReject=0 ; If 1, then UrlScan will not use the
RejectResponseUrl or allow IIS to log the request

; If RemoveServerHeader is 0, then AlternateServerName can be
; used to specify a replacement for IIS's built in 'Server' header
AlternateServerName=

[AllowVerbs]

;
; The verbs (aka HTTP methods) listed here are those commonly
; processed by a typical IIS server.
;
; Note that these entries are effective if "UseAllowVerbs=1"
; is set in the [Options] section above.
;

GET
HEAD
POST
DEBUG

[DenyVerbs]

;
; The verbs (aka HTTP methods) listed here are used for publishing
; content to an IIS server via WebDAV.
;
; Note that these entries are effective if "UseAllowVerbs=0"
; is set in the [Options] section above.
;

PROPFIND
PROPPATCH
MKCOL
DELETE
PUT
COPY
MOVE
LOCK
UNLOCK
OPTIONS
SEARCH

[DenyHeaders]

;
; The following request headers alter processing of a
; request by causing the server to process the request
; as if it were intended to be a WebDAV request, instead
; of a request to retrieve a resource.
;

Translate:
If:
Lock-Token:

[AllowExtensions]

;
; Extensions listed here are commonly used on a typical IIS server.
;
; Note that these entries are effective if "UseAllowExtensions=1"
; is set in the [Options] section above.
;

..asp
..cer
..cdx
..asa
..htm
..html
..txt
..jpg
..jpeg
..gif

;.idq
;.htw
;.ida
;.idc
;.shtm
;.shtml
;.stm
;.htr
;.printer
[DenyExtensions]

;
; Extensions listed here either run code directly on the server,
; are processed as scripts, or are static files that are
; generally not intended to be served out.
;
; Note that these entries are effective if "UseAllowExtensions=0"
; is set in the [Options] section above.
;

; Deny executables that could run on the server
..exe
..bat
..cmd
..com

; Deny infrequently used scripts
..htw ; Maps to webhits.dll, part of Index Server
..ida ; Maps to idq.dll, part of Index Server
..idq ; Maps to idq.dll, part of Index Server
..htr ; Maps to ism.dll, a legacy administrative tool
..idc ; Maps to httpodbc.dll, a legacy database access tool
..shtm ; Maps to ssinc.dll, for Server Side Includes
..shtml ; Maps to ssinc.dll, for Server Side Includes
..stm ; Maps to ssinc.dll, for Server Side Includes
..printer ; Maps to msw3prt.dll, for Internet Printing Services

; Deny various static files
..ini ; Configuration files
..log ; Log files
..pol ; Policy files
..dat ; Configuration files

;.asp
;.cer
;.cdx
;.asa
[DenyUrlSequences]
... ; Don't allow directory traversals
../ ; Don't allow trailing dot on a directory name
\ ; Don't allow backslashes in URL
: ; Don't allow alternate stream access
% ; Don't allow escaping after normalization
& ; Don't allow multiple CGI processes to run on a single request




fripper said:
I am able to load WebForm2 if I manually enter the url in the browser's
address box. Server log shows that the problem is on the postback of
WebForm1. The GET for WebForm2 does not appear. Here are the relevant
entries:

00:28:58 10.0.1.5 GET /WebTest/WebForm1 200
00:29:00 10.0.1.5 GET /<Rejected-By-UrlScan> 404

They don't tell me WHY it was rejected by UrlScan.

Guess I better plan to reinstall IIS ... will do so this evening.

Thanks, Nick


Nick Malik said:
Interesting app.

If you are at the browser, and you simply enter the url for
WebForm2.aspx, I
assume that it appears, right? (I do have to start with the obvious
question... sorry about that).

OK. when you click the button, the system posts back to the WebForm1
form.
It will execute the Redirect. This sends an HTTP header back to the
browser
indicating the redirect. The browser then issues a new GET request
against
the new page. Your 404 may be coming from this new request. It may not
be
from the form postback. That's why I asked if WebForm2.aspx is available
from the browser.

The server logs on the web server should tell you if both the form
postback
and the subsequent GET were received by the web server. That may help.

This is an odd problem. I haven't seen this.

By the way, you can reinstall IIS if you thing that will fix it, and then
follow the instructions here:
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q306005

Good luck,
--- Nick

fripper said:
I posted this problem a couple of days ago but felt I might have better luck
re-stating the problem.

Apparently I messed up IIS (v. 5) somehow because I am suddenly unable
to
load web forms! A simple example will help.

I created a simple web project [WebTest] that contains two simple forms ...
WebForm1 and WebForm2. WebForm1 has a button which when clicked simply does
a Response.Redirect("WebForm2.aspx"). When I run the program and click the
button I get "The page cannot be found ... Error 404" message. WebForm2 is
clearly there ... in the same folder that contains WebForm1. I have
developed a number of simple web apps over the past couple of years and have
never run into this problem; although I don't think I have tried this since
installing SP2.. IIS is installed and appears to be OK. Using debug mode
I
was able to ascertain that Server.MapPath is correct ... its value is
"c:\inetpub\wwwroot\WebTest"; WebTest is the folder that contains
WebForm1.aspx and WebForm2.aspx.

Now, when I click on a button (as I understand it) the page does a
round-trip to the server and back; I am getting the 404 Error on the reload
of WebForm1 on the return trip I presume. I have determined that the
web
site [WebTest] containing WebForm1 and WebForm2 allows the aspx
extension.

I do not want to reinstall IIS because I understand that it should be
installed before .Net ... and I do not want to risk uninstalling and
then
re-installing .Net.

I have developed a number of web apps and IIS has been a huge help as I
debug these apps before deploying them to the ASP server I use; I have never
had any difficulty with it. I suspect that I did something to IIS to cause
this but I cannot fathom what that might be ... I haven't messed around with
it at all.

If anyone has suggestions for what might be causing this problem I would
appreciate it. Might SP2 be the culprit?

Thanks for any advice you can give me.








I must have done something that has suddenly caused me to be unable to load
a new web form when developing web apps. Simple example: WebForm1 has a
button which when clicked simply does a Response.Redirect("WebForm2.aspx").
When
I run the program and click the button I get "The page cannot be found"
message. WebForm2 is clearly there ... in the same folder that contains
WebForm1. I have developed a number of simple web apps over the past couple
of years and have never run into this problem; although I don't think I have
tried this since installing SP2.. IIS is installed and appears to be OK.
Using debug mode I was able to ascertain that Server.MapPath is correct ...
its value is "c:\inetpub\wwwroot\WebTest"; WebTest is the folder that
contains WebForm1 and WebForm2.
Click to expand...
Click to expand...
Click to expand...
 
Back
Top