Versions Compared

Old Version 11

changes.mady.by.user Roar Hansen (Deactivated)

Saved on

compared with

New Version 12

changes.mady.by.user Zbigniew Marszolik (Deactivated)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Purpose of the program

...

Changes made to the system

File-system

Version

Default installation destination

Single User

c:\Users\<User>\AppData\Local\Apps\Locator DocumentHandler

Multi User

c:\Program Files (x86)\ayfie\Locator DocumentHandler

File

Description

log4net.dll

3rd party component used for logging

log.config

Configuration file for logging

InstallLogging.config

Configuration file for logging

Via.SDK.ConnectorPlugins.dll

Locator platform assembly

Via.Client.Components.Core.dll

Locator platform assembly

Via.Utility.dll

Locator platform assembly

Via.Application.DocumentHandler.exe

The main executable

Via.Application.DocumentHandler.exe.config

Application configuration file

Via.DocumentHandler.Service.exe

Document Handler service – only installed for multi-user version of Document Handler.

AutomaticUpdater.dll

3rd party component used for automatic updates

wyUpdate.exe

3rd party component used for automatic updates

client.wyc

3rd party component used for automatic updates

OFFICE.DLL

Microsoft Office Core Primary Interop assembly

Via.Alfresco.ProtocolHandler.Plugin.dll

Plugin to handle documents from Alfresco

Via.Domino.ProtocolHandler.Plugin.dll

Plugin to handle documents from IBM Domino

Via.EdocsDM.ProtocolHandler.Plugin.dll

Plugin to handle documents from eDOCS DM

Via.Exchange.ProtocolHandler.Plugin.dll

Plugin to handle documents from Microsoft Exchange

Via.FileServer.ProtocolHandler.Plugin.dll

Plugin to handle documents from a fileserver

Via.LoboDMS.ProtocolHandler.Plugin

Plugin to handle documents from LoboDMS

Via.WorkSite.ProtocolHandler.Plugin

Plugin to handle documents from WorkSite

 In addition, we install Microsoft .NET Framework v4.5.2 for Document Handler v2.9 and newer – if you use the single user executable (not the MSI’s).

Log Files

Version

Location log file(s)

Single User

  • Locator 2.11 SR5 and older: c:\Users\<User>\AppData\Roaming\VirtualWorks\DocumentHandler

  • Locator 2.11 SR6 and newer: c:\Users\<User>\AppData\Roaming\ayfie\DocumentHandler

Multi User

  • Locator 2.11 SR5 and older: c:\ProgramData\Virtual Works\ViaWorks\Log

  • Locator 2.11 SR6 and newer: c:\ProgramData\ayfie\DocumentHandler

Windows Registry

Key

Description

Vw

The VirtualWorks protocol that we register – vw for short.

ViaWorksDocumentHandler

Used to automatically run Document Handler when Windows starts

Single User Version

Key

Path

Vw

HKEY_CURRENT_USER\Software\Classes

ViaWorksDocumentHandler

HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run

 

Multi User Version

Key

Path

Vw

HKEY_CLASSES_ROOT

ViaWorksDocumentHandler

HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Run

Windows Services

To avoid complications, such as having a “port-listening-process” for each terminal server user logged in, and to ensure proper functioning, the Document Handler Multi User version installs a Windows service named “ayfie DocumentHandler Service”, running under the Local System account.

...

  • Windows Server 2008 SP2

  • Windows Server 2008 R2 SP1

  • Windows Server 2012

  • Windows Server 2012 R2

  • Windows Server 2016

Known issues

On no longer supported versions of Edge and Chrome web browsers, the prompt before opening a document might not have the option to allow opening further documents without asking. In such case, registry has to be manually updated with the following keys (HKLM\SOFTWARE\Policies\Google\Chrome for Chrome and HKLM\SOFTWARE\Policies\Microsoft\Edge\ for Edge):

  • new entry AutoLaunchProtocolsFromOrigins with value [{"protocol":"vw","allowed_origins":[""]},{"protocol":"ViaWorksDocumentHandler","allowed_origins":[""]}]

  • new key URLAllowlist with 2 entries (incremented number as each entry name) with values: vw:* and ViaWorksDocumentHandler:*

Figures 1-3 show how the registry editor should look after required modifications.

...

Reference articles: