Installation & version updates

From CuraWiki
Revision as of 15:06, 17 August 2016 by Admin (talk | contribs)
Jump to navigation Jump to search
The process for installing or updating Cura is exactly the same, and is handled by the same program. Therefore if you are installing or updating Cura, you should follow the steps on this page.

Step 1 - Prerequisites

Server Specification

We recommend the following specs for your web server hosting Cura:

  • 2GB RAM
  • 2 Cores

Microsoft.Net Framework

You will need to have Microsoft.Net Framework, version 4.0 or later installed in order to use Cura.

NOTE: It is important that on the IIS server the order of installation is Windows -> Webserver software -> .net Framework

Microsoft Internet Information Services (IIS)

Your web server must have IIS version 7.0 or later installed. In addition to this, the following IIS features must be present:

Web Server

Common HTTP Features
Static Content
Default Document
HTTP Errors
HTTP Redirection
Application Development
.Net Extensibility
ISAPI Extensions
ISAPI Filters
Windows Authentication
Management Tools
IIS Management Console
IIS Management Scripts and Tools
IIS 6 Management Compatibility
IIS 6 Metabase Compatibility

SIMS .net workstation components

If you want Cura to allow staff to login using their SIMS username and password, or if you want Cura to periodically update staff and student details from the SIMS database, then you will need to install a workstation version of SIMS onto the same server as Cura.

Step 2 - The Service Controller

Log in to our website,, using the login details that were sent to you when you purchased Cura. If you have lost your details, please contact us on 01902 824281.

Once you have logged in, click on the "Downloads" link at the top of our website. Download and run the latest Cura service pack on your IIS server. Once you have accepted the licence agreement, the installation will unpack and begin.

The Service Controller will open, which is the program that installs and updates the Cura database and website. There are five options on the left side, each explained below. You should work through these from top to bottom.

Please note if you are only upgrading your existing Cura version (version 1.179 and above) then the Data, Web site and Application stages will automatically be skipped and the "Commit" and "Background service" will only apply.

If you are upgrading from SQL LocalDB (Cura version 1.178 and below) then all stages will apply, please also uninstall the SQL LocalDB 2014 if it is not being used by any other program (but retain the databases located usually in inetpub\wwwroot\Cura\App_Data) and then restart your server before starting the update.


This node is used to configure the database for your Cura. The options available to you are Install SQL or Continue, please read further as both are explained:

Install SQL

This method is used for a first time install of Cura and updating from SQL LocalDB (Cura version 1.178 and below), which has a built in automated process that does the following:

  • Downloads SQL Server Express with Tools 2014 from the Microsoft website, this will be confirmed with a progress bar on your service controller
  • Once downloaded the SQL Server Express files are temporarily unzipped in the "Documents" folder and the install process begins
  • Command prompt will now open and begin the install (will remain active until install is completed, please do not close)
  • SQL Server 2014 Setup wizard will now appear and complete the install, this will install the databases required and relative permissions so the data can be accessed
  • Once the install is completed a message will be displayed "Please wait while SQL Server 2014 Setup processes the current operation"
  • The Command prompt and SQL Server window will now close and return back to the Service controller
  • Now please follow the Web site information below to continue with your install

S1 1.jpg


This method is used if you have an existing SQL Server that you would like to use for Cura. This also has an automated process you will find the information in the sections below please look for '"For Continue Method only:"

  • For Continue method only: The Data process is skipped and you are moved onto the Web site area to define your site address and location of the file usually located in inetpub\wwwroot\Cura\ for further information please see Web site section below.

Web site

This node is used to configure a website. You can either use one of the existing web sites listed in the panel (Default Web Site), or add a new site by clicking on the green "plus" button. If you add a new site you will be asked to specify the site name, the listening port (which should not collide with any existing sites or services), and an SSL certificate if any such are present (or choose (none) if you are going to install this at a later date).

Additionally, you need to specify a folder on the IIS server where the application files will be stored. It is important to choose a location that the IIS user (NetworkService) will have permissions to read. It is recommended to point the path to inetpub\wwwroot\cura. (Please create this folder manually)

S2 1.jpg


Once you have chosen your site, you can add an application to that site please click on the green "plus" button. There are no options for this stage.


  • For Continue method only: On Application please click on the green "plus" button and the application will be defined cura/cura, then please click on "Continue".


Next on the Commit node. Click the "Begin" button to commit the changes to your Cura application. This process needs to be performed each time a Cura service pack is run on the web server.

For updating from SQL LocalDB only, when the Commit node is running the databases in your existing Cura folder (inetpub\wwwroot\Cura\App_Data) will be renamed and moved to Program Files\Microsoft SQL Server\MSSQL12.SIMS\MSSQL\DATA this will also attach the databases to Cura instance created earlier with the SQL Server install.


Once the commit process has completed, Cura will open in your server's default internet browser. If this happens, your update/installation has worked successfully.

  • For Continue method only: On the Commit tab, click "Begin" at the bottom of the screen and "Yes" to confirm to continue on the message box.
  • For Continue method only: A message box will appear requiring your data source, please insert in the form data source=ServerName\Instance; user=sa; password=password; if incorrect information is entered and is not valid a message This is not a valid connection string will be displayed.


Background Service


  • For Continue method only: Please note if the database is located on a different server/location, see section "Amend the web.config" below.

Running status

This tells you whether or not Cura will be performing important automated processes. Follow the three steps below in order.

  • If the "Version" field includes the text "Update available" then click the "Uninstall" button at the bottom right
  • If the "Running status" field is blank, click the "Install" button at the bottom right
  • If the "Running status" field says "Stopped" then click the "Start" button at the bottom right Please insert SIMS MIS details before clicking on "Start"

Optional MIS details


If you have a SIMS database then you can enter a SIMS username and password into these fields. This will enable staff to login using their SIMS username and password, instead of/or their work email address and Cura password. Cura will also be able to periodically (3 times per day) scan SIMS to update its list of students and staff from the SIMS database.


The user details that are entered into the Service Controller must have a permission in SIMS called "Third Party Reporter" without this permission the service will not be able to automatically update new staff and students, and also other details such as attendance.
Please check this in SIMS before proceeding.

In order for this to work please enter the following details:

  • Optional SIMS username
  • Optional SIMS password

You may also need to create an Inbound Firewall Rule for the port that Cura is running on, in order for staff to be able to log in using their SIMS credentials.

Exit Codes in SQL Server 2014 Installation

When the SQL Server installation is coming to completion you may find that an exit code is displayed, please see below for further information.

  • Exit code: 3010 - Server requires to be restarted - please restart the server and run the Cura installer again
  • Exit code: 2068643839 - This error requires technical support please contact our helpdesk
  • Should you experience any other exit codes please contact our helpdesk

Amend the web.config

This method should only be used if your databases are located on a different server/location. Please do not attempt this if you are unsure of how to amend a config file.

To amend the web.config file please find in usual location (unless specified elsewhere) inetpub\wwwroot\Cura

  • Run your editor program in Administrator mode and open the file
  • Find within the file the following code (it may appear different on each machine)
<connectionStrings configProtectionProvider="DataProtectionConfigurationProvider">
  • Replace (overwrite) with the following code
 <add name="ApplicationServices" connectionString="Data Source=servername\CURA; user id=sa;password=password; initial catalog=CURA_aspnetdb;" providerName="System.Data.SqlClient"/>
  <add name="FileSystem" connectionString="Data Source=servername\CURA; user id=sa;password=password; initial catalog=CURA_FileManager;" providerName="System.Data.SqlClient"/>
 <add name="Database" connectionString="Data Source=servername\CURA; user id=sa;password=password; initial catalog=CURA_Database;" providerName="System.Data.SqlClient"/>
  • Amend the highlighted coding for the existing database to be used for your Cura, specifying:
    • The Datasource location: servername\CURA
    • The User ID if different from sa
    • The Password please be aware that this is case sensitive
  • Save and re-run the Cura service pack to encrypt the information that has been entered

If you are unsure of how to complete any of the above steps please contact our helpdesk