The IIS Debug Diagnostics Tool installs the IISCrashHangAgent. What service is hosting the agent?
IIS Crash/Hang Agent is an obsolete tool, which still is available here
http://www.microsoft.com/downloads/details.aspx?familyid=01c4f89d-cc68-42ba-98d2-0c580437efcf&displaylang=en
But to debug IIS problems, now you should use DebugDiag
http://www.microsoft.com/DOWNLOADS/details.aspx?FamilyID=28bd5941-c458-46f1-b24d-f60151d875a3&displaylang=en
Related
We have a WCF Service that we either have to host in a Windows Service or IIS. This is a commercial application that will be installed on consumer pc's running for example Win7 Home.
In my opinion IIS on Win7 is by Microsoft only meant for development and/or testing. Activating IIS on a consumer pc shouldn't be a real option.
So my question is: Is it a real option to host a WCF service in IIS in a commercial application on a simple consumer pc?
I use MSDeploy for deploying asp.net sites to servers with IIS. I also use MSDeploy for deploying Windows Services to the same servers that have IIS.
My MSDeploy agents listen on https://computername:8172/MSDEPLOYAGENTSERVICE
I'm evaluating if it's feasible to deploy a Windows Service to a machine that does not have IIS installed.
Does the MSDeploy agent require IIS or can the agent run without it?
I have tested this in my own environment. MSDeploy can be installed without IIS. It works for deploying Windows Services to a machine that does not have IIS on it.
IIS 7.5 is installed on two servers (both Windows Server 2008 R2) with Web Deploy 2.0 installed (to enable me to Publish from Visual Studio 2010.) Publishing straight from VS requires the Web Management Service be running on the server. I've been publishing to the first server for months, no problem. The second server has just been spun up (not by me) but as far as I can tell has all the same versions of components (OS, IIS, Web Deploy). However, on the second server the Web Management Service isn't installed. There's a key difference:
Web Deploy 2.0 options available on the first server:
Web Deploy 2.0 options available on the second server:
Why is there a difference between the two?
(Follow-up: I tried the Web Deploy 3.0 installer and encountered the exact same dialog as the second server, above, except that it said "3.0" instead of "2.0".)
Verify the proper IIS roles are installed on your new server. In the Server Manager console, under Web Server (IIS), verify the following roles are installed:
Management Tools
IIS Management Console
IIS Management Scripts and Tools
Management Service
Then try re-running your Web Deploy installer. I think you'll find you get the options you desire.
We are developing an application that we are deploying to Azure. It needs to work with a specific machine configuraiton. We we have this configured as a VM which developers can run locally.
However to test the VM configuration we need to publish to Azure and access it on a live Azure instance. Is there anyway to allow a local VM to get access to the Azure environment IIS on the developers machine? It doesn't seem to show up in IIS Express so I guess it isn't the same as a normal site?
Also is it possible to configure an Azure environment locally for testing. We want to host test applications for internal use and don't want them run on developers machines. We would like to run them on a server in the office.
Any ideas?
Thanks
I think that the answer to this question will outline the general guidelines you could follow to enable your environment.
Windows Azure Emulator has its own load balancer simulator which bind to socket 127.0.0.1:81 (most of the cases, if port 81 is free). If the Azure project is developed with Azure SDK 1.3 or later with Full IIS enabled, then the Azure Emulator (for versions 1.3 ~ 1.6) will use local IIS to host the sites. IIS Express is not involved in any way with the Azure project. If you happen to run IIS Express, then most probably you have set up your web application project as a StartUp project in the solution. The correct way to locally debug Windows Azure applications is to use the Cloud Project as a startup project.
Please kindly update your question, if there is some doubt or confusion after checking the mentioned related question.
We have a requirement where we need to have some web services running on a server machine but it does not have IIS available. I came across this article on running asmx without IIS and many other sites/blogs have mentioned this article as well.
http://msdn.microsoft.com/en-us/magazine/cc163879.aspx
Could somebody offer alternatives to above to run asmx web services without IIS installed?
Other option i could find was Cassini - http://ultidev.com/products/cassini/
Windows Azure! That is precisely what it was designed for... it’s cheap and reliable!