Version: 2021.3.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.



The property GetThumbnail_Quality is not applied​

Description​

Internal: see TFS [#57759]
The property "GetThumbnail_Quality" (inside the web.config) is not applied correctly.

Workaround​

Internal: see TFS [#57759]
There is no workaround for now.

The custom query hint is not cleared from the cache after the change​

Description​

Internal: see TFS [#58599]
The custom query hint is not cleared from the cache after the change. The cleanup happens only after 60 minutes, which is the default absolute expiration of the cache entry.

Workaround​

Internal: see TFS [#58599]
Modify the "HintsSettingsCacheAbsoluteExpiration" web.config key to value: 0.

Sorting for Mailbox Searchforms is not correctly converted to the new Searchform (MERGE 2021.3)​

Workaround​

Internal: see TFS [#58735]
Open the related searchform in the Search Form Designer and reconfigure the sorting. After this step the Client must be restarted once and then the sorting is correctly loaded and used.

Description​

Internal: see TFS [#58735]
Affects all existing searchforms only for the Mailbox and only if sorting is configured. After upgrade to this version the sorting is not correctly restored from the existing searchform. The Client is able to load and search with the searchform, just the sorting is not there anymore.

2021092101000028 Search result only show fields which have a visibility of 'Search result' and the 'Search' checkbox ticked​

Description​

Internal: see TFS [#58810]
The search result of a full text search and also related functions like the "Export" will only contain fields which have both a visibility with "Search result" enabled and also the checkbox "Search" ticked. If only one of these prerequisite is enabled the field may be added but will be empty.

Workaround​

Internal: see TFS [#58810]
Make sure that both the visibility with "Search result" and the checkbox "Search" are ticked.