Finance | Project Operations, Human Resources, ...

Why the D365 FnO cloud development environment service goes down except downtime and how can I identify the cause?

(0) Share

Report

Posted on by JAYAKRISHNAN M S

145

Hello Experts,

I noticed that, sometimes our D365 cloud managed development environment service goes down except downtime. How can I identify the exact cause / reason for this? The

Primary region of the environment is North Europe.

Any help should be greatly appreciated.

Thank you.

I have the same question (0)

All responses (13)

Answers (0)

Suggested answer

nmaenpaa 101,166 Moderator on at

Like (0)

Report

Could you elaborate what you mean by "goes down except downtime"?

- Does the whole VM shut down? Is there perhaps an automatic shutdown configured for the VM in Azure?

- Does just the D365FO service go down? That's expected when a developer is working in the system and compiling things. The system shouldn't be used by others when development work is going on.

Was this reply helpful? Yes No
Suggested answer

Sergei Minozhenko 23,093 on at

Like (0)

Report

Hi, JAYAKRISHNAN M S,

VM can be down also during restart after security updates are applied. You can check it by opening "Windows update settings" from Windows main menu -> Update history.

Was this reply helpful? Yes No
JAYAKRISHNAN M S 145 on at

Like (0)

Report

Hi Nikolaos Mäenpää,

Thank you for the quick response.

1. "goes down except downtime" means just the D365 service only go down. If I restart, its up with out any issue.

2. No. Not configured the automatic VM shutdown. I expected that one and verified from 'Automation Accounts'.

3. This (service go down) happens at night(IST) and no one is using it. But not at all nights.

Was this reply helpful? Yes No
JAYAKRISHNAN M S 145 on at

Like (0)

Report

Hi Sergei Minozhenk,

Thank you for the quick response and additional info.

Only D365 service go down for me. Is there any way to identify the cause?

Was this reply helpful? Yes No
Suggested answer

nmaenpaa 101,166 Moderator on at

Like (0)

Report

Most likely it's about Windows updates which might restart the VM. Did the VM restart when D365 was down? You can check the uptime of the server in Task manager.

Does it do some harm if the service is momentarily down in the night time? It's just a dev system.

Was this reply helpful? Yes No
JAYAKRISHNAN M S 145 on at

Like (0)

Report

Hi Nikolaos Mäenpää,

Right, here I attached the uptime and security update details of the server. It was just 4 days ago (14 Nov 2020). I had to restart the D365 service yesterday (18 Nov 2020).

-Some custom integration development is also in-progress (data transfer from .Net to D365) and which is also affected this unintentional D365 service down. Both are independent teams and may be the D365 team will not available for a restart.

That's why I am trying to figure out something if anything there.

Was this reply helpful? Yes No
Suggested answer

nmaenpaa 101,166 Moderator on at

Like (0)

Report

Thanks for the info. The next step would be to check the Event logs on the server and try to find some entries that help understand why the service went down.

Even though a single devbox is not a Highly Available service and there's no SLA from Microsoft, I would not expect the service to go down frequently just by itself.

Was this reply helpful? Yes No
Sergei Minozhenko 23,093 on at

Like (1)

Report

Hi JAYAKRISHNAN M S,

Is the dev environment used as a test environment?

Which D365 service you are referring to (iisexpress or AOSService web site on IIS server)?

Could it be that someone using VS on this VM? When VS is started it shutdowns AOSService on IIS and start IISExpress service

Was this reply helpful? Yes No
Suggested answer

nmaenpaa 101,166 Moderator on at

Like (1)

Report

In general it might be better to separate development and testing to different VMs. Dev VMs should only be used by developers and dev work. Of course someone can login to test the latest changes if needed, but generally testing should happen in a dedicated test system. And if some third party needs to connect to a system to test their third party developments, normally they would connect to a test system.

Dev systems are anyway going to be up and down randomly because the developer works there. So if some third party needs a reliable system to connect to, it should not be a dev system.

It can still be a cloud hosted onebox, but not one that is used for development.

Was this reply helpful? Yes No
JAYAKRISHNAN M S 145 on at

Like (0)

Report

Hi Sergei Minozhenko and Nikolaos Mäenpää

Really sorry for the late response and thank you for the quick responses.

1. "Which D365 service you are referring to (iisexpress or AOSService web site on IIS server)?"

Ans: I am referring AOSService web site on IIS server.

2. "In general it might be better to separate development and testing to different VMs"

Ans: For test environment, UAT is separate one for actual testing.

3. I am also attach here the event viewer logs of last 24 hours when I found the service had been down for reference.

Errors_5F00_last24hours_5F00_26Nov2020_5F00_5_5F00_24AM.zip

Was this reply helpful? Yes No