Dynamics F/SCM Customer Experience (CRM) Dynamics GP Dynamics Business Central (NAV) Dynamics SL Power Platform Fabric Copilot

[Phuong Nguyen]

we are running into an issue , all our user got into the error message below ” could not update: currently locked”  while using integration Manager. Please advice

——————————
phuong nguyen
ACC
——————————

[Blair Christensen]

That is usually a message from the database engine saying that two processes are competing over which one gets to modify records.  Its unusual to see because the only way it should be happening is if you have one process open as a transaction that is waiting for the transaction to close (and be made final) and another transaction comes along at the same time.

You need to find out what other process is trying to change something and allow it to complete.

——————————
Blair Christensen
Database Administrator
Oppenheimer Companies, Inc.
Boise ID
——————————
——————————————-

[Ryan Galang]

Hi Phuong,

Can you please check if your integration* is using a “Database” Storage Type?
* Right click on the Integration file (e.g. Bank Reconciliation) >>  (Bank Reconciliation) Properties  >> Logs tab >> [change to File, edit path] >> Apply

If yes, see if setting this to “File” (and assigning a corresponding path that both users have access to) stops the error from coming up?

——————————
Ryan Galang
BTP Technologies LLC
Chantilly VA
——————————
——————————————-

[valerie nguyen]

  we got below error message after running the integration manager ?. we could see the batch in GP after import. how could we fix this error message. i double check on logs – it is “database” as storage type. Please advice

——————————
valerie nguyen
System Integration Analyst
ACC
Irvine CA
——————————
——————————————-

[Blair Christensen]

In GP, have someone (with the appropriate privileges) open up the User Activity window (Dynamics GP -> Tools -> Utilities -> System -> User Activity) and see who else is in the company associated with your integration.  Have them log out of the company long enough to do the following test:

1. Delete the batch of entries created by the run displaying errors.
2. Run the integration again (after verifying no one is in the company in question)
3.  See if the error is resolved.

The contention is being caused by some other process trying to access the records in question.  This can be another user in GP or even a long-running report in some cases.  If this doesn’t result in success, check and see if there are any AFTER INTEGRATION scripts associated with the integration which might be causing data mutation (data edit by multiple simultaneous processes).  If still nothing there, it becomes a lot harder because you’ll have to get a DBA involved to do trace statements and find out what two processes are conflicting.

——————————
Blair Christensen
Database Administrator
Oppenheimer Companies, Inc.
Boise Idaho GPUG Chapter Leader
——————————
——————————————-