AOS machines application ( events )

Here are some events from the AOS machines application event that can be useful when managing an AOS:
Event Log Entries
How to Troubleshoot
Event ID 149. Object Server 01: Ready for operation
Use this to verify the AOS build/version information from the kernel build section.
Event ID 172.
Use this to verify the .Net Business Connector build. This is helpful if you think the issue is related to components not being on the same build.
Event ID 1000
Use this information along with any Event Id’s of 1001 to confirm the times when the AOS crashes.
Event ID 1001
This indicates that they have the option marked to send mini memory dumps to the Watson site. Pass the contents of this event on to your Escalation Engineer so they can review it to see if there is information that points to the issue.
Object Server 01: RPC error: RPC exception 1726 occurred in session X
This means that the AOS had data to send back to the client but the client was no longer available. You can see this if users are ending task on the client when they think processes are hung. If the user does this repeatedly in a short time it can cause an AOS crash or it could point to a process that has a problem and causes an AOS crash. Follow the steps in blog on how to trace a session back to a user. This way you can try to determine the process the user was doing and possibly trace that process.
Object Server 01: No ping from XX. Terminating the session
This error message occurs when the AOS tries to ping the client and does not get a response. You can see this if users are ending task on the client when they think processes are hung. If the user does this repeatedly in a short time it can cause an AOS crash or it could point to a process that has a problem and causes an AOS crash. Follow the steps in blog on how to trace a session back to a user. This way you can try to determine the process the user was doing and possibly trace that process.
Object Server 01: SPID XX for session id XX is still present in the database. Please delete the SPID from the database.
 This means that the SQL Server is still processing data from a client session that was terminated. Especially if you see these right before a crash find out the user that this session belongs to using the steps from blog. This will help you determine the user who had a process running but was no longer in the Dynamics AX client. Find out the process they were running, if possible, and try to trace that process or see if you can reproduce an AOS crash.
Object Server 01: Internal version mismatch. Microsoft Dynamics AX Client from MACHINENAME (0.0.0.0) tried to attach with 5.0.1500.4622 revision of AOS kernel."
This indicates that the AOS and the client builds do not match and can cause problems. This message was added to kernel build 5.0.1500.4622 and higher. The amount of detail returned will depend if the client is also at that version or above. Check the sysuserlog table for the buildnum and computername of clients connecting from an earlier build than the AOS. Example: select distinct(BUILDNUM) from SYSUSERLOG where CREATEDDATETIME > '2011-01-01'

Comments

Post a Comment

Popular posts from this blog

Table ID for the tables in AX 2012 R2

Table ID for the tables in AX 2012 R2 Hi, AccountingDistribution ( accounting distribution 7452 ) AccountingDistributionEventTmp ( accounting distribution 100001 ) AccountingDistributionTemplate ( Accounting distribution template 7453 ) AccountingDistributionTemplateDetail ( Accounting distribution template detail 7454 ) AccountingDistributionTmp ( AccountingDistributionTmp 100002 ) AccountingDistributionTmpAmounts ( Accounting distributions 7455 ) AccountingDistributionTmpJournalize ( accounting distribution 100003 ) AccountingDistributionTmpPurchSummary ( Encumbrance summary 7446 ) AccountingEvent ( Accounting event 7456 ) AccountingEventDateTmp ( Accounting event 100004 ) AccountingEventTmp ( Accounting event 100005 ) AccountingTmpEvent ( Accounting event 100006 ) AccountSumMap ( Account totals 1326 ) AddressCountryRegionBLWI ( BLWI country/region 1049 ) AddressCountryRegionGroupBLWI ( BLWI country/region groups 1050 ) AddressZipCodeImportLog_NL ( ZIP/postal code import log
Read more

Microsoft Support Lifecycle

Products Released Lifecycle Start Date Mainstream Support End Date Extended Support End Date Service Pack Support End Date Notes Microsoft Dynamics AX 2009 8/14/2008 4/10/2018 10/12/2021 1/11/2011 Mainstream support for Microsoft Dynamics AX 2009 is extended as shown in order to provide all customers with the standard lifecycle transition timeline. Please see additional details here . Microsoft Dynamics AX 2009 Service Pack 1 11/3/2008 Review Note Review Note Support ends 24 months after the next service pack releases or at the end of the product's support lifecycle, whichever comes first. For more information, please see the service pack policy here . Microsoft Dynamics AX 2012 9/25/2011 10/9/2018 10/12/2021 Mainstream support for Microsoft Dynamics AX 2012 is extended as shown in order to provide all customers with the standard lifecycle transition timeline. Microsoft Dynamics AX 2012 R2 2/19/2013 10/9/2018 10/12/2021 Mainstream support for Microsoft Dynamics AX 20
Read more