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!

 

[ettienne]

Set the workstation to use the server engine only.

 

[AABNV]

Hi Ettienne,

I did that. It doesn't work.

 

[Jay Converse]

Check again. LCK files mean you're using the Workgroup engine, and you should be using the client engine.

 

[ettienne]

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.

Your workstation is opening the database files with the local engine and locking other users out, set it so that it only uses the server engine.

 

[AABNV]

Is this setting below correct or not?

Thanks

 

[Jay Converse]

Is that on the server or the client?

 

[AABNV]

That is one the client.

 

[Jay Converse]

So is your setup a true client/server, or Workgroup?

You would have this problem if this new PC was workgroup, but everybody else was client/server.

If it's a WGE setup, there's a way to set the default workgroup engine, so that ~PVSW~.LOC is read-only, and has the name of the true server, not this new PC. I forget the steps exactly, I don't have a copy of P.2000 sitting around anymore.

 

[DjangMan]

I don't think there are too many steps. The easiest way to make one machine the permanent server (or gateway) is to kick everyone out. Then get the machine that should be the server to connect to the database. Then set the ~pvsw~.loc file to read-only.

There's also the gateway locator utility that will do the same.

 

[Jay Converse]

Yeah, gateway locator, that's the one!

Stupid alzheimers, couldn't remember it...

 

[AABNV]

then get the machine that should be the server to connect to the database. "

There is no ~PSVW~.Loc file when I log into ACCPAC on the server. :-(

Is there a site that I can download the gateway utility on?

 

[Jay Converse]

If there is no PVSW.LOC, then you're using a full server engine. Therefore, your new PC should have a client, not a workgroup engine installed. Uninstall the WGE, and find the client installer.

 

[DjangMan]

Use the Pervasive Control Center to open up a table in the database.

I have the gateway locator under the Tools menu in my Pervasive Control Center.

 

[ettienne]

Are you running the Pervasive Workgroup Engine or the Pervasive Server Engine?

 

[AABNV]

If there is no PVSW.LOC, then you're using a full server engine."

Hi tuba,

Yes, that's on the ACCPAC server. I also use ACCPAC there.

As for the clients, all of them have been installed in the same way. Via the \pvsw\Clients\Win shared folder on the that same server.

 

[AABNV]

I don't have the gateway locator, I've checked everywhere in the Pervasive Control Center.

Etienne,

I think it's the Pervasive Server engine I'm using.

 

[ettienne]

If you have the server engine then there is no gateway locator, the GW is only for workgroup engines.

 

[DjangMan]

It might be possible that you have another application that installed it's own pervasive workgroup engine and it is being used in place of the client.

Use the Pervasive Analyzer to track down any additional Pervasive engines.

 

[AABNV]

No, I have a freshly installed OS on the client. ACCPAC & pervasive were the first and only programs that I installed.

I'm starting to think that something may have gone wrong with the installation of that specific company database. Because all other company databases are working perfectly.