• Print
  • Share

Event Viewer Data

  • Updated on 01 May 2018
  • 3 minutes to read
  • Contributors

Event Viewer Data

BizTalk Server has the capability to maintain the logs of different events that happen in the environment. The events will be written into an event log that can be read using a Standard Event Viewer. BizTalk360's Advanced Event Viewer (AEV) is an extended version of Windows Event Viewer. BizTalk360 collects the events from all the servers that a part of the current environment and displays them in the AEV. BizTalk360 also has the Setting to configure which event logs are to be monitored and results collected. For instance, if logs of application events are to be received, you can add the event source to let BizTalk360 know it must generate an event log when there are any errors in the applications. When an application fails, the failure triggers an event (with an id) that will be captured by BizTalk360's Advanced Event Viewer. The cause of the failure may be simple/complicated for the support person to be able to fix it/understand the problem. Once the issue is fixed, the support person can add a knowledge base (KB) article for the particular event code/event log. This will be helpful for other support users to debug the issue if it occurs again in future.

Adding KB Article For The Event Logs

  • Log into the application
  • Click 'Knowledge Base' icon at the top of the page
  • Click 'Event Logs' in the Manage Knowledge Base articles page
  • Click 'Add New' to create a new KB article
  • In the Add New Knowledge base Article page, enter/select the following information. Only when the environment is selected from the drop-down, the application will allow the selection of other items.
  1. Article Title – Give a meaningful name for the article. The best practice would be to provide a name related to the event log.
  2. Event ID – Enter the event ID for which the KB article is created, say 6912
  3. Event Log Description – Enter the detailed information for the KB Article in the text editor space provided. The text can be formatted with the appropriate font/colors/bold/italics and so on.
  4. Environment – Choose the environment for which the KB Article is to be displayed. If the default option (Choose Environment) is chosen, the KB article will be applied to all the environments.
  5. Source – Choose the source from where the event log was generated
  6. Log User – Select the logged in user information
  7. Log Type – Choose the type of event log — whether the event log is for an error/warning/information
  8. Computer name – Select the computer name
  9. Category – Choose the category of the error type — BizTalk server, Enterprise SSO, Message Logging, and so on
  10. Log Name – Select the log name that has been generated for the event log
  • Click 'Save and Close' to save the KB article for the corresponding event log
  • Click 'Save and Add Another' to save the KB article and immediately create another new KB article
  • Click Close - to close the KB article creation window and display the list of created KB articles. It will prompt the user with a confirmation message as 'Are you sure you want to close?'. Click OK to close the KB article creation window.

event viewer data 1.gif

Create multiple articles for the same Event Log

Multiple articles can be created and tagged against the same event log. The application uses the Best Match scenario to identify and display the KB article. This depends on the additional options, known as tags, that the support person chooses while creating a KB article for the particular event log.

When creating multiple articles for the same event log source, follow the exact same steps as shown in "Adding a KB Article for the Event Log" section and select the appropriate tags (Environment, Source, Log User, Log Type, Computer Name, Category, Log Name) for the error code. The tags will play the differentiator role to display the appropriate KB article.