Forums

Problem of account login status Cancel The title field is required!

1. IT Admin

   

   11 posts
   Registered:
   24 Sep 2021
   10 Apr 2022

   Link to this post

   After we log out the portal with Account A and log in with Account B, the account name is still Account A, but it should be Account B.
   
   If we input “tpc.identity” (https://www.crmportalconnector.com/developer-network/documentation/how-tos/general-how-to/how-to-use-the-tpc-identity-object) in browser’s debug console with Account B logged in, the returned result shows the current account is Account A, which is wrong, and refresh does not change the result. After about 5 mins waiting, refresh the page, the account name will change to Account B, and “tpc.identity” shows the correct result.
2. Brady Ward

   

   92 posts
   Registered:
   19 Aug 2021
   11 Apr 2022 in reply to IT Admin

   Link to this post

   Hello IT Admin,
   
   This is actually a known issue and has been addressed in the latest build of The Portal Connector.
   
   6.1.0.124
   6.0.0.167
   5.3.0.212
   
   If you update to one of these builds, you should no longer experience the caching of the identity object.
   
   All the best,
   
   Brady
   TPC Web Developer
3. IT Admin

   

   11 posts
   Registered:
   24 Sep 2021
   11 Apr 2022 in reply to Brady Ward

   Link to this post

   We are using version v6.1.7700.121, but the issue still exists.
4. Brady Ward

   

   92 posts
   Registered:
   19 Aug 2021
   12 Apr 2022 in reply to IT Admin

   Link to this post

   Hello IT Admin,
   
   The latest version of The Portal Connector 6.1 is currently build 124. Our latest releases will only be available via NuGet going forward. The latest 6.1 release on crmportalconnector.com is only build 121.
   
   If you haven't already, you will need to update from legacy package to NuGet to upgrade to the latest build - https://www.crmportalconnector.com/developer-network/documentation/how-tos/mvc-based-widgets/how-to-transition-from-legacy-artifact-folders-to-nuget-packages
   
   Let me know if you have any questions,
   
   Brady
   TPC Web Developer
5. IT Admin

   

   11 posts
   Registered:
   24 Sep 2021
   13 Apr 2022 in reply to Brady Ward

   Link to this post

   Hello Brady,
   
   Thanks for your quick reply!
   
   Following the guide of document - https://www.crmportalconnector.com/developer-network/documentation/how-tos/mvc-based-widgets/how-to-transition-from-legacy-artifact-folders-to-nuget-packages
   
   We checked our Sitefinity’s version (which is 14.0) and TPC’s version (which is 6.1).
   
   We selected the version 6.1.140.124 of TPC in Nuget and started to install.
   The upgrade did proceed for a while, but an error popped up and the upgrade was rolled back.
   
   We used to install TPC this way https://www.crmportalconnector.com/developer-network/documentation/setup-portal-connector/installation/installing-tpc/installing-tpc-on-sitefinity-14 and our TPC works as excepted now.
   
   
6. IT Admin

   

   11 posts
   Registered:
   24 Sep 2021
   05 May 2022

   Link to this post

   Hello Brady,
   
   Recap from my last post, we have encountered issue when select the version 6.1.140.124 of TPC in Nuget and started to install. Do there has any suggestion?
7. Brady Ward

   

   92 posts
   Registered:
   19 Aug 2021
   05 May 2022 in reply to IT Admin

   Link to this post

   Hello IT Admin,
   
   When you say you've encountered an issue, do you mean the same issue as before or do you mean you are having trouble installing the The Portal Connector NuGet package?
   
   All the best,
   
   Brady
   TPC Web Developer
8. IT Admin

   

   11 posts
   Registered:
   24 Sep 2021
   06 May 2022 in reply to Brady Ward

   Link to this post

   Hi Brady,
   
   According to your last suggestion, it is suggest to update from legacy package to NuGet to upgrade to the latest build.
   Reported by our developer, we have encountered an issue when selected and install the version 6.1.140.124 of TPC in Nuget.
   Following message shown during the installation and roll back.
   Adding package "Microsoft SharePointOnline.CSOM 16.1.20211.12000" to folder "C:\XXX\XXX\packages". It said "Install failed. Rolling back...".
   Package "Microsoft SharePointOnline.CSOM 16.1.20211.12000" does not exist in project "Dev"
   Remove package "Microsoft.Owin.FileSystem.3.1.0" from "packages.config"
   Remove package "Microsoft.NETCore.Targets.1.1.3" from "packages.config"
   Remove package "Microsoft.NETCore.Platforms.1.1.1" from "packages.config"
   
   May I know is there has a bugs or we have miss something and cause the issue?
   
   Thanks for your help.
   
9. Brady Ward

   

   92 posts
   Registered:
   19 Aug 2021
   06 May 2022 in reply to IT Admin

   Link to this post

   Hello IT,
   
   No, it is not a bug. Unfortunately the install may not run perfectly the first time as every project and setup is different. What is the output in the console right before the "Install Failed. Rolling back..." message?
   
   One thing you can try (please backup your files before attempting) is deleting the Packages folder, restoring them from Visual Studio and then try a build/rebuild.
   
   All the best,
   
   Brady
   TPC Web Developer
10. IT Admin

    

    11 posts
    Registered:
    24 Sep 2021
    12 May 2022

    Link to this post

    Hello Brady,
    
    Thanks for the information. I have informed our developer to try again and should solved.
    But there have another problem we are facing. Could you please advise if there has any resolution?
    
    We have upgraded the solution version to 14.1.7800.0 and the Portal Connector is v6.1.141.126.
    However, the background management interface for Page keeps loading and we cannot do anything.
    Following error display in browser console.
    
    Uncaught (in promise): n: {"headers":{"normalizedNames":{},"lazyUpdate":null},"status":500,"statusText":"Internal Server Error","url":https://dev.XXXX.com/sf/system/pages/sfproviders?sf_site=4c92c6df-a8df-492f-bd44-258bd023d523,"ok":false,"name":"HttpErrorResponse","message":"Http failure response for https://dev.XXXX.com/sf/system/pages/sfproviders?sf_site=4c92c6df-a8df-492f-bd44-258bd023d523: 500 Internal Server Error","error":{"Message":"An error has occurred."}}
    Error: Uncaught (in promise): n: {"headers":{"normalizedNames":{},"lazyUpdate":null},"status":500,"statusText":"Internal Server Error","url":https://dev.XXXX.com/sf/system/pages/sfproviders?sf_site=4c92c6df-a8df-492f-bd44-258bd023d523,"ok":false,"name":"HttpErrorResponse","message":"Http failure response for https://dev.XXXX.com/sf/system/pages/sfproviders?sf_site=4c92c6df-a8df-492f-bd44-258bd023d523: 500 Internal Server Error","error":{"Message":"An error has occurred."}}
        at E (https://dev.XXXX.com/adminapp/polyfills.4c0ef5ba1df992bb680b.js:2:18288)
        at E (https://dev.XXXX.com/adminapp/polyfills.4c0ef5ba1df992bb680b.js:2:17818)
        at https://dev.XXXX.com/adminapp/polyfills.4c0ef5ba1df992bb680b.js:2:19147
        at e.invokeTask (https://dev.XXXX.com/adminapp/polyfills.4c0ef5ba1df992bb680b.js:2:9089)
        at Object.onInvokeTask (https://dev.XXXX.com/adminapp/vendor.0c509af5fc9e544ae913.js:2:394097)
        at e.invokeTask (https://dev.XXXX.com/adminapp/polyfills.4c0ef5ba1df992bb680b.js:2:9010)
        at t.runTask (https://dev.XXXX.com/adminapp/polyfills.4c0ef5ba1df992bb680b.js:2:4164)
        at y (https://dev.XXXX.com/adminapp/polyfills.4c0ef5ba1df992bb680b.js:2:11429)
        at t.invokeTask [as invoke] (https://dev.XXXX.com/adminapp/polyfills.4c0ef5ba1df992bb680b.js:2:10274)
    at p (https://dev.XXXX.com/adminapp/polyfills.4c0ef5ba1df992bb680b.js:2:22958)
    
    Best regard,
    IT Admin
11. IT Admin

    

    11 posts
    Registered:
    24 Sep 2021
    18 May 2022

    Link to this post

    May I know is there any resolution for the background management interface keep loading issue? Thank you.
12. Brady Ward

    

    92 posts
    Registered:
    19 Aug 2021
    Answered

    20 May 2022 in reply to IT Admin

    Link to this post

    Hey IT,
    
    One thing you can check is under Administration > Settings > Advanced > Feather. Make sure "Disable precompiled views" is NOT checked. If it is, deselect it and save your changes.
    
    I also assume you resolved your other issue with the error message?
    
    All the best,
    
    Brady
    TPC Web Developer
13. IT Admin

    

    11 posts
    Registered:
    24 Sep 2021
    23 May 2022 in reply to Brady Ward

    Link to this post

    Thanks Brady. All the problem should solved.
    
    Best regards,
    IT Admin
14. Khaliq Ur Rehman

    

    2 posts
    Registered:
    31 Jan 2023
    06 Jun 2023

    Link to this post

    Hi, 
    
    Is there any way to programmatically remove tpc.identity cache without upgrading TPC?
15. Rawdon Edghill

    

    76 posts
    Registered:
    16 Dec 2020
    07 Jun 2023

    Link to this post

    Hi Khaliq,
    
    Thank you for your question. 
    
    Is there any particular reason you are trying to remove tpc.identity? This is built into the product. 
    Are you having slow performance issues?
    
    Regards,
    Rawdon
16. Khaliq Ur Rehman

    

    2 posts
    Registered:
    31 Jan 2023
    12 Jun 2023 in reply to Rawdon Edghill

    Link to this post

    I am facing same issue "After we log out the portal with Account A and log in with Account B, the account name is still Account A, but it should be Account B." on the portal connector version 6.0.7600.145
    

    Last modified on 12 Jun 2023 09:06 by Khaliq Ur Rehman
17. Rawdon Edghill

    

    76 posts
    Registered:
    16 Dec 2020
    12 Jun 2023

    Link to this post

    Hi Khaliq,
    
    This was a known issue with the TPC version you are on.
    We have since addressed that issue in a later build of the The Portal Connector.
    
    6.0.0.167
    - Resolved an issue that resulted in the tpc identity object becoming cached.
    
    If you update your TPC build to this version or higher you should no longer experience the caching issue.
    
    Regards,
    Rawdon