How to upgrade Pronestor Planner On-premise

Table of contents:

Introduction and requirements

Check the database integrity

Unpack the Pronestor files

Updating the Outlook add-in

Exchange syncronization service upgrade

Roll back

Introduction and requirements

To fulfil this guide you need admin rights on the server where Pronestor Planner is installed.

For larger installations, we recommend that this is tried out in the test environment first.

It is important that the .net framework is installed on the server before the upgrade begins, since it requires a restart. Current versions of Pronestor requires .net framework version 4.7.1

You should make a backup of the sql database before we begin.

You can download the installation files for the upgrade here

Please remember to download the upgrade file instead of the installation files.

Check the database integrity.

The upgrade can only proceed if the database integrity can be verified.

Run a pronestor tool called diag.aspx, which is located in web site or directory called "Pronestor"

This is done from Internet Information Services (IIS). Go to your site, and make sure it's set to content view. Right click diag.aspx and choose browse.

When you open it, it will ask you to login. Contant Pronestor team regarding this.

Scroll down to “Data Integrity” section and Run Integrity Check.

Run “Fix All Checked” after the check has run and confirm all errors are resolved.

There are a few errors that it cannot handle automatically. If you can, you can go to the database and correct them manually and run the diag again. Otherwise, contact support for assistence, and abort this guide.
Close browser once all errors are fixed and proceed.

Unpack the Pronestor files

Warning, do not proceed with this unless the first step went well!

It is critical that you stop the application pool before you proceed. Go to IIS, press "Application Pool" and right click.

Press stop.

Go to the server and find the installation folder of your Pronestor installation. In this guide we use the example C:\inetpub\wwwroot\pronestor but it could be anything that you choose when you installed Pronestor the first time.

If you already have an upgrade folder, please delete it.

Now create an upgrade folder and unpack zip file into it.

Open the command promt as an administrator. It is important that it is run as administrator, and not just normally.

In the command promt, go to the upgrade folder and run FULL_UPGRADE.bat

Once that is done, run diag.aspx again. It will update the database to the new version.

If you are updating to version 8.1.22 or newer

After you did the update, but before you open the site, go to the installation path, fx c:\inetpub\wwwroot\yoursitename and delete the folder named App_Code

Updating the Outlook add-in

There are two ways to handle this. If you have enabled automatic updates within Pronestors administration module, it is handled automatically. Otherwise you have to pack the software within Pronestor. You can check whether you have automatic updates in the same place as you create the installation packages, so lets go to the administration module of Pronestor, choose settings and then other settings

Then scroll down untill it looks like this:

The ticket box means this example has automatic updates. If you don't have automatic updates, you can create installers here. Simply pick the version that matches your needs and press create installer. Now it can be downloaded here:

Then you can package it for SCCM, or every user can download the installer in their Pronestor and install it.

Exchange syncronization service upgrade

If you are using exchange syncronization service, it needs to be updated as well.

Ask for the upgrade file if you didn't get it with the upgrade files.

1. Unzip the "" to a temporary folder
2. Stop the "ExchangeBookingSyncService" via Services in Windows *
3. Copy all files EXCEPT the "ExchangeBookingSyncService.exe.config"  from the temporary folder to the location of the current installed ExchangeSyncService
4. Start the "ExchangeBookingSyncService" via Services in Windows


Roll back

IMPORTANT - Any changes made after the database was backed up and before the rollback will be lost.

Steps involved in a roll back

Stop application pool for Pronestor Web Site
Stop Sync service
Restore database from backup set
Restore files into the web folder from backup of web folder and sync service
(set permissions write permission on license, app_data, content folder in Pronestor folder - for the application pool user)
Restore Sync Service files
Start Sync Service
Start Application pool

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request


Powered by Zendesk