Inspect the Event Viewer

As an administrator of any platform, you should be checking the Event Viewer regardless of what you install or run.This utility can provide you with a great deal of insight about possible problems, and problems that might be waiting to occur.We are going to visit this utility to see what might have happened during the installation and any possible problems that occurred.

To use the Event Viewer, open the BizTalk Server Administration utility. The Event Viewer is "snapped in" by default.To open the Administration tool, go to Start | Programs | Microsoft BizTalk Server 2000 | BizTalk Server Administration.When the MMC opens, you will see the Event Viewer at the bottom of the console as shown in Figure 3.5.

Figure 3.5 The Event Viewer within the BizTalk Server Administration Utility m 'II i ...i. ■ JU

Figure 3.5 The Event Viewer within the BizTalk Server Administration Utility m 'II i ...i. ■ JU

As we look at the console in Figure 3.5, we see that there are errors and informational events associated with BizTalk Server 2000.We should be concerned about all messages that appear, but should pay special attention to the ones identified as errors. (The information events for BizTalk are letting us know that the BizTalk Server 2000 service has started.) Sometimes, these errors will point to a service not running, or an application that suffered a critical error. Regardless of what it might be, by using the reported events, you will be addressing the specific source of your problem, rather than chasing irrelevant hunches and potentially creating more problems. Let's look at the BizTalk Server error a little closer (Figure 3.6).

Figure 3.6 A BizTalk Server 2000 Critical Error Message within the Event Viewer

Figure 3.6 A BizTalk Server 2000 Critical Error Message within the Event Viewer

Upon further investigation by selecting the actual error in the Event Viewer, you can see that the receive function experienced problems. This is not a happy occasion, but it is certainly nice to know from the log what the problem might be.The log tells us that BizTalk Server could not process the receive function listed, and thus disabled it. Having been reenabled, it seems to be functioning properly after two days of stress testing. A good practice is to keep monitoring both the Event Log and the receive function in case it happens again. Since the log has not reported any more errors, we could say that it is safe to finish the preparatory and testing phase.

Was this article helpful?

0 0

Post a comment