Why am I getting a troubleshooting link with an error message after data collection in AS400/iSeries monitoring?
Reason: This could be due to any error which occurred during data collection for any of the modules (messages / disk / problem / historyLog).
Solution:
1. If the error message shows 'Not authorized ' or 'No authority to...' then it may be due to the user account which is used to monitor the AS400 does not have required authority. Please refer the prerequisites for AS400/iSeries in our help document.
2. If the error message shows 'No active collection' under the disk tab, then it indicates the performance collection service is not started or active.
If the performance collection service is not enabled in AS400/iSeries, you need to start it by executing the command STRPFRCOL or perform the following step in AS400/iSeries console window:
GO PERFORM-->COLLECT PERFORMANCE DATA-->START PERFORMANCE COLLECTION.
You can also execute the STRPFRCOL command from AS400/iSeries server monitor page in Admin --> Non-Interactive command option.
3. If the error message shows '/QSYS.LIB/QMHOLHST.PGM: Object does not exist', under history log tab, it is because the System API used to retrieve history log is NOT available for V5R4 or earlier systems. So for these systems we will monitor the message queue(if the user is interested to monitor) as an alternate which can be specified by adding the key 'am.as400.historylogalternative' in AS400Server.properties file (restart Applications Manager after making changes).
New to ADSelfService Plus?
Related Articles
Real User Monitor (RUM) - Troubleshooting
If the monitor has not polled data for a long time, follow the steps below for troubleshooting: Step 1: Check prerequisites to be done Real User Monitor requires the RUM Agent to be installed and mapped to the Applications Manager. Refer the help ...Troubleshooting Bad Request and Internal Server error
Bad Request & Internal Server error When the server of URL cannot understand the request it has received it responds with a Bad request or a malformed syntax error message. If there is an error in processing the request received by the server, it ...Troubleshooting errors during data collection in Microsoft 365 monitor (For versions upto v16300)
Prerequisites: Ensure that you have met all the prerequisites for the Microsoft 365 monitor. From Applications Manager version 16300 onwards, Microsoft 365 monitor will use Microsoft Graph API as the primary mode of data collection. We have migrated ...Troubleshooting WinRM errors
This KB serves as a guide for troubleshooting errors when using the WinRM mode of data collection. First, ensure that all the following conditions are met: Refer to the below link and check if all the WinRM prerequisites have been completed properly ...Ceph storage monitoring troubleshooting steps
Ceph Storage Monitoring: By default Ceph monitor added via ssh. so ssh should be work if the customer want to monitor the Ceph storage for the server. Supported Ceph Storage Version : >= v0.66 Command used to collected all performance data : ceph -s ...