/
Munis ERP Update Failure on Acquiring Packages or Health Check

Munis ERP Update Failure on Acquiring Packages or Health Check

Description of Issue

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.

Context
  • Munis ERP

  • Tyler Deploy

  • TSM OnPremise

  • TSM SaaS

Cause

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)

Resolution

On-Premise Clients

  1. Check if your Target Server(s) are showing as healthy on the Infrastructure Management page: How to Check the Health of a Target Server in Tyler Deploy

    1. If a server is reporting as unavailable, restart the Octopus Tentacle service in services.msc on the target server(s).

    2. Run the Check Health option after for the target server(s) in Tyler Deploy to verify the connection.

  2. If the health check fails, verify the following TCP Firewall Ports are open on your server(s):

    1. Ports 10943 through 10950

    2. 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

  3. Run the Check Health option again 

  4. Once the health check comes back successful, re-run the Munis ERP update

  5. If it continues to fail on this step, try running the updates with the Force Redeploy option enabled

SaaS Clients

  1. Please contact Tyler System Management Support or log a case via the Online Support Client Portal

 

Related content

Deploy Fails on Deploy Octopus Deployment Tools
Deploy Fails on Deploy Octopus Deployment Tools
More like this
Tyler Deploy Unable to Connect to This Machine
Tyler Deploy Unable to Connect to This Machine
More like this
Prerequisites Check Failed in Tyler Deploy
Prerequisites Check Failed in Tyler Deploy
More like this
Time and Attendance Update Failing on Acquire Packages Step
Time and Attendance Update Failing on Acquire Packages Step
More like this
Tyler Content Manager Update Failing on Acquire Packages Step
Tyler Content Manager Update Failing on Acquire Packages Step
More like this
Tyler Deploy Fails With Unable To Read Data From The Transport Connection Warning
Tyler Deploy Fails With Unable To Read Data From The Transport Connection Warning
More like this