Wonderware Information Server 2014 R2 (version 5.6)

Posted on 596 views

Last revision: 09/17/2014

About This Readme

This Readme provides information about important resolved and known issues for Wonderware® Information Server 2014 R2(version 5.6).

For information about new features, hardware and software requirements, product compatibility, installation and upgrades, and user documentation, see the ArchestrA® System Platform Readme, which is located in the root folder of the ArchestrA System Platform installation media.

Readme files from previous releases of Wonderware Information Server are posted to the Wonderware Developer Network at http://wdn.wonderware.com/Downloads.

Resolved Issues

Known Issues

Resolved Issues

This section describes important resolved issues. The following list is not a comprehensive list of all resolved issues.

Wonderware Information Server version 5.6

L00126879: HF CR L00126541: SR 103128503: The ‘&’ (ampersand) character is not supported for node name, URL, and description in the custom link.
L00127104: HF CR L00126589: SR 12612638: When the number of users is quite large, the Wonderware Information Server portal fails to browse the users in the domain.By setting the Server.ScriptTimeout to 600 sec in the ADSIServer.asp page from the {SystemDrive}:\inetpub\wwwroot\Wonderware\useng\admin\configure location, the Wonderware Information Server portal will be able to browse the users in the domain.
L00128101: HF CR L00127740: SR 35312334: If you run query with multiple Historians in the Wonderware Information Server, it does not keep all the added Historians after browser is closed and reopened.
L00128175: HF CR L00127873: SR 103128389: If you generate Historian Client Reports using the custom time range, reports might not publish correct result time.
L00131027: SR 48910191: DateTimePicker in Wonderware Information Server reports does not show the correct DateTime for dd-MMM-yy format.
L00131029: SR 45710754: If you access Report through Wonderware Information Server, the report parameter is not displayed correctly as per the language selected in Internet Explorer.
L00131009: HF CR L00130383: SR 15317191 : Single page is printed if you print ArchestrA Report from AppServer script to a printer.

ArchestrA Web Exporter

L00122986: HF CR L00122742: SR 10416892: Some background picture and icons are not available in the Web page if Silverlight 5.0 is installed.To work around this issue, uninstall the Microsoft Silverlight 5 runtime and install the Silverlight 4 runtime, which is available from: http://go.microsoft.com/fwlink/?LinkID=149156&v=4.0
L00123454: HF CR L00123229: SR 42410088 : Crash of the w3wp.exe at regular interval can result in ArchestrA Graphic not getting the live data value.
L00124478: HF CR L00123889: SR 103126851: Shut-down of the InTouch viewer can lead to the following issue:

  1. CPU usage can increase up to 80% because of the LMX Publisher Service.
  2. After restarting the InTouch viewer, the CPU is still high and doesn’t decrease.
  3. After restarting the InTouch viewer, the published Window in Wonderware Information Server doesn’t work (as if it still cannot connect to InTouch node).

The workaround is to end the process LMX Publisher Service in Task manager and restart the service from the Service panel, or reboot the Wonderware Information Server node.

L00124924: HF CR L00124816: SR 103127254:Quality and status indicator displayed in Wonderware Information Server is not the same as in InTouch Viewer.
L00125891: HF CR L00125609: SR 45110038: Accessing URL across a secured connection (HTTPS) produces the following error: “Connection failed…Reconnecting to the data source..”.
L00128046: HF CR L00125560: SR 103127004: Inconsistent Blue Banner/Title/Frame appear around some Windows when they are brought up from another window.
L00128335: HF CR L00128182: SR 45710111: Pipes created using the ArchestrA Graphics are not visible in Wonderware Information Server after export.

< top of document >

Known Issues

This section describes important known issues.

Wonderware Information Server 5.6

L00133366: If you upgrade Microsoft Office 2010 to Microsoft Office 2013 on a computer which already has ActiveFactory Reporting Website feature of the Wonderware Information Server installed on it, the ActiveFactory published excel report does not work.
To workaround this issue, open the Microsoft Excel Application Properties dialog box by running the Component Services > DCOM Config and modify the following:

  • Select Interactive User option in the Identity tab of the Microsoft Excel Application Properties.
  • Select the Used Default option in the Access Permissions section in the Security tab of the Microsoft Excel Application Properties.

Wonderware Information Server 5.5

L00128516: If you install Microsoft Excel on a computer which already has ActiveFactory Reporting Website feature of the Wonderware Information Server installed on it, the Historian Client ribbon will not be available in Microsoft Excel.
To workaround this issue, you must repair the Wonderware Information Server and reconfigure the ActiveFactory Reporting feature.
L00128778: When you export a report using ArchestrA functions from the Historian database, the following error in appears in the ArchestrA Logger: “ReportsFileSaveServer failed: System.Web.Services.Protocols.SoapException: Server was unable to process request. —> System.IO.FileNotFoundException: Could not load file or assembly ‘Microsoft.ReportViewer.Common, Version=8.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a’ or one of its dependencies. The system cannot find the file specified.”The workaround is to install Microsoft Report Viewer Redistributable 2005, which you can download from http://www.microsoft.com/en-us/download/details.aspx?id=21916. After installing this, use the Wonderware Information Server post-install Configurator to re-configure the ArchestrA Reporting feature.
L00129010: On the Windows 8 and Windows Server 2012 operating systems, the HTTP Activation feature under .NET Framework 4.5 must be manually turned on before ArchestrA Web Graphics can get live data.
For Windows 8, the HTTP Activation feature is under .NET Framework 4.5 Advanced Services\WCF Services. For Windows Server 2012, the HTTP Activation feature is under .NET Framework 4.5 Features\WCF Services.

Wonderware Information Server 5.0

L00079240: If you install Microsoft Excel on a computer which already has ActiveFactory Reporting Website feature of the Wonderware Information Server installed on it, the Historian Client ribbon will not be available in Microsoft Excel.
To workaround this issue, you need to repair the Wonderware Information Server and reconfigure ActiveFactory Reporting Website.
L00079240: The ActiveFactory Reporting Website Trend samples do not work when you configure the ActiveFactory reporting feature with a virtual directory other than AFWEB. To make the Trend samples work with any virtual directory, go to Table Weaver Manager -> Query and edit the AFRWS Trend related Queries (AFRWSTrendQuery, AFScatteredPlot, AFTargetRegions and AFTrend_LiveUpdate) and change the URL field from “/AFWEB/Trend.aspx” to “/YOUR AFVIRTUALDIRECTORYNAME>/Trend.aspx”.
L00116108: When you uninstall Wonderware Information Server, the language packs are also uninstalled even if the Wonderware Historian Client is still available on the computer. You can manually install the language packs by running the setup.msi file in the appropriate subfolder of the following folder of the ArchestrA System Platform DVD: …\ArchestrA System Platform\CD-HistorianClients\HistorianClient\Lang\.
L00116141, L00121351: If you modify the ArchestrA System Platform installation and select to install the Wonderware Historian Client, the language packs are not installed automatically. A dialog box appears, and you must browse to the folder containing the setup program to install the language packs. You must manually install the language packs by running the setup.msi file in the appropriate subfolder of the following folder of the ArchestrA System Platform DVD: …\ArchestrA System Platform\CD-HistorianClients\HistorianClient\Lang\.
L00116553 If you are configuring Wonderware Information Server on certain operating systems with ASP.NET 4.0, errors may appear in the SMC Logger.
Workaround: Configure the Information Server again when errors appear in the SMC Logger. The configuration will complete successfully.
L00116895 LMX component warning messages stating “Failed to create access manager instance for thread id 4408, hr 0x8007000e” are logged in the ArchestrA Logger if you publish an InTouch HMI window containing Galaxy data references to the Wonderware Information Server portal using the ArchestrA Web Exporter and a WinPlatform is not currently deployed on the Wonderware Information Server portal computer.
Workaround: Deploy the WinPlatform on the Wonderware Information Server computer.
L00117554: Wonderware Information Server does not currently support InTouch indirect tags.
L00119770: The Wonderware Information Server Configurator adds aaTrend mime type to web.config for the default website, which affects 1.1 applications such as the reporting website for Wonderware Intelatrac.

To fix this, configure the mime type not for the entire IIS portal, but only for the ActiveFactory Reporting Website.

L00120350: If a data source contains a UTC DateTime that falls during the hour where clocks are advanced for Daylight Saving Time, the conversion of the DateTime in the OverView client’s time zone will be done incorrectly. OverView will add an extra hour to the local time.By default, the Information Model Server is configured to consider DateTimes as being UTC. However, DST rules are applied to these Date Times as if they were using the data source’s time zone.

For example, if your data source is in the Pacific Time Zone, date times between 03/11/2012 2:00:00 AM and 03/11/2012 3:00:00 AM will be incorrectly interpreted because they do not exist in the Pacific Time Zone.

Here are two examples. Consider that:

  • In the Pacific Time Zone, the Daylight Saving Time began at 03/11/2012 2:00:00 AM
  • In the Central European Time Zone, the Daylight Saving Time began at 03/25/2012 2:00:00 AM
  • The UseSourceTimeZone attribute is not configured. DateTimes in the data source are considered to be UTC.
  • OverView converts DateTimes in its local time zone.
Data Source Time Zone OverView Time Zone Source Value Value that should be displayed in Overview Actual Value displayed in OverView
Pacific Time Zone Pacific Time Zone 03/11/2012 2:06:26 AM 3/10/2012 6:06:26 PM 3/10/2012 7:06:26 PM
Central European Time Zone Pacific Time Zone 03/25/2012 2:06:26 AM 3/24/2012 5:06:26 PM 3/24/2012 6:06:26 PM
L00121079: When starting the OverView client, you get an error message indicating that the application is already installed from a different location.This normally happens if you have installed OverView by clicking the OverView link in the Information Server Portal and then try to access OverView by starting it using the url directly and the url being used has a different case than the url used during initial installation.

For example:

  1. You click on the OverView link in Information Server Portal, the OverView application is downloaded from http://infoServerNodeName/OverView/OverView.application.
  2. You paste in your web browser (or click a link someone has sent you by email) that reads http://infoServerNodeName/overview/overview.application. (no capital letters)

Another situation exist to generate this issue. After installing OverView from the OverView in Information Server portal, you try to start OverView by directly using the url and you use “localhost” instead of the Information Server node name.

In any case, you can always start OverView by either clicking on the OverView link on the Information Server portal or by starting OverView from the Windows Start menu.

L00121126, L00122742: Some ArchestrA Symbols cannot be loaded by Silverlight 5.To work around this issue, uninstall the Microsoft Silverlight 5 runtime and install the Silverlight 4 runtime, which is available from: http://go.microsoft.com/fwlink/?LinkID=149156&v=4.0
L00121739: Wonderware Information Server cannot be configured on a computer running a Simplified Chinese or Japanese Windows operating system if the installation path includes Asian double-byte characters.
L00122488: Errors occur when the dbo.ReportsFileSave stored procedure is executed within the Historian Runtime database to generate an ArchestrA Report (SSRS).To resolve this issue:

  1. Copy the Micrsoft.ReportViewer.Common.dll file from the Global Assembly Cache (GAC) folder of the SQL Server computer.
  2. Paste the Microsoft.ReportViewer.Common.dll in the C:\inetpub\wwwroot\wonderware\ArchestrAReports\bin\ folder of the SQL Server computer where Wonderware Information Server is installed.
  3. Run the printing.sql on SQL Server computer.

Wonderware Information Server 4.5

If you are using the Windows 7 operating system, the ArchestrA License Server stops responding if you remove the hardware dongle that is associated with a license managed by the License Server. Also, the License Server may intermittently stop responding.

To recover the License Server, reconnect the hardware dongle and then restart the License Server.

L00091440:

The Wonderware Information Server portal and InTouch View.exe are running on the same computer, and that computer is running a Windows Vista or later operating system. In this scenario, the Alarm Manager used by Wonderware Information Server to consume the alarms runs in Session 0, and another instance of the Alarm Manager used by InTouch View.exe to provide the current alarms runs Session 1. Because the SuiteLink Name Service (slssvc.exe) cannot register multiple instances with the same name, “AlarmMgr,” the first instance to be registered is the only one that communicates alarms. Therefore, the portal cannot retrieve current factory alarms that are generated by the InTouch software running on the local node.

To avoid this issue, run InTouch view.exe on a computer that is remote to the Wonderware Information Server portal computer.

L00111700:

On Wonderware Information Server node, if the ClientSide Setup window appears, enable Allow previously unused ActiveX controls to run without prompt option in the Security Settings of Internet Explorer.

By default, the above setting is enabled for the Local intranet and Trusted sites zones and is disabled for the Internet zone. If you face this issue, add this website to your trusted sites list in the Internet Options settings of Internet Explorer.

L00114588:

You must manually install the language packs for the Wonderware Historian Client product by running the setup.msi file in the appropriate subfolder of the following folder of the ArchestrA System Platform DVD: …\ArchestrA System Platform\CD-HistorianClients\HistorianClient\Lang\.

L00115377:

The WinXML Exporter may not correctly handle complex conditions for a color animation expression field.

Wonderware Information Server 4.0 with SP1

L00104609:

While working on Japanese or Simplified Chinese operating systems, if you publish a trend from the Wonderware Historian Client to Wonderware Information Server, and then access it through the Wonderware Information Server portal, an error occurs and the resulting trend is empty. This happens when the name of the trend file contains Japanese or Simplified Chinese characters and you are using Internet Explorer version 6. To resolve this issue, upgrade Internet Explorer to version 7 or 8.

L00109491:

After opening a Windowset page by copying its URL and pasting it in a browser window, some of the buttons on that page do not function. An error message is displayed stating access is denied. Such functionality is not supported for this release of Wonderware Information Server.

L00110331:

If you publish an InTouch window (where the window is updating I/O tag data) to a local Wonderware Information Server node on the Windows Server 2008 SP2 operating system where Terminal Services are enabled, and then open the same window in Wonderware Information Server, there are no I/O tag data updates.

To work around this issue, if you intend to have Wonderware Information Server on a Terminal Services enabled system, make sure that the Terminal Services option is enabled and configured before installing Information Server.

Wonderware Information Server 4.0

L00101808: If Microsoft Excel is started on the Wonderware Information Server portal node for viewing a report published from ActiveFactory Workbook, and no license is available, Excel shows a message indicating that license “ActiveFactory of version 10.0” was not found. Installing a valid SVoyager_Portal (version 4.0) license will fix this issue. You do not need to have an ActiveFactory license.
L00102375: If you publish the Workbook report to Wonderware Information Server portal with Long Name and accessing the Scheduled Report link in ActiveFactory Reports Node, it results in an error.
L00102545: The ArchestrA Web Exporter must be installed on a node that has the ArchestrA IDE installed. Additionally, you will need to install Microsoft Silverlight 3.0 or Silverlight 3.0 P1 on each computer that will be used to view the published symbols and windows in Internet Explorer. Microsoft Silverlight can be installed on those computers by clicking the Microsoft Silverlight logo that appears when you select to view a published symbol or window on a computer without Microsoft Silverlight installed. If the client computer does not have an Internet connection, you can download the package from Microsoft, move it to the client computer, and then manually install it. The link to download the package is: http://go.microsoft.com/fwlink/?LinkID=149156

Win-XML Exporter

L00061632: You cannot open the online help for the Win-XML Exporter in a non-English OS. Documentation for the Win-XML Exporter is only available in English. To open the documentation for Win-XML Exporter, double-click C:\Program Files\Wonderware\SuiteVoyager\WinXMLExporter\Books\english\StartDesign.htm.  This starts Internet Explorer and opens the documentation page.  (If a popup blocker is installed, disable it.)
L00011415: The Win-XML Exporter installation program does not detect user privileges at the start of the installation. You must be an administrator on the computer on which you are installing the Win-XML Exporter. If you are not an administrator, the Win-XML Exporter installation program fails when it tries to copy files to the computer.

ArchestrA Web Exporter 1.0

L00094337: If you are viewing published symbols across a secure connection (HTTPS), you cannot view live data. To work around this problem, you need to modify the web.config file in the Information Server. To do this:

  1. Open the file C:\Inetpub\wwwroot\Wonderware\AADataSvc\web.config in a text or XML editor.
  2. In the system.ServiceModel section, locate the entry:
    <endpoint bindingConfiguration=”HttpNTLMBinding”
  3. Change “HttpNTLMBinding” to HttpsNTLMBinding”
  4. Save and close the web.config file.
  5. Restart Internet Information Services (IIS) by doing the following:
    From a command line, type iisreset and press Enter.
  6. Restart the ArchestrA LMX Publisher service.
L00095140: If you open a large number of Information Server sessions in the Internet Explorer at the same time, an Internet Explorer connection error may appear. This is caused by a limitation in the Thread Pool that limits the maximum number of sessions to the default of 350 for each CPU.

Note: We do not recommend increasing the default number of sessions due to the resulting high usage of system resources.

To work around this issue, change the value of MaxThreadPoolSize in the AppSettings section of the web.config file. Do the following:

  1. Open the file C:\Inetpub\wwwroot\Wonderware\AADataSvc\web.config in a text or XML editor.
  2. In the AppSettings section, locate the entry:
    <add key=”MaxThreadPoolSize” value=”350″>
  3. Set the value parameter to the number of sessions you want per CPU.
  4. Save and close the web.config file.
  5. Restart Internet Information Services (IIS) by doing the following:
    From a command line, type iisreset and press Enter.
  6. Restart the ArchestrA LMX Publisher service.
L00095827: If you configure an element with a Horizontal or Vertical Slider animation, at run time the slider tooltips showing the horizontal and vertical position do not move with the slider. This is caused by a limitation in Microsoft Silverlight 3.0.
L00097077: In published symbols, adjacent elements without boundary line may show a small gap between them. This is caused by a defect in Microsoft Silverlight 3.0.
L00097084: The coordinates of an InTouch popup window are not calculated correctly when opened in Internet Explorer. If the popup window is called from a Show QuickScript, it opens at the top left of the client area. If the popup window is called from a Show Window animation, it opens in the center of the client area. In both cases the configured coordinates are ignored.
L00097624: In published symbols, one pixel wide lines will not completely cover the background on which they are placed. This may effect the visual quality of the published symbol. This is caused by a defect in Microsoft Silverlight 3.0.
L00098489: The input animations of elements in a group (set up as an icon) in ArchestrA Symbols that are then embedded into an InTouch application, configured with InTouch input animation, and then transformed and published, still work in the published displays. Expected behavior is that the InTouch input animations override the input animations of the embedded ArchestrA Symbol, as it does in WindowViewer.
L00098852: If you configure more than one element with a pushbutton animation and different shortcut keys in an ArchestrA symbol, the shortcut keys do not work correctly in the published symbol.
L00098905: The percentage fill animation on ArchestrA Symbol element groups (with TreatAsIcon set as TRUE) follows the behavior of InTouch cell fill and not that of ArchestrA Symbols running in WindowViewer. Specifically, it follows the following rules:

  • Fill Style: Follow the fill style of each individual element in the group.
  • Unfill Style: Follow the unfill style of the group.
  • Fill Percentage: Follow the fill percentage of the group.
  • Fill Direction: Follow the fill direction of the group.
  • Fill Orientation: Follow the fill orientation of the group.
L00098962: If you open the String User Input dialog box of a published symbol at a resolution of 1024 x 768, you may not be able to see the OK, Cancel, Clear buttons, and buttons to move the cursor. To avoid this issue, switch to a higher resolution or view the published symbol in Internet Explorer full screen mode. To switch to full screen, press F11.
L00098968: If you configure a text element with the characters “{” or “}”, any animations except Tooltip or User Input do not work correctly in the published symbol. Avoid using the characters “{” and “}” in your application design and in your set of permitted characters.
L00098979: If you configure a Show Symbol animation with positioning relative to parent in a symbol that is already a popup symbol from another symbol, the positioning does not work correctly in the published symbol. Positioning relative to parent only works correctly for the first popup called from a symbol.
L00099100: You can successfully create a project containing one or more of the following characters: [email protected]#$%^&*()_+
However, you should not be able to. Avoid using any of the characters to prevent unpredictable results.
L00099147: If you install ArchestrA Web Exporter on a computer that has an older version of Microsoft Silverlight 3.0 SDK installed, the installation wizard does not remove the Silverlight SDK installation for you and the installation ends with a message. Uninstall Silverlight SDK from the Control Panel and then start the installation of ArchestrA Web Exporter again.
L00099223: You cannot change the value of a custom property of an embedded symbol with the SetCustomPropertyValue function in the hosting symbol. To work around this problem, create a new custom property in the hosting symbol and override the public custom property of the embedded symbol. You can now use the SetCustomPropertyValue function in the hosting symbol to change the new custom property which then redirects the custom property in the embedded symbol.

Example: Symbol S1 with the custom property CP1 is embedded in the Symbol S2. In Symbol S2, you cannot use the SetCustomPropertyValue function to set S1.CP1 to a value. To work around the problem, in symbol S2 create a custom property CP2 and override S1.CP1 with S2.CP2 in the Properties Editor. You can now use the SetCustomPropertyValue function to change the value of S2.CP2 which then also changes the value of S1.CP1.

L00099399: Elements in published ArchestrA symbols with radial gradients and focus scale values other than zero do not appear correctly. They appear with zero width and height focus scale. This is caused by a limitation in Microsoft Silverlight.
L00100142: ArchestrA Web Exporter does not allow “.” for Local Project Path” field value to store web project files.
L00100145: This release does not support following line cap styles: RoundAnchor, SquareAnchor, DiamondAnchor and ArrowAnchor. These line cap styles will be mapped to the other supported line cap styles. Below is the mapping:

  1. RoundAnchor transforms to Round
  2. SquareAnchor transforms to Square
  3. DiamondAnchor and ArrowAnchor transforms to Triangle

Wonderware Information Server 3.1

L00053415: When you start an ActiveFactory desktop client application or control, it takes 30-60 seconds for the application or control to open.

The computer you are using the control or application on does not have access to the Internet. The problem occurs because of the way Windows validates digital certificates used in code signing, such as that used by ActiveFactory. By default, when a computer is connected to a network, Windows attempts to access the certificate publisher’s “certificate revocation list” (CRL) to see if the certificate being used has been compromised. When the computer has access to the Internet, this check typically takes less than a second. However, when the computer does not have access to the Internet, this check waits on a timeout for the attempt to fail, normally about two minutes. To work around this issue, go to the computer on which the ActiveFactory control or application is installed and configure the Internet Explorer security options so that the Check for publisher’s certificate revocation check box is not selected.

L00058984: A pop-up for upgrading client components to newer version is displayed if your computer has lower version of the Wonderware Information Server Client Components installed. If the ActiveFactory shared component is already installed, the message “Remove the existing version of this product by using the Add/Remove Programs on the Control Panel” is displayed when you access the application. The message may pop-up again if the browser cache is not cleaned. Clean up the browser cache after installing the newer version of the Wonderware Information Server Client Components.
L00062855: Scheduled aaReports are not generating after DST time change in Fall Back settings, that is, from 1:59:59 AM to 1:00:00 AM. This is a known SQL Agent issue, the agent does not trigger during “the second hour,” see: http://support.microsoft.com/kb/931975/en-us. Extract: “…. However, there is a known issue in which scheduled SQL Server Agent jobs cannot run for one hour during the period when the November 2007 DST change occurs. After the clock is changed back from 2:00 A.M. to 1:00 A.M. on November 4, 2007, SQL Server Agent jobs would skip the next hour and wait until 2:00 A.M. to start next run. This is a known issue. This issue occurred even under the pre-2007 DST conventions. This issue does not result from the changes to DST in 2007 ….”
L00063757: The ActiveFactory Reporting Website Manual Data Entry does not save a value to the Historian database if you do not have write permission. Change the user for the Historian data source to wwAdmin or aaAdmin in the SDS Manager. The wwAdmin and aaAdmin user has write permission to enter values in the Historian database. After changing the user, re-configure the ActiveFactory feature and update the Manual Data Entry.
L00077735: Configuring Data Sources and Providers. The User Guide includes complete, specific guidance for configuring the RWS for use over HTTP/HTTPS in a single place. See Tech Note 541 (http://www.wonderware.com/support/mmi/comprehensive/kbcd/html/t002282.htm) for more information.
L00080904: A warning occurs when you configure the Wonderware Information Server with default Windows authentication mode pointing to SQL Server 2008 database. This happens because the user does not have “SYSADMIN” privileges. By default, the ‘BUILTIN\Administrators’ security group is not added to ‘sysadmin’ server role. To add this security group to ‘sysadmin’ server role, you need to run the stored procedure ‘SYS.SP_GrantLogin’ as given below:

EXEC SYS.SP_GrantLogin ‘BUILTIN\Administrators’.

After executing the stored procedure, you need to open the “BUILTIN\Administrators” login properties and add it to the ‘sysadmin’ security role.

L00081067: AFTrendSamples do not work if the ActiveFactory Reporting Website feature is not installed.
L00081275: Exception occurs when Wonderware Information Server is in the repair mode. This is a Microsoft related issue. An exception occurs during the repair mode as some COM+ components run in the background.
L00087936: You cannot see live data in the sample reactor window in Process Graphics on Windows 2008 operating system. This is because InTouch 10.1 is not supported on Windows 2008 operating system.
L00088749: The Factory Alarms will not work properly when you backup and restore the content in the Windows authentication mode. This problem is due to an exception caused by executing the stored procedure getproviderlist_sp in the SuiteVoyager database because of a dependency on the DataSourceTVF(SQL Assembly) which uses the SDS assembly. This problem is documented in Microsoft’s KB article http://support.microsoft.com/kb/918040.

To rectify, use any one of the following workarounds:

  • Change the database ownership to the logged user. Execute the following statement in SQL Query Analyzer after the restore operation.USE <DatabaseName>
    GO
    EXEC sp_changedbowner sqlUserName

    For example:

    USE SuiteVoyager
    GO
    EXEC sp_changedbowner ‘sa’ ;

  • Select the SQL authentication mode to backup and restore the content.
L00089162: An error message appears when you upload a file from the Custom Link configuration page. In IIS 7.0, go to the Wonderware virtual directory, and configure the properties for ASP applications. Edit the property Maximum Requesting Entity Body Limit and set the value as per your file size. By default, the supported file size is 200KB.
L00089810: On a computer with Windows Vista or Windows 7 operating systems, the Wonderware Information Server portal does not display the Alarm Viewer Control and the Tree View Control. As a workaround, customize the following settings in the Internet Explorer.

  1. Start Internet Explorer. On the Tools menu, click Internet Options. The Internet Options dialog box appears.
  2. Click the Security tab.
  3. Click Trusted sites or Local intranet.
  4. Click Custom Level. The Security Settings dialog box appears.
  5. Click the Prompt or Enable option for Download unsigned ActiveX Controls.
  6. Click the Prompt or Enable option for Initialize and script ActiveX controls not marked as safe for scripting.
L00090726: An error is displayed in the Wonderware Information Server Portal when the sample reports for Alarm and Historian are accessed and deployed using the Deploy Reports Utility. This is a limitation of the Tag Picker. The reports that use the Tag Picker, including the sample alarm reports require:

  • A default Historian data source
  • Installation of the Historian samples
L00090847: An error occurs when you access the Alarm Pareto Control in the Wonderware Information Server Portal. To rectify this, launch the Wonderware Information Server Portal using the Run As Administrator command.
L00091048: Custom static reports are not available for deletion in AFReports Manager -> Static Report. To delete the same, open the ReportParameters.xml file and delete the entry along with the source file.
L00091053: An error occurs when you access the Reports link in the Wonderware Information Server Portal after logging in as a system administrator and not as a portal admin of the Wonderware Information Server installed node.

To avoid this error, perform any one of the following workarounds:

  • Start Internet Explorer using Run As Administrator command and navigate to the portal using the system administrator credentials.
  • 1. Start Internet Explorer using Run As Administrator command with the credentials of the user who had configured the Information Server feature and type the URL http://localhost/reports/.
    2. Click Properties -> New Role Assignment.
    3. Type the System administrator’s user name and grant the roles by selecting the check boxes for the Content Manager option.

Versions Prior to Wonderware Information Server 3.1

L00055354: It is not possible to log on to Wonderware Information Server if the account name contains Asian double-byte characters. No workaround is available.
L00056077: SQL Server Reporting Services may fail to generate scheduled report snapshots during the fall Daylight Saving Time switchover. Also, time zone offset information may be wrong for snapshots generated during the switchover time period. This is a general issue with Microsoft SQL Server Reporting Services.
L00058228: Errors may occur in reports after changing a data source to point to a SQL Server that uses a different collation. Errors may occur in reports that use collation-sensitive operations if the SQL Server used as the data source uses a different collation than expected. This may be the case when editing the data source definition to point to a different SQL Server than the one that was used when the report was deployed. One report that is affected by this issue is the “Group Period” sample report.
L00058236: When setting up a data source that uses HTTP to connect to a historian, the Test Connection feature tests a direct SQL Server connection, not an HTTP connection. This behavior is as designed. Only clients use HTTP mode to establish a historian connection. Wonderware Information Server itself still requires a direct SQL Server connection. Therefore, the Test Connection feature tests the direct connection, not the HTTP connection.
L00058401: Preview of content unit crashes when the query is configured for 1000 alarms and display type is SmartSymbol. When you import an InTouch window with 1000 alarm records logged into the database and then configure a content unit with a display type of SmartSymbol, the total number of symbols = 1000, links = binding, and target = contentunit, the preview crashes.
L00058623: Additional steps may be necessary to establish a connection to an Oracle database. To set up a data source to connect to an Oracle database, some additional configuration steps may be necessary. See the following Microsoft article for details: http://support.microsoft.com/kb/255084.
L00058697: When using the Trend or Query controls in Wonderware Information Server from a client running the Microsoft Windows Vista or Windows 7 operating systems, an Internet Explorer security warning appears, requesting permission to run a program outside of protected mode. To work around this issue, allow the program to run in unprotected mode.
L00059073: Accessing drill-through reports may not work when viewing a report from Wonderware Information Server. In certain situations, you may not be able to access a drill-through report (that is, call a detail report from a main report) when viewing a SQL Server Reporting Services report from Wonderware Information Server. Instead, the main report is generated again or an error message appears. This is due to an issue with the Microsoft Report Viewer control. No workaround is available.
L00059809: Wonderware Information Server is not installed properly when specifying a virtual directory name that contains a percent sign (%). Although virtual directories in IIS are not allowed to contain this character, the setup program does not reject the invalid name. The setup procedure subsequently completes without errors, but the resulting installation is corrupted.
L00059947: When exporting an ArchestrA Reporting sample report to a PDF file, Asian double-byte characters don’t appear correctly. To work around this issue, edit the reports to use a font that supports these characters.
L00060022: When viewing a Process Graphics window that contains an InTouch Alarm Viewer control, Internet Explorer hangs or crashes if the InTouch alarm manager (alarmmgr.exe) isn’t running on the client computer. No workaround is available.
L00060330: When using the setup program’s Modify feature to install or uninstall the ActiveFactory Reporting feature, the ActiveFactory language packs are not installed or uninstalled accordingly. To work around this issue, run the ActiveFactory client setup package on the Wonderware Information Server computer. (The client setup is available under the ActiveFactory node in the Launch Pad.)
L00060369: Runtime errors may occur when using a published InTouch symbol display with a Table Weaver query that returns NULL values. If you use a published InTouch symbol that contains a value display tied to a Real tag to display the results of a Table Weaver query, runtime errors occur if the query returns a NULL value for the column that is mapped to the Real tag.
L00060567: The HideSelf() function may not work in nested popup windows. Calling the HideSelf() function to close a published InTouch popup window that was in turn opened from another popup window may not work. To work around this issue, don’t nest popup windows (that is, open one popup window from another).
L00060576: When using the Tag Picker to select tags as report parameters, the server name in the Server pane may not match the computer name in the URL used to access Wonderware Information Server. For example, if the URL uses the server’s IP address, the Tag Picker still shows the computer’s host name.
L00060930: In time zones whose offset from UTC is a fractional number of hours, scheduled hourly ActiveFactory reports are not executed on the full hour. For example, in a time zone with an offset from UTC of 5 hours and 30 minutes, hourly reports are generated at 1:30, 2:30, 3:30 local time and so on. To work around this issue, edit the schedule in the configuration.config file and specify a start time offset of 30 minutes. Assuming, for example, the <STARTTIME> element for the schedule looks as follows: <STARTTIME>*,*,*,0</STARTTIME> Change it to the following: <STARTTIME>*,*,*,30</STARTTIME>
L00061258: Misleading error message may appear when deploying a report that was developed using Report Builder. When you use the Deploy ArchestrA Reports utility to deploy a report that was developed using Report Builder, an error message may appear that the aaReports data source could not be found. You can ignore this message. The report is deployed correctly.
L00061262: Trend and Query controls in Internet Explorer still use the name of the account you logged into the computer, rather than the name you used to log into Wonderware Information Server. If you:

  1. Install Wonderware Information Server with the ActiveFactory features.
  2. Install a license by pointing to a license server without licenses for ActiveFactory and Active Factory Pro, but with ActiveFactory Web and ActiveFactory Pro Web licenses.
  3. Logon on a client node with a user account different than the default Wonderware Information Server user.
  4. Connect to Wonderware Information Server computer from a remote computer with a different user.

The license status on the Wonderware Information Server License Manager page shows the user logged onto the computer rather than the user logged onto the Wonderware Information Server computer. The reason for this is that the name of the user logged into the computer is used when named licensing is enforced.

L00061351: In the ActiveFactory Reporting web site, browsing from the main pane shows the wrong report list. The system has two sets of scheduled published reports: HOURLY and FIFTEENMINUTES. When browsing through the main (right) pane, drilling down to the HOURLY reports shows the FIFTEENMINUTES reports. The workaround is to use the tree but not the right-hand panels.
L00061655: The Publish option on ActiveFactory Trend is disabled. This can occur with a new InSQL Server and/or when the InSQL Server Runtime database has been rebuilt. In such cases, the tables required for publishing are missing until an ActiveFactory desktop client connects to it or Wonderware Information Server is installed and points to that InSQL computer. Once the tables have been created, the tables can be populated manually using this script (modify the computer names and paths to match your configuration): /* insert the report site */
use Runtime insert aaHistClientReportSite
(SiteURL, SitePath, Description, SiteVersion)
values
(‘http://QAINT273/AFWEB’,
‘C:\Inetpub\wwwroot\AFWeb’,
NULL,
1) /* Insert the Report Folders */
declare @sitekey int select @sitekey = ReportSiteKey
from aaHistClientReportSite
where SiteURL = ‘http://QAINT273/AFWEB’ insert aaHistClientReportsFolder
(ReportSiteKey, ReportFolderName, Description, ReportType, Disabled, JobType)
values (@sitekey, ‘Static’, ‘Static Reports’, 1, 0, 0) insert aaHistClientReportsFolder
(ReportSiteKey, ReportFolderName, Description, ReportType, Disabled, JobType)
values (@sitekey, ‘EVENT’, ‘Event’, 4, 0, 0) insert aaHistClientReportsFolder
(ReportSiteKey, ReportFolderName, Description, ReportType, Disabled, JobType)
values (@sitekey, ‘FIFTEENMINUTE’, ‘Every 15 minutes’, 4, 0, 0) insert aaHistClientReportsFolder
(ReportSiteKey, ReportFolderName, Description, ReportType, Disabled, JobType)
values (@sitekey, ‘HOURLY’, ‘Every hour’, 4, 0, 0) insert aaHistClientReportsFolder
(ReportSiteKey, ReportFolderName, Description, ReportType, Disabled, JobType)
values (@sitekey, ‘DAILY’, ‘Every day’, 4, 0, 0) insert aaHistClientReportsFolder
(ReportSiteKey, ReportFolderName, Description, ReportType, Disabled, JobType)
values (@sitekey, ‘WEEKLY’, ‘Every week’, 4, 0, 0) insert aaHistClientReportsFolder
(ReportSiteKey, ReportFolderName, Description, ReportType, Disabled, JobType)
values (@sitekey, ‘MONTHLY’, ‘Beginning of every month’, 4, 0, 0) insert aaHistClientReportsFolder
(ReportSiteKey, ReportFolderName, Description, ReportType, Disabled, JobType)
values (@sitekey, ‘SHIFT’, ‘Every shift’, 4, 0, 0) insert aaHistClientReportsFolder
(ReportSiteKey, ReportFolderName, Description, ReportType, Disabled, JobType)
values (@sitekey, ‘OnDemand’, ‘On Demand Reports’, 2, 0, 0)
L00066339: If an old Wonderware product has been installed, then Invensys License Server is installed and later uninstalled, no Invensys License Manager (LicView) is available on that computer anymore. The workaround is to reinstall the Invensys License Manager, aalicview.exe, from the license installation media.
L00010926: The SuiteVoyager alarm consumer query does not return alarms of contained Wonderware Information Server Areas. The query returns only alarms that are in the specific Area. To work around this, specify each alarm group in the alarm query. The only upper-level group that is handled correctly is the $System parent alarm group from the InTouch alarm provider. This group returns all alarms from the provider.
L00011706: If you use the PI(), StringFromTime(), and StringSpace() functions as expressions for display objects in InTouch, the displays do not resolve correctly in published windows. Work around this problem by introducing a tag into the expression so that the expression is updated in the browser. For example:

  1. Define an analog tag “tag0” and assign it a value 0. Replace the expression PI() with PI() + tag0.
  2. Define a message tag “mtag0” and assign it an empty string. Add “mtag0” to the StringFromTime() and StringSpace() expressions.
L00017054: Run-time errors occur when printing a window in a converted InTouch application. After you clear the error dialog boxes, printing resumes and works properly.
L00033125: If you attach an image to a Content Unit and then replace it with another image, you do not see the change unless Internet Explorer is correctly configured. To configure Internet Explorer:

  1. On the Tools menu, click Internet Options. The Internet Options dialog box appears.
  2. In the Temporary Internet Files group, click Settings. The Settings dialog box appears.
  3. Click Every visit to the page.
  4. Click OK to close the Settings dialog box.
  5. Click OK.
L00033464: Large Table Weaver queries may time out, and results may not be shown. Table Weaver is optimized for queries that produce 1,000 rows or less. While Table Weaver can support larger results, there may be a significant performance penalty. In extreme cases with thousands of results, you may need to increase the IIS application script timeout for the query to complete. Microsoft Internet Explorer may also have trouble showing very large result sets.
L00033701: A “Page cannot be displayed” error message occurs when the tabular display “Rows per view” is configured with a numeric value greater than 32767.
L00041235: Excel files contain Auto_Open() macros to perform a variety of functions when the file is opened. When published in AFRWS these macros do not get run and the report is invalid. The following article describes some of the differences between Auto_Open and Workbook_Open:
http://www.dailydoseofexcel.com/archives/2004/08/18/running-macros-when-a-workbook-is-opened Summary: “The Workbook_Open event resides in the ThisWorkbook module. The Auto_Open macro belongs in a standard module. If you have both, the event procedure will fire before the Auto_Open procedure. Other than their location, the primary difference between the two is what happens when you open a workbook via code. The event will still fire, the Auto_Open macro will not. VBA provides a RunAutoMacros method of the workbook object that allows you to run the Auto_Open code when a workbook is opened through VBA.” Suggested workaround: Instead of “Auto_Open”, use the “Workbook_Open” event. For example: Private Sub Workbook_Open()
Worksheets(“Sheet1”).Range(“A1”).Value = Date
Worksheets(“Sheet1”).Range(“B1”).Value = Time
End Sub
L00044583: ActiveX controls do not install even after adding the SuiteVoyager URL as a trusted site. Problem: When you click the Download/Upgrade button on the Process Graphics window, a dialog box appears with the message “This site might require the following ActiveX control: ‘Wonderware SuiteVoyager client cabinet file’ from ‘Invensys Systems, Inc.’. Click here to Install.”. If you click Install, you see a dialog box with the message “Failed to download the client side software.” This could be due to insufficient privileges. Cause: This happens because of the enhanced security settings of Windows Server 2003 and/or Windows XP SP2, if used as a client. ActiveX must be enabled in the Internet Explorer security settings. Solution: In Internet Explorer click on Tools, Internet Options, Security and select Internet. Click on Custom Level and select Enable for Script ActiveX Controls marked as safe for scripting.
L00046228: To be able to use Backup and Restore capabilities of SuiteVoyager that uses a remote SQL Server as its database, the MSSQLServer and SQLServerAgent services on the remote computer should be running under a network domain account and not a local system account.
L00047046: Backup process times out when backing up a large amount of configuration data. Problem: When you backup a Wonderware Information Server configuration that contains a large amount of data (for example a large published InTouch application) the backup process may time out. Solution: Click Start, Programs, Administrative Tools, Internet Information Services (IIS) Manager. In IIS Manager do the following:

  1. Expand the Internet Information Services node.
  2. Expand your computer name node.
  3. Expand the Web Sites node.
  4. Expand the Default Web Site node.
  5. Right click the SuiteVoyager web site and choose Properties.
  6. On the Virtual Directory tab click Configuration. The Application Configuration dialog appears.
  7. Click the Options tab.
  8. Increase the ASP script timeout value, for example 300 seconds.
L00047233: Adding and removing domain users to user roles with the SuiteVoyager User Manager fails. Solution: Make sure that the users in the SuiteVoyager Administrators role are also in local system Administrators group in the computer where SuiteVoyager server is running in order to add/delete users from the User Managers page.
L00005386: If you upload a file to the Custom Links area of the portal, make changes to the file, and then upload the file again, Internet Explorer may not recognize the change. You can force Internet Explorer to reload the file by changing the cache settings. To configure Internet Explorer:

  1. On the Tools menu, click Internet Options. The Internet Options dialog box appears.
  2. In the Temporary Internet Files group, click Settings. The Settings dialog box appears.
  3. Click Every visit to the page.
  4. Click OK to close the Settings dialog box.
  5. Click OK.
MEDU00000981: The ActiveFactory Reporting Website does not detect language variants when determining the client language to show. Four languages are supported for the ActiveFactory Reporting Website: French, German, Japanese, and Simplified Chinese. The countries supported are France, Germany, Japan, and China. If one of the supported languages is set for Internet Explorer, but a non-supported country is specified, then the ActiveFactory Reporting Website shows the English version. For example, if German(Austria)[de-at] is set for Internet Explorer, the website shows the English version instead of the German version. To work around this problem, add the appropriate supported language/country combination to the Internet Explorer configuration. To add the language/country combination:

  1. Start Internet Explorer.
  2. On the Tools menu, click Internet Options. The Internet Options dialog box appears.
  3. Click Languages. The Language Preference dialog box appears.
  4. Click Add. The Add Language dialog box appears.
  5. Select the appropriate supported language/country entry for the language you want to show: Chinese(China)[zh-cn], French(France)[fr], German(Germany)[de] or Japanese(Japan)[ja].
  6. Click OK.
  7. In the Add Language dialog box, move the selected language to the top of the Language list.
  8. Click OK.
  9. Click OK to close the Internet Options dialog box.
  10. Restart Internet Explorer.

< top of document >


© 2014 Invensys Systems, Inc. All Rights Reserved.

Leave a Reply

Your email address will not be published. Required fields are marked *

+ 81 = 89