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 [2024-02-26 12:11] (current) Jonatan Folger Asu |
||
---|---|---|---|
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** Lime CRM related (server, client and tools, e.g. Citrus). | + | - Perform [[installation: |
- | - Reboot the machine. | + | - Depending on which version is currently installed, see if there are some [[installation: |
- | - If HTTPS is used (through ldcws/Lime CRM Data Component Services) existing URL reservation and certificate bindings must be removed. Run these commands in an elevated command prompt:< | + | - [[https://platform.docs.lime-crm.com/en/latest/on-premise/solutions/# |
- | netsh http delete urlacl url=http://+:< | + | - Back-up the database. |
- | netsh http delete sslcert ipport=0.0.0.0:< | + | - Do the steps in this guide: [[kb: |
- | NOTE: Windows might refuse to accept | + | - Restart |
- | - Install according to the instructions in [[installation: | + | - Run the installer |
- | - First, register the database and then upgrade it, use [[configuration:limefu|Limefu]] and follow the instructions | + | - 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. | ||
- | <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 CRM Server User Account Credentials ==== |
- | </ | + | The installer application remembers the installation |
- | ===== Upgrading from version 12 or later ===== | + | ==== Go Through Release Notes ==== |
- | The installer application remembers | + | Read up on the [[releases: |
- | Follow these steps: | + | ==== Upgrade Add-ons ==== |
- | - Back-up | + | Go through all the add-ons that are installed in the Lime CRM application. Check [[addons:start|their documentation]] and see if there are new versions that could or MUST be installed. There are mainly two good reasons to also upgrade installed add-ons: |
- | | + | |
- | - Run the installer ('' | + | |
- | - Upgrade databases. | + | |
- | - Re-enable | + | |
- | | + | |
- | ===== Pre-upgrade preparations ===== | + | * The version that is installed for an add-on may not work anymore if the server is upgraded. |
- | Follow these steps to ensure that you' | + | * Doing a server |
- | ==== Close applications | + | ==== Check If Super Search Is Enabled |
- | Ensure that you don't have any of the following applications running: | + | Check if Super Search is enabled in Lisa. |
- | * Windows Task Manager | + | |
- | * Services Console | + | |
- | * Event Viewer | + | |
- | * Microsoft Management Console (MMC) | + | |
- | ==== Check port availability | + | ==== Use Latest Compatible Python Version |
- | If you see that Lime CRM Webfront is having problems starting, it most probably is due to the fact the port 443 is already in use by another process. Open a command prompt, | + | - Open cmd/ |
+ | - Write ‘python -V’ and press enter key to see Python version. | ||
+ | - If not using latest compatible version. Run the Python installer | ||
- | < | + | ===== Extra Upgrade Steps ===== |
- | netstat -nao | findstr LISTEN | + | When upgrading from some versions there are extra steps needed to complete the upgrade. |
- | </ | + | |
- | Ensure that there is no entry using port 443. These show up as '' | ||
- | ==== Uninstall old versions | + | ==== Upgrading From 2022.3 or Earlier |
- | Though it shouldn' | + | |
- | | + | **Python 3.11** is required from version 2023.1 and later of Lime CRM server. Follow the instructions [[installation: |
- | | + | |
- | | + | |
- | ==== Install Python 3.7.3 if upgrading from version < 12.51 ==== | + | **.NET 4.7.2** or later is required to run Lime CRM. **Recommendation is to run 4.8**. You can check which version |
- | <WRAP round info> | + | |
- | **Python 3.7 is required | + | |
- | From version | + | **Check SQL Server |
- | Instructions for how to install Python 3.7.3 is found [[installation: | + | **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 ('' |
- | </ | + | **Create a new search index**. You have to create a new search index with help of the command '' |
- | ===== Upgrading databases ===== | ||
- | All Lime CRM databases that are to be used after the upgrade must be migrated to the latest revision of the database schema. This is done using [[configuration: | ||
- | < | ||
- | limefu database upgrade --application " | ||
- | </ | ||
- | <WRAP round info> | + | ==== Upgrading From 2022.2 or Earlier ==== |
- | === Note! === | + | **Tips for the web client when upgrading** |
- | When upgrading databases, the user running | + | * 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:// |
- | </WRAP> | + | * 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? [[https:// | ||
- | ===== Create search index ===== | + | **Erlang and RabbitMQ Needs To Be Manually Uninstalled** |
- | 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: | + | |
- | < | + | Erlang and RabbitMQ needs to be manually uninstalled to get upgraded correctly by the Lime CRM installer. Follow this guide: [[kb: |
- | limefu search index --application " | + | |
- | </ | + | |
- | ==== Migrating file name data ==== | + | ==== Upgrading From 2021.1 or Earlier |
- | From Lime CRM Server | + | |
- | {{:installation:filename-migration-lime.zip|}} | + | ==== 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 99: | ||
{{: | {{: | ||
- | ===== 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 // | + |