Try shutting down all Sage 500 ERP applications, including the business desktop, then retry.  I believe logical locks are cleared when internal data connections are changed.  If not, let me know.

Hi Ramon,

I'll give a try first thing tomorrow and give you an update. Thanks!

Update: It didn't work. It's still showing the same error message.

Well, there are a couple of options.  First, try to reboot the client machine where you are processing 1099s and try again.

If that does not work, and you have access to SSMS (or Query Analyzer depending upon your version of SQL), you could perform the following query:

SELECT * FROM tsmLockWrk WITH (NOLOCK) WHERE Entity LIKE 'PROCESS1099%'

If this query returns 1 or more rows, that is what is locking down the application as it thinks there is a client using the application.  Take note of any "HostName" fields that should be the name of any client machine names holding a lock.  If any names are not the name of your client machine name, then see if you can find any machine that is not yours and open and close the application on that (those) machines. 

Then take a look at the "Entity"" fields.  Any values after "PROCESS1099" should be the name of the company that the lock is for.  For example "Process1099SOA" would be a lock for the "SOA" company.  It sounds like the value would be "PROCESS1099AAI" for you.

Should you find in records in tsmLockWrk under these circumstances, if that single record having that "LockID" field were to "go away" then lock(s) should be cleared.     It is very important to make sure that all  table rows do not go away, only the ones where the "EntityID" starts with "PROCESS1099" and ends with the company ID being processed ("AAI" for you).  Keep in mind that making the lock go away via means that are not driven by the Sage 500 ERP applications is unsupported by Sage and could potentially allow for data issues if the lock is valid due to the application being run on another client machine or an orphaned process on the client machine being used.

This process very important to maintain integrity of various applications that may wish to control access to an application to prevent processing issues, data duplication, or data corruption.  Sometimes it may be possible for a lock to get left behind due to system crashes, etc.  The system does try to clear any orphaned locks when it can detect it.

I do not recommend manually removing locks, and am just providing this a information on the process that may have meaning to qualified database administrators.

AGAIN, MAKING LOCKS GO AWAY MANUALLY IS NOT SUPPORTED BY SAGE.  BEFORE DOING ANY MANUAL MANIPULATION OF THE DATA YOU SHOULD DO A DATABASE BACKUP AND BE PREPARED TO RESTORE THAT BACKUP AND ACCEPT ALL IMPLICATIONS OF WHAT THAT MEANS.