I installed Visual Studio 2019 last night with SQL Server components, and now whenever I try to view web pages in Chrome, I get a connection reset error. I assume it has something to do with IIS. I tried uninstalling IIS Express, but that didn’t seem to help. I checked all my connections and everything seems to be fine. I can ping google in the command line, but for some reason I just can’t view the web. Does anyone have any ideas?
Maybe your services are turned off, try entering the task manager with CTRL + ALT + DELETE, and look for SERVICES, the SQL SERVER server you are using, and check if it is stopped.
VS2019 install with SQL Server components causes err_connection_reset
when viewing the web
This is not expected behavior after VS installation. Maybe something in that installing process modified your IE settings.
Try resetting all IE options(IE options=>Advanced=>Reset) and reinstall Chrome browser.
I fixed this by removing all Visual studio installations and reinstalling VS 2019.
Related
I have installed Visual Studio 2017 on a Windows 10 PC. I thought this would also install IIS Express. However, when I browse to localhost I get a localhost refused to connect error. The same error occurs when I try to browse to the http://localhost:49247 url for my solution in visual studio. I have tried installing IIS Express 10 separately and also tried turning on the IIS features in windows 10, but with the same results.
I've also tried changing the port number and deleting applicationhost.config, as suggested elsewhere on this site, but these didn't work for me either.
Can anyone tell me what I'm doing wrong?
I've found quite a few posts of similar issues, but I still am having trouble getting this resolved.
I have a TFS repository I know I have access to with my Microsoft account. I'm currently using it on my laptop as I'm typing this, and if I go there via chrome, I am having no issues.
I finally got my desktop up and running again, and after a fresh windows/VS 2013 install, I am getting unauthorized when trying to connect to team projects. I'm using the same credentials that are being using through Visual Studio on my laptop, and in chrome.
Does anyone have any idea what could be causing this?
Please use below ways to narrow down the issue.
Try to disable the Antivirus software on your desktop
Try to disable your firewall on your desktop and try again
If you are using VPN on your desktop, please disable it.
Clear TFS and VS cache in your desktop.
Clear the account info from the Credential Manager (Control Panel) both in
your laptop and desktop, then try it again.
Team -> Manage Connexions... -> re-select your project
Close Visual Studio > Reboot all servers in the Topology.
Please can someone help me, am getting this message whenever I start my windows 7 system:
Visual Studio Just-In-Time Debugger.
An unhandled exception ('System.IO.FileNotFoundException') occured in IAStorDataMgrSvc.exe [5824]. Just-In-Time debugging this exception failed with the following error: No installed debugger has Just-In-Time debugging enabled. In visual Studio, Just-In-Time debugging can be enabled from Tools/Options/Debugging/Just-In-Time.
I have uninstalled Visual Studio yet this challenge persists.
Because of the above error I can no longer properly use my wamp server.
Did you also install IIS when you installed Visual Studio.
IIS and the APache in WAMP are both web servers and both want to use TCP port 80. IIS is probably staring automatically and getting port 80 first so Apache cannot have it.
If you are not using IIS then uninstall it as well.
If you are then you will have to change IIS and probably some other bits so they dont start automaticaly. Do this on the Services dialog.
Ive got the same problem.
I dont know about the relationship betwin Visual studio and Wamp, and I somehow doubt its related, sence at the instal of VS2017 Ive had already instaled Wamp.
What I do know is that, even in offline instal mode this problem persists, my gues is that JustINtimeDebugger got locked.
My solution:
I killed the PowerShell.exe process (under vs_instalershell ) using File Explorer and install it later.
Note, this does not solve the problem it just bypass it.
Theoreticaly, next you should try to unlock the RegisterJustInTimeDebugger.ps1 file from C:\ProgramData\Microsoft\VisualStudio\Packages\Microsoft.VisualStudio.Debugger.JustInTime,version=15.0.26208.0 with (consider changing the path if needed):
Unblock-File -path "C:\ProgramData\Microsoft\VisualStudio\Packages\Microsoft.VisualStudio.Debugger.JustInTime,version=15.0.26208.0"
Altenative:
Update the System Variable __PSLockDownPolicy to 1 or delete it if it exists.
But I have failed to make it working even now.
I'm trying to run an MVC 4 project in IIS Express 8 (because that is apparently what comes with VS 2012) and every time I've tried to run it from VS, I get the following error.
Unable to launch the IIS Express Web server.
14:53:48: Error: Cannot initialize OLE
14:53:48: Error: Cannot initialize OLE
Launching IIS Express through WebMatrix seems to work fine. I've tried uninstalling and reinstalling, but nothing seems to work. Any suggestions?
I'm not sure this will help but it worked for me. After uninstalling IIS make sure you delete the IISExpress folder (on Windows 7 this is located in My Documents\IISExpress). This is where the IIS config files live and if you don't delete it after the uninstall the newly installed IIS will end up using the old config files.
I didn't see the OLE error you're having, but everything else is similar...
checking the event view, I was seeing an IIS error preloading .NET 4.0.30306. All the config files were pointing at 4.0.30319.
But... under my Windows/Microsoft.NET/Framework/ (and Framework64) I had what appeared to be a partial installation of a v4.0.30306.
Deleting both those .30306 folders and rebooting fixed the IIS Launch issue for me.
The environment:
Clean (new) install of Windows 7 64bit.
Clean (new) install of Visual Studio 2010 Professional (10.0.30319.1).
Windows Update is up to date.
The problem:
I cannot start the debugger on Visual Studio 2010 (hit F5): 'Unable to start debugging on the web server. Unable to connect to the web server. Verify that the web server is running and that incomming HTTP requests are not blocked by a firewall.'
However, 'attach to process' (what I usually do) does work, but it is painfully slow to start (Visual Studio 'thinks' a lot of time before the debugging is actually enabled).
On the same hardware, running VS 2008 on good old Windows XP (32bits), this problem never happened.
Trying to debug a site running under the ASP.NET Development Server also fails: 'Unable to connect to ASP.NET Development Server.'.
There are plenty of web pages about these errors (many very outdated and does not apply to my environment), none of them worked for me.
Notes:
No matter if I run Visual Studio as Administrator or not. The problem is
the same.
The problem happens even when running a brand new blank IIS web site, either created as 'localhost/something' or 'sample.local'.
If I create a 'File System' web site (to try ASP.NET Development Server), when I hit F5, the server starts, but after a long wait Visual Studio says 'Unable to connect to ASP.NET Development Server.'
The 'hosts' file has an explicit 127.0.0.1 entry for 'localhost' and for 'sample.local'
It's the same problem either running .NET 2.0 or 4.0.
It's the same either configuring the application pool with or without 'Enable 32-Bit Applications' true or false.
It's the same either configuring the application pool is classic or integrated mode.
In a desperate attempt, I've added all the IIS 6.0 legacy 'features' stuff (not needed!) and doesn't helped at all.
I don't now what else I can try.
Thanks.
OMG!, I'm so stupid. The most oblivious thing was truly wrong. There was a wrong rule in the firewall. Therefore, even being in 'interactive mode' (as it is was always set), the connection was denied.