Cannot start AOS web service after opening visual studio project and IIS worker process starts

(2) Share

Report

Posted on by Kauto

2,734

Hi,

Recently hit a problem on my dev environment, my D365 Finance and Operations tier 1 environment works fine until I open visual studio 2022 and open a development project (any one).

What appears to happen is the IIS worker process task starts up and kills the AOS service task. When I try to restart the AOS service it tells me the worker IIS process has the port 443.

If I kill that process I can start the application again.

Can anyone help me out here?

Thanks

Kauto.

Categories:

Dynamics 365 Finance

I have the same question (0)

All responses (9)

Answers (1)

Sort by

André Arnaud de Cal... 304,508 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Hi Kauto,

This is intended behavior. IIS express is used when development process is active in a cloud hosted development environment. The application should be available using both modi.

Was this reply helpful? Yes No
Kauto 2,734 on at

Like (0)

Report
Copy link

Link copied!

Hi Andre

Yes I have been a developer with this and AX for over 20 years.

But never encountered this behaviour - the net effect is that I cannot debug or simulatenously run D365 application and visual studio.

Are there certain settings I need to tweak or change?

Was this reply helpful? Yes No
Syed Amir Ali 205 on at

Like (0)

Report
Copy link

Link copied!

Hey,

Option: 1
Run the iisreset command in Command Prompt. Then try to restart the AOS Web Service manually if it does not start automatically.

Option: 2

Rebuild your custom models without performing a database synchronization, and then attempt to restart the AOS services again.

Regards,
Amir.

Was this reply helpful? Yes No
Kauto 2,734 on at

Like (0)

Report
Copy link

Link copied!

Hi Amir

Whilst that work normally this still doesn't fix my inability to run visual studio with the IIS worker process and run the application at the same time.

Opening visual studio starts the IIS worker process which kills the AOS service and runs the worker process on the 443 port stopping the AOS service from restarting.

This prevents me using visual studio (build and debug) and run the application at the same time.

I have started deployment of a replacement enviroment because I cannot work out what has gone wrong.

Was this reply helpful? Yes No
André Arnaud de Cal... 304,508 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Hi Kauto,

A follow up question would be to validate this in another environment. You are already deploying a new one. What I noticed the past years is that sometimes the application was not running where starting Visual Studio solved that. Your issue is vice versa.

Please let us know the result when you test it in the new environment.

Was this reply helpful? Yes No
Martin Dráb 239,381 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

Could you give us more details, please?

I don't understand the statement "Opening visual studio starts the IIS worker process which kills the AOS service". What do you mean by "AOS service" if not an IIS process? F&O is a web application, therefore you absolutely must have a web server running.

Also, do you agree with me that the expected behavior is stopping IIS and starting IIS Express? Or have you changed DEV configuration to use IIS instead of IIS Express?

Was this reply helpful? Yes No
Kauto 2,734 on at

Like (0)

Report
Copy link

Link copied!

Hi Martin,

If I open the visual studio project or if I restart IIS this process starts:

If this process starts (even via a project compilation and build the AOS service in IIS stops:

When the AOS Service stops we cannot access the application.

The only way to get it working again is kill the IIS Express Worker Process above - restart IIS.

However if we build the project after this the situation repeats.

This makes it impossible to debug or develop.

Can anyone suggest the way forward here or settings to change.

Thanks

Kauto.

Was this reply helpful? Yes No
Martin Dráb 239,381 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

What your first screenshot shows is IIS Express, not IIS. So, you actually meant IIS Express when you said IIS and IIS when you said AOS. Despite similar names, IIS and IIS Express are two different products.

What you see regarding IIS/IIS Express processes is the correct behavior. IIS Express is used for development and IIS otherwise, therefore when you start developing, IIS stops and IIS Express starts instead.

You're wrong in thinking that you need AOS running on IIS during development. It must be stopped, because the AOS runs on IIS Express instead and you can't have both servers handing the same hostname and port at the same time. So it's not something you should try to fix (although, as I mentioned before, you can configure your environment to use IIS for development if needed).

Now we can start about the actual problem - you're suggesting that something doesn't work when F&O runs on IIS. Please tell us what behavior you're observing and what you've done so far to analyze the problem (such as checking logs).

Was this reply helpful? Yes No
Verified answer

Kauto 2,734 on at

Like (0)

Report
Copy link

Link copied!

This is part of another issue, the MMC is failing for the event viewer as well.

Cannot work out what is wrong with this environment, I have given up and deployed a new one to replace it - the new one on the same code base, same restored DB working fine without issue.

Going to close this one out on environmental issues.

Was this reply helpful? Yes No