Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
installation:upgrades [2020-07-13 08:26] Gustav Garmer |
installation:upgrades [2025-03-10 13:12] (current) Mikko Nukarinen |
||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== Server | + | ====== |
- | This page describes how to upgrade an existing Lime CRM Server installation. The upgrade procedure | + | This page describes how to upgrade an existing Lime CRM Server installation. The upgrade procedure |
+ | |||
+ | ===== Upgrade Steps ===== | ||
- | ===== Upgrading from version 10.11 or earlier ===== | ||
Follow these steps: | Follow these steps: | ||
- | - Completely uninstall **everything** | + | - From release 2025.1 onwards, old Lime Active Directory Integration |
- | | + | - Perform [[installation: |
- | - If HTTPS is used (through ldcws/Lime CRM Data Component Services) existing URL reservation | + | - Depending on which version is currently installed, see if there are some [[installation:upgrades# |
- | netsh http delete urlacl url=http://+:< | + | - [[https://platform.docs.lime-crm.com/en/latest/on-premise/solutions/# |
- | netsh http delete sslcert ipport=0.0.0.0:< | + | - Back-up the database. |
- | NOTE: Windows might refuse to accept | + | - Do the steps in this guide: [[kb: |
- | - Install according to the instructions in [[installation: | + | - Restart |
- | - First, register the database and then upgrade it, use [[configuration:limefu|Limefu]] and follow the instructions | + | - Run the installer |
+ | - Restart | ||
+ | - [[installation: | ||
+ | - [[https:// | ||
- Re-enable [[configuration: | - Re-enable [[configuration: | ||
+ | - Create or [[configuration: | ||
+ | - Verify that the upgrade has succeeded. E.g. test some basic functionality and important solution customizations. | ||
+ | - Update IT card in Sublime with new Lime CRM/server version and any other relevant information | ||
- | <WRAP round important> | + | If the upgrade fails or something doesn' |
- | === Warning! === | + | |
- | Ignoring steps 1-2 above may lead to a severely broken Lime CRM Server | + | |
- | </WRAP> | + | |
- | <WRAP round info> | + | ===== Pre-upgrade Preparations ===== |
- | === Note! === | + | The pre-upgrade preparations should be performed several days ahead of the actual server upgrade. |
- | When limefu upgrades a database used with Lime CRM Server version 10.11 or earlier, it will automatically apply a fix for document performance problems. This may take 30 minutes or more depending on the amount | + | Follow these steps to ensure that you're upgrade is successful: |
- | If you want to run this prior to upgrading | + | ==== Server requirements ==== |
+ | The server requirements gets updated on a regular basis. Go to the [[https:// | ||
- | {{:installation:lime_stats_hotfix.zip|Hotfix #15090}} | + | ==== Login ==== |
- | </WRAP> | + | Ladi has end of life planned for end of 2024, so make sure the customer uses something else. Check what other options there are in the list here on platform: [[https://platform.docs.lime-crm.com/en/ |
- | ===== Upgrading from version 12 or later ===== | + | ==== Lime CRM Server User Account Credentials |
- | The installer application remembers the installation configuration (e.g. user and group information) specified from the last time it was run, however, no passwords are remembered | + | The installer application remembers the installation configuration (e.g. user and group information) specified from the last time it was run. However, no passwords are remembered. So make sure you know the password for the Lime CRM Server |
- | Follow these steps: | + | ==== Go Through Release Notes ==== |
+ | Read up on the [[releases:pro: | ||
- | - Back-up the database | + | ==== Upgrade |
- | - Perform pre-upgrade preparations | + | |
- | - Run the installer ('' | + | |
- | - Upgrade | + | |
- | - Re-enable [[configuration: | + | |
- | - (Re-index the database if needed) | + | |
- | ===== Pre-upgrade preparations ===== | + | Go through all the add-ons that are installed in the Lime CRM application. Check [[addons: |
- | Follow these steps to ensure | + | |
- | ==== Close applications ==== | + | * The version |
- | Ensure | + | * Doing a server upgrade is the perfect time to also make sure the add-ons are up to date so the customer can enjoy the latest and greatest version of the Lime CRM software. |
- | * Windows Task Manager | + | * Also uppgrade or add limepkg-lisa to the solution |
- | * Services Console | + | |
- | * Event Viewer | + | |
- | * Microsoft Management Console (MMC) | + | |
- | ==== Check port availability | + | ==== Check If Super Search Is Enabled |
- | If you see that Lime CRM Webfront is having problems starting, it most probably is due to the fact the port 443 is already | + | Check if Super Search |
- | < | + | ==== Use Latest Compatible Python Version ==== |
- | netstat | + | - Open cmd/terminal/ |
- | </code> | + | - Write ‘python -V’ and press enter key to see Python version. |
+ | - If not using latest compatible version. Run the Python installer and click " | ||
- | Ensure that there is no entry using port 443. These show up as '' | + | ===== Extra Upgrade Steps ===== |
+ | When upgrading from some versions | ||
- | ==== Uninstall old versions ==== | ||
- | Though it shouldn' | ||
- | * Lundalogik Lime CRM Server (Lundalogik LIME Pro Server on older installations) | + | ==== Upgrading From 2022.3 or Earlier ==== |
- | * Erlang OTP | + | |
- | * RabbitMQ | + | |
- | ==== Install | + | **Python 3.11** is required from version |
- | <WRAP round info> | + | |
- | **Python 3.7 is required from version | + | |
- | From version 12.51 and later of Lime CRM Server, Python 3.7.3 needs to be installed | + | **.NET 4.7.2** or later is required to run Lime CRM. **Recommendation is to run 4.8**. You can check which version is running by following the instructions [[https:// |
- | Instructions for how to install Python 3.7.3 is found [[installation: | + | **Check SQL Server version** SQL Server 2017 or later is required, Lime CRM 2024.3 will __not__ work on SQL Server 2016 or older |
- | </ | + | **Remove the Elastic Search 5 data directory.** Prior to creating a new search index, it is necessary to manually delete the previous data directory associated with ElasticSearch 5 ('' |
- | ===== Upgrading databases ===== | + | **Create a new search index**. You have to create a new search index with help of the command '' |
- | All Lime CRM databases that are to be used after the upgrade must be migrated to the latest revision | + | |
- | < | ||
- | limefu database upgrade --application " | ||
- | </ | ||
- | <WRAP round info> | ||
- | === Note! === | ||
- | When upgrading databases, the user running the '' | ||
- | </ | ||
- | ===== Create search index ===== | + | ==== Upgrading From 2022.2 or Earlier |
- | If using the Lime CRM Web Client, the search index might need to be re-created. Note that this might slow down the solution for the users, it is recommended to do this after work hours, especially if it is the first time or a big solution. This is done using [[configuration:limefu|limefu]] with the following command (from version 12.4): | + | **Tips for the web client when upgrading** |
+ | * The new start page is turned on by default. Make sure it looks good and that all widgets (especially info tiles) have been moved to the new start page. [[https:// | ||
+ | * Over delivery: Add multiple start pages if you think your customer needs them. | ||
+ | * Over delivery: Remove unnecessary fields from create new dialogs. Calculated fields, read only field, " | ||
+ | * Over delivery: Does you customer have a lime type that hold hundreds of thousands or even millions of records? Is there no need to have that lime type searchable? | ||
- | < | + | **Erlang and RabbitMQ Needs To Be Manually Uninstalled** |
- | limefu search index --application " | + | |
- | </ | + | |
- | ==== Migrating file name data ==== | + | Erlang |
- | From Lime CRM Server 12.6, the file-API makes it possible to include the name of the document-file as a proper filename. When upgrading, already existing files do not have any filename, | + | |
- | {{:installation:filename-migration-lime.zip|}} | + | ==== Upgrading From 2021.1 or Earlier ==== |
+ | * Server version 2022.2.739 (2.308.3) and higher requires Lime CRM Desktop Client version of 10.18.962 or higher | ||
+ | |||
+ | ==== Upgrading From 13.2 or Earlier ==== | ||
+ | In older server versions, the packages for the [[https:// | ||
+ | |||
+ | ==== Upgrading From 12.50 or Earlier ==== | ||
+ | From version 12.51 and later of Lime CRM Server, Python needs to be installed prior to installation or upgrade of Lime CRM Server. | ||
+ | |||
+ | Instructions for how to install Python is found [[installation: | ||
- | ==== Migrating lime-views and configuration | + | ==== Upgrading From 12.7 or Earlier |
From Lime CRM Server 12.9, lime-views and some configuration is stored in the database instead of in files. | From Lime CRM Server 12.9, lime-views and some configuration is stored in the database instead of in files. | ||
To migrate existing lime-views and configurations, | To migrate existing lime-views and configurations, | ||
Line 110: | Line 105: | ||
{{: | {{: | ||
- | ===== Troubleshooting ===== | + | ==== Upgrading From 12.4 or Earlier |
- | Some tips: | + | From Lime CRM Server 12.6, the file-API makes it possible to include the name of the document-file as a proper filename. When upgrading, already existing files do not have any filename, and if you want to set the filenames on the already existing files you need to run the following SQL-script. The script set the filename to the text in the field [description] on the document-table, |
- | * Don't manually delete directories and files if you're not really sure what the consequences are. | + | {{: |
- | * Check out [[kb:10012|RabbitMQ cannot be started after an upgrade of Lime CRM]] or [[kb: | + | |
- | + | ||
- | + | ||
- | ===== Active Directory Integration ===== | + | |
- | A new feature has been added to the [[configuration: | + | |
- | + | ||
- | Consider the following scenario: | + | |
- | + | ||
- | >The AD group // | + | |
- | + | ||
- | Since authorization starting with Lime CRM Server version 12 no longer uses the // | + | |
- | + | ||
- | * The AD group // | + | |
- | * The AD group //Lime CRM Users// must be mapped to the Lime CRM group //Users// with auto-create activated. | + | |
- | + | ||
- | Now everything will work in the same way as before, minus the extra complexity of the // | + |