D365FO: batches and workflows not working after database restored in VM




Tired and worried of your batches malfunctioning/not working, after you have restored your database in your local VM? In case if you have faced this issue, just thought of sharing with you – this could save a good amount of your time.

  1. Going to your System admin à setup à Batch group, in case if you are unable to see this tab:


This tab is very much essential, as this makes you assign servers to your batch group. Skipping this tab, will essentially make your batch groups left unassigned to any batch server.

  1. A little inspection in the form’s INIT method said:







Which means if the ‘Batch priority based scheduling’ is enabled à then this tab won’t be shown.

  1. Go to features à and see this features is enabled:





 

Turn it off and come back to your Sys admin page à batch group à reload the page. This tab will be shown now:

 

 




Once you have selected the server, your batches should resume now. 

Now whoa, whoa, whoa -- your batches are still not running? You gotta check your event viewer.

There will be errors like this:

Object Server DynamicsAXBatchManagement:

[Microsoft][ODBC Driver 17 for SQL Server][SQL Server]Index "I_3368STATUSORIGSTARTDATETIMEIDX" on

table "BATCHJOB" (specified in the FROM clause) is disabled or resides in a filegroup which is not

online.

UPDATE T1 SET STATUS=?,STARTDATETIME=?,EMITBUSINESSEVENT=?,MODIFIEDDATETIME=?,RECVERSION=?,STARTDATETIMETZID=? FROM BATCHJOB T1 WITH ( INDEX(I_3368STATUSORIGSTARTDATETIMEIDX), FORCESEEK, READPAST, ROWLOCK, READCOMMITTEDLOCK) WHERE ((STATUS=?) AND (ORIGSTARTDATETIME<=?)) AND EXISTS (SELECT 'x' FROM BATCHJOBACTIVEPERIOD T2 WITH ( READPAST ROWLOCK READCOMMITTEDLOCK) WHERE ((T2.ID=T1.ACTIVEPERIOD) AND ((((T2.FROMTIMEUTC<=T2.TOTIMEUTC) AND (T2.FROMTIMEUTC<=?)) AND (T2.TOTIMEUTC>=?)) OR ((T2.FROMTIMEUTC>=T2.TOTIMEUTC) AND ((T2.FROMTIMEUTC<=?) OR (T2.TOTIMEUTC>=?))))) AND EXISTS (SELECT 'x' FROM BATCH T3 WITH ( READPAST ROWLOCK READCOMMITTEDLOCK) WHERE ((T3.BATCHJOBID=T1.RECID) AND (T3.GROUPID=?))))

session 2 (-AOS-)

 

 

Then you need to run the below queries:

ALTER INDEX [I_3368STATUSORIGSTARTDATETIMEIDX] ON [dbo].[BatchJob] REBUILD  WITH ( PAD_INDEX  = OFF, STATISTICS_NORECOMPUTE  = OFF, ALLOW_ROW_LOCKS  = ON, ALLOW_PAGE_LOCKS  = ON, ONLINE = OFF, SORT_IN_TEMPDB = OFF )

GO

 

 

ALTER INDEX [I_22692FINISHINGIDX] ON [dbo].[BatchJobHistory] REBUILD  WITH ( PAD_INDEX  = OFF, STATISTICS_NORECOMPUTE  = OFF, ALLOW_ROW_LOCKS  = ON, ALLOW_PAGE_LOCKS  = ON, ONLINE = OFF, SORT_IN_TEMPDB = OFF )

GO

 

These are required to enable the above mentioned keys from BatchJob and BatchJobHistory tables.

Now you would see your batches have resumed, your workflows have resumed working too.

Comments

Post a Comment

Popular posts from this blog

X++ : mistakes which developers commit the most

Image
   The most important thing is to remember where and when to write the code. a. Developers have an inherent habit of writing erratic select statements: select * from custTable where custTable.AccountNum == <SomeValue> Where in essence we need to make use of optimized choice of fields in the select statement. b. Making use of 'continue' keywords: While select custTrans where <someConditions> { if (cusTTrans.CustGroup != mappingTable.CustGroup) { continue; } } 'Continue' statements are precisely a very unhygienic way of designing your code. The above statement could have been easily ornamented by using exists/not exists joins. Using Continue statements would eventually result in a high performance impact. Also select statements should be made punctuated with a 'firstonly' clause -- just not from best practise standpoint, but also from performance considerations. c. Writing nested loops: This is a common mistake that perha
Read more

Make your menu items visible on main menu, conditionally,, using this cool feature of D365FO

Image
  Wassup guys? I am sure you must have encountered this situation where you needed to display your menuItems, on main menu, based on some condition, haven't you? This was only possible by using config keys and flights. Things get a bit tricky,  when suppose you have a requirement like this: you need to make it dynamic, by introducing a toggle switch on a field on a paremeter form.  Suppose on Accounts Receivables Parameters >> You have a field called ' Show US customer '. You have a requirement that says when you turn on this toggle, then only the menuItem ' Input SSN details ', under AR module. This is now highly acheivable by leveraging subscription to 'SysMenuNavigationObjectFactory' class, simply by saying a. Create a new class USMenuItemsVisibilityManager b. Copy the following method, with proper documentation (don't change signature/anything else) [SubscribesTo(classstr(SysMenuNavigationObjectFactory), staticdelegatestr(SysMenuNavigationObjec
Read more

Speed up your execution performance by using SysGlobalCaches

Image
  Ever come across a situation where you needed to  a. Using a multi-threaded batch to import a journal header and lines, from a staging table. The table already contains the Journal Ids which you need to assign to the header and allocate the lines under that header. b. You need to continuously check after each line being imported, if the journal with the Id has been created. If not, it will create the header and create the lines under it;  If yes, it will directly create the lines for the header (Find or create). c. As you could rightly guess, this architecture has an inherent sluggishness associated with it -- each time you keep on checking if the header has been created or not, it does mean a lot of performance effects, as a consequence. Also as you can understand it's a multithreaded code, which means each thread has no direct relation with the other -- which does mean there is no way I can talk between the threads/pass on any information. SysGlobalCaches to the rescue: I perso
Read more