This document describes how to update Promis.e V8i to the latest version. To upgrade from versions prior to Promis.e V8i, please see Migrating Legacy Data To promis.e. If moving to a new PC, see the Moving Projects article. If moving from Promis.e for AutoCAD, see the Moving From Promis.e for AutoCAD to Promis.e Standalone article.
Users have historically been able to update their Promis.e software by installing a service pack, or patch. Upgrading to the next major release of Promis.e has been achieved by installing an entirely new piece of software with a "full install" file.
It was not possible to update promis.e V8i to SELECTseries 3 through 7 via a service pack or patch since these versions are only available as full installs.
Beginning with Promis.e V8i SELECTseries 7 Refresh 2 (08.11.12.101), it is possible to update the software to some newer versions from a previous version by installing a patch. These patches can only be applied to specific versions. For example, clicking on Promis.e V8i Update 1 (English) 32-bit in the download center opens a pop up that includes "This update (v08.11.13.96) is being made available exclusively for updating Promis.e V8i (SELECTSeries 8) 08.11.12.57. This update cannot be applied to any other version of Promis.e V8i." If downloading a patch, be sure to download the patch appropriate for the currently installed version (see the About Promis.e dialog). Patches can typically be only applied to versions in the same SELECTseries (you cannot patch SS7 up to SS8).
If a patch update installation file is not available for your currently installed version, download the full install file.
Before performing any update or upgrade, it is always a good idea to Backup Your Data, and to make sure the system, platform, and database requirements of the new version are met. What is compatible for your current version may not be compatible with the new version.
To update the currently installed version of Promis.e V8i to the latest version, use the following process:
Open the currently installed Promis.e application.
Navigate to the Promis.e Setup dialog and make note of the values in the Server Name and Database fields in the Project Database area. This is the database where the information for all projects currently accessible in Project Manager is stored. Also make note of the file or connection string used for the parts database, what paths are found in the Catalog Paths and their order, what the Data Folder Path is, etc.
The new version of Promis.e will typically ask if the project database should be backed up before it updates the database schema to match the new version. However, it is still a good idea to make backups of projects using Project Manager > File > Backup, at least for critical projects, before uninstalling the existing version. Projects backed up in this manner can be restored into a new database if this becomes necessary. Alternatively, it is also possible for someone with SQL experience to backup the project data by making a copy of the project folders and
This method would normally only be used when there are very many projects to preserve that do not have current backups (.PRJ) created using Project Manager.
Make a backup copy of supporting data (catalogs, templates, parts database, etc.). This data may or may not be limited to the data contained in the promis-e Data folder, so check the paths on the Setup dialog. Catalogs can also be exported to an archive file using Catalog Manager.
If upgrading via a full install (not a patch or Update file), uninstall the current version of Promis.e V8i using Add or Remove Programs / Uninstall a Program in the Windows Control Panel.
(Optional) If upgrading via a full install (not a patch or Update file), force a new "promis-e Data" folder with any updated items be created during installation, rename the existing local promis-e Data folder. Alternatively, specify a unique data folder path during installation. The default path with the new version may be different than the existing data folder. After installation is complete, customized data can be copied into the new data folder, and for multi-user environments, the new data folder can be copied to a shared location. Note: project folders should not be copied, they should be moved to avoid multiple instances.
Install the new Promis.e V8i version or Update as the case may be. Some older versions of Promis.e create a new, local, empty project database that the new version will automatically connect to. If so, previously created projects will be inaccessible in Project Manager, since the new database is empty. Specify the correct database in the following steps.
Start the new Promis.e and navigate to the Setup dialog. Enter the server name and database name noted in step 2 into the Project Database tab. Click Apply or OK. Note: in most cases this should be done after all the workstations using this database have been upgraded to the new Promis.e version.
If the program returns a "Database version does not match the application" message, update the database noted in step 2. Be aware that some earlier Promis.e V8i versions will attempt to update the database automatically when an out-of-date database is specified on Setup. The only prompt may be whether or not projects will be backed up in the process. The database can also be updated by using methods described in the Creating and Updating the Project Database article.
If upgrading to Promis.e V8i SELECTseries 8 or higher from Promis.e V8i SELECTseries 7 or lower, a service request must be submitted to have the new product code added to your contract. Until the new product code is added to your contract the new software will not activate and you will be limited to a 7 day trial period. See the Cannot activate Promis.e V8i SELECTseries 8 after upgrading.
In multi-user environments where the users share a common project database, installing the new version of Promis.e on each workstation will need to be a coordinated effort if updating the shared database is required. An existing database cannot be used by the new version of Promis.e until it is updated, and once it is updated it cannot be used by the old version. When trying to connect with the wrong version of Promis.e, a Database version does not match the application message may appear and projects will be inaccessible in Project Manager.
A variation on the above process is to create a new project database (compatible with the new version) instead of updating the existing database. Project backups (made in step 3) would then be restored while Promis.e is connected to the new database. See Creating and Updating the Project Database once again for details on creating project databases. The action for step 8 would be to point Promis.e to the new project database on the Setup dialog. Having new and old databases may be useful in multi-user environments where coordinating the update process is difficult, or where one workstation is to be updated for testing prior to rolling the software out to all users.
A setup.xml file from the older version of Promis.e can typically be put back in place after upgrading to restore the previous configuration without issue. It is recommended that the setup.xml file from the new version be backed up first and its replacement tested before distributing to other users.
Compatibility Chart - Promis.e V8iCompatibility Chart - Promis.e CONNECT
How to download the Promis.e software
Creating and Updating the Project Database
Error - Database version does not match the application
Project Database Version - Promis.e
Moving Projects
Moving From Promis.e for AutoCAD to Promis.e Standalone
Cannot activate Promis.e V8i SELECTseries 8 after upgrading