Tech Note 839 Resolving Timeout Issues for Wonderware Intelligence v1.5 All Tech Notes, Tech Alerts and KBCD documents and software are provided "as is" without warranty of any kind. See the Terms of Use for more information. Topic#: 002631 C reated: March 2012 Introduction Sometimes Wonderware Intelligence queries take a long time to execute and may fail if certain predefined timeout periods expire. You might see Warning or Error messages in the ArchestrA Logger about "the Request Channel timed out", or "Local socket timeout", or some other generic kind of timeout message. Wonderware Intelligence timeouts you might encounter fall into two general categories: WCF (Windows Communication Foundation) Communication Timeouts Between the IDE and the Intelligence Server (Wonderware Intelligence Service). Between the Intelligence Server and the Data Adapter Service (Wonderware Intelligence DA). SQL Timeouts Data Adaptors for the data source. The Intelligence database. Note: All timeout settings in the following examples use a value equivalent to 2 hours or 4 hours, but these are for illustrative purposes only. The actual values used should be based on the system experiencing the issue. Also, the values may vary among the different settings as needed; they do not all need to be configured to the same timeout value/amount. Application Versions Wonderware Intelligence 1.5 WCF Timeouts There are two aspects that must be considered with WCF timeouts, client and server, since both can specify how long they are willing to wait for communications to occur on a channel. Changing one or the other may not resolve a timeout issue since a lengthy communication can cause either side of the channel to time out. For WCF communications between the Intelligence Server and the Data Adapter Service, modify the following timeout settings: To Configure WCF Client Timeouts machine where the Intelligence Server is installed. https://wdnresource.wonderware.com/support/kbcd/html/1/t002631.htm 1/5
2. Use Notepad to open the IntelligenceService.exe.config file. 3. In the <appsettings> definition element (i.e. <appsettings> </appsettings>), you should see a key definition called DasClientSendTimeoutSeconds. 4. Set its value to 7200. This provides a client-side timeout of 2 hours and will apply to all WCF communications between the Intelligence Server and the Data Adapter Service. 5. If the DasClientSendTimeoutSeconds key definition is missing, then add the following to the <appsettings> definition: <!-- Configurable client send timeout, in seconds (Intelligence Data Adapter Service) --> <add key= DasClientSendTimeoutSeconds value= 7200 /> 7. Restart the Intelligence Server (i.e. the Wonderware Intelligence Service) FIGURE 1: WCF CLIENT TIMEOUT SETTING Configuring WCF Server Timeouts machine where the Data Adapter Service is installed. 2. Open the IntelligenceDataAdapterService.exe.config file in Notepad. 3. In the <nettcpbinding> definition (i.e. <nettcpbinding> </nettcpbinding>), you should see a binding definition (i.e. <binding> </binding>) with a property called sendtimeout. 4. Set its value to 02:00:00. This provides a 2 hour timeout for all WCF communications between any client and the Data Adapter Service. 5. If the sendtimeout property is missing, insert it after the name property in the binding definition. Note that only spaces are used to separate properties in the definition. https://wdnresource.wonderware.com/support/kbcd/html/1/t002631.htm 2/5
7. Restart the Data Adapter Service (i.e. the Wonderware Intelligence DA) FIGURE 2: WCF SERVER TIMEOUT SETTING SQL Timeouts You can configure two SQL timeout settings: the Data Adapter Service and the Intelligence data store: To Configure the Data Adapter Service SQL Command Timeout machine where the Data Adapter Service has been installed. 2. Open the IntelligenceDataAdapterService.exe.config file in Notepad. 3. In the <appsettings> definition (i.e. <appsettings> </appsettings>), you should see a key definition called CommandTimeout. 4. Set its value to 7200. This provides a 2 hour command timeout for any SQL command issued by a data adapter. 5. If the CommandTimeout key definition is missing, add the following to the <appsettings> definition: <!-- Configurable command timeout, in seconds --> <add key= CommandTimeout value= 7200 /> 7. Restart the Data Adapter Service (i.e. the Wonderware Intelligence DA). https://wdnresource.wonderware.com/support/kbcd/html/1/t002631.htm 3/5
FIGURE 3: DATA ADAPTER SERVICE SETTING To Configure the Intelligence Data Store SQL Command Timeout machine where the Intelligence Server has been installed. 2. Open the EMIRuntimeConfigurator.xml file using Notepad. 3. Find the <QueryTimeout> tag, if it exists, and 4. Set the value to 1440. This provides a 4 hour command timeout for any SQL query issued against the Intelligence data store. 5. If the <QueryTimeout> tag is missing, add the tag definition at the bottom of the file just before the line containing the closing tag (i.e. </EMIRuntimeConfiguration>): <QueryTimeout>14440</QueryTimeout> 7. Restart the Intelligence Server (i.e. the Wonderware Intelligence Service). https://wdnresource.wonderware.com/support/kbcd/html/1/t002631.htm 4/5
FIGURE 4: EMI DATA STORE COMMAND TIMEOUT SETTING Click the following icon to view this file in.pdf format: D. Beadle, C. Boutcher, S. Mariyala Tech Notes are published occasionally by Wonderware Technical Support. Publisher: Invensys Systems, Inc., 26561 Rancho Parkway South, Lake Forest, C A 92630. There is also technical information on our software products at Wonderware Technical Support. For technical support questions, send an e-mail to wwsupport@invensys.com. Back to top 2013 Invensys Systems, Inc. All rights reserved. No part of the material protected by this copyright may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying, recording, broadcasting, or by anyinformation storage and retrieval system, without permission in writing from Invensys Systems, Inc. Terms of Use. https://wdnresource.wonderware.com/support/kbcd/html/1/t002631.htm 5/5