Upgrading Enterprise Tester to 4.1
When upgrading from Enterprise Tester version 4.0.1 to version 4.1 or later, you need to be aware of some technical changes that have be made to the product which may require additional steps compared to your normal upgrade process.
#1 .Net Framework Changes
As of version 4.1 of Enterprise Tester, it now requires that you have the .Net Framework version 4.0 installed – previously the product required the .Net Framework 3.5 SP1 (which was using the .Net Framework 2.0 run-time). If running the .MSI, and the .Net Framework 4.0 is not installed, you will see this error.
You can either manually download and install the .Net Framework 4.0 from the link below, which we recommend if upgrading an existing installation of Enterprise Tester.
For trial users, you can run the included bootstrapper (.exe file) to have the .Net Framework 4.0 automatically downloaded and installed.
If using the boot strapper you will be prompted to upgrade as per this screen shot, you must click “Accept” to continue:
Additionally, in most cases installation of the .Net Framework 4.0 will require that windows reboot itself to complete installation.
Once the .Net Framework 4.0 is installed you can proceed with upgrading.
Note: When upgrading you will see a splash screen as part of the installation warning about reviewing the upgrade instructions – the good news is you are reading them right now – so feel free to ignore this screen and click “Next” to proceed with the upgrade.
As with any upgrade to Enterprise Tester we suggest backing up both your entire installation folder and your database prior to installing an upgrade.
Once the installation has been completed, Enterprise Tester will be upgraded and configured to use the .Net Framework 4.0. As part of this upgrade process Enterprise Tester will no longer use the Default Application Pool, instead the installer will create a new application pool called “Enterprise Tester” specifically for use by Enterprise Tester and targeting the .Net Framework 4.0 – this is to ensure the upgrade does not impact on users who may have other applications in the Default App Pool which still rely on the .Net Framework 2.0.
The new application pool will have the following attributes:
- Framework: .Net Framework v4.0
- Identity: Network Service
- 32 bit Applications: Enabled
- Idle Timeout: 0 (disabled)
- Regular Recycle Timeout: 0 (disabled)
For those customers making use of Integrated Authentication to the database or that require Enterprise Tester to be able to access network share locations – to support features such as importing data from .EAP files – it will be necessary to replicate the same identity settings from your old application pool to the new “Enterprise Tester” application pool.
Additionally, on 64bit machines, if you require either:
- To allow Enterprise Tester to address more then 4gb of memory.
- Require Enterprise Tester to use Native 64bit database drivers (such as Oracle 64bit ODP.Net drivers).
#2 – Web.config File Changes
In addition to to the application pool changes, there have been a number of changes to the web.config file – a number of redundant sections have been removed and everything now targets the new .Net Framework. Enterprise Tester’s installer will automatically upgrade the web.config file for you, removing / replacing sections as required.
Because of these changes though, if you wish to use a backed up web.config file from a previous Enterprise Tester install after installation of 4.1 or later, it is necessary to run the following command from your installation directory, to remove the redundant sections from the file:
c:\Program Files (x86)\Catch Limited\Enterprise Tester> PostInstallTasks.exe installation
Failure to do so will likely prevent Enterprise Tester from starting up correctly.
Alternatively if you are using the zip binary installation of Enterprise Tester, you need to run the following command from the \bin folder of your ET website installation’s \bin\ folder:
c:\inetpub\ET\bin\> PostInstallTasks.exe ziprelease
#3 – Installer Changes – IIS Site Detection and Configuration
As part of the version 4.1 release the Installation technology has been updated. Previously Enterprise Tester would always be installed to the site which had the following parameters:
- Port: 80
- IP Address: Any (unbound)
- Host header: None
This is no longer the case, and the installer will instead look for the website with the following name “Default Web Site”, regardless of port or bound IP Address. So, customers running Enterprise Tester on an alternative port (if port 80 is already in use), should now be able to upgrade via the installer without having to temporarily revert the port or host header.
Additionally our installer now automatically enables the ASP.Net 4 web service extension a step that had to be manually performed by users on older operating systems, such as Windows Server 2003.
Last of all, our installer no longer requires that IIS6 compatability extensions be installed in IIS, thus simplifying a common pitfall for customers installing onto machines where IIS is alread configured.
#4 – Bootstrapper Changes – SQL Server 2008 Express
The Enterprise Tester installer is split into two files; a bootstrapper (the file ending in the extension “.exe”, which is normally 600K in size ) and the installer itself (the file ending in the extension “.msi” which is aproximately 15-20mb in size). The bootstrapper takes care of installing the necessary prerequisites for an Enterprise Tester trial (.Net Framework, Windows Installer and Sql Server Express).
Prior to version 4.1 of Enterprise Tester this bootstrapper was incompatible with 64bit operating systems, due the use of Sql Server Express 2005 32bit. We have now updated the bootstrapper to target Sql Server 2008 Express and the installer will correctly handle installing the prerequisites for Enterprise Tester when doing a trial on 64bit operating systems, including Windows Server 2008 r2 and Windows 7 x64.
Note: For existing starter license users, installing version 4.1 via the bootstrapper will upgrade your version of Sql Server Express to 2008, this can be a time-consuming process. If you use Sql Server Express on your machine for any other applications, you may want to avoid this automatic upgrade. If so, we suggest manually installing the .Net Framework 4.0 and then launching the installation of Enterprise Tester via the .MSI file (don’t use the .exe bootstrapper) – Enterprise Tester version v4.1 is still compatible with Sql Server 2005 and above, as before.
We hope you enjoy this new version of Enterprise Tester. If you have any issues during the upgrade to version 4.1 please log your issue via our support page.
And also provide the following environmental details:
- Operating System (including if it’s a 32bit of 64bit edition).
- Old Version of Enterprise Tester.
- Version of Enterprise Tester being installed.
- Database being used, including version of both DB and Client (if different).
- Screenshot of the installation/startup error message.