Error: Timeout exceeded during script execution
This error occurs when some powershell scripts take longer time than the mentioned timeout value when Exchange server monitor is added in Powershell mode.
1. Try polling the monitor and check if the error continues to retain.
2. Open PowerShell in administrator mode in the Applications Manager installed machine.
3. Navigate to <AppManager-Home>\working\conf\application\scripts\powershell directory.
4. Run the respective commands for the metrics which is causing the timeout error.
5. Replace hostname, username, and password with that of the reported Exchange server to find the time taken for the execution of each script.
Format:Measure-Command{<command-to-run-script>}Example:Measure-Command{.\E201X_MBX_Tables.ps1 'hostname' 'username' 'password'}
-> Database Statistics:Exchange Server version 2010 and above:
.\E201X_MBX_Tables.ps1 'hostname' 'username' 'password'
Exchange Server version 2007:
.\E2007_MBX_Tablesps1 'hostname' 'username' 'password'-> Top Mailboxes and Inactive Mailbox Users:Applications Manager version 172900 and above:
.\EX_Mailbox_Statistics.ps1 'hostname' 'username' 'password'
Applications Manager version below 172900:
.\EX_Mailboxes.ps1 'hostname' 'username' 'password' 'TopMailboxes,InactiveMailboxes'-> Exchange Queues:Mailbox Role:
.\EX_Mailboxes.ps1 'hostname' 'username' 'password' 'ExchangeQueues'
Non-Mailbox Role:
(Use the Credssp argument if used in the Exchange Server monitor)
.\EX_Queues.ps1 'hostname' 'username' 'password' 'Credssp'
-> Server Component States:
.\E2013_ComponentStates.ps1 'hostname' 'username' 'password'-> Performance Metrics:
Example:
.\EX_CommonCounters.ps1 'hostname' 'username' 'password'Replace <scriptname> with the script file from below list based on version and role.
- Common Counters - EX_CommonCounters.ps1
- Exchange 2019 Mailbox Role - E2019_MBX_Counters.ps1
- Exchange 2019 Edge Transport Role - E2016_EDGE_Counters.ps1
- Exchange 2016 Mailbox Role - E2016_MBX_Counters.ps1
- Exchange 2016 Edge Transport Role - E2016_EDGE_Counters.ps1
- Exchange 2013 Mailbox Role - E2013_MBX_Counters.ps1
- Exchange 2013 Client Access Role - E2013_CAS_Counters.ps1
- Exchange 2013 Edge Role - E2013_EDGE_Counters.ps1
- Exchange 2010 Mailbox Role - E2010_MBX_Counters.ps1
- Exchange 2010 Client Access Role - E2010_CAS_Counters.ps1
- Exchange 2010 Edge/Hub Transport Role - E2010_TRANSPORT_Counters.ps1
- Exchange 2010 Unified Messaging Role - E2010_UM_Counters.ps1
- Exchange 2007 Mailbox Role - E2007_MBX_Counters.ps1
- Exchange 2007 Client Access Role - E2007_CAS_Counters.ps1
- Exchange 2007 Hub Transport Role - E2007_HUB_Counters.ps1
- Exchange 2007 Edge Transport Role - E2007_EDGE_Counters.ps1
- Exchange 2007 Unified Messaging Role - E2007_UM_Counters.ps1
- Exchange 2003 and Below - E2003_Counters.ps1
6. Check the time taken for the script execution and based on that set the Timeout and Polling interval in the Edit monitor page and poll the monitor.
Note: In Settings -> Performance Polling -> Optimize data collection -> Monitor Type as Exchange Server, increase the polling interval for the metrics taking longer time to collect or set to "Never collect data" if it is not required to be monitored.
New to ADSelfService Plus?
Related Articles
Error: Timeout exceeded during script execution - MS Office SharePoint monitor
The "Timeout exceeded during script execution" error usually occurs in the SharePoint Server monitor added in PowerShell mode. Run the below Measure-Command to measure the time taken for the script to be executed or the individual commands to be ...Script Monitor FAQs
Common queries, errors and troubleshooting: 1. To execute scripts other than .bat /.vbs in Windows and .sh / .bash in Linux: It is better to execute the script in the form of a command. Eg. To execute python script, you can use command py ...Steps to resolve APM - .NET Core Agent's `AgentDiagnoser.ps1` PowerShell Script Execution failure due to Digital Signature Error
When attempting to run a APM - .NET Core Agent PowerShell script "AgentDiagnoser.ps1" to generate agent diagnostics, you may encounter an error indicating that the script cannot be loaded because it is not digitally signed. This issue can occur due ...Troubleshooting Server error responses
When encountering the following server error responses—Bad Gateway (502), Service Unavailable (503), and Gateway Timeout (504)—it typically indicates issues with the server hosting the URL. Troubleshooting Review your server's access logs for the 30 ...Data Collection: Troubleshoot data collection issues in Exchange Server monitor
Prerequisites: Ensure that you have met all the prerequisites for the Exchange Server monitor. Refer to the below error scenarios and refer to the respective troubleshooting steps. No data collected for few metrics or all the metrics in Exchange ...