Lime CRM Desktop Client 11.1.2935
Product Lime CRM Desktop Client Version 11.1.2935 Date published 2023-06-19 Platform Windows Availability Manual installation and Automatic Updates.
Intermediate release, please use 11.1.2937 instead.
Product Lime CRM Desktop Client Version 11.1.2935 Date published 2023-06-19 Platform Windows Availability Manual installation and Automatic Updates.
Intermediate release, please use 11.1.2937 instead.
Product Lime CRM Desktop Client Version 11.1.2937 Date published 2023-06-19 Platform Windows Availability Manual installation and Automatic Updates.
This release is a wrap-up release backporting improvements and stability fixes from Insider.
These fixes has been made to the installer:
90421efef326_lsp_populate_updatelog_dataafter.py
and 600c5124e34e_lfn_getonsqlupdate_upgrade.sql
can now run on SQL Server 2014.+
button on tabs.DuplicateTargetEntries
. By default the SCIM implementation in Lime CRM exposes users and groups using only their record ids. This does not work in situations where a user and group has the same id. This version introduces an optional configuration flag to use unique ids instead, but doing so requires the SCIM process to be restarted, read the platform docs for more information.The incoming request has too many parameters. The server supports a maximum of 2100 parameters. Reduce the number of parameters and resend the request.
. This has been reported for an internal application with a very large amount of lime types and properties. A simple batching of the queries is now in place.Improved caching Large objects retrieved from Redis will now be cached locally as files to reduce internal network traffic. Previously this caching was only used when Redis was not available with the general assumption that Redis, especially when hosted on the same machine, will be faster than accessing the local filesystem, which may be on remote SAN. General caching rules have also been simplified to only use size to determine if memory or file should be used.
No more session-lists LDC will no longer use session lists to validate session identifiers or timestamps. The validation is now done per individual session instead. This will reduce overhead for loading, searching and caching huge XML documents. This change will (for good and bad) effectively disable any implicit housekeeping performed by lsp_getxmlsessionlist.
Bugfixes for batched updates from LISA Saving changes from LISA occasionally result in error messages, even that the update was successful. The root cause was that some changes triggered invalidation of the helper object, and this invalidation apparently included the session identifier. However, this only result in error if auditing was enabled for the operation, which depend on settings but also threshold values and database response time.
Modern API for Windows-based login Switched from Window 2000 era APIs to modern Windows APIs. This should result in better error messages for AD-based accounts.
could_not_determine_disk_free
. This is supposedly fixed in a later release of rabbitmq so we include that in the installer. For upgrades run the rabbitmq installer manually, it is available at C:\Program Files (x86)\Lundalogik\LIME Pro Server\webserver\externals\
Make sure that all Windows Management Console application (like windows event log, computer management etc.) are closed.
Uninstall Erlang (using Control Panel is fine)
Uninstall RabbitMQ (using Control Panel is fine)
Open a command prompt as admin and run
C:\Program Files\erlx.y.z (x.y.z could be any version number)
C:\Program Files (x86)\Lundalogik\Lime Pro Server\Erlang
C:\Program Files (x86)\RabbitMQ
C:\Program Files (x86)\Lundalogik\Lime Pro Server\RabbitMQ
%appdata%\rabbitmq
%programdata%\Lundalogik\LIME Pro Server\RabbitMQ
The folder ErlSrv might not exist in WOW6432Node which is fine.
Restart the server.
Run the Lime CRM Server installer.
Can not delete Erlang directory on step 5 in the guide. Open Task Manager and kill these processes:
If you still cannot delete Erland directory, try killing tasks run by Lime Service User and restart the server (Windows).
Event Handler crashes and the Event Handler log is printing this error message:
ConnectionRefusedError: [WinError 10061] No connection could be made because the target machine actively refused it
Erlang and RabbitMQ has not been uninstalled and installed correctly. Redo all the steps from the guide above.
If the installer fails to start the webfront service during the installation process with error code 3221225781
it is mean the required runtime dlls hasn't been installed.
Since the first installer release for 2023.1 Hvannadalsnjukur doesn't include the Visual C++ 2010 x86 Redistributable you will need to install this manually from https://download.microsoft.com/download/1/6/5/165255E7-1014-4D0A-B094-B6A430A6BFFC/vcredist_x86.exe and then re-run the installer.
Later installer releases for 2023.1 Hvanndalsnjukur will include this.
Microsoft has released version 114.0.1823.37 of a component that the Desktop Client depends on - the WebView2 Runtime. This version of the WebView2 runtime contains a regression that makes the Desktop Client crash during startup. An issue has been open with Microsoft and others have been reported affected.
For corporate customers with controlled IT environment we currently advise them to stop automatic updates until either the workaround have been distributed or a fully functional build of WebView2 have been released.
Microsoft have released a new build (114.0.1823.43 and later) that should resolve the underlying issue. This update will roll out via automatic updates and should reach most users 9-11th of June 2023.
We have developed two different solutions to the problem. Both solutions expect the auto update feature to be installed in your environment. By using the auto update feature the user does not need admin rights and the patch can be installed by the user them self.
We have applied a work-around to our latest stable version of Lime CRM Desktop - version 11.1.2918
. You can download a special installer that installs this version by clicking on this link.
Make sure that you shut down the desktop client before running the installer. Run the installer by double clicking on it and follow the steps described. You should now be able to use the Desktop Client again.
This is the recommended solution to the problem.
This solution should be used if you want to continue to use an older version of the Lime CRM Desktop client. The solution is compatible with Version 11.0 or greater of the Lime CRM Desktop Client.
This solution will apply a hot-patch to the existing installation, effectively replacing the DLL files that is responsible for communicating with WebView2.
Follow the guide below, in order to apply the hot-patch:
The instructions provided in this section is intended to be read by IT Administrators that needs to bulk update installations in their organisation.
It's possible to perform silent installations of the fixes described above. The only thing you need to do is to add the /VERYSILENT
flag to the installer:
or
Some organisations have disabled the service that makes it possible to auto update Lime CRM Desktop. The fixes described above does not work in those cases. In those cases, you have the following options:
We have applied a work-around to our latest stable version of Lime CRM Desktop - version 11.1.2918
. You can download the latest stable version by clicking on this link.
If you manage a large amount of client installations, instructions for deployment or automated installation of the Desktop Client can be found here.
This solution should be used if you want to continue to use an older version of the Lime CRM Desktop client. The solution is compatible with Version 11.0 or greater of the Lime CRM Desktop Client.
This solution will apply a hot-patch to the existing installation, effectively replacing the DLL files that is responsible for communicating with WebView2.
Follow the guide below, in order to apply the hot-patch:
hot-patch.zip
file (hot-patch.zip) and extract the zip file.~~=== Alternative solution 3: Downgrade WebView2 ===
This solution is more advanced and should only be applied if you have to use an older version of the Lime CRM Desktop Client. Please beware that this solution will install a fixed version of the WebView2 runtime. This means that you will not get security updates from Microsoft for this release.
== Prerequisites ==
These instructions are intended for System Administrators with basic knowledge about PowerShell scripts.
You need to have Administrator privileges to apply this fix. Your Administrator must have full access to C:\Program Files(x86)\Lundalogik (the folder where Lime CRM is installed). (You must modify the script your self if you have installed Lime CRM somewhere else.
== Instructions ==
C:\tmp\webview-fix.ps1
. If you're using a 32 bit architecture, please modify the first line of the script and set it to “x86”.
$ARCH=“x64”
$NAME=“Microsoft.WebView2.FixedVersionRuntime”
$VERSION=“113.0.1774.57”
$FULL_NAME=“$NAME.$VERSION.$ARCH”
$WEBVIEW2_URI=“https://builds.lundalogik.com/api/v1/builds/$NAME.$ARCH/versions/$VERSION/file/” $DOWNLOAD_DEST=“$env:temp\webview2.cab” $LIME_CRM=“${Env:ProgramFiles(x86)}\Lundalogik\Lime CRM”
$ProgressPreference = 'SilentlyContinue'
Invoke-WebRequest -Uri $WEBVIEW2_URI -OutFile $DOWNLOAD_DEST
expand “$DOWNLOAD_DEST” -F:* “$LIME_CRM”
if (Test-Path “$LIME_CRM\WebView2”) { Remove-Item “$LIME_CRM\WebView2” -Recurse -Force }
Rename-Item “$LIME_CRM\$FULL_NAME” “$LIME_CRM\WebView2” ~~
Product Lime CRM Desktop Client Version 11.1.2885 Date published 2023-04-24 Platform Windows Availability Manual installation and Automatic Updates.
Product Lime CRM Desktop Client Version 11.1.2918 Date published 2023-06-05 Platform Windows Availability Manual installation and Automatic Updates. Patch Manual installation for non-administrators
This is a roll-up patch release that include a workaround for problems introduced by Microsoft WebView2 Runtime 114.0.1823.37. See related knowledgebase article for alternative solutions.
Product Lime CRM Desktop Client Version 11.1.2924 Date published 2023-06-10 Platform Windows Availability Manual installation and Automatic Updates.
This release target problems seen after using fixed version override for Microsoft WebView2 Runtime.
The new search of the web client requires you to do a manual re-index after upgrade. This is done using limefu.
Python upgrade. Follow the installation guide.
We added the possibility to turn of database customizations on save. This will reduce the complexity and database traffic when saving objects. The benefits are:
Faster save
Reduced risk of deadlocks in the database
Less load on the database
This feature can be enabled with the feature flag run_sql_customizations_on_update set to false. It will then disable these SQL customizations:
csp_beforeupdate, csp_afterupdate, csp_afterdataupdate and csp_afterupdatecompleted.
SQL for update.
Update if relation has changed.
The main replacement at the moment where logic should be moved instead is Custom Limeobject.
Users and Groups are now managed in Lime Admin. Hold on to your hat because it has never been smoother nor faster to work with Users and Groups in CRM!
You will be able to do everything you can do in LISA for Users and Groups, such as:
Create users
Create groups
Add users to groups
Set passwords
Create API users and API keys
Deactivate and delete users
and more
Read more in our docs.
With this new feature, we also have the possibility to do all of these things via our API. Click User menu ➡ API Documentation. 🤘
The search which is used by the web client is faster, more reliable and future-proof. We are now using Elastic 7 instead of Elastic 5.
We have crushed a few bugs and doing indexing in a better fashion. Re-indexing is faster and not necessary to do as often. This means that if a property (also called field) on a limetype (table) is changed, deleted or added in LISA, a reindex of that limetype is NO LONGER required.
Select how you want to present time and dates. For example 2023-03-31 or 31.03.2023 for dates and 13:37 or 1:37 PM for times.
Enabled using feature switch useUserPreferences
We have a new, smooth and lean to-do workflow ready for you. Gone are the big modals with too many choices.
New postpone component. Fast, light and smooth. 😻
Quick note. Quickly add a history note with minimum amount of clicks. 💥
Mark as done with the option to Add next todo from a snackbar. No big modal that you need to dismiss every time. 🤘
When adding the new todo, we use the normal form. Which means: same layout, same features, auto-attach, hide fields, etc. works. 🙏
Add next todo from button in widget slot. If you want more than the Add next todo in the snackbar, you can add a button called Add next todo to the card, that's always present for done to-dos. ✅
Enabled by setting the feature switches useNewMarkAsDone and useNewTodo set to true. And add the web component limec-quick-note to the To-do card.
Possibility to add prepare_update() hook for Custom Limeobject, which runs before the database transaction starts. Which could reduce the risk of deadlocks in the database when saving.
Lime Admin has received some love and care. A better code editor and much more compact layout are two much requested features.
Lime Admin now works on phones. If you're on the run and need to add a column to a table view -- now you can.
Bulk update turned on everywhere. Previously, you needed to switch Bulk update on for each lime type. Now, Bulk update is available for all lime types by default. You can inactivate it for certain lime types or user groups if you wish.
Navigate to your profile (coworker) card via the user menu.
Set default filter set for explorer (to-do) widget using the parameter filterId.
Date picker for weeks looks different second time opened.
Text is column filters gets deleted for relation fields.
Separate settings for Global Search: one for The Search and one for relation fields.
Option queries should not be applied to column filter pickers.
Slow relation picker and wrong results.
Save via web component should only save specific fields.
Avoid loading web components twice
Sales pipe widget having proper translations for Finnish.
Variant not working when variant field is "a relation away".
"Clear column filter" redirects to start page
SUM in tables not working properly
You can't save a filter when using "show connected"
Content in tabs does not load until you press 🔃
Fields that should be read-only due to policies are not read-only
Users can mark todo-s as done even though they only have read access
Options that are not updated does not show up when searching
It is now possible to login even if you are a member of 100+ groups
Tasks triggered by API-keys now get the database default language, previously they reused the language they had last time. But if that language had been disabled they got incorrect data model information.
The system is now much faster to rebuild its cache when a table is changed in LISA.
SCIM once again refreshes member cache when groups members are updated. This was a regression in Rysy.
SCIM doesn't update databasetimestamp (which invalidates most internal caches) unless it has too.
Performance has been slightly improved when saving relations between objects.
System is better at detecting when a sql-on-update customization isn't working and abort the entire save operation.
The [key] column in [sys_data] is now much bigger allowing addons to be much more specific when saving user data.
Calls to /ldc/LDC.Database/ExecuteBatch can no longer save the updates if something else goes wrong.
LDC - 12.9.1893
LISA - 12.8.35
Elastic Search - 7.17.9
Java Development Kit (JDK) - 8u111
Ngnix for Windows - 1.23.3.1 SnapDragonfly
NSSM - 2.21-134
WinSW 2.12.0
Microsoft ODBC Driver 18 for SQL Server (MSODBCSQL18) - 18.0.1.1
Microsoft Visual C++ 2015 x86 Redistributable (VC Redist) - [14.34.31938.0]{.mark}
Microsoft Visual C++ 2015 x64 Redistributable (VC Redist) - 14.0.23026.1
Microsoft Visual C++ 2010 x86 Redistributable (VC Redist) - 10.0.40219.325 (Required by Nginx For Windows)
Microsoft OLE DB Driver 19 for SQL Server
Erlang OTP - 25.0.2
RabbitMQ Server - 3.10.5
Microsoft Handle (sysinternals) - 5.0
Erlang and RabbitMQ needs to be manually uninstalled to get upgrade. Check version first, if it's the same versions installed no action is needed. It's optional to upgrade. If upgrading, both Erlang and RabbitMQ needs to be upgraded. Instructions can be found here: Uninstall Erlang and RabbitMQ when doing Lime CRM Server upgrade
Lime CRM now requires Python 3.11 on-premise. The new python version must be installed before running the installer. Any pre-existing Python 3.7 should be left where it is.
The installer uses the py
launcher to make sure its starting Python 3.11, even if 3.7 is before it in the PATH
.
The venv
created for Lime CRM is now called lime_crm_venv
and is created by Python's built in venv
module, previously it was created by virtualenv
and called Python3
.
Solutions must be built for python 3.11 before they can be installed.
This release comes with Elastic Search 7 only. Previously Elastic Search 5 was used.
The new version enables many optimizations and is used slightly different. More detailed info can be found here.
Important information:
%LIME_HOME_PATH%\Elasticsearch\data
) associated with ElasticSearch 5. Otherwise, old indexes built for ElasticSearch 5 will remain on the server and take up disk space and interfere with the new installation.JAVA_HOME
system environment variable in your system configuration. If such a variable exists, kindly remove it to ensure proper functionality (the installer will fail if this variable is set). For instructions on modifying system environment variables on a Windows computer, please refer to the following external resource: Modifying Environment Variables on WindowsSome of the services installed by Lime CRM has changed names in this version. Further the import- and task handler services has been split into two services each.
Lime services (2023.1):
lime-event-handler
)lime-crm-importer-1
)limecrm-scheduler
)lime-crm-search-indexer
)llab-lisa
)lime-task-scheduler
)lime-task-handler-1
)lime-crm-webfront
)lime-crm-webserver
)Lime Component Services (2023.1):
We have updated all our Python services to be run as a service with WinSW. This is a change compared to previous versions where some services were installed via a python win32 library from lime-core and some using NSSM.
WinSW is installed in C:\Program Files (x86)\Lundalogik\LIME Pro Server\Lime Services
. There is one exe
and xml
for each service. These files are not meant to be edited and will be overwritten by the installer.
The logging for all Python services is now written to file directly from lime-core, previously it used stdout and was written to file by nssm
. This has the benefit that they can all be configured in the same way.
Read more about the logging configuration.
The convenient command prompt on the desktop now has access to both limefu
and lime-project
at the same time without having to activate any extra venvs.
In this version of Lime CRM, we have updated the SQL driver. Previously, the SQL Server Native Client was used. But from now on, LDC uses the Microsoft OLE DB Driver when connecting to the SQL server.
The SQL Server Native Client has been removed from SQL Server 2022 (16.x) and SQL Server Management Studio 19 (SSMS) and is no longer recommended to use by Microsoft.
The task handler, task scheduler and importer are Celery applications. Celery has not received the necessary patches from its maintainers to enable all its features when running Python 3.11 on Windows yet so in this release we opt to run in threads
connection mode.
Lime CRM Webserver is a python based WSGI Server. We have changed the WSGI server that Lime CRM is run with from Cheroot to Waitress.
Newer versions of RabbitMQ requires the program Handle.exe
to work properly. This software is automatically installed when you install this version of Lime CRM Server.
What is Handle?
Handle is a utility that displays information about open handles for any process in the system. You can use it to see the programs that have a file open, or to see the object types and names of all the handles of a program. Read more here
The installer now enables LongPathsEnabled
in the registry.
Below is a list as originally shipped with 2023.1: