MES Software 4.0 SP1

Wonderware MES Software version 4.0 SP1 Readme

Last revision: 02/8/2011

About This Readme

This document contains important information about Wonderware® MES software version 4.0 Service Pack 1 (SP1). Review this document for known and resolved issues in this version and changes, if any, to the MES software documentation included on this CD.

This Readme combines information from the previous MES 4.0 release and this Wonderware MES 4.0 SP1 release so all release note information is available for a full installation. The information order is based on when the Wonderware MES Software versions were released. Use the content links below to navigate between release note versions.

Important! Review the Installing Wonderware MES 4.0 SP1 section prior to upgrading your system.

Wonderware MES 4.0 SP1 Release Notes

• Release Summary - Wonderware MES 4.0 SP1
• System Requirements - Wonderware MES 4.0 SP1
• Product Compatibility - Wonderware MES 4.0 SP1
• Licensing - Wonderware MES 4.0 SP1
• Installing Wonderware MES 4.0 SP1
• Resolved Issues – MES 4.0 SP1
• Known Issues - MES 4.0 SP1
• Updated Wonderware MES 4.0 SP1 Documentation

Wonderware MES 4.0 Release Notes

• About This Release - Wonderware MES 4.0
• System Requirements - Wonderware MES 4.0
• Product Compatibility - Wonderware MES 4.0
• Licensing - Wonderware MES 4.0
• Upgrading from a Previous Version - Wonderware MES 4.0
• Known Issues – Wonderware MES - Wonderware MES 4.0
• Known Issues – Wonderware MES 4.0 Documentation
• Wonderware MES 4.0 Documentation

---

Release Summary - Wonderware MES 4.0 SP1

Wonderware MES 4.0 SP1 offers the following new features and enhancements:

• Wonderware MES 4.0 SP1 Qualification:
  • SQL Server 2008 R2 – MES 4.0 SP1 is tested to run on SQL server 2008 R2.
  • Operating Systems – MES 4.0 SP1 is tested to run on Windows 7 and Windows 2008 R2.
  • Microsoft Hyper-V Server 2008 R2 – MES 4.0 SP1 support of Hyper-V virtual machine environment on systems running Windows 2008 R2 64-bit operating system. For specific Microsoft Hyper-V Server 2008 R2 system requirements, go to http://www.microsoft.com/hyper-v-server/en/us/system-requirements.aspx
    • Not Supported
      • Live migration: Dynamically move virtual machines from one physical machine to another with no downtime.
      • Host Clustering
• Spanish Translation: All language strings are translated to Spanish.
• Physical Entities: Added Physical Entities operations and performance configuration options from Configurator to the MES Client.
• Parent Item Class: Parent Item Class configuration in the MES Client for grouping item classes.

< top of document >

---

System Requirements - Wonderware MES 4.0 SP1

This section describes the hardware, software, and operating system requirements to install the Wonderware MES version 4.0 SP1 software.

• Hardware Requirements
• Software Requirements
• Database Requirements
• Operating System Requirements
• Support for Non-English Versions of Operating Systems
• Wonderware MES Firewall Exceptions List
  

Hardware Requirements

Minimum Hardware Requirements

See your specific Microsoft operating system hardware requirements for details.

Operating Systems	Link to Microsoft Operating System Requirements
Windows Server 2003 R2 SP2	http://technet.microsoft.com/en-us/windowsserver/bb430827.aspx#EIC
Windows Server 2008 R2	http://www.microsoft.com/windowsserver2008/en/us/system-requirements.aspx
Windows Server 2008 SP2	http://technet.microsoft.com/en-us/library/dd540766(WS.10).aspx
Windows Vista Business SP1	http://windows.microsoft.com/en-us/windows-vista/products/system-requirements
Windows XP Professional SP3	http://www.microsoft.com/windowsxp/sysreqs/pro.mspx
Windows 7 SP1	http://windows.microsoft.com/en-us/windows7/products/system-requirements

Note: Depending on complexity and size of your database server, 30 GB or more of available disk space is recommended. Your database hard disk space should be enough to support the performance requirements for your particular deployment.

Software Requirements

This section lists the Wonderware and other third-party software requirements to install the Wonderware MES software:

• Microsoft .NET Framework 3.5 SP1. If this version of the .NET Framework is not installed on the computer, the Wonderware MES installation automatically installs the .NET Framework.
• The Entity Model Builder feature requires ArchestrA Integrated Development Environment (ArchestrA IDE).
• The Wonderware Information Server Integration feature requires WIS version 4.0 or later.

Database Requirements

Microsoft SQL Server

Version	Type		Service Pack Level	Notes
Microsoft SQL Server 2005	Standard or Enterprise Edition	32-bit only	SP2, SP3, SP4	See notes 1, 2 & 3
Microsoft SQL Server 2008	Standard or Enterprise Edition	32-bit & 64-bit	SP1, SP2	See notes 1, 2 & 3
Microsoft SQL Server 2008 R2	Standard or Enterprise Edition	32-bit & 64-bit	-	See notes 1, 2 & 3

Oracle Database

Version	Notes	Oracle Components (recommended versions)
		Client	Data Access Components	Data Provider for .NET	Provider for OLE DB	Objects for OLE	Services For Microsoft Transaction Server
Oracle Database 10g Release 2	See note 4	10.2.0.1	10.2.0.2.20	10.2.0.2.20	10.2.0.2.20	10.2.0.2.20	10.2.0.1.0
Oracle Database 11g (Standard or Enterprise Edition)	See note 4	11.1.0.6.0	11.1.0.6.0	11.1.0.6.0	11.1.0.6.0	11.1.0.6.0	11.1.0.6.0

Notes:

1. SQL Server should be configured for TCP/IP for local and remote connections. If you use SQL Server, make sure it is installed using a case-insensitive collation.
2. Microsoft Distributed Transaction Coordinator and IIS 6.0 or later.
3. MESDB using multiple languages requires AL32UTF8 Unicode character set installed on your server.
4. The MESDB Configuration Utility requires the Oracle Client installation to configure an Oracle database. SQLPlus must be available.

Operating System Requirements

The following table lists the operating systems that are supported and can be installed on computers that run Wonderware MES.

Operating Systems		Service Pack Level	Wonderware MES Features
			Client Components	Database	Middleware	Factory Connector	Manager	WIS
Windows Server 2003	32-bit only	SP2	Yes	Yes	Yes	Yes	Yes	Yes
Windows Server 2003 R2	32-bit only	SP2	Yes	Yes	Yes	Yes	Yes	Yes
Windows Server 2008	32-bit & 64-bit	SP2	Yes	Yes	Yes	Yes	Yes	Yes
Windows Server 2008 R2	64-bit	-	Yes	Yes	Yes	Yes	Yes	Yes
Windows Vista Business	32-bit & 64-bit	SP1	Yes	Yes 1	Yes 1	Yes 1	No	No
Windows XP Professional	32-bit & 64-bit	SP3	Yes	Yes 1	Yes 1	Yes 1	Yes	No
Windows 7	32-bit & 64-bit	-	Yes	Yes 1	Yes 1	Yes	Yes	Yes

¹ - Indicates that it is supported for sales and demo purposes only, not for production systems.

Note: If no Service Pack is indicated in the Service Pack level column, then the operating system is only supported without any Service Pack.

Support for Non-English Versions of Operating Systems

Wonderware MES 4.0 SP1 software runs on the following non-English operating systems:

• French
• German
• Japanese
• Simplified Chinese
• Russian
• Spanish

The corresponding language versions of MSSQL server are used, where applicable.

Wonderware MES Firewall Exceptions List

The following table lists the port name and corresponding port numbers that must be added in the Windows Firewall exceptions list for Wonderware MES.

Port Name	Port Number
Port 5413	5413
SQL TCP 1433	1433
SQL Server Browser 1434	1434
HTTP 80	80
TCP 8099	8099

The list of application names that must be added in the Windows Firewall exceptions list for Wonderware MES is as follows:

• DANSrv.exe
• OpcEnum.exe
• Microsoft SQLServer
• MSDTC
• dllhost.exe

< top of document >

---

Product Compatibility - Wonderware MES 4.0 SP1

The Wonderware MES version 4.0 SP1 is compatible and can co-exist with the following products:

• Wonderware Application Server 3.1 SP2 or later
• Wonderware InTouch HMI 10.1 SP2 or later
• WIS 4.0 or later

< top of document >

---

Licensing

Wonderware Component Licensing

None

Microsoft Office Fluent UI Licensing

The 2007 Microsoft Office Fluent User Interface is subject to protection under U.S. and international intellectual property laws and is used by Wonderware MES under license from Microsoft.

< top of document >

---

Installing Wonderware MES 4.0 SP1

• Updating MES .NET Controls in ArchestrA
• Updating the Script Library in ArchestrA
• Updating MES Application Objects (OCO, UCO)
• Updating ArchestrA Reports
• After upgrade is complete

Prior to installing MES 4.0 SP1 you should review these instructions and the Wonderware MES 4.0 Installation Guide. You must apply MES 4.0 SP1 on all servers and clients that are running:

• Standard Clients

• Middleware Servers
• Database Servers
• ArchestrA IDE Clients
• GR Node if you are using:
• Utilization Capability Object (UCO)
• Operations capability Object (OCO)
• MES .Net Controls
• MES Script Library

Important: Installation and upgrading MES Objects (UCO and OCO), MES .NET Controls, and the MES Script Library requires a separate import operation after completing the main installation. Refer to the following upgrade steps and the MES Installation Guide prior to installing MES 4.0 SP1.

Updating MES .NET Controls in ArchestrA

1. In the ArchestrA IDE Graphic Toolbox, locate any MES Controls and delete them. This will break your references, but they will be repaired when the new version of the controls are imported.
2. Click File > Import > Client Control and import the desired controls from C:\Program Files\Wonderware\MES\Controls\.
3. Close and re-open the ArchestrA IDE.

For additional information, see the MES .NET Controls Programmer’s Guide (Importing .NET Controls, Pgs. 26-30).

Updating the Script Library in ArchestrA

1. In ArchestrA IDE, click File > Import > Script Function Library.
2. Change the File Type selection to Script Library Files (*.aaSLIB).
3. Import the aaMES.aaSLIB script library from C:\Program Files\Wonderware\MES\Controls\ to replace the existing script library.
   Optional: If using the Fact.Common.dll to access Middleware via XML, import this DLL.
4. Click on File > Import > Client Control and import the file from C:\Program Files\Wonderware\MES\FactWebAccess\bin
5. In Application, right-click and validate all viewapp objects, object templates, instances, and symbols that use the aaFactMES script library.
   Note: Validate the derived templates that use the script library first.
   Tip: Right-click on the Galaxy name to validate all objects, or press Ctrl + Click to select specific objects.
6. Close and re-open the ArchestrA IDE.

For additional information, see the MES Installation Guide (Upgrading the Wonderware MES Script Library Pgs. 81-82).

Updating MES Application Objects (OCO, UCO)

1. Using the ArchestrA IDE, click File > Import > Objects.
2. From C:\Program Files\Wonderware\Factelligence\AppObjects\, import UtilizationCapability.aaPKG and OperationsCapability.aaPKG.
3. Accept the default import options.
4. Close and re-open ArchestrA IDE.

For additional information see:

• Operation Capability Object (OCO) User’s Guide, Importing the OCO (Pg. 13)
• Utilization Capability Object (UCO) User’s Guide, UCO Installation (Pg. 30).

Updating ArchestrA Reports

1. Click Start>Programs>Wonderware>Information Server>Deploy ArchestrA Reports.
2. Click aaReports Database > Deploy Reports on the left panel.
3. Click the Existing Shared Data Source option.
4. For Existing SDS Type, click aaMES.
5. Browse for the configuration file C:\Program Files\Wonderware\MES\Reporting Services\RptServicesConfig.xml.
6. Click the Deploy button.
7. Open Wonderware Information Server (WIS). You should see the reports displayed in the WIS System Panel.

After upgrade is complete

• Restart Factelligence Service (and Factory Connector if used).
• Redeploy platforms that host UCOs, OCOs, Factelligence .NET Controls, or Factelligence Script library.

< top of document >

---

Resolved Issues - Wonderware MES 4.0 SP1

This section describes all resolved issues in Wonderware MES version 4.0 SP1.

L00107615:	HF CR L00107046 (Hot Fix 2125) SR 103118835: Unable to record production to inventory with decimals (Oracle DB only)
L00108141:	SR 19911569: You cannot login with the same credentials after the MES client logs out, if the Seconds of inactivity before automatic logoff is set in General Parameters under the Security section.
L00108351:	HF CR L00100846 (Hot Fix 1883) SR 14432476:Incorrect entries in the tpm_stat table.
L00108352:	HF CR L00103272 (Hot Fix 1892) SR 35311491:Supervisor does not allow "READY" to change to "COMPLETED" for a job in the Queue window.
L00108353:	HF CR L00104228 (Hot Fix 1958) SR 40210466: Unable to properly access inventory from a previous Operation where Rejects were produced with Good Production when using Consume from WIP functionality. Additionally, inventory is not handled correctly when an entity is used twice in a process.
L00108354:	HF CR L00104341 (Hot Fix 1961) SR 40210536: When executing a standard work order (without process) import in Supply Chain Connector, the datetime values are not populated in the WO table with the values provided.
L00108355:	HF CR L00104372 (Hot Fix 1965) SR 19911447: After upgrading to 3.5, the Dataeditor will not start and cannot be used.
L00108356:	HF CR L00104660 (Hot Fix 1989) SR 19911452: It takes over 30 seconds to view the Entity in the Jobs tab and sometimes the entity configuration window cannot be seen below the screen.
L00108357:	HF CR L00104994 (Hot Fix 2011) SR 40210652: When upgrading to 3.5, an issue was discovered when trying to reduce production for the current job. When reducing production a negative value is written to the quantity produced.
L00108358:	HF CR L00105099(Hot Fix 2020): Shift times do not change as the Factelligence services get an error trying to insert a duplicate record.
L00108359:	HF CR L00105473 (Hot Fix 2036) SR 103118067: Unable to create a work order from process if the start and required quantities equal 1008.
L00108360:	HF CR L00106330(Hot Fix 2074) SR 40010021: The SUM (pct_to_apply) in the labor_usage table is greater than 1 for: ent_id, wo_id, oper_id, seq_no and labor_start_utc.
L00108361:	HF CR L00106245 (Hot Fix 2083) SR 40210746: OEE_KPI control does not have the Refresh Rate exposed for the control.
L00108362:	HF CR L00106695 (Hot Fix 2094) SR 40210743: When shipping an item from inventory with a WO, Oper, and Seq assigned, system ships that item_id, but with no WO, Oper and Seq details. Also, shipping any item never reduces that record, it always creates new records with negative quantities.
L00108363:	HF CR L00106869 (Hot Fix 2105) SR 40210780: The Operator Labor screen crashes when changing labor category for an Entity with two or more work orders running on it.
L00108364:	HF CR L00106862 (Hot Fix 2104) SR 19911532: Unable to Consume from a Step, when upgraded from 3.5 to 4.0. This is due to the Entity location not showing any of the lots that are to be used.
L00108365:	HF CR L00107046(Hot Fix 2125) SR 103118835: Unable to record production details with decimals to the inventory.
L00108366:	HF CR L00106892 (Hot Fix 2110) SR 37111633: When using serialized parts, produced items do not consume the items produced in the previous operations, if Consuming from WIP is set.
L00108367:	HF CR L00106019 (Hot Fix 2067) SR 19911506: When the filters are configured on the Equipment and Labor pages of Manager and a automatic refresh occurs the default filters are used in place of the configured filters.
L00108368:	HF CR L00105582 (Hot Fix 2166) SR 40210704: The Job_Exec table does not clear after the job is completed.
L00108369:	HF CR L00107856 (Hot Fix 2175) SR 103118960: In the TransferAndUpdateInv API method, the transferComments parameter does not get written to the Oracle database.
L00108371:	HF CR L00107211 (Hot Fix 2136) SR 40210780: When the labor category is changed, it does not get saved when the labor category window is closed and reopened. On trying to close it, an error appears, which is unrelated to the changes.
L00108372:	HF CR L00107147 (Hot Fix 2159) SR 40210779: When creating a Schedule, if a row exists, on deleting it an error appears and the row is not removed.
L00108373:	HF CR L00107567 (Hot Fix 2158) SR 38710132: Blank screen observed when performing order filter on Queue window.
L00108374:	HF CR L00107341 (Hot Fix 2144) SR 40210831: Entity attributes are getting deleted and showing an error when the value is changed.
L00108453:	HF CR L00105389 (Hot Fix 2095) SR 40210696: Job Notes is getting wrapped in the Operator screen.
L00108456:	HF CR L00106538 (Hot Fix 2084) SR 103118699: When a spec has more than two decimal places defined, the Spec Value, Max and Min in the global specifications it is being limited to two decimal places.
L00108502:	SR 19911583: In Configurator, the Entity attribute Value field should be the same size as the field in the database which is of 1700 characters.
L00108555:	HF CR L00108182 (Hot Fix 2189) SR 15011028:Factelligence Service clears out its own session after startup because it thinks it is an abandoned session.
L00108883:	HF CR L00100007 (Hot Fix 1760) SR 23518644 : Reports show incorrect data since the runtime column in the TPM_STAT table doesn?t get updated after the utilization data is updated in DataEditor for historical data.
L00108888:	HF CR L00108169 (Hot Fix 2188) SR 40210892: Client could not complete job as qty_prod in the job table was not equal to qty_required.
L00108889:	HF CR L00108523 (Hot Fix 2212) SR 103119181: The tpm_stat updates when the PENDING downtime utilization reason is changed by an operator to a run time rawreason.

< top of document >

---

Known Issues - Wonderware MES 4.0 SP1

This section describes all known issues in Wonderware MES version 4.0 SP1.

L00108855:

The Steps .NET Control does not display the configuration dialog box when the Vista theme is enabled in Windows Server 2008

< top of document >

---

Updated Wonderware MES 4.0 SP1 Documentation

The Wonderware MES documentation set includes the following:

• Wonderware MES Client Guide - Updated MES Client with Parent Item Class and Physical Entities configuration modules.
• Wonderware MES Stateless API Online Reference - Updated Stateless API to support new MES Client functionality for custom ArchestrA scripting within the ArchestrA Integrated Development Environment (IDE).
• ReadMe (This document) - Provides information about software and hardware requirements, known issues, licensing, and documentation.

The Wonderware MES version 4.0 SP1 product library consists of a set of Portable Document Files (PDF) located in the UserDocs folder of the Wonderware MES installation CD. You need to install Adobe Reader on your computer to view the Wonderware MES documentation. You can download the latest version of Adobe Reader from the Adobe Corporation Web site:

www.adobe.com/products/acrobat/readstep2.htm

After installing Adobe Reader, double-click a PDF file to view the book. You can also open a book with the Adobe Reader Open command from the File menu.

The Wonderware MES version 4.0 SP1 installation instructions are located in the root folder of the Wonderware MES version 4.0 SP1 installation CD as an online help file. You can view these instructions by clicking Help as you start the Wonderware MES version 4.0 SP1 installation procedure.

< top of document >

---

Wonderware MES version 4.0 Readme

Last revision: 04/16/2010

This document contains important information about Wonderware® MES version 4.0. Review this document for descriptions of new features, installation requirements, procedure to upgrade from a previous version, any known issues, and changes to the Wonderware MES version 4.0 documentation included on this CD.

About This Release - Wonderware MES 4.0

System Requirements - Wonderware MES 4.0

Product Compatibility - Wonderware MES 4.0

Licensing - Wonderware MES 4.0

Upgrading from a Previous Version - Wonderware MES 4.0

Known Issues – Wonderware MES - Wonderware MES 4.0

Known Issues – Wonderware MES Documentation - Wonderware MES 4.0

Wonderware MES Documentation - Wonderware MES 4.0

< top of document >

---

About This Release - Wonderware MES 4.0

Wonderware MES 4.0 offers the following new features and enhancements:

• Rename Factelligence to Wonderware MES: Factelligence is renamed to Wonderware MES in the Wonderware MES application as well as in the documentation.
• Operation Capability Object: Migrate PEM (Production Events Module) templates and instances to OCO (Operations Capability Object) template. The OCO extends the ArchestrA IDE equipment model to trigger production events and log associated production data in the Wonderware MES database (MESDB).
• Dynamic Routing: Dynamic Routing is a mini process used to produce processes from job route. Dynamic routes are used for rework or alternate processing. Dynamic Routing occurs when a specified item reason is entered for production within one of the jobs created from a process operation.
• Specification Capability Object (SCO): A new SCO is created to replace the Formula Manage Module (FMM) object and to enhance the specification creation and maintenance.
• Enhanced Calculations: Additional categories are added to enable different calculation methods for Utilization Reasons.
• Supply Chain Connector: Enhanced support for the import and export feature in the Supply Chain Connector.
• Multi Level Reason Groups: The number of utilization reason groups level is revised from 1 to 10.
• New Technology Upgrades: The Wonderware MES Client application is updated to support the latest technologies, such as User Account Control (UAC) and 64-bit OS support.
• OS Based Security: The OS based security feature allows you to add OS based users and user groups in the Wonderware MES Client application.
• Extended and Enhanced API: Provide an API that is extended and enhanced to enable full access to the new capabilities being added in the middleware. Provides access to the middleware for the Picasso extensions, the OCO and the SCO.
• WCF (Windows Communication Foundation) Support : The MES Client API and middleware is updated to support WCF.
• Enhance the API wrapper support for ArchestrA : The current API wrapper for ArchestrA scripting is enhanced to include the Stateless API and any changes to the Stateful API.
• Middleware Extensibility hooks: Added new extensibility hooks to the middleware to allow custom code (.NET assemblies or Stored Procedures) to be called before or after the OPS middleware code.
• Rewrite selected functionalities from Configurator and Supervisor as Picasso extensions: Selected functionalities from Configurator and Supervisor are re-written and made part of the new MES Client. Multiple tabs within Configurator or Supervisor are broken down into its own editor.

< top of document >

---

System Requirements - Wonderware MES 4.0

This section describes the hardware and software requirements to install Wonderware MES version 4.0.

• Hardware Requirements
• Operating System Requirements
• Software Requirements

Hardware Requirements

The following are the recommended hardware requirements to install Wonderware MES version 4.0.

Middleware or Database Server

• Computer with dual core processor with 2 gigahertz (GHz) or faster clock speed, or single core processor with 3 GHz or faster clock speed Dual core processor recommended for optimal performance.
• 2 gigabytes (GB) or more of RAM. (1 GB minimum supported; may limit performance of some features)

Manager Web Application Server

• Computer with 2 GHz or faster processor clock speed.
• 1 GB RAM or higher.

All Systems (Client Applications)

30 GB of available disk space

Super VGA (1024 x 768) or higher resolution video adapter and monitor

CD-ROM or DVD drive

Keyboard

Mouse or compatible pointing device

Note: The Microsoft Windows Vista operating system imposes hardware requirements that exceed the minimum requirements for Wonderware MES 3.5. If you intend to run selected components of the Wonderware MES version 4.0 with Windows Vista, see the following Microsoft Web site for hardware requirements: www.microsoft.com/windows/products/windowsvista/editions/systemrequirements.aspx.

Operating System Requirements

The following table lists the supported operating systems that can be installed on computers that run Wonderware MES.

Operating Systems	Wonderware MES Features
	Client Components	Database	Middleware	FactoryConnector	Manager	WIS
Windows Server 2008	Yes	Yes	Yes	Yes	Yes	Yes
Windows Server 2003 SP2 or Windows Server 2003 R2 SP2	Yes	Yes	Yes	Yes	Yes	Yes
Windows XP Professional SP2	Yes	Yes (1)	Yes (1)	Yes (1)	Yes	No
Windows Vista Business (See Vista Restrictions)	Yes	Yes (1)	Yes (1)	Yes (1)	No	No

Note: (1) indicates that it is supported for sales and demo purposes only, not for production systems.

Software Requirements

The following are the software requirements for Wonderware MES 4.0:

• Microsoft .NET Framework 3.5. If this version of the .NET Framework is not installed on the computer, the Wonderware MES installation automatically installs the .NET Framework.
• The MESDB requires SQL Server 2005 with SP2, or SQL Server 2008 with SP2 or Oracle Database 10g Release 2 or Oracle Database 11g Standard or Enterprise edition.

Note: SQL Server should be configured for TCP/IP for local and remote connections. If you use SQL Server, make sure it is installed using a case-insensitive collation.

• The MESDB also requires Microsoft Distributed Transaction Coordinator and IIS 6.0 or later.
• Requires InTouch 10.1 SP2 and Wonderware Application Server 3.1 SP2.
• The Entity Model Builder feature requires ArchestrA Integrated Development Environment (ArchestrA IDE) version 3.1 or later.
• The WIS Integration feature requires Wonderware Information Server (WIS) 3.0 or later.
• The MESDB Configuration Utility requires the Oracle Client installation to configure an Oracle database. SQLPlus must be available.
• The MESDB using multiple languages requires AL32UTF8 Unicode character set installed on your server.

< top of document >

---

Wonderware MES Firewall Exceptions List

The following table lists the port name and corresponding port numbers that must be added in the Windows Firewall exceptions list for Wonderware MES.

Port Name	Port Number
Port 5413	5413
SQL TCP 1433	1433
SQL Server Browser 1434	1434
HTTP 80	80
TCP 8099	8099

The following is a list of application names that must be added in the Windows Firewall exceptions list for Wonderware MES:

• DANSrv.exe
• OpcEnum.exe
• Microsoft SQLServer
• MSDTC
• dllhost.exe

< top of document >

---

Vista Restrictions

• You can run Wonderware 32-bit software only with a 32-bit version of Windows Vista. You cannot run a Wonderware 32-bit application with a 64-bit version of Windows Vista on 64-bit hardware.
• The Windows Vista User Account Control (UAC) must be disabled when running the utilities. For updating UAC see http://technet2.microsoft.com/WindowsVista/en/library/0d75f774-8514-4c9e-ac08-4c21f5c6c2d91033.mspx?mfr=true.

Note: When you disable the Windows Vista UAC, you must restart the computer before attempting to install the utilities or any other Wonderware product.

< top of document >

---

Product Compatibility - Wonderware MES 4.0

The Wonderware MES version 4.0 is compatible and can co-exist with the following products:

• Wonderware Application Server 3.1 SP2
• Wonderware InTouch HMI 10.1 SP2
• App Object Toolkit Beeblebrox 2.0 or later
• WIS 4.0 or later

< top of document >

---

Licensing - Wonderware MES 4.0

Wonderware Component Licensing

None

Microsoft Office Fluent UI Licensing

The 2007 Microsoft Office Fluent User Interface is subject to protection under U.S. and international intellectual property laws and is used by Factelligence under license from Microsoft.

< top of document >

---

Upgrading from a Previous Version - Wonderware MES 4.0

• Support upgrades of a Factelligence 3.4 (Sidus 1) or 3.5 (Sidus 2) system. To upgrade from any other previous version of Factelligence, the user will be required to first uninstall the old version of Factelligence (same as Factelligence 3.4).
• The MES Database Configuration utility delivered with this project supports migration of databases from version 3.1 and later. Migration from versions earlier than 3.1 requires manual steps to first update the database to version 3.1. Custom modifications to any version of the Factelligence database may not be supported by the utility and may prevent migration.

Note: You cannot upgrade from a version earlier than 3.4 to the current version of the software. You must first uninstall the previous version, and then install the new version.

For more information on upgrading, see the online help file (Install.CHM) available in the Wonderware MES installation root folder.

< top of document >

---

Known Issues - Wonderware MES 4.0

This section describes all known issues identified in Wonderware MES version 4.0.

L00072940: Cannot install Reporting Services reports for Oracle-based MES database.

In Factelligence version 3.4, Reporting Services reports for MES are not supported on an Oracle-based MES database. To work around this problem, do the following:

1. Install Oracle client components on the Wonderware Information Server (WIS) server node.
2. Verify that you can connect to the remote Oracle server node.
3. On the Start menu, point to Programs > Wonderware > Information Server > Deploy ArchestrA Reports. The ArchestrA Reports Database Configuration Utility dialog box appears.
4. Select Create New shared Data Source type and Default Data Source.
5. Enter information as follows:
   • In New SDS Type, type MES Oracle.
   • In the Data Source Name, type MESDB
   • In the Server field, type localhost.
   • In the Database field, type ReportServer.
6. Select Windows Authentication.
7. Browse for RptServicesConfigEmpty.xml on the Wonderware MES installation CD.
8. Click Deploy. The data source is created.
9. On the Start menu, point to Programs > Microsoft SQL Server > SQL Server Management Studio.
10. Delete the linked MES Oracle server.
11. Add a new MES Oracle server and link it to your Oracle MES database.
12. On the Start menu, point to Programs > Wonderware > Information Server > Deploy ArchestrA Reports. The ArchestrA Reports Database Configuration Utility dialog box appears.
13. Select Existing Shared Data Source.
14. In Existing SDS Type, type FactelligenceOracle.
15. Browse for RptServicesConfig.xml on the Wonderware Factelligence installation CD.
16. Click Deploy. The data source is created and deployed.



L00075441: Cannot log on to Configurator with error if the database name contain double-byte character.

Databases with double-byte characters are not supported.

L00075554: An error appears if you attempt to create a work order from process if the date format is specific format, such as yyyy/mm/dd.

If the date format is set to a specific format, such as "yyyy/mm/dd" and you attempt to create a work order from process in Supervisor, a run-time error appears. To prevent this error, use the date format mm/dd/yyyy.

L00075569: When consuming item substitutes, it is not decreasing the quantity of the main consumed item.

When consuming an ingredient/component for a particular BOM position, the amount consumed does not take into account the amount consumed for the item substitute.

The check for over-consumption based on the Max. Quantity is made separately for each ingredient. The consumption is not converted to common units and summed, and an overall check is not applied to that total.

L00079817: Logging data via Factory Connector requires a separate data log group for each job.

You should set up enough different datalog groups so each of your jobs that are running simultaneously can have its own group.  Each data log group then gets its own set of datalog value records and has a place to write the newly obtained values that won’t be affected by other jobs.

L00083613: String Raw Reason Codes cannot be sent through Factory Connector since FactoryConnector standard tag is analog.

Raw Reason Codes created in the Factelligence DB by the Entity Model Builder from the Utilization Capability Object are strings. If the user tries to update the Raw Reason Code on an entity using an OPC Client using the standard Util.SetRawReasCd tag, it will be analog. FactoryConnector will reject the write if the user tries to write a string value because FactoryConnector is always trying to convert it to an analog value.

L00086541: MES Manager Browser Window display issue.

If the MES Manager browser window is shrunk to a size smaller than the data grid of the displayed report, the data grid may appear "torn" after scrolling using the browser's scroll bar. Re-running the report will resolve the problem.

L00086458: Error message Fact.GetDS() error: {xxx} is not specific to database disconnect.

Fact.GetDS() error: {xxx} errors may be related to setup, configuration or connection problems. This error may be seen if the application cannot communicate with the middleware or database due to a network communication problem, incorrect installation, or configuration.

L00086839: Creating Oracle databases produces error when user is logged in with native Russian characters in the name.

Work-around is to run the Database Setup utility from the start menu when logged-in as a user with no Russian characters in the name.

L00092408: Large numbers of identical job execs can impact performance.

If you log on to the MES Operator having large number of job execs, the operator would get an exception error and the MES Operator will not start. To resolve this, log on to the MES Configurator and reduce the number of identifcal job execs to the minimum actually needed for each entity that can run jobs; then the MES Operator will start.

L00094583: No support for Middleware call to split a utilization record.

Wonderware MES does not support Middleware call to split a utilization record.

L00095917: Errors encountered in the log file while creating an Oracle database.

When you create an Oracle database of MESDB on a clean machine, errors are logged in the log file during the database creation for the items not being properly created.

L00097318: Not able to start or stop services from Service Monitor on Windows 2008 SP2 (32-bit) node with SQL Server 2008 SP1.

When you install the Wonderware MESDB on Windows 2008 SP2 (32-bit) node with SQL Server 2008 SP1, you may receive a warning message in system tray for service monitor.

L00100019: Errors encountered in the log file while running the Entity Model Builder.

If you move an UCO object from a child user-defined object to the parent user-defined object and that UCO is previously associated with OCO and then run the Entity Model Builder, you will encounter an error in the log file.

L00100291: No support for Middleware in a clustered environment.

Wonderware MES does not support the Middleware in a clustered environment.

L00100499: The EventDateTime attributes are not updated with time.

The EventDateTime attributes are not updated with the time the event occurs when it is set to auto generate.

L00100654: Obsolete columns available in the Session table.

tz_bias and std_time columns are available in the Session table. These columns are no longer used in Wonderware MES and are replaced by region_id.

L00100704: An error appears stating the connected galaxy does not have the OperatiosCapabilityObject package imported and the conection to the Galaxy is not allowed.

If you rename the base OperationsCapabilityObject template which has derived templates, and then connect to the galaxy using PEM Migration Utility, it will not allow you to connect to the Galaxy.

L00100719: A Start Next Job Command executes without error or warning if there are no available jobs to start.

When executing multiple jobs by using the Start Next Job command, when the final job is completed and no other jobs is available for execution, the system executes the Start Next Job Command without any error or warning.

L00100847: Wonderware MES 4.0 do not support Chinese(Simplified)-Microsoft Pinyin.

Chinese characters should not allowed to be input when Chinese(Simplified)-Microsoft Pinyin is set as input method.

L00100892: No support for new server side transaction feature with the OLEDB.

Work-around is to use Oracle provider if you need to use server side new transactions. In order to run with the Oracle provider you must install the Oracle Client.

L00101649: Issues while upgrading Factelligence version 3.1 database to Factelligence v 3.5 database

If you run the 3.5 upgrade scripts, it resets the Identical_job_execs field to zero in the ENT table and does not maintain prior value after upgrade.

L00101975: Wonderware MES 4.0 do not support entities at different sites with the same name.

To upgrade a system that has entities at different sites with the same name, the user will have to dump the database scripts to disk, and edit the upgrade script as follows:

• Oracle - Change the following code in oracle_upgrade_fiv35_to_fiv40_0001.sql

  CREATE UNIQUE INDEX IX_ENT ON ENT (ENT_NAME) TABLESPACE FI_INDEX_2 NOPARALLEL;

  to

  CREATE UNIQUE INDEX IX_ENT ON ENT (ENT_NAME, SITE) TABLESPACE FI_INDEX_2 NOPARALLEL;

  and change

  ALTER TABLE ENT ADD ( CONSTRAINT IX_ENT UNIQUE (ENT_NAME) USING INDEX TABLESPACE FI_INDEX_2);

  to

  ALTER TABLE ENT ADD ( CONSTRAINT IX_ENT UNIQUE (ENT_NAME,SITE) USING INDEX TABLESPACE FI_INDEX_2);

• SQL Server - Change the following code in upgrade_fiv35_to_fiv40_0001.sql

  CREATE NONCLUSTERED INDEX [IX_ent] ON [dbo].[ent] ([ent_name]ASC)

  WITH

  (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON, FILLFACTOR = 90) ON [FI_Index]

  to

  CREATE NONCLUSTERED INDEX [IX_ent] ON [dbo].[ent] ([ent_name] ASC,[site] ASC)

  WITH

  (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON, FILLFACTOR = 90) ON [FI_Index]

L00102027:Wonderware MES do not support localization of the error message when a middleware error occurs.

The error message is not localized when the middleware server is not reachable because the language string is instantiated every time and it always return a default value.

L00102472: Reporting System error encountered while viewing reports after upgrading Wonderware MES from Factelligence 3.5.

To resolve this, you must manually reset the Template report files path location to "C:\Program Files\Wonderware\Factelligence\Manager\? in the Manager group under General Parameter module of the MES Client.

L00103245: Ensure that backend functionality is still exposed via web services and HTTP handler.

Installing the MES FactWebAccess feature gives the user a web service interface to the Middleware and is available to users to provide backwards compatibility from pre-MES 4.0 versions. Users are recommended to use the new available client API for middleware access since the FactWebAccess feature does not support all the features that the Middleware Host provides in MES 4.0. The following configuration tasks may be needed for upgrading to MES 4.0 FactWebAccess functionality:

1. Modify IIS Manager configuration to use ASP.Net version 2.x by opening IIS Manager, navigate to Web Sites/Default Web Site/FactWebAccess. Right-click on the FactWebAccess Web folder and select Properties. Select the ASP.Net tab and change the ASP.Net version to point to 2.0.xxx. Apply changes and restart IIS.
2. If you need to use a SQL Server Login in your DatabaseConnectionEditor, you can configure the Web.Config to setup for the Integrated security needed. By default, this is not supported.

< top of document >

---

Known Issues–Wonderware MES 4.0 Documentation

Item	Location of Change	Existing Documentation	Change
1	None	None	None

 

< top of document >

---

Wonderware MES Documentation - Wonderware MES 4.0

The Wonderware MES documentation set includes the following:

• Wonderware MES Installation Guide - Provides information about installing Wonderware MES applications.
• Wonderware MES Client Guide - Provides information about customizing and maintaining the plant floor information.
• Operation Capability Object User's Guide - Provides information about installing, configuring, and using the Operations Capability Object.
• Utilization Capability Object User's Guide - Provides information about extending the ArchestrA Integrated Development Environment (IDE) equipment model.
• PEM Migration User's Guide - Provides information about migrating the existing PEM templates to the OCO template.
• Entity Model Builder User's Guide - Provides information about creating entities from the ArchestrA equipment model.
• Wonderware MES Configurator - Provides information about customizing and maintaining the Wonderware MES system.
• Wonderware MES Supervisor - Provides information about coordinating and oversee the daily activity of the plant floor.
• Wonderware MES Manager - Provides information about managing and viewing status tables and run reports on the data generated by the Wonderware MES system.
• Wonderware MES Operator - Provides information about executing processes at the plant floor.
• Wonderware MES Report Designer - Provides information about creating and configuring custom reports.
• Wonderware MES Reports in Wonderware Information Server - Provides information about viewing Wonderware MES reports with either the Reporting Services feature or the Table Weaver feature of Wonderware Information Server (WIS).
• Wonderware MES .NET Controls Programmers Guide - Provides information about integrating the Wonderware MES .NET controls into ArchestrA automation objects.
• Wonderware MES DataEditor - Provides information about inserting and modifying data in the Wonderware MES Database.
• Object Help - Provides information about run-time behavior, configuration, and run-time attributes of the UCO and the OCO objects.
• ReadMe (This document) - Provides information about software and hardware requirements, known issues, licensing, and documentation.

The Wonderware MES version 4.0 product library consists of a set of Portable Document Files (PDF) located in the UserDocs folder of the Wonderware MES installation CD. You need Adobe Reader installed on your computer to view the Wonderware MES documentation. You can download the latest version of Adobe Reader from the Adobe Corporation web site:

http://get.adobe.com/reader/

After installing Adobe Reader, double-click on a PDF file to view the book with Adobe Reader. You can also open a book with the Adobe Reader Open command from the File menu.

The Wonderware MES version 4.0 installation instructions are located in the root folder of the Wonderware MES version 4.0 installation CD as an online Help file. You can view these instructions by clicking Help as you start the Wonderware MES version 4.0 installation procedure.

< top of document >

---

© 2011 Invensys Systems, Inc. All Rights Reserved.