Finance | Project Operations, Human Resources, ...

IIS stays Started but site becomes unresponsive after closing Visual Studio (fixed by IISRESET)

(0) Share

Report

Posted on by Raed Salah Bzour

Hi everyone,

I’m facing a strange issue with a Dynamics 365 Finance & Operations development VM.

The Environment:
- Full D365 F&O Dev VM (local VM)
- IIS Application Pool: AOSService
- URL works normally when Visual Studio is open

The Problems:

- When Visual Studio is OPEN → the D365 site works normally
- After closing Visual Studio → the site becomes unresponsive (URL does not load)
- IIS still shows the AOSService app pool as "Started"
- The issue is NOT that IIS stops, but the application becomes unresponsive
- Running IISRESET fixes the issue immediately

My Observations:
- Idle timeout is set to 0
- No recycling schedule configured
- App pool does NOT appear stopped
- Issue started recently (it was working 100% before)

So, I have a couple of Questions:

1. Why would closing Visual Studio cause the IIS-hosted D365 application to hang?
2. Is Visual Studio implicitly keeping certain services or runtime dependencies alive?
3. Could this be related to debugger attachment or improper process lifecycle handling?
4. What configuration is required to make IIS fully independent from Visual Studio?

Any help or guidance would be appreciated.

Thanks!

Categories:

Dynamics 365 Finance

I have the same question (0)

All responses (3)

Answers (0)

Sort by

Suggested answer

Subra 972 on at

Like (0)

Report
Copy link

Link copied!

Hi @Raed Salah Bzour

Could you please check the event viewer for additional error message?

Thanks,
Subra

If this helped, please mark it as "Verified" for others facing the same issue

Was this reply helpful? Yes No
Suggested answer

André Arnaud de Cal... 305,294 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!
Hi Raed,

Let me try to answer your questions.

There are two IIS applications in use. IIS and IIS express. IIS express is used when Visual Studio is active. When you close Visual Studio, it should switch to IIS.

See point 1. VS is not keeping services alive, but it uses another edition of IIS to be able to perform debugging.

As mentioned, it should switch back to IIS, but you will need to look at event logs to see if something prevents IIS from running normally.

This request is not possible for the pre-configured dev VM. You can check if you can find the culprit. If not, try to download and start using a new fresh VM for development. That is usually my mitigation with this type of issues.

Was this reply helpful? Yes No
Suggested answer

Subra 972 on at

Like (0)

Report
Copy link

Link copied!

Hi @Raed Salah Bzour

We also had a similar issue but for us whenever the VS open we are not able to open D365 FO.

Please don't much spent much time on this. As mentioned by Andre, please go and create a new VM.

Thanks,
Subra

If this helped, please mark it as "Verified" for others facing the same issue

Was this reply helpful? Yes No