invantive documentation
Invantive Support ForumsLog In / Sign Up

Release notes of Invantive Bridge

Release Note - Installer

Invantive Bridge 27.0, from 26.0

Build Date Description
26.0.4 22-03-2026 first build of release 26.0
27.0.92 09-11-2026 latest build of release 27.0 at the time of writing

The older state is the first build of release 26.0, not its last: later builds of 26.0 received ports of changes made for 27.0, so those changes are part of this step. The 27.0 line also contains the beta builds 26.1.x.

  • 32 enhancements
  • 19 bug fixes
  • 1 things to check before upgrading

Before You Upgrade

These changes ask for a check:

  • Settings files move from XML to JSON
    • Settings files are converted from XML to JSON when they are read. From 27.0 the JSON file takes precedence and the XML file is removed in release 28.0: edit the JSON file from now on and keep a copy of the XML file until then.

Top 25 Changes

  1. Settings files move from XML to JSON
    • Enhancement
    • action needed
    • Action needed before or after the upgrade.
  2. Invantive License Service: clearer messages, grace period and new modules
    • Enhancement
    • A licence key of the wrong type is explained, a licence service that is unavailable gets a specific message, and a licence that was valid stays in force for a grace period when the service cannot be reached. The check that prolongs a licence runs hourly. New licence modules exist for the Support Assistant, OEM use and subscription software, the built-in trial and open data keys use the new format, and text-mode products show tips about the licence in use.
  3. Data containers and credentials from Invantive Credentials Server
    • Enhancement
    • A database definition can point to Invantive Credentials Server, which supplies the data containers and sign-in credentials. The log-on window and the partition menu show these containers with their own icon, errors of the server are shown with their details, and a retrieval is repeated after a time-out.
  4. The legacy Oracle driver and the Invantive Web Service driver are removed; Oracle 18 is the minimum
    • Enhancement
    • The legacy Oracle driver is no longer registered and Oracle is handled by the managed driver, a log-on to a database older than version 18 is refused, and the Invantive Web Service driver and its data container are no longer offered.
  5. Register every call to a platform in the connection activity
    • Enhancement
    • Calls of drivers to platforms, including database drivers, are registered with begin and end, rows and duration. The connection monitor shows them while they run and with the action of the user that caused them. Earlier, several calls were not registered or were counted twice.
  6. The keychain and settings files are written safely
    • Enhancement
    • The keychain and settings files hold either the old or the new contents, also after a crash or a full disk, are guarded with a file lock when two programs use them, are written less often and open faster.
  7. Licence keys can be supplied through environment variables
    • Enhancement
    • A licence key can be given in the environment variables INVANTIVE_LIC_KEY and INVANTIVE_LICX_KEY, also with surrounding text or line breaks. This helps with unattended starts, for example in scripts and containers.
  8. Sensitive values are masked in traces, error data and OAuth logs
    • Enhancement
    • Passwords, secrets, tokens, API keys, cookies, authorisation headers and one-time codes are no longer written in clear text in traces, exception data and the log text of OAuth calls.
  9. File names longer than 260 characters work on Windows
    • Enhancement
    • Where Windows allows it, file and folder paths up to 32,767 characters are accepted. The setup program declares support for long paths and the trace shows whether they work.
  10. Links to documentation, forums and support use the invantive.eu address
    • Enhancement
    • Help links, the splash screen, the default address of Customer Service and the links of data sources point to the invantive.eu domain.
  11. A script can query its own execution profile
    • Enhancement
    • Runs of Invantive Script, their statements, started operating system commands, variables and exit codes are registered and can be queried with plain SQL through the new data container Script. The name of the profile log can be chosen, and statements register the memory they allocated.
  12. Invantive MCP Server is recognised as an application
    • Enhancement
    • The Invantive MCP Server is now a known application for licence checks and for the choice of client settings.
  13. Read the licence key from the variables INVANTIVE_LIC_KEY and INVANTIVE_LICX_KEY
    • Enhancement
    • A licence key can be supplied in an environment variable. When one is set, the licence file is not searched for.
  14. UTF-8 files are written without a byte order mark by default
    • Enhancement
    • Exports, trace files, plug-in files and the input and output of operating system commands are written as UTF-8 without a byte order mark unless one is asked for.
  15. Web calls wait and retry better
    • Enhancement
    • Timeouts apply as configured, a stalled connection is cut off and treated as temporary, retries wait longer each time with a random part and follow the Retry-After header, a session slows down before the minutely rate limit is used up, a token endpoint that does not answer is dropped after 30 seconds, and damaged compressed answers are read again.
  16. XML from outside is no longer allowed to load external entities
    • Bug Fix
    • Processing XML from external services, XSLT transformations and the XML of an RSA key no longer resolves DTDs or external entities.
  17. Zstandard compression for trace files, caches and SQL functions
    • Enhancement
    • Trace files, persistent caches, saved result sets and the disk cache of web answers are compressed with Zstandard, which is faster than gzip at a similar size. Two SQL functions compress and decompress with Zstandard, and a text file with gzip or Zstandard content is read as plain text.
  18. More diagnostics: message codes, trace detail and monitoring
    • Enhancement
    • More failures have their own message code, trace records carry a severity name, spans with standard trace identifiers and an OpenAPI description, the trace shows memory and processors including container limits, and a failure to load an assembly is explained. A trace level below debug can be switched on separately.
  19. Separate folders for environment files, the keychain, databases and traces
    • Enhancement
    • The folders for environment files and for the Invantive Keychain can be set through environment variables, database definitions live in a sub-folder of the configuration folder, and traces go to a Trace folder there by default; the folder is created when missing.
  20. Statistics show memory and CPU time per statement
    • Enhancement
    • The statistics of a statement include the heap allocations and the CPU time of its threads.
  21. Sample configuration files are written with documentation of every setting
    • Enhancement
    • The product can write sample configuration files that list every setting with its description, default and example. The folder can be chosen with an environment variable.
  22. Access to the local file system can be blocked in shared environments
    • Enhancement
    • On shared multi-user environments, statements that read or write local files are refused with a clear error, and a file name from outside cannot leave its folder. A single workstation, such as Query Tool, is not affected.
  23. Configuration errors point to the documentation of the setting
    • Enhancement
    • An error about an invalid configuration value now includes a hint that comes from the documentation of the setting.
  24. A failure to write the backup copy of a settings file no longer blocks reading it
    • Bug Fix
    • Reading a settings file failed when the last known good copy could not be written. The copy is now written separately and a failure is reported without stopping the log on.
  25. A stack overflow while logging at start-up is prevented
    • Bug Fix
    • Asking for information about the process while that information was being collected could repeat itself until the program stopped. The collection is now protected against re-entry.

All Enhancements

Changes to behaviour, platforms, drivers and settings, grouped by area.

Installation and platform

Settings files move from XML to JSON

A settings file in XML is converted to JSON when it is read. The user and installation settings, the cached list of databases and the databases of the user are also written in JSON, through an atomic write, and a damaged XML file is recovered where possible. From 27.0 the JSON file takes precedence; the XML file is still written for older releases on the same workstation and is planned to disappear.

What to Do

Settings files are converted from XML to JSON when they are read. From 27.0 the JSON file takes precedence and the XML file is removed in release 28.0: edit the JSON file from now on and keep a copy of the XML file until then.

  • action needed
  • importance 5
File names longer than 260 characters work on Windows

Where Windows allows it, file and folder paths up to 32,767 characters are accepted. The setup program declares support for long paths and the trace shows whether they work.

  • importance 3
The keychain and settings files are written safely

The keychain and settings files hold either the old or the new contents, also after a crash or a full disk, are guarded with a file lock when two programs use them, are written less often and open faster.

  • importance 3
Configuration errors point to the documentation of the setting

An error about an invalid configuration value now includes a hint that comes from the documentation of the setting.

  • importance 2
Sample configuration files are written with documentation of every setting

The product can write sample configuration files that list every setting with its description, default and example. The folder can be chosen with an environment variable.

  • importance 2
Separate folders for environment files, the keychain, databases and traces

The folders for environment files and for the Invantive Keychain can be set through environment variables, database definitions live in a sub-folder of the configuration folder, and traces go to a Trace folder there by default; the folder is created when missing.

  • importance 2
Use the www.invantive.com address as product address of the installer

The installer and release notes refer to www.invantive.com instead of the old ado.net-provider.cloud address.

  • importance 1

Licensing and sign-in

Data containers and credentials from Invantive Credentials Server

A database definition can point to Invantive Credentials Server, which supplies the data containers and sign-in credentials. The log-on window and the partition menu show these containers with their own icon, errors of the server are shown with their details, and a retrieval is repeated after a time-out.

  • importance 4

Invantive Credentials Server, Concept of Invantive Credentials Server

Invantive License Service: clearer messages, grace period and new modules

A licence key of the wrong type is explained, a licence service that is unavailable gets a specific message, and a licence that was valid stays in force for a grace period when the service cannot be reached. The check that prolongs a licence runs hourly. New licence modules exist for the Support Assistant, OEM use and subscription software, the built-in trial and open data keys use the new format, and text-mode products show tips about the licence in use.

  • importance 4

License Service

Invantive MCP Server is recognised as an application

The Invantive MCP Server is now a known application for licence checks and for the choice of client settings.

  • importance 3
Licence keys can be supplied through environment variables

A licence key can be given in the environment variables INVANTIVE_LIC_KEY and INVANTIVE_LICX_KEY, also with surrounding text or line breaks. This helps with unattended starts, for example in scripts and containers.

  • importance 3

Environment variables

Read the licence key from the variables INVANTIVE_LIC_KEY and INVANTIVE_LICX_KEY

A licence key can be supplied in an environment variable. When one is set, the licence file is not searched for.

  • importance 3
Email addresses are accepted when the validation service does not answer

When Customer Service cannot validate an email address, because it fails or does not answer, the address is accepted as entered and the situation is traced. An invalid address reported by the service is still refused.

  • importance 2
Support the Invantive Credentials Server for OAuth sign-in

The provider for the Invantive Credentials Server is registered, so OAuth credentials can be obtained through it when it is allowed.

  • importance 2
Obsolete Windows RSA properties removed from the system properties

Two obsolete properties about the Windows RSA service and an operating system update check are no longer listed in the system property view. Some descriptions now say text instead of string.

  • importance 1
Registration of new Invantive products and connectors in licensing

The licensing and product lists know the Invantive MCP Server, Credentials Server, App Online and a Credentials API connector, with licence modules, documentation links and download addresses. Differences between Bridge Online personalities are registered too.

  • importance 1

Security

Sensitive values are masked in traces, error data and OAuth logs

Passwords, secrets, tokens, API keys, cookies, authorisation headers and one-time codes are no longer written in clear text in traces, exception data and the log text of OAuth calls.

  • importance 3
Access to the local file system can be blocked in shared environments

On shared multi-user environments, statements that read or write local files are refused with a clear error, and a file name from outside cannot leave its folder. A single workstation, such as Query Tool, is not affected.

  • importance 2
IP address ranges in CIDR notation support IPv6

A range such as 192.168.0.0/16 or one with IPv6 addresses is now matched against IPv4 and IPv6 addresses in both notations. A range with an invalid address or prefix matches nothing.

  • importance 2
Update a component with a security advisory

A cryptography component used for XML signatures is updated to a version without a known security issue.

  • importance 2
Mail domain proguidex.com is blocked

Email addresses at the domain proguidex.com are refused.

  • importance 1

Scripting

A script can query its own execution profile

Runs of Invantive Script, their statements, started operating system commands, variables and exit codes are registered and can be queried with plain SQL through the new data container Script. The name of the profile log can be chosen, and statements register the memory they allocated.

  • importance 3

Platforms and drivers

The legacy Oracle driver and the Invantive Web Service driver are removed; Oracle 18 is the minimum

The legacy Oracle driver is no longer registered and Oracle is handled by the managed driver, a log-on to a database older than version 18 is refused, and the Invantive Web Service driver and its data container are no longer offered.

  • importance 4
Web calls wait and retry better

Timeouts apply as configured, a stalled connection is cut off and treated as temporary, retries wait longer each time with a random part and follow the Retry-After header, a session slows down before the minutely rate limit is used up, a token endpoint that does not answer is dropped after 30 seconds, and damaged compressed answers are read again.

  • importance 3

Export and import

UTF-8 files are written without a byte order mark by default

Exports, trace files, plug-in files and the input and output of operating system commands are written as UTF-8 without a byte order mark unless one is asked for.

  • importance 3

Performance

Zstandard compression for trace files, caches and SQL functions

Trace files, persistent caches, saved result sets and the disk cache of web answers are compressed with Zstandard, which is faster than gzip at a similar size. Two SQL functions compress and decompress with Zstandard, and a text file with gzip or Zstandard content is read as plain text.

  • importance 3

Logging and diagnostics

Register every call to a platform in the connection activity

Calls of drivers to platforms, including database drivers, are registered with begin and end, rows and duration. The connection monitor shows them while they run and with the action of the user that caused them. Earlier, several calls were not registered or were counted twice.

  • importance 3
Error about a single-row fetch names the table and the value

Errors saying one row was expected name the table that was queried and the value looked for.

  • importance 2
More diagnostics: message codes, trace detail and monitoring

More failures have their own message code, trace records carry a severity name, spans with standard trace identifiers and an OpenAPI description, the trace shows memory and processors including container limits, and a failure to load an assembly is explained. A trace level below debug can be switched on separately.

  • importance 2
Statistics show memory and CPU time per statement

The statistics of a statement include the heap allocations and the CPU time of its threads.

  • importance 2

Documentation

Help links, the splash screen, the default address of Customer Service and the links of data sources point to the invantive.eu domain.

  • importance 3
Improve the sample program: no key press wait on redirected input, exit codes, errors

The sample program only waits for a key press when a console is attached. It ends with a defined exit code and prints the message code, the time and all messages of an unhandled exception.

  • importance 1

All Bug Fixes

Defects of the older release that are repaired.

Installation and platform

Fix a null initialisation error at start-up in the dependency helpers

Internal helpers could be used before their global state had been created, which gave a null error during start-up. The state is now created on first use.

  • importance 2
Make sure the process exits even when the exit registration fails

When registering the exit or the clean-up raised an error, the process did not always end. The process now always exits.

  • importance 2
Avoid a possible hang when reading the installation identifier on Linux and macOS

The command used to read the installation identifier could block when its output filled a buffer. Output and errors are now read at the same time.

  • importance 1

Licensing and sign-in

A failure to write the backup copy of a settings file no longer blocks reading it

Reading a settings file failed when the last known good copy could not be written. The copy is now written separately and a failure is reported without stopping the log on.

  • importance 2
A system property returned the licence text under the name of the title

The system property with the licence agreement text had the name of the title property. The name is corrected.

  • importance 2
Keep one session identifier for the whole log on

The session identifier was replaced at the end of a log on. Components such as the data cache that had already registered the session then pointed to a session that no longer existed.

  • importance 2
Repair reading of connection files that list failover before data containers

Connection files written before November 2019 could lose their data containers when read. Both element orders are now read in full.

  • importance 2
Fix licence keys that contain line endings of another platform

Line endings in a licence key were removed by looking for two specific characters. This is replaced by a platform-independent removal. Text meant for Windows is now generated with Windows line endings on every platform.

  • importance 1
Log on refused by a message of Customer Service gives one error instead of two

When a log on is refused after the user was told why, the session no longer raises an extra error.

  • importance 1

Security

XML from outside is no longer allowed to load external entities

Processing XML from external services, XSLT transformations and the XML of an RSA key no longer resolves DTDs or external entities.

  • importance 3
Reject malformed encrypted data with a clear error

Decryption of damaged or incomplete encrypted data failed with a null-reference error or named the wrong block in its message. It now rejects the data with a correct error.

  • importance 2
OAuth events and TOTP rate limiters no longer grow without bound

The list of recorded OAuth events is capped at 100 entries and returns the newest ones. The administration kept for repeated failed one-time-password checks is cleaned up after it is idle.

  • importance 1

Logging and diagnostics

A stack overflow while logging at start-up is prevented

Asking for information about the process while that information was being collected could repeat itself until the program stopped. The collection is now protected against re-entry.

  • importance 2
Fix a serialisation error in session logging with the dummy driver

Logging a session of the dummy driver failed with error code itgenclr003 because some properties could not be written as XML. These properties are now excluded and the address is written in a separate XML field.

  • importance 2
Trace files no longer fail when the trace folder name is long

A trace folder with a long name made the creation of the trace file fail with a path-too-long error. The folder part of the trace file mask is now determined without checking the full path length.

  • importance 2
Fix lost logging of exceptions raised at the same time on several threads

An exception raised on one thread could be left out of the trace while another thread was still writing a record about an exception. Each thread is now handled on its own.

  • importance 1
Forward the messages printed at the end of an Invantive Data Hub run

Messages produced while Invantive Data Hub was ending were reported as not forwarded. They are now written straight to the trace output once the final flush starts.

  • importance 1
Keep the row count when result set information is copied

Information about a result set lost its row count when it was copied.

  • importance 1
Show the platform name in the message about a new OAuth token

The message that a new token was received showed the placeholder instead of the name of the platform.

  • importance 1

What It Builds On

Kind Name From To
invantive component Invantive Bridge 26.0.4 27.0.92
invantive component Invantive(R) Basics 26.0.4 27.0.92
invantive component Invantive(R) SQL for Core 26.0.4 27.0.92
invantive component Invantive(R) SQL 26.0.4 27.0.92
invantive component Invantive(R) SQL for Windows 26.0.4 27.0.92
build tool Invantive Deploy 26.0.4 27.0.92
build tool change Installing and upgrading a .NET 10 product no longer runs the NGEN tool per assembly
build tool change Installer shows an error when another installation is already running
build tool change Final installer window shows the version link
build tool change Progress bar of the installer follows the measured duration of the installation stages
build tool change Installer windows flicker less when moving to the next step
build tool change Installer no longer stalls on an unreachable Customer Service and cancels reliably
build tool change Installer explains in a window why installation settings cannot be downloaded
build tool change Maintenance window checks that the product is still installed
build tool change Installer shows unexpected errors in its own window
build tool change Repair Office add-in name, optional email check and installs run as SYSTEM
build tool change Installs run as SYSTEM are attributed to the end user, not to the SYSTEM account
build tool change Each product gets one .NET 10 installer; the .NET Framework installer is no longer built
build tool change Installer includes the files .NET needs to find native libraries such as WebView2
build tool change Installer carries native runtime folders and Catalan, Hungarian and Romanian resources
build tool change Installer no longer includes the crash dump tool
build tool change Supported Windows versions in release information follow mainstream support dates
build tool change Installer writes its trace to the Invantive Trace folder when trace to file is on
build tool change Installer texts for new messages are available in all supported languages
build tool change Installer email step rejects example and test domains
third party summary

More Information

How This Note Was Made

  • For all products together 28 items whose changed lines are 50 to 70 % in the first build of 26.0 and 23 items that a content check would have left out were read against that build; the items that apply to this product are kept or left out on that reading.
  • Range: commits of origin/release-27.0 that are not reachable from the first build of release 26.0 (stamp 26.0.4, per repository). Commits that were ported to later builds of 26.0 are therefore included.
  • For a product that does not offer SQL to its users, items of the shared libraries outside the areas installation, licensing, security and diagnostics, and items about one platform, are left out and counted as internal.
  • The commits are the ones of the range that touch a project of the product; each commit was classified once, for all products, and the items of a product are the items that contain such commits.
  • Version stamp commits of the build pipeline are left out.
  • A change whose changed lines are for 70 % or more already in the first 26.0 build is left out; items between 50 % and 70 % and all such exclusions were checked by reading the code of that build.
  • A bug fix whose repaired lines were written by another commit of the same range is merged into its feature or left out.
  • Texts were written from the commit messages and from the changes themselves; items carry a confidence.
  • 185 links between a change and a source commit are recorded.
  • 5 exclusions are recorded in the audit of the note.