Loading...

Forums

Forums / Bugs & Issues / upgrade from 6.0 to 6.1 CrmParallelConnection - (Get Client)

upgrade from 6.0 to 6.1 CrmParallelConnection - (Get Client)

Feed for this thread
2 posts, 0 answered
  1. Missing user
    Missing user avatar
    14 Oct 2022
    Link to this post
    I'm trying to login on my sitefinity after the upgrade, the failed count is increasing in the database, but my credentials are correct. I noticed an exception in TPC trace.logs, maybe that can be issue.

    {
      "ErrorId": "aba8ea22-ed93-4a15-936b-465d4d0b4eff",
      "Title": "CrmParallelConnection - (Get Client)",
      "Message": "Creating Client with name Default Connection.",
      "StackTrace": null,
      "InnerException": null,
      "ErrorDate": "2022-10-14T16:55:09.5156449-04:00",
      "Level": "CRM",
      "LogType": "Trace",
      "Severity": "None",
      "ErrorPageURL": "http://127.0.0.1/",
      "CultureInfo": "en-US",
      "MachineName": "MOM123456",
      "ErrorSource": "Developer",
      "WindowsIdentity": "AzureAD\\user",
      "Type": "System.Exception",
      "ErrorlineNo": null,
      "InnerMessage": null,
      "Trace": null
    }
  2. Omar S
    Omar S avatar
    52 posts
    Registered:
    04 Jul 2019
    18 Oct 2022 in reply to Missing user
    Link to this post
    To clarify, after an upgrade, you are unable to login? Unfortunately, such an issue would require more details and/or a case to be created to resolve. In order to create a case, email TPC Support at: support@crmportalconnector.com

    You also have the option of attending our Daily Q+A to see if we can resolve the issue within the allotted time.

    The Trace log about parralelconnection has to do with parallel connections you may have set up to the CRM. This issue is not related to logging into the Portal. To see SF errors, you can find the errors under your App_Data folder > Sitefinity > Logs > error.txt 

    TPC Error logs can be found in The Portal Connector configuration under Error Handling side menu > View Error Logs. For your Dev environments, ensure you have the error verbosity set to Developer. The setting can be found in the Error Handling section.
    Last modified on 18 Oct 2022 19:10 by Omar S
2 posts, 0 answered