AOS restart - D365 on premise version

(0) Share

Report

Posted on by Gautam

3,945

Hi all,

We are using D365 on premise version, just wondering how to restart AOS, where can I get the same.

Thanks
Gautam

*This post is locked for comments

I have the same question (0)

All responses (5)

Answers (0)

Martin Dráb 237,972 Most Valuable Professional on at

Like (0)

Report

What exactly do you mean by "restarting AOS" in the context of Service Fabric?

Was this reply helpful? Yes No
Gautam 3,945 on at

Like (0)

Report

Hi Martin,

Like in development D365 VM , that AOS is there on IIS .

So here how can we get, as I am only able to see service fabric on IIS .
And our main issue is that sometime our D365 url is unreachable.

Thanks

Gautam

Was this reply helpful? Yes No
Suggested answer

Martin Dráb 237,972 Most Valuable Professional on at

Like (0)

Report

The architecture of DEV boxes and on-premise deployments is completely different, therefore trying to do the same things makes little sense. If nothing else, all production environments have more than a single AOS.

You can restart Service Fabric nodes in Service Fabric Explorer, for example.

But it seems that you should rather focus on why the environment isn't reachable. Just keep restarting a production ERP system wouldn't be a solution...

Was this reply helpful? Yes No
Community Member on at

Like (1)

Report

Sometimes you might want to enter maintenance mode to manage licenses.

This requires the "restart of AOS".

To restart AOS service in your on-prem environment go to the Service Fabric explorer, expand Nodes and restart AOS by clicking on the dotted lines menu to the right of nodes whos name starts with AOS_ and choosing Restart. Do it for all nodes with AOS roles.

Was this reply helpful? Yes No
Suggested answer

Pete Alberts 3,542 on at

Like (0)

Report

Here is my solution (since 2 minutes ago) to "restart the AOS". The other suggestions didn't work for me since I'm clueless with anything outside Visual Studio.

My context: To toggle config keys on a onebox environment you need to enter maintenance mode and then "restart the AOS".

1) Add the SysConfig form to project - it has the SysConfig table as datasource (you can't add SysConfig to your project).

2) Rebuild project (with sync)

3) And you're done! :)

If it's stupid and it works, it's not stupid.

4) The elements subjected to the config keys that were toggled need to be rebuilt (with sync) - in my case it was a load of menu items which I allready included in another project. So I rebuilt that project -> then the changes take effect. Which makes sense. Or you could rebuild your the models related to the toggled config keys, it's just a lengthy operation.

Was this reply helpful? Yes No