Some upgrades, depending on the version you are upgrading from,
require that you check in all checked out documents before upgrading, to ensure
the integrity of master/reference document relationships. Exported documents
are not affected and can remain exported during the upgrade.
ProjectWise V8i (08.11.05.xx) introduced a file called file_name.fileinfo.xml, which gets created locally upon check out of a master document. Because of this change, upgrading a pre-V8i version ProjectWise database to the current version requires that you check in all checked out documents having references, raster references, or link sets before upgrading.
ProjectWise V8i (SELECTseries 1) (08.11.07.1xx) introduced the creation of shapefile sets and raster sets. Because of this change, upgrading a pre-V8i (SELECTseries 1) version ProjectWise database to the current version requires that you check in all checked out DGN documents having links to shapefiles and/or raster files (which have their own related files) before upgrading.
- Back up your existing database. A complete cold backup should be made and verified using the database vendor's recommended backup procedures.
- Back up all server-side ProjectWise configuration files, including DMSKRNL.CFG.
- Ensure that your database software is still supported in the current version of ProjectWise (see the readme - readme_ProjectWise.chm). Note that the suggestions in this upgrade planning document do not address the conversion between database types (for example, SQL Server to Oracle conversions, or vice versa).
- If there has been API-driven customization of your ProjectWise system, that customization will at a minimum need to be recompiled to be binary compatible with the current version of ProjectWise. Installers will need to be updated to properly register the customizations on the new ProjectWise clients.
- The administrative user performing the upgrade will need to have access to the top folder of the datasource. If you are concerned about whether this user has access, you may want to turn off that user's user setting, , before you begin your upgrade, then turn it back on after upgrade is complete.
The following installers from the current version of
ProjectWise can be used to automatically upgrade
an earlier version of the product to the current version, when the earlier
ProjectWise V8i or
An automatic upgrade will uninstall the earlier version and then install the new version. Note that you are not required to use the automatic upgrade feature; you can still use Programs and Features to manually uninstall the earlier version before installing the new version, if you prefer.
The ideal situation in which to use the automatic upgrade feature is when one of the above applications is the only application from ProjectWise V8i or later that is installed on the computer. If you have more than one of the above applications from the same ProjectWise V8i or later version installed, you must perform back-to-back upgrades of each application, as you cannot have applications from different ProjectWise versions installed and running on the same computer.Note: To upgrade an application not listed above, you must use Programs and Features to uninstall the existing version before installing the new version. If you have a mix of applications installed from the same V8i or later version (that is, some from the list above and some not), then it is recommended that you do not use the automatic upgrade feature for the applications listed above, and instead use Programs and Features to uninstall all applications from that release version before you install the new ones.Note: If you have a ProjectWise V8i or later application from the list above installed next to a pre-V8i version of the same application on the same computer, then it is recommended that you use Programs and Features to remove the pre-V8i version, before you can use the automatic upgrade feature to automatically upgrade the ProjectWise V8i or later version.