Guest DougBlakely Posted August 5, 2007 Posted August 5, 2007 I need to get some fresh ideas. We're using a POS system called TRS written in visual BASIC. Network is peer-to-peer, XP pro on all systems. Problem starts at the machine serving the data files for TRS. Windows just shuts down by itself. After serveral restarts, hoping that it was some fluke, the shutdown "spreads" to the client machines! I need an idea for some method(s) for troubleshooting. So far, we have tried: Format/re-install Virus & malware scans using various products Running a nework monitor on a couple of machines until one shuts down. None of the above yields anything helpful. Thanks all! -- Doug Blakely Blakely Communications Claremore, OK doug@blakelycomm.com
Guest Malke Posted August 5, 2007 Posted August 5, 2007 Re: Computers on network shutting down DougBlakely wrote: > I need to get some fresh ideas. > We're using a POS system called TRS written in visual BASIC. > Network is peer-to-peer, XP pro on all systems. > Problem starts at the machine serving the data files for TRS. Windows just > shuts down by itself. After serveral restarts, hoping that it was some fluke, > the shutdown "spreads" to the client machines! > I need an idea for some method(s) for troubleshooting. > > So far, we have tried: > Format/re-install > Virus & malware scans using various products > Running a nework monitor on a couple of machines until one shuts down. > > None of the above yields anything helpful. Offhand, it sounds like possibly the database is corrupted, although why that would shut the machines down I don't know. Normally if there is a failure machines will restart instead of just shut down. Is there anything in the Event Viewer logs? Start>Run>eventvwr.msc [enter] If this is a new phenomenon, what changed between the time things worked and the time they didn't? You should contact tech support for TRS for this. Malke -- Elephant Boy Computers http://www.elephantboycomputers.com "Don't Panic!" MS-MVP Windows - Shell/User
Guest Gerry Posted August 5, 2007 Posted August 5, 2007 Re: Computers on network shutting down Doug Wouldn't your questions be better asked in a Networking newsgroup? -- Hope this helps. Gerry ~~~~ FCA Stourport, England Enquire, plan and execute ~~~~~~~~~~~~~~~~~~~ DougBlakely wrote: > I need to get some fresh ideas. > We're using a POS system called TRS written in visual BASIC. > Network is peer-to-peer, XP pro on all systems. > Problem starts at the machine serving the data files for TRS. Windows > just shuts down by itself. After serveral restarts, hoping that it > was some fluke, the shutdown "spreads" to the client machines! > I need an idea for some method(s) for troubleshooting. > > So far, we have tried: > Format/re-install > Virus & malware scans using various products > Running a nework monitor on a couple of machines until one shuts down. > > None of the above yields anything helpful. > > Thanks all!
Guest DougBlakely Posted August 6, 2007 Posted August 6, 2007 Re: Computers on network shutting down Thanks! I am very grateful for everyone's time. I have not been able to account for any changes that coincide with this phenomenon. The first occurance was back in 2006. After formatting and re-loading Windows it went away. Then it came back some months later. They decided to buy all new machines (for various reasons) at that point. They got 10 identical 3G P4 Dell machines in early 07 and everything worked correctly..for a while. A few months later it came back. When I contacted TRS tech support, the author told me that there is no way the software or data can do it. Hmmmm. That's what I would think...and yet.... What I really want to know is what I can check, monitor, etc. to discover how this happens and hopefully stop it. -- Doug Blakely Blakely Communications Claremore, OK "Malke" wrote: > DougBlakely wrote: > > I need to get some fresh ideas. > > We're using a POS system called TRS written in visual BASIC. > > Network is peer-to-peer, XP pro on all systems. > > Problem starts at the machine serving the data files for TRS. Windows just > > shuts down by itself. After serveral restarts, hoping that it was some fluke, > > the shutdown "spreads" to the client machines! > > I need an idea for some method(s) for troubleshooting. > > > > So far, we have tried: > > Format/re-install > > Virus & malware scans using various products > > Running a nework monitor on a couple of machines until one shuts down. > > > > None of the above yields anything helpful. > > Offhand, it sounds like possibly the database is corrupted, although why > that would shut the machines down I don't know. Normally if there is a > failure machines will restart instead of just shut down. Is there > anything in the Event Viewer logs? Start>Run>eventvwr.msc [enter] > > If this is a new phenomenon, what changed between the time things worked > and the time they didn't? > > You should contact tech support for TRS for this. > > > Malke > -- > Elephant Boy Computers > http://www.elephantboycomputers.com > "Don't Panic!" > MS-MVP Windows - Shell/User >
Guest DougBlakely Posted August 6, 2007 Posted August 6, 2007 Re: Computers on network shutting down Thanks, Gerry. I didn't realize there WAS a networking group until after I posted this in "General". So, I posted a very similar inquiry in the netoworking group. Unfortunately, I didn't know that I was "cross-posting". Gulp. I got scolded for that. -- Doug Blakely Blakely Communications Claremore, OK "Gerry" wrote: > Doug > > Wouldn't your questions be better asked in a Networking newsgroup? > > -- > > > > Hope this helps. > > Gerry > ~~~~ > FCA > Stourport, England > Enquire, plan and execute > ~~~~~~~~~~~~~~~~~~~ > > > > DougBlakely wrote: > > I need to get some fresh ideas. > > We're using a POS system called TRS written in visual BASIC. > > Network is peer-to-peer, XP pro on all systems. > > Problem starts at the machine serving the data files for TRS. Windows > > just shuts down by itself. After serveral restarts, hoping that it > > was some fluke, the shutdown "spreads" to the client machines! > > I need an idea for some method(s) for troubleshooting. > > > > So far, we have tried: > > Format/re-install > > Virus & malware scans using various products > > Running a nework monitor on a couple of machines until one shuts down. > > > > None of the above yields anything helpful. > > > > Thanks all! > > >
Guest Ken Blake, MVP Posted August 6, 2007 Posted August 6, 2007 Re: Computers on network shutting down On Mon, 6 Aug 2007 10:06:03 -0700, DougBlakely <DougBlakely@discussions.microsoft.com> wrote: > Thanks, Gerry. > > I didn't realize there WAS a networking group until after I posted this in > "General". So, I posted a very similar inquiry in the netoworking group. > > Unfortunately, I didn't know that I was "cross-posting". Gulp. I got scolded > for that. Just for future reference, cross-posting is posting a single message simultaneously to more than one newsgroup. There's nothing wrong with doing that if you cross-post to only a *few* newsgroups and they are related ones. It sounds like what you did was multi-post to two newsgroups--send two messages separately--and that's bad. Not to scold you, but just to inform you--here's my standard post on multi-posting: Please do not send the same message separately to more than one newsgroup (called multiposting). Doing so just fragments the thread, so someone who answers in one newsgroup doesn't get to see answers from others in another newsgroup. And for those who read all the newsgroups the message is multiposted to, they see the message multiple times instead of once (they would see it only once if you correctly crossposted instead). This wastes everyone's time, and gets you poorer help than you should get. If you must send the same message to more than one newsgroup, please do so by crossposting (but only to a *few* related newsgroups). Please see "What is the accepted way to share a message across multiple newsgroups?" at http://smjg.port5.com/faqs/usenet/xpost.html -- Ken Blake, Microsoft MVP Windows - Shell/User Please Reply to the Newsgroup
Guest DougBlakely Posted August 6, 2007 Posted August 6, 2007 Re: Computers on network shutting down Ken, thank you. That is very helpful. -- Doug Blakely Blakely Communications Claremore, OK "Ken Blake, MVP" wrote: > On Mon, 6 Aug 2007 10:06:03 -0700, DougBlakely > <DougBlakely@discussions.microsoft.com> wrote: > > > Thanks, Gerry. > > > > I didn't realize there WAS a networking group until after I posted this in > > "General". So, I posted a very similar inquiry in the netoworking group. > > > > Unfortunately, I didn't know that I was "cross-posting". Gulp. I got scolded > > for that. > > > > Just for future reference, cross-posting is posting a single message > simultaneously to more than one newsgroup. There's nothing wrong with > doing that if you cross-post to only a *few* newsgroups and they are > related ones. > > It sounds like what you did was multi-post to two newsgroups--send two > messages separately--and that's bad. > > Not to scold you, but just to inform you--here's my standard post on > multi-posting: > > Please do not send the same message separately to more than one > newsgroup (called multiposting). Doing so just fragments the thread, > so someone who answers in one newsgroup doesn't get to see answers > from others in another newsgroup. And for those who read all the > newsgroups the message is multiposted to, they see the message > multiple times instead of once (they would see it only once if you > correctly crossposted instead). This wastes everyone's time, and gets > you poorer help than you should get. > > If you must send the same message to more than one newsgroup, please > do so by crossposting (but only to a *few* related newsgroups). > > Please see "What is the accepted way to share a message across > multiple newsgroups?" at http://smjg.port5.com/faqs/usenet/xpost.html > > -- > Ken Blake, Microsoft MVP Windows - Shell/User > Please Reply to the Newsgroup >
Guest Ken Blake, MVP Posted August 6, 2007 Posted August 6, 2007 Re: Computers on network shutting down On Mon, 6 Aug 2007 13:26:00 -0700, DougBlakely <DougBlakely@discussions.microsoft.com> wrote: > Ken, thank you. > That is very helpful. You're welcome. Glad to help. > "Ken Blake, MVP" wrote: > > > On Mon, 6 Aug 2007 10:06:03 -0700, DougBlakely > > <DougBlakely@discussions.microsoft.com> wrote: > > > > > Thanks, Gerry. > > > > > > I didn't realize there WAS a networking group until after I posted this in > > > "General". So, I posted a very similar inquiry in the netoworking group. > > > > > > Unfortunately, I didn't know that I was "cross-posting". Gulp. I got scolded > > > for that. > > > > > > > > Just for future reference, cross-posting is posting a single message > > simultaneously to more than one newsgroup. There's nothing wrong with > > doing that if you cross-post to only a *few* newsgroups and they are > > related ones. > > > > It sounds like what you did was multi-post to two newsgroups--send two > > messages separately--and that's bad. > > > > Not to scold you, but just to inform you--here's my standard post on > > multi-posting: > > > > Please do not send the same message separately to more than one > > newsgroup (called multiposting). Doing so just fragments the thread, > > so someone who answers in one newsgroup doesn't get to see answers > > from others in another newsgroup. And for those who read all the > > newsgroups the message is multiposted to, they see the message > > multiple times instead of once (they would see it only once if you > > correctly crossposted instead). This wastes everyone's time, and gets > > you poorer help than you should get. > > > > If you must send the same message to more than one newsgroup, please > > do so by crossposting (but only to a *few* related newsgroups). > > > > Please see "What is the accepted way to share a message across > > multiple newsgroups?" at http://smjg.port5.com/faqs/usenet/xpost.html > > > > -- > > Ken Blake, Microsoft MVP Windows - Shell/User > > Please Reply to the Newsgroup > > -- Ken Blake, Microsoft MVP Windows - Shell/User Please Reply to the Newsgroup
Recommended Posts