Dynamics 365 CommunityForums Microsoft Dynamics GP (Archived) Recovery of unsuccessf...

Recovery of unsuccessfull posted records due to sudden power shut down or connection failure

(0) Share

Report

Posted on by Community Member Microsoft Employee

Dear Sir / Madam,

One of our client is using gp remotely for it's branches through terminal servers and due to sudden power shutdown or connection failure transactions are getting incompletely posted in the database and these incomplete transactions are not retrievalbe through gp screen. Why the gp is allowing to save incompelte records and why it has no roll back facility? Kindly explain and provide the solution for this problem.

Your Immediate reply will be highly appreciated.

Thanks & Regards,

GP Technical Consultant

*This post is locked for comments

All responses (1)

Answers (0)

Suggested answer

Community Member Microsoft Employee on at

Like (0)

Report

Re: Recovery of unsuccessfull posted records due to sudden power shut down or connection failure

Saving uncompleted transactions is infrequent; the only cause for this behavior is having the power shutdown in the middle of posting a transaction that has saved a part (header or details) of the transaction without saving the other part, and such case could be handled by the user using ledger reconciliation check links operation.

If the transaction was not accessible by GP screen, and was not fixed by the GP utilities, then an expert must investigate and identify missed transactions then fulfill application workflow or delete and reenter the transaction.

However, you could work around such events by utilizing the GP modules that distributed the transactions over your network or running the application over a failover clustering environment.