If you receive the error "Sorry! We're having trouble processing your request right now. Please try again in a few minutes" while accessing the ECP console.
To fix the ECP issue, follow the below steps
1. Check the connection statistics in Exchange
2. Stop the services HpExMon and HpExMonWD and set it as manual. This will disable the server from LB.
3. Check the connection statistics in Exchange again there shouldn t be any new connections to the server.
4. Stop IISadmin and W3SVC (World Wide Web Publishing Service)
5. Go to "C:\Windows\Microsoft.NET\Framework64\v2.0.50727\Temporary ASP.NET Files" and rename ECP directory to "ECP-old"
6. Start IISadmin and W3SVC (World Wide Web Publishing Service)
6. test whether issue persists or not. If the issue persists go to step 9.
7. If the issue is resolved, start HpExMon and HpExMonWD services and set it as automatic. This will enable the server LB.
8. Check the connection statistics in Exchange and make sure the server is accepting the sessions. This ends the troubleshooting.
9. Remove the ECP virtual directory using the following command, Remove-EcpVirtualDirectory -Identity "EXCHTESTSVR\ecp (default Web site)"
10. Create new ECP virtual directory using , New-EcpVirtualDirectory -externalurl "https://webmail.domain.com/ecp" -internalurl "https://webmail.domain.com/ecp" -Server "EXCHTESTSVR"
11.Restart IIS and verify the ECP functionality
12. Start HpExMon and HpExMonWD services and set it as automatic. This will enable the server LB.
13. Check the connection statistics in Exchange and make sure the server is accepting the sessions. This ends the troubleshooting.
To fix the ECP issue, follow the below steps
1. Check the connection statistics in Exchange
2. Stop the services HpExMon and HpExMonWD and set it as manual. This will disable the server from LB.
3. Check the connection statistics in Exchange again there shouldn t be any new connections to the server.
4. Stop IISadmin and W3SVC (World Wide Web Publishing Service)
5. Go to "C:\Windows\Microsoft.NET\Framework64\v2.0.50727\Temporary ASP.NET Files" and rename ECP directory to "ECP-old"
6. Start IISadmin and W3SVC (World Wide Web Publishing Service)
6. test whether issue persists or not. If the issue persists go to step 9.
7. If the issue is resolved, start HpExMon and HpExMonWD services and set it as automatic. This will enable the server LB.
8. Check the connection statistics in Exchange and make sure the server is accepting the sessions. This ends the troubleshooting.
9. Remove the ECP virtual directory using the following command, Remove-EcpVirtualDirectory -Identity "EXCHTESTSVR\ecp (default Web site)"
10. Create new ECP virtual directory using , New-EcpVirtualDirectory -externalurl "https://webmail.domain.com/ecp" -internalurl "https://webmail.domain.com/ecp" -Server "EXCHTESTSVR"
11.Restart IIS and verify the ECP functionality
12. Start HpExMon and HpExMonWD services and set it as automatic. This will enable the server LB.
13. Check the connection statistics in Exchange and make sure the server is accepting the sessions. This ends the troubleshooting.
Worked like a charm. Been fighting this issue for a while and these instructions were the simplest to follow and included all the steps beyond removing the temp files. Thank you!
ReplyDeletewhat "HpExMon & HpExMonWD" ? thank you
ReplyDelete