versaSRS Knowledge Base

 

 

Setting Up Two Instances Of versaSRS On The Same Server

Article ID: Q731374

Category: FAQ - How To

The information in this article applies to:

  • versaSRS Version 7
  • versaSRS Windows Services
  • Installation

The below steps can be followed to create an additional instance of versaSRS on the same server where an existing instance is installed

1. Copy the application folder, default location C:\Program Files (x86)\VersaDev\versaSRS, of the existing versaSRS folder and paste it in the same VersaDev folder under a new name. Ensure folder permissions are the same as the existing folder.

2. Setup new website on the server under IIS and duplicate the same applications that are present under the existing versaSRS site in IIS. Ensure that each application maps to the path within the new versaSRS folder created in step one.

  • **SRSConnect **
  • **versaAssetsWebService **
  • **versaChatWebAPI **
  • **versaInstall **
  • **versaSRS **
  • **versaSRSWebServices **
  • **versaSurvey **

3. Right click on the Application Pools list to create a Second Application pool named SRSConnect. In the Advanced Settings, for the Applications added in Step 2, ensure SRSConnect, versaSurvey, and versaChatWebAPI are in the SRSConnect Application Pool, and that the others are in the default Application Pool for this instance of versaSRS
NOTE: By default the Identity of both Application Pools is set to ApplicationPoolIdentity, if desired change the Identity to NetworkService

4. In IIS click the versaInstall application for the new instance and click Browse to launch the database installer. Follow the steps in the database installer to install the versaSRS database. Ensure that the database name is different to the existing versaSRS database.

5. Access the versaServiceMonitor folder (C:\Program Files (x86)\VersaDev\versaSRS_Instance_2\versaSRSServiceMonitor) and edit the EmailTemplates.xml file and ensure the notification templates and recipients are set appropriately for this instance. (This is only required if the monitoring should be sent to different people than the original instance).

6. Right click the VersaSRSServiceMonitor.exe.config file and set the connection string to point to the newly installed database.

7. In the Windows Search, search for cmd and right click on Command Prompt and select Run as Administrator. Run the following commands (replace Instance Name with a name of your choosing).

  • cd C:\Program Files (x86)\VersaDev\versaSRS_Instance_2\VersaSRSWindowsServices (ensure the file path is for the newly created versaSRS folder)
  • installsrs.cmd Instance Name

cmd Install Mail Services

8. The Service Monitor needs to be installed separately from the other Windows Services. You can do this with the following commands (replace Instance Name with a name of your choosing).

  • cd C:\Program Files (x86)\VersaDev\versaSRS_Instance_2\versaSRSServiceMonitor (ensure the file path is for the newly created versaSRS folder)
  • install.cmd Instance Name

9. Access the Windows Services and confirm that versaSRS Services have been installed with the new instance name

10. Update all connection strings, including the ones in the versaSRS Web.config file to point to the newly installed database. Use versaSRS Global Settings menu to update DSN entries.
If you cannot access the Global Settings via versaSRS. Execute the following SQL query to identify which values need updating.
NOTE: VersaDev takes no responsibility for any data corruption or loss incurred, be sure to take extra care not to remove or change any data by mistake when running queries directly on the database, we recommend performing a backup and implementing on a test environment before performing on production.

SELECT * FROM tbl_ApplicationSettings WHERE TypeID = 6
Value1 = [SERVERNAME]    
Value2 = [DATABASE]    
Value3 = [SQLUSER]    
Value4 = [SQLPASS]

11. Update the connection string in the versaSRSDSN.xml file, located in the VersaSRSWindowsServices folder. This is for the Mail Services.

12. Browse to all URLs and ensure they are working

13. Within versaSRS access the Global Settings and change the following fields:

  • AppTitle: Set this to show that it is the second instance so it is not confused with the existing instance
  • TempFolder: This needs to be changed to a valid folder path in the file system (this cannot be the same folder for both instances)

14. Start the secondary instance versaSRSServiceMonitor

15. Confirm email, scheduling, and monitoring Services are working correctly

183 Installing versaSRS on Windows OS - Prerequisites

272 Create a New/Second Instance of SRSConnect

355 Migrating versaSRS to a New Server

368 Creating a Host Header in IIS

375 Installation & Configuration for versaSRSServiceMonitor

Did the information in this article help answer your question?

Yes
No
Did not apply

Last Reviewed: 11/10/2024
Powered By VersaDev Pty Ltd Copyright 2022
Last Reviewed:
11/10/2024

Provided by
VersaDev Support Services