: Cannot Access LogViewer in the System Management Console

Purpose:

This document provides a solution for the situation when a customer has installed an FSArchestrA Product (InTouch 8.0/9.X) on a PC running Windows XP Professional with SP2 or Windows 2003 SP1 and when going to the Wonderware LogViewer in the System Management Console (SMC), and selecting “LOCAL”, they are prompted with a message that says cannot connect or access the LogViewer on that node. Typically, performing steps 1, 2 and 3 below will resolve this.

Procedure:

Modify the boot.ini file: Go to your MyComputer Icon on the Desktop; Right Mouse Click and select “Properties”; go to “Advanced”; go to the bottom and select “Settings” under Startup and Recovery; Select the “Edit” button next to “Startup systems manually…”; Physically change the “/noexecute=optin/” to /noexecute=Alwaysoff/. The explanation of this is on page 2 of this document.
Run the OS Configufation Utility: If you have installed InTouch 9.X, go to Start/Programs/Wonderware/Common and run the OS Configuration Utility. If it is not there, download the utility from the Wonderware website or get it emailed from Q-mation.

NOTE: Perform both Steps 1 & 2 before step 3.

Reboot the PC and go back into the SMC to check that you can now access the LogViewer. If steps 1, 2, and 3 do not work steps 4 and 5 provide further settings to check.
The path for the Wonderware Logger. Go to Start Settings\Control Panel\Admin Tools\Services\ArchestrA Logger : the path should be C:\Program Files\Common Files\ArchestrA. If this is set for C:\Program Files\FactorySuite\Common, then do a reinstall of the Common components for the FS2000 products and set the path to C:\Program Files\Common Files\ArchestrA instead of the default C:\Program Files\FactorySuite.
Local Security Policy: Go to Control Panel\Admin Tools\Local Security Policy\Local Policies\Security Options\Network Access: Sharing and Security model for local accounts - Should be set for "Classic" (Not Guest).

The /NoExecute switch relates to the new data execution prevention (DEP) technologies that Microsoft introduced in Windows 2003 SP1 and Windows XP SP2. DEP technologies help stop malicious code from accessing data pages. Two types of DEP technologies exist: software-enforced and hardware-enforced. The table shows the four parameters you can use with the /NoExecute switch.

Parameter	Description
OptIn	This setting is the default configuration. On systems with processors that can implement hardware-enforced data execution prevention (DEP), DEP is enabled by default for limited system binaries and programs that opt in. With this option, only Windows system binaries are covered by DEP by default.
OptOut	DEP is enabled by default for all processes. You can manually create a list of specific programs that don't have DEP applied by using the System Control Panel applet. You can use the Microsoft Windows Application Compatibility Toolkit to opt out one or more programs from DEP protection. System-compatibility fixes for DEP do take effect.
AlwaysOn	This setting provides full DEP coverage for the entire system. All processes always run with DEP applied. No exceptions are possible. System-compatibility fixes for DEP don't take effect. Programs that have been opted out by using the Windows Application Compatibility Toolkit still run with DEP applied.
AlwaysOff	This setting doesn't provide any DEP coverage for any part of the system, regardless of hardware DEP support. The processor doesn't run in Physical Address Extension (PAE) mode unless the /PAE option is present in the boot.ini file.

Please feel free to email support@qmation.com with questions.