Jump to content

All Activity

This stream auto-updates     

  1. Today
  2. I am still getting prompted for username and password and it will not be accepted. The "Windows Integrated API Documentation" is the only page with this behavior thus far. You do not have permission to view this directory or page.
  3. After upgrading to version 8 we are getting the following error with our Windows Local Admin Account discovery jobs: Error: An error has occurred in the Passwordstate Windows Service executing the method 'ProcessAccountsDiscoveryJob'. Error = Conversion from string "" to type 'Integer' is not valid.&stacktrace= at Microsoft.VisualBasic.CompilerServices.Conversions.ToInteger(String Value) at Microsoft.VisualBasic.CompilerServices.Conversions.ToInteger(Object Value) at PasswordstateService.PasswordstateService.ProcessAccountsDiscoveryJob(DataTable DataTable) These jobs where running without an error before the upgrade.
  4. Hi, I updated the files are per your instructions, but i still get the same error at the admin creation screen. This is what i did Created a new server Installed passwordstate Setup SSL Checked that the site worked Stopped the PWS service Did a manual overwrite of the file with the zip you gave me Started the PWS service Went through the setup Failed with the exact same error on the admin creation screen and was logged in the PWS debug log in the database I did a reboot of the server and tried again Same error.
  5. PS in HA in Azure (multi region)

    Hi Matt, Thanks for your post, and I'll try and provide some guidance - we do not have much in the way of experience with Azure, but hopefully between your knowledge of Azure, and ours of Passwordstate, we can get your questions answered. Passwordstate can connect to any version of SQL Server (2012 an above), and it really doesn't care what database replication technology is used. With On-Premise solutions, you can use Transnational Replication, High Availability Groups, Clustering etc. Within the web.config file, you will see the "database connection string" - it is this configuration which governs which SQL Server it can connect to. We've done limited testing with Azure SQL, and it seems to work fine - we can have Passwordstate pointed to one Azure SQL DB, and it seems to failover without any issues. So I do not believe this would be an issue for you. When you install the second node of Passwordstate, we recommend setting the PassiveNode key in the web.config file to "active", and then both Nodes of Passwordstate can have write access to the DB's - changing this key simply means the second Node will not duplicate processing with the Passwordstate Windows Service i.e. sending emails, synchronising AD Security Groups, performing Password Resets, etc. I hope this helps, and please let me know if you have any further questions about this. Regards Click Studios
  6. Thanks Jack, and this confirms what we believe the issue is. I've just sent you an email with the new test build, and hopefully this will resolve it. Thanks again for all your help. Regards Click Studios
  7. When trying to access the new Windows API Documentation from the Help menu in Passwordstate 8, it is possible you get a Windows based prompt asking for a username and password. To fix this, please ensure your Passwordstate URL is located in the Local Intranet Zone. To see if it is located in the Local Intranet zone, open Internet Explorer, browse to your website and open Internet Options -> Security. If it is detected it is in the Local Intranet zone, it will appear blue as per below screenshot: If you need to you can add the site in the Internet Options above, or add the site to group policy to ensure all machines detect it by default.
  8. Yesterday
  9. Yes, that server is using the same culture and language settings as the new server. PS F:\Backup\passwordstate_upgrade\passwordstate> get-host Name : ConsoleHost Version : 5.1.14393.1532 InstanceId : 5f7a71e2-0fbf-4ea2-9cb7-90f811b499c3 UI : System.Management.Automation.Internal.Host.InternalHostUserInterface CurrentCulture : nb-NO CurrentUICulture : en-US PrivateData : Microsoft.PowerShell.ConsoleHost+ConsoleColorProxy DebuggerEnabled : True IsRunspacePushed : False Runspace : System.Management.Automation.Runspaces.LocalRunspace I hadn't updated to the latest bugfix version, so the preferences pane wasn't available (server error). So before I updated I tested changing the user password via the Administration > Users screen. It worked fine. Then I updated to the latest bugfix version 8065. I logged in after the update I then clicked on my username and the preferences panel come up (Yay!) I then went to Authentication Options I changed my password Clicked save Got en ERROR - The same error as on the new server 1768 2017-08-17 14:39:18.000 General Error Error Code = The statement has been terminated. The conversion of a nvarchar data type to a smalldatetime data type resulted in an out-of-range value., StackTrace = at System.Data.OleDb.OleDbCommand.ExecuteReaderInternal(CommandBehavior behavior, String method) at System.Data.OleDb.OleDbCommand.ExecuteNonQuery() at Passwordstate.User.ResetUserPassword(String Password, String FormsPassHistory, Int32 PasswordStrengthIndex) Error
  10. Hi We are going to pull the trigger on PS and plan on running it as IaaS in Azure. We are purchasing the HA option as we plan to have an active/active setup. Some questions. Region 1: Web server and SQL server. Region 2: Web server and SQL server Plan to use availability groups and front them through an Azure load balancer. Preference is to use synchronous replication for data integrity. Questions Is this possible? How do I connect the two SQL instances, is it just using network security groups and specifying the appropriate ports? Can I use synchronous replication with SQL in Azure IaaS. Should I consider Azure SQL, does PS even support it? I'd rather not use an active/passive setup as PS documentation states that uses SQL transactional replication, and I have better experience with AoG and would prefer to use it. Thanks in advance Also posted in r/sysadmin
  11. Hi Jack, Can you do me one more favour? On your version 7 install which was upgraded to V8, does this have the same time/date settings as the failed server? If so, can you go to the Preferences screen, and then 'Authentication Options' tab, and try changing the password for an account - I'd like to know if this fails at all? Thanks very much. Regards Click Studios
  12. No rush. Glad to help. Feel free to put debug info or anything else that might be useful. The database is empty, it's a fresh install.
  13. Hi Jack, Thanks very much - we really appreciate it. This won't be today though, as we need to make the coding changes, recompile, and upload for you. I'll send you a message as soon as we have it ready. Thanks again. Regards Click Studios
  14. No problem. Just let me know what you need done and I'll do it. I'll have to do it later on tonight (my time) as I've got some family business to attend to. I'll send you my email in a private message and you can send me what needs to be done there.
  15. HI Jack, If you're willing, we could provide you a custom upgrade zip file to test i.e. overwrite all your existing files after your initially install Passwordstate. There are two fields I can make a change on here, and then hopefully we can determine what the cause is. Let me know if you're willing to do this, and have the time? Regards Click Studios
  16. Hi again, Did you reinstall the web server from scratch or just change the culture via Powershell? The reason i ask is because i tried to change the culture on the server installed with the nb-NO culture to en-US via powershell (system wide) . Although it seemed to be applied system wide I still got the error when installing Password state. When i reinstalled the webserver from scratch and choose English - United States at the start of the Windows Setup everything worked as intended. So if your server was installed with en-US as the culture then I would presume everything would still work even if you changed the culture via Powershell to nb-NO. Anyhow. I have now tested by reinstalling the server (2016 server core) with our usual settings (English, Norwegian Bokmål, Norwegian). The database is using the Danish_Norwegian_CI_AS collation as before. Here is a Get-Host of the server. PS F:\Backup> Get-Host Name : ConsoleHost Version : 5.1.14393.206 InstanceId : 05f6fb6c-4a82-41a0-b32b-5e1ff62a2afb UI : System.Management.Automation.Internal.Host.InternalHostUserInterface CurrentCulture : nb-NO CurrentUICulture : en-US PrivateData : Microsoft.PowerShell.ConsoleHost+ConsoleColorProxy DebuggerEnabled : True IsRunspacePushed : False Runspace : System.Management.Automation.Runspaces.LocalRunspace CurrentCulture = nb-NO CurrentUICulture = en-US This time i didn't join the server to the domain in case there was some strange GPO at work. I then reinstalled passwordstate and i get the same error as before on the admin creation page. The conversion of a nvarchar data type to a smalldatetime data type resulted in an out-of-range value. I really have no idea. But seeing as you cannot reproduce the error even with a server installed with my culture settings I think we should just cut our losses and move forward. Having the server installed with en-US as the primary culture is fine. As i mentioned above it didn't cause any problems during testing yesterday, so I don't expect any problems going forward. I really do appreciate you taking the time to troubleshoot on your end. But I'm fully aware that Cultures and Languages other than English are not supported. I'll reinstall (yet again :)) with United States as the primary culture and get our new server up and running.
  17. Yes, all the servers are installed in English - Trust me, no one uses language packs on a Windows Server. One of the main reasons is that error messages in Norwegian don't get many hits on Google No culture/language or UI settings are changed after install. All we do is update the server, run our DSC script to install IIS and required modules. Then we install Passwordstate and off we go. I'll reinstall a new server manually with our usual settings (English, Norwegian, Norwegian) and try again. I'll get back to you when I've done that. Thanks for taking the time to have a look at this and hopefully i haven't sent us on a wild goose chase. Maybe there was some sort of corruption with that initial server I setup that caused the issue and simply reinstalling (coincidentally with the United States Time and date format) fixed the issue.
  18. Hi Jack, We must be missing something, as we cannot seem to replicate this issue. I've tried: Time and Currency Format: Both Norwegian options And setting SQL Collation to "Danish_Norwegian_CI_AS" Rebooting the server after making these changes as well, and I cannot seem to fault this. Was your web server originally installed with English United States as the language, or was this changed afterwards? I also testing with SQL being installed on the same web server - I doubt that would make any difference. Regards Click Studios
  19. New Entry Time Out

    Hi Michael, You should only be logged out if you are inactive on the site for the timeout period specified - which is 10 minutes by default. You can check this on the screen Administration -> System Settings -> Miscellaneous tab. Are you leaving the Add Password screen open for more than 10 minutes without any activity on the screen? If you are not, then do you have any Anti-virus software installed on your web server - we've seen McAfee and Trend kill sessions in IIS, and this could be the cause? Regards Click Studios
  20. New Entry Time Out

    Is there a control to prevent being logged out while entering a new credential into PasswordState? I keep losing important passwords as i configure devices then dont get back in time to hit the save button.
  21. Last week
  22. Hi Jack, Thanks very much, and we'll setup a new server today with those Time and Currency Format, and see if we can work on a fix for this. We appreciate the feedback. Regards Click Studios
  23. Improve Bad Passwords feature

    Just an idea: You (clickstudios) could host this datas (with a powerfull method, like suggested above) and publish it by an API to the internet. So the users webbrowser could then directly access this API... just an idea :-)
  24. Improve Password Generator

    Thank you for the quick response. I look forward to seeing all the new features Cheers
  25. I finally got past the screen and it seems the solution was to install the Webserver (Server 2016 Core) with "English - United States" Region Settings All our servers are installed with the following (It's in the image): Language: English United States Time and Currency Format: Norwegian Keyboard: Norwgian I did a manual install with the following Language: English United States Time and Currency Format: English United States Keyboard: Norwgian The SQL Collation is the default for our SQL Servers "Danish_Norwegian_CI_AS". I was now able to complete the installation and all seems well. So it was the region settings on the webserver causing the problems. I don't see any major problems with having the Server for Passwordstate using the United States regions settings. But it's obviously not optimal. However it's nothing major and won't hamper our use of the product.
  26. That's very odd. All of our SQL Servers are set to a collation of 'SQL_Latin1_General_CP1_CI_AS'. I wouldn't have thought that collation is that much different to the one you selected. We'll set up a new SQL Server tomorrow with your collation, and forms based authentication, and see if we can reproduce the issue. Thanks for working with us on this. Regards Click Studios
  27. Improve Bad Passwords feature

    Thanks Nick I'd expect we'd be able to get reasonable performance as well if we only performed the check on clicking the 'Save' button, but we'd need to think about whether we want to make this change. We've had some customer's who's SQL Server times out trying to insert 10,000 records for our WordDictionary table - I wonder how it will go inserting 300 million records, with 5 GB of data
  28. Improve Bad Passwords feature

    Not to flog a dead horse but this guy got it working with reasonable (sub-1-second) performance - https://stuart-clarkson.blogspot.com.au/2017/08/creating-local-version-of-pwned.html - by splitting the passwords up based on the first few characters of the hash. :-)
  1. Load more activity
×