AVIcode Terminology

Recently, I started to learn AVIcode. I wanted to cover some terminology to make clear each component, AVIcode is a product and currently still is that can run as a standalone product, although Microsoft want you to use it as an ‘Add-In’ to Operations Manager.

Intercept Agent
AVIcode Intercept Agent provides the following monitors:

1. Intercept Operations Monitor – collects performance and exception information from .NET applications.
2. Intercept Event Log Monitor (part of the Intercept service) – collects events from the Windows Event Log
3. Intercept Performance Counter Monitor  (part of the Intercept service) – collects both State performance counters (for current application health state) and Troubleshooting performance counters (for historical application health state)

The Intercept monitors attach to any .NET application on the fly, without any code modifications or recompilation of the monitored application.  The Intercept Agent uses standard common language runtime (CLR) mechanisms, so that it will have no behavioral effect on the monitored application.

Intercept Service
The Intercept Service is responsible for activating monitoring for Applications, Web Services, Executables, Windows Services, COM+ Applications, Event Logs, Performance Counters and instrumentation. It also controls the Intercept Event Log Monitor and the Intercept Performance Counter Monitor.

SE-Viewer Configuration Utility
The SE-Viewer Configuration Utility  provides a convenient way to configure SE-Viewer to use a Microsoft SQL Server database and to manage the Advisor database.

Intercept Management Console
The Intercept Management Console provides a convenient way to configure monitored applications in Intercept Studio.  It allows system administrators to add applications, to select either performance or event monitoring, and to set thresholds and other options.

 

 

Advertisements

Operations Manager 2007 R2 – SQL 2008 R2 Reporting Services Installation Hang Issue

How to install Operations Manager 2007 R2 Reporting

Note You must follow these steps on the SQL Server 2008 R2 Reporting Services server.

  1. Open Computer Management.
  2. In the Computer Management MMC snap-in, expand System Tools, expand Local Users and Groups, and then click Groups.
  3. Locate the following group:
    SQLServerReportServerUser$<var><hostname></var>$MSRS10_50.<var><SQLInstanceName></var>
  4. Rename the group to the following by removing “_50” from the group name:
    SQLServerReportServerUser$<var><hostname></var>$MSRS10.<var><SQLInstanceName></var>
  5. Install System Center Operations Manager 2007 R2 Reporting.
    For more information, see the following Microsoft TechNet Website:

    Important: When you install System Center Operations Manager 2007 R2 Reporting, you should not install the Data Warehouse component.

  6. After you install System Center Operations Manager 2007 R2 Reporting, rename SQLServerReportServerUser$<var><hostname></var>$MSSRS10.<var><SQLInstanceName></var> back to original name SQLServerReportServerUser$<var><hostname></var>$MSSRS10_50.<var><SQLInstanceName></var>

Operations Manager 2007: Operations Console does not open and gives SDK service error

When you try to open the System Center Operations Manager 2007 console on the RMS server it may fail to open with the following error:

Date: <date> <time>
Application: System Center Operations Manager 2007
Application Version: 6.0.6278.0
Severity: Error
Message: Failed to connect to server ‘RMS-FQDN’

Microsoft.EnterpriseManagement.Common.SdkServiceNotInitializedException: Sdk Service has not yet initialized. Please retry
at Microsoft.EnterpriseManagement.DataAbstractionLayer.SdkDataAbstractionLayer.HandleIndigoExceptions(Exception ex)
at Microsoft.EnterpriseManagement.DataAbstractionLayer.SdkDataAbstractionLayer.CreateChannel(TieredManagementGroupConnectionSettings managementGroupTier)
at Microsoft.EnterpriseManagement.DataAbstractionLayer.SdkDataAbstractionLayer..ctor(DuplexChannelFactory`1 channelFactory, TieredManagementGroupConnectionSettings managementGroupTier, IClientDataAccess callback, CacheMode cacheMode)
at Microsoft.EnterpriseManagement.DataAbstractionLayer.SdkDataAbstractionLayer.CreateEndpoint(ManagementGroupConnectionSettings connectionSettings, IClientDataAccess clientCallback)
at Microsoft.EnterpriseManagement.DataAbstractionLayer.SdkDataAbstractionLayer.Connect(ManagementGroupConnectionSettings connectionSettings)
at Microsoft.EnterpriseManagement.ManagementGroup..ctor(String serverName)
at Microsoft.EnterpriseManagement.ManagementGroup.Connect(String serverName)
at Microsoft.EnterpriseManagement.Mom.Internal.UI.Common.ManagementGroupSessionManager.Connect(String server)
at Microsoft.EnterpriseManagement.Mom.Internal.UI.Console.ConsoleWindowBase.TryConnectToManagementGroupJob(Object sender, ConsoleJobEventArgs args)

You may also see the following in the Operations Manager event log on the RMS:

Event Type: Error
Event Source: OpsMgr SDK Service
Event Category: None
Event ID: 26322
Date:  <date>
Time:  <time>
User:  N/A
Computer: <RMS-Name>
Description:
A database exception was thrown in the Operations Manager SDK service. Exception Message: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 26 – Error Locating Server/Instance Specified)

This can happen if the RMS is not able to contact the SQL Server where the Operations Manager database resides.

AVIcode 5.7: 5 reasons you will not see data in AVIcode (Reason #2)

There are a few exception classes that are excluded from data collection in the default configuration:

System.Threading.ThreadAbortException
System.AppDomainUnloadedException
System.ArgumentException
System.Web.HttpUnhandledException

You can only disable/enable data collection for particular exception classes if you update configuration files manually. There is no UI option for that.

In order to enable these for exceptions (or to disable some other exceptions), do this:

– Open PMonitor.config file (\Program Files\AVIcode\Intercept\Agent\v5.7.491\Configuration\Standard)

– Locate ss:exceptions section for w3wp application

Excluded Exceptions

Excluded Exceptions

– Add condition=”excluded” lines for the exceptions you want to disable
– Remove such lines for the exceptions you want AVIcode to capture

Note that “ss:exceptions” settings can be configured globally for all applications, or they can be configured per application.

AVIcode 5.7: 5 reasons you will not see data in AVIcode (Reason #1)

Reason #1: Supported .NET FW is not configured properly

When AVIcode Agent gets installed, it is configured to support all versions of .NET FW up to and including the maximum version specified in the configuration file. If the version of .NET FW installed on the agent server has a higher build number, that version will not be monitored.

The value of this configuration parameter can be updated right in the configuration file:

\Program Files\AVIcode\Intercept\Agent\v5.7.491\Configuration\Standard\PMonitor.config

Figure 1: Supported FW settings

As an alternative, you can modify this parameter in the Intercept MMC Console:

Supported FW in the Intercept MMC

Figure 2: Supported FW in the Intercept MMC

If you have .NET Management Pack installed, though, you should create an override:

Supported FW in the .NET MP

Figure 3: Supported FW in the .NET MP

Agent versus Agentless Monitoring for Operations Manager 2007

Like many other software packages, Operations Manager can deploy an agent to the system being monitored. Whether or not to deploy agents in general is always a discussion point. Let’s talk about the agent used by Operations Manager.

While Operations Manager can use agentless monitoring, most management packs are built to perform better with an agent. The rules and other managment pack objects are deployed to each agent that they pertain to, allowing monitoring to occur even if contact is lost with the management server. Without an agent, the agent component on the management server collects data from the agentless managed computer using remote calls to that system. If the two systems cannot communicate, information is not collected.

In some cases, any change to a computer may lead to complications. While sometimes these complications are more political than operational, the IT group may want to avoid even the appearance of affecting an applicaiton server to avoid potential liability. Agentless sytems have a more limited set of features than do agent-based managed computers. Some mangement packs will not even run agentless. This list includes:

  1.     Active Directory
  2.     Exchange
  3.     IIS
  4.     SharePoint Portal Server

Other management packs such as SQL Server can run agentless but with reduced functionality.

For Operations Manager, agentless monitoring is recommended only when an agent-managed configuration is not possible. While agentless monitoring may decrease the load on the monitored system, it increases the resource load on the managment server monitoring that system. It also leads to increased network utilization when the data is sent across the pipe, is not as reliable in collecting data as using agent-monitored systems, and has reduced management capability.