Inventory Closing Job is Stuck

(0) Share

Report

Posted on by Community Member

We had not run inventory closing for last 1.5 years so when running it for the first time I had this in my mind that it is gonna take a little longer but to my surprise the job is not getting finished for last 15 days. I ran it on server but every morning I find it paused then I resume it but even after 2 weeks it hasn't finished.

The cancellation button is inactive and I don't know what to do now. What could be done from end user's perspective?

*This post is locked for comments

I have the same question (0)

All responses (5)

Answers (1)

Sort by

Verified answer

Ludwig Reinhard Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

Hi,

That it a difficult issue.

Have you setup any additional helpers and batch servers that might accelerate the process?

What you can try in addition is possibly running incremental inventory Closes, that is one for Jan 16, Feb 16, Mar 16 ... until you arrive at June 17.

Best regards,

Ludwig

Was this reply helpful? Yes No
Fredrik Sætre 12,644 on at

Like (0)

Report
Copy link

Link copied!

What does your log say?

Was this reply helpful? Yes No
Suggested answer

guk1964 10,888 on at

Like (0)

Report
Copy link

Link copied!

Not running inventory close regularly is a common bad practice for this performance reason.

Maybe you have overfull event logs, or temp databases, or bad data, or millions of transactions, or..... its difficult to guess.

If you have not run inventory close, then maybe there other data, log management, or sql maintenance tasks also not done, that are overloading the system.?

Have you tried the Pause and Resume option?

Ludwig's suggestion of incremental closes is probably your best option, However, you first need to complete or cancel the one that's running. Cancellation is not without its challenges,

I am not sure what version you are on - but it sounds like it may be at least two years or more old - so check out this bug https://community.dynamics.com/ax/f/33/t/71527 where a spelling error seems to have crept into the code. Also look for hotfixes.

Look at the settlements of what has been processed so far and verify that all of those have the necessary posting accounts, if an account is missing, then try to manually enter it in the InventSettlements table.

If all else fails restore a back up - and start again - but If its already been running two weeks that will be a problem with end users, and you may need expert technical/Microsoft help to kill the process.

Was this reply helpful? Yes No
Community Member on at

Like (2)

Report
Copy link

Link copied!

Fredrick got it right. I just checked the log and it is giving error for several items "Number sequence Inve_18 has been exceeded."

So I have increased the maximum range of the said sequence by two more characters. I will resume the closing procedure and will let you know the outcome.

P.S: Ludwig I will come to your incremental closing solution incase this didn't work. Cheers

Was this reply helpful? Yes No
guk1964 10,888 on at

Like (0)

Report
Copy link

Link copied!

Maybe do it for smaller time frames e.g. 6 quarters rather than for 1.5 years.

Was this reply helpful? Yes No