Our support engineers have assembled the top recommended solutions for you.
Microsoft Dynamics AX 2012CRM Connector in Microsoft Dynamics AX 2012Financials Management in Microsoft Dynamics AX 2012Upgrading to Microsoft Dynamics AX 2012
Microsoft Dynamics AX 2009
Application Object Server (AOS)
Enterprise Portal and Role Centers
Inventory Costing in Microsoft Dynamics AX 2009
SSRS and SSAS Integration
Long time reader, first time poster
Earlier this week we reinstalled AX 2012 in our development environment with the 2/1/2012 Feature Pack release. Kernel version: 6.0.1108.403, Application version: 6.0.947.280
Now whenever I attempt to delete a row from the HcmPositionDetail table, I get the following sequence of infolog events:
Note that line 12 of the delete method on HcmPositionDetail is a call to super();. I've tried surrounding super() with calls to ttsbegin and ttscommit, but that throws a different error (ttscommit can't be called before ttsbegin).
Is anybody else seeing this? I have some customizations in the USR layer to HcmPositionDetail, but even after I removed them I still can't seem to delete rows. The only workaround I've found so far is to delete the applicable row(s) via SQL, but that's hardly a sustainable solution. Is this a known issue? Any ideas?
Were you able to resolve this? I am having similar issues after feature pack upgrade. If you were able to come up with a solution please let me know. Thanks!
Is there a reason for the difference in Kernel and Application build numbers?
If I had to guess on his situation. There are probably multiple AOS instances running on the same server. With one of the AOS instances being more updated than the one in the post. Fairly educated guess as I have a similar setup in the environments that I run in.
Ok. I have a new client with the same build numbers the OP posted. So I am trying to determine if this is problematic. If the previous partner skipped installing the Feature Pack CU3 on the database. The clients and AOS both have the build number 6.0.1108.403 but the application is 6.0.947.280 (CU2).
Does the server have multiple AOS instances? If so what is the build level of the others?
Only 1 AOS. The build number of both AX32.exe and AX32Serv.exe is 6.0.1108.403
has anyone been able to resolve this. we have 1 AOS and we are getting this error. we are running R2.
Other Microsoft Sites
I'm a Customer
I'm a Partner
Use the official Twitter tags:
#MSDYNCOMM | #CONV13