web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :

D365: Admin user provisioning tool cannot stop DynamicsAXBatch service

Galyna Fedorova Profile Picture Galyna Fedorova 3,566

Recently I’ve faced an issue with the user provisioning on local VM. Dynamics 365 for Finance and Operations: Admin User Provisioning displayed the error message that it cannot stop DynamicsAXB atch service on computer.

Error message is presented below.

Error message

I am going to provide you with the steps which I followed in order to solve it.

Step#1: Go to the services and try stopping the batch service Microsoft Dynamics 365 Unified Operations: Batch Management Service manually. If you are facing the same error, go to the next step.

Service error message

Step #2:  Restart IIS and restart AOSService site there. If you still cannot provision the user, go to the next step.

Step #3: Change time zone on VM to match time zone on your laptop. If you still cannot provision the user, go to the next step.

Step #4: Go to event viewer and check the errors.

For my example, I found only 1 error – Office 2016 Licensing Service

Details:

The description for Event ID 0 from source Office 2016 Licensing Service cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

Subscription licensing service failed: -1073418225

I decided to fix this issue:

1.From Control Panel navigate to Programs and /or Programs and Features and select Office 2016 installation.

2.Click on Change and then select the Online Repair option. Wait until it’s completed.

Step #5: Try rebooting of VM.

In my case, only after step #5 I was able to provision my user.

Good luck!


This was originally posted here.

Comments

*This post is locked for comments