Important notes

inPoint.Enterprise

For the changes introduced by inPoint.Enterprise 2025.1, please refer to the separate documentation.

inPoint.Web.IdentityServer is included in the inPoint.Wizard

The upgrade process of the inPoint.Wizard now handles the inPoint.Web.IdentityServer installation. Please check the fresh install, upgrade, and cluster sections of the documentation.

Changes for inPoint.Standalone

Before 2024.1: All executables (and .config files) are in the same folder.

• C:\Program Files (x86)\HS Europe\inPoint.Client

Starting with 2024.1 the applications are installed to new locations: Every application is installed into a different sub-folder.

• C:\Program Files (x86)\HS Europe\inPoint.Client\inPoint.Standalone
• C:\Program Files (x86)\HS Europe\inPoint.Client\inPoint.Shell
• ...

The log4net.config file is still at C:\Program Files (x86)\HS Europe\inPoint.Client\log4net.config

The application configs (*.exe.config and *.dll.config) are configured to use the common log4net.config (..\log4net.config)

For upgrades: All *.exe.config and *.dll.config files are reverted to their original values (like a fresh install). So if you made some changes you have to backup the config files before running an upgrade of the client. After the upgrade you can merge the changes manually into the new config files.

Oracle Database support

Support for Oracle 11g has ended.

Performance issues during Kibana Upgrade

There can be performance issues while removing the old Kibana folder during upgrade to the latest version.

To avoid this issue please go to the old Kibana folder and rename it to "_Kibana" - in this way the inPoint.Wizard will ignore the deletion completely and will create the new Kibana folder automatically.

Archiving of large files (file size approx. 5GB)

There is an error message during archiving of large files after 10 minutes.

Solution:
Increase the timeouts inside the following configs:

• web.config
• Pam.Archive.config (inPoint.Admin)
• inPoint.HybridStore\appSettings.json
• inPoint.config (%appdata%/inPoint -> on client side)

to receiveTimeout="02:00:00" and sendTimeout="01:00:00"

Example:
5GB = ~10min

web.config:
Path: %installdir%\HS Europe\inPoint.Enterprise\inPoint.WebDav\web\web.config

inPoint.HybridStore:
Path: %installdir%\HS Europe\inPoint.HybridStore\appSettings.json Default: 60 minutes

inPoint.Admin (for HybridStore):
Default: 60 minutes

inPoint.config: Path: %appdata%\inPoint\inPoint.config (client side)
Default: 300 seconds

Pam4AppConn/ColdScript: Pam4AppConn.dll cannot be registered

... because of missing MV C++ Redistributable for VS 2015
ColdScript is not working correctly because of a missing prerequisite.

Solution:
Install the prerequisite and continue.

Microsoft Windows TIFF IFilter (Windows Server 2012 R2)

On Windows Server 2012 R2 the Microsoft TIFF IFilter does not support all formats. LZW Encoding with black & white works.
"CCITT Group 4 Fax Encoding" is not working.
It can be tested with inPoint.Indexer.exe CONVERT

Solution:
Update to Windows Server 2016 if possible.

Service cannot be started or long Client startup times

inPoint.Core Service cannot be started. When you try to start the service in the Service Manager. After 30 seconds, an error message window appeared and the service is not running.
inPoint.Identity Service cannot be started. When you try to start the service in the Service Manager. After 30 seconds, an error message window appeared and the service is not running.
inPoint Standalone client: After the Application was started, it takes 30 seconds and then the window will appear and it starts Loading.
Can also happen in some other Applications.

Solution:
If you have any inPoint Server without an internet connection: I recommend to deactivate the "Check for publisher’s certificate revocation" check completely.
Steps:

• Click the Menu Start => Run, type "Control Panel", and click "OK"
• Double click "Internet Options"
• Navigate to the tab "Advanced"
• Uncheck the "Check for publisher’s certificate revocation" under the "Security" section

If you just want to disable this check for any certain process, then add to the Application configuration this line:

<generatePublisherEvidence enabled="false"/>

For more information see: Microsoft Documentation generatePublisherEvidence Element Make sure that you insert this line to the correct position in the .app Config File:

<configuration>
<runtime>
<generatePublisherEvidence>

When this problem appears on some Clients which don't have access to the internet:
Add the generatePublisherEvidence manually to the inPoint.Standalone.exe.config.
Change the setting in the "Internet Options".
If multiple clients are affected. This setting can also be changed with an Registry Key change.
See: GPO: Disable check for publisher's certificate revocation

Client does not start (XamlParseException is shown in the EventViewer)

When the inPoint.Standalone.exe was started (double clicked the inPoint Icon), nothing happens. Nothing was written into the %temp%/logs/inPoint.log File and in the EventViewer the Error System.Windows.Markup.XamlParseException is shown.

Solution:
Mostly when this Error happens, the .NET Framework 4.8 is not correctly installed or broken.

First, check which .NET Framework Version is installed in "Programs and Features". Must be .NET Framework 4.8! If no Framework installation is shown, see How to: Determine which .NET Framework versions are installed to check in the Registry, which Version is installed. Must be >= 528040

If multiple .Net Versions are installed (shown in "Programs and Features") uninstall all of them and just installed .NET Framework 4.8.

If only .NET Framework 4.8 is installed, download the Installer Download .NET Framework 4.8 and do a repair with this Setup.

Check also the Windows Version if it is supported by us! (See our Prerequisites Document)

Close and Save with WebDav opened files in Office 2016

If files are opened with WebDav in Office 2016, then closed and saved, the Office Upload Center complains that it cannot save the file.

Solution:
Disable caching in Office Upload Center

• Open the Microsoft Office Upload Center, click on "Settings" and check the box: "Delete files from the Office Document Cache when they are closed"
• Use the Registry to directly set it (where XXX is your office version): HKEY_CURRENT_USER\Software\Microsoft\Office\XXX\Common\FileIO\ DisableLongTermCaching a REG_DWORD with a value of 1.

Save (wait some seconds), then close the file.

Folder-Templates and inherit-permissions

When creating folders from templates permissions are correctly restored. Folders with inherit-permissions are now re-created correctly (with no ACL set). Earlier versions (before 2019.4.3 release) created them with the effective-permissions.

This effects only templates created with the client starting from version 2019.4.3. Old templates created before the 2019.4.3 release should be re-created.

Templates created with the current client (version 2019.4.3 and above) should not be used by old clients (before version 2019.4.3) because the old client would restore all folders saved with inherit-permission as folders with no-permissions.

Export & Import Packages Command

Since the export / import uses the same code when exporting / inporting folder structures like the Folder-Templates. Exports written with an old client should not be used anymore.

When old exports are imported, the permissions have to be fixed manually after folders has been restored.

Multiple folder locations for a document is not supported, because of the security architecture

One document can have only one folder location in inPoint. The same docid can be shared under multiple locations ONLY by using links. The rule reevaluation will not work for documents having multiple folder locations.

Limitations/performance issues while re-evaluating the "Rule based" security for formats

inPoint.Client starts re-evaluating the security based on format rules when:

• Creating the rule
• Modifying the conditions in the rule
• Deleting the rule
• Changing the order of the rules

, and displays the following dialog:

While re-evaluating the security, ACLs might be changed for all folders/documents using the given element format containing rules. This might be an expensive operation taking hours depending on the amount of folders/documents/number of rules/complexity of the conditions. The re-evaluation dialog will timeout in this case in the inPoint.Client, but the operation will continue in the background. The user will get the following message:

IMPORTANT
The restart of the server/Pam.Web application pool during the re-evaluation process will cause a rollback of the complete operation.

The limitation/duration of the re-evaluation is different based on the database type:

Re-evaluation of the "Rule based" security for formats on Oracle

• Number of folders are not limited
• Number of documents are not limited
• Number of rules are not limited
• The re-evaluation process takes longer compared to the MS SQL implementation
  • Re-evaluating 1 million documents takes approximately 7 hours.

Re-evaluation of the "Rule based" security for formats on MS SQL

• If the re-evaluation process takes longer than 1 hour, the complete operation is rolled back.
  • In this case the number of folders/documents are limited. Giving an example:
    • The re-evaluation process takes approximately 1 hour for 800,000 documents using 12 rules

Upgrade inPoint Index

The ElasticSearch index from any version previous of 2022.1 must be upgraded because of changes for the search favorites! While the upgrade is running in the background inPoint can be used but the search favorites will not show previously archived documents or folders.

For using the new improved highlighting using 'index_option=offsets' a migration of the index is required.

For details how to upgrade see the documentation.