Hi Guys,

First time I've come across this error. It's at a remote site running a
network, and I'm a little bit suspicious that it has to do with Nortons.

Looking back at previous posts, I see that a lot has been said about this
topic, but I'm not sure if anyone has come to any resolutions (Besides
deleting Nortons, which I'd love for them to do, but have stuff all chance
of getting them to do it). I don't use Nortons myself, so I'm not really
clued up as to what can and can't be done with it.

In short, does anyone have any workarounds to this problem with DBISam, or
if anything has been added since V 4.022b3 to combat this issue. (I know
it's not a DBISam problem, but thought maybe there might have been something
we can do our end to "help" the problem go away).

Thanks & Regards

Adam.

"Adam H." <ahairsub4@rREMOVEMEspamSTOPPER.jvxp.com> wrote:

>First time I've come across this error. It's at a remote site running a
>network, and I'm a little bit suspicious that it has to do with Nortons.

>In short, does anyone have any workarounds to this problem with DBISam, or
>if anything has been added since V 4.022b3 to combat this issue.

If you mean Symantec NAV, I stopped using it. But it had options to disable directory
scanning or to disable "real time scanning." Its actually easy to disable scanning. To bad
it made the PC slowwwwww to shutdown.  To bad it is almost impossible to completely
remove. Even using the "removal tools", abandoned registry keys abound.

Dave M

Hi Dave,

Thanks for your reply. Unfortuantly in this instance, I don't have the
option to remove. This particular program is used by approximately 400
different companies, and the one that I had the issue with is a large
corporation, with their standards - that don't take lightly to someone
telling them to even disable their antivirus application to 'test'.

However, in the end, I blamed NAV wrongly. They found the fault. The data
location they were using had plenty of spare space, but they had a quota
limit turned on, which was causing this particular error. After nearly 3
hours on the phone, searching NG archives and them assuring me they had
plenty of disk space with no security issues or readonly problems,  Nortons
was the only other thing I could think of. (Them not willing to disable it
didn't make things any easier either in the diagnostics effort

Although, I must admit, I did cut a break - the IT guy I was communicating
with, while sticking to company policy, was thankfully pleasant to deal
with.  (All the same, I guess if he wasn't, I wouldn't have lasted 3 hrs on
the phone with him

Thanks for replying all the same, and thank goodness the days over. <sigh of
relief>    

Cheers

Adam.

Adam,

<< Looking back at previous posts, I see that a lot has been said about this
topic, but I'm not sure if anyone has come to any resolutions (Besides
deleting Nortons, which I'd love for them to do, but have stuff all chance
of getting them to do it). I don't use Nortons myself, so I'm not really
clued up as to what can and can't be done with it. >>

The resolution is described here:

http://www.elevatesoft.com/bulletin_14.htm

--
Tim Young
Elevate Software
www.elevatesoft.com