Hi Team,
Once I check the Event Log while crash happens(services stop).Blow errors are there.
First error
Object Server 01: The database reported (session 1 (-AOS-)): [Microsoft][SQL Server Native Client 11.0][SQL Server]Could not find stored procedure
'ITFLAX2012R3PRODUCTION_model.dbo.XU_IsModelIdInstalled'.. The SQL statement was: "{ CALL [ITFLAX2012R3PRODUCTION_model].[dbo].[XU_IsModelIdInstalled](?, ?) }"
second error
Object Server 01: Unexpected situation
More Information: Cursor building error 1
Third Error
Faulting application name: Ax32Serv.exe, version: 6.3.5000.5032, time stamp: 0x59305c38
Faulting module name: KERNELBASE.dll, version: 6.3.9600.18666, time stamp: 0x58f33794
Exception code: 0xc0000005
Fault offset: 0x00000000000095fc
Faulting process id: 0xc2d4
Faulting application start time: 0x01d3207be5ef9e5c
Faulting application path: C:\Program Files\Microsoft Dynamics AX\60\Server\ITFLAX2012R3PRODUCTION-AOS2\Bin\Ax32Serv.exe
Faulting module path: C:\Windows\system32\KERNELBASE.dll
Report Id: f6f71fe5-8c72-11e7-80c5-000c2930f414
Faulting package full name:
Faulting package-relative application ID:
I am using AX 2012 R3
*This post is locked for comments
[View:https://community.dynamics.com/ax/b/axaptavsme/archive/2015/04/26/how-to-delete-auc-files:750:50]
[View:https://community.dynamics.com/ax/b/makecreatereiterate/archive/2015/09/03/finding-the-auc-files-in-a-flash-where-to-find-the-appdata-folder:750:50]
delete cache files??? what that means
Then something is fishy here, since you are showing version 6.3.3000.111 here, but your AX AOS crash event log entry says a higher version:
Faulting application name: Ax32Serv.exe, version: 6.3.5000.5032
You must make sure kernel version matches, otherwise it will cause a lot of issues! Communication protocols are regularly adjusted between patch versions, which can cause unreliable behavior and crashes.
Again, same instructions: patch it all up, delete cache files, and if it still crashes, collect a crash dump and open a support incident.
I Vilmos,
My Enviorment Details is below
Kernel version:6.3.3000.111
Application version:6.3.3000.111
You seem to be using an older kernel, the latest one is not older than 2 weeks, this would be the first thing Microsoft would suggest as well.
blogs.msdn.microsoft.com/.../overview-of-microsoft-dynamics-ax-build-numbers
Make sure you patch up all AX components, you are not allowed to use different client and server executables and assemblies..
Do you have enough resources? I have seen AOS crashes when memory was too low, and due to a memory leak in a customization or in the kernel it went kaboom due to eating up all resources. Our deployment has 180 concurrent users, split between 2 AOS instances, which has 8 physical CPU cores and 32 GB RAM (+4 additional AOSes for batch/reporting/AIF integrations).
Finally, you could collect a crash dump using the Windows Error Reporting (WER) tool by setting a registry key to capture a first-chance exception, then open a Microsoft Support Incident and upload it to the support team to check what exact code call causes the crash.
There are 100 license,three AOS loadbalancing enviorment,but concurrent users go 180 .
Concurrent user is alaways more than no of license customer has purchased.
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
André Arnaud de Cal... 291,240 Super User 2024 Season 2
Martin Dráb 230,104 Most Valuable Professional
nmaenpaa 101,156