{"id":956,"date":"2014-08-29T22:13:29","date_gmt":"2014-08-29T22:13:29","guid":{"rendered":"https:\/\/ephesoft.com\/docs\/?p=956"},"modified":"2020-05-19T12:25:18","modified_gmt":"2020-05-19T19:25:18","slug":"upgrade-procedure-windows","status":"publish","type":"docs","link":"https:\/\/ephesoft.com\/docs\/products\/transact\/install-and-upgrade\/4-5-0-0\/install-upgrade-single-server\/upgrading-on-windows\/upgrade-procedure-windows\/","title":{"rendered":"Upgrade Procedure: Windows"},"content":{"rendered":"

Upgrade Procedure:<\/b><\/p>\n

1. Stop Ephesoft
\n2. Take a backup of the Ephesoft Installation Folder, SharedFolders and database.
\n3. Shutdown all Ephesoft related services and processes (e.g. soffice.bin)
\n4. Check that UAC is off and that the file is unblocked.
\n5. Run command prompt as administrator and run Ephesoft MSI Installer through following command.<\/p>\n

msiexec.exe \/i \u201c<Path to Ephesoft Installer>\u201d<\/b><\/i>\r\n<\/pre>\n
Optionally, to turn on installation logging (recommended for production upgrades):<\/p>\n
msiexec.exe \/i \u201c<Path to Ephesoft Installer>\u201d \/L*v “C:\\EphUpgradeLog.txt”<\/b><\/i><\/p>\n
6.Installer will check for .NET framework 4.5.1, if not present will stop the installation and would request user to install the same manually. Download link is provided along with the message.
\n<\/b><\/i><\/p>\n
7.The system will Check the pre-requisites for the upgrade only then Backup folders will be created.<\/p>\n
Note (System will also check the server.xml in addition to the registry entry for DB installation, both should match otherwise system will halt the install with the\u00a0error message “Installer has detected difference in selected database in Windows Registry and Installed Application. Please update the configuration to match each other and re-try the installation”<\/p>\n
8. Installer will detect your current installation and ask if you wish to apply the Database Patch (This will be checked by default,\u00a0Note: Only perform this update once when upgrading servers setup in a Multi-Server Environment<\/i>)<\/p>\n
9. If upgrading from an earlier version of Ephesoft before 4.0.3.0, you will need new licensing. Otherwise, your existing license file will be valid.
\n10. After installation is complete, please check our\u00a0Downloads and Updates<\/a>\u00a0page for cumulative updates between Service Pack versions that may be available. Before applying any further updates, ephesoft must start successfully at least once.<\/p>\n
11.\u00a0After performing an upgrade, any BI that was mid processing in the system would need to be restarted from Folder Import.<\/p>\n
Please Note<\/b>: Some newly added features will require reprocessing of your existing batch instances. Due to this it is recommended that you upgrade when your Ephesoft has no Batch Instances in queue.
\nFor Ephesoft Enterprise users:<\/b>\u00a0If you have any issues, please send the dcma-all.log files to Tickets@ephesoft.com<\/p>\n
Highly Recommended POST-UPGRADE Check<\/b>\u00a0Use Winmerge tool to compare settings from [backed up pre-upgrade] and [post-upgrade] META-INF config *.properties files and config *.xml files. Expect new line items in config files if upgrading to new version of ephesoft. Make adjustments to customized settings as found.<\/p>\n