Version: 2022.1.2

🏴‍ Known Issues

Client freeze, when switching between mysite and globalsite if doclist is sorted and paging is used​

Description​

Internal: see TFS [#40038]

If an folder is selected, which have paging enabled and is sorted by any column, and then the user switches to the mysite or the globalsite it can happend that the client freezes and stops working!

Workaround​

Internal: see TFS [#40038]
If the Client was freezed, restart it!
Try to avoid switching between my and global site when paging is enabled on the currently selected folder. Select a different folder first (which does not have paging enabled) and then change the site.

inPoint.SetupCommon: installation is not working if "service pw" contains special characters​

Internal: see OTRS [2020081301000038]

Description​

Internal: see TFS [#42012]
The characters ";" and ":" cannot be used for the service password.

Workaround​

Internal: see TFS [#42012]
Please install the setup with an empty service user-password and change the password manually after the installation has finished successful.

Unpin inPoint folders from windows explorer "Quick access" is not possible​

Internal: see OTRS [2019102901000033]

Description​

Internal: see TFS [#49496]
If any inPoint folder is D&D into the windows "Quick access", it is automatically pinned.
Then this folder cannot be unpinned, because the contextmenu entry for "Unpin from Quick access" is missing on all virtual inPoint folders. 
This is a Windows Bug, because this happens also for some other applications!

Workaround​

Internal: see TFS [#49496]
  1. Add any windows explorer folder to the pinned "Quick access".
  2. Select "Quick access"
  3. On the right side: "Frequent folders", hold down CTRL and select all inPoint folders and this one additionally added windows folder
  4. Right click on the windows folder and select "Unpin from Quick access"
All selected inPoint folders are "unpinned"

AD sync: Inconsistency may occur between the inPoint user name and the AD user name, because of local security authority (LSA) cache update delay in Windows​

Description​

Internal: see TFS [#53804]
When the user name has been changed on a domain controller, the AD synchronization is not recognizing this change immediately.
In this scenario, the AD synchronization may return the old user name instead of the new user name.

The local security authority (LSA) caches the mapping between the SID and the user name in a local cache on the domain member computer. The cached user name isn't synchronized with domain controllers. The LSA on the domain member computer first queries the local SID cache. If an existing mapping is already in the local SID cache, the LSA returns the cached user name information instead of querying the domain controllers. This behavior is by design and is intended to improve performance.

The cache entries do time out, however chances are that recurring queries by applications keep the existing cache entry alive for the maximum lifetime of the cache entry.

Workaround​

Internal: see TFS [#53804]

Preview document/Adobe Acrobat Reader: opening the preview first time cause an issue​

Description​

Internal: see TFS [#57617]
After running an upgrade, starting for inPoint.Client for the first time and opening the Document-Prefiew for the first time the Adobe-Reader fails.


img

Workaround​

Internal: see TFS [#57617]
Restart the inPoint.Client.

Searchform restore: ComboBox values are not selected​

Internal: see OTRS [2020120201000041]

Description​

Internal: see TFS [#59270]
When you select a value in a drop down list in a the search form of the standalone client, then run the search and then go back to the search form the previously selected value is not selected anmyore.

This seems to be issue with the (oder of the?) events fired by the drop down list when the search form is restored.

Workaround​

Internal: see TFS [#59270]
Currently no solution: Just select the previously selected value again.

Fresh install/inPoint.Admin: inPoint.CoreAlive check fails (waiting for new setup)​

Description​

Internal: see TFS [#59674]
On a fresh install with the wizard inPoint.Admin is installed but not working because it requires also inPoint.Identity and inPoint.Core.

So you have to install inPoint.Core inPoint.Identity.Server (and maybe also inPoint.Client) as well.

When you execute inPoint.Admin after installing you get an error that AdminAPI is not working.

This is because the services (Admin/Core/Identity) have to be restarted after re-configuring for identity. To solve this a new wizard wich has Core and Identity also included is needed (and starts up the services after the configuration in the correct order)

Workaround​

Internal: see TFS [#59674]
Restart the inPoint.Admin, inPoint.Core and inPoint.Identiy services after all of them has been installed and configured before starting the inPoint.Admin application.

Sometimes the connection to Pam.Archive is broken after creating a GSR or tenant​

Description​

Internal: see TFS [#60279]
When you create a new tenant or a new GSR the Pam.Archive.config is not automatically reloaded by inPoint.Core. (The changes are done by the Pam.Loader.Console which does not notify the backends)

InPoint.Admin has now a check which verifies that the Pam.Archive.configs loaded by inPoint.Server and inPoint.Core are equal.

Currently the syncronization which should reload the Pam.Archive.config on changes automatically is not working reliable.

Workaround​

Internal: see TFS [#60279]
Use the refresh button in inPoint.Admin to force reload of the Pam.Archive.configs of the backends.

The checks and reloads are implemented on the following nodes:
  • Repository Configuration
  • Repository Configuration / Tenants
  • Repository Configuration / [Tenant]
  • Repository Configuration / [Tenant] / Archives
  • Repository Configuration / [Tenant] / Global Site Repositories
  • Repository Configuration / [Tenant] / Flat Archive Units

All Addins cannot download the Plugins from inPoint.Core if TLS1.0 is disabled​

Internal: see OTRS [2022040501000057]

Description​

Internal: see TFS [#61371]
If the Customer does have TLS 1.0 deactivated in the Server. Then any Addin (Outlook, Excel or Word) is started, then download of the Plugins from inPoint.Core fails and the Addin cannot be used afterwards.

Workaround​

Internal: see TFS [#61371]

Moving a document with a manual relation or a workflow-report is not possible​

Description​

Internal: see TFS [#61900]
If a document is linked to another document it is not possible to move this document to another location.

A document link can be created by using the command "Related Documents Diagram" and adding another document or by attaching  a workflow report to a document.
The move of the document can be done by using Cut&Paste on the document itself or by using Cut&Paste on any parent folder of a document.

The error logged on the server side, will include this message:
Cannot insert the value NULL into column 'FT_ITEMURI', table 'ip.IP_FULLTEXT'; column does not allow nulls. INSERT fails.

Workaround​

Internal: see TFS [#61900]
The only workaround is to remove the document relation or the attached workflow report and then move the document.

HSLegacyConnector fails after update from 2021.1.3 to 2022.1.3​

Internal: see OTRS [2022061501000016]

Description​

Internal: see TFS [#62532]
After the setup has finished all calls to the web-service fail with a message similar to this:

System.TypeInitializationException: The type initializer for  "Pam4Hsm.PAM4HSMWS" threw an exception. ---> System.IO.FileNotFoundException: Could not load file or assembly "log4net, Version=1.2.13.0, Culture=neutral, PublicKeyToken=669e0ddf0bb1aa2a" or one of its dependencies. The system cannot find the file specified.

This is because some libraries are not included any more by inPoint.Enterprise.

Workaround​

Internal: see TFS [#62532]
Manually copy the missing files from the old setup into the "Bin" folder. Use the backup created during the installation and take the files from the directory "inPoint.HybridStore"!

The "Bin" folder default location is here:
"C:\Program Files (x86)\H&S Heilig und Schubert Software AG\HSLegacyConnector\Web\Bin"

These files need to be copied:
  • HsLog.dll
  • HybridStore.API.dll
  • log4net.dll