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 below steps for troubleshooting. Step 1: Check the RUM Agent configuration Real User Monitor requires the RUM Agent to be installed and mapped to the Applications Manager. Refer this help ...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 ...Troubleshooting Bad Request and Internal Server error
When a server responds with a Bad Request (400) or Internal Server Error (500), It typically indicates issues with how the request is being made or processed. The reasons for these errors can vary, but the most common causes are Incorrectly formatted ...Webpage Analyzer - Troubleshooting
Prerequisites: Web Page Accessibility: Ensure the web page monitored is accessible from the machine where the Applications Manager is installed. Proxy Configuration: If a proxy is required to access the URL, ensure that the same proxy settings are ...Troubleshooting Mailbox and Database Statistics Data Collection
In an Exchange Server monitor added in PowerShell mode, if performance metrics are visible but Mailbox and Database Statistics data is not collected, the issue might be that the normal PowerShell session is working fine, but the Exchange PS Session ...