Troubleshooting AX AOS Peformance on VM

Hello!
Thought to share one odd issue regarding AX performance

Issue:

We have one of our DEV AOS's running on a separate VM and suddenly we were experiencing performance degradation

Solution:

Upon troubleshooting with help of our networking guys, we figured out that the culprit was cqmgserv.exe.
We no longer needed this HP Monitoring service so disabled it and that solved the issue.

Troubleshooting AOS Service Startup Error Object Server 01 The specified schema name DBO either does not exist

Few days back, one of my AOS Services won't start. In the Event Viewer, I found this error message:


Error 1 - Object Server 01 The database reported session 1 AOS [Microsoft][ODBC SQL Server Driver][SQL Server]The specified schema name DBO either does not exist


Solution - After some troubleshooting, Found that this was due to the Collation change at SQL Server level which was made sometime back for testing Chinese characters.


Changed the Collation back to the default collation of SQL Server and now AOS Service started.


SQL Collations is a whole new world which I explored a while ago. Will be writing a detailed post soon on that. Watch out this space!

Scheduling a Batch Job through code, Batch Multithreading and creating batch tasks at run time

Last few days, I was bit busy exploring and experimenting with Batch  Jobs and multithreading as we need to load balance these jobs on our 6 AOS Servers to get the maximum performance out of them

Thought to share the following links available on msdn and Klaas blog.

http://msdn.microsoft.com/en-us/library/cc636647.aspx


http://www.artofcreation.be/2010/10/03/batch-multithreading/

Troubleshooting Dynamics AX 2009 SSRS Report Generation Error

None of the SSRS reports were rendering correctly. This was working well before the Xmas break.

Error:

An error has occurred during report processing.
The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040) 

Solution:

As you see from the error above, it's not much helpful and sort of misleading as I thought it could be the SSRS components which got installed in GAC may have got corrupted. After some troubleshooting, found that the Validate button on Administration > Setup > Reporting Services > Reporting Servers was not validating the datasource folder properly. Then, performed the following steps to rectify it.

a. Recreated the reporting data source and folder and now the Validate button started functioning without any issues.

b. Restarted SSRS Service from the Control Panel > Services window (As without restarting I was getting the same dll error) to make it work.

Dynamics AX Troubleshooting AOS Error Internal Error occured executing stored procedure when creating session for the AOS

Issue

One of our AOS suddenly stopped working and it won't restart any more. Learned that there was a database refresh the last night.

The error I found in event viewer was  Object Server 01: Internal Error occured executing stored procedure when creating session for the AOS (Screenshot below)

Solution

http://daxdilip.blogspot.com/2010/09/object-server-01-internal-error-occured.html

[Updated] How to Debug Batch Jobs running on Dynamics AX 2009 with AOS Server on Windows Server 2008

I'm having a hard time debugging batch jobs on server, my batch job executes but it never hits the breakpoint.

I followed all the steps mentioned in this blog post http://blogs.msdn.com/b/x/archive/2009/06/25/step-by-step-checklist-for-debugging-batch-jobs-in-dynamics-ax.aspx

and additionally installed the hotfix as our AOS Server runs on Windows Server 2008, but still unable to hit the breakpoint.

Just wondering, if anybody out there has achieved success in debugging batch jobs on AOS Server (which runs Windows Server 2008)? If yes, would be glad if they can share their experiences or email me on maildotdilipnATgmaildotcom or put a comment below. Thanks

Thanks to all who replied me via emails and comments. Appreciate it.

Solution (If you debugging batch jobs on Windows Server 2008)

a. Make sure you have checked all the steps http://blogs.msdn.com/b/x/archive/2009/06/25/step-by-step-checklist-for-debugging-batch-jobs-in-dynamics-ax.aspx



b. Run the hotfix mentioned in the blog link above
 
c. Logon to your remote desktop using (mstsc /console)
 
d. Run the Debugger As Administrator i.e. right click AxDebug. exe and Run as Administrator.
 
Observation - It's not necessary to logon with the same account as your AOS Service account, I logged in with my network alias which happened to be the admin on the box and it worked well for me, Usually in strict environments we won't get access to the service account's password.
 
In my scenario, I missed Steps c and d. This is required if you run on Win Server 2008

Error - Your Microsoft Dynamics Session is no longer valid. Log off your computer and log on again

Suddenly, we are getting this communication error whenever we try from our client to connect to our DEV AOS box with , which says the below, The only change which we did to our environment recent days were changing the database server from one box to another:

We tried the following options but nothing works:

a. Deleted axapd.aoi file and Restarted AOS on DEV box
b. On the Client, tried clearing the .auc files (Axapta object cache files) from the local user profile, but that too doesn't work
c. Checked if the stored procedures CREATESERVERSESSIONS and CREATEUSERSESSIONS existed in the database and if the service account running AOS Service has enough permissions to execute the sp's
d. Apart from this error, in the event viewer, we were getting bunch of RPC Errors which says "Object Server 01: RPC Error: RPC Exception 1702 occured in sesssion 6", We are on Dynamics AX 2009 SP1 and the latest rollup (Rollup 5), so it should have the RPC Hotfix installed
e. Thought that the stored procedures CREATEUSERSESSIONS were cached on the db server so used the flush commands to clear the cache http://www.sql-server-performance.com/tips/dbcc_commands_p1.aspx, still no luck
f. Installed a new AOS on the box, same issue, we have 3 AOS's on that box and we get the same error when any client connect to the 3 AOS's.
g. Ran SQL Server Profiler, checked SQL Management Log but couldn't detect anything
h. Cleared SYSSYSTEMSEQUENCES table, this table is used by AX when it startups, cleared the sessions from SYSCLIENTSESSIONS table but still no luck

WORKAROUND:

Installed AOS on a different box , left the application files and database as it is, and this works. We have raised a ticket with Microsoft and they are working on this. Would be interested to see what they can come up with.

Will keep this post updated if we come across some breakthrough for the original issue

Object Server 01: Internal Error occured executing stored procedure when creating session for the AOS

We were getting this error when trying to start the AOS Service after we restored an AX Database from one of our existing environments:

Error : Object Server 01: Internal Error occured executing stored procedure when creating session for the AOS

By seeing this error, I was quickly able to conclude that it has to do something related to the stored procedures which creates server sessions and client sessions, I compared the permissions of the sp's with our other AX databases and found that the aos service account didn't have "Execute" permissions on these 2 sp's and hence the errors, After assigning the permissions, we could start the service without any hiccups

I had a similar experience troubleshooting these stored procedures in the past which has been blogged http://daxdilip.blogspot.com/2009/02/sysserversessions-and-sysclientsessions.html

 

Microsoft Dynamics AX Application Object Server running on an Operating System thats not supported

We were getting this error frequently last week on our DEV AOS box. Every 2 minutes the AOS used to go down with this entry in the event viewer (screenshot below)

Solution

Without wasting much time, I googled around to see if my fellow Dax-ians are getting the similar error as me. Found couple of links which spoke about the Dynamics AX 2009 Rollups (which we hadn't installed on our box as we were reviewing the fixes available in roll ups and how we benefit from them)

http://www.ms-news.net/f510/dynamics-ax-2009-sp1-aos-service-11954174.html

http://blogs.msdn.com/b/emeadaxsupport/archive/2009/06/15/error-executing-code-insufficient-memory-to-run-script.aspx

https://mbs.microsoft.com/knowledgebase/kbdisplay.aspx?wtntzsmnwukntmmyymyqksymxosooumlsptppzlsnrlsqxpn

We were thinking to go ahead with the rollups, but we tried one last attempt by stopping the AOS Service, deleting the axapd.aoi file and then restarting the AOS Service, This worked for us.

Handy screenshot to get the version number related with the roll ups