Btrieve error 85 with Arcserve 6.1 + Netware 4.11

[SteveWallis]

We run a Netware 4.11 OS with Arcserve 6.1 Build 96.
We have no problem with backing up data, but we have
an annoying Btrieve error message 85 when trying to
restore. The message appears as we begin to expand the
tree in the Arcserve workstation manager to select the files
to be restored. The message box translated from the French
says :
« Btrieve Warning : 85 on accessing file
INTRANETWARE/SYS:\ARCSERVE.6\DATABASE\ASOBJECT.DB
When atempting : Open file
File locked – Check that there are not two Btrieve files with the same
name but with a different extension, or that the specified file is not
locked. »

The Btrieve version is 6.15 1208 December 11 1995

There are not two Btrieve versions on the system.

The parameters in BSTART.NCF are :
LOAD BTRIEVE -p=4096 –f=30 –h=60 –l=20 –t=15 –u=0 –s=30 –m=512
LOAD BSPXCOM –d=8192 –s=15 –w=3

Can anyone give me a lead here,
Help much appreciated.
Steve Wallis

 

[Linda84]

It's probably one of two things.

Check your workstation for a client Btrieve engine that might be installed from some other application. The Arcserve workstation manager may incorrectly be trying to use this, which would cause a status 85 if the server engine was already accessing the files. Search your local drive(s) for wbtrv32.dll or w3btrv7.dll. Do not use Windows Explorer to search for DLLs, it doesn't always find them even if they're on the system. Instead, go to a command prompt and enter something like:
dir c:\wbtrv32.dll /s

The other possibility is that some other non-Btrieve process has the file open. If this is the case, the Btrieve engine will not be able to open it, since it wants exclusive access to the file. It could be a virus scanner, Arcserve, or something else causing the conflict. When you get the status 85, use the NetWare monitor (not the Pervasive monitor) to check the Active Files list and see if a process has the file in question open. Linda
Pervasive Software Support

 

[SteveWallis]

Problem Solved.
The restore problem was due to Inoculan.
When we started the server without Inoculan, the restore process worked fine. After updating signatures and reloading Inoculan we found the restore wouldn't work again. So we stopped Inoculan and restore worked fine.
Thanks very much Linda for your help.
Steve Wallis