Try Microsoft Edge
A fast and secure browser that's designed for Windows 10
The Batch process service is showing as DEAD on the SA/ online users page. I am unable to manually start the service.
The Microsoft Dynamics 365 for Operations - Batch Management Service fails with the following errors in the event log:
Failed to create a metadata service client in 5 attempts.
Metadata service communication retry attempts failed to resolve issues with the following settings AX7CertificateUserName: FRServiceUser@dynamics.com; AX7CertificateThumbprint: B##############FederationRealm: spn:00000015-0000-0000-c000-000000000000; AX7ProviderName: mintedtoken.dynamics.com; AX7TokenIssuer: fakeacs.accesscontrol.windows.net Component: Microsoft.Dynamics.Integration.Common.TraceLog User: NT AUTHORITY\NETWORK SERVICE
Received the following exception when contacting the AX Metadata Service possibly due to expired token. Attempted to retry the operation 5 times with no success. Internal Server Error Action: Fault code: Receiver IsSenderFault: False IsReceiverFault: True Reason: Internal Server Error
Cant find much info on this for d365, anyone know what can be done to get the batch service up and running?
What exact environment are you using? What platform update is installed? Is it an older or more recent machine running locally or on Azure?
It is an older non-production environment Update 3 running on an Azure VM with a local database. This environment is used for training purposes and not critical but does contain some good data and I'd rather not try to blow this away just yet.
I'm facing the same error messages on an Azure deployed virtual machine that was deployed in June but maintained with Platform Updates since then.
However, the messages are created by the Management Reporter Service (Management Reporter 2012 Services) - which makes slightly more sense because of the user that is named (FRServiceUser => FR stands for Financial Reporting aka Management Reporter).
I do not have a solution for this yet though...