ID: 109379 |
Message: PATROL Adapter Auto workflow Error - {0}
Explanation: Automated workflow: Monitor Type import failed
User Response: Automated workflow: Unimport any monitor type already imported, and re-create the adapter. |
ID: 109380 |
Message: PATROL Adapter Auto work flow - Error in getting the default value for {0}
Explanation: Automated workflow: Could not fetch the metadata
User Response: Automated workflow: Unimport the monitor type, and reimport. |
ID: 109381 |
Message: PATROL Adapter Auto work flow - Error in getting discovery poll attributes.
Explanation: Automated workflow: Could not get the discovery poll attributes.
User Response: Automated workflow: Edit the PATROL Adapter and provide the attributes, and then trigger autosync. |
ID: 109382 |
Message: PATROL Adapter Auto work flow - Error manipulating the input attributes.
Explanation: Automated workflow: The input required to create the PATROL Adapter is incorrect.
User Response: Automated workflow: Check the credentials that you have entered. |
ID: 109383 |
Message: PATROL Adapter Auto work flow - Adapter Creation failed.
Explanation: Automated workflow: The PATROL Adapter has not been created. This can be due to various factors. Check the log file for the specific error.
User Response: Automated workflow: Manually unimport the monitor types that were imported, and then re-create the adapter. |
ID: 109640 |
Message: PATROL Adapter Auto work flow Monitor import status - {0}
Explanation: Automated workflow: Displays the status of the Patrol Adapter creation.
User Response: Automated workflow: See the log file for the exact status. |
ID: 109641 |
Message: PATROL Adapter Auto work flow - Monitor Types to import - {0}
Explanation: Automated workflow: Displays the list of monitor types to be imported.
User Response: Automated workflow: You can use this list and crosscheck with the database or log files to check whether all the monitor types were imported. |
ID: 109642 |
Message: PATROL Adapter Auto work flow Monitor import status - {0}
Explanation: Automated workflow: This error message indicates the status of the PATROL Adapter creation in general.
User Response: Automated workflow: See the log files for the exact status. |
ID: 360702 |
Message: Error Getting Publication History Headers
Explanation: This error is displayed when communication with the Publishing Server cannot be established.
User Response: Verify whether the Publishing Server is running. |
ID: 360703 |
Message: Error Getting Publication History Details
Explanation: This error is displayed when communication with the Publishing Server cannot be established.
User Response: Verify whether the Publishing Server is running. |
ID: 368526 |
Message: Error Getting Explicit Filter Platform
Explanation: This error is displayed when communication with JServer cannot be established.
User Response: Verify whether JServer is running. |
ID: 368527 |
Message: Error opening property file {0}
Explanation: The specified property file might not exist.
User Response: Check whether the specified property file exists. |
ID: 111465 |
Message: RPMPooledInstancesDataCache::Failed to create db connection.
Explanation: While creating a Resource Pool monitor, a connection to the database could not be established.
User Response: Verify whether the correct database credentials were entered. Restart the database. |
ID: 111467 |
Message: RPMPooledInstancesDataCache::Unable to get initial attribute data for monitor type {0}
Explanation: While creating a Resource Pool monitor, initial attribute data for monitor type could not be obtained.
User Response: Verify whether correct information was entered in the UI when creating a monitor. |
ID: 361141 |
Message : PATROL Adapter Auto work flow - PatrolProxyStatus - {0}
Explanation: Automated workflow: This indicates the PATROL proxy status.
User Response: AWF: Check the log files for the exact status. |
ID: 850001 |
Message: PATROL Adapter Auto work flow - FILTERS FOR MOTYPEID: {0}
Explanation: Automated workflow: This error lists the filters that are currently active.
User Response: Automated workflow: Change the filters by editing the adapter in the admin UI. |
ID: 850002 |
Message: PATROL Adapter Auto work flow - DEVICE_FILTER_INCLUDE for {0} = {1}
Explanation: Automated workflow: This lists the device include filters that are currently active.
User Response: Automated workflow: Change the filters by editing the adapter in the admin UI. |
ID: 850003 |
Message: PATROL Adapter Auto work flow - DEVICE_FILTER_EXCLUDE for {0} = {1}
Explanation: Automated workflow: This lists the device exclude filters that are currently active.
User Response: Automated workflow: Change the filters by editing the adapter in the admin UI. |
ID: 850004 |
Message: PATROL Adapter Auto work flow - INSTANCE_FILTER_INCLUDE for {0} = {1}
Explanation: Automated workflow: This lists the instance include filters that are currently active.
User Response: Automated workflow: Change the filters by editing the adapter in the admin UI. |
ID: 850005 |
Message: PATROL Adapter Auto work flow - INSTANCE_FILTER_EXCLUDE for {0} = {1}
Explanation: Automated workflow: This lists the instance exclude filters that are currently active.
User Response: Automated workflow: Change the filters by editing the adapter in the admin UI. |
Comments