file is busy error

A few of my long time clients have recently been experiencing 'file is busy'
errors.  Code has not been changed for years and the error rarely occurred
in the past. Other clients with the same application never experience this
error.  I am not able to re-create the error in the Superbase application
(SB36i/WinXP).  Any idea on what could be causing this?

Thanks
Dennis Brownlie
Del Mar Data Systems
dennis@windowareaccounting.net

oops...forgot to mention app is running on Windows 2003 Small Business
Server.

"dennis brownlie" <dennis@windowareaccounting.net> wrote in
message
news:fsgk4j$58o$1@ipx22096.ipxserver.de...
> A few of my long time clients have recently been experiencing 'file is
busy'
> errors.  Code has not been changed for years and the error rarely occurred
> in the past. Other clients with the same application never experience this
> error.  I am not able to re-create the error in the Superbase application
> (SB36i/WinXP).  Any idea on what could be causing this?
>
> Thanks
> Dennis Brownlie
> Del Mar Data Systems
> dennis@windowareaccounting.net
>
>

dennis brownlie wrote:
> oops...forgot to mention app is running on Windows 2003 Small Business
> Server.
> 
> "dennis brownlie" <dennis@windowareaccounting.net> wrote in
message
> news:fsgk4j$58o$1@ipx22096.ipxserver.de...
>> A few of my long time clients have recently been experiencing 'file is
> busy'
>> errors.  Code has not been changed for years and the error rarely
occurred
>> in the past. Other clients with the same application never experience
this
>> error.  I am not able to re-create the error in the Superbase
application
>> (SB36i/WinXP).  Any idea on what could be causing this?

So what has changed recently? It sounds like it could be either a write 
caching problem, or some other server-related issue. Or there is simply 
a huge amount of traffic at the same time. This error occurs when either 
the superbas.net needs to be exclusively locked for a brief time and it 
is already locked, or if the same is occurring on one of the lock files. 
Try deleting all the *.SB! and the SUPERBAS.NET and see if the problem 
goes away.

I've seen this error on Windows 2003 server. The latest was error 174 
(Can't lock dabase file). Clearing the lock files corrected this.  It 
appears (to me at least) that I need to clear the lock files at least 
once per month.

In a Linux Samba server environment, this does not seem to occur.

Neil Robinson wrote:
> dennis brownlie wrote:
>> oops...forgot to mention app is running on Windows 2003 Small Business
>> Server.
>>
>> "dennis brownlie" <dennis@windowareaccounting.net>
wrote in message
>> news:fsgk4j$58o$1@ipx22096.ipxserver.de...
>>> A few of my long time clients have recently been experiencing 'file
is
>> busy'
>>> errors.  Code has not been changed for years and the error rarely 
>>> occurred
>>> in the past. Other clients with the same application never
experience 
>>> this
>>> error.  I am not able to re-create the error in the Superbase 
>>> application
>>> (SB36i/WinXP).  Any idea on what could be causing this?
> 
> So what has changed recently? It sounds like it could be either a write 
> caching problem, or some other server-related issue. Or there is simply 
> a huge amount of traffic at the same time. This error occurs when either 
> the superbas.net needs to be exclusively locked for a brief time and it 
> is already locked, or if the same is occurring on one of the lock files. 
> Try deleting all the *.SB! and the SUPERBAS.NET and see if the problem 
> goes away.
> 

Just had a thought re "file is busy" - one time I had something
similar a  
(long) while back was MS Office FindFast was opening the file with a deny  
write lock while it looked through for indexing info - just wondering if  
Windows' file indexing is doing the same thing.  It took me ages to find  
that one, mainly because nobody told me that EDS had installed Office on  
the PC I was supporting...

If you can exclude SB!s and Superbas.net from the server's indexing, might