Cubes Connection Service Deployment Fails on Step 4

Owned by Knowledge Assistant
Last updated: Jul 27, 2023 by Moriah Yorkey
1 min read
Description of Issue

Cubes Connection Service failing on step 4 when deploying to AWS. What is causing this Cubes Connection Service deployment to fail?

Context

  • Cubes Connection Service

  • Cubes

  • Hub

  • Tyler Deploy

  • EERP

  • AWS

  • Deployment Failure

Cause

During a Cubes Connection Service deployment, the Cubes Connection Service deployment (or sub-deployment of Hub) fails with the error:

Unable to get valid response from SSL host header https://<CRM_Custom_ID>tylerapp.tylerhost.net!
Exception calling "GetResponse" with "0" argument(s): "The remote server returned an error: (403) Forbidden.
Unable to get valid response from non-SSL host header http://<CRM_Custom_ID>tylerapp.tylerhost.net!
Exception calling "GetResponse" with "0" argument(s): "The remote server returned an error: (403) Forbidden.

***************************
Summary for Verify Deployment
Deployment Target: SaaSAWS.CPMU<Pod_ID>SAPAP 
INVALID Host Header: <CRM_Custom_ID>.tylerhost.net
VALID Disk Space: D:\
***************************

Resolution

Contact TSM support for resolution.

Additional Information

Â