I was working on the Dynamics 365 Finance and Operations environment with Platform update 30, and I had removed a model from my Dev VM. After that, I noticed that batch jobs were not running, and the service 'Microsoft Dynamics 365 Unified Operations: Batch Management Service' was stopped.
When I tried to start the service, I encountered the following error:
Services
Windows could not start the Microsoft Dynamics 365 Unified Operations: Batch Management Service service on Local Computer.
Error 1064: An exception occurred in the service when handling the control request.
There were also some error messages in the Event log:
Faulting application name: Batch.exe, version: 7.0.6651.92, time stamp: 0xa0847b19 Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000 Exception code: 0x80131623 Fault offset: 0x00007ff9311594e3 Faulting process id: 0x1fd0 Faulting application start time: 0x01d9c6e9e907759b Faulting application path: K:\AosService\WebRoot\bin\Batch.exe Faulting module path: unknown Report Id: a3b06914-d21c-4d92-828a-494565ab6bcf Faulting package full name: Faulting package-relative application ID:
After researching online, I found a solution suggesting to disable Dynamics 365 Finance and Operations Maintenance mode .
To fix the issue, I ran the following query:
update SQLSYSTEMVARIABLES SET VALUE = 0 where PARM = 'CONFIGURATIONMODE'
Then, I restarted IIS.
After performing these steps, I was able to run the 'Microsoft Dynamics 365 Unified Operations: Batch Management Service' batch job successfully.
Comments
Post a Comment