SCCM Upgrade from 2207 to 2309 Prerequisite check failing

We would like to upgrade our SCCM environment from 2207 to 2309. So, we ran the Prerequisite check.  But, it refuses to complete.  In the ConfigMgrPrereq.log we are seeing:
*** Failed to connect to the SQL Server, connection type: SMS ACCESS.
ERROR: Failed to connect to SQL Server to check application catalog roles
PXDRS10SCCMPS01.Corporate.Providence.com; Application catalog roles are unsupported; Warning; The application catalog website point and application catalog web service point site system roles are unsupported. One or both of these roles are detected at this site. Users now have the same experience with Software Center. If you have any tools that communicate with application catalog services, update them to use the management point. For more information, see https://go.microsoft.com/fwlink/?linkid=2166027. NOTE: we removed the application catalog website point and application catalog web service point from the primary server, but the error continues.
*** [08001][-2146893022][Microsoft][ODBC Driver 18 for SQL Server]SSL Provider: The target principal name is incorrect.
*** [08001][-2146893022][Microsoft][ODBC Driver 18 for SQL Server]Client unable to establish connection

Steps we have tried:
We have confirmed that we can connect to the DB using ODBC Data Sources 64 bit.
We have confirmed that we are connecting to the SQL DB using a PKI Certificate, and this same PKI Certificate is specified in Configuration Manager.

In the SMSProv.log file we found:
Execute SQL =select distinct SMS_ConfigurationPolicy.CI_ID,SMS_ConfigurationPolicy.LocaleID,SMS_ConfigurationPolicy.ActivatedCount,SMS_ConfigurationPolicy.ApplicabilityCondition,SMS_ConfigurationPolicy.AssignedCount,SMS_ConfigurationPolicy.CI_ID,SMS_ConfigurationPolicy.CI_UniqueID,SMS_ConfigurationPolicy.CIType_ID,SMS_ConfigurationPolicy.CIVersion,SMS_ConfigurationPolicy.ComplianceCount,SMS_ConfigurationPolicy.CompliantPercentage,SMS_ConfigurationPolicy.ConfigurationFlags,SMS_ConfigurationPolicy.CreatedBy,SMS_ConfigurationPolicy.DateCreated,SMS_ConfigurationPolicy.DateLastModified,SMS_ConfigurationPolicy.EffectiveDate,SMS_ConfigurationPolicy.EULAAccepted,SMS_ConfigurationPolicy.EULAExists,SMS_ConfigurationPolicy.EULASignoffDate,SMS_ConfigurationPolicy.EULASignoffUser,SMS_ConfigurationPolicy.IsUserCI,SMS_ConfigurationPolicy.FailureCount,SMS_ConfigurationPolicy.IsAssigned,SMS_ConfigurationPolicy.IsBroken,SMS_ConfigurationPolicy.IsBundle,SMS_ConfigurationPolicy.IsEnabled,SMS_ConfigurationPolicy.IsExpired,SMS_ConfigurationPolicy.IsHidden,SMS_ConfigurationPolicy.IsLatest,SMS_ConfigurationPolicy.IsQuarantined,SMS_ConfigurationPolicy.IsSuperseded,SMS_ConfigurationPolicy.IsUserDefined,SMS_ConfigurationPolicy.IsVersionCompatible,SMS_ConfigurationPolicy.LastModifiedBy,SMS_ConfigurationPolicy.Description,SMS_ConfigurationPolicy.DisplayName,SMS_ConfigurationPolicy.CIInformativeURL,SMS_ConfigurationPolicy.LocaleID,SMS_ConfigurationPolicy.ModelID,SMS_ConfigurationPolicy.ModelName,SMS_ConfigurationPolicy.NonComplianceCount,SMS_ConfigurationPolicy.PermittedUses,SMS_ConfigurationPolicy.PlatformType,SMS_ConfigurationPolicy.Precedence,SMS_ConfigurationPolicy.SDMPackageVersion,SMS_ConfigurationPolicy.SedoObjectVersion,SMS_ConfigurationPolicy.Severity,SMS_ConfigurationPolicy.SourceSite from fn_ListConfigurationPolicy_List(1033) AS SMS_ConfigurationPolicy LEFT OUTER JOIN v_CICategories AS __rationPolicyv_CICategories0 ON SMS_ConfigurationPolicy.CI_ID = __rationPolicyv_CICategories0.CI_ID where __rationPolicyv_CICategories0.CategoryInstance_UniqueID = N'SettingsAndPolicy:SMS_CoManagementSettings' OPTION(USE HINT('FORCE_LEGACY_CARDINALITY_ESTIMATION'))

Our SQL Admin is scratching his head and says the same methods we used for SCCM have fixed issues connecting to other SQL DB's via SSL.
How can we get the 2309 Prerequisite Check to play nice, do you have some suggestions for us, or are there any workarounds?  I'd be happy to provide any info needed to help resolve this issue.  Thank you!
Sincerely, Richard Roati