Accpac 4.2 locked record error

[balin]

Accpac 4.2
Win 2K server

Workstations or remote machines Run Accpac via terminal services. (max 5 at once)

We have had on occasions locked record errors when posting OE Orders, AR batches. IE we get 'record is locked because another task is trying access....' etc. etc. This persists even though all other users are off the system.

Re-starting Accpac doesn't resolve the error. Neither does closing terminal services sessions etc.

Issues - what might cause this error?

And ...Our solution has been to re-start the server but this is very inconvenient. Is there another way to 'unlock' the records.

JON

 

[Jay Converse]

Accpac service packs?
Database and service packs?

 

[ettienne]

Sounds like Pervasive settings are off, if you are running Pervasive/Btrieve. Next time this happens check the Pervasive Monitor.

 

[balin]

Accpac 4.2A service pack 2 on OE,AR,AP,IC,PO

Pervasive database but that's where you lose me.

I have found the Prevasive monitor but I'm not sure what I'm looking for.

Also the Pervasive event log for yesterday.
11-13-2007 09:05:58 NTMKDE 00000980 NTDBSMGR.EXE SERVER I Resources released
11-13-2007 09:11:14 W3COMSRV 00000994 NTDBSMGR.EXE SERVER E WinSock socket() error=10047.
11-13-2007 09:11:14 NTMKDE 00000994 NTDBSMGR.EXE SERVER I Error initializing the SPX protocol. Error code: 11.
11-13-2007 09:23:26 NTMKDE 00000994 NTDBSMGR.EXE SERVER I Resources allocated
11-13-2007 09:26:16 NTMKDE 00000994 NTDBSMGR.EXE SERVER I Resources released
11-13-2007 09:34:25 NTMKDE 00000994 NTDBSMGR.EXE SERVER I Resources allocated

Hope this means something to someone, it's not a huge problem and Accpac is otherwise trouble free. thanks in adavance.

JON

 

[Jay Converse]

When you run the Monitor, look at Microkernel/Resource Usage.

 

[ettienne]

The next time you get a locked record try restarting Pervasive instead of restarting the server. If that releases the lock then it indicates a problem at the Pervasive end.

 

[balin]

Thanks guys I can't wait for the Next Locked record !!

Keep up the great work on this forum.
JON

 

[ettienne]

Something just struck me, on Terminal Server the workgroup engine can load and cause all kinds of nasties, like locked records.
Delete (or rename) C:\PVSW\BIN\w3dbsmgr.exe on the terminal server, this is not required and is known to cause problems.

 

[balin]

I'll try it
Thanks
JON

 

[balin]

Can't find C:\PVSW\BIN\w3dbsmgr.exe anywhere on the server.

Don't lose any sleep over it.

JON

 

[balin]

In case anyone is interested.
1. the pervasive monitor does show records locks.
2. restarting the prevasive services via the pervasive contol center seems to do the trick.

If it is a matter of changing pervasive settings as ettiene suggests. What settings might they be???

But we still can't say what is causing this.
JON

 

[ettienne]

That's where Pervasive Monitor comes in handy, keep an eye on Resource Usage and look for anything where the current values reach the maximum.
Also check your available RAM on the server when thing lock up (in Windows Task Manager), older versions of Pervasive had memory management issues when the server runs low on RAM.