Personalized Community is here!
Quickly customize your community to find the content you seek.
Have questions on moving to the cloud? Visit the Dynamics 365 Migration Community today! Microsoft’s extensive network of Dynamics AX and Dynamics CRM experts can help.
2021 Release Wave 1Discover the latest updates and new features to Dynamics 365 planned April 2021 through September 2021.
Release overview guides and videos Release Plan | Preview 2021 Release Wave 1 Timeline
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Upcoming TechTalks | All TechTalks
The following is resolution to an issue we stumbled upon recently. In case anyone were to come across a similar situation, the below could be useful.
Here's what one of our customers came across on AX 2012.
They took a backup of the AX database (AX version 6.0) on the production environment and wanted to restore this file onto the test environment. This should have been a straight forward task but for some strange reason, we were unable to restart the AOS service after restoring the backup.
To begin with, the event logs were not very helpful and intuitive. The only error message we received was a generic one listed below.
Faulting application name: Ax32Serv.exe, version: 6.0.947.280, time stamp: 0x4ec317b2Faulting module name: Ax32Serv.exe, version: 6.0.947.280, time stamp: 0x4ec317b2Exception code: 0xc0000005Fault offset: 0x0000000000488754Faulting process id: 0x5bcFaulting application start time: 0x01cd5340c143b395Faulting application path: C:\Program Files\Microsoft Dynamics AX\60\Server\MSDynamicsAXProd\Bin\Ax32Serv.exeFaulting module path: C:\Program Files\Microsoft Dynamics AX\60\Server\MSDynamicsAXProd\Bin\Ax32Serv.exe
After some troubleshooting, we were able to find the root cause for the above issue.
A database log had been set up for the table 'SQL Dictionary' (Table ID 65518).
It seems that once you set up a log on this particular table and if you stop the AOS service and try to restart it, you will be unable to do so. You need to then delete the record via SSMS in order to get the AOS to restart. Although, technically, I do not know why this happens for the table in question.
In our case, after deleting the record in the test environment, we were able to restart the AOS service.
I am having the same problem. I looked at the SQL Dictionary but I don't see the Field ID or Table ID that matches 65518. When I select top 1000 rows (it had 1000 of rows!) which one to delete? Pls help
When you say you are having the same problem, does it mean you are unable to restart the AOS service?
The steps I followed were:
Go to SQL management studio, select the record(s) for table ID 65518 in the table 'Databaselog'.
Restart AOS service.
I am facing the same issue. I followed the post of Victoria, but system is showing multiple DIC files permission errors . then i granted the rights to user on GP 2013 folder. its working fine now.
Business Applications communities