support

Issue: You attempt to log into Passwordstate, but you get the following error: Potential Fixes: This error can be caused by a few different options, and below we will list these to help you investigate the issue Web.config file explanation: On your Passwordstate web server, you will find a c:\inetpub\passwordstate\web.config file. You should see a connection string which includes four pieces of information - your database server and instance, database name and a SQL username and password. An example of this can be found below: If you cannot find these details in your web.config file, then this will mean someone he encrypted the file for added security, and you'll need to decrypt the file to be able to read it in clear text. More about what an encrypted file looks like, and how to decrypt it can be found in this forum post: https://forums.clickstudios.com.au/topic/2699-encrypting-and-decrypting-the-webconfig-file/ Potential Fix #1 First thing to check is that the password for your SQL account in your web.config file is valid. Using SQL Management Studio Tools, try establishing a connection to your database server using the detail from your connection string. If the connection is refused, you will need to update the password in the web.config file to match the actual password on the database server. Potential Fix #2 If your database resides on a separate server, check to see if there are any firewalls blocking access. To test this, open Powershell on your web server, and run the following command, but substitute in your database server name: Test-NetConnection -ComputerName SQLServer01.clickdemo.com -Port 1433 If this does not come back with a true result, it could mean that either a firewall is blocking access, or your SQL server is listening on a different port than the default port 1433. To check if you are using a differnt port, open SQL Server Configuration Manager on your database server, and look for the TCP/IP connection properties. You will see the Port number under the IP Addresses tab: If you find that the port is different, you will need to update it in your web.config file, using this example below as a guide: Potential Fix #3 Sometimes we have seen the SQL account password has expired. Log into your database server using another privileged account, and deselect the password policy for the "passwordstate_user" account (this is the default account most people will use) Potential Fix #4 Check for outstanding Windows updates that require a reboot on both your web server, and database server (assuming the database is hosted separately). Just search for updates from the Start Menu and if a reboot is required, schedule one as soon as possible. Potential Fix #5 If you are using SQL Replication in any capacity to replicate data between two database servers, you may be using a SQL Listener. A SQL Listener is a virtual computer in Active Directory, that makes connections to either of your databases where you are replicating data to. If you are using a SQL Listener, try hardcoding the database server and and instance in the Connection String, in the web.config file. Potential Fix #6 Check that the SQL Services are running on your database server: If you still have connection issues, please log a support call with Click Studios Support: https://www.clickstudios.com.au/support.aspx Regards, Support

Issue: You have installed Passwordstate on Server 2022, and are attempting to run through the initial set up wizard. Your Test Connection button comes back as a successful test, but half way through the wizard the screen crashes asking you to look in the "DebugInfo" table for any error. You check the DebugInfo table, and nothing gets returned. Potential Cause: At the time of writing this forum post we've only seen this issue a couple of times, and we believe this occurs if TLS 1.2 has been disabled on the web server. This could be applied via Group Policy or may be built into the OS by default. TLS 1.2 is still perfectly safe to use, and TLS 1.3 will be supported by Click Studios we think in the next major build we release. Potential Fix: Enable TLS 1.2 on your system, reboot, and reset the initial Passwordstate set up wizard. The easiest way to do this is with IIS Crypto tools, and this process is outlined below: Download IIS Crypto GUI from this link on your web server, and open it once downloaded: https://www.nartac.com/Products/IISCrypto/Download Click the Best Practices button Reboot your web server Reset the Passwordstate installer as per these instructions: https://forums.clickstudios.com.au/topic/1663-resetting-the-passwordstate-setup-process/ Run though the initial set up wizard If for some reason this does not help, please log a support call with Click Studios Support: https://www.clickstudios.com.au/support.aspx Regards, Support

Hello Mark, We need to update the wording on this screen, as it has not been done since we've added the App Server feature. The message is referring to the 'Primary Server' Server Role, you see on this screen. So there are no issues with you deleting the App Server role here. Regards Click Studios

Hello Roman, Unfortunately there are no plans to develop extensions for those browsers. We use to have Safari extensions, but then Apple made large architectural changes to how Safari extensions work, requiring software developers to completely re-write their extensions. At that stage, we dropped support for Safari. Regards Click Studios

Issue: The Passwordstate Windows Service executes back ground tasks such as password resets, heartbeats, reports and email notifications. If you notice that the Passwordstate Windows service is in a stopped state, this could be due to your AV solution quarantining the executable for the Windows Service. Cause: In build 9708, we moved the passwordstate.exe file to a new location, in a dedicated folder. Moving this file has resulted in some AV solutions to quarantine the file. Fix: Step 1: Check if the c:\inetpub\passwordstate\windowsservice\passwordstate.exe file exists. If it doesn't proceed to step 2. If it exists, but the service will still not start, please log a support call with Click Studios as this will be a different issue. Step 2: On your Passwordstate webserver, download the zip file from here and extract it: https://www.clickstudios.com.au/downloads/temp/PasswordstateWindowsService_Build9753.zip Step 3: Place it in the c:\inetpub\passwordstate\WindowsService folder Step 4: Run the upgrade again straight away by following section 3 in this guide: https://www.clickstudios.com.au/downloads/version9/Upgrade_Instructions.pdf Regards, Support

Hi Jeff84, Unfortunately there's no direct upgrade path from Version 5 to the latest build, so we'd recommend installing a new version of Passwordstate on the new server, in the new domain, and then exporting the passwords from the old instance and import them into the new instance. You'll then need to set up your new domain details and users and apply permissions throughout the software accordingly. You can apply your current licenses to the new instance whilst doing this migration to open up the same amount of licenses. Hopefully this works and happy to discuss more over our support email if you would prefer to contact us there. Depending on how many folders and password list you have and how you have your systems structured, we may be able to script the creation of these objects when using the bulk import feature? Our support can be contacted via this page: https://www.clickstudios.com.au/support.aspx Regards, Support

Hello Everyone, Today we have released build 9753. For full details, please refer to our changelog here https://www.clickstudios.com.au/passwordstate-changelog.aspx Regards Click Studios

Hello, The forums is designed for customers to help each other out, and please log your support ticket here if you require some help from us - https://www.clickstudios.com.au/support.aspx Regards Click Studios

Hi Fabio, As explained in your support ticket, you can use SAML Authentication and Local Accounts in Passwordstate, to achieve what you want. Please have another look at the support ticket we responded to this morning. Regards Click Studios

Yes, please open a support ticket. We will need to be able to replicate the issue to fix any bugs, and at this stage we cannot seem to do that. Are you using a later build of version 9? Regards Click Studios

Hi Guys, When we search in an OU, we are initially filtering on the following: mySearcher.Filter = ("(&(objectClass=computer)(operatingSystem=*)(!(userAccountControl:1.2.840.113556.1.4.803:=2)))") 'userAccountControl is to exclude any disabled hosts - ! means Not Disabled When we have the data for this filter, we then look at the attributes lastlogontimestamp, dnshostname, name & operatingsystem. I have added a Host into an OU manually, where the following attributes are blank - lastlogontimestamp, dnshostname & operatingsystem. My discovery job does not error, and it imports other records as appropriate. As you've posted this in the Version 8 section of the forums, are you still using version 8? If so, please try upgrading to version 9, using these instructions - https://www.clickstudios.com.au/downloads/version9/Upgrade_Instructions.pdf Regards Click Studios

Hi Andy, Thanks for your request. In case you're not aware, the users can simply re-enroll again, and set their own pin. Regards Click Studios

Hello Everyone, Today we have released build 9737. For full details, please refer to our changelog here https://www.clickstudios.com.au/passwordstate-changelog.aspx Regards Click Studios

Hello mackov83, Using the Test buttons, sends emails live from the UI - so it doesn't add records into the QueuedEmail table, for the Passwordstate Windows Service to send. The Windows Service will pick up any settings changes within 5 minutes, but as you configured your settings quite some time ago, this would not be relevant. Plus, upgrading Passwordstate also restarts the Passwordstate Windows Service. If you see items in Sent Items, and are not receiving them, then possibly check your spam folder - the test Email Template email for me was caught by our spam software. Regards Click Studios

Hi Guys, We are working on synchronizing Azure AD user accounts and security groups in version 10, which we believe will somewhat help with this feature request. With SAML authentication, you can also use Azure MFA for this already as well. Regards Click Studios

Hello, I tested this, separate to the other developer, and it's working for me. I've ensured no SMTP settings were set, and tested the Email Templates, Self Destruct Messages, and various functionality where the Passwordstate Windows Service sends emails. Have you selected the option to "Save Emails to Sent Items"? If so, in Exchange Online, does it say it's sent the email or not? Regards Click Studios

Hello mackov83, Could you please upgrade to build 9735, and let us know if you have any further issues. Regards Click Studios

Hello Everyone, Today we have released build 9735. For full details, please refer to our changelog here https://www.clickstudios.com.au/passwordstate-changelog.aspx Regards Click Studios

Okay - thanks.

Hello Fersa, Are you aware that you can currently enable Biometrics for 2FA? Regards Click Studios

Thanks again for your patience - we appreciate it.

Hello, we believe we've figured out the issues this time, which will be fixed in the next release. The reason we did not pick it up in our testing, was because we left behind some SMTP settings, instead of clearing them. As a work around for now, you can make this work: By having something in the SMTP mail server setting whilst using Exchange Online as the mail option By having an email address in Also Send Emails To section on the Email Templates page. Thanks again for reporting it, and for your patience. Regards Click Studios

Hello, To confirm, the only issue you're having is testing sending emails from the Email Template screen, and all other functionality is working? If so, we'll revisit this again in the next build. As testing these templates is not critical to the software, it will be a while before next build. But if there is something more critical we're not aware of, please let us know. Regards Click Studios

Hello Mackov83, Could you please try upgrading to build 9727, and let us know if you have any further issues? Thanks Click Studios

Hello Everyone, Today we have released build 9727. With this release, we have a new Windows Credential Provider for our Password Reset Portal module, which no longer requires Internet Explorer. It also does not rely on other browsers like Chrome or Firefox. For full details, please refer to our changelog here https://www.clickstudios.com.au/passwordstate-changelog.aspx