Try Microsoft Edge
A fast and secure browser that's designed for Windows 10
We are currently using NAV 2013 R2
While processing the VAT calc. & Settlement Statement Nav had crashed
When I logged back in NAV had only processed one side of the journal [for the purchase ledger] but did not post the double entry into the settlement G/L account
This has resulted in an unbalanced TB
I can not reverse the transaction as it's not a journal and I cant post a journal to rectify this one sided entry as my journal wont balance.
Any idea's on how I can fix this problem - reverse/delete this one sided entry
Did your SQL-server did crash too?
Or do you have any customization in that process?
What you are describing is impossible with the NAV-standard. As soon as the client crashes, the SQL-server notices the connection loss and runs a rollback automatically.
I believe the SQL server did crash - the message I received was the Program is not responding and then shut down
I would of thought there was a fail safe for this not to happen - but unfortunately it has
Any suggestion's on how to resolve this?
Normally, when the client does crash, the SQL is still alive.
Did you had to restart the ServiceTier or SQL-Server then?
From a solution point of view:
- when the incident is not to far away, restore an SQL-backup
- or, analyse the postings and cleanup manually (but this should be done by someone with experience)
Business Applications communities