With the 2021-4.1 release users are seeing an error when launching the Local Routing Queue with CCH Axcess™ Document.
- Article Type:
- Problem Resolution
- Last Modified:
- 11/05/2022
Symptoms
With the 2021-4.1 release users are seeing an error when launching the Local Routing Queue with CCH Axcess™ Document.
Below is the error:
The Type
"WK.Telemetry.WcfMessageInspector.Client.TelemetryEndpoint,
WK.Telemetry.Wcf.MessageInspector.Client, Version = 1.0.0.0,
Culture = neutral, PublicKeyToken= 9247b3c6100d5b88'
registered for extension 'telemetryExtension' could not be
loaded. (C:\Program Files (x86)\WK\ProSystem fx Suite\Smart
Client\SaaS\configuration\z003
\CCH.Pfx.Document.LocalRoutingService.exe.config line 1612)
Below is the error:
The Type
"WK.Telemetry.WcfMessageInspector.Client.TelemetryEndpoint,
WK.Telemetry.Wcf.MessageInspector.Client, Version = 1.0.0.0,
Culture = neutral, PublicKeyToken= 9247b3c6100d5b88'
registered for extension 'telemetryExtension' could not be
loaded. (C:\Program Files (x86)\WK\ProSystem fx Suite\Smart
Client\SaaS\configuration\z003
\CCH.Pfx.Document.LocalRoutingService.exe.config line 1612)
Environment
CCH Axcess™ Document
Cause
N/A
Resolution
Development is working to identify the root cause and will plan a release for a fix. Until this issue is resolved, use the following steps as a workaround:
- Download the attached LRQConfigUpdate.bat on the machine that is running the Local Routing Queue.
- Execute the file. (This will copy the necessary files to resole the error).
- Launch the Local Routing Queue again and verify there are no errors.
Additional Information
N/A
| Solution Id | 000249037/145189 |
|---|---|
| Direct Link |
