One or more records are locked by another task. 2

[AABNV]

Hi,


I hope someone can help me with the following question.
We have ACCPAC 4.2a with Pervasive SQL installed on our server with the databases of several companies. We also have 6 ACCPAC clients installed. A year ago we created a new company database (let's call it Company D) and since then it's been working properly with the existing clients.

I've recently installed ACCPAC on a new workstation, and it's working as expected with all companies with exception of Company D.

If I open that company on that workstation, while others have already logged into that company I get the following error: "One or more records are locked by another task. Wait and choose Retry. If you choose Cancel, you may lose your changes". If I click on Retry, I get the error again. If I click on Cancel I get the following: "Cannot access database (error=118). See Help for more information."

It only happens with this Company (D). The others work properly when I log into them (on the new workstation) while others are already in.

Furthermore I've noticed that when I'm the first one to log in on the new workstation, others get the same error on that Company database only. Additionaly when I look in the DATA folder of that company, the ~PVSW~.LOC file appears, and I'm unable to delete it.

I've followed the steps on the site below, but it still doesn't work.

http://kb.accpac.com/cgi-bin/sageso...td_adp.php?p_faqid=23832&p_created=1184975414

And I haven't encountered any files with a *.lck file extension.

Are there any suggestions for me to do to solve this problem?

Thanks!

 

[Jay Converse]

On the server, go to Accpac database setup, and check the paths for every company, you may have mixed up UNC and drive letters. Deleting and re-adding that company to database setup (on the server) may help.

 

[AABNV]

Thanks tuba, I will do that as soon as possible.

 

[AABNV]

Thank you Tuba!! That was it!

In Edit in the Database setup, the folders of all other companies where listed as \\server\d\ while the faulting company was on D:\. I've fixed that and it works!

Thank you!

 

[Jay Converse]

Good, I guess my alzheimer's isn't as bad as I thought...