web
You’re offline. This is a read only version of the page.
close
Skip to main content
News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Finance | Project Operations, Human Resources, ... / Ax 2009 - missing meth...
Finance | Project Operations, Human Resources, ...
Unanswered

Ax 2009 - missing methods, fields after "axcus.aod Error Code: 64 = network name no longer avail"

(0) ShareShare
ReportReport
Posted on by vv1984 1,087
Hi,
yesterday we had this error on our production environment:
axcus.aod while reading in record 215B1D0 Windows Error: =  Error Code: 64 = The specified network name is no longer available.
Almost nothing was available, I could not navigate the AOT, I could open some forms but lot of custom functions were not available.
 
We recovered it somehow by just restarting the AOS service. After that, many custom functions were again usable and the AOT was available again.
But then I've noticed that a lot of custom classes (cus layer) where missing methods and some custom fields (cus layer) were missing from standard tables too. 
 
How can we recover from this? What could have caused this issue?
It's the first time it happened since we installed Ax 2009 in 2014.
I have the same question (0)
  • André Arnaud de Calavon Profile Picture
    André Arnaud de Cal... 297,200 Super User 2025 Season 2 on at
    Ax 2009 - missing methods, fields after "axcus.aod Error Code: 64 = network name no longer avail"
    Hi vv1984,
     
    Can you provide us with an update on this question, please? Did you manage to solve the issue with Martin's comments or do you still need more help from the community?
  • Martin Dráb Profile Picture
    Martin Dráb 235,796 Most Valuable Professional on at
    Ax 2009 - missing methods, fields after "axcus.aod Error Code: 64 = network name no longer avail"
    I don't know what caused it, it might be a file system error or some problem with communication between AOS and the file server that ultimately led to data corruption.
     
    The first thing I would try it rebuilding the application index (.aoi). The next one (which may be worth doing in all cases) is deploying the CUS layer again (if you deploy whole layers, which I strongly recommend) or taking it from a backup.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

News and Announcements

Dynamics 365 Community Calls Return
Join experts in person to explore low code and AI agents at the Power Platform Community Conference sponsored by Microsoft
Responsible AI policies for the Community

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Mansi Soni – Community Spotlight

We are honored to recognize Mansi Soni as our August 2025 Community…

Congratulations to the July Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Finance | Project Operations, Human Resources, AX, GP, SL

#1
Sohaib Cheema Profile Picture

Sohaib Cheema 665 User Group Leader

#2
Martin Dráb Profile Picture

Martin Dráb 595 Most Valuable Professional

#3
Yng Lih Profile Picture

Yng Lih 558

Last 30 days Overall leaderboard

Featured topics

End-of-life Announcement for Microsoft Dynamics GP

Product updates

Dynamics 365 release plans