-
Posted to
IIS7 - General
by
fabioy
on
06-02-2009, 7:07 PM
The "net.tcp" sites will always report "Unknown" because the site status only knows or can report about the "http" protocol. Apologies for the confusion in the UI.
Also, the "MSMQ Listener Adapter" not running is fine, as long as you're not using MSMQ for WCF processing.
Finally, the config error ...
-
Posted to
IIS7 - General
by
fabioy
on
06-02-2009, 6:59 PM
A1) If it's a module (and not a request handler), then the module will be loaded and run at the time a request arrives. Note, though, that this is also dependent upon the "precondition" set for the module. Take a look at this entry for more info: http://blogs.iis.net/thomad/archive/2006/11/04/precondition-what.aspx
A2) ...
-
Posted to
Troubleshooting
by
fabioy
on
06-02-2009, 6:47 PM
I'd discount the registry read failures as the cause of the problem. Most likely cause of worker process crashes are faults within the user code. Take a look at the dumps and/or run the worker process(es) under a debugger and see if the call stack of the failure give you more info.
If after this analysis you feel this is a product ...
-
Posted to
Configuration & Scripting
by
fabioy
on
04-16-2009, 4:51 PM
Most likely cause is that you have the IISADMIN service running, but the W3SVC service is not. That could result in the App Pool State returning zero.
Hope this helps.
-
Posted to
IIS7 - General
by
fabioy
on
03-19-2009, 4:34 PM
If you wish to use your program (and here I'm assuming it's a request handler), then you need to create a handler mapping to ensure that the requests are routed to it. For example, a "*" mapping for it would ensure that all requests to the app would get to it.
There may be an easier way to do this, though, via the WebDav ...
-
Posted to
ASP.NET Administration
by
fabioy
on
03-13-2009, 6:14 PM
There are a couple of ways to solve the problem:
If the ASP.Net application expects to be running under an application node, then go to the IIS MMC and mark the virtual directory as an "Application" directory and ASP.Nets should be happy again. This is especially important if the app contains a "global.asax" file, ...
-
Posted to
IIS7 - Known Issues and Workarounds
by
fabioy
on
03-13-2009, 6:06 PM
The worker process is crashing, thus causing the application pool to shutdown eventually. You need a bit more information to find out the cause of this.
If you remove all files related to the app from your virtual directory and only leave a simple .htm file, does the worker process serve the page? If so, some ...
-
Posted to
IIS7 - Publishing
by
fabioy
on
03-13-2009, 5:53 PM
The unrecognized element typically means that either the FTP schema file is not being read or was not installed properly. I'd try the following:
Try resetting all IIS services (i.e. "iisreset") and see if that fixes the issue.
If that doesn't work, uninstall and reinstall the FTP 7 bits. Try doing that while ...
-
Posted to
IIS7 - General
by
fabioy
on
03-13-2009, 5:49 PM
An alternative would be to call the native "SetDllDirectory" API from your app before the managed code accesses the C++ dlls. This would effectively add the directory to the dll search path for the process before the next LoadLibrary call.
Here's the MSDN link to it: http://msdn.microsoft.com/en-us/library/ms686203.aspx
Hope ...
-
Posted to
IIS7 - General
by
fabioy
on
03-13-2009, 5:43 PM
This may be a permission issue on the DCOM object that is used to communicate with the WAS service. Try the following:
Open the DCOM configuration tool (run "dcomcnfg").
Navigate down to "Component Services"->"Computers"->"My Computer"->"DCOM Config"->"IIS W3 ...