Alan Posted March 2, 2021 Share Posted March 2, 2021 On Build 9050. Getting the same generic error when trying to perform either action (below). Nothing is logged to the Error Console or the SQL Query. "Unfortunately an error has occurred within the Passwordstate web site, for which we apologize for the inconvenience. If Passwordstate is able to communicate with the database, then the error will be logged on the screen Administration -> Passwordstate Administration -> Error Console. If you are unable to view the Error Console screen for any reason, you can ask your Database Administrator to run the following SQL Query, which will show the same data from the Error Console Screen: USE Passwordstate SELECT * FROM DebugInfo" Link to comment Share on other sites More sharing options...
support Posted March 2, 2021 Share Posted March 2, 2021 Hi Alan, Unforortunately we cannot reproduce this issue with version 9 or 8. Do you know if you have done any server hardneing on your web server, as one customer previously reported this error when they performed this? Regards Click Studios Link to comment Share on other sites More sharing options...
Alan Posted March 2, 2021 Author Share Posted March 2, 2021 We've encrypted the Database Connection and appSettings as recommended in the Passwordstate installation manual. The only other "hardening" we've done is to apply the "Best Practice" settings of the Nartac IIS Crypto utility. It's my understanding this just sets which protocols, ciphers, etc. are enabled for IIS and also sets the cipher suite order. The Passwordstate site is the only application installed and in use by IIS on this server. We are using SAML2 authentication against our AzureAD instance. Both functions were working on v8995 prior to upgrading to v9050. Link to comment Share on other sites More sharing options...
support Posted March 2, 2021 Share Posted March 2, 2021 Okay, thanks Alan. We'll see if we can try and replicate this in a few different environments. Regards Click Studios Link to comment Share on other sites More sharing options...
support Posted March 3, 2021 Share Posted March 3, 2021 Hi Alan, Could you try the following for us? In the following document, follow section '5. Manual Upgrade Instructions' to replace all the files a second time - https://www.clickstudios.com.au/downloads/version9/Upgrade_Instructions.pdf Does this help at all? Regards Click Studios Link to comment Share on other sites More sharing options...
Jake Posted March 3, 2021 Share Posted March 3, 2021 I'm seeing this error as well. Link to comment Share on other sites More sharing options...
Alan Posted March 3, 2021 Author Share Posted March 3, 2021 Yes. After following the steps in Section 5 both tasks are working now. Thanks for your help! Link to comment Share on other sites More sharing options...
KC_BREC Posted March 3, 2021 Share Posted March 3, 2021 Confirming that we see the same error(s_) as well after performing the upgrade via the administrator interface. Also confirming that after running the offline manual upgrade as mentioned above the errors are no longer present. It would appear to me that something is missing from online upgrade process. Link to comment Share on other sites More sharing options...
Fabian Näf Posted March 4, 2021 Share Posted March 4, 2021 I'm also experience this issue. My upgrade to version 9 was not so smooth. After using the inplace upgrade I got a "SQLite assembly could be loaded" errors in the event viewer and Passworstate was not running. Then I did a manual upgrade by using the upgrade tool (chapter 5 in the manual) with PasswordstateManualUpgrade.exe. I also had to install PowerShell 5 for this step, which could have been the issue with the initial inplace upgrade. => So I also did a manual upgrade and I'm still having this issue. Link to comment Share on other sites More sharing options...
support Posted March 4, 2021 Share Posted March 4, 2021 Hi Guys, We do not see this issue in any of our environments, so we're going to have to do some digging to see if we can somehow reproduce the issue, and then provide a fix for it. Fabian, did you also run the Health Check Utility after the upgrade completed - it mentions this as a requirement on the post upgrade screen? Thanks Click Studios Link to comment Share on other sites More sharing options...
Fabian Näf Posted March 5, 2021 Share Posted March 5, 2021 Yes I did. The Health Check Utility stated that everything's fine. Link to comment Share on other sites More sharing options...
Adam-Equinox Posted March 15, 2021 Share Posted March 15, 2021 I was about to post saying that I experienced the same problem but found the below known issue and resolution: Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.