Jump to content
gazhak

Upgrading Passwordstate from v6.3 to v7.0 experiences

Recommended Posts

I want to describe my experience when upgrading Passwordstate from a clean (first time) installation

 

Versions:

 

Current Build: Version 6.3 (Build 6350)     New Build: Version 7.0 (Build 7033)

 

Note: I am running Passwordstate on a server, that is not connected to a domain/AD.

 

I had a fair bit of trouble with this, probably mostly due to the fact I am new to passwordstate, so I thought I would document for any other readers running into the same problem.

 

My issue were primarily with getting the backup working.

 

Here's what I did: 

  • I put in my userinfo and backup path to a shared folder on our server ( i.e. C:\<folder name>\ ) and I put in credentials for an administrator account and hit the "test settings" button. Nothing was happening, and I never got any error message.
  • So I tried starting the upgrade process via the notification in the top of the passwordstate webapp, and I got the following error:  Upgrade error detected - Index was outside the bounds of the array. - Method = StopWindowsServiceButton_Click
 
What I did to solve this was:
  • First change my account name from <account> to .\<account>  (since I'm using a local account and not an AD account)
  • Add permissions for the account "NT services\MSSQLSERVER" account: right click your chosen backup folder, select properties > security tab > hit Edit... button > click Add... > type in NT services\MSSQLSERVER > select MSSQLSERVER from the list > click OK

After completing these two steps, I was able to succesfully test backup settings and get going with the upgrade.

 

 

Regards,
Gazhak

Share this post


Link to post
Share on other sites

Hi Gazhak,

 

Many thanks for the feedback, and hopefully it will help some other customers if they run into the same issue. We might also include the local account details in our documentation as you've done, although it's not really recommended you backup to the same server where Passwordstate is installed - if you have a server crash, potentially your backups will be gone as well.
 

Regards
Click Studios

 

Share this post


Link to post
Share on other sites

Thank you for your reply.

 

I am well aware of the risks that exist when backing up to the same machine, on which Passwordstate is running.

 

We are currently runnning a test setup on a virtual machine, which is backed up in full on another host. So even if we suffer a serious server issue, we will have access to our backup files.

 

This is also the reason we're using a local account. When we go into full production mode with Passwordstate, we might change the account to be more integrated with the rest of our network, but for now we prefer having a standalone installation that is not dependant on an AD server.

 

Again, thanks for your feedback. I felt it was worth documenting my issue and post the solution here for other users also running a simple test environment.

 

Regards,

Gazhak

Share this post


Link to post
Share on other sites

Hi Gazhak,

Yes we understand, and thanks for sharing. From memory we helped another customer setup a similar environment, except they were copying off onto another shared on another workgrouped computer. By using the same .\<account> and password on both computers, the backup also worked fine.

Regards

Mark

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...

×
×
  • Create New...