STP Documents On-Premise 8.8

STP Documents On-Premise 8.8.16

These release notes include all changes up to and including version 8.8.16. Previous patch versions of 8.8 have been incorporated into this document.

The new version includes the following:

Version 8.8.16 is primarily a stability and bug fix release. The main points are the update of the PDF conversion library Aspose to version 26.6, which fixes a specific display error, as well as the resolution of 14 issues.

Please note:

The following components must also be updated—if you use them:

• new Winsolvenz version 11.7.102
• new beA DESK version 1.12.0

If you use the STP Cloud, you must also update the following components, if applicable:

• new WOPC (Winsolvenz OnPremise Connector) version 11.7.102
• new STP.OnPremise.Connector version 1.10.0
• new STP Documents OnPremise Agent version 1.14.3.0

If you use Input Management, you must also update:

• new STP winsolvenz FLOW Connector version 1.0.104

If you use InsO-Up, you must also update:

• new InsO-Up Cockpit version 9.3.2

On this page: New Features · Bug Fixes · Important Notes · Release · Known Issues

New and Enhanced Features

Current — Version 8.8.16

• Aspose has been updated to version 26.6. This provides the latest improvements and optimizations of the Aspose components.

Bug Fixes

Current — Version 8.8.16

• Issue (ZD 164141): An issue with converting Word documents to PDF, which could cause altered page breaks, has been fixed by updating Aspose to version 26.6. Formatting is now correctly preserved when generating PDFs. (113753)

• Issue (ZD 181575): Fixed a bug that allowed the TOCR Fulltext Worker to start in the 32-bit version. Starting in the 32-bit version is now prevented. (121717)

• Issue (ZD 174297): Fixed a bug where tasks created in MobileDesk could not be completed in StandardDesk. Tasks can now be properly processed and completed regardless of where they were created. (118938)

• Issue (ZD 147764): Fixed a bug where the sidebar would become unresponsive after importing in Standard Desk. The area now remains usable and responds correctly after import. (121169)

• Issue (ZD 170473): Fixed a bug that could lead to a faulty database query and a corresponding error message in the DMS server log. (116433)

• Issue (ZD 163222): Fixed a bug where certain error messages in the DMS server log could cause unexpected system crashes. (113526)

• Issue (ZD 171426): Fixed a bug where Standard Desk could freeze and cause display errors or malfunctions in the sidebar. (116875)

• Issue (ZD 165185): Fixed a bug where the DMS server sent messages without Create User or Modify User. (114410)

• Issue (ZD 153892): Fixed a bug where the STP Admin was always shown as the user in the deletion history in the database. (108948)

• Issue (ZD 157297): Fixed a bug where the message “LCAS not connected” was repeatedly displayed, requiring the server to be restarted regularly. (110489)

• Issue (ZD 162108): Fixed a bug where the Lexolution Client App Service (LCAS) lost its connection. (111443)

• Issue (ZD 163125): Fixed a bug where a document would still appear in the user directory and in the “Documents in Progress” list after being opened and then closed. Closed documents are now correctly removed from these areas. (113410)

• Issue (ZD 159751): Due to a bug in RabbitMQ communication, users were sometimes unable to work with Documents; this has been fixed and the service’s stability restored. (111444)

• Fixed a bug where a license check was verifying the presence of the GIS license code. (119827)

• Fixed a bug where, after a DMS update, some users experienced synchronization issues. In these cases, documents could sometimes no longer be checked in correctly. The cause was a .json file in the user's roaming directory that was not created correctly after the update in certain cases. The faulty behavior has been corrected so that the configuration file is now reliably created. (118348)

Important Notes for This Version

SQL Server 2025 / Full-Text Index (since 8.8.11) As of now, version 8.8.11 is also approved for SQL Server 2025. When updating or installing SQL Server 2025, the full-text index must be recreated.

-- 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

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

Discontinued system support (since 8.8.11) The following systems are no longer supported as of version 8.8.11: Windows 10 · Windows Server 2016 · Office 2019 · Office 2016 · SQL Server 2016

Release Information

Current status for version 8.8.16

Supported Systems

• Windows Server 2025
• Windows Server 2022
• Windows Server 2019
• MS SQL Server 2025 (Standard or Enterprise)
• MS SQL Server 2022 (Standard or Enterprise)
• MS SQL Server 2019 (Standard or Enterprise)
• Windows 11 (Professional or Enterprise, 64-bit)
• MS Exchange Server 2019
• MS Exchange Server 2016
• Microsoft 365 (with limitations, see technical documentation)
• Office 2024 (Professional Plus 64-bit)
• Office 2021 (Professional Plus 64-bit)
• STP.Common.Services at least 1.6.530.0
• STP.User Management 1.11.0
• TOCR Version 5

* with limitations, see below

Support for Office 32-bit is only available with an additional agreement from STP. For the 32-bit version, it is important that compatibility mode is enabled in all Office products—before installing Outlook DESK and Office Integration. We generally recommend the 64-bit version of Office, as the 32-bit version is known to quickly run into memory issues.

Support for Office 365 only applies to local installations of already supported Office products (Microsoft 365 Apps for enterprise)—not the cloud version. We cannot rule out that an update to the Office 365 desktop applications may affect the STP add-ins.

Documents On-Premise has been tested and approved for Exchange Online in the current version; this only applies as a backend system, not for Outlook Web Access (OWA).

Limitations

• Client operating systems: Home, Starter, and RT editions are not supported.
• Office editions Starter, Home & Student, Home & Business, and Office RT: Incompatibilities possible.
• On Windows 11, users without administrative rights cannot write directly to C:—the corresponding Documents settings must be adjusted.

Additional Notes

• .NET Framework 4.8 is required on both server and client sides (installation requires a restart).
• STP User Management from 1.7.506.0 and STP Common Services from 1.5.0 are required.
• winsolvenz: at least winsolvenz.p4 10.12 (winsolvenz.p3 is not supported).
• LEXolution: at least version 6.1.132.
• For newer SQL Server versions: Compatibility mode must be set to SQL Server 2008.
• For load-balanced terminal servers/profile synchronization: configure a central working directory.
• After the update: restart the DMS server once.

Known Issues

• Inconsistent document list layouts: Delete the folder for local personal layouts (%AppData%\STP AG\LEXolution.Office...). This will remove personalized layouts, which will need to be recreated.
• Citrix environments: If you see the message "Not enough quota available to process this command," clean up the temporary files in Windows (cleanmgr).
• Empty add-in dialog in Office: Step-by-step solution here.