Skip to main content

Fixing the “Can’t Stop DynamicsAxBatch” Error During Admin User Provisioning in Dynamics 365 F&O

 If you're working with Microsoft Dynamics 365 for Finance and Operations (D365 F&O) and encounter the dreaded error “Can’t stop DynamicsAxBatch” while using the Admin User Provisioning Tool, you're not alone. This guide walks you through a quick and effective solution to resolve the issue and get back to work without delays.

🛠️ What Is the Admin User Provisioning Tool?

The Admin User Provisioning Tool is used to register a user as an administrator on a D365 F&O instance—typically for development and customization purposes. You provide your Azure AD credentials (email address) to gain admin access.

❌ The Problem: “Can’t Stop DynamicsAxBatch” Error

While registering via the Admin Provisioning Tool or attempting to stop the service manually through Windows Services, you might encounter an error stating:

“Can’t stop DynamicsAxBatch”

This error prevents you from proceeding with the registration process.

 The Solution: Step-by-Step Fix 

Step 1: Try Stopping the Service Manually 1. Open Services (Win + R  type services.msc  Enter).

 2. Locate the service named: Microsoft Dynamics 365 Unified Operations: Batch Management Service 3. Right-click and choose Stop. 

Step 2: If Manual Stop Fails, Use Command Prompt ? 

Open Command Prompt as Administrator - Press Win, type cmd, right-click on Command Prompt, and select Run as administrator.

Find the Service PID Run the following command to get the Process ID (PID): sc queryex DynamicsAxBatch Look for the line that starts with PID and note the number. 

Kill the Process Use the PID to forcefully stop the service: taskkill /f /pid [PID_NUMBER] Example: taskkill /f /pid 2145


Final Step: Register Using Admin Provisioning Tool 

Now that the service is stopped, run the Admin User Provisioning Tool again and register your user. The error should no longer appear. 

Troubleshooting Tips 1. Verify Service Name Ensure you're using the correct service name: DynamicsAxBatch 

2. Check for Permissions Make sure you're running Command Prompt as Administrator.

3. Check for Dependent Services In Services  Properties  Dependencies, stop dependent services first if needed. 

4. Use PowerShell as an Alternative 

 Stop-Process -Id [PID] -Force 5

Restart the Machine A system reboot may release the lock on the service.

Final Thoughts This quick fix should help you bypass the Can't stop DynamicsAxBatch error and continue with your development or customization tasks in D365 F&O. 

If you found this helpful, feel free to like, comment, and share. And if you've discovered a better workaround or have questions, drop a comment below

Labels:

Comments

Post a Comment

Popular posts from this blog

How to get batch header and recurrence information in service class for sysoperation frame work in D365 F&O

  BatchHeader batchHeader         = this.getCurrentBatchHeader();         int         timeUnitsSelected   = 0;         if(this.isExecutingInBatch())         {             RefRecId batchRecId = batchHeader.parmBatchHeaderId();             BatchJob batchJob;             select firstonly batchJob             where batchJob.RecId == batchRecId;                      SysRecurrenceData recurrenceData = batchjob.recurrenceData;             SysRecurrenceUnit timeUnits = conPeek(recurrenceData, 7);             timeUnitsSelected = timeUnits;         }
Post a Comment
Read more

Table Keys: Surrogate, Alternate, Replacement, Primary, and Foreign

Primary key A primary key is one type of key. The other type of key is an alternate key. There is a maximum of one primary key per table , whereas a table can have several alternate keys . The primary key is usually the type of key that other tables, called child tables, refer to when a foreign key field in those other tables need a relational identifier. Starting in Microsoft Dynamics AX 2012 the primary key for every new table is always enforced by an index that has exactly one field. The one field is usually an incremented number or a completely meaningless number that is generated by the system. For new tables the default is a primary key based on the RecId field. This is represented as the surrogate key in the user interface. The following table describes the  PrimaryIndex   property and other major properties that are related to keys. Property Description PrimaryIndex The drop-down list contains the surrogate key plus every index on the table that has its  Alternate...
Post a Comment
Read more