Disk or Network error

[Jim]

If we leave a database open for an extended period without activity when we
come back to it we have many disk or network error boxs to click ok on. Once
you go through all of them it appears that nothing is in the database.
However you can close it and come back in an all appears fine. What could be
causing these errors. Note database is on win server 2003 shared drive.

 

[TC]

A bit more information would help.

What is the exact text of the messages?

Do they come from Access, or from something else? (what is in their
title bars?)

Is your database running any code (eg. on a timer, or in a loop, or a
long-running SQL statement) when they appear?

TC (MVP Access)
http://tc2.atspace.com

 

[Jim]

--
JIM

A bit more information would help.

What is the exact text of the messages?

Do they come from Access, or from something else? (what is in their
title bars?)

Is your database running any code (eg. on a timer, or in a loop, or a
long-running SQL statement) when they appear?

TC (MVP Access)
http://tc2.atspace.com

Thank you for your reply. The error comes from access. Opening the help reveals error 3043. There is no code (timer or loop) that I am aware of. The error (3043) indicateds that the network may have disconnected however checking my computer indicates all network drives are connected. I have checked techknowladge for that error code and did not come up with anything.

Thank you.

 

[Immanuel Sibero]

Jim,

What version of Access? What Service Pack?
Can you reproduce the errors if you were to run the whole app locally on
your c: drive?

Immanuel Sibero



reveals error 3043. There is no code (timer or loop) that I am aware of. The
error (3043) indicateds that the network may have disconnected however
checking my computer indicates all network drives are connected. I have
checked techknowladge for that error code and did not come up with anything.

 

[Jim]

-- To lay this all out the version of access is 2003, running from a desktop
the data base is stored on a win 2003 server that is also our SQL server . In
answering can it be recreated the answer is yes all you need to do is leave a
database open for a while and you will get many disk or network error box's
that you must close. This happens on the CEO machine all the time as he is in
access almost everyday. I have even had it happen to me as well. The network
cards are set not to disconect to save power nor does it appear to be
dropping the network. If i can get a screen shot i will post that next time.
Thank you in advance.
JIM

 

[Carl Colijn]

In

-- To lay this all out the version of access is 2003, running from a
desktop the data base is stored on a win 2003 server that is also our
SQL server . In answering can it be recreated the answer is yes all
you need to do is leave a database open for a while and you will get
many disk or network error box's that you must close. This happens on
the CEO machine all the time as he is in access almost everyday. I
have even had it happen to me as well. The network cards are set not
to disconect to save power nor does it appear to be dropping the
network. If i can get a screen shot i will post that next time.

Hi Jim,

Don't know if you still read this thread, but I'm resolving the same error
on one of my client's setups. The situation is not exactly the same; they
install a fresh copy of the database and cannot get in because they get the
3043 error - "disk or network error".

I've researched a bit on Google, and I have compiled a list of the possible
causes. Not all of these seem applicable to your situation, but some might
be. I'm also not 100% sure if this list is correct or not; I'm just now
researching all possible causes myself, and just note everything that comes
up in Google. The list I compiled so far is:
- The backend database might be opened exclusively by some administrator;
this may lock out other users and raise this error
- Users need Read, Write, Create but also Delete rights on the network share
or drive
- Make sure the users have these rights on both the share itself as in the
NTFS filesystem
- On NT 4: the temp folder that is specified in the environment variable TMP
doesn't exist
- Maybe a faulty or misconfigured NIC and or cabling; access keeps the DB
connection open for a long time, so a NIC, network cable or hub that gives
infrequent connection losses will raise faults easier in Access than in
other applications
- Sometimes NIC drivers will also have a hand in this issue (both client and
server)
- Novel networks are (by default) configured with a low maximum number of
locks; Access uses many locks in some situations
- Using the IPX/SPX protocol also gives rise to this error more often than
TCP/IP and/or NetBEUI

If this still doesn't resolve the issue, it might be an option to enable
your server logs. Access raises the 3043 error whenever there is a fault
with accessing the network, but the exact cause is not reported; you might
find out more about it in your server logs.

Hope this helps,
Carl Colijn

--
TwoLogs - IT Services and Product Development
A natural choice!
http://www.twologs.com
TimeTraces: the powerfull and versatile time registration system!
http://www.twologs.com/en/products/timetraces.asp