Navigation Menu

Click the "+" to see inside a chapter or use the search to the right.


Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


  1. Ensure that the file updated in steps 1 and 2 of Upgrading from 7.1704 to 7.1705 is placed in folder C:\EnvProp\. Also, ensure that the file created in step 3 of Upgrading from 7.1704 to 7.1705 is placed in folder C:\SecProp\.
  2. Info
    titleItemGroup Database Setup

    We are Migrating the application and from below 7.1807 to 7.1807 or higher version we need to execute this step and create Itemgroup DB. If we already created Itemgroup DB we can skip this step.


    1. From 1807 release, we introduced a new Microservice: Item Group. This will be utilized for managing groups of items in future releases.

    2. In order to set it up, we need to configure a new database first.

    3. Open SQL Server Management Studio and connect to the one being used with ExamDeveloper.

    4. Right-click Database node in Object Explorer and select New Database from the context menu.

    5. Name the database Itemgroup on the general tab and accept the default settings. If we are using multiple instances in the same server we need to provide different names for each instance like for example Itemgroup_BETA / Itemgroup_PROD.

    6. Go to Security → Logins, and right-click Properties on the user that is utilized for ExamDeveloper login. For example; ED is shown in below picture

    7. Assign the same permissions given to another database to the Itemgroup database.

    8. Enable Snapshot isolation for ItemGroup database name in step e using the following commands tougher from Microsoft SQL Server Management Studio :

      ALTER DATABASE [ItemGroup]


  3. Create SVNScript folder in D drive.
  4. Download the Migrate-SVNClient.ps1 script file and save it on D:\SVNScript \. (see attachment Migrate SVN clients to Target location )

  5. Open Windows PowerShell as Administrator. Change the location of the script to be located inside D:\SVNScript folder.

  6. Bypass the PowerShell execution policy with the following command and press enter, while asking the confirmation press "y" and enter:

    Set-ExecutionPolicy bypass
  7. Info

    While setting versions in point f above, instead of 1805 we need to use 1805.1 and also instead of 1809 we need use 1809.01


    Run the command ./Migrate-SVNClient.ps1 -download -installServices -installWebApplication -SVNFilesDownloadPath D:\SVNScript -instanceName 'Standard' -versions <Version List>. where are Version List is verstions of current version to It will start to upgrade the application to the target version. 
    If current version is 1806 and we are migrating the application from 1806 to 1904 command will be ./Migrate-SVNClient.ps1 -download -installServices -installWebApplication -SVNFilesDownloadPath D:\SVNScript -instanceName 'Standard' -versions @("1806","1809.01","1901","1902","1903","1904")
    1. download: This flag will be used to download files from the SVN repository to a local folder. while doing 2nd instance (SideBySide) in the same server we can remove this flag form the command because files already downloaded with the 1st upgrade.
    2. installServices: This flag to indicate to install the Service.
    3. installWebApplication: This flag to indicate to install the web application.
    4. SVNFilesDownloadPath : Location, where we are downloading the SVN files in our example location, is D:\SVNScript .
    5. instanceName: We will pass this instance name for running the multiple instances in the same server, in this example, it is "Standard" represented for a single instance in the server. If we need to install SideBySide instances in the same server InstanceName will be APP_RELATIVE_URI_PREFIX= key value from the self-hosted properties files. this will be like Beta / Prod Etc....
    6. versions - Release versions list from which release to which release client application is migrating.


  8. Info

    While executing the script please follow the screen instructions below:

    1. First, it will prompt the service user credentials please provide them along with domain name like below screenshot
      (created in step 3 of Upgrading from 7.1702 to 7.1704)


      Please ensure that the User name is entered in the "domain-name\username" format; in our example, it is "WIN10-PC\Administrator".

    2. Next, It will prompt for files like below:
    3. After click OK it will open file open dialog box like below please set the path and select the file and click open:
    4. Next, It will prompt for files like below:
    5. After click OK it will open file open dialog box like below please set the path and select the file and click open:
  9. Info
    titleIf Target version is 1903 or we are Jumping 1903 First time

    QuestionRevisioningMigration utility will migrate user tracking data for the project shared questions. Follow the steps below to execute the QuestionRevisioningMigration utility.

    1. Open Command prompt as Administrator. 

    2. Change folder location to D:\SVNScript \7.1903\web\web\QuestionRevisioningMigration.

    3. Type QuestionRevisioningMigration.exe <CONNECTION_STRING> "projectshare" and press Enter, <CONNECTION_STRING> is your ExamDeveloper database connection string, which is the same as the value of the CONNECTION_STRING token from the file.

      Example: QuestionRevisioningMigration.exe "Data Source=WIN-VSGF1NBSVPB;Initial Catalog=ExamDeveloper;Persist Security Info=True;User ID=ExamDev;Password=P@s$w0rd" "projectshare"

    4. This is a long-running process that will take some time based on the data available in the database. 

    5. The command prompt screen will tell you how many Question version updates completed and show the progress of migrating question revisioning data. 

    6. If there were any error, you can find them here: D:\SVNScript\7.1903\web\QuestionRevisioningMigration\logs\QuestionRevisioningMigration.log and D:\SVNScript\7.1903\web\QuestionRevisioningMigration\logs\QuestionRevisioningMigrationPerformance.log.


Please follow the instructions in Uninstall service using command prompt to uninstall service manually.