Tech Note 715 Resolving Issues with DAServer Diagnostic Node on the Windows 2008 Operating System 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#: 002489 Created: June 2010 Introduction This Tech Note outlines fixing an issue when using DAServer Diagnostics from a remote node that runs on the Windows 2008 Operating System. The Symptoms, Cause and Resolution are described in detail. Application Versions Machine One (computer name WIN8PC1) Windows 2008 Standard SP2 SQL Server 2008 Standard SP1 Application Server 3.1 SP2 (all components) SimpleTCP-Server DAServer Machine Two (computer name WIN8PC2) Windows 2008 Standard SP2 Application Server 3.1 SP2 (Bootstrap only) Symptoms The Diagnostics node of DAServer does not populate when viewed from the Remote Node. The DAServer SimpleTCP is activated on machine 1, WIN8PC1. In Figures 1-2 (below), the DAServer running on WIN8PC1 is accessed from another node called WIN8PC2. Notice that the Diagnostics node is not populated.
FiGuRE 1: Local ViEw from WIN8PC1
FiGuRE 2: REmotE ViEw from WIN8PC2 The Diagnostics node should be populated (Figure 3 below) on both the local node and from the remote node.
FiGuRE 3: EXpEctEd DiaGnostics NodE ElEmEnts Cause The Windows firewall setting on the DAServer machine prevents the Diagnostics node from being populated. Resolution Populate the Diagnostics node by setting up the DAServerExe in the Windows Firewall exception list. Configure the Firewall exceptions on the machine where DAServerExe is running. In this example it is the WIN8PC1 computer. This is done as follows: 1. Open Windows Control Panel and click Windows Firewall. 2. Click Allow a program through Windows Firewall.
FiGuRE 4: Allow a PRoGRam THRouGH Windows FiREwall 3. Click Continue on the User Account Control Pop up. Windows needs your permissions to continue. The Windows Firewall Settings dialog box appears (Figure 5 below). 4. Click the Exceptions tab.
FiGuRE 5: Windows FiREwall EXcEptions List 5. Click Add program. The Add a Program dialog box appears (Figure 6 below).
FiGuRE 6: Add a PRoGRam 6. Click Browse to locate and select the path for the DAServerExe. DAServerExe refers to the name of the executable (exe) file that is created for custom DAServer. In this example, a DAServer called SimpleTCP has been developed. The name of executable in this example is SimpleTCP.exe. 7. Verify that the DAServerExe file (SimpleTCP.exe) is checked under the Exceptions tab (Figure 7 below).
FiGuRE 7: DASERvEREXE Windows FiREwall EXcEption 8. Click OK to close the dialog box and save the changes. 9. Close the Windows Firewall Settings panel. 10. Now open the SMC and expand the DAServer Diagnostics node from the Remote machine:
FiGuRE 8: DiaGnostics NodE from REmotE MacHinE
FiGuRE 9: DiaGnostics NodE from Local MacHinE P. Kulkarni Tech Notes are published occasionally by Wonderware Technical Support. Publisher: Invensys Systems, Inc., 26561 Rancho Parkway South, Lake Forest, CA 92630. There is also technical information on our software products at Wonderware Technical Support. For technical support questions, send an e-mail to support@wonderware.com. Back to top 2010 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.