Problems running ASP.NET 2.0 in Windows XP

microsoft.public.dotnet.framework.aspnet

8 Sep 2006 3:29 PM

Chris

Good Morning,
I have spent a considerable amount of time trying to get aspx pages to
render in IIS 5.1 to no avail. At first I thought it was a problem
with the installation of the Quickstarts since they were the first
failure I saw after loading framework and SDK 2.0.

The problem presents itself as follows:
When I attempt to load static content (HTM) the page renders as
expected. But when I attempt to load even the simplist .net script
(ASPX) the page fails to render or display an error message. I just
hear a bonk noise and the page loads forever. I discovered that this
bonk noise was a window that would not open due to the IISADMIN service
being run in "Allow service to interact with desktop" unset. When I
set it and loaded the page again, a dialog appeared with the following
message:

The program [C:\WINDOWS\system32\inetsrv\inetinfo.exe] caused a problem
and is going to close.

Would you like to save a dump file?

The IIS State stack dump is shown below this message. Used IISState
application to get info.

I have repaired the framework, uninstalled and reinstalled it.
Uninstalled and reinstalled IIS. Changed the ASPNET account to
Administrator, changed the account that the .net apps run under to an
admin account, disabled all startup programs in msconfig, manually
turned off Norton and Black ICE, and finally, stood and screamed at my
box. The last step scared me a little after I observed the force of my
angry yawp tilted my monitor slightly. The police, by the way, have no
idea what IIS or .net is but do understand the frustration expressed by
my 90 year old neighbor who was awoken by subsequent swearing.

Please help.

Chris

Partial Stack Dump follows:

(Truncated)

..cxr 1a1f6ec
# ChildEBP RetAddr
WARNING: Stack unwind information not available. Following frames may
be wrong.
00 01a1fac0 65f1730b bmnet!ExtSetSocketState+0x2de0
01 01a1faf0 5aa46ea4 ISATQ!AtqTransmitFile+0x9e
02 01a1fb20 5aa4861f w3svc!CLIENT_CONN::TransmitFile+0x4b
03 01a1fb54 5aa5801e w3svc!HTTP_REQ_BASE::TransmitFile+0xa8
04 01a1fb98 5a8567c9 w3svc!WAM_REQUEST::TransmitFileInProc+0x1a2
05 01a1fbf4 5a8579ed wam!WAM_EXEC_INFO::TransmitFile+0x11c
06 01a1fc1c 6a2a9213 wam!ServerSupportFunction+0x442
07 01a1fc70 6a2a9351 webengine+0x9213
08 01a1fce4 6a2a9456 webengine+0x9351
09 01a1ff48 6a2a4aca webengine+0x9456
0a 01a1ff64 6a2a9086 webengine+0x4aca
0b 01a1ff80 6a2a400c webengine+0x9086
0c 01a1ffb4 7c80b683 webengine+0x400c
0d 01a1ffec 00000000 kernel32!BaseThreadStart+0x37

**Current Stack State**

Other information: Thread is throwing an exception. Checking for known
issues.
Thread Type: HTTP Listener
# ChildEBP RetAddr
00 01a1c218 77d49418 ntdll!KiFastSystemCallRet
01 01a1c250 77d561c6 USER32!NtUserWaitMessage+0xc
02 01a1c278 77d6a92e USER32!InternalDialogBox+0xd0
03 01a1c538 77d6a294 USER32!SoftModalMessageBox+0x938
04 01a1c688 77d95fbb USER32!MessageBoxWorker+0x2ba
05 01a1c6e0 77d96060 USER32!MessageBoxTimeoutW+0x7a
06 01a1c714 77d80577 USER32!MessageBoxTimeoutA+0x9c
07 01a1c734 77d8052f USER32!MessageBoxExA+0x1b
08 01a1c750 100206d4 USER32!MessageBoxA+0x45
WARNING: Stack unwind information not available. Following frames may
be wrong.
09 01a1ef08 7815e3b2 bmnet!WSPStartup+0x1474
0a 01a1ef18 7c86304e MSVCR80!__CxxUnhandledExceptionFilter+0x63
0b 01a1f5b4 7c83ab20 kernel32!UnhandledExceptionFilter+0x1ec
0c 01a1f5bc 7c839b09 kernel32!BaseThreadStart+0x4d
0d 01a1f5e4 7c9037bf kernel32!_except_handler3+0x61
0e 01a1f608 7c90378b ntdll!ExecuteHandler2+0x26
0f 01a1f6b8 7c90eafa ntdll!ExecuteHandler+0x24
10 01a1f738 7c918e74 ntdll!KiUserExceptionDispatcher+0xe
11 01a1f7f8 7c918e74 ntdll!_LdrpInitialize+0x25b
12 01a1f884 7c911538 ntdll!_LdrpInitialize+0x25b
13 01a1fac0 65f1730b ntdll!RtlAllocateHeap+0x925
14 01a1faf0 5aa46ea4 ISATQ!AtqTransmitFile+0x9e
15 01a1fb20 5aa4861f w3svc!CLIENT_CONN::TransmitFile+0x4b
16 01a1fb54 5aa5801e w3svc!HTTP_REQ_BASE::TransmitFile+0xa8
17 01a1fb98 5a8567c9 w3svc!WAM_REQUEST::TransmitFileInProc+0x1a2
18 01a1fbf4 5a8579ed wam!WAM_EXEC_INFO::TransmitFile+0x11c
19 01a1fc1c 6a2a9213 wam!ServerSupportFunction+0x442
1a 01a1fc70 6a2a9351 webengine+0x9213
1b 01a1fce4 6a2a9456 webengine+0x9351
1c 01a1ff48 6a2a4aca webengine+0x9456
1d 01a1ff64 6a2a9086 webengine+0x4aca
1e 01a1ff80 6a2a400c webengine+0x9086
1f 01a1ffb4 7c80b683 webengine+0x400c
20 01a1ffec 00000000 kernel32!BaseThreadStart+0x37

Thread ID: 38
System Thread ID: 14b0
Kernel Time: 0:0:0.0
User Time: 0:0:0.0
Thread Type: Other
# ChildEBP RetAddr
00 01a5ff4c 7c90e31b ntdll!KiFastSystemCallRet
01 01a5ff50 7c80a746 ntdll!ZwRemoveIoCompletion+0xc
02 01a5ff7c 6a2a3fbb kernel32!GetQueuedCompletionStatus+0x29
03 01a5ffb4 7c80b683 webengine+0x3fbb
04 01a5ffec 00000000 kernel32!BaseThreadStart+0x37

8 Sep 2006 6:13 PM

Chris Cap

Let's check a few things first.

Is the asp.net 2.0 dll allowed in the list of server extensions? If it
doesn't appear in the list, it might not be registered with IIS.

To register it, go to your framework directory (something like
%windowsrootdir%/microsoft.net/framwork/v2.0575/aspnet_regiis.exe -i

What operating system are you running?

Show quote

"Chris" wrote:

> Good Morning,
> I have spent a considerable amount of time trying to get aspx pages to
> render in IIS 5.1 to no avail. At first I thought it was a problem
> with the installation of the Quickstarts since they were the first
> failure I saw after loading framework and SDK 2.0.
>
> The problem presents itself as follows:
> When I attempt to load static content (HTM) the page renders as
> expected. But when I attempt to load even the simplist .net script
> (ASPX) the page fails to render or display an error message. I just
> hear a bonk noise and the page loads forever. I discovered that this
> bonk noise was a window that would not open due to the IISADMIN service
> being run in "Allow service to interact with desktop" unset. When I
> set it and loaded the page again, a dialog appeared with the following
> message:
>
> The program [C:\WINDOWS\system32\inetsrv\inetinfo.exe] caused a problem
> and is going to close.
>
> Would you like to save a dump file?
>
> The IIS State stack dump is shown below this message. Used IISState
> application to get info.
>
> I have repaired the framework, uninstalled and reinstalled it.
> Uninstalled and reinstalled IIS. Changed the ASPNET account to
> Administrator, changed the account that the .net apps run under to an
> admin account, disabled all startup programs in msconfig, manually
> turned off Norton and Black ICE, and finally, stood and screamed at my
> box. The last step scared me a little after I observed the force of my
> angry yawp tilted my monitor slightly. The police, by the way, have no
> idea what IIS or .net is but do understand the frustration expressed by
> my 90 year old neighbor who was awoken by subsequent swearing.
>
> Please help.
>
> Chris
>
>
> Partial Stack Dump follows:
>
> (Truncated)
>
> ..cxr 1a1f6ec
> # ChildEBP RetAddr
> WARNING: Stack unwind information not available. Following frames may
> be wrong.
> 00 01a1fac0 65f1730b bmnet!ExtSetSocketState+0x2de0
> 01 01a1faf0 5aa46ea4 ISATQ!AtqTransmitFile+0x9e
> 02 01a1fb20 5aa4861f w3svc!CLIENT_CONN::TransmitFile+0x4b
> 03 01a1fb54 5aa5801e w3svc!HTTP_REQ_BASE::TransmitFile+0xa8
> 04 01a1fb98 5a8567c9 w3svc!WAM_REQUEST::TransmitFileInProc+0x1a2
> 05 01a1fbf4 5a8579ed wam!WAM_EXEC_INFO::TransmitFile+0x11c
> 06 01a1fc1c 6a2a9213 wam!ServerSupportFunction+0x442
> 07 01a1fc70 6a2a9351 webengine+0x9213
> 08 01a1fce4 6a2a9456 webengine+0x9351
> 09 01a1ff48 6a2a4aca webengine+0x9456
> 0a 01a1ff64 6a2a9086 webengine+0x4aca
> 0b 01a1ff80 6a2a400c webengine+0x9086
> 0c 01a1ffb4 7c80b683 webengine+0x400c
> 0d 01a1ffec 00000000 kernel32!BaseThreadStart+0x37
>
>
> **Current Stack State**
>
> Other information: Thread is throwing an exception. Checking for known
> issues.
> Thread Type: HTTP Listener
> # ChildEBP RetAddr
> 00 01a1c218 77d49418 ntdll!KiFastSystemCallRet
> 01 01a1c250 77d561c6 USER32!NtUserWaitMessage+0xc
> 02 01a1c278 77d6a92e USER32!InternalDialogBox+0xd0
> 03 01a1c538 77d6a294 USER32!SoftModalMessageBox+0x938
> 04 01a1c688 77d95fbb USER32!MessageBoxWorker+0x2ba
> 05 01a1c6e0 77d96060 USER32!MessageBoxTimeoutW+0x7a
> 06 01a1c714 77d80577 USER32!MessageBoxTimeoutA+0x9c
> 07 01a1c734 77d8052f USER32!MessageBoxExA+0x1b
> 08 01a1c750 100206d4 USER32!MessageBoxA+0x45
> WARNING: Stack unwind information not available. Following frames may
> be wrong.
> 09 01a1ef08 7815e3b2 bmnet!WSPStartup+0x1474
> 0a 01a1ef18 7c86304e MSVCR80!__CxxUnhandledExceptionFilter+0x63
> 0b 01a1f5b4 7c83ab20 kernel32!UnhandledExceptionFilter+0x1ec
> 0c 01a1f5bc 7c839b09 kernel32!BaseThreadStart+0x4d
> 0d 01a1f5e4 7c9037bf kernel32!_except_handler3+0x61
> 0e 01a1f608 7c90378b ntdll!ExecuteHandler2+0x26
> 0f 01a1f6b8 7c90eafa ntdll!ExecuteHandler+0x24
> 10 01a1f738 7c918e74 ntdll!KiUserExceptionDispatcher+0xe
> 11 01a1f7f8 7c918e74 ntdll!_LdrpInitialize+0x25b
> 12 01a1f884 7c911538 ntdll!_LdrpInitialize+0x25b
> 13 01a1fac0 65f1730b ntdll!RtlAllocateHeap+0x925
> 14 01a1faf0 5aa46ea4 ISATQ!AtqTransmitFile+0x9e
> 15 01a1fb20 5aa4861f w3svc!CLIENT_CONN::TransmitFile+0x4b
> 16 01a1fb54 5aa5801e w3svc!HTTP_REQ_BASE::TransmitFile+0xa8
> 17 01a1fb98 5a8567c9 w3svc!WAM_REQUEST::TransmitFileInProc+0x1a2
> 18 01a1fbf4 5a8579ed wam!WAM_EXEC_INFO::TransmitFile+0x11c
> 19 01a1fc1c 6a2a9213 wam!ServerSupportFunction+0x442
> 1a 01a1fc70 6a2a9351 webengine+0x9213
> 1b 01a1fce4 6a2a9456 webengine+0x9351
> 1c 01a1ff48 6a2a4aca webengine+0x9456
> 1d 01a1ff64 6a2a9086 webengine+0x4aca
> 1e 01a1ff80 6a2a400c webengine+0x9086
> 1f 01a1ffb4 7c80b683 webengine+0x400c
> 20 01a1ffec 00000000 kernel32!BaseThreadStart+0x37
>
>
>
>
> Thread ID: 38
> System Thread ID: 14b0
> Kernel Time: 0:0:0.0
> User Time: 0:0:0.0
> Thread Type: Other
> # ChildEBP RetAddr
> 00 01a5ff4c 7c90e31b ntdll!KiFastSystemCallRet
> 01 01a5ff50 7c80a746 ntdll!ZwRemoveIoCompletion+0xc
> 02 01a5ff7c 6a2a3fbb kernel32!GetQueuedCompletionStatus+0x29
> 03 01a5ffb4 7c80b683 webengine+0x3fbb
> 04 01a5ffec 00000000 kernel32!BaseThreadStart+0x37
>
>

9 Sep 2006 4:34 PM

Chris

Thanks for the response, Chris. Yeah, I checked the server extensions,
I registered and re-registered it. No luck. Finally, I broke down and
called Microsoft. to see if there was some other thing I was doing that
could cause this problem. Before I go on, I should say, the problem
has been fixed.

Turns out, the the Cingular connection manager I use to configure my
cellular modem attaches either the Bmwebcfg.exe process or the
Bmnet.dll file itself to the inetinfo.exe process and silently cripples
it. With all the searching I did I could not find any reference to
this problem. The MS tech pointed me to this KB article:
http://support.microsoft.com/?id=910435. By the way this doesn't only
affect creation of projects from Visual Studio but also execution of
any asp.net code at all.

Long story short, I uninstalled the Cingular Connection manger and all
is well. I re-installed an upgraded version and to this point have had
no problems. Thanks Cingular. Thanks for providing me with an
incredibly useful modem whose software went rogue and stole several
days from me. C'est la vie.

~+~+~+~+~+~+~+

Chris Cap wrote:

Show quote

> Let's check a few things first.
>
> Is the asp.net 2.0 dll allowed in the list of server extensions? If it
> doesn't appear in the list, it might not be registered with IIS.
>
> To register it, go to your framework directory (something like
> %windowsrootdir%/microsoft.net/framwork/v2.0575/aspnet_regiis.exe -i
>
> What operating system are you running?
>
> "Chris" wrote:
>

11 Sep 2006 7:42 AM

msnews

It appears you have a major problem which may go well beyond IIS and the
..NET Framework. Have you looked at the Events log?

And you may have a little more success if you run the aspnet_regiis.exe
utility.

You need to have it run the installation routine.

aspnet_regiis.exe -i

You will need to either add the .NET folder to your PATH environment
variable or run the command from that folder.

Here are more docs...

http://msdn2.microsoft.com/en-us/library/k6h9cz8h.aspx

Brennan Stehling
http://brennan.offwhite.net/blog/

Show quote

"Chris" <chris.anonacco***@gmail.com> wrote in message
news:1157729368.259655.139700@i42g2000cwa.googlegroups.com...
> Good Morning,
> I have spent a considerable amount of time trying to get aspx pages to
> render in IIS 5.1 to no avail. At first I thought it was a problem
> with the installation of the Quickstarts since they were the first
> failure I saw after loading framework and SDK 2.0.
>
> The problem presents itself as follows:
> When I attempt to load static content (HTM) the page renders as
> expected. But when I attempt to load even the simplist .net script
> (ASPX) the page fails to render or display an error message. I just
> hear a bonk noise and the page loads forever. I discovered that this
> bonk noise was a window that would not open due to the IISADMIN service
> being run in "Allow service to interact with desktop" unset. When I
> set it and loaded the page again, a dialog appeared with the following
> message:
>
> The program [C:\WINDOWS\system32\inetsrv\inetinfo.exe] caused a problem
> and is going to close.
>
> Would you like to save a dump file?
>
> The IIS State stack dump is shown below this message. Used IISState
> application to get info.
>
> I have repaired the framework, uninstalled and reinstalled it.
> Uninstalled and reinstalled IIS. Changed the ASPNET account to
> Administrator, changed the account that the .net apps run under to an
> admin account, disabled all startup programs in msconfig, manually
> turned off Norton and Black ICE, and finally, stood and screamed at my
> box. The last step scared me a little after I observed the force of my
> angry yawp tilted my monitor slightly. The police, by the way, have no
> idea what IIS or .net is but do understand the frustration expressed by
> my 90 year old neighbor who was awoken by subsequent swearing.
>
> Please help.
>
> Chris
>
>
> Partial Stack Dump follows:
>
> (Truncated)
>
> .cxr 1a1f6ec
> # ChildEBP RetAddr
> WARNING: Stack unwind information not available. Following frames may
> be wrong.
> 00 01a1fac0 65f1730b bmnet!ExtSetSocketState+0x2de0
> 01 01a1faf0 5aa46ea4 ISATQ!AtqTransmitFile+0x9e
> 02 01a1fb20 5aa4861f w3svc!CLIENT_CONN::TransmitFile+0x4b
> 03 01a1fb54 5aa5801e w3svc!HTTP_REQ_BASE::TransmitFile+0xa8
> 04 01a1fb98 5a8567c9 w3svc!WAM_REQUEST::TransmitFileInProc+0x1a2
> 05 01a1fbf4 5a8579ed wam!WAM_EXEC_INFO::TransmitFile+0x11c
> 06 01a1fc1c 6a2a9213 wam!ServerSupportFunction+0x442
> 07 01a1fc70 6a2a9351 webengine+0x9213
> 08 01a1fce4 6a2a9456 webengine+0x9351
> 09 01a1ff48 6a2a4aca webengine+0x9456
> 0a 01a1ff64 6a2a9086 webengine+0x4aca
> 0b 01a1ff80 6a2a400c webengine+0x9086
> 0c 01a1ffb4 7c80b683 webengine+0x400c
> 0d 01a1ffec 00000000 kernel32!BaseThreadStart+0x37
>
>
> **Current Stack State**
>
> Other information: Thread is throwing an exception. Checking for known
> issues.
> Thread Type: HTTP Listener
> # ChildEBP RetAddr
> 00 01a1c218 77d49418 ntdll!KiFastSystemCallRet
> 01 01a1c250 77d561c6 USER32!NtUserWaitMessage+0xc
> 02 01a1c278 77d6a92e USER32!InternalDialogBox+0xd0
> 03 01a1c538 77d6a294 USER32!SoftModalMessageBox+0x938
> 04 01a1c688 77d95fbb USER32!MessageBoxWorker+0x2ba
> 05 01a1c6e0 77d96060 USER32!MessageBoxTimeoutW+0x7a
> 06 01a1c714 77d80577 USER32!MessageBoxTimeoutA+0x9c
> 07 01a1c734 77d8052f USER32!MessageBoxExA+0x1b
> 08 01a1c750 100206d4 USER32!MessageBoxA+0x45
> WARNING: Stack unwind information not available. Following frames may
> be wrong.
> 09 01a1ef08 7815e3b2 bmnet!WSPStartup+0x1474
> 0a 01a1ef18 7c86304e MSVCR80!__CxxUnhandledExceptionFilter+0x63
> 0b 01a1f5b4 7c83ab20 kernel32!UnhandledExceptionFilter+0x1ec
> 0c 01a1f5bc 7c839b09 kernel32!BaseThreadStart+0x4d
> 0d 01a1f5e4 7c9037bf kernel32!_except_handler3+0x61
> 0e 01a1f608 7c90378b ntdll!ExecuteHandler2+0x26
> 0f 01a1f6b8 7c90eafa ntdll!ExecuteHandler+0x24
> 10 01a1f738 7c918e74 ntdll!KiUserExceptionDispatcher+0xe
> 11 01a1f7f8 7c918e74 ntdll!_LdrpInitialize+0x25b
> 12 01a1f884 7c911538 ntdll!_LdrpInitialize+0x25b
> 13 01a1fac0 65f1730b ntdll!RtlAllocateHeap+0x925
> 14 01a1faf0 5aa46ea4 ISATQ!AtqTransmitFile+0x9e
> 15 01a1fb20 5aa4861f w3svc!CLIENT_CONN::TransmitFile+0x4b
> 16 01a1fb54 5aa5801e w3svc!HTTP_REQ_BASE::TransmitFile+0xa8
> 17 01a1fb98 5a8567c9 w3svc!WAM_REQUEST::TransmitFileInProc+0x1a2
> 18 01a1fbf4 5a8579ed wam!WAM_EXEC_INFO::TransmitFile+0x11c
> 19 01a1fc1c 6a2a9213 wam!ServerSupportFunction+0x442
> 1a 01a1fc70 6a2a9351 webengine+0x9213
> 1b 01a1fce4 6a2a9456 webengine+0x9351
> 1c 01a1ff48 6a2a4aca webengine+0x9456
> 1d 01a1ff64 6a2a9086 webengine+0x4aca
> 1e 01a1ff80 6a2a400c webengine+0x9086
> 1f 01a1ffb4 7c80b683 webengine+0x400c
> 20 01a1ffec 00000000 kernel32!BaseThreadStart+0x37
>
>
>
>
> Thread ID: 38
> System Thread ID: 14b0
> Kernel Time: 0:0:0.0
> User Time: 0:0:0.0
> Thread Type: Other
> # ChildEBP RetAddr
> 00 01a5ff4c 7c90e31b ntdll!KiFastSystemCallRet
> 01 01a5ff50 7c80a746 ntdll!ZwRemoveIoCompletion+0xc
> 02 01a5ff7c 6a2a3fbb kernel32!GetQueuedCompletionStatus+0x29
> 03 01a5ffb4 7c80b683 webengine+0x3fbb
> 04 01a5ffec 00000000 kernel32!BaseThreadStart+0x37
>