MS Access database support - FE/BE Disk error on Access 2003

Author

FE/BE Disk error on Access 2003

ph@icw.ie

2006-04-06, 11:34 am

Similar to many other postings, but just wanted to make sure I'm not
doing something stupid before tackling this.

New Access 2003 database on 20+ WinXP workstations with backend on
Win2003 Server. Every week or two, some of the workstations will lose
their link to the back end and come up with disk error. A logoff/reboot
seems to be the only way to clear this problem. Only other app on the
workstations is NAI Viruscan V8, which updates daily from an ePO
server. Network traffic is generally light with a small number of PLC's
using the same LAN. Whenever I've checked a workstation with a disk
error, the LAN has been freely available and it just seems to be the
Access link which has failed. When I reboot Access always comes up okay
and the database always works fine again.

Questions.

Is Access2003 very sensitive to disruption between FE and BE.
Can Access recover from disruption, or does it always have to be a
reboot/logoff.
Could this be a problem with the Access database, or am I definitely
looking at a network problem.

I'd be grateful if anyone can give me a few pointers before I lose my
sanity

Pat

Bob

2006-04-06, 8:29 pm

We are dealing with exactly the same problem. A restore of the LAN
connection (right mouse click in LAN connection in system tray) will
also help, but it leaves a small window at the desktop (I think a
Microsoft bug), which will only disappear after logoff/logon. But this
restore prevents you to logoff.

At this moment it seems to be a domain problem or something to deal
with certificates. I have our technical department, cause is for 99,99
% a network error. But indeed, MS Access 2003 only looses its
connection without reconnecting.

Our situation: 4 xp clients and 2 NT 2000 on a W2k3 server. The NT 2000
clients donnot have these problems.

Sponsored Links