IISExpress fails with message "failed to translate IP address + Hostname to Site Id" - iis-express

I have a .NET 4 webservice running on IIS Express 7.5 on a 2008 Server
the service runs fine for a couple of hours or even a day but after some time the process crashes with an error message failed to translate IP address + Hostname to Site Id which is displayed red in the console output.
I streamlined the applicationhost.config to only contain a single site and the binding is only to an ip address and localhost but no success.
I use this command line to start IISExpress
iisexpress.exe /config:c:\myconfig\applicationhost.config /site:mysite
First of all a solution for the error would be great but any information on how to optain more data for this error would also help. I already checked the eventlog but can't find anything.

Well, I upgraded to IISExpress 8 which runs stable now.
I did not know what caused this issue, but I belive it was somehow related to heavy load on the server since to often (but not exclusively) happend during a scheduled backup.

Related

Unable to render HTML. Unable to access URL. COM error 800c0019 in FACILITY_INTERNET. The drive cannot locate a specific area or track on the disk

I am getting the above error message in production when trying to call the AddImageUrl section of ABCPdf (version 10). This started occurring yesterday just after midday my hosting provider assures me nothing has changed I am the only developer on the project as was working on something else entirely.
The URL provided in the stack trace can be accessed in IE on the web server without any error messages (including SSL). There is also a UAT environment on the same web server in which the PDF works, the UAT environment is identical in code and application pool settings, the only difference is the web address and database.
The HTML the PDF is calling can take a little time to come up on first load. Given that data is different I have increased the timeout from 15 seconds to 2 minutes.
I have arranged a reboot to see if that fixes it, but I have run out of things to check.
Edit: I did think of one further check, could I add the image of a page not on the site (https://www.google.co.uk/), doing this resulted in the same error so it appears not to be a blocking issue on the worker process.
—
Edit2: switched to the gecko engine and it is now working.
You can sometimes get this error if the web browser within Abcpdf cant access the URL.
On the webserver add the URLs directly to the local machine hosts file
C:\Windows\System32\drivers\etc\hosts
The entry should look something like this
127.0.0.1 example.com

IIS failing after machine name change

If I change the machine name of a Win2016 server (as a precursor to putting it on the domain) this causes the 'Default Website' in ISS v10 to fail.
I have not created any other website, virtual directory or AppPool. There are just the objects and settings that IIS creates when it is first installed.
As soon as I navigate to 'http://localhost' in a browser the 'DefaltAppPool' will stop and several errors will be generated in the 'Event Viewer' (from the 'WAS' source in the 'System' log and the 'IIS-W3SVC-WP' soruce in the 'Application' event log). These errors indicate the 'worker process failed to initalise and therefore could not be started'.
If I change the machine name back to the old name then the IIS appPool works as normal.
It suggest that the 'ApplicationPoolIdentity' is somehow hard-coded to a specific machine name.
I have also tested a Win2008 R2 VM with IIS v7 and the same issue occurs. I have also found this with another Win2016 VM that has never had IIS installed before.
It seems that even if IIS has never been installed before if the machine's name has been changed at any time IIS will not work.
Although I am familiar with IIS I am not an expert but I would expect that when I have installed IIS as a brand new role that the 'Default Website' and 'DefaultAppPool' that are created as standard should work without any further configuration.
Can you please advise how I can investigate / resolve this ?
============ Update 07-12-2018 =================
I have been doing some more testing and I think I may have found the trigger (although cause & resolution still unknown).
The original name of the unchanged Win2016 VM was 'WSVR2016-02016' and I tried changing the name (but keeping the VM in a workgroup) and after each change restarted the machine then when it came backup I made sure the IIS 'DefautlAppPool' was started in IIS Manager, visited "http://localhost" in the Chrome borwser and then checked the IIS Manager to see if the AppPool had stopped.
I tried each of the following names (all still in a Workgroup) and they all worked:
WSVR2016-O2018 |
WSVR2016-O2018T |
TEST-PAL-AD |
TEST-PAL-ADV2
I then tried changing the networking of the VM to Bridged rather than NAT but keeping the last machine name - still it worked.
I then tried, with the same 'TEST-PAL-ADV2' machine name, connecting the VM to our domain and when I went to 'http://localhost' the IIS AppPool stopped !
So it looks like connecting to the domain is what causes the problem - but how ?
(I did notice that each time I changed the machine name the name of the server retained the old name in IIS. So the top 'connection' node was saying "WSVR2016-02016 (TEST-PAL-ADV2\Administrator" - but it did the same through all the name changes and did not stop IIS working)
There may be settings or policies pushed out by the domain that are preventing the ApplicationPoolIdentity from running. I would suggest changing the DefaultAppPool pool to run as local system and inquire with your domain admins regarding any policies that might be interfering. You may also be able to discern some of that yourself by running gpresult

zend studio debugger timing out

I am attempting to setup a remote profiling session with a server. I have downloaded the latest version of Zend Debugger, and have installed it on the server with the following setup - http://puu.sh/3ezyh/39247f2f15.png . With my local machine, I have setup a putty session to the remote server, and forwarded port 10137 as per the KB article listed on zend.com.
I am able to debug the remote server without a problem, however when I goto profile the page, the page will process, then a dialog will pop up with a "Waiting for the debugger's response" message. After approximately ~20 seconds, I get the following error: http://puu.sh/3ezDk/57f6dc1bb5.png .
However, there will be profiling information displayed , as well as execution statistics, but no execution flow, almost like it's getting part of the data but not all of it.
The page in question does have anywhere from a 20-30 second page load (which is why I'm tyring to profile to find the problem.)
The only error I can find is in the server's error_log, which just says "[Zend Debugger] Cannot send message"
Is there anyway to diagnose why I'm not getting the complete response?
I wonder if it is getting your IP address and trying to send directly to it instead of over the local forwarded connection. You might need to set your host IP to 127.0.0.1 as the address like in http://screencast.com/t/7lheaOlx. If that doesn't work I would say do a
tcpdump port 10137
And see what you can see. Also, depending on your local OS you may have a firewall blocking access to your instance of Studio.

Test Controller exception: No such host is known

I'm getting following errors on the test controller machine, when I'm trying to run CodedUI Tests remotely:
(QTController.exe, PID 3032, Thread 12)
ControllerDeployment.DoDeployment: System.Net.Sockets.SocketException
(0x80004005): No such host is known
During controller and agent configuration no errors came up. And when I go to Manage test controller dialog in Visual Studio I can see all the agents active. But when I try to execute any CodedUI test remotely it's hanging forever.
Not sure if it's connected with the fact that I've upgraded client/controller/agents to 2012 versions recently, but I've started seeing the problem only after this upgrade.
From Microsoft KB 2643086:
This issue occurs because the test agent computer sends its Network
Basic Input/Output System (NetBIOS) name instead of sending its Fully
Qualified Domain Name (FQDN) name to the test controller computer.
When the DNS server of the test controller computer does not have the
IP address mapping of the NetBIOS name of the test agent computer, the
issue that is described in the "Symptoms" section occurs.
You should ensure you are using fully qualified domain names (FQDN).
There is also a hotfix is available from Microsoft. However, you have to contact Microsoft Customer Support Services to obtain the hotfix.
I had similar problem, still not completely resolved but a workaround is to install Visual Studio on controller box and keeping result DB on same box.
Mostly the issue is restriction / firewall on VPN which might be blocking incoming traffic on TCP ports of machine / laptop.

.net 3.5 IIS7.5 website can not be debugged - "Specified cast is not valid."

I'm trying to migrate an IIS6 site to 7.5, and in the IIS Manager's status section, I see "Unknown:Specified cast is not valid. (http). I've configured a base site that's just binding on port 80 to http. This doesn't stop the site from running. It does stop me from debugging though. When I hit F5 in VS, I get: "Unable to start debugging on the web server. Specified cast is not valid.". Digging into the EventViewer, I see a number of Informational messages that say:
Counter 0 of instance({some guid},[some number]_[AppPoolName], 0) could not be modified. Error: "The parameter is incorrect."
Other versions of the event list different Counter #'s. The user on all of these messages is IIS APPPOOL[AppPoolName] and the source is Diagnosis-PCW. Event ID: 16
That's the info I think is relevant. And now here's everything else that might be:
I have VS 2010 Beta 2 installed.
Win 7 x64, the site has a number of custom modules and handlers we've written, one of which was our own MVC implementation (MS's was not ready at the time). I don't think this is the issue, because I at one point had a standard MVC site on there that was giving me the same error.
Thoughts?
I'm not sure if this will help but here are two things to check/try out:
The application pool's managed pipeline is using the 'classic' mode.
32-bit applications are enabled on the application pool. (if necessary)

Resources