10.0.16 cloud hosted environment

(0) Share

Report

Posted on by Dave C Eng

Hi,

We are trying to deploy a new 10.0.16 cloud environment and have tried about 4 times every time the deployment fails.

This mentions issues with upgrades https://community.dynamics.com/ax/b/d365fortechies/posts/microsoft-dynamics-365-finance-update-error-globalupdate-script-for-service-model-retailserver but not sure what to do for a new deployment?

Has anyone had any success deploying a 10.0.16 environment.

Thanks

Dave

I have the same question (0)

All responses (7)

Answers (1)

Gunjan Bhattachayya 35,423 on at

Like (1)

Report

Hi Dave,

What is the error you get during deployment? Is it related to retail server?

We have seen the same issue while updating environments, but have never faced issues deploying new ones.

Was this reply helpful? Yes No
Suggested answer

Ludwig Reinhard Microsoft Employee on at

Like (1)

Report

Hello Dave,

There are some issues mentioned on LCS.

Would recommend that you open a support ticket with MS who could do a screensharing session with you and get things fixed.

Best regards,

Ludwig

Was this reply helpful? Yes No
Dave C Eng on at

Like (0)

Report

Hi Both,

Thanks for the replies. I will ask the system admin who was doing the deployment for the error don’t have it to hand.

Ludwig could you point me to where in LCS you can see there are issues.

It does seem to be some bigger issues with deployments as we tried a 10.0.13 environment and that failed too.

I have had to ask Microsoft to escalate as they initially said they only support the managed environments and won’t help with cloud hosted environment. I explained that they have removed all our managed T1 environments and we are deploying a vanilla environment as a pre cursor to us being able to upgrade sandbox and prod so hopefully they help out otherwise we can’t check our customisations for the upgrade.

Thanks

Dave

Was this reply helpful? Yes No
André Arnaud de Cal... 301,035 Super User 2025 Season 2 on at

Like (0)

Report

Hi Dave,

Depending on the error log, it will be something that you can fix yourself or need help. If you update an older version, it might get stuck on a pre-requisite for installing .NET 4.7.2 prior to the update itself. However, there can be tons of reasons why it fails, so the error log is key here.

Was this reply helpful? Yes No
Verified answer

Ludwig Reinhard Microsoft Employee on at

Like (1)

Report

Hello Dave,

Please check especially this issue:

fix.lcs.dynamics.com/.../Details

In addition, check out this site for more possible issues:

fix.lcs.dynamics.com/.../Results

Best regards,

Ludwig

Was this reply helpful? Yes No
Dave C Eng on at

Like (0)

Report

Hi Ludwig,

Thanks I will check out those links to cross reference the error with the ones we are getting. Will also keep trying with Microsoft.

Andre it’s not just upgrades deployments of fresh environments are failing for us as well so we are a bit blocked on this upgrade.

Really hope we can get into a better rhythm with these upgrades they are eating up way to much time and money for us at the moment!!

Thanks

Dave

Was this reply helpful? Yes No
Dave C Eng on at

Like (0)

Report

Hi,

The error we are getting on deployment of all cloud hosted environments is "Script [Run-CommandAOSServiceResetAosAdminUser] failed execution against <VMNAME>. Last Result: 0xFFFFFFF ()."

This looks like the solution is here www.mathdax.ca/.../d365-finance-and-operations-les-ports.html

The issue is the firewall settings on the virtual network we have setup for all out AX cloud hosted boxes. We will setup the firewall rules as suggested in the article and retry.

Thanks

Dave

Article translation to English

"received the following error while deploying a Cloud-Hosted environment in my Azure infrastructure:

Attempted to remotely execute a powershell script but was unable to reach the Windows Remote Management service. Please make sure the virtual machine in resource group is accessible.

In order to correct the problem, I opened the ports to access WinRM and try a new deployment. This time I got the following message:

Script [Run-CommandAOSServiceResetAosAdminUser] failed execution against VM. Last Result: 0xFFFFFFF ().

The problem is still the firewall. In fact, this is because I am selecting a VNET and a subnet that already exists in my Azure infrastructure. The subnet is attached to a Network Security Group (NSG) which restricts externally accessible ports. Since I was unable to find the port requirements for deploying a Cloud-Hosted environment, I did a deployment and let LCS create the VNET and the subnet. Then the deployment was a success and I went to look at the default configuration of the NSG.

Then just change the permissions of the existing NSG so I want to use it for future deployments." Credit to Mathieu Tessier for posting this solution.

Was this reply helpful? Yes No