We have installed the TIBCO Scribe® Insight server with all updates, installed the NAV adapter all according to the TIBCO Scribe® Insight Manuals.  The TIBCO Scribe® Insight NAV adapter on the NAV server is listening on port 8085 as per documentation.  All modifications have been made on the NAV database, everything seems to be functioning, but when we try to connect to NAV through the Workbench we get this message:

"Delegate not set for 'Command' operation."
With this stack trace:
"System.ApplicationException: Delegate not set for 'Command' operation.

Server stack trace:
at Scribe.NavAdapter.NasHook.Receiver.Command(String commandName, String& errorMessage)
at Scribe.NavAdapter.NasHook.Transmitter.Command(String commandName, String xmlIn, String& errorMessage)
at Scribe.NavAdapter.NasHook.Transmitter.Command(String commandName, String& errorMessage)
at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Object[]& outArgs)
at System.Runtime.Remoting.Messaging.StackBuilderSink.SyncProcessMessage(IMessage msg)

Exception rethrown at [0]:
at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
at Scribe.NavAdapter.NasHook.API.ITransmitter.Command(String commandName, String& errorMessage)
at Scribe.NavAdapter.Helpers.Hook.GetTablesDefinitions()
at Scribe.NavAdapter.Database.DoTableFactory(Object db)"


There are several other errors that could be returned referencing the microsoft.msxml.dll, including:

• Cannot load type MSXML.DOMDocument.Microsoft.MSXML
• Cannot create an instance of the following .NET Framework object: assembly Microsoft.MSXML
• SetXmlBuffer Error:  Scribe.NavAdapter.NasHook.Receiver.SetXmlBuffer
• Codeunits may not compile.

When connecting to the NAV Adapter in the TIBCO Scribe® Insight Workbench, the message "Delegate not set for 'Command' operation" displays when the microsoft.msxml.dll does not exist or is in the wrong location.

This issue can result when the microsoft.msxml.dll file does not exist or is in the wrong location.  The file may exist in C:\Program Files (x86)\Microsoft.NET\Primary Interop Assemblies folder.  If you do not locate it on the server, you will need to contact Microsoft for a copy of the file.

In some cases the microsoft.msxml.dll can be copied into the same folder on the NAS server wherever the Scribe.NavAdapter.NasHook.dll file is located.  This could be in 1 or more of the following locations, for example:
...\Microsoft Dynamics NAV\90\Service\Add-Ins\Scribe
...\Microsoft Dynamics NAV\90\Role Tailored Client\Add-Ins\Scribe

Generally this is all that is required to resolve these errors.  However, if this fails to resolve the issue, then try to install/register the dll "Global Assembly Cache (GAC) folder for .NET. (One customer had to install into the GAC for Windows 2016 servers).