Skip to content

Lime CRM Knowledge Base

Lime CRM 2022.3 - Rysy - Patch 6

Description

This is the sixth patch release of 🇵🇱Lime CRM 2022.3 Rysy.

Patch Upgrade Instructions

If upgrading to this release from:

🪲 Fixes

##

  • Fix so that the Lime CRM Active Directory integration works again.
  • The installer will ensure that the correct version of Microsoft Visual C++ Redistributable package is installed on your machine.
  • It will throw an error and crash if your .NET version is too old. You need to manually upgrade it if this happens. Recommendation to run version 4.8.

Lime CRM 2022.3 - Rysy - Patch 5

Description

This is the fifth patch release of 🇵🇱Lime CRM 2022.3 Rysy.

Patch Upgrade Instructions

If upgrading to this release from:

🪲 Fixes

RabbitMQ expects Handle.exe

Needs a manual fix, please see:

RabbitMQ logs an error message every 5 minute in its log file [Lime CRM Wiki] (lime-crm.com)

SQL Driver

The installation step for SQL Native Client has been improved. Before this fix, the installer checked for the current installed version in the wrong place in the Windows Registry. This caused the installer to sometimes not upgrade the SQL Native Client version. This has been fixed in this version.

Event-handler

Ensure that the event-handler service don't crash when the body of a message sent to it is of an unknown type. The Rysy release introduced a regression which meant that you couldn't send a body of type string or list to the event-handler. This has been fixed in this release and everything should work as before Rysy again.

Http API

We have fixed a regression where the error code 400 was returned instead of error code 422 when the parsing of a request failed on the server.

Elasticsearch-dsl5

We have updated the version of this package. The previous package defined it's dependencies in a format that is no longer considered valid, which caused the installation step to sometimes fail. This has been fixed in this release.

RabbitMQ logs an error message every 5 minute in its log file

Issue

After installing Lime CRM Server 2022.3 (Rysy), Rabbit MQ started to log the following error in it's log file every 5 minute:

[error] <0.547.0> Could not find handle.exe, please install from sysinternals

Why does this happen?

New versions of Rabbit MQ expects Handle.exe to be installed. Handle.exe is required by RabbitMQ to work properly with Windows file descriptors. This version of Lime CRM Server does not install it. Future versions of Lime CRM Server will automatically install it.

How to solve it?

  1. Download Handle.exe installation file: http://technet.microsoft.com/en-us/sysinternals/bb896655.
  2. Extract Handle package to C:\Program Files\Handle and add this path to the system PATH in Environments settings.
    1. Open File Explorer and right click on “This PC”. Click on “Properties”
    2. Click “Advanced system settings” in the left panel.
    3. Click “Environment Variables…”
    4. In the lower list (System Variables) find “Path” and highlight it, click on “Edit…”
    5. Click “New” in the top right corner and paste in C:\Program Files\Handle
    6. Click “OK”
    7. To check if it's correctly added to path. Open CMD and run “handle”. If you don't get an error and a program starts it's all set. Exit the program.
  3. Restart RabbitMQ

Lime CRM Desktop Client 11.1.2847

Product Lime CRM Desktop Client Version 11.1.2847 Date published 2023-03-22 Platform Windows Availability Manual installation and Automatic Updates.

Fixes

  • Added error message for rename.
  • Improved handling of long filenames
  • Default to ID for description for limetype with empty descriptive expression.
  • Switched to string marshaling for errors.
  • Improved robustness for invalid default values.
  • Ensure default value is saved also for linked fields.
  • Improved robustness for automatic upgrade when logging or usage feedback fails.
  • Handle modifications to new record as default values if restored.
  • Improved robustness to better handle recreating WebView2 after upgrade.
  • Added recommendation for corrupted session list.
  • Ensure coworker record is fully populated.
  • Use singular health check during startup.
  • Verify file size in Document.CheckIn
  • Improved performance for accessing record description by populating cache during load. The primary goal is to speed up validation of relation fields.

Lime CRM Desktop Client 11.1.2856

Product Lime CRM Desktop Client Version 11.1.2856 Date published 2023-03-28 Platform Windows Availability Manual installation and Automatic Updates.

Features

  • Added tooltip for partially visible content in lists

Fixes

  • Ensure template record is validated before template is populated.
  • Reduced memory usage for large documents.
  • Worked around issues related to control-state if record is refreshed without triggering controls-level refresh.

Lime CRM Desktop Client 11.1.2863

Product Lime CRM Desktop Client Version 11.1.2863 Date published 2023-03-29 Platform Windows Availability Manual installation and Automatic Updates.

Fixes

  • Worked around problems with orphaned sessions that could be revived by calling /client/logout/ to properly terminate the flask session.
  • Fixed problem with “No database”-error for partial command line arguments.
  • Worked around problems with different casing for locales.
  • Use wait cursor for events.
  • Avoid triggering events for closed inspector.
  • Force “send and receive” in Outlook to avoid outgoing messages from MAPI/Redemption “stuck” in Draft-folder.
  • Refactored client-side batching for statefull calls to preseve backend errors.
  • Improved robustness for creating Outlook.Application via COM.
  • Fixed resource leak and improved robustness.

Lime CRM Desktop Client 11.1.2869

Product Lime CRM Desktop Client Version 11.1.2869 Date published 2023-03-30 Platform Windows Availability Manual installation and Automatic Updates.

Fixes

  • Updated dependencies WebView2, Sentry and .Net modules
  • Avoid race-conditions for accessing template-based properties.
  • Ensure WebView2 become visible after upgrade.
  • Improved stability for callbacks in WebView2.
  • Fixed potential crash during update for orphaned record that was previously added or deleted.

Lime CRM Desktop Client 11.1.2875

Product Lime CRM Desktop Client Version 11.1.2875 Date published 2023-04-11 Platform Windows Availability Manual installation and Automatic Updates.

Fixes

  • Updated validation to for options to accept inactive values since that was implicitly supported due to bugs in old versions.
  • Worked around race-conditions for sequence calls to Record: Open, Delete, Update
  • Fixed comparison misstake for language settings.

Lime CRM 2022.3 - Rysy - Patch 4

Description

This is the fourth patch release of 🇵🇱Lime CRM 2022.3 Rysy.

Patch Upgrade Instructions

If upgrading to this release from:

🚨 Known Issues

Event-handler service

A bug in the event-handler service. The work around for now, is to change so that you only publish events with dicts as payloads.

RabbitMQ expects Handle.exe

Newer versions of RabbitMQ, expects Handle.exe to be installed. RabbitMQ will work, even though it’s not installed, but it will log an error every 5 minutes in its log file with a message that looks like this [error] <0.753.0> Could not find handle.exe, please install from sysinternals. The next version of Lime CRM Server will fix this issue. If you are installing Rysy in the upcoming weeks, we recommend that you manually install Handle.exe by following the instructions here: https://docs.lime-crm.com/kb/10050.

🪲 Fixes

LDC

LDC upgraded to version 12.9.2816. Highlighted improvements are:

  • Fixes some memory leak issues

Read full release notes here: LDC 12.9.2816 Release Notes

Lime CRM Server Installation Fails to Install lime-webserver.exe

Issue

Lime CRM Server installation fails when trying to install lime-webserver.exe with 'InvalidRequirement' exception. Example from Lime CRM Server installation log:

11:52:51: INFO: Installing lime-webserver.exe service...
Traceback (most recent call last):
  File "c:\progra~2\lundal~1\python3\lib\site-packages\pkg_resources\__init__.py", line 3039, in _dep_map
    return self.__dep_map
  File "c:\progra~2\lundal~1\python3\lib\site-packages\pkg_resources\__init__.py", line 2835, in __getattr__
    raise AttributeError(attr)
AttributeError: _DistInfoDistribution__dep_map
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
  File "c:\progra~2\lundal~1\python3\lib\site-packages\pkg_resources\_vendor\packaging\requirements.py", line 35, in __init__
    parsed = parse_requirement(requirement_string)
  File "c:\progra~2\lundal~1\python3\lib\site-packages\pkg_resources\_vendor\packaging\_parser.py", line 64, in parse_requirement
    return _parse_requirement(Tokenizer(source, rules=DEFAULT_RULES))
  File "c:\progra~2\lundal~1\python3\lib\site-packages\pkg_resources\_vendor\packaging\_parser.py", line 82, in _parse_requirement
    url, specifier, marker = _parse_requirement_details(tokenizer)
  File "c:\progra~2\lundal~1\python3\lib\site-packages\pkg_resources\_vendor\packaging\_parser.py", line 120, in _parse_requirement_details
    specifier = _parse_specifier(tokenizer)
  File "c:\progra~2\lundal~1\python3\lib\site-packages\pkg_resources\_vendor\packaging\_parser.py", line 209, in _parse_specifier
    tokenizer.consume("WS")
  File "C:\Program Files\Python37\Lib\contextlib.py", line 119, in __exit__
    next(self.gen)
  File "c:\progra~2\lundal~1\python3\lib\site-packages\pkg_resources\_vendor\packaging\_tokenizer.py", line 185, in enclosing_tokens
    span_start=open_position,
  File "c:\progra~2\lundal~1\python3\lib\site-packages\pkg_resources\_vendor\packaging\_tokenizer.py", line 166, in raise_syntax_error
    span=span,
pkg_resources.extern.packaging._tokenizer.ParserSyntaxError: Expected closing RIGHT_PARENTHESIS
    pytz (>dev)
         ~^
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
  File "C:\Program Files\Python37\Lib\runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "C:\Program Files\Python37\Lib\runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "C:\PROGRA~2\LUNDAL~1\Python3\Scripts\lime-webserver.exe\__main__.py", line 7, in <module>  File "c:\progra~2\lundal~1\python3\lib\site-packages\lime_webserver\__main__.py", line 67, in main
    lime_config.load_config('Web Server')
  File "c:\progra~2\lundal~1\python3\lib\site-packages\lime_config\__init__.py", line 90, in load_config
    current_cfg = get_config()
  File "c:\progra~2\lundal~1\python3\lib\site-packages\lime_config\__init__.py", line 81, in <lambda>    service_name, default_config, entry_points, plugin_entry_points),
  File "c:\progra~2\lundal~1\python3\lib\site-packages\lime_config\__init__.py", line 169, in build_default_config
    cfg = merge_configs_from_packages(cfg, entry_points)
  File "c:\progra~2\lundal~1\python3\lib\site-packages\lime_config\__init__.py", line 253, in merge_configs_from_packages
    return reduce(merge_dicts, entry_points(), cfg)
  File "c:\progra~2\lundal~1\python3\lib\site-packages\lime_config\__init__.py", line 44, in <genexpr>    return (ep.load() for ep in eps)
  File "c:\progra~2\lundal~1\python3\lib\site-packages\pkg_resources\__init__.py", line 2476, in load
    self.require(*args, **kwargs)
  File "c:\progra~2\lundal~1\python3\lib\site-packages\pkg_resources\__init__.py", line 2499, in require
    items = working_set.resolve(reqs, env, installer, extras=self.extras)
  File "c:\progra~2\lundal~1\python3\lib\site-packages\pkg_resources\__init__.py", line 820, in resolve
    new_requirements = dist.requires(req.extras)[::-1]
  File "c:\progra~2\lundal~1\python3\lib\site-packages\pkg_resources\__init__.py", line 2755, in requires
    dm = self._dep_map
  File "c:\progra~2\lundal~1\python3\lib\site-packages\pkg_resources\__init__.py", line 3041, in _dep_map
    self.__dep_map = self._compute_dependencies()
  File "c:\progra~2\lundal~1\python3\lib\site-packages\pkg_resources\__init__.py", line 3051, in _compute_dependencies
    reqs.extend(parse_requirements(req))
  File "c:\progra~2\lundal~1\python3\lib\site-packages\pkg_resources\__init__.py", line 3104, in __init__
    super(Requirement, self).__init__(requirement_string)
  File "c:\progra~2\lundal~1\python3\lib\site-packages\pkg_resources\_vendor\packaging\requirements.py", line 37, in __init__
    raise InvalidRequirement(str(e)) from e
pkg_resources.extern.packaging.requirements.InvalidRequirement: Expected closing RIGHT_PARENTHESIS
    pytz (>dev)
         ~^
Traceback (most recent call last):
  File "C:\Program Files (x86)\Lundalogik\LIME Pro Server\webserver\\install.py", line 1323, in <module>    sys.exit(main())
  File "C:\Program Files (x86)\Lundalogik\LIME Pro Server\webserver\\install.py", line 67, in main
    install()
  File "C:\Program Files (x86)\Lundalogik\LIME Pro Server\webserver\\install.py", line 104, in install
    install_webserver_service()
  File "C:\Program Files (x86)\Lundalogik\LIME Pro Server\webserver\\install.py", line 671, in install_webserver_service
    _install_service_from_exe('lime-webserver.exe')
  File "C:\Program Files (x86)\Lundalogik\LIME Pro Server\webserver\\install.py", line 988, in _install_service_from_exe
    subprocess.check_call(cmd)
  File "C:\Program Files\Python37\Lib\subprocess.py", line 363, in check_call
    raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['C:\\PROGRA~2\\LUNDAL~1\\Python3\\Scripts\\lime-webserver.exe', '--username', 'lime-service-user', '--password', '*******', '--startup', 'auto', 'install']' returned non-zero exit status 1.
Installation failed...
Traceback (most recent call last):
  File "C:\Users\lime_support\AppData\Local\Temp\RarSFX0\\deploy.py", line 194, in <module>    sys.exit(main())
  File "C:\Users\lime_support\AppData\Local\Temp\RarSFX0\\deploy.py", line 35, in main
    raise e
  File "C:\Users\lime_support\AppData\Local\Temp\RarSFX0\\deploy.py", line 30, in main
    perform_install()
  File "C:\Users\lime_support\AppData\Local\Temp\RarSFX0\\deploy.py", line 165, in perform_install
    "Failed to call install script. Return code: {}".format(res))
Exception: Failed to call install script. Return code: 9999
Installation failed...

Why Does This Happen?

During the installation time of Lime CRM Server, a virtualenv is created. Unfortunately, it always installs the latest version of setuptools in the venv.

Old versions of setuptools accepted requirements to be listed in a non PEP440 compliant way. Below you can see two examples of invalid requirement definitions:

Invalid requirement definition for pytz:

"pytz>dev" # The version "dev" is not PEP440 compliant

Invalid requirement definition for pytest:

"pytest>=3.0.0<4.0.0" # A "," is missing between "3.0.0" and "<"

The definitions above are considered valid in any version of setuptools<67.0.0. (changelog), but will result in errors for all newer versions of setuptools.

Solution

Install latest release of Lime CRM Server: Lime CRM Server Release Notes