Historian Client control in InTouch slow to load
Last updated: March 6th, 2025Description
- Author: Brian Schneider
- Published: March 6th, 2025
Details:
Description
If using a Historian Client control (ex: Trend, Query, etc.) in a container such as InTouch HMI, windows may take a long time to open (upwards of 4 minutes). This can occur if the application was developed or is running on a computer which does not have .NET Framework 2.0 SP2 or later installed, or does not have Internet connectivity.
Problem is known to exist in Historian Client Trend 10.x
Cause
This problem occurs because the software will attempt to verify the SSL security certificates but is unable to reach one over the network (HTTP/Port 80).
IMPORTANT: Testing at InSource Solutions' Center of Excellence has shown that the issue can present with .NET Framework 3.5 when an Internet connection is available. Both conditions listed above DID NOT have to be present.
Testing For This Condition
To test for this condition add an Internet connection and reboot the machine. If the delay resolves, the cause is likely a known issue with Microsoft .NET Framework as described below.
This slow start condition is a known issue, discussed in Microsoft Knowledge Base Article 93607: "FIX: A .NET Framework 2.0 managed application that has an Authenticode signature takes longer than usual to start"
http://support.microsoft.com/kb/936707
From the above referenced MS Tech Alert:
"This problem occurs because a .NET Framework 2.0 managed assembly that has an Authenticode signature takes longer than usual to load. The signature is always verified when the .NET Framework 2.0 managed assembly that has an Authenticode signature is loaded.
Additionally, the .NET Framework 2.0 managed assembly may take longer than usual to load because of various other settings. For example, the .NET Framework 2.0 managed assembly may take longer than usual to load because of the network configuration."
This is a known issue to Wonderware and is under investigation. Reference Wonderware Change Request L00072837
NOTE: L00072837 is documented in the 10.0 SP1 Readme that is provided with the 10.0 SP1 install.
Goal
After implementing the fix shown below, any windows which host the Historian Trend Control should open without delay. You may need to implement one of both of the steps outlined below.
First Step
To work around this issue, create a config file for the executable of the container application and include the following text:
<?xml version="1.0" encoding="utf-8" ?>
<configuration>
<runtime>
<generatePublisherEvidence enabled="false"/>
</runtime>
</configuration>For example, if you are using the Query control in InTouch WindowMaker, create a file called “wm.exe.config” in Notepad or other text editor which does not add hidden formatting, add the above text, and place the file in the same directory as the wm.exe file.
As another example, if you are using the Trend control in InTouch WindowViewer, create a file called “view.exe.config”, add the above text, and place the file in the same directory as the view.exe file.
You should restart WindowViewer for the change to take effect.
Second Step
If adding or modifying an existing wm.exe.config file as described above does not improve load time for the windows on which the Trend control is hosted, you should also try the following.
1. Open Control Panel and click on Internet options
2. Click the Advanced tab to the far right on the Internet Options pane
3. Scroll down and uncheck the box for “Check for publisher’s certificate revocation”
4. Apply and OK the change. Restart WindowViewer.
.jpg)
What's Next
Test your application thoroughly, and review the Wonderware logger and Event Viewer System and Application logs for any indications of problems. Contact Technical Support if issues persist or if you have any questions about this solution. At time of publication this problem has not been reported with System Platform 2014.
Give feedback about this article
