By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
424,949 Members | 946 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 424,949 IT Pros & Developers. It's quick & easy.

appsettings in web.config hangs aspnet_wp

P: n/a
Hi,

I have a rather unusual problem.
I have a very simple ASP.NET application, basically hello world type.
I created it with Visual Studio 2003 and am running it in debug mode.
It runs fine until I put the <appSettings> section in its web.config file
or machine.cfg.
After that the application starts, the web browser opens, it connects and
then shows waiting for page to open. At this point it just sits there
forever. I cannot close the page or terminate the application. i cannot
terminate devenv(VS2003). A worker task is running (aspnet_wp), it will not
terminate either. If I open another browser window, it hangs too (even
trying
to open msn.com).
The only wat to continue is to force power off my machine and restart.
IIS is running on the local machine and that is where I am running VS from.

I have put a break point on the initializecomponent call, it never gets
there.

if I delete the appSettings section, it works ok

ASPNET_WP.exe is running and cannot be killed, I noticed
another process dllhost.exe (not sure if anything to do with problem. If I
terminate dllhost.exe, within seconds it is back.

Thanks for any assistance,

--
Robert Pfeffer
VP of Technology
Sun Valley Systems, Inc.

Nov 19 '05 #1
Share this Question
Share on Google+
4 Replies


P: n/a
Perhaps you could post the contents of your appsettings so we could see what
the error is?

Probably a small syntax or XML error.

"Robert Pfeffer" <rm*@community.nospam> wrote in message
news:0E**********************************@microsof t.com...
Hi,

I have a rather unusual problem.
I have a very simple ASP.NET application, basically hello world type.
I created it with Visual Studio 2003 and am running it in debug mode.
It runs fine until I put the <appSettings> section in its web.config file
or machine.cfg.
After that the application starts, the web browser opens, it connects and
then shows waiting for page to open. At this point it just sits there
forever. I cannot close the page or terminate the application. i cannot
terminate devenv(VS2003). A worker task is running (aspnet_wp), it will
not
terminate either. If I open another browser window, it hangs too (even
trying
to open msn.com).
The only wat to continue is to force power off my machine and restart.
IIS is running on the local machine and that is where I am running VS
from.

I have put a break point on the initializecomponent call, it never gets
there.

if I delete the appSettings section, it works ok

ASPNET_WP.exe is running and cannot be killed, I noticed
another process dllhost.exe (not sure if anything to do with problem. If
I
terminate dllhost.exe, within seconds it is back.

Thanks for any assistance,

--
Robert Pfeffer
VP of Technology
Sun Valley Systems, Inc.


Nov 19 '05 #2

P: n/a
Hi Robert,

I think Ken's suggestion is reasonable, maybe you can share the
modificaiton in your web.config so that we can have a look. Generally the
asp.net runtime will check the configure file when the application starts ,
so the breakpoint in your page's method will never be hit.

Thanks.

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.)

Nov 19 '05 #3

P: n/a
Hi Ken / Steve,

Thanks for responding.

The appSettings entry is:

<configuration>
<appSettings>
<add key="commandline" value="A0471001 SASLMF P0515KFG 0002 SASLMF
P0515KFG SVS99540"/>
</appSettings>
<system.web>

A window forms application can access the appsettings (when they are in
machine.cfg).

I tried uninstalling and reinstalling Framework (with SP1). No change.

Once the app hangs, I can no longer connect to any website.

Robert Pfeffer

"Steven Cheng[MSFT]" wrote:
Hi Robert,

I think Ken's suggestion is reasonable, maybe you can share the
modificaiton in your web.config so that we can have a look. Generally the
asp.net runtime will check the configure file when the application starts ,
so the breakpoint in your page's method will never be hit.

Thanks.

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.)

Nov 19 '05 #4

P: n/a
Hi Robert,

Thanks for your response. Seems the <appSettins> keys are very simple, I've
testing on my own local machine (put the appSettings DATA in both
machine.config or web.config) but didn't reproduce the behavior. I'm
thinking the problem is likely project specific. Can you verify that the
problem just go away if you remove those appsettings items? And what are
those keys's useage, used in your web application?

Also, I think you can still try the following things:
1. Does the problem only occurs when you launch the application in VS.NET,
what about visit the page outisde VS.NET in IE?

2. Try creating a new simple web application with a empty page to see
whether it suffers the problem.

3. Adding breakpoint or use other trace means to see whether the web
application's global Application_Start event has entered.

4. Checking the IIS log and eventlog to see whether there is any useful
info.

In addition, I've checked some former issues and foudn that some cases
similiar to your problem, some of them are caused by the .net database
provider that eat the CPU TIME and make the application hang.
And from the nature of this issue, it would require intensive
troubleshooting such as dump analysis which would be done quickly and
effectively, I suggest you consider contacting the Microsoft Support
Professional through Microsoft Product Support Services if you feel this an
urgent issue.

Thanks.

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.)

Nov 19 '05 #5

This discussion thread is closed

Replies have been disabled for this discussion.