Lỗi visual 2010 unable to laugh to iis connect server

So you have a web application at http://wpnne76648:2010, and wpnne76648 is the local name of your server? Do you have alternate access mappings in place for the FQDN also? If you open a browser on this server and point it to http://wpnne76648:2010 does the web application open?

There could be a number of things in the way. If this is a development environment, you can add a hosts file that points wpnne76648 to 127.0.0.1 (localhost), which will force it to resolve locally as opposed to going out to DNS and resolving to the IP for the machine. I wouldn't do this for production, but it's a quick way to prove if your issues are DNS related in a development or lab environment.

The second piece is that as you quick deploy or deploy solutions from Visual Studio to the SharePoint server, Visual Studio needs the ability to access everything on the system and call for IISReset. Make sure the user account you're logged in while you're trying to do all of this is local admin. As a better practice to get into, do any solution development logged in as the setup/install account for the farm, as this account is local admin on all SharePoint boxes, unlike the farm account which should not be local admin on any of the boxes.

It's "possible" it's blowing up on the connection because it knows it doesn't have sufficient rights to do what it will ultimately need to (hence the IIS error).

It doesn't make sense that I should delete the bin and/or obj folders. I have several projects, and they all have the same error.

What's the real issue here? Anyone know?

I have VS 2019, build 16.4.3, with .Net 4.8

1. 2023-02-13T12:07:43.1466667+00:00 Thanks @Coreysan That's was the solution. Great Man ! Tks.
2. 2023-07-05T07:52:31.9866667+00:00

2 answers

2022-04-08T01:45:16.257+00:00

Hi @Coreysan ,

What kind of application and what .NET version you use? Something I think you can try and if anything wrong or abnormal, I need your feedback.

1. Try to create an empty asp.net or asp.net core application and run it in IIS Express directly. Please tell me the result.
2. Delete .vs\config\applicationhost.config file, then right click on prject solution -> properties -> debug tab ->web server settings, change port number to be different from all other applications. Restart VS and rebuild solution.

If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment". Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Best regards, Bruce Zhang

1. 2022-04-08T03:10:03.317+00:00 I've tried deleting .vs lots of times, and it didn't solve anything. However, changing the port number did. So that's my solution. I wonder why that's needed sometimes? IF you want to provide this as your answer, I'll flag it answered for you! Thanks so much!!!!
2. 2022-04-08T03:12:09.48+00:00 BTW - my project is a MVC Core 3.1 project with N-Tier architecture, and I use UnitOfWork. When I created the project I chose the Core 3.1 library. I have no idea if I should rebuild using the .Net 5 library, or upgrade VS 2019, or even move up to 2022. A big change like 2022 kinda scares me.
3. 2022-04-08T05:33:30.283+00:00 Hi @Coreysan , From what I've tried, this problem all happens randomly. But I think it's likely that IIS express is still listening on the original port because it didn't exit normally. This means that the initial port is still occupied by the process. When deleting the applicationhost.config file of IIS express and changing the port, IIS express uses another port which is not occupied by other processes and everything works.
4. 2022-04-08T18:26:33.463+00:00 @Bruce Zhang-MSFT That was a very satisfying answer - thanks!!! You should consider being a therapist, cuz you helped me calm down! Corey

2022-04-11T01:16:00.253+00:00

Hi @Coreysan ,

Thank you for such a high rating. It's so nice of you can accept the answer. I am honored to be able to help you.