•
You cannot install and use Application Server on a computer that has both Microsoft SQL Server 2000 and Microsoft SQL Server 2008 or later versions installed.•
The GR locks the SQL Server maximum memory usage to 65% of the computer's physical memory.•
TCP/IP must be enabled on the computer hosting a SQL Server database. The TCP/IP protocol setting can be verified from the SQL Server Network Configuration under SQL ServerConfiguration Manager. Do the following steps to enable TCP/IP.
To enable the TCP/IP protocol for the SQL Server database instance
1 Open the Start menu, point to All Programs, point to Microsoft
SQL Server, point to Configuration Tools, and then click SQL
Server Configuration Manager.
2 In the tree pane, click SQL Server Services.
3 In the results pane, verify that, under the State column, Running
appears next to the name of each service.
If Stopped appears, right-click the name of the service, and click
Start.
4 In the tree pane, click SQL Server Network Configuration to expand it, and then click Protocols for
MSSQLServer/<InstanceName>.
If you specified the default instance during installation, the instance name will be MSSQLSERVER.
5 In the results pane, verify that, under the Status column, Enabled
appears next to the name of the TCP/IP protocol.
If Disabled appears, right-click TCP/IP, and then click Enable.
6 In the tree pane, click SQL Native Client Configuration to expand it, and then click Client Protocols.
7 In the results pane, verify that, under the Status column, Enabled
appears next to the name of the TCP/IP protocol.
If Disabled appears, right-click TCP/IP, and then click Enable.
8 In the tree pane, click SQL Server Services.
9 In the results pane, right-click SQL Server
SQL Server Requirements33
SQL Server Rights Requirements
SQL Server 2008 and later versions do not automatically create the BUILTIN\Administrators role that was delivered in SQL Server 2005. Because of this change to SQL Server, the Application Server
installation process creates the necessary operating system user group (aaAdministrators), as well as the necessary SQL Server logon. This automated process provides the rights required to allow operations within the GR without the need for blanket BUILTIN\Administrator rights. The aaAdministrators group must be present and enabled. If you accidentally delete the aaAdministrators group from the Windows operating system, you can run either of the two following options to restore it:
•
Click Start, point to All Programs, point to Wonderware, and then click the Change Network Utility.•
Click Start, point to All Programs, point to Wonderware, and then click the aaConfig SQL Utility.If you accidentally delete the aaAdministrators group from the SQL Server security logons, you must run the aaConfig SQL Utility to restore it.
Working with SQL Server Versions
The installation workflow will vary, depending on whether or not SQL Server is already installed. The version of SQL Server that is installed can also make a difference in the workflow. If SQL Server is not already installed, the Wonderware System Platform installation program will install SQL Server Express. This is adequate for small configurations, but not for medium and large configurations. For these, install SQL Server before installing Wonderware. The following workflow scenarios are described:
•
SQL Server not found on node: small configuration•
SQL Server not found on node: medium and larger configurations•
Compatible version of SQL Server already installed•
New (untested) version of SQL Server already installed•
Incompatible version of SQL Server already installedSQL Server not found on node: small configuration
If you install the Application Server Galaxy Repository and SQL Server is not found on the computer, SQL Server 2012 SP1 Express is installed as part of the installation process. This version of SQL Server is suited for small configurations, up to 5,000 I/O per node, and is best for a single-node system.
34 Chapter 2 Application Server Requirements and Prerequisites
SQL Server not found on node: medium and larger configurations
For medium and larger systems, the following versions are supported:
•
Recommended version: SQL Server 2012 SP1, Standard or Enterprise edition•
SQL Server 2014, Standard or Enterprise edition•
SQL Server 2012 SP2, Standard or Enterprise edition•
SQL Server 2008 R2, Standard or Enterprise editionFor more information about the comparative capabilities of different SQL Server editions, see "Features Supported by the Different Versions of SQL Server 2012" at the following URL:
http://msdn.microsoft.com/en-us/library/cc645993(v=SQL.110).aspx.
Compatible version of SQL Server already installed
If a compatible version of SQL Server is already installed, Wonderware System Platform installation will continue without interruption (SQL Server 2012 Express will not be installed).
New version of SQL Server already installed
If a new version of SQL Server is already installed that has not yet been fully tested with Wonderware System Platform 2014 R2
products, a warning is displayed stating that the installed SQL version has not yet been tested. You can proceed with the installation, but we recommend that you contact Wonderware customer support before proceeding to check if any issues have been found.
Incompatible version of SQL Server already installed
If an older version of SQL Server is already installed that is not supported for use with Wonderware System Platform 2014 R2
products, installation will stop and a warning will be displayed stating the SQL Server version is not compatible. You must exit the
installation process and upgrade to a supported version of SQL Server before you can resume installation.
Issues with Legacy Common Components35
Issues with Legacy Common Components
Wonderware Application Server uses the latest version of the ArchestrA common components, which are installed to the following folder:
C:\Program Files\Common Files\ArchestrA
On a 64-bit operating system, the common components are installed to the following folder:
C:\Program Files (x86)\Common Files\ArchestrA
Legacy ArchestrA common components are installed to the following folder:
C:\Program Files\FactorySuite\Common
On a 64-bit operating system, legacy common components are installed to the following folder:
C:\Program Files (x86)\FactorySuite\Common
It is possible to install duplicate common components on a computer if you install an ArchestrA product that still uses the legacy common components after you install Application Server. Unexpected behavior can occur if duplicate common components are installed. The system components may not run properly, or may not run at all. Contact technical support for further assistance. You can also reference Tech Note 454, Manual Uninstall of Wonderware Products.
37