DavidRa Posted August 3, 2021 Share Posted August 3, 2021 Summary - the web extension never turns blue or black after upgrading the server from 9117 to 9300. Looks like I busted something with the upgrade from build 9117 to 9300. Passwordstate itself is working as expected - it's all still branded / coloured correctly, and it does show up as build 9300. The settings under Adminstration show that the browser extension is enabled for all: But the extension (I'm using version 9117 from the Microsoft Edge store - https://microsoftedge.microsoft.com/addons/detail/pbbamlchainnpdodbeobfpgcpffpclka, on Edge 93.0.961.10 (Official build) dev (64-bit) in case it's relevant) stubbornly refuses to change from red to black even after a reinstall and clicking on the "Confirm" option for the URL. The server error console is empty. Any suggestions? Link to comment Share on other sites More sharing options...
support Posted August 4, 2021 Share Posted August 4, 2021 Hi Dave, Can you please check that your API is working okay - i.e. open the Standard API documentation from under the Help Menu? Or look in IIS, and see if the PasswordstateApps application pool is possibly stopped? Regards Click Studios Link to comment Share on other sites More sharing options...
DavidRa Posted August 4, 2021 Author Share Posted August 4, 2021 The API pool was indeed stopped and the API was returning 503 as a result. Starting it (and moving to a new VM host that wasn't overloaded) has fixed, thank goodness. Link to comment Share on other sites More sharing options...
support Posted August 4, 2021 Share Posted August 4, 2021 Hi David, Would there be any information in the Windows Application Event log as to why it would have been stopped? We've just performed the same upgrade you did above, and the App pool was started for us after the upgrade. Regards Click Studios Link to comment Share on other sites More sharing options...
cjohnston Posted August 4, 2021 Share Posted August 4, 2021 We have done the upgrade to 9300 and our website application pool was still running. However there are two other application pools, the PasswordstateWinAPI and the PasswordstateApps pools. The PasswordstateApps pool had been disabled. Re-enabling that allowed our users to access the extension and have it prefill normally Link to comment Share on other sites More sharing options...
support Posted August 5, 2021 Share Posted August 5, 2021 Hi Guys, We've tested this quite a few times, and all our App Pools are started after the upgrade has completed. We'll continue to do some testing to see if we can replicate the issue. Can you check your Windows Application Event log at around the time of the upgrade, to see if there were any exeptions when trying to start the App Pools? Regards Click Studios Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now