In the last couple of weeks, the AOS crushed several times, and they are getting a variety of errors in the Event Log. Here are the error messages we have seen:

(1) This error appeared when the AOS crushed yesterday and previously:

Faulting application ax32serv.exe, version 4.0.2163.0, stamp 455e7fa7, faulting module ax32serv.exe, version 4.0.2163.0, stamp 455e7fa7, debug? 0, fault address 0x00197bdf.

(2) This error appears on occasion:

Object Server 01: Dialog issued for client-less session 1: Cannot edit a record in LastValue (SysLastValue).

An update conflict occurred due to another user process deleting the record or changing one or more fields in the record.

(3) Not sure if this issue is related, but we are seeing this warning numerous times now every day. It is just a warning, but we have not seen it before (obviously the session ID is not constant in these warnings).

Object Server 01: RPC error: Client provided an invalid session ID 76


Sorry to hear that AOS is crashing several times within last couple of weeks. Do you mean that you did not have this issue before that? If yes, what change did you make? Perhaps these changes are causing such issues.

Regarding the third one, RPC error was widely reported one couple of years ago. Please see whether this helps in resolving RPC error -

Regarding second one, as the message indicates it happens when two users do some work on the same record. To be more precise - when first user is editing record. Then second user comes along to make changes to the same record or tries to delete, that is when this error happens. Perhaps some training would resolve such issues.

Hope this helps,


We are having the same issue as Andrian

(2) Cannot edit a record in Vendor transactions (VendTrans).
An update conflict occurred due to another user process deleting the record or changing one or more fields in the record.

We know the user is not currently in the application. Can someone please explain where the record locking data is kept? Which table

Hi Kurt,

The record locking details are not stored in Ax. Please click here to learn about record locking.

How do you get this error? Are there any modifications / customisations done on this table?


Hello Harish, Thanks for the response although this does not appear to be a db level lock. The problem occured in our production db. We then took a backup of that db and restored it to out test server and still get the error on the same records. We also stopped & restarted the AOS with no success fixing it. Therefore I surmise that there is some problem within the db or the AX code. We do not have customizations in this area. The problem occures in the Bank>Checks>Check reversal while reversing the check.

one point of interest is that it seems to happen consistently when the field VendTrans.Settled1099amount was not zero. It is successful when this value is zero.

We are using AX 2009 which we recently upgraded to two weeks ago. This was not a problem prior.

Thanks, Kurt

Found work-around:

It seems that if a check is applied to an invoice that is marked for 1099, the check cannot be reversed through bank. However, if we went into vendor transactions and reversed the “settlement” (unapplied the documents), we were able to reverse the payment in bank.

Hi All,

I too face same problem in our production environment, but we done customization on this area where we are closing and opening ledger period for posting journal.

But this doesn’t happen in UAT, and I get error message “Cannot edit records in ledger periods, The values displayed in the form are not current, so an update or deletion cannot be made. To view the current values, on the Command menu, click Restore or press CTRL+F5."

This comes often and when we press ctrl f5 for long time then its the new value.

Any Idea to overcome this, Has anyone has experienced it.

Thanks In Advance