Announcements
Hi Experts,
I noticed that in my dev environment, I always get 503 error until I open a project under visual studio. Is it something related to IIS express which visual studio starts while loading the project. If yes, any solution which can fix this issue?
Note: The above issue is not related to services like IIS admin and the world wide web.
Hi Sachin,
Is this related to D365FO?
Best regards,
Ludwig
Take a look at suggestions from the link below
community.dynamics.com/.../process-to-debug-not-found-and-503-whenever-trying-to-build-rebuild-or-debug
Hi Sachin Goyal,
if it is D365 I saw it in our environments in some rare cases in the past. In our cases it was related with IIS. Please check the AOS and application pool in IIS. If one of them is stopped the web site is not available.
Does it happen every time when you try to open a project or only when you just started VM? I noticed similar behavior but only after VM restart and looks like not all services are started at this point.
Hi goyalsachin6,
When you open Visual Studio, the VM switches to use IIS Express instead of IIS, which means that IIS will stop and IIS Express will start. This also means that you cannot start IIS again because IIS Express is now using the port.
When you close VS, it will close IIS Express and restart IIS for you.
And you could restart IIS Express by selecting Dynamics 365 > Restart IIS Express in Visual Studio.
Hi Sergei,
Yes, This issue comes when you start the VM and try to access the application. I believe it supposed to use IIS which I checked is started but still application remain unavailable. however when you open visual studio which eventually starts IIS express it becomes avaialable and after that when you close the visual studio, your application again become unavailable.
I also notice that in build/test box, application always remains available when you start the VM.
There should be some difference in terms of settings for both types of VM which is causing this issue.
Yes Ludwig.
Did you ever get this resolved? I have the exact same issue right now in my dev environment. Only works if VS is open.
Hi Andrew,
I had the same issue last week on a demo machine which was also a DEV topology. We updated the machine with latest releases and removed one package. At that time, we had the same issue. After installing a new deployable package, the issue got resolved.
Can you tell what might be changed when you run into this issue or is this a fresh VM?
André, thank you so much! We applied the latest deployable package from the Dev branch to my environment and now it works the way it should!
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.
Jump in, show your community spirit, and win prizes!
Expanding mentorship, skilling, and AI innovation
These are the community rock stars!
Stay up to date on forum activity by subscribing.
Abhilash Warrier 658 Super User 2026 Season 1
André Arnaud de Cal... 632 Super User 2026 Season 1
Giorgio Bonacorsi 570
