Jump to content

Upgrading from 9117 to 9350


tburke
 Share

Recommended Posts

When running the "upgrade now" after putting PasswordState into Maintenance Mode I was getting this error.  I tried a couple times and got the same error.  It's quite possible somewhere in my companies network security this is being blocked.  Is this download initiated via https protocals, TLS 1.2 or better?  I'm trying to figure out what to bring to our cyber team to work out what might be going on but usually they want some details on how this is happening.  Time frame in case it was on the Clickstudio side was about 20 minutes before posting this msg.

 

The following exception was raised when executing the method DownloadButton_Click() = .An exception occurred during a WebClient request. - at System.Net.WebClient.DownloadFile(Uri address, String fileName) at (Object , String , String ) at Passwordstate.upgrades_step1.DownloadButton_Click(Object sender, EventArgs e)

 

 

On a different network I was trying to do the same update from version 9117 to the latest, and on that one it would download the update...but only 18k of it and it would always say the update was corrupted.  

Link to comment
Share on other sites

I was already running version 9117 and that post says maintenance mode not working fixed in 9065.  I'm not really convinced this is a PasswordState issue.  I have a feeling one of our network firewall policies might be restricting the traffic to pull the update down.  However, I need to be very specific with our cyber team in order to allow that access across our internal network.  I'm in the US so I think one blocking point might simply be this is pulling outside the country.  Is there an alias of what the upgrade server name is so I can whitelist it on our firewalls?  Also if it's anything other than using standard https (443) port connection I'll need to specify that as well in my firewall policy request.  Unless there been some other issues on Clickstudio side, I'm guessing this problem is on my side but will need to know how to fix it.

 

The alternative is I can do manual upgrades.  I actually tried this in my test environment by grabbing the latest version and installing over the top of what I had installed.  everything looked ok, it let me do it, first log in I saw the upgrading database part show up.  UI looked updated, saw the new version, most stuff in the Administrator tab looked like it was working but as soon as I click on a password list, I got this error.  Looking at the web.config, looks like my keys are good, I can connect to the DB using SQL manager but I can't see any of my passwordlists.  No big lost, just my test setup but I must have did the manual upgrade incorrectly.

 

This is the error message in the error console:

 

Quote

Build No '9350' - Error Code = Could not load file or assembly 'System.Text.Encoding.CodePages, Version=4.1.3.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040), StackTrace = at AngleSharp.Browser.EncodingMetaHandler..ctor() at AngleSharp.Configuration..ctor(IEnumerable`1 services) at Ganss.XSS.HtmlSanitizer.CreateParser() at Ganss.XSS.HtmlSanitizer.SanitizeDom(String html, String baseUrl) at Ganss.XSS.HtmlSanitizer.Sanitize(String html, String baseUrl, IMarkupFormatter outputFormatter) at (Object , String , String , IMarkupFormatter ) at uRM=.6UY=.6BM=()

 

Link to comment
Share on other sites

Hi tburke,
 
Looking at your forum post again, we think we know what the issue is now. The old In-Place Upgrade method is no longer available, and as of build 9300 our upgrade feature has changed to streamline the process and improve security.  Please follow this new set of instructions to help you get upgraded to the latest build available: https://www.clickstudios.com.au/downloads/version9/Upgrade_Instructions.pdf

 

Before attempting the new upgrade process. Can you please delete the c:\inetpub\passwordstate\upgrades\upgradelog.txt if it exists?

 

The manual uprade method you tried is also no longer supported, because of the way we "can" make changes to the web.config file during the upgrade process. In your web.config file, can you look for the reference to the CodePages above, and change it to the values below:

 

<dependentAssembly>
        <assemblyIdentity name="System.Text.Encoding.CodePages" publicKeyToken="b03f5f7f11d50a3a" culture="neutral" />
        <bindingRedirect oldVersion="0.0.0.0-5.0.0.0" newVersion="5.0.0.0" />
      </dependentAssembly>

Regards

Click Studios

Link to comment
Share on other sites

Fixing the assemblyidentity version numbers worked and got my test setup seeing credentials again.  Thank you!  So in that case, because I wasn't able to download the update through the "upgrade"  button then the way to do the upgrade for the one I have in production is actually to do the same thing which is to download the latest as described in that upgrade instructions pdf and run that installer (which is how I did it here in my test setup).  Then if I run into the same issue update the web.conf.

 

The upgrade in place is the part where in the "backups and upgrade" section there is a "Upgrade Now" option right?  So moving forward, that not going to be there, just wanted to make sure I understood what you where say, just need to update our upgrade processes.

 

One more followup question, I currently use a modified script from Clickstudio "Unattended_Install.ps1" that I jammed into a Chef Cookbook for quick automated deployments of this service for testing, I noticed the links and post to this are no longer here.  I'm guessing this will no longer will work with the latest builds?  I think the script was really only needed because the of the installer itself, in the newer installer, is there a "silent" option to run the install of the latest release?  I would much prefer not running a special unattended wrapper script.  I did't see any unattended install flags in any of the docs I've looked through yet but if there is, I'd love to try it.

Link to comment
Share on other sites

Hi tburke,

 

Yes, as of build 9300, there is no option in the UI to do In-Place Upgrades. You need to use the Windows Installer for this.

 

And that's correct, we no longer provide an unattended install option for our software, as we need to use the Windows Installer now - we no longre provide zip files with all the files, for security reasons.

Regards

Click Studios

Link to comment
Share on other sites

Most windows installers can have parameters passed to make them go through an unattended/silent installation, it's a good thing using the MSI.  I understand though if there some security issues with doing this but I would like to add a request to put in support for an unattended installation as it really saves me allot of time setting up a test system quickly.  Thanks again for all your help.  🙂

Link to comment
Share on other sites

Will do.  If you make a Chocolatey (https://chocolatey.org/) package for it I will be super excited because it would pretty much eliminate my hacky automation solution for bringing up a test environment.  I think Microsoft got OneGet in a stable state and built into PowerShell now so that could be another good automation route.  I'll add it to the feature request, thanks again for all your help, I'm defiantly unstuck with my dev env and a path forward to getting my production system updated. 

Link to comment
Share on other sites

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 account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

×
×
  • Create New...