web
You’re offline. This is a read only version of the page.
close
Skip to main content
Community site session details

Community site session details

Session Id :
Microsoft Dynamics SL (Archived)

SL 2011 - SQL Server Message 1205

(0) ShareShare
ReportReport
Posted on by

We are getting "Error message when you use Process Manager on the computer that is running Order Management in Microsoft Dynamics SL: SQL Server Message1205 - "Another user has locked a database record that this application needs in order to continue" "

What causes this issue and why would we get it in SL 2011 after an upgrade from SL 7 along with an upgraded SQL server.

Thanks,

Chuck

 

 

*This post is locked for comments

I have the same question (0)
  • Verified answer
    Community Member Profile Picture
    on at
    RE: SL 2011 - SQL Server Message 1205

    Looks like this error is a bug.

    Microsoft has had me change the global solomon.ini file command to equal as noted below:

    [Database Runtime]

    AsyncDelay=1

    I hope this helps someone else working with SL 2011 FP 1 SP2.

    Thanks,

    Chuck

  • Community Member Profile Picture
    on at
    RE: SL 2011 - SQL Server Message 1205

    Mark

    We just got another SQL Server Message 1205 error.

    It always occurs on transactions with serial numbers after releasing sales orders and clicking save.

    New error details are:

    Transaction was deadlocked on lock resources with another process and has been chosen as the deadlock victim.  Rerun the transaction.

    This has only started happening since we upgraded to SL 2011 FP 1 SP2.

    Any help would be appreciated.

    Thanks,

    Chuck

  • Community Member Profile Picture
    on at
    RE: SL 2011 - SQL Server Message 1205

    Mark

    I appreciate your help once again.

    The user was trying to put a serial number on a shipper when they got the errors.

    Programming Bulletproof Error 11500

    Exception: System.Exception

    Event Handler: OM401100.Form1.Update1_UpdateEvent

    Line<not available>

    Thanks,

    Chuck

  • Mark Asmus Profile Picture
    on at
    RE: SL 2011 - SQL Server Message 1205

    Chuck,

    It's hard to say.  Does the error give any additional details on what table was locked?   If not, maybe check the SL event log or the SQL event log to see if more details are logged in either of those places.

    In general, that error would indicate that some other process, say a batch release process, has a table locked for a period of time.  Then process manager tries to access the batch table but can't because the release process has it locked.  

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Mansi Soni – Community Spotlight

We are honored to recognize Mansi Soni as our August 2025 Community…

Congratulations to the July Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics SL (Archived)

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans