Baanboard.com

Go Back   Baanboard.com > Blogs > sasank's blog

User login

Frontpage Sponsor

Main

Poll
As a Customer What would do to keep your ERP Implementation intact
Proactively define Business Process-- Take the Project Ownership
100%
Handover everything to System Integrator from drawing BP till implementation of ERP
0%
Hire more inhouse skilled & capable IT Resource to work directly with SI
0%
Rely on SI Architects/Consultants
0%
Total votes: 1

Baanboard at LinkedIn


Reference Content

 
Fatal Error-201 Error
By sasank at 28 Feb 2013 - 09:41

Hi,

When i am updating the session, some fatal error is showing like:

: 201 (Record changed after delayed lock)
ExtraInfo : session: "tivel0515m000";object: "tivel0515m000"; function: "update.bom" commit.transaction; company number: 202
Message : FATAL ERROR: Error 201 (Record changed after delayed lock) on tivel010202 (No retry point specified)
Can not continue in tivel0515m000 (update.bom)[commit.transaction]
Stack trace:
    update.bom()  (in object otivel0515m000)
    update.enq.pric()  (in object otivel0515m000)
    frmcmd.executefunction()  (in object ottstpstandard)
    frmcmd.execute()  (in object ottstpstandard)
    frmcmd.handleexecution()  (in object ottstpstandard)
    frmcmd.start()  (in object ottstpstandard)

Can you please guide me with the help lines.

 Rgds,

Sasank N

AttachmentSize
Fatal Err.doc52 KB
0
No votes yet

by bdittmar on March 1, 2013 - 11:27am
bdittmar's picture
Quote:
Originally Posted by sasank View Post
A new blog entry has been added:

Fatal Error-201 Error
Hello,

seems to be an own developed session ?

db.retry point !

Regards


All times are GMT +2. The time now is 12:42.


©2001-2018 - Baanboard.com - Baanforums.com