SDFD

moved my question:https://forums.clickstudios.com.au/topic/15434-setting-up-test-instance-license-limits/

I've been trying to build a test instance, but boy is it cumbersome to install with the provided documentation. I have followed the following instructions: https://clickstudios.com.au/downloads/version9/Move_New_Web_Server.pdf https://clickstudios.com.au/downloads/version9/Move_New_Database_Server.pdf i created a new server, installed SQL. installed PWS up to Section 5 (did not do Section 6). Copied the "connectionStrings and AppSettings" (unencrypted). copied over the "SecureID" folder, as a wasn't sure this applied. We do use 2FA, but not RSA. copied the production database to the test server. recreated the 'passwordstate_user' with 'db_owner' role. adjusted the "web.config' to match the new host and password (database remained the same). And finally restarted all services just to be sure. When i try to access the website, i get the attached error. Can't i just install a new instance, according to documentation, and simply use my existing keys? I don't really need the data from production to test stuff out.

I made the mistake of asking below question in the community forum. [Question] Setting up Test instance - license limits - Community Support - Click Studios Community Hi, I've been meaning to set up a test environment of PasswordState but i had a few questions. according to this blog-post https://blog.clickstudios.com.au/can-you-setup-a-test-instance-with-production-data/ and the EULA https://www.clickstudios.com.au/downloads/Passwordstate_EULA.pdf We're allowed to set up a single production server, and a single non-production, unless otherwise specified. Where can i find if it is otherwise specified? From what i have received, i think i'm allowed to run the above 2 instances, but i cannot be for sure. Aside from that, can you setup a non-production instance with the same licences that we've received (in our case Client Access licenses and Annual support)? I couldn't find an answer to this on the blog linked above. As it talkes about "Passwordstate Production License Keys". Thanks!

I've been trying to build a test instance, but boy is it cumbersome to install with the provided documentation. I have followed the following instructions: https://clickstudios.com.au/downloads/version9/Move_New_Web_Server.pdf https://clickstudios.com.au/downloads/version9/Move_New_Database_Server.pdf i created a new server, installed SQL. installed PWS up to Section 5 (did not do Section 6). Copied the "connectionStrings and AppSettings" (unencrypted). copied over the "SecureID" folder, as a wasn't sure this applied. We do use 2FA, but not RSA. copied the production database to the test server. recreated the 'passwordstate_user' with 'db_owner' role. adjusted the "web.config' to match the new host and password (database remained the same). And finally restarted all services just to be sure. When i try to access the website, i get the attached error. Can't i just install a new instance, according to documentation, and simply use my existing keys? I don't really need the data from production to test stuff out.

Hi, I've been meaning to set up a test environment of PasswordState but i had a few questions. according to this blog-post https://blog.clickstudios.com.au/can-you-setup-a-test-instance-with-production-data/ and the EULA https://www.clickstudios.com.au/downloads/Passwordstate_EULA.pdf We're allowed to set up a single production server, and a single non-production, unless otherwise specified. Where can i find if it is otherwise specified? From what i have received, i think i'm allowed to run the above 2 instances, but i cannot be for sure. Aside from that, can you setup a non-production instance with the same licences that we've received (in our case Client Access licenses and Annual support)? I couldn't find an answer to this on the blog linked above. As it talkes about "Passwordstate Production License Keys". Thanks!

It seems i can't get it to work on 1433 either anymore. I try to run as clean as i can, so that i don't come across problems that may be caused by something unknown. So i always try to revert any changes i just made if it doesn't work. initially after i opened this post i removed PWS and removed the SQLEXPRESS instance according to MS docs: Uninstall existing instance - SQL Server | Microsoft Docs because I was hoping i didn't need to reinstall MSSQL entirely. After confirming that the SQL server was running on its defaults settings, i tried to launch the PWS configuration site but i ended up getting the same 2 error screens as above. No database was created (nor the PWS user). I can't think of anything that i changed/tested that could result in this problem. I just tried to run the config again, the database connection test came out positive and the configuration was running longer than usual. Now i get the 2nd database error (Sorry no screenshot). but this time the database is somehow/somewhat created including the PWS user. The error said i needed to remove the database 'passwordstate' the user 'passwordstate_user' and try again. Either way, PWS wasn't working. The only thing i can image is something with the firewall. I did add a rule to it, but i later removed that because PWS still wasn't working. On this server only the Private and Public Firewall are running (Windows 2019, 1809, build 17763,2145). Domain firewall is disabled currently. I'll reinstall the entire IIS/SQL/PWS to see if i can get working on the default port again. edit: I've managed to make PWS work on the default port again. Seems i wrecked some registry causing MSDTC not working anymore. After reinstalling en enabling MSDTC i was able to reinstall PWS entirely and on the default DB port 1433. Let me know if you find any solution to changing the DB port.

unfortunately no. the number 12345 is just an example. if i put the number 6 in front it will look closer. the screenshots might also make it a bit difficult to be sure. this is the copy-paste: HOSTNAME,88888

I was working my way through the PWS setup but i can't seem to get it to work with a custom port for the database. If i run the setup on the default ports, the database will be created. when i'm at the Database settings page, i enter the DB server, instance name and credentials (i've obscured some details) My MSSQL is setup according to the SQLExpress 2019 documentation and both PWS and SQL run on the same machine. when i test the connection, i get positive results. But when i click next, it start to try and create the PWS database and user, but it returns an error. i've edited the SQL Server Network Configuration as described in the documentations Unfortunately, i can't seem to get it to work on a custom port. I tried changing the "Listen All" setting to no avail. Nor did it help to enable the "Named Pipes" setting or enabling the SQL Server Browser. When i open Microsoft SQL Server Management Studio and try to connect to the servername: HOSTNAME,PORT\SQLSERVER i can connect just fine. testing it with a powershell command: powershell -Command "Test-NetConnection -ComputerName 'HOSTNAME' -Port 12345" says the TcpTestSucceeded: True. The strangest thing i see is when i look in Event Viewer. After i restart the SQL Server service, i see the Event ID 26022 initially show the correct port i specified. Server is listening on [ any <ipv4> 12345]. but a fraction of a second later, it shows a random port but for localhost: Server is listening on [ 127.0.0.1 <ipv4> 49699]. I'm a bit at a loss here what i can see/do to fix this problem. Maybe i've missed something during the SQL setup or i'm configuring PWS wrong. Hopefully you can help me out here.