Tracking Down Intermittent Problems

team lib

Intermittent problems are by far the most difficult to solve because they don't happen when you want them to and you can't always reproduce them. These types of problems occur after a sequence of events, usually in a particular order unbeknownst to you. Your work is to figure out the sequence of events. Impossible, you say. Not really!

If you started your system log, record the following items to help you eliminate possible causes of the problem:

  • Note the time and day of the problem: For example, does the problem seem to occur only at 10 A.M. on Wednesdays? Perhaps a particular activity in one of the departments happens every week, such as right before a departmental meeting when everyone is trying to access or print reports . This extra activity could place a load on the server or the network. Look for trends in dates and time. Use System Monitor if you suspect this.

  • Note the equipment in use: Does the problem occur only on a particular workstation or server? Does the problem occur only when a particular user logs on to the network? Check the user 's account information, plus his or her desktop configuration files.

  • Note the application in use: Does the problem occur only when a certain application is used? Reinstall the application. An application file can become corrupt, and the corruption can go unnoticed until a user performs a particular function of that application.

  • Note the environment in use: Does the problem occur only on a certain floor, near a certain area such as an elevator? If so, you may have some wiring conflicts near heavy motors or fluorescent lighting.

  • Check the visitor's log: Does the problem occur every time the maintenance person enters a wiring closet or the computer room? If so, follow this person in the next time and see what he or she is doing. (Don't forget the overcoat and sunglasses!)

  • Viruses: Always an obvious possibility, viruses are often the last things checked. Viruses introduce random oddities onto networks. If you suspect one, immediately disconnect the server from the rest of the network and WAN, and scan it. Until recently, this would have been enough. However, it's important to instruct your users not to send any e-mail if you suspect a virus. You may have to disable the company post office to ensure that no e-mail is distributed at this time.

  • Known bugs : Sometimes, you pound your head into the wall trying to solve a problem that is really a known bug. Check the Microsoft Web site regularly, and check for new service packs. Remember to check other organizations' Web sites as well. For example, if you use Microsoft Office, check Microsoft's site for service packs for that suite. If you use all 3Com Ethernet cards, check the 3Com Web site for driver updates that correct bugs. Staying on top of known problems can save you oodles of time.

team lib


Windows Server 2003 for Dummies
Windows Server 2003 for Dummies
ISBN: 0764516337
EAN: 2147483647
Year: 2003
Pages: 195

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net