Jump to content

support

Administrators
  • Posts

    5,087
  • Joined

  • Last visited

  • Days Won

    318

Posts posted by support

  1. Hi Tim,

     

    Our fields are applied at the Password List level, and not at the password record level - which sounds like what you're asking based on the Account Type field.

     

    This would require a major re-architecture of our software, which is not something we would consider any time soon.

     

    So you can select different fields at the Password List level, or you can also use Password List Templates - and link them to Password Lists if required.

    Regards

    Click Studios

  2. Hello Maurice,

     

    If you want High Availability for database connectivity for your App Server, we recommend using either Basic or Always On Availability groups in SQL Server. Then you can point your App Server, to the SQL Listener, just like you would with the core product.

    If you do not have Basic or Always On Availability groups, you would need to modify the database connection string for your App Server, and manually change it to your other SQL Database Server - since you do not have any automatic failover for SQL Server.

    We hope this helps.

    Regards

    Click Studios

  3. Issue:

    If you try to manually sync a Security Group in Passwordstate, and you see the following error:

     

    2022-08-18_8-52-54.png

     

    The error above is telling you to look in  the Administration -> Error Console and you will find the message below:

     

    Build No '9535' - Error Code = The user name or password is incorrect. , StackTrace = at System.DirectoryServices.DirectoryEntry.Bind(Boolean throwIfFail) at System.DirectoryServices.DirectoryEntry.Bind() at System.DirectoryServices.DirectoryEntry.get_AdsObject() at System.DirectoryServices.PropertyValueCollection.PopulateList() at System.DirectoryServices.PropertyValueCollection..ctor(DirectoryEntry entry, String propertyName) at System.DirectoryServices.PropertyCollection.get_Item(String propertyName) at System.DirectoryServices.AccountManagement.PrincipalContext.DoLDAPDirectoryInitNoContainer() at System.DirectoryServices.AccountManagement.PrincipalContext.DoDomainInit() at System.DirectoryServices.AccountManagement.PrincipalContext.Initialize() at System.DirectoryServices.AccountManagement.PrincipalContext.get_QueryCtx() at System.DirectoryServices.AccountManagement.Principal.FindByIdentityWithTypeHelper(PrincipalContext context, Type principalType, Nullable`1 identityType, String identityValue, DateTime refDate) at System.DirectoryServices.AccountManagement.Principal.FindByIdentityWithType(PrincipalContext context, Type principalType, String identityValue) at System.DirectoryServices.AccountManagement.GroupPrincipal.FindByIdentity(PrincipalContext context, String identityValue) at uRM=.9x4=.pBk=(Int32 Eh8=, String Ex8=, String FB8=, String FR8=, Boolean Fh8=, String Fx8=)

     

    Specifically it says that the Username and Password is incorrect, and this is referring to the Privilege Account you has assigned to your domain.  But if you check the password for the Privileged Account, it is correct.  We've had a customer advise that either setting a domain controller on their domain as per the screenshot below fixes this issue, or you can change your Privileged Account to be in the format of user@domain.com instead of domain\user

     

    2022-08-18_8-58-36.png

     

    Your Security Groups should now start sync'ing correctly.  If they still don't please log a support call to Click Studios.

     

    Regards,

    Support.

     

  4. Issue:

    You may see issues like scheduled password resets not occurring, or scheduled reports being sent out, or possibly even backups are not running.  The Passwordstate Windows Service does a lot of background tasks, all of which are outlined in this blog post:  https://blog.clickstudios.com.au/what-does-the-passwordstate-windows-service-actually-do/

     

    Click Studios Support have seen issues reported to us by customers previously where an AV solution can quarantine your Passwordstate Windows Service, or perhaps something else has completely uninstalled it.  Below are instructions on how to reinstall this manually.

     

    Fix:

    First check your Windows Services on your Passwordstate webserver to see if you can see the Service running.  If it's present, but not start it, please start it.

     

    2022-08-16_12-57-10.png

     

    If you do not see the above service at all, you'll need to first check that the c:\inetpub\passwordstate\bin\passwordstate.exe file exists.  If this does not exist, you should restore this file from your AV Quarantine, or do a repair on your Passwordstate website. 

     

    2022-08-16_12-58-50.png

     

    Once the file is restored, open a DOS prompt as Administrator, and then run the following commands, one at a time:

     

    CD "C:\Windows\Microsoft.NET\Framework\v4.0.30319"

     

    InstallUTIL.exe "C:\inetpub\Passwordstate\bin\Passwordstate.exe"

     

    net start "Passwordstate Service"

     

     

    This will complete the process.  Please note, you may want to check that you do not have a lot of emails queued up before performing this process.  To check this and possibly purge them, go to Passwordstate Administration Home and click on the button below:

     

    2022-08-16_13-02-50.png

     

    Regards,

    Support.

     

     

  5. If you are trying to set up a folder structure where you can keep control of where users are creating Password Lists and Folders, you can consider preventing your users from creating these objects in the root of Passwords Home.  This way, they will only be able to create new Folders and Lists in a existing folder where they have the appropriate permissions.  Below is the areas where you will lock this down by removing permissions for the appropriate user:

     

    2022-08-10_10-38-23.png

     

    2022-08-10_10-37-58.png

     

    Regards,

    Support

     

     

×
×
  • Create New...