Jump to content

SGauvin

Members
  • Content Count

    26
  • Joined

  • Last visited

About SGauvin

  • Rank
    Member

Recent Profile Visitors

547 profile views
  1. Hi All, I found a post that mentions how to prevent Chrome from automatically updating a specific extension. It is a little bit of a hack, but would allow you to control WHEN that extension gets upgraded. The solution is to download the desired extension, unzip it and then open the file call "manifest.json". Modify the "update_url" entry to a bogus URL (https://localhost e.g.). Finally manually install the extension by going to "chrome://extensions" (and pointing to the location where your modified version resides). I have followed these steps to install an older version of the PasswordState extension (I found on https://crx.dam.io/) and got Chrome to work with PasswordState version 8765. Hope this helps someone else. Thanks... Scott
  2. The issue of the Build Number being hard-coded to a particular version of PasswordState is frustrating. Unfortunately for me, we have a change-management process (that includes rigorous testing) that takes about 3 months to get any new versions into Production. I just upgraded to 8765 last week! Is there any reason why the Chrome plug-in (extension) itself can't be developed in such a way that it is backwards compatible to support previous version of PasswordState ? Then it wouldn't matter if Google automatically pushes the extension updates automatically or not. p.s. I thought I had read something that mentioned that the plug-in dependency to a particular version of PasswordState was being removed, I must have misinterpreted it. Thanks... Scott
  3. Hi, As an interim solution (until we can upgrade) I'm OK with getting the warning, and have to accept it. Please email me the details. Thanks... Scott
  4. Hi, We also recently upgraded to 8556, and are having issues with the Browser Extensions for IE , Firefox and Chrome. We have users that have downloaded the latest extension, and are now not able to use the plugin. Unfortunately our Change Management process does not afford us to quickly upgrade to 8573 - it will take us at least 3 months to turn-around. Is it possible to get a copy of the -1 version of these Browser Extensions (one that works with 8556), so that I can get these workstation working again? Thanks... Scott
  5. We've recently upgraded to 8.5 (from 7.6) and I have a user that leverages and extensive amount of Folder. When they click on a Folder, they are presented with the following: They would like to suppress the displaying of the "Folder Properties' and 'External Links' blocks. They use the 'Search Passwords in Folder' and would like to extend / stretch the block containing the results - to make them more presentable (some values are quite long). Is it possible to either suppress these blocks, or rearrange the blocks so they are underneath the base Folder block? Thanks... Scott
  6. We recently upgraded to version 8556 (from 7.6) and when attempting to assign the Account-Type on a new password account the custom Account-Types are not showing in the drop-down. I've attached a pdf that contains snapshots supporting this error. I was able to find a couple of workarounds, but would like to know if there is an 'official' solution on how this should be handled? Workaround #1 - When in the Add New Password form, deselect both the 'Enabled for Resets' and 'Enabled for Heartbeat' options next to Managed Account. When this is done, the custom Account-Types are displayed in the drop-down. Workaround #2 - Modify the Password List Template to deselect the 'Enable Password Reset - allows password resetting with other systems'. When this is done the Managed Account line including ‘Enabled for Resets’ and ‘Enabled for Heartbeat’ no longer shows up in the Add New Password form, and the custom Account-Types are displayed in the drop-down. Thanks... Scott Upgrade_SnapshotsShowingCustomAccountType.pdf
  7. SGauvin

    URGENT - upgrading from 7.6 failed

    Hi, I downloaded and ran build 8556 in our lab environment, and it resolved the upgrade issue. Thank you for all your help. Thanks... Scott
  8. SGauvin

    URGENT - upgrading from 7.6 failed

    Unfortunately, as you've experienced with other customers, providing a copy of our database is not an option (even with a NDA). Here are a couple of possible options: 1) Is this something that could be facilitated via a WebEx (or something similar), where your team could access our environment, add the debugging code and execute? In spite of the time difference, I would make myself available 2) As an alternative, provide me with source code with Debugging enabled and I can run it, then provide you with the results. Let me know if either of these would work, or suggest another alternative. p.s. I'm on vacation next week (Dec 10-14), so whatever is decided will have to be executed the week of Dec 17-21 Thanks... Scott
  9. SGauvin

    URGENT - upgrading from 7.6 failed

    Hi Support, I now have an environment that is a replica of production. I attempted the -upgrade- and it failed in the identical spot: 2018-12-05 11:50:42 AM - Build 7721 - Step 2 Completed Successfully. 2018-12-05 11:50:46 AM - Build Process 'Build_7721_CopyPassword()' failed with the following error - Thread+was+being+aborted. ::: +++at+System.Threading.Thread.AbortInternal()%0d%0a+++at+System.Threading.Thread.Abort(Object+stateInfo)%0d%0a+++at+System.Web.HttpResponse.AbortCurrentThread()%0d%0a+++at+Passwordstate.Common.AddDebugInfoData(String+Category%2c+String+DebugInformation%2c+String+EventType)%0d%0a+++at+Passwordstate.Audit.AddAuditing(String+strActivity%2c+String+strDescription%2c+Int32+intPasswordListID%2c+Int32+intPasswordID)%0d%0a+++at+Passwordstate.Upgrade.Build_7721_CopyPassword(String+PasswordID%2c+String+HostID%2c+String+ScriptID%2c+Boolean+ResetStatus%2c+DateTime+LastResetDate%2c+Boolean+AuditRecordFound%2c+String+HostName%2c+String+UserName) 2018-12-05 11:50:46 AM - Build Process 'Build_7721_UpdateNonActiveDirectoryAccounts()' failed with the following error - Thread+was+being+aborted. ::: +++at+System.Threading.Thread.AbortInternal()%0d%0a+++at+System.Threading.Thread.Abort(Object+stateInfo)%0d%0a+++at+System.Web.HttpResponse.AbortCurrentThread()%0d%0a+++at+Passwordstate.Upgrade.Build_7721_CopyPassword(String+PasswordID%2c+String+HostID%2c+String+ScriptID%2c+Boolean+ResetStatus%2c+DateTime+LastResetDate%2c+Boolean+AuditRecordFound%2c+String+HostName%2c+String+UserName)%0d%0a+++at+Passwordstate.Upgrade.Build_7721_UpdateNonActiveDirectoryAccounts() 2018-12-05 11:50:46 AM - Build Process 'Build_7721_Updates' failed with the following error - Thread+was+being+aborted. ::: +++at+System.Threading.Thread.AbortInternal()%0d%0a+++at+System.Threading.Thread.Abort(Object+stateInfo)%0d%0a+++at+System.Web.HttpResponse.AbortCurrentThread()%0d%0a+++at+Passwordstate.Upgrade.Build_7721_UpdateNonActiveDirectoryAccounts()%0d%0a+++at+Passwordstate.Upgrade.Build_7721_Updates() What are the next steps to determine the cause? p.s I can restore the Application and Database at will, so further debugging can be performed if necessary. Thank... Scott
  10. SGauvin

    URGENT - upgrading from 7.6 failed

    First to answer the comment from 'Buckit', yes we did test the upgrade in our lab but we did not have a true replica of the production setup (for the lab we had both the Application and DB on the same server. and in production these are on different servers), and we did not have a production copy of the data. I'm now creating a replica of our production setup (both on virtual-servers). We've restored the production database into the Database_labvn. We also cloned the production Application server into a Application_labvm and modified the web.config to point to the Database_labvm. On the Application_labvm, is there a file where I can modify the URL (https://hostname:9119) so that it points to the Application_labvm and not production (example https://Application_labvm:9119)? Thanks... Scott
  11. SGauvin

    URGENT - upgrading from 7.6 failed

    Thanks for the quick reply - we successfully backed out as we don't have AV on this server. What are our next steps, to identify the issue? Is there anything I could provide that would help? FYI - I took a backup of the database (in case it can provide some insight) along with a backup of the inetpub\passwordstate. I will likely set-up a lab-environment to replicate production tomorrow (as it is 11:50pm local time). Thanks... Scott
  12. HI, I'm attempting to upgrade to version 8 from 7.6 and I got the following: 2018-11-26 10:20:12 PM - Preparing for upgrade has completed successfully. 2018-11-26 10:38:36 PM - Build 7668 Upgrade Started. 2018-11-26 10:38:36 PM - Build 7668- Step 1 Completed Successfully. 2018-11-26 10:38:36 PM - Build 7668 - Step 2 Completed Successfully. 2018-11-26 10:38:36 PM - Build 7668 - Step 3 Completed Successfully. 2018-11-26 10:38:36 PM - Build 7668 completed successfully. 2018-11-26 10:38:37 PM - Build 7676 Upgrade Started. 2018-11-26 10:38:37 PM - Build 7676 - Step 1 Completed Successfully. 2018-11-26 10:38:37 PM - Build 7676 completed successfully. 2018-11-26 10:38:38 PM - Build 7721 Upgrade Started. 2018-11-26 10:38:38 PM - Build 7721- Step 1 Completed Successfully. 2018-11-26 10:38:39 PM - Build 7721 - Step 2 Completed Successfully. 2018-11-26 10:38:47 PM - Build Process 'Build_7721_CopyPassword()' failed with the following error - Thread+was+being+aborted. ::: +++at+System.Threading.Thread.AbortInternal()%0d%0a+++at+System.Threading.Thread.Abort(Object+stateInfo)%0d%0a+++at+System.Web.HttpResponse.AbortCurrentThread()%0d%0a+++at+Passwordstate.Common.AddDebugInfoData(String+Category%2c+String+DebugInformation%2c+String+EventType)%0d%0a+++at+Passwordstate.Audit.AddAuditing(String+strActivity%2c+String+strDescription%2c+Int32+intPasswordListID%2c+Int32+intPasswordID)%0d%0a+++at+Passwordstate.Upgrade.Build_7721_CopyPassword(String+PasswordID%2c+String+HostID%2c+String+ScriptID%2c+Boolean+ResetStatus%2c+DateTime+LastResetDate%2c+Boolean+AuditRecordFound%2c+String+HostName%2c+String+UserName) 2018-11-26 10:38:47 PM - Build Process 'Build_7721_UpdateNonActiveDirectoryAccounts()' failed with the following error - Thread+was+being+aborted. ::: +++at+System.Threading.Thread.AbortInternal()%0d%0a+++at+System.Threading.Thread.Abort(Object+stateInfo)%0d%0a+++at+System.Web.HttpResponse.AbortCurrentThread()%0d%0a+++at+Passwordstate.Upgrade.Build_7721_CopyPassword(String+PasswordID%2c+String+HostID%2c+String+ScriptID%2c+Boolean+ResetStatus%2c+DateTime+LastResetDate%2c+Boolean+AuditRecordFound%2c+String+HostName%2c+String+UserName)%0d%0a+++at+Passwordstate.Upgrade.Build_7721_UpdateNonActiveDirectoryAccounts() 2018-11-26 10:38:47 PM - Build Process 'Build_7721_Updates' failed with the following error - Thread+was+being+aborted. ::: +++at+System.Threading.Thread.AbortInternal()%0d%0a+++at+System.Threading.Thread.Abort(Object+stateInfo)%0d%0a+++at+System.Web.HttpResponse.AbortCurrentThread()%0d%0a+++at+Passwordstate.Upgrade.Build_7721_UpdateNonActiveDirectoryAccounts()%0d%0a+++at+Passwordstate.Upgrade.Build_7721_Updates() Hoping you can help immediately, before I have to back out. Is there an easy fix/quick fix for this? Thanks. ... Scot
  13. Hi, I appreciated the 'quick' reply but your answer does not make sense to me, at least not in the situation I provided. The DATABASE is 'down' so there is no way the information being presented comes from the database. Here is a snapshot of the screen that I am referring to: On this error page it has an embedded link 'Passwordstate Web Site' (which has a URL reference) - as the database is 'down' I'm assuming this must be coming from a property-file or somewhere else on the file-system. Can you verify where this is sourced? p.s. I'm not necessarily looking for a solution that is dynamic, I'm OK with making manual modifications. Thanks... Scott
  14. Hi, I'm in the process of upgrading to 8.4 (from 7.6), and would like to take this opportunity to enhance the standard error-pages to include a link to our HA server when our main-server is inoperable (especially for 'Database Connectivity Error'). We currently have an Active-Passive setup for HA. I opened the /passwordstate/error/dbconnectivity.aspx file - thinking this is a likely place to add the reference, but it contains "This is a marker file generated by the precompilation tool, and should not be deleted!". Is it possible to modify the standard error pages? If so, what are the steps to do so? If not, is there another way that the link to the HA server can be provided via PasswordState? Thanks... Scott
  15. Hi, In the version I have installed (v7.6) I have the System Setting option called "Enable the 'Toggle Visibility of Web API IDs' menu for Password List Administrators only", and currently have it set to YES. The problem I have is that ONLY users with 'Administrator' access can see it. I would like to grant users with 'Modify' access to be able to see it too [ I would like to give these users access without having to elevate their privileges to 'Administrator'').
×