I attempted to run my web service through visual studio. I faced an issue like :
--------------------------- Microsoft Visual Studio --------------------------- Unable to launch the IIS Express Web server. Failed to register URL "http://localhost:63591/" for site "xxxxxx" application "/". Error description: The process cannot access the file because it is being used by another process. (0x80070020) --------------------------- OK ---------------------------
I saw the task manager and found that PID 4 is used by System and its Description is
NT Kernel & System.
So I tried to stop the
All dependency services stopped. But I am facing an issue in stopping http service like
The service is starting or stopping. Please try again later.
So, I tried to stop and start the service manually. But the End process is disabled. It will be helpful if anyone could help with this issue
ERROR_SHARING_VIOLATION, which in the case of IIS Express (or IIS) means that the port that it is attempting to listen on is being used by another process.
netstat command to find out which application is using the port.
netstat -ao | findstr <port_number_to_search_for>
a parameter tells netstat to display all connections and listening ports.
o parameter tells netstat to display the process ID associated with the connection.
Running the above netstat command will produce output such as:
C:\>netstat -ao | findstr 4026 TCP 126.96.36.199:4026 cs-pc:4026 LISTENING 9544
The last number displayed (9544 here) is the process ID.
I had a similar issue when trying to run a project from Visual Studio 2019 on Windows 10.
The application could not start because the port was apparently being used by another process. However, the
netstat command showed that the port was not being used by any application.
After spending 2-days Googling I found a solution that worked for me. The port I was trying to use was in the excluded port range which you can see by running the command:
netsh interface ipv4 show excludedportrange protocol=tcp
The culprits that reserved these ports in my case were Docker for Windows and Hyper-V
I uninstalled Docker (as I did not need it) and disabled Hyper-V. To disable Hyper-V: Go to: Control Panel-> Programs and Features-> Turn Windows features on or off. Untick Hyper-V and restart the computer.
After the restart the command
netsh interface ipv4 show excludedportrange protocol=tcp showed no ports reserved.
I then added the port for my application to the excluded port range by running the following command from an elevated command line:
netsh int ipv4 add excludedportrange protocol=tcp startport=50403 numberofports=1 store=persistent
Then I reenabled Hyper-V (Docker can be reinstalled if needed) and restarted the computer again.
Hyper-V now reserved its ports without interfering with the port used by my application: Reserved Port Ranges
I had the same Issue. As @Kautsky Lozano mentions above Another application is using that port.
So [for a Windows OS] just:
netstat -ano | findstr <your port number>
The port might be excluded, try this command to see if the range is blocked by something else:
netsh interface ipv4 show excludedportrange protocol=tcp
You can try to unblock the range from the start port for a number of ports (need Command Prompt with Administrator):
netsh int ip delete excludedportrange protocol=tcp numberofports=<number of ports> startport=<start port>
For me I couldn't unblock these, I just got "Access is denied", so I ended up having to pick another port for my site.
I ran into the same problem after we had upgraded a solution from Visual Studio 2012 to 2015. I had come here and ran
netstat only to find that no other application was using the same ports. It turns out I had the same sites with the same ports mapped in the
Users/<username>/Documents/IISExpress/config and the
applicationhost.config in the
.vs folder inside my solution. I should note that the problem didn't start right after the upgrade either. It just start failing consistently one morning. A couple reboots didn't seem to solve the problem either.
Removing the conflicted sites from the one stored in my Documents and restarting Visual Studio solved the problem.
Solution that worked from me is,
To fix this you must temporarily disable the winnat service, this is simply done by running this command (must be run as administrator)
net stop winnat
Start your docker services and start winnat again
net start winnat
After updating Windows 10 and/or Visual Studio 16+ it might happen due to an internal bug that IISExpress fails to register any development website because it no longer accepts
To fix the issue, you just have to register again the binding. To do so, run from an administrative shell the following command:
netsh http add iplisten ipaddress=::
I just had this issue even though netstat did not show any conflicts.
The following fixed it for me:
I had this problem when upgrading an MVC project. I copied over the newer-MVC .csproj over my existing .csproj file then worked back to a fully working Project. What I failed to consider is the existing port number in the old .csproj. The new project had a new port number, yet shared the Project/Assembly Name. That was enough to make IIS Express lose its mind and throw this exception.
Just digging the old port number out of git and changing the IIS Express URL to include it in Project Settings was enough to fix it.
In my case, doing the following did the trick:
When I restarted Visual Studio, it assigned the project a completely new port number and ran perfectly
The easiest first pass at this without getting into the command console is to just shut down all applications (including VS), then launch VS by itself and try it again. There is likely another application like your browser causing the conflict. In my case Chrome caused it and was solved when shutting everything down and restarting VS. I opened Chrome again and everything was fine.
The netstat stuff above is useful, but to me that's only if you can't do what I'm suggesting.
to summarize all the answers. There are 2 solutions. Both worked for me. - Solution #1 Kill the app that uses the same port. - Solution #2 Configure IIS Express to use a different port for your project.
Solution #1 (supposing the port in the error message was 443) Run in the command line:
netstat -ao | findstr 443
TCP 0.0.0.0:443 pe01:0 LISTENING 2904
The last number (thanks to @chris-schiffhauer) is PID to kill. Go to the Task Manager -> Processes -> [Show Processes From All users], Kill a process with PID=2904. In my case, it was VmWare host.
(Supposing message was: Failed to register URL "http://localhost:433/" for site "MyProject.Website0"...).
Open the folloing file in notedpad++:
C:\Users\MY_USER_NAME\Documents\IISExpress\config\applicationhost.config Find in it a line containing:
<site name="MyProject.Website0" id="... ... <bindings> <binding protocol="http" bindingInformation="*:80:localhost" /> <binding protocol="https" bindingInformation="*:443:localhost" /> </bindings>
433 to something else, like
4330 or delete the conflicting
Port numbers do not match
In my case the problem was in my Bindings Tags found in the config file in .vs under my solution folder, the port numbers did not match. The bindings were as follows
<bindings> <binding protocol="http" bindingInformation=":16433:localhost" /> </bindings>
And in my settings i had url set as
So what i did was to delete inside binding and run my web app, then it generated new binding with a different number then i copied the new generated port to my settings, then the error went away.
I ran into this problem in Visual Studio 2019 today and spent 3 hours before finally figuring out the problem. Visual Studio uses 2 files to track the SSL port number, so you have to fix both and you have to fix both while Visual Studio is closed. The two files are the applicationhost.config file that is in the .vs\???\config folder of your solution; and also the .csproj.user folder of your web project. Edit both files and removing the offending configs. Maybe even just delete both files. Then re-open your app in Visual Studio. Good luck!
I was able fix this problem by removing everything from
</site> tags in
<sites> <site> . . ===> remove this content including the <site> and </site> tags. . </site> </sites>
Having just wasted half a day trying to fix this same issue, I felt I should add the solution which eventually worked for me.
netstatindicates that the problematic isn't in use, still try a few others in a totally different range
I've run into this problem before but usually find restarting visual studio, changing ports (increment by 1) or rebooting do the trick. However on this occasion none of this helped, and
netstat wasn't finding a conflicting process. I even reinstalled IIS and visual studio and removed several other programs which I suspected could be interfering. It seemed as though IIS was trying to launch multiple instances of the same site.
Eventually I tried running
findstr. I visually scanned the list of active ports and noticed that although the ones I had tried were not listed, there were a few processes using ports in a similar range. So instead I looked for a range which was free, picked a port number and that seems to now be working.
I'd love to hear if anybody can explain why this might have worked?
Reason for this error that is you give the wrong port number to your application.
just use http ports for your application to run
use the port near to 8080 number, i.e:
to change the port for you application in visual-Studio
goto project properties > web > Server > ProjectUrl
I tried the following already:
I also tried using this but zero results.
netstat -aon | find ":80"
I also tried using but also return zero results.
netstat -ao | findstr
So what I did is delete this "Microsoft.VsHub.Server.HttpHostx64.exe" then my project successfully started and launch in browser. The error was fixed. I am not sure why but it works.
Here is the screenshot:
I had the same problem today, and nothing I found on the internet worked. I have been using port 2057 for years, but suddenly it didn't work any more. Changing it to another low number like 2058 gave same error message, but when I changed it to 20057, everything worked again. Maybe something changed with the way the lower port numbers are handled.
User contributions licensed under CC BY-SA 3.0