Error messages

When I try to open a Solaris rulebase on a Microsoft Windows machine, I get the message "Invalid Microagent ... Unable to construct Test Editor"

Some rulebases are platform-independent whereas some rulebases are platform-independent.

When editing a rulebase, all of the microagents used within that rulebase must be loaded locally in the agent (or the repository's host agent) used as the editing platform. Otherwise, the agent does not have access to the necessary descriptors.

Platform: Not Specified

Version: All

When you open a rulebase loaded by an agent, you can look at all of its rules. However, you cannot choose a data source that is unavailable to that agent, and you cannot edit tests that rely on unavailable data sources. Why?

If you want to examine or change rules whose data sources are not available from the machine on which you are using the TIBCO Hawk Display, interact with an agent located on a machine on which the data sources are available. For example, if you have Microsoft Windows and Solaris machines in your network and you want to examine a Solaris rulebase from a Microsoft Windows machine, select an agent running on a Solaris machine, choose 'Get RuleBases', and examine or change the rules there.

Platform: Not Specified

Version: All

Why is the Application Event Log full of performance DLL errors?

Under certain conditions the TIBCO Hawk Performance Microagent can cause the Application Event Log to fill rapidly with messages similar to:

"The open procedure for service "htpps4.1" in DLL e:\netscape\server\bin\htps\nsctr.dll failed. Performance data for this service is not available. Status code returns DWORD0 1008". 

This error occurs whenever a Microsoft Windows service's performance DLL (service htpps4.1 in this case) fails to load. Each failed load also causes the application (Hawk HMA) to leak memory. The problem lies in the Microsoft Windows performance counter libraries. To fix this problem, rename the DLL listed in the error message.

Platform: Microsoft Windows 2000   

Version: All

The Microsoft Windows Performance API reports errors regarding counter values that cause mathematical errors in performance statistics calculations.

The Microsoft Windows Performance API is driven by a set of Microsoft Windows and third-party extension DLLs, which implement the various performance objects and associated counters. These extension DLLs may occasionally return counter values that cause mathematical errors in performance statistics calculations. These errors are reported by the Microsoft Windows Performance API. For example:

Error Code Error Text

0x8000078D8 A counter with a negative value was detected.

0x8000078D6 A counter with a negative denominator was detected.

These errors are reported by HMA for information purposes. The errors are not caused by HMA. They are caused by bugs or design flaws in the associated extension DLL.

Platform: Microsoft Windows

Version: All

Why do I get an error when I call a method of my instrumented application?

Check that the message descriptor in your describeMethods return messages that match up exactly with the messages returned by your methods. If the identifiers do not match, an error is returned. See the TIBCO Hawk Programmer's Guide for further details.

Platform: Not Specified

Version: All

What does a NoDataSource error mean?

This type of error means that a rule attempted to obtain information from a data source that did not exist at the time of the rule evaluation and the specified information could not be obtained.

If the data source is a HMA microagent method, check to see that the HMA process is running. When the operating system starts, make sure your HMA process starts before your TIBCO Hawk agent process.

If the HMA process is running, there may be some reason why the communication between the agent and the HMA is upset.

If the data source is a log file, check to see that the log file has not been renamed or moved.
If the data source is an instrumented application, check to see if the application is running.

Rules that operate on applications instrumented with AMI can only work when the application is running.

Platform: Not Specified

Version: All