Hi Josh,

It probably has to do with Global-Assembly-Cache (GAC) assemblies. The client tools - because of their COM+ registration towards the xml editors - register assemblies in the GAC. The problem assemblies are probably NLog (so logging framework). Probably either Docker or Docs Client Tools has an older version of the logging framework that by coincidence is missing features for one or the other.

-Dave

SRQ-13410

Thanks Dave!

From what I was seeing the Cached NLog version by the SDL Client Tools was preventing Docker from running.

Do you have a suggested solution for having both Docker and the Doc Client Tools working at the same time? Is there a way to have Docker ignore the cached version of NLog? Something like that?

thanks again!

-Josh

Hi Dave,

I sort of found a solution… every time PM (and I am assuming other client tools) launches it will add NLog to GAC so unfortunately this is not a one time effort. To run Docker I am able to manually remove the cached NLog from GAC using the following procedure.

Please let me know if this is not advised or there is a better way to handle it.

Remove NLOG from GAC:

Remove it using the GACViewer: http://www.nirsoft.net/dot_net_tools/gac_viewer.html

Run GAC Viewer as administrator

Navigate to File -> Select GAC folder

And select the folder: C:\Windows\Microsoft.NET\assembly\GAC_MSIL

Find Nlog and remove it:

Start Docker.

Microsoft assembly search path mostly always favors GAC over a local file. So probably the version that Docker requires is different from the version that SDL requires. If you know the exact NLog version numbers you might be able to submit the "largest" "compatible" number into the GAC, that might make both of them work. (If not, it is uninstall both, and try again).

Depending on the exact SDL version, there might be a workaround. I know it is bypassed in Tridion Docs 14. So if it is really an issue you can log a support request, best to hint "SRQ-13410"

-Dave