STP Documents On-Premise 8.8

STP Documents On-Premise 8.8.11

Note
Version 8.8.11 is now also approved for SQL Server 2025.

When updating or performing a new installation of SQL Server 2025, the full-text index must be recreated using the following SQL script.

SQL Script

-- Check if the full-text catalog exists, if not, create it
IF NOT EXISTS (SELECT [name] FROM sys.fulltext_catalogs)
BEGIN
    CREATE FULLTEXT CATALOG [volltextkatalog]
    WITH ACCENT_SENSITIVITY = ON
    AS DEFAULT;

    PRINT 'Full-text catalog has been created.';

    CREATE FULLTEXT INDEX ON dbo.tblFulltext
    (
        [Metatext],
        [ContentDaten]
    )
    KEY INDEX PK_tblFulltext  -- Name of the table's unique index
    ON [volltextkatalog]
    WITH CHANGE_TRACKING AUTO;

    PRINT 'Full-text index has been created.';
END
ELSE
BEGIN
    IF EXISTS (SELECT [name] FROM sys.fulltext_catalogs WHERE [name] = 'volltextkatalog')
    BEGIN
        ALTER FULLTEXT CATALOG [volltextkatalog] REBUILD;
        PRINT 'Full-text catalog already exists. Rebuild: volltextkatalog';
    END

    IF EXISTS (SELECT [name] FROM sys.fulltext_catalogs WHERE [name] = 'Volltext_Lex')
    BEGIN
        ALTER FULLTEXT CATALOG [Volltext_Lex] REBUILD;
        PRINT 'Full-text catalog already exists. Rebuild: Volltext_Lex';
    END
END

Note
Recreating the full-text index may take some time depending on the size of your database. During this process, full-text search may be limited or temporarily return no results.

Important: For DMS version 8.8.11, you should install the new versions of STP User Management and STP Common Services.

The following systems are no longer supported with version 8.8.11:

  • Windows 10

  • Windows Server 2016

  • Office 2019

  • Office 2016

  • SQL Server 2016

New and enhanced features:

  • The license check for using the Documents API is currently disabled.  (106829)

Bug fixes:

  • In certain cases, it was possible to import files with 0 KB into Standard Desk. (105184)

Release

Documents On-Premise is approved for the following systems
  • Windows Server 2025
  • Windows Server 2022
  • Windows Server 2019
  • Windows 11
  • MS SQL Server 2022
  • MS SQL Server 2019
  • MS SQL Server 2017
  • MS Exchange Server 2019
  • MS Exchange Server 2016
  • Exchange Online (see limitation below)
  • Office 2024
  • Office 2021
  • Office 365 (see limitation below)
  • TOCR Version 5
  • STP Common Services from version 1.5.0
  • STP User Management from version 1.7.506.0

Approval for Office 32-bit only applies with a supplemental agreement from STP.

For the 32-bit version, it is important that compatibility mode is enabled in all Office products. Without compatibility mode, various errors may occur in Outlook DESK and Office Integration.

It is important to set compatibility mode before installing Outlook DESK and Office Integration, otherwise errors may occur on first launch.

We generally recommend using the 64-bit version of Office whenever possible. The 32-bit version is known to quickly run into memory limitations, which can lead to errors and crashes.

Approval for Office 365 comes with limitations and only applies to local installations of already approved Office products (Microsoft 365 Apps for enterprise). Approval does not apply to the cloud version of Office.

We approve Office 365 with the caveat that we cannot rule out that updates to the Office 365 desktop applications may affect the functionality of STP add-ins.

Documents On-Premise has been tested and approved for use with Exchange Online (Office 365) in its current version.

We will continue to test future versions against the then-current version. However, updates to the Exchange Online environment may cause issues that will need to be analyzed as soon as possible.

This approval only applies to using Exchange Online as a backend system and not for use with Outlook Web Access (OWA). Using Documents On-Premise Outlook DESK in OWA is not possible.


Limitations:
  • For client operating systems, please note that Home, Starter, and RT Editions are NOT supported.
  • With Office Editions Starter, Home & Student, Home & Business, and Office RT, incompatibilities may occur.
  • On Windows 11, users without administrative rights cannot save files directly to C:. All settings in Documents On-Premise that result in files being saved directly to C: must be changed.
Additional notes:

  • Documents On-Premise requires Microsoft .NET Framework 4.8 on both the server and client sides. Please install .NET Framework 4.8 in advance (for example, during a scheduled maintenance window) on the DMS server and clients to ensure the Documents On-Premise update runs smoothly and without interruption. Installing the .NET Framework requires a system restart.

  • Documents On-Premise requires central STP User Management (UM) version 1.7.506.0 or higher and STP Common Services version 1.5.0 or higher. You can find downloads for these components on the STP website under Software Downloads.

  • For use with winsolvenz, at least winsolvenz.p4 10.12 or higher is required. winsolvenz.p3 is not supported.

  • For use with LEXolution, at least LEXolution 6.1.132 or higher is required.

  • For newer SQL Server versions, it is mandatory to set the compatibility mode to SQL Server 2008; otherwise, updating the Documents On-Premise database will not be possible.

  • When using DMS with load-balanced terminal servers or user profile synchronization, configuring the central editing directory is absolutely necessary.

  • After successfully updating to this version of Documents On-Premise, please restart the DMS server machine once.

STP Documents On-Premise 8.8.10

New and enhanced features:

  • This version requires a valid license file to use the DMS OnPremise API. This ensures that only authorized technology partners can develop and operate integrations with the DMS system. Unlicensed API access will be rejected by the server. During an optional transition period, the check can be relaxed depending on the installation (with a warning in the log). Nothing changes for STP customers regarding licensing. The transition period ends on 4/1/2026. (99637)

Bug fixes:

  • Fixed an issue where, when determining "Unprocessed Documents," all excluded file formats are ignored. Only documents suitable for full-text generation are included in the results. (100484)

  • Fixed an issue when determining "Unprocessed Documents" if the start and end dates are the same. (100922)

  • Fixed an issue where full text was not reliably generated during parallel processing with TOCR. (101189)

  • Logging for document access is now multi-server compatible. (103047)

  • Problem (122795): Fixed errors with RabbitMQ queues. Unused queues without consumers are deleted. (99637)

Version 8.8.8

Bug fixes:

  • Problem (132748) - Word freezes after using Office Integration (100272)

Version 8.8.6

New and enhanced features:

  • Updated various notification texts (99415)

Bug fixes:

Version 8.8.5

Bug fixes:

  • Problem (125359) - Collaborative editing in documents did not work. (97590)

Version 8.8.4

Bug fixes:

  • User settings were not transferred to the client when starting the client. (96980)

Version 8.8.2

Bug fixes:

  • Problem (123574) – Error message when importing an email without a subject  (95859)
  • Problem (124488) - Unacked messages in Standard DESK (96251)

Version 8.8.1

New and enhanced features:

  • In the Firm settings, under “ERV / EGVP / beA” “Send to beA DESK,” a separate section for file naming has been introduced, allowing a separate file naming scheme for sending documents to beA DESK. (84899)

  • In personal settings, under “ERV / EGVP / beA” “Send to beA DESK,” a separate section for file naming has been introduced, allowing a separate file naming scheme for sending documents to beA DESK. (84985)

  • The preview feature from previous versions is now available by default for all users in Documents. No separate activation is required anymore. (85239)

  • You can now disable the “Mark for deletion” function in the Firm settings. If disabled, the related menu entries will no longer be visible in the system—both in the context menu and in personal settings. Note: Only disable this function if you ensure the four-eyes principle for deleting documents in another way. (85040)

  • PDF/A documents can be excluded from conversion when sending to beA DESK. (92206)

  • The online manual for Documents is now available in the STP Help Center. (93944)

Bug Fixes: - Issue (109561) - In the register display, the desktop could not be loaded if the register label started with a letter that was mistakenly interpreted as a Roman numeral (e.g., "V" in "Versicherung"). (91961)

  • Issue (117083) - In certain situations, unacked messages were generated, leading to performance issues with Documents. This problem has now been fixed. (93116)

  • For the file naming scheme during export, the internal file reference was incorrectly included when "Folder/File Name" was selected; now, only the name is used as intended. (84990)

  • In certain situations, null consumer queues were created. This issue has now been resolved. (88925)

  • In some cases, the same document could unintentionally be checked out multiple times by a user on different computers without any warning—potentially leading to data loss. Documents now optionally warns you if a document has already been checked out by the same user on another device. The "Show warning" option is available in the firm and personal settings and is disabled by default. (91985)

  • Documents that are excluded from PDF/A conversion according to the firm settings are now fully included in the beA message when sent via "Send to beA DESK," without any error message. (94708)

Known Issues

If you experience inconsistencies with the STP standard document list layouts, please delete the folder containing your local personal layouts. The relevant path in the user's roaming profile for your personal layouts is: %AppData%\STP AG\LEXolution.Office...

Note: Deleting this folder will remove your personalized layouts, and you will need to recreate them.

When using Citrix environments, you may encounter issues where the log, for example, states:

"Not enough quota available to process this command."

In this case, you should clean up the temporary files in Windows (cleanmgr).

Note
In some versions of Microsoft Office, there was an issue with the integration of add-ins and features, where only a blank dialog appeared instead of the expected functions. After a thorough analysis, we identified the cause and developed a solution that restores the correct display of features and add-ins in Microsoft Word. | You can find a step-by-step guide to resolving this issue here

Release

Documents On-Premise is approved for the following systems
  • Windows Server 2025 (from version 8.7)
  • Windows Server 2022
  • Windows Server 2019
  • Windows Server 2016
  • Windows 10
  • Windows 11
  • MS SQL Server 2022
  • MS SQL Server 2019
  • MS SQL Server 2017
  • MS Exchange Server 2019
  • MS Exchange Server 2016
  • Exchange Online (see limitation below)
  • Office 2024
  • Office 2021
  • Office 2019
  • Office 2016
  • Office 365 (see limitation below)
  • TOCR Version 5
  • STP Common Services 1.5.0
  • STP User Management 1.6.512

Approval for Office 32-bit is only valid with an additional agreement from STP.

In the 32-bit version, it is important that compatibility mode is enabled in all Office products. Without using compatibility mode, various errors may occur in Outlook DESK and Office integration.

It is important to set compatibility mode before installing Outlook DESK and Office integration, as errors may occur on first launch otherwise.

We generally recommend using the 64-bit version of Office whenever possible. The 32-bit version is known to quickly run into memory limitations, which can lead to errors and crashes.

Approval for Office 365 includes limitations and only applies to local installations of already approved Office products (Microsoft 365 Apps for enterprise). Approval does not apply to the cloud version of Office.

We approve Office 365 with the caveat that we cannot rule out that an update to the Office 365 desktop applications may affect the functionality of the STP add-ins.

Documents On-Premise has been tested and approved for use with Exchange Online (Office 365) in its current version.

We will continue to test future versions against the then-current version. However, updates to the Exchange Online environment may cause malfunctions that will need to be analyzed as soon as possible.

This approval only applies to using Exchange Online as a backend system and not for use with Outlook Web Access (OWA). Using Documents On-Premise Outlook DESK in OWA is not possible.


Limitations:
  • For client operating systems, please note that Home, Starter, and RT editions are NOT supported.
  • With Office editions Starter, Home & Student, Home & Business, and Office RT, incompatibilities may occur.
  • On Windows 10, users without administrative rights cannot save files directly to C:. All settings in Documents On-Premise that result in files being saved directly to C: must therefore be changed.
Additional Notes:
  • Documents On-Premise requires the Microsoft .NET Framework 4.8 on both the server and client sides. Please install the .NET Framework 4.8 in advance (e.g., during a scheduled maintenance window) on the DMS server and on the clients to ensure the Documents On-Premise update runs smoothly and without interruption. Installing the .NET Framework requires a system restart.
  • Documents On-Premise requires central STP User Management (UM) version 1.6.512 or higher and STP Common Services version 1.5.0 or higher. You can download these components from the STP website under Software Downloads. When updating from LEXolution.DMS 7.0, please perform the DMS update first, then update STP User Management and STP Common Services.
  • For use with winsolvenz, at least winsolvenz.p4 10.12 or higher is required. winsolvenz.p4 is not supported.
  • For use with LEXolution, at least LEXolution 6.1.132 or higher is required.
  • With newer SQL Server versions, it is essential to set the compatibility mode to SQL Server 2008; otherwise, updating the Documents On-Premise database will not be possible.
  • When using DMS with load-balanced terminal servers or user profile synchronization, configuring the central editing directory is absolutely necessary.
  • Starting with Documents On-Premise 8.0.213, the standard DESK for document editing requires LCAS installation and Office integration.
  • After successfully updating to this version of Documents On-Premise, please restart the DMS server machine once.
------------------------------------------------------------------------------------------------------------------
This article has been automatically translated by an AI and may therefore contain errors.

Related to