"Your network access was interrupted."
in [General]
|
Prev: Not receiving post
Next: Limited Combo Box Option
From: John Glassco on 5 Apr 2010 14:54 We've been running an Access FE/BE with the backend in a shared location on the server for quite some time. Most of the PCs running the program are working fine. There are three PCs, however, that get a message: "Your network access was interrupted. To continue close the database and then open it again." The only difference between these three PCs and the rest that are operating normally is the OS. Two are running Windows 7 64, and one is running Windows Vista 64. All the other PCs are using XP 32 or 64. This seems to rule out any network issues. This problem also usually only crops up after hours. One workstation (Windows 7) is being used all the time, so they will experience problems anywhere from 7 PM to 4 AM. The other two computers (Windows 7 and Windows Vista) are admin computers that only receive the error if there are queries open overnight. However it doesn't happen at a consistent time or day of the week. Once the message comes up, all the connections in the current database have to be closed before things will begin operating normally. Has anyone else encountered this problem? And if so, is there a way to fix this?
From: John Spencer on 5 Apr 2010 15:03 I would guess that something is happening on the server that interrupts the connection- especially in view of the fact this problem seems to crop up during the off hours. Is it possible that there are automatic backups set (or other processes) that "Turn off" the network for a brief period of time? John Spencer Access MVP 2002-2005, 2007-2010 The Hilltop Institute University of Maryland Baltimore County John Glassco wrote: > We've been running an Access FE/BE with the backend in a shared location on > the server for quite some time. Most of the PCs running the program are > working fine. > > There are three PCs, however, that get a message: "Your network access was > interrupted. To continue close the database and then open it again." > > The only difference between these three PCs and the rest that are operating > normally is the OS. Two are running Windows 7 64, and one is running Windows > Vista 64. All the other PCs are using XP 32 or 64. This seems to rule out > any network issues. > > This problem also usually only crops up after hours. One workstation > (Windows 7) is being used all the time, so they will experience problems > anywhere from 7 PM to 4 AM. The other two computers (Windows 7 and Windows > Vista) are admin computers that only receive the error if there are queries > open overnight. However it doesn't happen at a consistent time or day of the > week. > > Once the message comes up, all the connections in the current database have > to be closed before things will begin operating normally. > > Has anyone else encountered this problem? And if so, is there a way to fix > this?
From: John Glassco on 5 Apr 2010 16:20 I don't think that's it. As I mentioned, the interruptions aren't consistent. They also don't match up to the times of any of our automated processes. In addition, there are three XP PCs that are being used at the same time as the Win7 workstation that have no problems at all. The three XP PCs and the Win7 PC all use the same functionality on the same screen in the Access program, but the Win7 PC is the only one that ever has issues. "John Spencer" wrote: > I would guess that something is happening on the server that interrupts the > connection- especially in view of the fact this problem seems to crop up > during the off hours. > > Is it possible that there are automatic backups set (or other processes) that > "Turn off" the network for a brief period of time? > > John Spencer > Access MVP 2002-2005, 2007-2010 > The Hilltop Institute > University of Maryland Baltimore County > > John Glassco wrote: > > We've been running an Access FE/BE with the backend in a shared location on > > the server for quite some time. Most of the PCs running the program are > > working fine. > > > > There are three PCs, however, that get a message: "Your network access was > > interrupted. To continue close the database and then open it again." > > > > The only difference between these three PCs and the rest that are operating > > normally is the OS. Two are running Windows 7 64, and one is running Windows > > Vista 64. All the other PCs are using XP 32 or 64. This seems to rule out > > any network issues. > > > > This problem also usually only crops up after hours. One workstation > > (Windows 7) is being used all the time, so they will experience problems > > anywhere from 7 PM to 4 AM. The other two computers (Windows 7 and Windows > > Vista) are admin computers that only receive the error if there are queries > > open overnight. However it doesn't happen at a consistent time or day of the > > week. > > > > Once the message comes up, all the connections in the current database have > > to be closed before things will begin operating normally. > > > > Has anyone else encountered this problem? And if so, is there a way to fix > > this? > . >
From: Mrs. Lori Andersen on 5 Apr 2010 17:39 "John Spencer" <spencer(a)chpdm.edu> wrote in message news:Ob6eiKP1KHA.5536(a)TK2MSFTNGP04.phx.gbl... >I would guess that something is happening on the server that interrupts the >connection- especially in view of the fact this problem seems to crop up >during the off hours. > > Is it possible that there are automatic backups set (or other processes) > that "Turn off" the network for a brief period of time? > > John Spencer > Access MVP 2002-2005, 2007-2010 > The Hilltop Institute > University of Maryland Baltimore County > > John Glassco wrote: >> We've been running an Access FE/BE with the backend in a shared location >> on the server for quite some time. Most of the PCs running the program >> are working fine. >> >> There are three PCs, however, that get a message: "Your network access >> was interrupted. To continue close the database and then open it again." >> >> The only difference between these three PCs and the rest that are >> operating normally is the OS. Two are running Windows 7 64, and one is >> running Windows Vista 64. All the other PCs are using XP 32 or 64. This >> seems to rule out any network issues. >> >> This problem also usually only crops up after hours. One workstation >> (Windows 7) is being used all the time, so they will experience problems >> anywhere from 7 PM to 4 AM. The other two computers (Windows 7 and >> Windows Vista) are admin computers that only receive the error if there >> are queries open overnight. However it doesn't happen at a consistent >> time or day of the week. >> >> Once the message comes up, all the connections in the current database >> have to be closed before things will begin operating normally. >> >> Has anyone else encountered this problem? And if so, is there a way to >> fix this?
From: Paul Shapiro on 5 Apr 2010 18:17
I don't know for sure, but it could be that the default behavior for keeping a workstation-server session open changed between Windows XP and Win 7. I seem to remember something about network sessions timing out after 15 minutes of being idle. Other than searching the web for info, which I didn't find easily, all I can think of is to capture network packets and see what closes the network session. You could also check that all service packs and Microsoft Updates are applied to the server, workstations and Office. Check for the latest network interface drivers. What OS is the server running? If it's Server 2003, you might want to disable the advanced networking features. You can find more info about that by searching "netsh int tcp set global", which is the command to disable some of those features. These are network optimizations that can interfere with performance and/or connectivity if both sides of the connection, and any networking gear in between, does not have fairly current drivers. "John Glassco" <JohnGlassco(a)discussions.microsoft.com> wrote in message news:4A1BBB6D-FAE6-4693-9D2C-930E7B5B8CCA(a)microsoft.com... > I don't think that's it. As I mentioned, the interruptions aren't > consistent. They also don't match up to the times of any of our automated > processes. > > In addition, there are three XP PCs that are being used at the same time > as > the Win7 workstation that have no problems at all. The three XP PCs and > the > Win7 PC all use the same functionality on the same screen in the Access > program, but the Win7 PC is the only one that ever has issues. > > "John Spencer" wrote: > >> I would guess that something is happening on the server that interrupts >> the >> connection- especially in view of the fact this problem seems to crop up >> during the off hours. >> >> Is it possible that there are automatic backups set (or other processes) >> that >> "Turn off" the network for a brief period of time? >> >> John Spencer >> Access MVP 2002-2005, 2007-2010 >> The Hilltop Institute >> University of Maryland Baltimore County >> >> John Glassco wrote: >> > We've been running an Access FE/BE with the backend in a shared >> > location on >> > the server for quite some time. Most of the PCs running the program >> > are >> > working fine. >> > >> > There are three PCs, however, that get a message: "Your network access >> > was >> > interrupted. To continue close the database and then open it again." >> > >> > The only difference between these three PCs and the rest that are >> > operating >> > normally is the OS. Two are running Windows 7 64, and one is running >> > Windows >> > Vista 64. All the other PCs are using XP 32 or 64. This seems to rule >> > out >> > any network issues. >> > >> > This problem also usually only crops up after hours. One workstation >> > (Windows 7) is being used all the time, so they will experience >> > problems >> > anywhere from 7 PM to 4 AM. The other two computers (Windows 7 and >> > Windows >> > Vista) are admin computers that only receive the error if there are >> > queries >> > open overnight. However it doesn't happen at a consistent time or day >> > of the >> > week. >> > >> > Once the message comes up, all the connections in the current database >> > have >> > to be closed before things will begin operating normally. >> > >> > Has anyone else encountered this problem? And if so, is there a way to >> > fix >> > this? |