A computer's message log can provide you with important diagnostics information in case the computer isn't behaving as expected.

To view the message log, select ANALYZE > Computers > Computer Search, and search for a computer. Then, in the search results, click the name of the required computer, and then select the Message Log tab.

You can only do this if you're a PerformanceGuard administrator.

When you analyze a computer's message you may find it helpful to know some log messages that relate to typical problems—and what you can do to solve those problems:

First Chance Failure Detected with 'Maximum Agent Size Exceeded'

The PerformanceGuard agent on the computer regularly checks how much of the host computer's memory it uses. If the agent detects that it uses 60 MB or more of the host computer's RAM, it will wait a few seconds and then restart itself in order not to use excessive amounts of the computer's memory.

This message from the InitApplication component marks the start of the waiting time. If the agent's memory usage doesn't drop below 60 MB within a few seconds, the agent will automatically restart, and you'll see the message Agent restart caused by : Agent memory size exceeded (described in the following).

Older versions of the PerformanceGuard agent use a limit of 40 MB, and very old agent versions don't have the memory usage check feature at all.

Solution: If the message occurs rarely, you can safely ignore it. If the message occurs often, please report it to CapaSystems Support (to view contact options, click the PerformanceGuard logo at the top of this page to go to the front page of the help system).

Agent Restart Caused by : Agent Memory Size Exceeded

Example: Agent restart caused by : Agent memory size exceeded - Heap size (kB) = 65290

The PerformanceGuard agent on the computer regularly checks how much of the host computer's memory it uses. If the agent detects that it uses 60 MB or more of the host computer's RAM for more than a few seconds, the agent will automatically restart itself in order not to use excessive amounts of the computer's memory.

This message from the SelfSurveillance component marks the restart of the agent and shows you the amount of memory (in KB) that the agent used before it was restarted.

Older versions of the PerformanceGuard agent use a limit of 40 MB, and very old agent versions don't have the memory usage check feature at all.

You can read more about the PerformanceGuard agent's self checks in Agent Self-Surveillance.

Could Not Create Custom Counter

This message from the E2EPerfCustomCounterProcessor component occurs if the syntax in a custom counter isn't valid.
The message will also occur if the syntax is valid, but the PerformanceGuard agent on the computer can't find the information that the custom counter asks it to find, for example if the custom counter asks the PerformanceGuard agent to collect information about the D: drive on a computer that doesn't have a D: drive.

Solution: Verify that the custom counter syntax is valid, and that the custom counter is relevant for the computer in question.

Could Not Set Timing Mode

This message from the npf.sys or pgnpf.sys component occurs if the PerformanceGuard agent isn't allowed to write in the registry key that controls the packet capture driver.

This is logged as a severe error because the agent is unable to do something. In reality, however, the problem is not very serious, because the npf.sys and pgnpf.sys components will simply use the default timing method instead.

Get Login time via Wmi failed. Using alternative

This message from the PSystemInfo component occurs if the operating system of the computer that runs the PerformanceGuard agent doesn't support the method used to get login information.

This is not a serious problem. The agent simply uses another login method, and that's what causes the message.

Solution: Ignore the message.

No adapter found to capture from

This message from the E2ETcp component typically occurs if the computer that runs the PerformanceGuard agent does not have a working network connection.

If you get this message from an agent on a computer that does have a working network connection, there's a problem with connecting the packet capture driver with the network interface. This can happen if the computer has a complex setup, for example with teamed network adapters or locally installed firewall software that's not fully NDIS compliant.

Finally, the message may also be caused if any of the agent's WinPcap components have become corrupt.

The message is typically followed by a Configuration failed message.

Solution: First check if the computer has a working network connection. Next, try to find out if someone has installed non-NDIS compliant firewall software or an old WinPcap version on the computer, because that may have caused the problem. If you're stuck, report the problem to CapaSystems support (see contact options in the Technical Support section at the bottom of the page).

Configuration failed

This message from the E2ETcp component occurs if the computer that runs the PerformanceGuard agent does not have a working network connection or if there's a problem with connecting the packet capture driver with the network interface.

See No adapter found to capture from in the previous.

Search this documentation

On this page

In this section