TROUBLESHOOTING
1. If upgrading the schema of an existing database and you do not see the new 011 and 012 pipeline folders appear, try running the command on the associated distribution SQL Database:
insert into BIZ_EVENT (event_data3, event_data4) select ‘INITIALIZE’, ‘$\Pipeline.ps1’
2. If you have problems, try validating the SQL login credentials. You may have to install SQL Server Management Studio in order to test the login credentials to the server.
3. Most operations are logged to the serenedi root folder under a file called “install_log” – see if there are any problems there.

• SQL Server connection string:  This defines the location and possibly the login credentials of the SQL Server account.  This account should have permissions to create a database and access it with full permissions.  For different examples of the connection string, visit:  https://www.connectionstrings.com/sqlconnection/ 
• If you do not have access to a SQL Server instance and would like to quickly set one up:
  1. Install Docker Desktop
  2. Run this command:

     docker run -e TZ=America/Los_Angeles -e "MSSQL_PID=Express" -e ACCEPT_EULA=Y -e SA_PASSWORD=strongPass1 -p 1433:1433 --name MSSQL -d mcr.microsoft.com/mssql/server:2019-latest

  3. Later during the install process when you are prompted for a SQL Connection string, use this:
     Data Source=host.docker.internal;Database=serenediCore;User id=sa;Password=strongPass1;
  4. An account and password with local administrator privileges: This is the account that will be used with the SERENEDI Service that is installed.  If this is a domain account, it should be expressed in the form DOMAIN\username.  If it is a local account, it should be expressed as ‘.\username’  (no quotes).
     If your database permissions are maintained via Active Directory, this account needs to be fully provisioned with DBO privileges to the database, as well.

• The SERENEDI Windows installer is a single MSI file, around 65MB in size. Double-clicking on the file will result in the following dialog: 
• Click Next, then click on the checkbox indicating acceptance of the End-User License Agreement and click Next.  The license viewed will be either a Trial Evaluation license or a Production license.
  
• Choose the destination folder for SERENEDI.  By default, the folder is C:\serenedi. If you’d like to choose another folder, enter it here. Otherwise, select Next.
  
• Enter in the account with local administrator rights along with the password in the boxes.  If the account is local, precede it with (for example, .\admin for a local account named admin) 
  
• Enter the connection string to the database.  Note: if you have previously installed SERENEDI to this server, any existing database will be completely destroyed unless you specify a different database name in the connection string.  Also note: in certain circumstances, you may need to add “;TrustServerCertificate=true;” to the end of the connection string.
• 
• Click “Yes” at the User Account Control popup to start the installation. 
  
• After a few seconds, SERENEDI will complete the initial setup and then install the database.  The following window will pop-up:
  
• If all steps are successful, you should get a Setup Complete dialog.  To further ensure normal operation of SERENEDI, go to C:\serenedi\shared\pipeline, and look for the following folder structure:
  
  If this folder structure exists, then SERENEDI is running and processing events successfully.

  NOTE 1: There is a known bug where if the initial Windows install fails, there could be a lingering “SERENEDIService” that is not deleted, and will prevent SERENEDI from being installed thereafter.  To remedy this, run the following commands from an Administrator shell before attempting to reinstall.  The second command should be run twice – once immediately, and again after a reboot:

Remove-Item 'Registry::HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\SERENEDIService' -Recurse
sc.exe delete SERENEDIService
<<Reboot Host>>
sc.exe delete SERENEDIService

NOTE 2: Please note that if you are reinstalling with an existing serenediCore database, the installer will destroy the existing serenediCore database and all associated data – so please back up any data you wish to keep before this time.