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

Critical Hot fixes ( AX 2009 )

Critical Hot fixes The Dynamics AX kernel hotfixes are cumulative fixes that address issues in the executable and dll files for Dynamics AX. These hotfixes do not modify any X++ code, therefore they do not require full X++ code review when deploying to your environment. The kernel fixes are designed to address stability, performance, and compatibility with other software applications. When you apply a kernel hotfix you do want to do testing and the key areas to focus on are printing, pdf functionality, and integration points. When you apply a kernel hotfix you want to be sure that it is applied on all machines that have a Dynamics AX component, such as the client, AOS, or .Net business connector. If you do run into any issues with the Kernel hotfix you can safely remove the hotfix from the Programs and Features area of the Control Panel. It is recommended that you consider regular installation of Kernel rollups in your Microsoft Dynamics AX environments. We find that many times w
Read more

This transaction has been marked for settlement by another user in AX 2009 / 2012

Image
“I need to settle a customer (or vendor) transaction but when I go to the ‘Settle open transactions’ form for the customer (or vendor), I cannot mark the transaction. There is a red icon in the ‘Is marked’ field and I receive an error if I try to mark. I’ve looked all over and I cannot find where to unmark it." Solution When this happens, the user has generally already done their due diligence and checked the likely places to find where the transaction may be marked – in other journals of the same type, in the Settle open transactions form, etc. and still cannot find where it is mysteriously marked. To find where the transaction is marked, take the following steps: 1. Go to Accounts receivable-> Common-> Customers-> All customers-> highlight customer-> Collect tab-> Settle open transactions (similar path for Vendor transactions). Normally you will see the transaction still has the red icon indicating the transaction is still marked elsewhere. 2. Highlight the rec
Read more