Unrecognized "Page not found" error

I installed DotNetNuke on IIS6 (Server 2003 Standard) so I could run a
DNN-based In-Out Board on our company intranet. Most of the time, the
In-Out Board works beautifully for our 27 users, but occasionally a user who
tries to visit the page is greeted with the following error message:

Oops.

Your requested page was not found. please try again

The error will persist for that user for minutes or hours, but other users
will continue to have no trouble with the page. No other message appears; no
404 error, nothing, and the URL in the address bar doesn't reflect any
particular page; it simply shows the normal URL for the page; namely,
http://inout.mydomain.com/dnn. I'd never seen that type of Page Not Found
error and assumed it was a DNN error message, but when I posted this
question to the DNN forum, I was told that in fact that is not a DNN error
message. I've searched for the text "Oops." inside every file on that IIS
server's hard drive in the hopes I could discover the source of the message
and possibly get some insight in how to fix it, but came up empty-handed. I
even speculated that my internal DNS entry might sometimes be failing to
resolve properly, resulting in the DNS request being forwarded to external
name servers. But nslookups, pings, and ipconfig /flushdns troubleshooting
all seemed to confirm that DNS was functioning properly, and the IIS server
responded to pings by IP and DNS name.

I'm just about out of ideas. Is there some way to definitively track down
the source of this mysterious "Page Not Found" error?

Thanks in advance,

BJ

David
Wed Jun 28 01:44:34 CDT 2006

"oops" is not in any IIS error message.

After making sure the request actually made it to the IIS6 server, I would
start looking at what else is installed on it. Because it definitely is not
an IIS6 issue...

--
//David
IIS
http://blogs.msdn.com/David.Wang
This posting is provided "AS IS" with no warranties, and confers no rights.
//

"Bryan L" <blinton.nospam@connellinsurance.nospam.com> wrote in message
news:OyIMg6imGHA.5052@TK2MSFTNGP04.phx.gbl...
>I installed DotNetNuke on IIS6 (Server 2003 Standard) so I could run a
>DNN-based In-Out Board on our company intranet. Most of the time, the
>In-Out Board works beautifully for our 27 users, but occasionally a user
>who tries to visit the page is greeted with the following error message:
>
> Oops.
>
> Your requested page was not found. please try again
>
> The error will persist for that user for minutes or hours, but other users
> will continue to have no trouble with the page. No other message appears;
> no 404 error, nothing, and the URL in the address bar doesn't reflect any
> particular page; it simply shows the normal URL for the page; namely,
> http://inout.mydomain.com/dnn. I'd never seen that type of Page Not Found
> error and assumed it was a DNN error message, but when I posted this
> question to the DNN forum, I was told that in fact that is not a DNN error
> message. I've searched for the text "Oops." inside every file on that IIS
> server's hard drive in the hopes I could discover the source of the
> message and possibly get some insight in how to fix it, but came up
> empty-handed. I even speculated that my internal DNS entry might
> sometimes be failing to resolve properly, resulting in the DNS request
> being forwarded to external name servers. But nslookups, pings, and
> ipconfig /flushdns troubleshooting all seemed to confirm that DNS was
> functioning properly, and the IIS server responded to pings by IP and DNS
> name.
>
> I'm just about out of ideas. Is there some way to definitively track down
> the source of this mysterious "Page Not Found" error?
>
> Thanks in advance,
>
> BJ
>

Bryan
Wed Jun 28 15:29:10 CDT 2006

David,

Thanks for the reply.

How would I go about verifying whether the request made it to the IIS6
server? Is there some log on either the workstation or the server I can
check for this? Also, if it didn't make it to the server, then how can I
trace that error message back to its source? It's coming from *somewhere*,
but I haven't figured out a way to get visibility into what's actually
happening.

Thanks again.

Bryan

"David Wang [Msft]" <someone@online.microsoft.com> wrote in message
news:eTuAN9nmGHA.464@TK2MSFTNGP05.phx.gbl...
> "oops" is not in any IIS error message.
>
> After making sure the request actually made it to the IIS6 server, I would
> start looking at what else is installed on it. Because it definitely is
> not an IIS6 issue...
>
> --
> //David
> IIS
> http://blogs.msdn.com/David.Wang
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> //
>
> "Bryan L" <blinton.nospam@connellinsurance.nospam.com> wrote in message
> news:OyIMg6imGHA.5052@TK2MSFTNGP04.phx.gbl...
>>I installed DotNetNuke on IIS6 (Server 2003 Standard) so I could run a
>>DNN-based In-Out Board on our company intranet. Most of the time, the
>>In-Out Board works beautifully for our 27 users, but occasionally a user
>>who tries to visit the page is greeted with the following error message:
>>
>> Oops.
>>
>> Your requested page was not found. please try again
>>
>> The error will persist for that user for minutes or hours, but other
>> users will continue to have no trouble with the page. No other message
>> appears; no 404 error, nothing, and the URL in the address bar doesn't
>> reflect any particular page; it simply shows the normal URL for the page;
>> namely, http://inout.mydomain.com/dnn. I'd never seen that type of Page
>> Not Found error and assumed it was a DNN error message, but when I posted
>> this question to the DNN forum, I was told that in fact that is not a DNN
>> error message. I've searched for the text "Oops." inside every file on
>> that IIS server's hard drive in the hopes I could discover the source of
>> the message and possibly get some insight in how to fix it, but came up
>> empty-handed. I even speculated that my internal DNS entry might
>> sometimes be failing to resolve properly, resulting in the DNS request
>> being forwarded to external name servers. But nslookups, pings, and
>> ipconfig /flushdns troubleshooting all seemed to confirm that DNS was
>> functioning properly, and the IIS server responded to pings by IP and DNS
>> name.
>>
>> I'm just about out of ideas. Is there some way to definitively track
>> down the source of this mysterious "Page Not Found" error?
>>
>> Thanks in advance,
>>
>> BJ
>>
>
>

Steve
Thu Jun 29 23:49:10 CDT 2006

I would review the IISLogs for 404 errors and see what machine requested the
webpage. That could provide leads to what is potentially caused the issue,
by default IISLog files are located in
%systemroot%\system32\logfiles\w3svcXXX. These will rollover once a day by
default.

--

Steve Schofield
Windows Server MVP - IIS
ASPInsider Member - MCP

http://www.orcsweb.com/
Managed Complex Hosting
#1 in Service and Support


"Bryan L" <blinton.nospam@connellinsurance.nospam.com> wrote in message
news:e$c$FGvmGHA.2452@TK2MSFTNGP04.phx.gbl...
> David,
>
> Thanks for the reply.
>
> How would I go about verifying whether the request made it to the IIS6
> server? Is there some log on either the workstation or the server I can
> check for this? Also, if it didn't make it to the server, then how can I
> trace that error message back to its source? It's coming from
> *somewhere*, but I haven't figured out a way to get visibility into what's
> actually happening.
>
> Thanks again.
>
> Bryan
>
> "David Wang [Msft]" <someone@online.microsoft.com> wrote in message
> news:eTuAN9nmGHA.464@TK2MSFTNGP05.phx.gbl...
>> "oops" is not in any IIS error message.
>>
>> After making sure the request actually made it to the IIS6 server, I
>> would start looking at what else is installed on it. Because it
>> definitely is not an IIS6 issue...
>>
>> --
>> //David
>> IIS
>> http://blogs.msdn.com/David.Wang
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>> //
>>
>> "Bryan L" <blinton.nospam@connellinsurance.nospam.com> wrote in message
>> news:OyIMg6imGHA.5052@TK2MSFTNGP04.phx.gbl...
>>>I installed DotNetNuke on IIS6 (Server 2003 Standard) so I could run a
>>>DNN-based In-Out Board on our company intranet. Most of the time, the
>>>In-Out Board works beautifully for our 27 users, but occasionally a user
>>>who tries to visit the page is greeted with the following error message:
>>>
>>> Oops.
>>>
>>> Your requested page was not found. please try again
>>>
>>> The error will persist for that user for minutes or hours, but other
>>> users will continue to have no trouble with the page. No other message
>>> appears; no 404 error, nothing, and the URL in the address bar doesn't
>>> reflect any particular page; it simply shows the normal URL for the
>>> page; namely, http://inout.mydomain.com/dnn. I'd never seen that type of
>>> Page Not Found error and assumed it was a DNN error message, but when I
>>> posted this question to the DNN forum, I was told that in fact that is
>>> not a DNN error message. I've searched for the text "Oops." inside
>>> every file on that IIS server's hard drive in the hopes I could discover
>>> the source of the message and possibly get some insight in how to fix
>>> it, but came up empty-handed. I even speculated that my internal DNS
>>> entry might sometimes be failing to resolve properly, resulting in the
>>> DNS request being forwarded to external name servers. But nslookups,
>>> pings, and ipconfig /flushdns troubleshooting all seemed to confirm that
>>> DNS was functioning properly, and the IIS server responded to pings by
>>> IP and DNS name.
>>>
>>> I'm just about out of ideas. Is there some way to definitively track
>>> down the source of this mysterious "Page Not Found" error?
>>>
>>> Thanks in advance,
>>>
>>> BJ
>>>
>>
>>
>
>