After loading the dynamic services code onto a Windows VM, the service returns a server 500 error.
The underlying cause is that somehow the href handler’s config was declared with the name glossaryLinkHandler, but the actual section was named legacyDictionarySupport.
Issue description
After loading the dynamic services code onto a Windows VM, the service returns a server 500 error.
The underlying cause is that somehow the href handler’s config was declared with the name
glossaryLinkHandler, but the actual section was namedlegacyDictionarySupport.Steps to reproduce the issue
What's the expected result?
-
What's the actual result?
-
Additional details / screenshot
Related Tickets