Thanx Mr. Bach! we excluded "*.dat"(our Btrieve-Files are named that way)
and
"*.^^^" from scanning and it seems, that error 46 has gone.
Regards from Jena
Mircea
Bill Bach schrieb:
> Status 46's of this nature are usually caused by running into an
> AntiVirus or Backup process. Tell your AV solution to avoid scanning
> the Btrieve files (either by directory or extension). Then, make sure
> that all users are out of the system before backup, and that the backup
> finished BEFORE the users come back in.
>
> If you are running Backup Agent and getting the message you indicated,
> this means that the file was NOT open at the beginning of the backup,
> but was opened later on. My guess is that the file happens to be
> CURRENTLY backed up when BA tries to put it into continuous mode. This
> is the primary reason that I keep asking Pervasive to add a white-list
> feature to the Backup Agent.
>
> If you would like to avoid this problem, our HoldOpen tool can help by
> implementing a white-list, when implemented along with the Backup
> Agent. Alternatively, you can build your own HoldOpen-like script by
> doing a BUTIL -STAT of all files immediately after activating the
> Backup Agent.
> Goldstar Software Inc.
> Pervasive-based Products, Training & Services
> Bill Bach
> BillBach@[EMAIL PROTECTED]
> http://www.goldstarsoftware.com
> *** Chicago: Pervasive Service & Sup****t Class - 08/28/2007 ***
>
>
> nmm wrote:
>
>> Hallo Btrivieans!
>>
>> we observed, that on a sertain installation of PSQL 8.1, while
>> running the backup-Agent, we get Btrieve-Error 46 on
>> add-record-commands.
>>
>> The situation is following:
>>
>> the application is a btrieve-app.
>> While BA is on, there runs a backup of all files except *.^^^. The
>> Backup is performed by Backupexec.
>> (The procedure runs every day statring BA at 23:50, Backup at 0:05 an
>> stopp BA at 1:55 h)
>>
>> Open file for (say) DVSALL.DAT returns status 0 - in the PBA-log
>> appear the statement: BA is now on for the file DVSALL.DAT.
>> An add record-command now returns error 46.
>>
>> Unfortunately the error appear not allways, only once a month or so.
>>
>> Any idea, what here happns?
>> Any hint will be welcome!
>>
>> Thanks in advance
>>
>> Mircea
>
|
