Microsoft Dynamics AX (Archived)

Inventory Closing AX 2012

(0) Share

Report

Posted on by Dhanicca Macatangay

355

Hello Microsoft Community!

We are currently encountering an Inventory Close related issue with our client.

They ran an inventory close in their server for it not to be interrupted but unfortunately upon checking the status of the inventory close it was paused due to undetermined error.

We initially checked it and got this error log.

We are on the process of investigating the issue and we would also like to ask for any help that could aid us to fix it.

Furthermore, may I also ask for the possible impacts of this error?

Thank you very much!

*This post is locked for comments

I have the same question (0)

All responses (9)

Answers (2)

Suggested answer

Ludwig Reinhard Microsoft Employee on at

Like (0)

Report

Hi,

For the SQL error message:

Please get into contact with a system administrator or developer who looks into the error that the SQL database issued an error.

Once that is finished you should be able to resume the inventory close by making use of the 'resume' function/button.

Best regards,

Ludwig

Was this reply helpful? Yes No
Dhanicca Macatangay 355 on at

Like (0)

Report

Hi Ludwig,

They were able to close the inventory for May and June 2019. The client is having trouble completing the July 2019 inventory close and this is also the first month where volume of Production order transactions were posted.

Does this affect the length of time needed to run the inventory close? If not, as a standard how long shall an inventory close takes place?

Also, what can be the impact of running the inventory close for days and still not finish? How can we know that the inventory close is already done or is only hanging?

Thank you for the response!

Best Regards,

Dhanicca Macatangay

Was this reply helpful? Yes No
Verified answer

Ludwig Reinhard Microsoft Employee on at

Like (0)

Report

Hello Dhanicca,

You can setup so-called batch helpers that accelerate the inventory close.

Some tips and tricks how to speed up the inventory close can be found here:

microsofterpax.wordpress.com/.../

Note:

Those tips and tricks are not related to the error message that you received further above. To get this error fixed you would need a technical expert looking into this.

Best regards,

Ludwig

Was this reply helpful? Yes No
Suggested answer

André Arnaud de Cal... 301,141 Super User 2025 Season 2 on at

Like (0)

Report

Hi Dhanicca,

I have seen similar errors in the past. Can you check with your SQL database administrator if there are maintenance jobs running at the same time as this closing job is running? If so, there might be a script which could change some settings for e.g. the index fill factor. This was the culprit in two occasions where I had this or a similar error.

Was this reply helpful? Yes No
Dhanicca Macatangay 355 on at

Like (0)

Report

Hi Andre,

Does restarting the AOS affects the inventory close run? And could possibly be one of the reasons for the occurrence of the SQL error?

Thank you!

Best Regards,

Dhanicca Macatangay

Was this reply helpful? Yes No
Verified answer

André Arnaud de Cal... 301,141 Super User 2025 Season 2 on at

Like (0)

Report

Hi Dhanicca,

Restarting the AOS during the inventory close run for sure has impact. But then it gets interrupted by the AOS. Your error comes from a change on the SQL database table. This might be caused by the maintenance or someone did change the table in the AOT directly when this job was running. Usually someone is not changing the table in the production environment directly (however, I have seen weird things happening...).

Was this reply helpful? Yes No
Dhanicca Macatangay 355 on at

Like (1)

Report

Many thanks for the insights, Ludwig and Andre.

I'll get back here to share the steps we did once we solved this issue!

Was this reply helpful? Yes No
Dhanicca Macatangay 355 on at

Like (0)

Report

Hi Ludwig and Andre,

With the help of our technical expert and developer, they found out that batch jobs do not conflict with the inventory close run.

We opened ticket with Microsoft for this client-specific error.

Thank you very much!

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

Like (0)

Report
It might be a bug at SQL level depending on your version.

Check neither of these are scheduled while your cursor process is running:

Auto-shrink can also cause this error, when it re-arranges data pages while the cursor is open.

Maintenance plans that do re-indexing can also create the issue.

The problem is often about database buffer. The cursor, is created before any schema change and the cursor is stored in the database buffer, and does not match with the new schema. In that case cleaning the buffer will solve the problem, or a server restart will also do it.

SQL Transaction replication might also cause it.

I suggest run:

DBCC DROPCLEANBUFFERS DBCC FREEPROCCACHE

The use of cursors is often not the best option. Try explicitly setting the cursor to be LOCAL STATIC FORWARD_ONLY. A better way to execute dynamic SQL on databases/servers supplied by a variable is to use sp_executesql and pass strongly typed parameters.

Was this reply helpful? Yes No