AOS Failed to Start

by | Updated August 15, 2016 | Dynamics AX, Set Up, Upgrade

The AOS failed to start error is found in System event viewer: ‘The Microsoft Dynamics AX Object Server 6.3$01-DemoDataAX service terminated with service-specific error Attempt to use a file handle to an open disk partition for an operation other than raw disk I/O.’

I was in the process of upgrading to AX 2012 R3 from AX 2012 RTM. I was at the point where I had installed the R3 database, and was then installing the R3 AOS per the AX 2012 Upgrade guide.

During the install of the R3 AOS component, setup failed on starting the AOS.

 

What was the cause of the AOS failed start?

One of the pre-requisite steps in the upgrade process is that you have to remove any customization from the system classes. These are the classes you need to check: Info, Session, Application, Company, Site, ClassFactory, Global, VersionControl, SysStartupCmd*, SysSetupForm*, SYS*, and Batch Framework

We tried to override the ISV changes by removing the code in VAR layer but that did not work.

The workaround was to remove the ISV code from modelelementdata table. This is not supported by Microsoft so proceed at your own risk. However, we did complete the upgrade and there have been no negative effects from this workaround.

 

Here are some scripts we used to find the offending codes. Run these against axRTMDEV01 and AXRTMDEV01_model:

 

After the delete, run these to verify only Microsoft’s system classes are present:

By deleting the offending objects, we were then able to start the AOS then installed the AX 2012 R3 client and Management utilities then proceed with the upgrade.

We also opened a support case with Microsoft and here’s another alternative to this issue:

I tested an alternative to deleting the objects directly. I created a test table in a VAR layer (assume that is the ISV). I then changed to the CUS layer and set my model to a new custom model. I then made a change to the table and fields. This involved adding a comment of “.” to the “Developer Documentation” property on the table, and a “.” to the “Help Text” property on each field. I made an export of the CUS model just as a backup, and delete the VAR model. I found that what I had left was the table and fields in the CUS layer. Therefore, all table IDs and Fields were kept.

 

Related Posts

0 Comments

Submit a Comment

Your email address will not be published. Required fields are marked *

Upcoming Events

december

02dec9:00 am12:00 pmOnline Workshop - Dynamics GP Year End Close (Morning Session)

03dec11:00 am12:00 pmConfab with Stoneridge - Livestream: Live Agents, Power Virtual Agents, Omnichannel – Oh My!

03dec1:00 pm4:00 pmOnline Workshop - Dynamics GP Year End Close (Afternoon Session)

09dec10:00 am10:30 amThe Modern Manufacturer - Manufacturing Policy Management

17dec11:00 am12:00 pmConfab with Stoneridge - Livestream - Technology in 2020: A Year in Review

january

06jan10:00 am10:30 amThe Modern Manufacturer - MRP v MPS – What, When and How

14jan11:00 am12:00 pmConfab with Stoneridge - Livestream - Looking Forward: Predictions for Technology in 2021

20jan10:00 am10:30 amThe Modern Manufacturer - Demand Forecasting Functionality

About Stoneridge
Stoneridge Software is a unique Microsoft Gold Partner, with emphasis on partner. With specialties in Microsoft Dynamics 365, Microsoft Dynamics AX, Microsoft Dynamics NAV, Microsoft Dynamics GP and Microsoft Dynamics CRM, we focus on attracting the most knowledgeable experts in the field to our team, and prioritize delivering stellar solutions with maximum impact for your business. At Stoneridge, we are deeply committed to your results. Each engagement is met with a dedicated team, ready to provide thorough, tailored, and expert service. Based in Minnesota, we intentionally “step into your shoes,” wherever you are. We focus on what you care about, and develop trusting, long-term relationships with our clients.

Subscribe To Our Blog

Sign up to get periodic updates on the latest posts.

Thank you for subscribing!

X