ArticlesArticles Most Helpful ArticlesMost Helpful Articles Language SettingsLanguage Settings LoginLogin
RSS Feeds
DrillDown Icon Table of Contents Back
 . . . . . . . . . . . . .
DrillDown Icon MX
DrillDown Icon MANUALS and Other Info for SQL MANEX Client Server
DrillDown Icon Customer Relationship Management (CRM)
DrillDown Icon ManEx Minute
DrillDown Icon ManEx Component Exchange
DrillDown Icon ManEx Supplier Directory & Rankings
  Email This ArticlePrint PreviewPrint Current Article and All Sub-Articles
 
SQL-SYSTEM LOCK ERROR - What to do if System PO Lock appears?
Q.  What to do if system locks up while in Purchase Order records, and one of the following messages appear:
 
 
 

A.  There is a PO_lock.sql attached below and/or there is a stored procedure sp_unlockPoFlag as part of the database.   Go into the SQL Server Management and run the attached script, this will remove the PO Lock placed on your tables.   

Reason:  The lock will occur either by the user saving a record lost connection to the network (or computer crashed) or there are two users attempting to save the exact same Purchase Order record at the same time.  This lock is to prevent  duplications.  Normally the lock is only on for a small amount of time to allow the first user to finish saving the record and then the next user usually then can proceed.  If User #2 becomes impatient and does not wait for the temp lock to clear and Clt+Alt+Delete out of the system, this too would place the permanent lock on the records and would then require you to run the PO_lock.sql file. 

Prevention:  If users see a message that the file is currently in use have them wait a few minutes and try again, not to Clt+Alt+Delete out of the system.

Attachments
Article ID: 5276