Munis ERP Update Failure on Acquiring Packages or Health Check
- Knowledge Assistant
Tyler Deploy update failed on acquiring packages or the health check failed
Errors:
The step failed: Activity Health Check on the Octopus Server failed with error 'The health check failed. One or more deployment targets were not available.'
A request was sent to a polling endpoint, but the polling endpoint did not collect the request within the allowed time (00:05:00), so the request timed out. Server exception: System.TimeoutException: A request was sent to a polling endpoint, but the polling endpoint did not collect the request within the allowed time (00:05:00), so the request timed out.
Munis ERP
Tyler Deploy
TSM OnPremise
TSM SaaS
These errors can be caused by multiple factors, but ultimately it is a connectivity issue between the Tyler Deploy servers and the client server(s)
On-Premise Clients
Ensure your Target Servers are showing as healthy in Tyler Deploy: How to Check the Health of a Target Server in Tyler Deploy
If a server is reporting as unavailable, restart the Octopus Tentacle service in services.msc on the Target Server.
Run the Check Health option after for the server in Tyler Deploy to ensure it come's back as healthy
Verify the following TCP Firewall Ports are open on your server(s):
Ports 10943 through 10950
Allow 2 way communication between your servers and the following:Â
tylerdeployer.tylerdeploy.com:10943, tylerdeployer2.tylerdeploy.com:10944,
tylerdeployer3.tylerdeploy.com:10945, tylerdeployer4.tylerdeploy.com:10946,Â
tylerdeployer5.tylerdeploy.com:10947, tylerdeployer6.tylerdeploy.com:10948,Â
tylerdeployer7.tylerdeploy.com:10949, tylerdeployer8.tylerdeploy.com:10950
Run the Munis ERP update again
If it continues to fail on this step, try running the updates with the Force Redeploy option enabled
SaaS Clients
Please contact Tyler System Management Support or log a case via the Online Support Client Portal