¿Qué podemos hacer con los eventos que aparecen en el event viewer, cuando hay issues en el AOS como: Crash, Hang o comportamientos extraños?
Hola,
Siempre cuando se tienen issues de conexión, o caídas, o hangs de nuestro AOS, siempre tenemos que revisar el event viewer para que nos dé un poco más de información y un punto de referencia para nuestro troubleshooting.
Los eventos más comunes durante un troubleshooting de soporte casi siempre son los siguientes:
****
Event ID: 110 (EVMSG_MSG)
Description: A general event message that you can use for tracing the causes of other events.
Action: N/A
Applies to: AOS COM
This event means that a Dynamics AX Client (or BC.NET) did not validate the session
for some time (several minutes). This could mean a Dynamics AX Client as crashed or
was terminated hard (kill session in Task Manager) or this could indicate Network
Errors. So or so the AOS has terminated the Client session to save licenses
Event ID: 180Para este evento está el siguiente Hotfix 913184
To do this I would recommend:
1. Schedule a time for all users to be logged out of AX.
2. Login to AX and check the Administration -> Online Users screen, end any remaining sessions
3. Logout of AX
4. Shutdown the AOS service
5. Restart the SQL server (this will clear any leftover SQL sessions from AX clients)
6. Start the AOS service
Event ID: 117 (EVMSG_SQL_ERROR)
Description: A database error has occurred. The message body will specify the error message and the session/userid that is causing the error.
Action: Depending on the error, check the database server for errors, or correct the code that is causing the error. Applies to: AOS COM
Event ID: 140 (EVMSG_SQL_LOGINFAIL)
Description: The Object Server could not log on to the SQL server.
Action: This event contains the error message that is issued by the SQL server when Microsoft Axapta tried to log on. The event log also contains an event EVMSG_SQL_DIAGNOSTICS (163) that specifies the basic parameters that are used to establish the connection. Review these events, and then correct the Microsoft Axapta configuration, the ODBC setup, or the database security to resolve this problem.
Applies to: AOS
Event ID: 163 (EVMSG_SQL_DIAGNOSTICS)
Description: This event provides diagnostics information about the Microsoft Axapta SQL engine.
Action: See the following article in the Microsoft Knowledge Base: KB909229 Event ID 163 is logged for Microsoft Axapta Object Server Applies to: AOS COM
Event ID: 180
Para este evento está el siguiente Hotfix 913184
To do this I would recommend:
1. Schedule a time for all users to be logged out of AX.
2. Login to AX and check the Administration -> Online Users screen, end any remaining sessions
3. Logout of AX
4. Shutdown the AOS service
5. Restart the SQL server (this will clear any leftover SQL sessions from AX clients)
6. Start the AOS service
Este otro Link, contiene una compilación de Eventos comúnes en tu event viewer, que van del 103 al 173.
También les recomiendo el siguiente link de KB.
Donde podrán tener los eventos 108 & 142 que corresponden al Login de usuarios en Dynamics AX
Integralos a tu toolbox como Ingeniero de Dynamics AX.
Espero te sriva.
Eumir Arnäiz