Historian Client Control in InTouch Slow to Load (Delete Me 2)
Overview
If you are using a Historian Client control (such as the Query control or Trend control) in a container application (such as the InTouch HMI), and the computer on which the application is developed or is running does not have .NET Framework 2.0 SP2 or later installed AND does not have connectivity to the Internet, any windows that host a Historian Client control may be slow to open - in many cases extraordinarily slow - some reports as long as three or four minutes.
Known to exist in Historian Client Trend 10.x
Once the window is displayed, Trend operates normally and will continue to reopen without the delay until the next time the application is restarted.
This error means that Windows is unable to connect to a security certificate's revocation server.You may see certificate events or certificate revocation warnings in Event Viewer.
The underlying issue with this error is that a machine is being blocked from contacting the revocation servers for an SSL certificate. To pass the check a machine needs to contact at least one revocation server over HTTP/port 80.
IMPORTANT: Testing at InSource Solution Center of Excellence have shown that the issue can present with Dot Net Framework 3.5 when an Internet connection is available. Both conditions listed above DID NOT have to be present.
Troubleshoot/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 Dot Net Framework as described below.
This delayed/slow start condition is a known issue related to Microsoft Dot Net Framework 2.0 managed application that has an Authenticode signature. Application take longer than usual to start.
For a detailed explanation of the issue see Microsoft Article ID: 936707
http://support.microsoft.com/kb/936707
From the above referenced MS Tech Alert:
FIX: A .NET Framework 2.0 managed application that has an Authenticode signature takes longer than usual to start
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. The exact steps required are related to your network configuration such as access to port 80, Internet access, firewalls, etc. If you suspect that any of these conditions exist, it may be worth trying step 2 first. If you are working in a Terminal Services environment though, step 2 below requires that you perform the recommended steps for each user log on. In that case the fasted thing is to try step 1 first.
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.
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.