You’re offline. This is a read only version of the page.
Announcements
150
Hi
One of my customers suddently found out that batchjobs did not run. After lots of research and including full CIL compile I found out that a customer superuser had created a new record i table PARTITIONS. The new partition is named 'aaaa'. It looks like a test or something. Usually my customers only uses the default partition.
This is the error from the applicationlog of the batch AOS:
Object Server 01: Microsoft.Dynamics.Ax.Xpp.ErrorException: Exception of type 'Microsoft.Dynamics.Ax.Xpp.ErrorException' was thrown.
at Microsoft.Dynamics.Ax.MSIL.Interop.throwException(Int32 ExceptionValue)
at Microsoft.Dynamics.Ax.MSIL.Interop.ttscommit()
at Dynamics.Ax.Application.BatchRun.serverGetOneTask(Batch batch, String serverId) in BatchRun.serverGetOneTask.xpp:line 116
at Dynamics.Ax.Application.BatchRun.serverGetTask(Batch batch, String serverId) in BatchRun.serverGetTask.xpp:line 10
at BatchRun::serverGetTask(Object[] )
at Microsoft.Dynamics.Ax.Xpp.ReflectionCallHelper.MakeStaticCall(Type type, String MethodName, Object[] parameters)
at BatchIL.startTask()
at BatchIL.CheckBatchJobs()
at BatchIL.threadFunc(Object threadArg)
I've debugged the method BatchRun.serverGetOneTask() in batch via VS2013 and when the outer loop is handling the new PARTITIONS record the method fails.
So ... I don't know. I can't delete the new partition record from within the Partions form. But if the superuser did not continue setting up the new Partition (I don't think he did but I don't know yet) maybe I may delete the new partition record from tablebrowser or SQL Server?
Or maybe establishing a backup of the db (oh no - one day of work is gone) is the only solution?
Any suggestions are very welcome.
Best regards,
Ebbe Jensen,
Ax supporter
Was in touch with Microsoft
Via SQL Server Management Studio checked main tables for records with the new partition. Only 2 records i table UserInfo were found. An "admin" and a "guest" account. They may only got to do with access to the new partition.
So via SQL Server Management Studio the new partition was deleted and the batchjobs are now executing again.
Thanks for helping out.
BR,
Ebbe
Hi
Thank you for your suggestions. I'll give it a try. MIcrosoft does not return to me so I'm glad that you do.
I've talked to the superuser now. He was working on budgets. Copying them or something. He was rightclicking some budget related record a presented all fields of the record. He tried to change the Partition field but he couldn't. He somehow managed to create a new partition there. Not via the Systemadministration module. I don't think he finished any Partition setup guide.
I hope the new Partitions record can be deleted but I'll have research at first.
BR,
Ebbe Jensen
HI Ebbe,
When only the record for the partition was created, but not used elsewhere, you can indeed delete it from SQL. Dick Wenning wrote a blog in the past to delete a partition which could contain already more records: Delete an AX 2012 R2 or R3 partition
For sure, test carefully before applying it on a production environment.
I've never done that, but I would choose deleting the partition record in SQL. Then I would also check if there are records in any table for this partition (and delete them too). Of course, you should test it on another environment before doing it in production.
#1
André Arnaud de Cal...
294,079
Super User 2025 Season 1
#2
Martin Dráb
232,860
Most Valuable Professional
#3
nmaenpaa
101,158
Moderator
Share
Report
All responses (
Answers (
