The latest release of QSDA Pro is v2.2.0 see what’s new Get Started View installation and getting started instructions on the Help site. Stay in Touch Join our mailing list.
Est. reading time: 1 minute
This release includes new optional columns in the resource views, support for https wildcard certificates and several performance enhancements.
See the release notes for a complete list of changes.
https://help.easyqlik.com/qsda/topics/idh-topic1130.htm
After upgrading QS to AUg-2022 IR and PostgreSQL to 12.5 using the Upgrade tool from Qlik and Upgrading the QSDA Pro to 2.2.0, we suddenly see this on the local server on a unlicensed version of QSDA Pro.
We do have other Licensed versions on our own and Client servers, but often Dog-food new version in our sandbox environment.
Has anyone seen this behaviour before? Any suggestions?
We are unsure if this is related to QSDA Pro upgrade or Qlik Sense upgrade.
We have a number of upgrades coming up in the next 2 month, so any clarification would be nice.
Any relevant messages in Admin > Error log?
Try clearing local storage and cookies for the QSDA site.
That is a quick answer
Latest entry from qsda-log
:
2022-09-13 12:07:45.1095 Microsoft.AspNetCore.Hosting.HostingApplicationDiagnostics.LogRequestStarting Info Request starting HTTP/1.1 POST
http://localhost:5000/notifications/negotiate?negotiateVersion=1
- 0
2022-09-13 12:07:45.1095 Microsoft.AspNetCore.Routing.EndpointMiddleware.Invoke Info Executing endpoint ‘/notifications/negotiate’
2022-09-13 12:07:45.1095 Microsoft.AspNetCore.Routing.EndpointMiddleware.Invoke Info Executed endpoint ‘/notifications/negotiate’
2022-09-13 12:07:45.1095 Microsoft.AspNetCore.Hosting.HostingApplicationDiagnostics.LogRequestFinished Info Request finished HTTP/1.1 POST
2022-09-13 12:07:45.1095 Microsoft.AspNetCore.Hosting.HostingApplicationDiagnostics.LogRequestStarting Info Request starting HTTP/1.1 GET
http://localhost:5000/notifications?id=Umpiqnjqr4LqeyYzG1oBsw
- -
2022-09-13 12:07:45.1095 Microsoft.AspNetCore.Routing.EndpointMiddleware.Invoke Info Executing endpoint ‘/notifications’
Latest entry from error-log
:
2022-09-13 11:06:01.3011 Qsda.Shared.Protection.DataProtection.Unprotect Error Error unprotecting value System.Security.Cryptography.CryptographicException: The provided payload cannot be decrypted because it was not protected with this protection provider. For more information go to
at Microsoft.AspNetCore.DataProtection.KeyManagement.KeyRingBasedDataProtector.UnprotectCore(Byte[] protectedData, Boolean allowOperationsOnRevokedKeys, UnprotectStatus& status)
at Microsoft.AspNetCore.DataProtection.KeyManagement.KeyRingBasedDataProtector.Unprotect(Byte[] protectedData)
at Microsoft.AspNetCore.DataProtection.DataProtectionCommonExtensions.Unprotect(IDataProtector protector, String protectedData)
at Qsda.Shared.Protection.DataProtection.Unprotect(String value)
2022-09-13 11:06:01.3690 Microsoft.AspNetCore.Components.Server.Circuits.CircuitHost.ReportUnhandledException Error Unhandled exception in circuit ‘Tvfyc3d3NynTupjsjh6udn-UprpgbtyN95IPFwB3pKE’. System.NullReferenceException: Object reference not set to an instance of an object.
at Qsda.UI.Pages.Analyze.PageApplist..MoveNext()
— End of stack trace from previous location —
at Microsoft.AspNetCore.Components.ComponentBase.CallStateHasChangedOnAsyncCompletion(Task task)
at QsdaUI.Components.ConnectionList..MoveNext()
— End of stack trace from previous location —
at Microsoft.AspNetCore.Components.ComponentBase.RunInitAndSetParametersAsync()
at Microsoft.AspNetCore.Components.RenderTree.Renderer.GetErrorHandledTask(Task taskToHandle, ComponentState owningComponentState)
Same problem with other Browser (Chrome instead of Standard Edge), so should have clear cache.
jcscubed:
Qsda.Shared.Protection.DataProtection.Unprotect Error Error unprotecting value System.Security.Cryptography.CryptographicException: The provided payload cannot be decrypted because it was not protected with this protection provider.
That error means that the connection or config files did not migrate properly, My apologies. I understand you resolved by following the steps at
Error screen after upgrade from QSDA V1 to V2
