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