|
|
| Copyright © Cloud Software Group, Inc. All Rights Reserved |
Programming error. AMI error handle passed to function is invalid, corrupted or was previously destroyed.Programming error. AMI session handle passed to function is invalid, corrupted or was previously destroyed.Programming error. AMI method handle passed to function is invalid, corrupted or was previously destroyed.Programming error. AMI subscription handle passed to function is invalid, corrupted or was previously destroyed.Programming error. AMI parameter list handle passed to function is invalid, corrupted or was previously destroyed.Programming error. AMI parameter list handle passed to function is invalid, corrupted or was previously destroyed.Programming error. AMI parameter handle passed to function is invalid, corrupted or was previously destroyed.An agent (e.g. TIBCO Hawk Agent or Console API application) has invoked a non-existent method on this AMI session. Contact TIBCO Support for assistance.Programming error. Parameter function called for non-existent parameter. Check the method creation code to insure that the specified parameter was actually added to the method.TIBCO Rendezvous error <error number> occurred attempting to get value for argument <argument name> of method <method name>. <error text>.The specified TIBCO Rendezvous error occurred when attempting to get argument value. Refer to TIBCO Rendezvous documentation.<method name> invocation received for unknown subscription with context <context number> and reply subject <subject name>.Unable to get CONTEXT field in AMI reply message for <microagent_id>, <com.tibco.rv.TibrvException>An AMI message is incorrectly formatted. Consult the documentation for the AMI instrumented application.Unable to process AMI reply message in: <microagent_id>, <com.tibco.rv.TibrvException>Async method control msg reply contained non-empty RETURN field, Async method may have sent data to incorrect reply-subjectAn AMI message is incorrectly formatted. Contact the vendor of the AMI instrumented application.An error has been received from an AMI instrumented application. Consult the documentation for the AMI instrumented application.Method <name> returned tabular data but INDEX was not specified. Ignoring all but first RETURNS fieldAn AMI instrumented application is returning tabular data for a method that was not described to return tabular data. Contact the vendor of the AMI instrumented application.An AMI message is incorrectly formatted. Contact the vendor of the AMI instrumented application.Announced AMI application <application name> did not respond to first heartbeat request. Presumed dead.Discovering methods. AMI App: <name>, exception: <com.tibco.rv.TibrvException>An AMI message is incorrectly formatted. Contact the vendor of the AMI instrumented application.Creating AMI microagent <name>, <COM.TIBCO.hawk.talon.MicroAgentException>;An AMI message is incorrectly formatted. Contact the vendor of the AMI instrumented application.Unable to remove AMI microagent <name>, <COM.TIBCO.hawk.talon.MicroAgentException>An AMI message is incorrectly formatted. Contact the vendor of the AMI instrumented application.AmiTibrvService dispatch thread was interrupted: <java.io.InterruptedException>AmiTibrvService dispatch thread caught exception: <com.tibco.rv.TibrvException>Internal error. Attempt to lookup an unknown error message. Contact TIBCO Support for assistance.TIBCO Hawk HMA tracing function failed for the specified reason. If resolution is not obvious from the error description then contact TIBCO Support for assistance.An invalid value was specified for a command line option. Refer to TIBCO Hawk documentation for command line description.Execution of TIBCO Hawk HMA failed. Error <error number> occurred on thread <thread ID (hex)> at line <line number> in file <file name>. <error text>.Wrapper used to report errors with thread ID, file name, and line number. Actual error could be any of the errors documented for the TIBCO Hawk HMA.An invalid directory name was specified. If resolution is not obvious from the error description then contact TIBCO Support for assistance.An invalid file name was specified. If resolution is not obvious from the error description then contact TIBCO Support for assistance.An error occurred for the specified file function. If resolution is not obvious from the error description then contact TIBCO Support for assistance.An invalid command line option was specified. Refer to TIBCO Hawk documentation for command line description.An invalid value was specified for a command line option. Refer to TIBCO Hawk documentation for command line description.No value was specified for a command line option. Refer to TIBCO Hawk documentation for command line description.The specified error was encountered processing the specified command line. Refer to TIBCO Hawk documentation for command line description.OPTIONS RVD_SESSION<rendezvous parameters> TRACELEVEL<trace level> LOGDIR<log directory> LOGMAXSIZE<maximum log size> LOGMAXNUM<maximum log number>Error <error number> occurred on thread <thread ID (hex)> at line <line number> in file <file name>. <error text>.Wrapper used to report errors with thread ID, file name, and line number. Actual error could be any of the errors documented for the TIBCO Hawk HMA.An error occurred for the specified function. If resolution is not obvious from the error description, contact TIBCO Support for assistance.Unable to obtain configuration for TIBCO Hawk HMA. If resolution is not obvious from the error description, contact TIBCO Support for assistance.Attempt was made to synchronously invoke an asynchronous method. Specific method does not support synchronous invocation.Invalid microagent name was specified in command line option. Refer to TIBCO Hawk documentation for command line description.TIBCO Hawk HMA microagent <microagent name> has been disabled via disable command line option.Attempt to increase default thread stack size failed. Function <function name> returned error <Error code>TIBCO Hawk HMA signal handling for signal <signal name> has been disabled via command line option.This message logs the fact that the HMA has been configured via command line option -disable to ignore the specified signal. This disables the default HMA signal handling for that signal.The HMA was unable to set the default signal handling for the specified signal. The default signal handling will not be in effect. Contact TIBCO Support for assistance.If a restart method invocation is made against a microagent already in the process of restarting then this error is generated. You cannot restart a microagent which is being stopped by a previous restart invocation.Internal error. OpenSCManager failed. WIN32 error <error code> (<error code hex>): <error text>This error will also contain the OS specific error description. If resolution is not obvious from the error description then contact TIBCO Support for assistance.Internal error. GetServiceDisplayName failed for service "<service name>". WIN32 error <error code> (<error code hex>): <error text>This error will also contain the OS specific error description. If resolution is not obvious from the error description then contact TIBCO Support for assistance.Internal error. QueryServiceConfig failed for service "<service name>". WIN32 error <error code> (<error code hex>): <error text>This error will also contain the OS specific error description. If resolution is not obvious from the error description then contact TIBCO Support for assistance.Internal error. EnumServicesStatus failed. WIN32 error <error code> (<error code hex>): <error text>This error will also contain the OS specific error description. If resolution is not obvious from the error description then contact TIBCO Support for assistance.StartService failed for service "<service name>". WIN32 error <error code> (<error code hex>): <error text>This error will also contain the OS specific error description. If resolution is not obvious from the error description then contact TIBCO Support for assistance.OpenService failed for service "<service name>". WIN32 error <error code> (<error code hex>): <error text>This error will also contain the OS specific error description. If resolution is not obvious from the error description then contact TIBCO Support for assistance.ControlService failed for service "<service name>". WIN32 error <error code> (<error code hex>): <error text>This error will also contain the OS specific error description. If resolution is not obvious from the error description then contact TIBCO Support for assistance.QueryServiceStatus failed for service "<service name>". WIN32 error <error code> (<error code hex>): <error text>This error will also contain the OS specific error description. If resolution is not obvious from the error description then contact TIBCO Support for assistance.ChangeServiceConfig failed for service "<service name>". WIN32 error <error code> (<error code hex>): <error text>This error will also contain the OS specific error description. If resolution is not obvious from the error description then contact TIBCO Support for assistance.Unable to retrieve process command line for this Microsoft Operating System version. Please contact TIBCO Hawk technical support.Internal error. EnumProcesses failed. WIN32 error <error code> (<error code hex>): <error text>This error will also contain the OS specific error description. If resolution is not obvious from the error description then contact TIBCO Support for assistance.HMA process could not load ntdll.dll. Make sure that PATH environment variable contains path which points to ntdll.dll.Could not locate entry point for function NtQueryInformationProcess in dll NTDLL.DLL. 'Parent Process ID' column for all processes are set to -1.Make sure TIBCO Hawk HMA is running with root permission. If not resolved then contact TIBCO Support for assistance.This error will also contain the OS specific error description. If resolution is not obvious from the error description then contact TIBCO Support for assistance.This error will also contain the OS specific error description. If resolution is not obvious from the error description then contact TIBCO Support for assistance.This error will also contain the OS specific error description. If resolution is not obvious from the error description then contact TIBCO Support for assistance.This error will also contain the OS specific error description. If resolution is not obvious from the error description then contact TIBCO Support for assistance.<function name> socket(AF_INET,SOCK_DGRAM,0) returned [<socket>] errno[<error number] [<error text>]This error will also contain the OS specific error description. If resolution is not obvious from the error description then contact TIBCO Support for assistance.<function name> ioctl(<socket>, <ioctl function id>,) returned [<ioctl rc>] errno[<error number] [<error text>]This error will also contain the OS specific error description. If resolution is not obvious from the error description then contact TIBCO Support for assistance.<function name> ioctl(<socket> NIC[%d] returned [<ioctl rc>] errno[<error number] [<error text>]This error will also contain the OS specific error description. If resolution is not obvious from the error description then contact TIBCO Support for assistance.lseek(<file handle>, <seek operation>, <seek position>) returned [<return code>] errno[<error number] [<error text>]This error will also contain the OS specific error description. If resolution is not obvious from the error description then contact TIBCO Support for assistance.read(<file handle>, <buffer address>, <buffer size>) returned [<return code>] errno[<error number] [<error text>]This error will also contain the OS specific error description. If resolution is not obvious from the error description then contact TIBCO Support for assistance.This error will also contain the OS specific error description. If resolution is not obvious from the error description then contact TIBCO Support for assistance. If "access denied" is indicated then make sure TIBCO Hawk HMA is running with root permission.<function name> knlist lookup on symbol [<symbol name] failed - res[<return code>] errno[<error number] [<error text>].This error will also contain the OS specific error description. If resolution is not obvious from the error description then contact TIBCO Support for assistance.Make sure TIBCO Hawk HMA is running with root permission. If not resolved then contact TIBCO Support for assistance.HWKHMA-00 4030putmsg stream function failed for primitive <primitive name> errno = <error number> and errormessage = <error text>.Name Of Driver: <driver name>, PPA Number assigned to LAN interface: <interface number>, NMID No: <nmid number>, Card Instance Number: <card instance number>, Media Access Control: <media access control>.Failed to get required control message. Expected Primitive: <primitive number>, Primitive in error: <primitive error>, DLPI error code: <dlpi error code>, UNIX error code: <unix error code>Received Wrong Primitive. Expected Primitive: <primitive number>, Received Primitive: <primitive number>.This error will also contain the OS specific error description. If resolution is not obvious from the error description then contact TIBCO Support for assistance.This error will also contain the OS specific error description. If resolution is not obvious from the error description then contact TIBCO Support for assistance.This error will also contain the OS specific error description. If resolution is not obvious from the error description then contact TIBCO Support for assistance.This error will also contain the OS specific error description. If resolution is not obvious from the error description then contact TIBCO Support for assistance.This error will also contain the OS specific error description. If resolution is not obvious from the error description then contact TIBCO Support for assistance.This error will also contain the OS specific error description. If resolution is not obvious from the error description then contact TIBCO Support for assistance.This error will also contain the OS specific error description. If resolution is not obvious from the error description then contact TIBCO Support for assistance.This error will also contain the OS specific error description. If resolution is not obvious from the error description then contact TIBCO Support for assistance.This error will also contain the OS specific error description. If resolution is not obvious from the error description then contact TIBCO Support for assistance.This error will also contain the OS specific error description. If resolution is not obvious from the error description then contact TIBCO Support for assistance.This error will also contain the OS specific error description. If resolution is not obvious from the error description then contact TIBCO Support for assistance.This error will also contain the OS specific error description. If resolution is not obvious from the error description then contact TIBCO Support for assistance.This error will also contain the OS specific error description. If resolution is not obvious from the error description then contact TIBCO Support for assistance.This error will also contain the OS specific error description. If resolution is not obvious from the error description then contact TIBCO Support for assistance.Invalid network parameter specified in Rendezvous microagent network parameter. Refer to TIBCO Hawk Microagent Reference manual.hma_getHostAddr() returned <error code> for network <network parameter> and daemon <daemon parameter>.<function name>: received advisory message with subject: <subject name> message: <message text>.The argument "HMA_N_INTERVAL" is less than 90 seconds. It has been changed to the default value of 90 seconds.Unable to determine RV daemon statistics because some daemon status information were missing in the last reporting interval.Object encountered with no defined counters so no data can be returned. Object is being ignored. No action required.PdhCollectQueryData for method <method name> instance <instance name> failed with error <error code>.PdhCollectQueryData for object <object name> and instance <instance name> failed with error <error code>.PdhGetFormattedCounterValue for object <object name> and instance <instance name> and counter <counter name> failed with error <error code>.PdhRemoveCounter for object <object name> and instance <instance name> and counter <counter id> failed with error <error code>.PdhCloseQuery for object <object name> and instance <instance name> failed with error <error code>.Failed to get instance and counter information for method <methodname>. Ignoring method : <method name>Specified Object (Method) does not contain any Counter and Instance Information. Skipping this Object(Method) from announcing it as a method during discovery process.Found duplicate counter name: <counter name> for method: <method name>. Ignoring method: <method name>.Specified Object contains duplicate counter name. Skipping this Object from announcing as method during discovery process.RegOpenKeyEx failed for key <key name>. WIN32 error <error code> (<error code hex>): <error text>This error will also contain the OS specific error description. If resolution is not obvious from the error description then contact TIBCO Support for assistance.RegFlushKey failed for key <key name>. WIN32 error <error code> (<error code hex>): <error text>This error will also contain the OS specific error description. If resolution is not obvious from the error description then contact TIBCO Support for assistance.RegCloseKey failed for key <key name>. WIN32 error <error code> (<error code hex>): <error text>This error will also contain the OS specific error description. If resolution is not obvious from the error description then contact TIBCO Support for assistance.RegQueryValueEx failed for key <key name> entry <entry name>. WIN32 error <error code> (<error code hex>): <error text>This error will also contain the OS specific error description. If resolution is not obvious from the error description then contact TIBCO Support for assistance.RegEnumValue failed for key <key name>. WIN32 error <error code> (<error code hex>): <error text>This error will also contain the OS specific error description. If resolution is not obvious from the error description then contact TIBCO Support for assistance.This error will also contain the OS specific error description. If resolution is not obvious from the error description then contact TIBCO Support for assistance.RegCreateKeyEx failed for key <key name>. WIN32 error <error code> (<error code hex>): <error text>This error will also contain the OS specific error description. If resolution is not obvious from the error description then contact TIBCO Support for assistance.RegSetValueEx failed for key <key name> entry <entry name> value <value>. WIN32 error <error code> (<error code hex>): <error text>This error will also contain the OS specific error description. If resolution is not obvious from the error description then contact TIBCO Support for assistance.RegSetValueEx failed for key <key name> entry <entry name> value <value>. WIN32 error <error code> (<error code hex>): <error text>This error will also contain the OS specific error description. If resolution is not obvious from the error description then contact TIBCO Support for assistance.Registry microagent value specified is not the specified type. Check actual registry entry for correct data type.An invalid system root key was specified. See TIBCO Hawk Microagent Reference for correct system key values.RegFlushKey failed for key <key name>. WIN32 error <error code> (<error code hex>): <error text>This error will also contain the OS specific error description. If resolution is not obvious from the error description then contact TIBCO Support for assistance.RegCloseKey failed for key <key name>. WIN32 error <error code> (<error code hex>): <error text>This error will also contain the OS specific error description. If resolution is not obvious from the error description then contact TIBCO Support for assistance.This error will also contain the OS specific error description. If resolution is not obvious from the error description then contact TIBCO Support for assistance.OpenEventLog failed for <event log name> event log. WIN32 error <error code> (<error code hex>): <error text>This error will also contain the OS specific error description. If resolution is not obvious from the error description then contact TIBCO Support for assistance.beginthread failed for <event log name> event log monitoring thread. System reports error <error number> <error text>.This error will also contain the OS specific error description. If resolution is not obvious from the error description then contact TIBCO Support for assistance.RegOpenKeyEx failed for key "<key name>". WIN32 error <error code> (<error code hex>): <error text>This error will also contain the OS specific error description. If resolution is not obvious from the error description then contact TIBCO Support for assistance.RegQueryValueEx failed for value "<value name>" under key "<key name>". WIN32 error <error code> (<error code hex>): <error text>This error will also contain the OS specific error description. If resolution is not obvious from the error description then contact TIBCO Support for assistance.RegCloseKey failed for key "<key name>". WIN32 error <error code> (<error code hex>): <error text>This error will also contain the OS specific error description. If resolution is not obvious from the error description then contact TIBCO Support for assistance.This error will also contain the OS specific error description. If resolution is not obvious from the error description then contact TIBCO Support for assistance.LoadLibraryEx failed for library "<library name>". WIN32 error <error code> (<error code hex>): <error text>This error will also contain the OS specific error description. If resolution is not obvious from the error description then contact TIBCO Support for assistance.FormatMessage failed for event <event ID> of event source "<source name>". WIN32 error <error code> (<error code hex>): <error text>This error will also contain the OS specific error description. If resolution is not obvious from the error description then contact TIBCO Support for assistance.Message file name of event source "<source name>" exceeds maximum size of <maximum size> characters.RegisterEventSource failed for event source "<source name>". WIN32 error <error code> (<error code hex>): <error text>This error will also contain the OS specific error description. If resolution is not obvious from the error description then contact TIBCO Support for assistance.ReportServiceEvent failed for event source "<source name>". WIN32 error <error code> (<error code hex>): <error text>This error will also contain the OS specific error description. If resolution is not obvious from the error description then contact TIBCO Support for assistance.DeregisterEventSource failed for event source "<source name>". WIN32 error <error code> (<error code hex>): <error text>This error will also contain the OS specific error description. If resolution is not obvious from the error description then contact TIBCO Support for assistance.Due to extreme system load the EventLog microagent was unable to process new event log entries before they were discarded. This error is sent as an unsolicited message in order for rulebases to respond to this loss of events.A single event log entry exceeded the maximum size and was skipped. This error is sent as an unsolicited message in order for rulebases to respond to this skipped event.The dedicated processing thread encountered an unrecoverable error and has shutdown. This error is sent as an unsolicited message in order for rulebases to respond to this thread shutdown.Failed to get description for event <record number> in source "<source name>". Error <error number> <error text>.This error will also contain the OS specific error description. If resolution is not obvious from the error description then contact TIBCO Support for assistance.This error will also contain the OS specific error description. If resolution is not obvious from the error description then contact TIBCO Support for assistance.The EventLog microagent in the HMA attempts to reopen a Microsoft Windows event log should its existing event log handle become invalid. This can happen if the event log is manually cleared from the Microsoft Windows Event Viewer for example. The microagent makes three (3) attempts to reopen the event log. If all three retries fail this error message is logged and also sent as an unsolicted message to the associated Hawk Agent. The event log monitoring thread is then terminated. This error indicates a serious problem with the Windows Event Log facility. If the Microsoft Windows Event Viewer does not provide a reason for this failure then contact TIBCO Support for assistance.This error will also contain the OS specific error description. If resolution is not obvious from the error description then contact TIBCO Support for assistance.The <event log name> event log has changed (e.g. cleared) between read operations. Possible loss of events. Re-opening event log.This message is logged and sent as an unsolicted message to the associated Hawk Agent whenever the EventLog microagent detects that a Microsoft Windows event log has been modified by another application. The most common occurrence of this is when an event log is manually cleared via the Microsoft Windows Event Viewer. When the event log is cleared it is impossible for the microagent to get any deleted events beyond the ones it has already read so that events may have been lost. When monitoring a Microsoft Windows event log your rulebase should subscribe to the EventLog:: _onUnsolicitedMsg method so it will receive notification of this condition.This message is logged and sent as an unsolicted message to the associated Hawk Agent whenever the EventLog microagent fails in all attempts to resynchronize with the Microsoft Windows Event Log after an overrun condition. Under extreme load the EventLog microagent may not be able to process new event log events before they are aged out (deleted). When an overrun is detected the EventLog microagent logs and sends an unsolicted message to the associated Hawk Agent indicating the condition and the count of lost events. It then attempts to resynchronize (catch-up) with the event log. When monitoring a Microsoft Windows event log your rulebase should subscribe to the EventLog:: _onUnsolicitedMsg method so it will receive notification of this condition.Event category specified, <event category number>, is invalid. Category value must be between 0 and 65535 inclusive.Can not determine current working directory from system property user.dir Please specify config path.Make sure that the specified configuration path is readable and it contains TIBCO Hawk configuration filesAn internal error occurred while waiting to read the output from the executed command. Contact TIBCO SupportDuplicate ami_rvd_transport parameters. Ignoring ami_rvd_transport <service> <network> <daemon>The rvd_transport and ami_rvd(s)_transport parameters match. Ignoring ami_rvd(s)_transport <service> <network> <daemon>Make sure that the number of parameters following -ems_transport option are either one or three.Agent will try to connect to the server again. The number of attempts and the interval between attempts to connect can be changed by adding the following Java system propertieswhere n is number of attempts (default value is 1800) , andInitialization of -repository_dir failed: <COM.TIBCO.hawk.agent.source.SourceException>COM.TIBCO.hawk.microagent.Repository: Failed to load rulebase <rulebase name>. Exception: <SourceException>COM.TIBCO.hawk.microagent.Repository: Failed to load rulebase <rulebase name>. Exception: <SourceTimeoutException>COM.TIBCO.hawk.microagent.Repository: Failed to load rulebase <rulebase name>. Exception: <SourceException>COM.TIBCO.hawk.microagent.Repository: Failed to load rulebase <rulebase name>. Exception: <SourceTimeoutException>COM.TIBCO.hawk.microagent.Repository: Failed to load schedules. Exception: <SourceTimeoutException>COM.TIBCO.hawk.microagent.Repository: Failed to load rulebase map <rulebase map name>. Exception: <SourceException>COM.TIBCO.hawk.microagent.Repository: Failed to load rulebase map <rulebase map name>. Exception: <SourceTimeoutException>COM.TIBCO.hawk.microagent.Repository: Failed to load rulebase map <rulebase map name>. Exception: <SourceException>COM.TIBCO.hawk.microagent.Repository: Failed to load rulebase map <rulebase map name>. Exception: <SourceTimeoutException>COM.TIBCO.hawk.microagent.Repository: Failed to start request listener. Exception: TibrvException <>COM.TIBCO.hawk.microagent.Repository: Fatal error: Duplicate repository(<name>) detected.COM.TIBCO.hawk.microagent.Repository: Failed to retrieve rulebase <rulebase name>. Exception: <SourceException>COM.TIBCO.hawk.microagent.Repository: Failed to retrieve rulebase <rulebase name>. Exception: <SourceTimeoutException>This internal error occurred while adding (or updating) a rulebase in the repository. Contact TIBCO SupportThis internal error occurred while adding (or updating) a rulebase in the repository. Contact TIBCO SupportMake sure the file TIBCrypt.jar is present in the EMS client directory and jce.jar is present in JRE lib directory.Make sure that the "patternfile" argument specified to "onNewLineWithPatternFile" method is correct and the file contains at least one valid Perl5 patternAn internal error occurred while trying to read additional data from the logfile being monitored. Contact TIBCO SupportAn internal error occurred while trying to close the logfile being monitored. Contact TIBCO SupportAn internal error occurred while waiting to read the output from the executed command. Contact TIBCO SupportData is being produced at a rate faster than the rule can process it. Usually due to a temporarily overloaded machine. Contact TIBCO Support if this error persists.A valid data source does not exist for the rule. Instantiate a valid data source or modify the rulebase to use available data sources.Rule datasource error for rule <path> exception: <COM.TIBCO.hawk.talon.MicroAgentException>Invalid arguments for Scheduler.deregister(), node:<node>, scheduleName:<scheduleName>In Scheduler.evaluateSchedules() - node <node> threw exception <exception> in response to inSchedule() call. Deregistering node from scheduler.");Unable to purge config_file from local cache. If resolution is not obvious from the error description then contact TIBCO Support for assistance.Unable to examine config_source inventory. If resolution is not obvious from the error description then contact TIBCO Support for assistance.Unable to purge config_source inventory cache. If resolution is not obvious from the error description then contact TIBCO Support for assistance.Unable to examine config_source inventory. If resolution is not obvious from the error description then contact TIBCO Support for assistance.Unable to purge config_source inventory cache. If resolution is not obvious from the error description then contact TIBCO Support for assistance.Unable to examine config_source inventory. If resolution is not obvious from the error description then contact TIBCO Support for assistance.Corrupt rulebase <rulebase name> from <config source>, name of the rulebase does not correspond to the name of config object.Unable to load named rulebase from named config_source. Check configuration according to exception or contact TIBCO Support.Error loading <config object name> from <config source>, <SourceTimeoutException>Corrupt rulebase <rulebase name> from <config source>, name of the rulebase does not correspond to the name of config object.Unable to load named rulebase from named config_source. Check configuration according to exception or contact TIBCO Support.Config object is of incorrect type: <name>, expected COM.TIBCO.hawk.config.rbengine.rulebase.RulebaseloadRuleBase() may not be invoked when agent is in auto-config mode. Use loadRuleBaseFromFile() instead.The loadRuleBase() method of the RBEngineMicroAgent was used under conditions when it is not permitted. Use the loadRuleBaseFromFile() method instead.Corrupt rulebase <rulebase name> from <config source>, name of the rulebase does not correspond to the name of config object.Unable to deliver email. Check email server or sendMail method invocation as per exception or contact TIBCO Support.Arbitrable node <node> threw exception <exception> in response to wonArbitration() call. Deregistering node from Arbiter.Arbitrable node <node> threw exception <exception> in response to wonArbitration() call. Queued for deregistration from Arbiter.Unchecked exception thrown in SubscriptionMultiplexer thread while processing SubscribeEvent for sub: <subscription>, microagent:<id>, exception: <exception>Unchecked exception thrown in SubscriptionMultiplexer thread while calling onSubscriptionError() for handler: <subscription>, microagent:<id>, exception: <exception>Unchecked exception thrown in SubscriptionMultiplexer thread by method Subscription.cancel() for sub: <subscription>, microagent:<id>, exception: <exception>Unchecked exception thrown in SubscriptionMultiplexer thread while processing MAAddedEvent for sub: <subscription>, microagent:<id>, exception: <exception>Unchecked exception thrown in SubscriptionMultiplexer thread while calling onSubscriptionError() for handler: <subscription>, microagent:<id>, exception: <exception>RemoteAccessServer dispatch thread caught exception: <com.tibco.rv.TibrvException>RemoteAccessServer processRequest thread caught exception: <java.lang.Throwable>RemoteAccessServer.processRequest(), request type= <type> <java.lang.Throwable>RemoteAccessServer dispatch thread was interrupted: <java.io.InterruptedException>RBMap::toXML() - Unable to write to output stream.\n Exception: <java.io.IOException>MicroAgentDescriptorReader - Unable to read DataDescriptor.\n Exception: <java.lang.Exception><COM.TIBCO.hawk.console.hawkeye.WarningExceptionEvent.getConsoleWarning().getMessage()>An error occurred while locating container when moving a container. Verify that the name of the container to be moved is valid.An error occurred while reading the specified variables file. If the resolution is not obvious from the exception description then contact TIBCO Support.An error occurred while reading the specified variables file. If the resolution is not obvious from the exception description then contact TIBCO Support.An error occurred while reading the specified variables file. If the resolution is not obvious from the exception description then contact TIBCO Support.An error occurred while reading the specified variables file. If the resolution is not obvious from the exception description then contact TIBCO Support.Make sure that the variable’s file is readable, it contains at least one valid variable and is in the proper Java properties formatAn error occurred while reading the specified display file. This message is followed by a message with detail reason for the failure.An error occurred while opening a display file. If the resolution is not obvious from the exception description then contact TIBCO Support.Unable to initialize TIBCO Hawk Display : <COM.TIBCO.hawk.console.hawkeye.ConsoleInitializationException>An error occurred while initializing TIBCO Hawk Display. If the resolution is not obvious from the exception description then contact TIBCO Support for assistance.An error occurred while initializing TIBCO Hawk Display. If the resolution is not obvious from the exception description then contact TIBCO Support for assistance.Unable to reinitialize TIBCO Hawk Display : <COM.TIBCO.hawk.console.hawkeye.ConsoleInitializationException>An error occurred while reinitializing TIBCO Hawk Display. If the resolution is not obvious from the exception description then contact TIBCO Support for assistance.An error occurred while reinitializing TIBCO Hawk Display. If the resolution is not obvious from the exception description then contact TIBCO Support for assistance.The specified key is not found in the HawkGui.properties file. The HawkGui.properties may be corrupted or of invalid version. Verify that the version HawkGui.properties is supported.The specified key is not found in the HawkGui.properties file. The HawkGui.properties may be corrupted or of invalid version. Verify that the version HawkGui.properties is supported.The default container Discovered is not found in the Display. A default Discovered will be created. Retry the operation. If the error persist, contact TIBCO Support.Multiple rulebases with the specified name is found on different agents. Some of the rulebases may be out of date. Replace out of date rulebases with the most up to date version.TIBCO Hawk Display is unable to open the specified display file. If the resolution is not obvious from the exception description then contact TIBCO Support.Unable to open display file: <file name> - Error <java.io.StreamCorruptedException>TIBCO Hawk Display is unable to open the specified display file. If the resolution is not obvious from the exception description then contact TIBCO Support.TIBCO Hawk Display is unable to open the specified display file. If the resolution is not obvious from the exception description then contact TIBCO Support.The properties file is of different version. Check or re-install Hawk to ensure that HawkGui.properties and Display are of the same version.The HawkGui.properties file is not found in the resource directory. Check or re-install Hawk to ensure that HawkGui.properties is at the proper location.The image directory is not found. Check or re-install Hawk to ensure that HawkGui.properties is at the proper location.Unable to send config object. - Error <COM.TIBCO.hawk.talon.MicroAgentException>An error occurred while sending rulebases or schedule to multiple agent. If the resolution is not obvious from the exception description then contact TIBCO Support for assistance.ERROR: building method invocation while performing network query/action: <exception message>An error occurred while performing network query/action. The exception message should provide more details about the error.An error occurred while performing network query/action. The exception message should provide more details about the error.An error occurred while performing network query/action. The exception message should provide more details about the error.Unable to retrieve Micro Agents from - <hostname>. - Error: <java.lang.Exception>An error occurred while performing network query/action. The exception message should provide more details about the error.Failed to invoke java command: <toolCommand>; Exception - <java.lang.Exception>An error occurred while invoking the specified tool command. This message is followed by a message that displays an exception that describes the error. Verify that the Java class specified is valid and the classpath for the class is included in CLASSPATH.An error occurred while loading resource such as an icon. Verify that the resource’s path is valid.An error occurred while saving preferences to the resource file. The path of the file may be invalid or the file may have read-only access.Failed to invoke java command: <toolCommand>; Exception - <java.lang.Exception>An error occurred while invoking the specified tool command. This message is followed by a message that displays an exception that describes the error. Verify that the Java class specified is valid and the classpath for the class is included in CLASSPATH.An error occurred when loading the class specified for the menu command. Hawk may not have access to the definition of the class because the class is a public class. The message is followed by a message that indicates the Java class in error.An error occurred when loading the class specified for the menu command. Hawk may not have access to the definition of the class because the class is a public class. The message is followed by a message that indicates the Java class in error.An exception is thrown by the main or the constructor of the class specified for the menu command. The message is followed by a message that indicates the Java class in error.An error occurred during static initialization of the class specified for the menu command. The message is followed by a message that indicates the Java class in error.A error occurred while saving rulebase to a local file system. If the resolution is not obvious from the exception description then contact TIBCO Support.A error occurred while saving rulebase to a local file system. If the resolution is not obvious from the exception description then contact TIBCO Support.A error occurred while sending the rulebase to the agent. If the resolution is not obvious from the exception description then contact TIBCO Support.Unable to add rulebase - <rulebase name>; Exception: <COM.TIBCO.hawk.talon.MicroAgentException>A error occurred while sending the rulebase to the agent. If the resolution is not obvious from the exception description then contact TIBCO Support.A error occurred while sending the rulebase to the agent. If the resolution is not obvious from the exception description then contact TIBCO Support.Unable to update rulebase - <rulebase name>; Exception: <COM.TIBCO.hawk.talon.MicroAgentException>A error occurred while sending the rulebase to the agent. If the resolution is not obvious from the exception description then contact TIBCO Support.A error occurred while unloading the rulebase from the agent. If the resolution is not obvious from the exception description then contact TIBCO Support.Unable to unload rulebase - <rulebase name>; Exception: <COM.TIBCO.hawk.talon.MicroAgentException>A error occurred while unloading the rulebase from the agent. If the resolution is not obvious from the exception description then contact TIBCO Support.Unable to send rulebase; Exception: <COM.TIBCO.hawk.talon.MicroAgentException>A error occurred while sending the rulebase to the agent. If the resolution is not obvious from the exception description then contact TIBCO Support.Unable to retrieve rulebase <rulebase name> from <agent or repository name>; Exception: <java.lang.Exception>A error occurred while retrieving the rulebase from the agent (or the repository). If the resolution is not obvious from the exception description then contact TIBCO Support.Unable to load Micro Agent Descriptors from - <host name>; Exception - <java.lang.Exception>A error occurred while trying to load microagent descriptors from the agent. If the resolution is not obvious from the exception description then contact TIBCO Support.Unable to clone rulebase for - <rulebase name>; Exception - <java.lang.Exception>Unable to export Micro Agent Descriptors from - <host name>; Exception - <java.lang.Exception>A error occurred while trying to export microagent descriptors to the agent. If the resolution is not obvious from the exception description then contact TIBCO Support.Unable to retrieve Micro Agents from - <agent name>; Exception - <java.lang.Exception>An error occurred while retrieving micro agents from the specified agent. The exception message should provide more details about the error.An error occurred while executing the specified command in the command file for Tekmon support. Verify that the command is a valid command.Unable to retrieve schedules from - <host or repository name>. - Error <java.lang.Exception>An error occurred while retrieving schedules from either the agent or repository. The exception message should provide more details about the error.An error occurred while sending schedules to either the agent or repository. The exception message should provide more details about the error.Specify missing command line options if TIBCO Hawk events needs to be written to file or database.Check the TIBCO Rendezvous session -rvd_session command line option and verify that it is validUnable to create RV session for AMI communication - <com.tibco.tibrv.TibrvException>Check the TIBCO Rendezvous session -ami_rvd_session command line option and verify that it is validJDBC Driver is unable to insert a record for "onAgentAlive" event. <java.sql.SQLException>JDBC Driver is unable to insert a record for "onAgentExpired" event. <java.sql.SQLException>JDBC Driver is unable to insert a record for "onAlert" event. <java.sql.SQLException>JDBC Driver is unable to insert a record for "onClear" event. <java.sql.SQLException>JDBC Driver is unable to insert a record for "onMicroAgentChange" event. <java.sql.SQLException>JDBC Driver is unable to insert a record for "onRulebaseChange" event. <java.sql.SQLException>JDBC Driver is unable to create table "HawkAlertClearInfo". <java.sql.SQLException>
|
|
| Copyright © Cloud Software Group, Inc. All Rights Reserved |