Tyler Bus Hooks Service cannot be reached after upgrading it to v2021.1.18

Owned by Knowledge Assistant
Last updated: Jan 23, 2024
1 min read
Description of Issue

Time and Attendance shows the message Workflow Services are not currently available. 

When testing the Tyler Workflow connection, the error messages are:

     Tyler Workflow reports partial required components available

     Tyler Bus Hooks Service cannot be reached

When browsing to the Tyler Bushooks dashboard, the following error is received:

     HTTP Error 500.31 - ANCM Failed to Find Native Dependencies

Time and Attendance Application log shows the following error:

     Error creating or sending REST request to https://FQDN/instance/tylerbushooks/api/Status 500 Internal Server Error

Context

  • Time and Attendance

  • ExecuTime

  • Tyler Workflow

  • TWF

  • Tyler Bushooks

  • Bushooks

  • Bushooks v2021.1.18

Cause

This is caused by not having the required .NET Core 8.0 Runtime Hosting Bundle installed on the Tyler Workflow server

Resolution

*Note: All error messages described in the Description of Issue must be present for this resolution to apply

  1. On the Tyler Workflow Server, open a browser and navigate to https://dotnet.microsoft.com/en-us/download/dotnet/8.0 

  2. Under the latest release, select the Windows Hosting Bundle for ASP.NET Core Runtime 8.0.XX

  3. Let the download start and complete

  4. Select the file from the browser downloads to start the installation

    1. Select the check box for I agree to the license terms and conditions

    2. On the pop up, select Yes

    3. Installation will take place and once completed, it will show Installation Successfully Completed

    4. Select Close

  5. Reboot the server

  6. Login to Time and Attendance and test the Tyler Workflow connection to ensure that the Bushooks error is resolved

Additional Information

After the server is rebooted, logging immediately into the application and testing the connection might still show Tyler Workflow reports partial required components available message.

This is normal as the services have not stood up as quickly as Time and Attendance and testing the connection again will show a successful connection