m12-073 update causes IIS service unavailable - windows

I am a developer. I have created a web site and service with Visual Studio 2010. I am running a fully patched Windows 7 computer.
I need to be able to debug it with devices other than my dev computer hitting the web server. I installed IIS 7.5 and configured everything to be working. I was able to debug when another device hit the web site on this dev computer.
That was yesterday. This morning I started up my computer and there was an update from Microsoft. m12-073. It mentioned IIS.
When I started working on this project today after doing the update now I get a service unavailable (503) error on any computer or device NOT the dev computer. The dev computer still works fine.
The only change from yesterday and today is the update and rebooting.
I tried uninstalling the update and that didn't fix it. I tried a system restore to before the update and that didn't work.
I am now stumped. It worked yesterday and doesn't work today with only the update being the change.
Help?

Related

IIS Express Remote access with Visual Studio 2019

I don't remeber this being an issue before, and many threads are rather outdated now.
On my Windows 10 installation VS 2019 hosts my project at http://localhost:58402 just fine.
However when I go to change the url under Properties > Debug > App URL to 0.0.0.0:58402 I get the error:
Cannot connect to web server IIS Express
What I have tried:
Running VS 2019 as admin
Restarting computer
Deleting hidden VS folder
Modifying launchSettings.json in my API project properties folder
I can change the port just fine. But as soon as I change localhost to 0.0.0.0 the error occurs.
Update:
I have been using the NPM package iisexpress-proxy with great success now as a daily driver for 5 months now.
Had some difficulty with CORS, but disabling that for local debugging allows me to do everything I would expect.
https://www.npmjs.com/package/iisexpress-proxy

HTTP verbs PUT and DELETE stopped working

I have a ASP.NET Web API project where I use PUT and DELETE frequently. Sometime during the last couple of months PUT and DELETE stopped working. The web.config is still the same and the verbs works fine on my other machine.
I haven't worked with the project during this time. The only things I recall I have done is the Windows 10 anniversary update and a couple of Visual Studio updates, but I have done the same updates on my other machine.
During this time my WCF services stopped working too. In attempts to get them to work I reinstalled some Windows components. I have installed everything that has to do with IIS.
Can this verb problem have anything to do with missing Windows components? I have no idea what it can be.
Apparently I managed to install support for WebDav publishing when I reinstalled the Windows features for IIS. I removed it and got my PUT and DELETE back!

TFS 2010 Connection Issue

I have been working on this weird issue for a few days now and I'm going to pull my hair out! I have a PC and a server in the default WORKGROUP. I created a new collection and a new project and now I'm trying to connect from my PC to the server via VS2010. When I go to the connect team project dialog box and input my info it doesn't connect!
If I copy the preview http and input that into the browser it works fine! It asks for credinitals and the project comes up without an issue. For the fun of it I installed VS2013 team explorer and it pulls it up without an issue. What's going on here?
In the end I ended up going with VS2013. I'm no longer having this issue.

Can no longer access TFS from workstation

All of the sudden I can no longer access my TFS 2010 server. It is on the same network as my laptop. I have made no changes to anything. I worked on it one day and then the next day VS2012 and 2010 can't connect. I can also not connect to the web UI from the outside either.
I have VS2010 installed on my server and it can connect just fine. I have looked at my services on my laptop and found nothing about TFS or Visual Studio.
What I have tried.
Restarting the server
Restarting my laptop.
Resetting the TFS user account on my server.
Restarting the web server that TFS runs under.
Checked the server logs for errors.
ipconfig /flushdns
Using VS2010 and VS2012. With all updates.
Turned off Bitdefender firewall.
Firewall on server is turned off.
Ping server name. This works.
RDC into server via same server name. This works.
Connecting to TFS from VS2010 on the server. This works.
I would say this is a DNS issue but I can get to my server just fine except when TFS is involved. It seems like there is a communication issue from an outside source to TFS.
Any ideas on why access from any other source than the server would just stop?
I use Bitdefender too and for my final hope to solve this problem, I went to Control Panel > Uninstall a program > and Repair the Bitdefender, TFS came back!
While Bitdefender was repairing, I was able to access TFS Web site in the same network. Restarted Windows and the problem didn't show up again.
Hope this helps!

Intermittent IIS8/Visual Studio 2010 debugging issue

I have an intermittent issue when trying to debug local IIS sites.
Visual will hang and eventually displays the error:
The web server did not respond in a timely manner. This may be because another debugger is already attached to the web server
If I wait a minute and hit "Start Debugging" again it will work (sometimes I may get the error several times but it eventually works).
There is nothing in the Event Viewer around the times I try to debug.
The app pool is .net V4.0 Integrated.
I am running Windows 8 Pro with IIS 8 and Visual Studio 2010.
Also its a site using EpiServer 6 R2.
I have tried IISReset, stopping/starting the site, closing and reopening Visual, rebooting my machine. None of that seems to make a difference, its hit and miss whether the solution will debug or not.
Once the solution is debugging, it runs fine without issue. Until I stop debugging and try and start debugging again.
The site runs fine in all other aspects, its only when I try to debug.
So... I never fixed this issue, but have since upgraded to a solid state drive. So I now have a fresh install of Windows 8 Pro and Visual and the issue has not resurfaced.

Resources