磁盘或网络错误 [英] Disk Or Network Error
问题描述
我为一个大型组织工作，我的团队已经在Access 2000中开发了2个非常实际的数据库。这些数据库在过去的6年里一直很好用。
最小的问题或问题。大约1个星期前的今天
我们已经开始遇到错误Microsoft Visual Basic运行时间
错误3043磁盘或网络错误几乎每天都在同一时间每天
（此时数据库中的活动开始增加）。
有时，错误发生在最小的问题上，其他的则结束在其中一个可以修复的数据库中损坏了（感谢上帝）。
后这一集似乎都运行正常。
这两个数据库都有一个驻留在服务器上的前端，所有用户都支持
访问（我知道这不是一个好习惯）和后端也在服务器上驻留
。服务器是Windows NT，所有客户端都运行Windows
2000.我们通常在数据库中约有20个左右的并发用户
这在过去没有任何问题。该公司最近升级了许多客户端机器。当我们联系我们的服务器网络工作人员来讨论这个问题时，他们检查所有服务器事件日志并找不到
报告错误。他们甚至检查了一些用户的NIC卡
设置，结果发现它们设置为100满，而不是自动
，这已被证明会导致问题。
我们每周在所有数据库上运行一个压缩和修复，并保持数据库没有未使用的表单和其他数据库对象。这个问题看起来好像将会b / b
永远不会消失。有没有人有任何关于这可能是什么的想法
以及我们可以做些什么来解决这个问题？任何帮助都会很多
赞赏。
温馨的问候，
Mark
I work for a large organization were my team has developed 2 very
substantial databases in Access 2000. These databases have been working fine
for the last 6 years with minimal issues or problems. About 1 week ago today
we have started experiencing the error "Microsoft Visual Basic Run Time
Error 3043 Disk or Network Error" just about every day around the same time
each day (activity starts to increase at this time in the databases).
Sometimes the error happens with minimal problems and others that end in a
corruption of one of the databases that can be repaired (thank god). After
this episode all seems to work fine.
Both databases have a front end that resides on the server that all users
access (I know this is not a good practice) and a back end that also resides
on the server. The server is Windows NT with all the clients running Windows
2000. We usually range about 20 or so concurrent users in the databases
which has not been any issue in the past. The company has recently upgraded
many of the client machines. When we contact our server network staff to
look into this issue they check all the server event logs and find no
reports of errors. They have even checked some of the users NIC card
settings only to discover that they are set at 100 full and not at automatic
which has been documented to cause problems.
We run a compact and repair on all databases weekly and keep the databases
clear of unused forms and other DB objects. This problem seems like it will
never go away. Does anyone have any ideas as to what this can possible be
and what we can do to resolve the problem? Any help would be much
appreciated.
Warm Regards,
Mark
推荐答案
2007年1月4日星期四23:19:41 -0500，NEWSGROUPS
< ma *********** @ comcast.netwrote：
我的猜测是网卡或网线不好。即使是暂时中断
的服务也会导致Access后端崩溃。
使用二进制试错法找出哪一个。
在更新过程中，通过杀死访问会话，试图破坏后端的流氓用户不是吗？我之前发布了关于这个问题的解决方案的
。
-Tom。
On Thu, 4 Jan 2007 23:19:41 -0500, "NEWSGROUPS"
<ma***********@comcast.netwrote:
My guess is a bad NIC or network cable. Even a momentary interruption
of service can crash an Access back-end.
Use a binary trial-and-error to find out which one.
It isn''t a rogue user who is trying to destroy the back-end by killing
the Access session in the middle of an update, right? I have
previously posted about solutions to this problem.
-Tom.
>我在一个大型组织工作，我的团队在Access 2000中开发了两个非常实质的数据库。这些数据库在过去的6年里一直很好用，只需要很少的问题。大约1个星期前的今天
我们已经开始遇到错误Microsoft Visual Basic运行时间
错误3043磁盘或网络错误几乎每天都在同一时间每天（此时数据库中的活动开始增加）。
有时候错误发生在最小的问题上，而另一些则以腐败结束其中一个可以修复的数据库（感谢上帝）。这一集之后似乎一切正常。
两个数据库都有一个驻留在服务器上的前端，所有用户都可以访问（我知道这不是一个好习惯）还有一个后端也位于服务器上。服务器是Windows NT，所有客户端都运行Windows
2000。我们通常在数据库中约有20个左右的并发用户，这在过去没有任何问题。该公司最近升级了许多客户端机器。当我们联系我们的服务器网络工作人员以查看此问题时，他们会检查所有服务器事件日志，并找不到错误报告。他们甚至检查了一些用户的NIC卡设置，结果发现它们设置为100满而不是自动
，这已被证明会导致问题。
我们每周运行一个紧凑的并修复所有数据库，并保持数据库清除未使用的表单和其他数据库对象。这个问题似乎永远不会消失。有没有人对这可能是什么以及我们可以做些什么来解决问题有任何想法？任何帮助都会非常感激。
热烈的问候，
Mark
>I work for a large organization were my team has developed 2 very
substantial databases in Access 2000. These databases have been working fine
for the last 6 years with minimal issues or problems. About 1 week ago today
we have started experiencing the error "Microsoft Visual Basic Run Time
Error 3043 Disk or Network Error" just about every day around the same time
each day (activity starts to increase at this time in the databases).
Sometimes the error happens with minimal problems and others that end in a
corruption of one of the databases that can be repaired (thank god). After
this episode all seems to work fine.
Both databases have a front end that resides on the server that all users
access (I know this is not a good practice) and a back end that also resides
on the server. The server is Windows NT with all the clients running Windows
2000. We usually range about 20 or so concurrent users in the databases
which has not been any issue in the past. The company has recently upgraded
many of the client machines. When we contact our server network staff to
look into this issue they check all the server event logs and find no
reports of errors. They have even checked some of the users NIC card
settings only to discover that they are set at 100 full and not at automatic
which has been documented to cause problems.
We run a compact and repair on all databases weekly and keep the databases
clear of unused forms and other DB objects. This problem seems like it will
never go away. Does anyone have any ideas as to what this can possible be
and what we can do to resolve the problem? Any help would be much
appreciated.
Warm Regards,
Mark
Tom
什么是使用二进制试错法找出哪一个。我到目前为止，
完全依赖我们的网络人员。
我不能相信它是一个胭脂用户。事实上，我已经看了几个用户在系统中处理他们的工作，然后在例程完成之前收到错误
消息。
谢谢，
马克
Tom van Stiphout < no ************* @ cox.netwrote in message
news：pd ***************** *************** @ 4ax.com ...
Tom
What is meant by "Use a binary trial-and-error to find out which one". I
have relied totally on our Network people thus far.
I can''t believe that it is a rouge user. In fact I have watched a couple
users processing their work in the system and then receiving the error
message before the routine completes.
Thank you,
Mark
"Tom van Stiphout" <no*************@cox.netwrote in message
news:pd********************************@4ax.com...
On Thu，2007年1月4日23:19:41 - 0500，NEWSGROUPS
< ma *********** @ comcast.netwrote：
我的猜测很糟糕网卡或网络电缆。即使是暂时中断
的服务也会导致Access后端崩溃。
使用二进制试错法找出哪一个。
在更新过程中，通过杀死访问会话，试图破坏后端的流氓用户不是吗？我之前发布了关于这个问题的解决方案的
。
-Tom。
On Thu, 4 Jan 2007 23:19:41 -0500, "NEWSGROUPS"
<ma***********@comcast.netwrote:
My guess is a bad NIC or network cable. Even a momentary interruption
of service can crash an Access back-end.
Use a binary trial-and-error to find out which one.
It isn''t a rogue user who is trying to destroy the back-end by killing
the Access session in the middle of an update, right? I have
previously posted about solutions to this problem.
-Tom.
>>我为一个大型组织工作是我的团队在Access 2000中开发了两个非常实质的数据库。这些数据库在过去的6年中一直很好用
最小的问题或问题。大约1个星期前今天
我们已经开始遇到错误Microsoft Visual Basic运行时
错误3043磁盘或网络错误几乎每天大约每天都在相同的时间
每天（此时数据库中的活动开始增加）。
有时错误发生在最小的问题上，而其他问题则以最终的问题结束。 />其中一个可以修复的数据库损坏（感谢上帝）。这一集之后似乎一切正常。
两个数据库都有一个驻留在服务器上的前端，所有用户都可以访问（我知道这不是一个好习惯）还有一个后端也在服务器上驻留
。服务器是Windows NT，所有客户端都在运行
Windows
2000。我们通常在数据库中约有20个左右的并发用户，这在过去没有任何问题。该公司最近升级了许多客户端机器。当我们联系我们的服务器网络工作人员以查看此问题时，他们会检查所有服务器事件日志，并找不到错误报告。他们甚至检查了一些用户的NIC卡
设置，发现它们设置为100满，而不是自动
，这已被证明会导致问题。
<我们每周在所有数据库上运行一个压缩和修复，并保持数据库清除未使用的表单和其他数据库对象。这个问题似乎将永远不会消失。有没有人对这可能是什么以及我们可以做些什么来解决问题有任何想法？任何帮助都会非常感激。
热烈的问候，
Mark
>>I work for a large organization were my team has developed 2 very
substantial databases in Access 2000. These databases have been working
fine
for the last 6 years with minimal issues or problems. About 1 week ago
today
we have started experiencing the error "Microsoft Visual Basic Run Time
Error 3043 Disk or Network Error" just about every day around the same
time
each day (activity starts to increase at this time in the databases).
Sometimes the error happens with minimal problems and others that end in a
corruption of one of the databases that can be repaired (thank god). After
this episode all seems to work fine.
Both databases have a front end that resides on the server that all users
access (I know this is not a good practice) and a back end that also
resides
on the server. The server is Windows NT with all the clients running
Windows
2000. We usually range about 20 or so concurrent users in the databases
which has not been any issue in the past. The company has recently
upgraded
many of the client machines. When we contact our server network staff to
look into this issue they check all the server event logs and find no
reports of errors. They have even checked some of the users NIC card
settings only to discover that they are set at 100 full and not at
automatic
which has been documented to cause problems.
We run a compact and repair on all databases weekly and keep the databases
clear of unused forms and other DB objects. This problem seems like it
will
never go away. Does anyone have any ideas as to what this can possible be
and what we can do to resolve the problem? Any help would be much
appreciated.
Warm Regards,
Mark
NEWSGROUPS写道：
NEWSGROUPS wrote:
我不能相信它是一个胭脂用户。
I can''t believe that it is a rouge user.
相反。脸红的人通常是罪魁祸首:-)。
James A. Fortune
CD ******** @ FortuneJames.com
古埃及语中的驴语发音类似于
ee-aww。
On the contrary. The one who blushes is usually the culprit :-).
James A. Fortune
CD********@FortuneJames.com
The ancient Egyptian word for donkey is pronounced something like
ee-aww.
这篇关于磁盘或网络错误的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
