C
CaptainBly
About a year ago at a client I started getting Disk or Network Error
occasionally throughout the day. Did a lot of research and could
never really find anything firm for a solution. We tried EVERYTHING
imaginable and couldn't get this error to stop.
We think we may have finally found it. I am linking to the backend
database on the server via mapped drives. Evidently (and I am not a
network engineer) there is a setting in the registry on the servers
that will basically make a mapped drive connection go to sleep if it
isn't used in XX minutes. Well, that seems to be the problem. The
default setting on the server was 15 minutes (I believe). Well, the
main application that we were getting the errors on was left open all
day long and would regularly sit for 15 or more minutes as the users
did other things in other apps. When they would come back to process
a record that came in, they would get the error.
Here is what our network guy wrote up to resolve this issue:
For Windows 2000, 2003 server:
Open the registry editor on the server by clicking START -> Run and
typing “regedit” and pressing return (or clicking OK)
Navigate to “HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services
\lanmanserver\parameters”
Locate the “autodisconnect” key. Double click it to modify it.
Change the value from HEX to Decimal.
Change the value from the default (which should be 15) to something
larger. I chose 45. Number represents minutes (we actually have now
upped this to 480 because 45 wasn't enough either)
Exit the registry editor.
Effects are immediate. No reboot necessary.
If the MDB is hosted on a Windows XP or 2000 Professional PC mapped
drive, I believe this registry value is the same there as well.
I have seen a lot of other posts with similar sounding scenarios to
mine so hopefully this will help someone else out there.
occasionally throughout the day. Did a lot of research and could
never really find anything firm for a solution. We tried EVERYTHING
imaginable and couldn't get this error to stop.
We think we may have finally found it. I am linking to the backend
database on the server via mapped drives. Evidently (and I am not a
network engineer) there is a setting in the registry on the servers
that will basically make a mapped drive connection go to sleep if it
isn't used in XX minutes. Well, that seems to be the problem. The
default setting on the server was 15 minutes (I believe). Well, the
main application that we were getting the errors on was left open all
day long and would regularly sit for 15 or more minutes as the users
did other things in other apps. When they would come back to process
a record that came in, they would get the error.
Here is what our network guy wrote up to resolve this issue:
For Windows 2000, 2003 server:
Open the registry editor on the server by clicking START -> Run and
typing “regedit” and pressing return (or clicking OK)
Navigate to “HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services
\lanmanserver\parameters”
Locate the “autodisconnect” key. Double click it to modify it.
Change the value from HEX to Decimal.
Change the value from the default (which should be 15) to something
larger. I chose 45. Number represents minutes (we actually have now
upped this to 480 because 45 wasn't enough either)
Exit the registry editor.
Effects are immediate. No reboot necessary.
If the MDB is hosted on a Windows XP or 2000 Professional PC mapped
drive, I believe this registry value is the same there as well.
I have seen a lot of other posts with similar sounding scenarios to
mine so hopefully this will help someone else out there.