Epicor 9.05 Installation Guide: New Install 9.05.702 - SQL

Epicor 9.
05 Installation Guide
New Install 9.05.702 - SQL
Disclaimer
This document is for informational purposes only and is subject to change without notice. This document and its
contents, including the viewpoints, dates and functional content expressed herein are believed to be accurate as of its
date of publication. However, Epicor Software Corporation makes no guarantee, representations or warranties with
regard to the enclosed information and specifically disclaims any applicable implied warranties, such as fitness for a
particular purpose, merchantability, satisfactory quality or reasonable skill and care. As each user of Epicor software is
likely to be unique in their requirements in the use of such software and their business processes, users of this document
are always advised to discuss the content of this document with their Epicor account manager. All information contained
herein is subject to change without notice and changes to this document since printing and other important information
about the software product are made or published in release notes, and you are urged to obtain the current release
notes for the software product. We welcome user comments and reserve the right to revise this publication and/or
make improvements or changes to the products or programs described in this publication at any time, without notice.
The usage of any Epicor software shall be pursuant to an Epicor end user license agreement and the performance of
any consulting services by Epicor personnel shall be pursuant to Epicor's standard services terms and conditions. Usage
of the solution(s) described in this document with other Epicor software or third party products may require the purchase
of licenses for such other products. Where any software is expressed to be compliant with local laws or requirements
in this document, such compliance is not a warranty and is based solely on Epicor's current understanding of such laws
and requirements. All laws and requirements are subject to varying interpretations as well as to change and accordingly
Epicor cannot guarantee that the software will be compliant and up to date with such changes. All statements of
platform and product compatibility in this document shall be considered individually in relation to the products referred
to in the relevant statement, i.e., where any Epicor software is stated to be compatible with one product and also
stated to be compatible with another product, it should not be interpreted that such Epicor software is compatible
with both of the products running at the same time on the same platform or environment. Additionally platform or
product compatibility may require the application of Epicor or third-party updates, patches and/or service packs and
Epicor has no responsibility for compatibility issues which may be caused by updates, patches and/or service packs
released by third parties after the date of publication of this document. Epicor® is a registered trademark and/or
trademark of Epicor Software Corporation in the United States, certain other countries and/or the EU. All other
trademarks mentioned are the property of their respective owners. Copyright © Epicor Software Corporation 2013.
All rights reserved. No part of this publication may be reproduced in any form without the prior written consent of
Epicor Software Corporation.
New Install 9.05.702 - SQL

Revision: July 02, 2013 11:35 a.m.
Total pages: 65
install_New_sql.ditaval
Epicor 9.05 Installation Guide Contents
Contents
Part I: Getting Started......................................................................................7
Chapter 1: Verify Prerequisites...................................................................7

1.1 Verify Access to EPICweb....................................................................................................................7
1.2 Verify Epicor 9.05 Install Guide Version...............................................................................................7
1.3 Review Epicor 9.05 Functionality.........................................................................................................8
1.4 Review Software Requirements...........................................................................................................8
1.5 Verify SQL Server Installation...............................................................................................................9
1.6 Review Hardware Requirements........................................................................................................10
1.6.1 Review Hardware Sizing Guide...............................................................................................10
1.6.2 Review Hardware Scenarios....................................................................................................11
SQL Config #1: Two Servers.....................................................................................................11
SQL Config #2: Three Servers...................................................................................................12
SQL Config #3: Four or More Servers........................................................................................13
1.7 Verify Epicor AEP Requirements........................................................................................................13
1.8 Verify Windows Server 2008 Compatibility........................................................................................14
1.9 Verify Temporary Files Do Not Exist...................................................................................................14
Chapter 2: Perform Pre-Installation Steps...............................................15

2.1 Configure Application Server Role.....................................................................................................15
2.2 Disable Error Reporting.....................................................................................................................16
2.3 Set Up SQL Collation for Epicor 9.05.................................................................................................16
2.4 Determine Web Service Type: WSE or WCF.......................................................................................17
Part II: Installation..........................................................................................18
Chapter 3: Install Progress OpenEdge.....................................................18

3.1 Install Progress OpenEdge 10.2A......................................................................................................18
Chapter 4: Install or Upgrade the Epicor 9.05 Application.....................22

4.1 Download Latest Release Files...........................................................................................................22
4.2 Install Epicor 9.05 Server...................................................................................................................23
4.3 Install Epicor 9.05 Patch on the Server..............................................................................................27
4.4 Install Epicor 9.05 Help Content Pack................................................................................................28
Part III: Post-Installation.................................................................................29
New Install 9.05.702 - SQL 3

Contents Epicor 9.05 Installation Guide
Chapter 5: Configure Application Server.................................................29

5.1 Establish Security for Progress AppServer..........................................................................................29
5.1.1 Establish an Administrative Account........................................................................................29
5.1.2 Establish Local Security Policy..................................................................................................29
5.1.3 Establish the AdminService Setting..........................................................................................30
5.1.4 Configure Security for Multiple Servers...................................................................................30
5.2 Setup Full-Text Searching on MS SQL Server......................................................................................31
5.2.1 Review the Process - Building Full-Text Catalogs......................................................................31
5.2.2 Starting the MS SQL Search Service.........................................................................................31
5.2.3 Defining the Catalogs.............................................................................................................32
5.2.4 Initial Population of Catalogs..................................................................................................32
5.2.5 Setting Up the Catalogs to Update Incrementally....................................................................33
5.2.6 Testing Server Impact for each Job..........................................................................................33
5.3 Setup Progress OpenEdge Manage Tool............................................................................................34
5.4 Update Parameter File for Multi-Server Configuration.......................................................................35
5.5 Verify Parameter File Settings............................................................................................................36
5.6 Configure the Euro Currency Symbol................................................................................................38
Chapter 6: Prepare Your Database...........................................................39

6.1 Initialize or Convert Your Database...................................................................................................39
6.1.1 Before You Begin...................................................................................................................39
6.2 Add Epicor and Application Server Connections................................................................................39
6.3 Import License Codes........................................................................................................................40
6.4 Add Company..................................................................................................................................41
6.5 Stop Main AppServer........................................................................................................................42
6.6 Run Conversions Using Epicor Admin Tools.......................................................................................42
6.7 Stop and Start AppServers................................................................................................................43
6.8 Verify Avalara Path Value..................................................................................................................43
Chapter 7: Install Epicor 9.05 Client on a Workstation...........................44

7.1 Install Microsoft Tools .NET 3.5 and WSE or WCF Runtime (Client)....................................................44
7.2 Install Epicor 9.05 Client Software....................................................................................................44
7.3 Install Crystal Reports Runtime..........................................................................................................45
Chapter 8: Log in the First Time...............................................................47

8.1 Import Posting (Booking) Rules.........................................................................................................47
8.2 Verify System Agent for Printing.......................................................................................................48
8.3 Test System and Repeat Installation..................................................................................................48
Chapter 9: Restore Demonstration Database..........................................49

9.1 Download Demonstration Database File............................................................................................49
4 New Install 9.05.702 - SQL

Epicor 9.05 Installation Guide Contents
9.2 Verify Prerequisites...........................................................................................................................49

9.3 Restore the Demonstration Database................................................................................................49
9.4 Start Main AppServer........................................................................................................................51
9.5 Import License Codes and Enable Modules.......................................................................................51
9.6 Run Manual Conversions..................................................................................................................52
9.7 Set Up System Agent for Printing (Demo Database)...........................................................................52
9.8 Start Remaining Appservers..............................................................................................................53
9.9 Test Demonstration Database Update...............................................................................................53
Chapter 10: Configure Windows Admin Workstation............................54

10.1 Verify Prerequisites for Windows Admin Workstation......................................................................54
10.2 Install ODBC Driver (SQL Server Native Client 10)............................................................................54
10.3 Install Progress OpenEdge...............................................................................................................55
10.4 Install Epicor 9.05 Client.................................................................................................................55
Chapter 11: Troubleshooting....................................................................56

11.1 Share the Epicor Folders..................................................................................................................56
11.2 Verify Specific Folders are Not Read-Only........................................................................................56
11.3 Review Configuration File Settings..................................................................................................57
11.4 Verify Time Synchronization on Client and Server............................................................................57
11.5 Known Issue with Turkish Format Culture Display...........................................................................57
11.6 Configure Environments for Test and Pilot......................................................................................58
11.7 Error Accessing Menu Maintenance................................................................................................59
11.8 Progress Client Has Stopped Working.............................................................................................59
11.9 Change or Uninstall Epicor 9.05 Application...................................................................................59
11.9.1 Add or Remove Programs and Features................................................................................59
11.9.2 Repair or Reinstall Epicor 9.05 Application............................................................................60
11.9.3 Uninstall Epicor 9.05 Application..........................................................................................60
11.9.4 Uninstall Epicor 9.05 Client...................................................................................................62
Part IV: Supplemental Installations...............................................................63

Contents Epicor 9.05 Installation Guide

Epicor 9.05 Installation Guide Getting Started
Part I: Getting Started

Welcome to the Epicor 9.05 Installation Guide - Version 9.05.702. This comprehensive guide explains how to
install the Epicor 9.05 application system for new customers.
This part of the guide explains how to verify the prerequisites and perform pre-installation steps prior to installing
your Epicor 9.05 installation. You can use the following process flow to track your path through the installation.
Chapter 1: Verify Prerequisites
This part of the guide explains how to verify the prerequisites prior to installing or upgrading your Epicor 9.05 installation.
1.1 Verify Access to EPICweb
Use the following instructions to verify you have appropriate permissions to access the EPICweb site.
1. Verify you have Internet access at your workstation.
2. Verify you have a valid User ID and Password for Epicor's Customer Portal (EPICweb). To create an account
go to: http://support.epicor.com
1.2 Verify Epicor 9.05 Install Guide Version

Use these steps to verify that you are using the correct version of the Epicor 9.05 installation guide. Be sure to
always use the installation guide with the latest Revision date.
1. Log on to EPICweb and go to the Customer Portal Page. Navigate to Support > Epicor 9 > Downloads.
Note You can use this link: https://epicweb.epicor.com/Support/epicor9/Downloads
2. Navigate to Epicor 9 > Version 9.05.700.

Getting Started Epicor 9.05 Installation Guide
3. In the Available Downloads list, locate and download the installation guide for your platform, either SQL,
Progress, or Linux/UNIX. Note that specific guides are available for different installation types, including:
New installation, Upgrading from Epicor 9.04, or Service Pack upgrade from 9.05.60x.
Note If you are upgrading from Vantage 8.03.40x to 9.05.70x, you must download and follow the
Epicor Data Upgrade Utility Guide.
4. Open the file. On the Disclaimer page, verify that the Revision Date is the same as the revision date on the
installation guide you are using.
1.3 Review Epicor 9.05 Functionality
It is recommended that you become familiar with the features available in the Epicor 9.05 release prior to installing
the Epicor 9.05 application.
1. Review the Epicor 9.05 Feature Summary to learn about the features in the Epicor 9.05 release. To access
the 9.05 Feature Summary, log onto the EPICWeb Documentation site and click the Feature Summaries link.
Note that you can also view the Feature Summary using the online help system.
2. If desired, contact the Services group to learn more about upgrading or migration to Epicor 9.05.
Note To request assistance from Services, fill out the Services Request Form available on the EPICWeb
Services site. You can use this link: https://epicweb.epicor.com/services/Pages/default.aspx.
1.4 Review Software Requirements
Software requirements have been updated for this release. Use the following information to update your system.
• Windows Server 2008 or Windows Server 2008 R2 must be installed on the server.
• Epicor is verified to work with Microsoft Windows operating systems, including Windows XP, Windows 7 and
Windows 8. Depending on the operating system running on your workstation, the steps in this guide might
be slightly different. If you use a Windows XP workstation, you must have Windows XP Service Pack 2 installed.

• You must have the Microsoft Internet Information Services (IIS) installed in order to use several features
of the Epicor application, including Embedded Education Courses, and Epicor Web Access. If you do not have
IIS installed, refer to your operating system documentation for instructions.
• You must have the ASP.NET module of your Windows Internet Information Services (IIS) installation enabled
in order to use several features of the Epicor application, including Epicor Web Access, Epicor Mobile Access,
or Epicor Embedded Education.
• Verify you have Microsoft .NET 3.5 installed on your server. Use the instructions on the Microsoft Download
Center site to download and install the application. Note that the .NET 3.5 installation includes the .NET
Service Pack when you download .NET 3.5 from the Microsoft Download Center website.
• If you are hosting an Epicor Web Access site on the Epicor application server, the IIS Server name must not
include the underscore character. If the IIS Server name has an underscore, the user won't be able to log in.
• To use a SQL or SQL Unicode database with the Epicor 9.05 application, you must have a supported version
of SQL Server installed on your database server. For more information, see the "Verify SQL Server Installation"
section of this guide.
• To run the Epicor Administration Console, you must have the latest Microsoft Management Console (MMC)
3.0 or later installed. See the MMC 3.0 download site for download information.
• If you have Customer Connect, the service pack for that product must be installed on your system.
• If you have SQL installed and you are using that SQL database for your transactional database, and you plan
to use Epicor Enterprise Search, you do not need to install Epicor Replication because you can use your SQL
database. See more detail in the Supplemental Installation section for Replication.
1.5 Verify SQL Server Installation
Verify that a supported version of Microsoft SQL Server is installed on your database server and Windows Admin
Workstation. If necessary, use these steps to install Microsoft SQL Server. Note that SQL Server 2008 Express or
SQL Server 2008 Express R2 can be installed on the Windows Admin Workstation.
Note It is recommended that you review the SQL Books Online information in order to become familiar
with the SQL Server administration functionality. The documentation is typically installed with the SQL
Server application. To access it, navigate to Start > All Programs > Microsoft SQL Server >
Documentation and Tutorials > SQL Server Books Online
1. On your database server, verify that one of the supported SQL Server versions is installed:
• SQL Server 2008
• SQL Server 2008 R2
• SQL Server 2012
If necessary, install SQL Server on your database server using the instructions that came with your SQL
installation. Be sure to install any Microsoft service pack and patch updates related to your SQL version.
2. On your Windows Admin Workstation, verify that one of the supported SQL Server versions is installed:
• SQL Server 2008
• SQL Server 2008 R2
• SQL Server 2012
• SQL Server 2008 Express (if your database is hosted on SQL Server 2008)
• SQL Server 2008 Express R2 (if your database is hosted on SQL Server 2008 R2)

If necessary, install SQL Server on your Windows Admin Workstation using the instructions that came with
your SQL installation. Be sure to install any Microsoft service pack and patch updates related to your SQL
version.
Important For SQL Server 2012 installations, you must download and install SQL Server Native Client
10. For more information, see the "Install ODBC Driver (SQL Server Native Client 10)" instructions in
the Post-Installation section of this guide.
3. If your SQL Server is hosted on a different machine than the Epicor 9.05 Application Server, verify that
network connectivity exists between the servers. To do this, complete the following steps on the two
machines:
a. For the Application Server, do the following:

• Verify SQL Express 2008 R2 (minimum) in installed.
• Add a domain account with Administrator permissions.
• Log into the Application Server using the domain account with Administrator permissions.
• Run AdminService for OpenEdge 10.2A using the domain account. This is required in order for the
AppServers to start.
b. For the SQL Server, do the following:

• Add the domain account login (with Administrator permissions) to the Administrators group.
• Verify the SQL Server service properties specifies "Log On As" that specific domain account.
• In SQL Server Management Studio, create the domain account as a SQL login account with sysadmin
rights.
Note During the installation of Epicor 9.05, when prompted to select the Authentication Mode,
you must select Windows Authentication.
1.6 Review Hardware Requirements
Use this section to review hardware requirements for Epicor 9.05. You can review the documents provided for
hardware sizing and configuration, and you can also review example hardware configuration scenarios based on
your platform and required applications. It is highly recommended that you understand your hardware requirements
prior to installing your Epicor products.
1.6.1 Review Hardware Sizing Guide
Use these steps to download and review the Epicor Hardware Sizing and Configuration Guide. Note that Hardware
requirements may change based on the specific release. It is recommended that you have an understanding of
the hardware requirements prior to installing.
Note You can use this link:https://epicweb.epicor.com/Support/epicor9/Downloads
2. Navigate to Utilities > Hardware Sizing Guide.

3. Download and extract the Epicor90570x_HardwareGuide.zip file. Note that this zip contains two files:
Hardware Guide (PDF) and Sizing Spreadsheet (XLS)
4. Open the Epicor90570x_HardwareGuide.pdf file. Review the entire guide, including these sections:
• Introduction (how to use the guide)
• Application Load Profile (usage and patterns)
• Server Hardware Sizing (Standard, Medium, Large)
• Epicor 9.05 Scenarios (based on user count)
• Other Hardware Requirements
• Appendix (SAN, CPU, RAM, RAID, UPS)
5. Open the Epicor9SizingSpreadsheet.9057xx.Template.xls file. Review the entire template, including

these tabs: Summary, Software Purchased, and Workload. Note that you may already have a completed
version of this sizing spreadsheet.
6. Use the two documents to assist in understanding your hardware requirements.
1.6.2 Review Hardware Scenarios
Use this section to review examples of hardware scenarios, including basic multi-server configurations. The
examples list the applications that might be installed on each server. Review the example scenarios to determine
which type of configuration is appropriate for your environment. Note that these are basic examples and your
desired configuration may be more complex.
SQL Config #1: Two Servers
Review the Two Servers configuration example to determine if it is appropriate for your environment.

SQL Config #2: Three Servers
Review the Three Servers configuration example to determine if it is appropriate for your environment.

SQL Config #3: Four or More Servers
Review the Four or More Servers configuration example to determine if it is appropriate for your environment.
1.7 Verify Epicor AEP Requirements
If you use Epicor AEP (Advanced Estimating and Pricing), use these steps to verify the installation requirements.
1. Verify that the same version of the Epicor 9 and the Epicor AEP application is available. Your Epicor AEP
application must be at the same version as the Epicor 9 application in order to be functional. For example,
if you want to install Epicor AEP 9.05.702A, then your Epicor 9 application version must be 9.05.702A.
Important If a matching version of the Epicor AEP application is not available, do not proceed with
upgrading your Epicor 9 application.
2. If you are performing an upgrade, verify that your Epicor 9 and Epicor AEP applications are at version 9.05.607
or later. To upgrade to Epicor AEP 9.05.70x, you must have at least Epicor AEP 9.05.607 installed.
Note Be sure to follow the instructions in the Pre-Installation section of the AEP Installation Guide.

3. If you use Progress and want to upgrade from 9.05.607 to 9.05.70x, several manual steps are required prior
to upgrading to the Epicor 9.05.70x application. These manual steps must be completed by Epicor Technical
Support. Contact Epicor Technical Support to perform these steps.
1.8 Verify Windows Server 2008 Compatibility
If you have Windows Server 2008 or Windows Server 2008 R2 installed on your server, use the following steps
to verify the compatibility with the Epicor Application.
1. If you use Windows Server 2008 or Windows Server 2008 R2, note that to open an executable file, you do
not double-click the file. Instead, you right-click and select the Run as Administrator option.
2. If you use Windows Server 2008 or Windows Server 2008 R2, you also need to install Application Server
and IIS with V6 compatibility.
3. With Windows Server 2008 and Windows Server 2008 R2, a firewall is installed. The firewall must be disabled
in order for connectivity from other machines to allow for administering of the Epicor 9.05 Appservers.
Based on your company practices, you can enable your firewall after the installation process is complete.
1.9 Verify Temporary Files Do Not Exist

Prior to installing the upgrade, use the following steps to clear out any existing temporary folders and files related
to install aware processing. These temporary folders and files may exist due to prior upgrades that were not fully
completed and they may cause your current upgrade to not install properly.
1. Go to your system Temp folder. The location of the Temp folder differs based on your operating system.
To find the location of this folder, you can do one of the following:
• Select Start > Run. In the command window, type: %temp%. Click OK. The Temp folder location
opens in a browser. For example, the browser could open to C:\Users\[UserId]\AppData\Local\Temp.
• Select Start and right-click on Computer. Select Properties. Click the Advanced System Settings link
or the Advanced tab. Click Environmental Variables. In the User variables section, record the value
for the Temp variable.
2. In the Temp folder and subfolders, delete the following:

• folders that start with MIA*
• files that end with *.TMP

Chapter 2: Perform Pre-Installation Steps
This part of the guide lists the steps to perform before installing or upgrading Epicor 9.05.
2.1 Configure Application Server Role
Use these steps to configure the Application Server role. Note that if the server roles already exist, you can still
review the list of role features to verify that your roles are configured properly.
1. On the server, open Server Manager. Select the Roles node.
2. In the Roles Summary section, verify if the Application Server role is listed.
• If this role is not listed, use the following steps to add the roles services.
• If the role is listed, click the Add Role Services link on the right side. Then use the step below regarding
the Application Server dialog to verify that the required Application Server role services have been installed.
3. Click Add Roles and click Next.
4. On the Select Server Roles dialog, do the following:
a. Select Application Server. If the Add Roles Wizard opens, click the Add Required Features button
to add the listed features. For example, features may include the .NET Framework 3.5.1 and Windows
Process Activation Service.
b. Click Next.
5. On the Introduction to Application Server dialog, review the noted comments and click Next. On the Select
Role Services dialog, notice that .NET Framework 3.5.1 is already selected for you. Select these additional
options and click Next:
• COM+ Network Access
• TCP Port Sharing
• Windows Process Activation Service Support
• Message Queuing Activation
• TCP Activation
• Named Pipes Activation
• Distributed Transactions
• Incoming Remote Transactions
• Outgoing Remote Transactions
6. Click Next. Then, click Install. The Application Server Role and features are installed.
7. Click Close.

2.2 Disable Error Reporting
Use the following steps to disable error reporting on your workstation. This step is recommended in order to
save processing time by not automatically reporting software issues during installations. Based on your company
practices, you can enable error reporting after the installation process is complete. Note that the steps differ
based on your operating system.
Using Windows Server 2008 R2
1. Navigate to Start > Control Panel > System and Security.
2. Select Action Center. Select the Change Action Center Settings link.
3. Open Maintenance and then select the Problem reporting settings link.
4. Select Never check for solutions button. Click OK.
Using Windows 7
1. Verify that you have administrator privileges.
2. Open the Local Group Policy Editor. To do this, open Start > Search. Type gpedit.msc and press Enter.
3. Navigate to Computer Configuration > Administrative Templates > System > Internet Communication
Management > Internet Communication Settings.
4. From the main window, select Turn Off Windows Error Reporting.
5. On the dialog, select the Enabled check box. Click OK. The change takes place immediately.
2.3 Set Up SQL Collation for Epicor 9.05
A typical SQL installation sets the default database collation to be dependent on the Regional Settings of the SQL
Server. This collation must match the collation of the individual Manufacturing databases in order for queries to
operate properly. For example, if the collation does not match, searches on Parts Entry or Sales Order Entry will
not work. This collation is not related to full text indexing; other full text indexed table searches will run fine. This
is an issue only when the SQL server is not localized for English (US).
Use these steps to verify your SQL database collation.
1. Review the list of collation settings that are dependent on Regional Settings. To do this, click on the following
SQL 2008 link: http://msdn.microsoft.com/en-us/library/ms143508.aspx
The correct collation setting for Manufacturing databases is SQL_Latin1_General_CP1_CI_AS, which is
the default for English (US) localized systems.
2. If the collation does not match, you must reinstall SQL Server and select custom to allow a collation setting
to be selected. Simply changing the databases to match a different system collation setting does not resolve
the issue.
The SQL installer does not show the codes, it only shows descriptions. The required selection is under
Collation Settings > SQL Collations. An example is Dictionary Order, Case-Insensitive, 1252 codepage.
This produces the required matching SQL_Latin1_General_CP1_CI_AS collation.

3. Change the Compatability Level to SQL 2008 (100) for all databases that will run in the Epicor 9.05 application.
The Epicor 9.05 application does not support SQL 2005.
2.4 Determine Web Service Type: WSE or WCF
Use this information to determine which type of Web Service you will install. Epicor 9.05 is compatible with two
types of Web Services: WCF (Windows Communication Foundation) and WSE (Web Service Enhancements).
1. Determine which type of Web Service you want to install.

• If you are a new customer, you can choose to start using WSE or WCF. It is recommended you use the
WCF version. Note that WCF is included into the .NET Framework 3.5 SP1, which is a part of Epicor 9.05
Installation.
For more information on WCF, click the following link to read the article What is WCF: http://msdn.mi
crosoft.com/en-us/library/ms731082(VS.85).aspx
• If you are an existing customer using WSE, and you have already invested resources and time in Epicor
Service Connect workflows or custom coding that use WSE, you can choose to continue using WSE and
then start to transition over to the WCF version. Note that based on Microsoft development, WSE will
be replaced with WCF.
2. If you want to install Web Services Enhancements (WSE) 3.0 Runtime, use the following steps:
a. In an Internet browser, search for "Web Services Enhancements WSE 3.0 Runtime".
b. From a trusted site, download the latest version of Microsoft WSE 3.0 Runtime to your server and
Windows Admin workstation.
c. Use the instructions provided on the website to guide you through the installation process.

Installation Epicor 9.05 Installation Guide
Part II: Installation

This part of the guide explains how to install or upgrade the Epicor 9.05 application.
Chapter 3: Install Progress OpenEdge
Use this section to verify and install Progress OpenEdge 10.2A and the required OpenEdge Service Packs and OpenEdge
Service Pack Hot Fixes on your server.
3.1 Install Progress OpenEdge 10.2A
Use these instructions to install Progress OpenEdge 10.2A, SP 03 and SP Hot Fix 29 on your server and/or Windows
Admin workstation. You will need to reboot the server after completing this section. Note that if you already
have OpenEdge 10.2A, SP 03 and SP Hot Fix 29 installed, you can skip this section.
Note If you are using Windows Server 2008, the Progress Explorer Tool is not available. Instead, you must
set up a workstation to act as the Windows Admin Workstation. A remote Progress Explorer Tool connection
must be made from this Windows Admin Workstation to the server running Windows Server 2008 in order
to monitor AppServers and database status using Progress Explorer Tool.
1. Insert your OpenEdge 10.2A for Epicor 9.05.700 DVD in the server's DVD-ROM drive (D:\). The autorun
feature should launch the Installation wizard. If not, choose Start > Run and enter the command:
D:\OEMenu.exe.
2. The OpenEdge Installation option window appears. It may look similar to the following:

Epicor 9.05 Installation Guide Installation
3. Click the OpenEdge button to begin the installation.
4. The Welcome window appears. Click Next.
5. The installation wizard verifies if the required Progress OpenEdge components are installed on the server.
Review the Current Status of the components and whether an update is required. Click Next to continue.

6. The OpenEdge Install Type window appears. It is highly recommended that you select the Open Edge
Typical/Automatic Install option. Using this method, the install automatically specifies settings and
permissions.
Note If you want to install OpenEdge 10.2A using the Advanced/Manual method, select the
OpenEdge Advanced/Manual option and then use the Supplemental Installations section for
instructions.
7. If you need to install files for the web server, select the Install Files for Web Server check box. Click Next.
Note The files will be installed to C:\InetPub\adminscripts and C:\InetPub\wwwroot. If the directories
do not exist, they will be created automatically.
8. On the OpenEdge Version window, it is recommended that you select the 64 Bit Open Edge option. Click
Next.
Note If you are installing OpenEdge on an Admin Workstation, select the 32 Bit Open Edge option.
If you are installing OpenEdge on a 32 Bit operating system, this window is not displayed.
9. On the OpenEdge Location window, select the OpenEdge folder location for the Progress OpenEdge software
directory. The default directory is C:\Epicor\oe102a. Click Next.
10. The installation begins. The Progress Install Wizard runs in the background and is displayed in the bottom
task bar. Based on the current status of your system, the following components are installed:
• OpenEdge 10.2A
• OpenEdge Service Pack

• OpenEdge Service Pack Hot Fix

Note If you have a 64-bit operating system and you selected to install 32-bit Open Edge, you may
be prompted with several compatibility and security messages. The messages are warnings caused by
incompatibilities between Progress Open Edge and Microsoft. It is recommended you click Run Program
to continue through to a successful installation.
11. When the installation is complete, click Exit.
12. You are returned to the OpenEdge Installation Option window. Click Exit to close the installer.
Note After you have completed your upgrades, you can use the Post-Installation section of this guide
to setup the Progress OpenEdge Explorer Tool and the Supplemental Installation Guide to install Sonic,
if needed.
13. You now need to install the required hot fix (HF29) for Open Edge 10.2A SP3. To do this:
a. Log on to EPICweb and go to the Customer Portal Page. Navigate to Support > Epicor 9 > Downloads.
You can use this link: https://epicweb.epicor.com/Support/epicor9/Downloads .
b. Navigate to Version 9.05.700 > Third Party Products > OpenEdge > 10.2A.
c. Based on your environment, download the latest OpenEdge hotfix file onto your machine. For example,
download one of the following files:
• Windows 32: Rl102asp0329hf.EXE
• Windows 64: Rl102asp0329hf-64.EXE
d. Right-click on the file and select Run as Administrator. The installation program opens.
e. The Welcome window appears. Click Next.
f. Click OK to confirm you have stopped the OpenEdge related functions.

Note If you have not stopped the AppServer, database and AdminServices functions, click No
and then stop the functions before continuing.
g. Select the OpenEdge 10.2A directory as your Destination directory. For example, select C:\Epicor\oe102A.
Click Next.
h. The Ready to Install window appears. Click Next. The installation proceeds.
i. Click Finish. Depending on your selection, the files appear for review.
14. In order to successfully install the Progress OpenEdge Explorer Tool, you need to disable the Admin Service
for OpenEdge service. The service will be automatically re-enabled after the installation is complete. To
disable the service:
a. Select Start > Control Panel > Administrative Tools > Services. Right-click on AdminService for
OpenEdge and select Properties.
b. On the General tab, use the drop-down menu for Startup type to select Disabled. Click OK.
15. Reboot your server.

Chapter 4: Install or Upgrade the Epicor 9.05 Application
Use this section to install or upgrade your Epicor 9.05 application.

Note The installation process creates the application directory on your server, so you only need to install once.
You must install the application on the server before you install the client on any workstations.
Note Do not reference mapped drive letters in these instructions. Only use physical drive letters or UNC paths.
If you use mapped drive letters, the server installation will not work. For example, these instructions use C:\ drive
but you can use any physical drive of your choice.
4.1 Download Latest Release Files
Use these steps to download the latest Epicor 9.05 release, service pack, patch, and help files that will be installed
later in the installation process.
Note You can use this link:https://epicweb.epicor.com/Support/epicor9/Downloads
2. Navigate to Epicor 9 > Version 9.05.700.
3. Download the latest Epicor 9.05 release file related to this installation. For example, select the required file,
based on your environment:
• SQL Server: SP90570x-S.EXE
• SQL Unicode: SP90570x-SU.EXE
Note Be sure to also download the Release Notes document for this specific release. The Release
Notes filename may be similar to Epicor905_ReleaseNotes_ 90570x.pdf.
4. Download the latest Epicor 9.05 application patch related to this installation, if one is available. For example,
select one of the following files, based on your environment:
• SQL Server: PA90570xx-S.EXE
• SQL Unicode: PA90570xx-SU.EXE
Note Be sure to also download the Release Notes document for this specific release. The Release
Notes filename for a patch may be similar to Epicor905_ReleaseNotes_90570xx.pdf.
5. Download the latest Epicor 9.05 help content pack related to this installation. For example, download the
HELP90570x.EXE file.

4.2 Install Epicor 9.05 Server
Use the following steps to install or upgrade your Epicor 9.05 server software. During the installation you are
prompted to select the type of installation: Complete, Standard, Minimum, or Custom. Note that based on the
type selected, different components are delivered (not installed) as executable files to a folder on your server.
1. Go to the directory where you downloaded the Epicor 9.05.70x application file. For example, the filename
is similar to SP90570x-x.exe.
2. Double-click on the file to run it. The InstallAware wizard verifies that the setup package content is compatible
with your environment and prepares for your installation. This may take several minutes.
3. The Welcome window appears for installing the Epicor 9.05 server software. Click Next.
4. On the Installation Type dialog, select the type based on which features you want to install. The default
option is Complete. Options include:
Type Server Client Client Admin Delivers Delivers Delivers

Server Console Utilities EXE Server Web
Add-On Add-On
EXEs EXEs
Complete X X X X X X X
Standard X X X X X
Minimum X X X X
Custom optional optional optional optional optional optional optional
Note The components for the Utilities, Server Add-On, and Web Add-On features are delivered as
executable files to a folder on your server. The components are delivered, but they are not installed.
After your installation, you can use the Supplemental Installation section of this guide for instructions
on installing these additional features and programs.
Note The Server Add-On features include BPM Server, Enterprise Search, Epicor Education, Information
Worker, Replication, SSRS. The Web Add-On features include Epicor Mobile Access, Epicor Sharepoint
Publisher, Epicor Web Access, WCF Services, Web Services.
5. If you selected a Custom installation, you are prompted to select the specific features to install and deliver.
Select the features by clicking the down-arrow next to the X and selecting Install. The screen looks similar
to the following:

Note The selected features default from the Standard option.
6. After selecting the installation type and features (if selecting a Custom install), click Next.
7. The Application Folders window appears, prompting for the path for the application server and Data Work
folder. Keep the default folder locations or click Change to search and specify another folder. Click Next.
The screen may look similar to the following:

Note It is highly recommended that you keep the default folder locations and paths.
8. The UNC Path Name window appears, displaying the UNC path name for the Share directories. Click Next.
Note The Share folders will be created with Everyone having Full Control. After your install, use the
Post-Installation section of the guide to configure your shared folders to your environment.
9. The SQL Instance window appears. The instance name is used to define the ODBC connection to your SQL
Database. The default is the SQL 2008 instance name for your domain. Click Next.
Note If you want to install your initial SQL database on a different SQL server than where your Epicor
9.05.70x application is being installed, click the down-arrow and select a different SQL instance name.
10. The Testing Connection window appears. The SQL Connection to the instance name you selected is tested.
• If the test is successful, a message appears stating the SQL Connection test was successful. Click OK.
• If the test was not successful, a message appears stating the SQL Connection failed. When asked to try
again, select Retry. Verify the instance name you selected. You may have selected an instance name
that is not SQL 2008 or later. Click Next and try again. Note that if you select Cancel the installation will
stop.
11. If you selected to install your initial SQL database on a different SQL server than where your Epicor 9.05.70x
application is installed, you are prompted with the Remote SQL Database Paths window. Enter the paths to

specify the location on the remote SQL database server to install the database and log files. Note that you
must specify the remote (not local) locations for both the Production and Training databases. The screen
may look similar to the following:
Note After the installation, you must verify that the databases have been restored on the remote
SQL database server. If the databases are not restored, use the Post-Install instructions to manually
restore the SQL Database in that environment.
12. The Ready to Update window appears. Verify the server install directory. Verify the other components you
selected to install and deliver. For a Complete type installation, the screen may look similar to the following:

13. After verifying the components to install and deliver, click Next.
14. The installation begins. Informational messages appear. The installation process may take several minutes.
Note that when the empty databases are installed, a command box opens and processing messages may
display. This is normal.
Note If prompted with a message that a folder does not exist or cannot be accessed, verify that the
folder is shared and is not Read-Only, and then click Retry. For more information, see the
Post-Installation > Troubleshooting section of this guide.
15. The Setup Complete window appears when the installation is complete. Click Finish. If prompted to confirm
exiting the setup program, click OK.
Note The two environments configured by the installation are under ports 9401 and 9411. If you
want to configure additional environments, such as for a Test or Pilot database, use the "Configure
Environments for Test and Pilot" instructions located in the Post Installation > Troubleshooting section.
4.3 Install Epicor 9.05 Patch on the Server
Use these instructions to install the Epicor 9.05 patch on the server, if a patch is available.
1. Go to the directory where you downloaded the patch file.
2. Double-click on the file to run it. The InstallAware wizard verifies that the setup package content is compatible
with your environment and prepares for your installation. This may take several minutes.
3. A Welcome window appears. Click Next.

4. Enter the directory where your Epicor program files are located. Click Next.
5. You may be prompted to verify your server name, operating system or database type. If prompted, select
the appropriate option and click Next. Note that this prompt is only displayed if your mfgsys.ver file is
incomplete.
6. The Start Installation window appears. Click Next.
7. A message appears, stating that the application patch installation is complete. Click Finished.
The Epicor application patch is now installed.
4.4 Install Epicor 9.05 Help Content Pack
Use these steps to install the Epicor Help Content Pack on your system. The Help Content Pack contains the
updated online help system available with this release.
1. Go to the directory where you downloaded the latest Epicor 9.05 Help Content pack file.
2. Double-click on the file to run it. A Welcome window appears. Click Next.
3. Enter the directory where the Epicor 9.05 program files are located on the application server. Click Next.
The Start Installation window appears. Click Next.
4. A completion message appears. Click Finish.

Epicor 9.05 Installation Guide Post-Installation
Part III: Post-Installation

The following procedures explain the steps you perform after installing or upgrading Epicor 9.05, right up to
logging into the application client.
Chapter 5: Configure Application Server
Use the following instructions to configure your application server after installation.
5.1 Establish Security for Progress AppServer
Use these instructions to setup security and allow necessary privileges for the Progress AppServer software. These
steps can be used anytime, not just after installation, to keep your company's security requirements current.
5.1.1 Establish an Administrative Account
1. Create an account, or use an existing account, as an administrator. The account can be local (only to the
server) or a domain account (usable anywhere).
2. Verify that the account has administrative rights on the server where Progress OpenEdge 10.2A is installed.
5.1.2 Establish Local Security Policy
Use the following instructions to establish the local security policy.
1. Using the admin logon account specified above, select Control Panel > Administrative Tools > Local
Security Policy.
2. On the left pane, select Local Policies > User Rights Assignment.
3. In the right panel, double-click each of the following Policies, and add the domain User Account of the
user or group with system administrative rights for the server. You will connect these accounts through
Progress Explorer.
• Act as part of the operating system
• Adjust memory of quotas for a process
• Create a token object
• Create permanent shared objects
• Log on as a batch job
• Log on as a service

Post-Installation Epicor 9.05 Installation Guide
• Replace a process level token
5.1.3 Establish the AdminService Setting
Use the following instructions to establish the AdminService setting.
1. Use the Progress Explorer Tool or OpenEdge Explorer Tool to verify that your appservers and databases are
not running.
2. Using the admin logon account specified above, select Control Panel > Administrative Tools > Services.
3. Verify that the AdminService is stopped. To do this, right-click AdminService for OpenEdge 10.2A and
select Stop if the service is running.
4. To set up the service account, right-click AdminService for OpenEdge 10.2A and select Properties.
5. In the Log On section, click This Account, and specify the same user or group as with the Local Security
Policy settings. Again, the user or group must have administrative rights for the whole server.
6. Click OK. Then exit the Services window.
7. Click Start to start the service.
5.1.4 Configure Security for Multiple Servers
Use the following instructions to configure your security settings if your Epicor 9 environment includes more than
one application server with SQL Server hosted on a remote machine. For example, you need to set up a specific
domain account if you plan to set up your Application server as Server #1 and your SQL Server as Server #2.
1. Create a domain account that has domain user rights. The domain must be the domain where Server #1
and Server #2 will be located. For example, create a domain account for Domain1\Epicor9ServiceUser.
2. On both Server #1 and Server #2, add the domain account to the administrators group so that the account
has local administrator rights. For example, add the domain account Domain1\Epicor9ServiceUser.
3. Add the domain account as a SQL login user that has rights to the Epicor 9 database on Server #2 (SQL
Server).
4. Configure OpenEdge and your SQL Server services to be run using the domain account you just created.
For example, configure both to use the domain account Domain1\Epicor9ServiceUser.
5. Verify your ODBC Connection is set up using Windows Authentication.
6. Log into the Application Server (Server #1) using the domain account you configured. For example, log in
using Domain1\Epicor9ServiceUser. Using this domain account you will be able to run any processes including
the SQL Schema upgrade.

5.2 Setup Full-Text Searching on MS SQL Server
To emulate the Progress database engine on Microsoft SQL Server, the need for keyword searches on certain
fields is required.
However, SQL Server does not allow the same, less featured, quicker searches that Progress natively allows. In
order to fulfill this need, you are required to use the more fully featured and resource-intensive Microsoft Search
Service.
The Microsoft Search Service uses Full-Text Catalogs to perform word searches on specific fields in the database.
The Full-Text Catalogs are separate files of proprietary data structures, established for the purpose of evaluating
Contains and FreeText queries.
These files are not automatically updated along with the rest of the database. Full-Text Catalogs must be refreshed
on a periodic basis for them to reflect current data. The following information reviews the approach to keeping
these Catalogs up-to-date while minimizing the impact of the refresh process on the overall server performance.
5.2.1 Review the Process - Building Full-Text Catalogs
Populating Full-Text Catalogs requires a great deal of processing power and substantial writes to the Disk subsystem
on the server.
Due to this, you benefit greatly from moving the catalogs to separate disks to avoid contention for the disk when
writing the catalogs. More than one Catalog being built onto a disk results in Catalogs competing for space. The
server's resources will dictate how well you can avoid this bottleneck.
Another variable in the creation of the Catalogs is the Noise files used. Noise files contain any words or characters
to be skipped in the creation of the Catalogs. Since our description fields largely do not contain actual text, the
noise files are blank since this allows searching on most everything. The noise file feature is targeted more at the
evaluation of text where there are many filler words that are unimportant for searching.
SQL Server allows two Refresh options: Full Population which refreshes the entire catalog from the metadata
in the database; and Incremental Population which refreshes only the parts that have been changed. Results
vary based on the placement of the catalogs on the disks, server resources, and the number of changes. However,
Incremental populations take on average about one-third the time of Full populations.
Since populating (refreshing) the Catalogs is done on a regular basis and since the process can be intensive,
optimizing performance is an important part of optimizing the overall database server.
5.2.2 Starting the MS SQL Search Service
1. To verify that MS Search Service is running on the server, select Start > Control Panel > Administration
Tools > Services.
2. Confirm that the following Services are set:

• SQL Server > Started > Automatic
• SQL ServerAgent > Started > Automatic
• SQL Full-Text Filter Daemon Launcher > Started > Automatic
For any services that are not started, start the service and change the startup configuration if needed.
3. You may need to register a new SQL Server. To do this, open SQL Server Management Studio. Register
the server by selecting SQL Server Group. Right-click and choose New SQL Server Registration. Follow
the prompts to set this up.

5.2.3 Defining the Catalogs
After enabling full-text search on the database, you need to enable the full-text searching on the specific database,
tables, and columns. To do this, you need to define the Catalogs.
The Catalogs are separate files, so you need to determine where to place the files. For performance reasons,
locating the Catalogs on separate drives avoids contention for disk resources during the regular populations of
the Catalogs. Consider this, along with the times that you will run the jobs. If you choose to change the locations,
you need to perform step 3 in the following steps to drop the catalogs then you can re-edit the scripts and jobs
to reflect the new strategy.
Note The MSSQL Full Text scripts are available in the Epicor905\server\sql folder on the server where
your Epicor application is installed. For example, in a standard installation the path is
C:\Epicor\Epicor905\server\sql.
1. This is an optional step to change location. To drop the existing metadata and Catalogs, run the
FullTextCatalogDrop.sql script. If you choose to perform this step, you will need to perform the above
steps in the previous Starting the MS Search Service section again to re-setup the Catalogs, before you
proceed.
2. In SQL Management Studio, go to File > Open > File and navigate to the Epicor905\server\sql folder.
Select the script file FullTextCatalogCreate.sql. Click OK.
3. Scroll to the USE statement and change the database name between the brackets to your Epicor database
name. Click Execute on the toolbar. When completed, the results window should read Query batch
completed at the bottom of the window. Confirm that the catalogs are created by opening SQL Server
Management Studio then your server, Databases. Select the Epicor905 Database, then select Storage and
drill down to Full-Text Catalogs. All 32 Catalogs should appear in this list. You may need to refresh the
display or open and close SQL Server Management Studio to get it to reflect the new Catalogs.
5.2.4 Initial Population of Catalogs
At this point, the MSSQL Server database is prepared and the Catalogs are created. You now need to add data.
You do this by initially fully populating them.
1. In SQL Management Studio, go to File > Open > File and navigate to the Epicor905\server\sql folder.
Select the script file FullTextCatalogFullPop.sql. Click OK.
2. Scroll to the USE statement and change the database name between the brackets to your Epicor database
name. Click Execute on the toolbar. This may take several minutes to several hours depending on the size
of your database and the speed of your server. This step needs to be run only once.
When running the this initial population of the catalogs, you can use the Windows Task Manager to help
you determine when the populations have completed. To do this, open the Windows Task Manager and
click on the Performance tab. Review your CPU usage. Once your CPU usage returns to a less utilized status,
then the Catalog Initial Population should be complete.
3. To test that the Catalogs have been populated, log onto the Epicor application. Check that the keyword
searches function is based on the data currently in your database. The preferred testing method is to use
the Where Part Description Contains field for the Part Search component.
If your search returns appropriate data, then your Full-Text configuration is complete.

5.2.5 Setting Up the Catalogs to Update Incrementally
After you have finished the initial population of your full-text catalogs, you may want to set your catalogs to be
updated incrementally so they reflect the most current information.
Each Full-Text enabled column has been split into its own separate Catalog to allow the flexibility of being run
independently. Certain Catalogs will not be changed often enough to warrant running the refresh jobs on a daily
basis (such as langorg). Use the following steps to configure an incremental schedule.
1. Log into Microsoft SQL Server Management Studio. Expand the SQL Server Agent.
2. Right-click the Jobs folder and select New Job.
3. On the General page, enter a name for the schedule. For the category, select Full-Text. Enter a brief
description of the schedule task.
4. Select the Steps page. Click the New button. Enter the name for the step. Verify that Transact-SQL script
(TSQL) type is selected. Select the database on which you want this job to run. Click Open.
5. Select the FullTextIncremental.sql script. Click Open. You should see the contents of the script displayed
in the window. Verify that the USE statement contains the name of your database. If necessary, update the
USE statement. Click OK.
6. Select the Schedules page. Click the New button.
7. Enter the desired days and times you want the schedule to run. Click OK. Click OK on the Job Properties
window.
You have now configured your catalogs to be incremented automatically on a schedule.
5.2.6 Testing Server Impact for each Job
After building the full-text catalogs and setting up the schedule, each Administrator should review the overall
impact of the process and determine a strategy to balance timeliness and server performance.
1. At the server, go to Start > Control Panel > Administrative Tools and open the Performance program.
Right-click on the Counter column and select Add Counters. For Performance Object: Processor, add %
Processor Time. For Performance Object: Memory, add Pages/sec.
2. Run each job individually.
3. In the Performance monitor, review the Processor and Memory values. Verify they are low enough to see
the effect of the populations, such as Processor Time: 25% or under and Pages/sec: 10 or under. This process
may need to be the only activity running against the server in order to view the real effect.
4. You can also confirm the current status of the Catalog using Enterprise Manager > Databases >
Manufacturing > Full-Text Catalogs. The listing of the Catalogs with their Status and Last Population are
included. Note that this screen does not refresh easily.
You can also run sp_help_Fulltext_Catalogs in the Query Analyzer to determine the current status. See
the BOL (SQL Server books online) for detail.
5. Adjust the individual schedules of the Catalog Refreshes to optimize timeliness and server performance.

5.3 Setup Progress OpenEdge Manage Tool

If you want to use the OpenEdge Manage tool instead of the Progress Explorer Tool, use these steps to setup
the OpenEdge Manage tool. If you already have the Progress OpenEdge Manage Tool installed and setup, you
can skip this section.
1. Verify that the AdminService for OpenEdge 10.2A is not running. To do this:
a. Select Start > Control Panel > Administrative Tools > Services.
b. Right-click on AdminService for OpenEdge and select Properties.
c. On the General tab, verify the Service status is Stopped. Click OK.
2. Insert your Progress OpenEdge 10.2A for Epicor 9.05.700 DVD in the server's DVD-ROM drive (D:\). The
autorun feature should launch the OpenEdge Installation wizard. If not, choose Start > Run and enter the
command: D:\OEMenu.exe.
Note If you do not have access to the DVD, you can download the required files from EPICweb
Support Downloads.
3. The OpenEdge Installation option window appears. Click the OpenEdge Manage button to begin the
installation.
4. The OpenEdge License Code window appears. It looks similar to the following window. Note that you will
need to enter the Serial Number and Control Number in the next step during the installation. This window
will remain open during the installation so that you can copy the text from the fields into the installer. If
desired, you can also record the license codes. Click Next.
5. The OpenEdge Progress Software installer runs. On the Welcome window, click Next.
Note If you are installing OpenEdge Explorer Management for 64-bit on a Windows 64-bit machine,
you may be exited from the installation. This is a known issue with the Progress OpenEdge Explorer

Management installation. To resolve the issue, close all applications and restart the OpenEdge Explorer
Management installation.
6. Enter the Serial Number and Control Number. You can copy and paste the text from the OpenEdge Install
window that is minimized on your status bar. Be sure to copy the data for your platform.
7. Click Accept. Click Next.
8. On the Destination and Working Path Directories window, click Next to use the default paths.
9. On the Program Folder window, click Next to select the OpenEdge Explorer.
10. On the Summary window, click Next. The files are installed.
11. When the installation is complete, click Finish.
12. You are prompted to reboot your computer. Click Yes. If you click No you are returned to the OpenEdge
Installation option window. Click Exit.
13. Change the starting method for the AdminService for OpenEdge. To do this:
c. On the General tab, use the drop-down menu for Startup type to select Manual. Click OK.
14. Start the AdminService for OpenEdge 10.2A . To do this:
c. On the General tab, click Start. Click OK.
15. To configure your OpenEdge Explorer, go to Start > Programs > OpenEdge Explorer > Management
Console. This program launches your web browser with the URL: http://localhost:9090. When prompted
for a username and password, enter admin / admin.
16. To configure the tool, use the OpenEdge Explorer guides. To access the guides, go to Start > Programs >
OpenEdge Explorer > Documentation > OpenEdge Explorer.
5.4 Update Parameter File for Multi-Server Configuration
Use these steps to update the Host parameter value if you use a multi-server configuration, for example, if you
have your Epicor 9.05 application server installed on a different machine than your SQL server. This parameter
value change is required in order for your system to run properly.
1. On the server where your Epicor application is installed, navigate to the Server\Config folder.
2. With a text editor, open the mfg*TCP.pf parameter file for the database you want to configure. For
example, parameter files include: MfgTCP.pf, MfgTrainTCP.pf, MfgTestTCP.pf, MfgPilotTCP.pf.

3. Locate the -db line. Update the -H value to be your Epicor application server. For example, the line would
look similar to the following:
-disabledeltrig
-T "C:\Epicor\EpicorData"
-db mfgsyssh -H EpicorApplicationServer -S 9400
where "EpicorApplicationServer" is the machine name of your Epicor application server.
4. Save and close the file.
5. You now need to update your Epicor Admin Tools client workstation. To do this, on the server where you
run your Epicor Admin Tools, navigate to the Server\Config\cs folder. Repeat the above steps to update
the following files: MfgTCP.pf, MfgTrainTCP.pf, MfgTestTCP.pf, MfgPilotTCP.pf.
Note If you do not use these steps to update the Host (-H) parameter, when you open Epicor Admin
Tools to run the conversion programs, you will be prompted with a message similar to the following:
"Could not connect to server for database mfgsyssh, errno 0 (1432)."
5.5 Verify Parameter File Settings
Use these steps to verify the parameter settings that are defined in the *.pf files. Several parameter settings are
required in order for your appservers to start and for your system to run properly. The parameter settings may
differ based on your database type, either Progress or SQL.
Note If the required parameters are not included in the *.pf file, your appservers will not start.
1. On the server where your Epicor application is installed, navigate to the Server\Config folder.
2. With a text editor, open the parameter file for the database you want to configure. For example, locate one
of the following files: Mfgsys.pf, MfgsysTCP.pf, MfgTrain.pf, MfgTrainTCP.pf, MfgTest.pf, MfgTestTCP.pf,
MfgPilot.pf. MfgPilotTCP.pf.
3. For both SQL and Progress databases, use the following to verify the required parameters in the .pf file.
Parameter Description Required Value

-disabledeltrig Disable delete trigger to allow replication logic to run properly. -disabledeltrig
Even if you do not use replication, this parameter is required.
This parameter must not be the last line in the .pf file.
-rereadnolock changes read-only record retrieval to get consistent results -rereadnolock
-ttmarshal Improve performance -ttmarshal 5
-tmpbsize Improve performance by allowing appserver agent to hold -tmpbsize 8
more temporary table records before paging them out to the
temporary disk file. If the value is not 8, a warning message
is displayed but the appservers are allowed to start.
4. For SQL databases only, use the following to verify the required parameters in the .pf file.
Parameter Required Value

PRGRS_NOWAIT_OVERRIDE PRGRS_NOWAIT_OVERRIDE,1

Parameter Required Value

TXN_ISOLATION TXN_ISOLATION,1
PRGRS_NATIVE_LOCKWAIT PRGRS_NATIVE_LOCKWAIT,30000
5. For both SQL and Progress databases, use the following to verify the optional parameters in the .pf file.
Parameter Description Optional Value

-Bt Improve appserver performance in dealing with temporary tables. -Bt 4096
Increase the value based on the amount of memory on the server
where the Epicor application is installed. For example, for 4 GB of
RAM, increase value to 4096; for 8 GB of RAM increase to 8192.
6. If needed, review the parameter values in the following example .pf files.
• Example: Progress
• Example: SQL

• Example: SQL Unicode
7. Later, when you start your appserver, if the appserver does not start due to parameter validation issues,
review the appserver log file. In a standard installation, the log file is located in the Server\Logs folder.
5.6 Configure the Euro Currency Symbol
If you use a non-unicode Epicor environment and you need to display the Euro currency symbol within Epicor
program or reports, you must update the .pf file code page reference to leverage Windows-1252 code.
An optional post-installation step, you can display the Euro currency symbol by adding a code page reference
line to the AppServer .pf file. This reference line causes your Epicor application to use the Windows-1252 code.
1. Navigate to the directory that contains your server configuration files. For example:
C:\epicor\deployment\server\config
2. Locate the AppServer .pf file you use with the Epicor application. For example, locate one of the following
files: Mfgsys.pf, MfgsysTCP.pf, MfgTrain.pf, MfgTrainTCP.pf, MfgTest.pf, MfgTestTCP.pf, MfgPilot.pf.
MfgPilotTCP.pf.
3. Open your .pf file in a text editor like Notepad or a similar application.
4. Enter this line within the .pf file:

-cpinternal 1252 -cpstream 1252
5. Save the file and close the text editor.
Your Epicor application now uses Windows-1252 code. This code set contains the Euro currency symbol, so you
can display this symbol on various programs and reports throughout the Epicor application.

Chapter 6: Prepare Your Database
Use the following instructions to prepare your database prior to logging in the first time.
6.1 Initialize or Convert Your Database
Use these instructions to initialize (for new installations) or convert (for existing installations) your database for
compatibility with the Epicor 9.05 application.
6.1.1 Before You Begin
1. Verify that you have SQL and 32-bit Progress OpenEdge installed on any machine where Epicor Admin Tools
or Epicor Schema Change is installed.
2. Verify that the following steps are completed on a machine that has SQL and 32-bit Progress OpenEdge
installed. The Epicor 9.05 Schema Change process must be executed on a machine that has both SQL and
Progress OpenEdge installed.
3. Use the Progress Explorer Tool or OpenEdge Explorer Tool to verify that your Appservers are not running.
Your Appservers cannot be running when you run schema changes or conversions.
4. Use the Progress Explorer Tool or OpenEdge Explorer Tool to verify that your database is running. Your
database must be running in order to run schema changes or conversions.
5. Verify you created a backup of your database as a step in the Getting Started > Verify Prerequisites section.
6.2 Add Epicor and Application Server Connections
Use the following steps to use the Epicor Administration Console to add and then connect to the Epicor server
and application server.
1. Use the Progress Explorer Tool or OpenEdge Explorer Tool to do the following:
• Verify that your database is running.
• Start the main AppServer specific to this database. For example, start the Epicor905 AppServer.
2. Open the Epicor Administration Console. To do this, navigate to Start > Programs > Epicor Software >
Epicor Administrative Tools > Epicor Administration Console.
Note You may be prompted to update your Microsoft Management Console (MMC) to version 3.0
or later. See the Microsoft MMC 3.0 download site for more information.
3. Login with a valid User ID and Password. Note that the user must have Security Manager rights. For example,
login as epicor / epicor.
4. Right-click on the Server Management node. Select Add Epicor Server.
5. Enter the Name of the server.

6. Click Ping Server. Click OK to confirm that the server was located.
7. Click OK to add the Epicor Server.
8. Right-click the Epicor Server you just added. Select Add Application Server.
9. Select New Application Server Properties, including the following:
a. Name. Enter the name of the application server.
b. Port Number. Enter the identifier of the port to which you are connecting.
c. User Name. Enter "manager" as your user name to log into the Epicor database.
d. Password. Enter "manager" as your password to login to the Epicor database.
10. Click Test Connection. Click OK to confirm the connection.
11. Right-click on the Application Server you just added. Select Connect to Application Server.
Note If you are a new customer, a User Name called Manager is created when you connect to the
Application server for the first time. The password for this user is Manager.
The Epicor server and Application server should now be configured.
6.3 Import License Codes
Use the following steps to import your Epicor 9.05 application license codes.
Note If you are using an Epicor 9.05.60x application, you must complete the following steps. If you are
using an Epicor 9.05.70x application, you have already completed these steps and you can proceed to the
next section.
Note If you are an existing customer using EDI or Demand Management, you must use these steps to
import the new license for those modules.
1. In the Epicor Administration Console, right-click on the desired database and select Connect to Application
Server.
2. Right-click on the Licensing node and select Import License File. Your dialog may look similar to the
following:

3. Browse to the location where you previously downloaded the license code file. Select the file and click Open
to import the file.
4. Double-click on the licensing code to open it. The Properties dialog opens.
5. Click the Modules tab. Select the check box for each module you want enabled.
Note It is recommended that you carefully review the modules that you have selected to enable.
Failure to enable your modules may result in possible data corruption. Also, if you enable a new module
at this time, you are committing to basic configuration and implementation steps within the application.
6. Click OK.
7. Repeat the above steps, if you are importing licensing for multiple databases.
6.4 Add Company
Use the following steps to create or add a company. If you are a new customer, you must create a company.
1. In the Epicor Administration Console, right-click the Companies node. Select Add Company. The dialog
may look similar to the following:

2. In the Add Company dialog, specify your company information.
3. To assign a Serial Number to the new company, click the browse (...) button to search for a list of serial
numbers. Select the appropriate serial number. Click OK.
4. Click OK to save the information.
5. Repeat these steps for additional companies, if desired.
6.5 Stop Main AppServer
Use the following instructions to stop the main AppServer.

Note If you are using an Epicor 9.05.60x application, you must complete the following steps. If you are
using an Epicor 9.05.70x application, you have already completed these steps and you can proceed to the
next section.
1. Use the Progress Explorer Tool or OpenEdge Explorer Tool to stop the main AppServer.
2. Minimize the Progress Explorer Tool or OpenEdge Explorer Tool.
6.6 Run Conversions Using Epicor Admin Tools
Use these steps to run the data initializations (for new installations) or data upgrades (for existing installations)
on your Epicor 9.05 application.
Important If you use a 64-bit server you must run Epicor Admin Tools from a 32-bit Admin workstation.
To do this, use the instructions in the "Configure Windows Admin Workstation" section.
1. On the server, run the Epicor Admin Tools program as Administrator. To do this, navigate to Start >
Programs > Epicor Software > Epicor 9.05, right-click Epicor Admin Tools and select to Run as
Administrator.

2. Login using "manager / manager" as your User ID and Password. Note that this user has Security Manager
rights and was created when you connected to the Application server for the first time.
3. Click OK. Mandatory initialization programs run.
4. To verify that the mandatory conversions or initializations completed successfully, make sure the database
conversion date is the correct date. To do this:
a. Select the Run Conversion Program option.
b. Review the list of programs that were run. If necessary, scroll to the right to see the Date the program
was run.
Note If you use Extended UD Table functionality, a schema change was run automatically for those
extended UD tables.
5. When the processing is completed, close Epicor Admin Tools.
6.7 Stop and Start AppServers
If the AppServers were running during any previous conversion step, use these steps to stop and start the
AppServers. It is strongly recommended that you complete these steps after running the automatic data conversions.
1. Use the Progress Explorer Tool or OpenEdge Explorer Tool to stop the AppServer processes in the following
order: Epicor905ProcessServer, Epicor905TaskAgent, Epicor905.
2. Use the Progress Explorer Tool or OpenEdge Explorer Tool to start the AppServer processes in the following
order: Epicor905, Epicor905TaskAgent, Epicor905ProcessServer.
6.8 Verify Avalara Path Value
If you use Avalara Tax functionality, use the following steps to verify that the OpenEdge path defined in a required
batch file is accurate.
1. On your server, navigate to the \Avalara folder. For example, go to \server\Avalara.
2. With a text editor, open the WinAvalaraPlugin.bat file.
3. Locate the line for the OE value. Verify that the path corresponds to the location of your OpenEdge folder.
For example, if your OpenEdge folder is located on the C: drive, the value is OE=C:\oe102a.
4. Save and close the file.

Chapter 7: Install Epicor 9.05 Client on a Workstation
Use the following instructions to install the Epicor 9.05 client on your workstation. New customers or existing customers
who are adding a new client workstation should use the following instructions to install the Epicor 9.05 Client. If you
are an existing customer and you are not adding a new client, you should use the following instructions to update the
version of Crystal Runtime installed on your client workstation.
Note The instructions on Crystal Runtime installation can also be used on your server or Windows Admin
workstation, if you plan to print Crystal Reports forms from your server or Windows Admin workstation.
7.1 Install Microsoft Tools .NET 3.5 and WSE or WCF Runtime (Client)
Use the following steps to download and install Microsoft tools, such as .NET and either WSE (Web Services
Enhancements) or WCF (Windows Communication Foundation) from the Microsoft Download Center website.
Note that WCF is included as part of the base .NET 3.5 framework.
Note Review your decision to install either WSE or WCF, which you determined in the Perform
Pre-Installation Steps section.
1. Download Microsoft .NET 3.5 from the Microsoft Download Center to your workstation. To do this:
a. Click the following link to go to the Microsoft Download Center: http://www.microsoft.com/download

s/details.aspx?displaylang=en&FamilyID=ab99342f-5d1a-413d-8319-81da479ab0d7
b. Download the latest version of Microsoft .NET 3.5 to your workstation.
Note The .NET 3.5 installation includes the .NET Service Pack when you download .NET 3.5 from the
Microsoft Download Center website.
2. If you want to install Web Services Enhancements (WSE) 3.0 Runtime, use the following steps:
a. Click the following link to go to the Microsoft Download Center: http://www.microsoft.com/download

s/details.aspx?FamilyID=1F445589-818A-4E7B-B49B-FFE9393E4D0A&displaylang=en
b. Download the latest version of Microsoft Web Services Enhancements (WSE) 3.0 Runtime to your server
and Windows Admin workstation.
7.2 Install Epicor 9.05 Client Software
Use the following instructions to start the client installation.
1. Make sure you are logged in as the Local Administrator on the client workstation.
2. Use Windows Explorer to navigate to the server where Epicor 9.05 is installed. Go to the Epicor905 folder.
Double-click to run the Epicor9Client.msi file.
3. The Welcome window appears for installing the client software. Click Next.

4. The Destination Folder window appears. Specify the Client Destination and the Server Share Location path.
a. For the Client Destination, click Change to navigate to a destination folder. For example, you can use
C:\Epicor\Epicor905.
b. For the Server Share Location, use \\<servername>\Epicor905, where <servername> is the machine name
where the server installation was done.
c. Click Next.
5. The Shortcut Creation window appears. Select the Create Desktop Icons check box to create the following
shortcut icons on your client desktop.
a. Epicor 9.05: Select this checkbox to run your Epicor 9.05 database from this workstation.
b. Epicor 9.05 MES: Select this checkbox to run the Data Collection programs from this workstation.
c. Epicor 9.05 Admin Tools: Select this checkbox to run the Epicor 9.05 Admin Tools from this workstation.
d. Epicor 9.05 Schema Change: Select this checkbox to run the Epicor 9.05 Schema Change from this
workstation.
Note The Epicor 9.05 Admin Tools and the Epicor 9.05 Schema Change check boxes are only
available if OpenEdge is installed on the workstation. If these check boxes are available, you must also
specify the OpenEdge installation location.
6. In the same window, you can also select the following check boxes to create icons in your program menu:
• Create Training Icons: Select this checkbox for training icons that can access the training database.
• Create Test Icons: Select this checkbox for test icons that can access the test database.
• Create Pilot Icons: Select this checkbox for pilot icons that can access the pilot database.
7. Click Next.
8. The Ready to Install the Application window appears. Click Next.
9. When finished, click Finish to complete.
10. If prompted, reboot the workstation at this time.
7.3 Install Crystal Reports Runtime
Use the following steps to install Crystal Reports 2010 SP3 Runtime on your client. You can also use these steps
to install Crystal Reports 2010 SP3 Runtime on your server or Windows Admin workstation, if you plan to print
Crystal Reports forms from your server or Windows Admin workstation.
Note You cannot install both Crystal Reports 2010 SP3 Runtime and Crystal Reports 2008 Developer on
the same client.
1. If you have a previous version of Crystal Reports .NET Runtime installed on your client, use the following to
uninstall the previous version:
a. Navigate to Start > Control Panel > Programs > Uninstall a Program.
b. Select Crystal Reports .NET Runtime and click Uninstall.

c. Verify the uninstallation was completed successfully.
Note You can use this link: https://epicweb.epicor.com/Support/epicor9/Downloads
3. Navigate to Epicor 9 > Version 9.05.700 > Third Party Products > Crystal > Version 9.05.70x.
4. Download the latest Crystal 2010 SP3 Runtime file. For example, download Crystal Reports 2010 SP3.zip.
5. Navigate to the downloaded file. Open the .zip file and extract the contents.
6. Double-click to run the .msi file. For example, if you run your Epicor client using the 32-bit mfgsys.exe, run
the CRRuntime_32bit_13_0_3.msi file.
7. The Welcome window appears. Click Next.
8. Review the license agreement information. Select I accept the License Agreement. Click Next.
9. If prompted, confirm the installation. Click Next.
10. The installation proceeds. When it is finished, click Finish.

Chapter 8: Log in the First Time
Use the following steps to verify and test your Epicor 9.05 application the first time you log in.
8.1 Import Posting (Booking) Rules
If you are installing Epicor 9.05 for the first time, use these steps to import your posting rules for both Standard
and Extended Rules.
1. Open the Epicor 9.05 application.
2. Select Financial Management > General Ledger >Setup > GL Transaction Type.
3. From the Actions menu, select Import ACT Type.
4. Click the Input File Name button. Navigate to the necessary folder based on your posting rules type. For
example, go to one of the following:
• Standard rules: \\<servername>\Epicor905\server\PostingRules\Standard
• Extended rules: \\<servername>\Epicor905\server\PostingRules\Extended
5. Select one or more .XML files. You can select multiple files by pressing the Shift key while you highlight
the files. Click Open to select the highlighted files.
6. Select the Import All check box to specify that you want to import all the selected XML files. To specify
individual XML files instead, you can select the Selected check box for each file.
7. If this is not the first time you are importing posting rule files, you can select the Replace All check box to
replace your existing revision with the same name. To specify to replace individual XML files instead, you
can select the Replace Existing check box for each file.
8. Select the Change All Revision Statuses To Active check box if you want to change the revision from a
draft to active for all transaction types being imported. To specify to activate individual XML files instead,
you can select the Activate check box for each file.
9. Select the Import into all companies check box if you want to import the posting rules into each company.
Note that newly created revisions are automatically set to Active in all companies.
10. Click OK to begin the import.
11. You may be prompted with the Book Mapping dialog if any imported revisions contain books with IDs that
do not exist in the company to which you are importing rules. Do the following and click OK:
• Specify the mapping to select which book in the company should receive rules from which book in the
import xml file. The import program verifies if the imported rules use segments that don't exist or are
defined with a different name in the receiving book's Chart of Accounts (COA). If such segments exist,
you must either manually select the correct segment of the receiving COA that should be used or specify
that these segments should be assigned new values during the import.
• If you want to map the selected book identifier to all transaction types, select the Use for all transaction
types check box.

12. Click Save to save your imported financial data.

Note To copy the rules from one book to another, you can use GL Transaction Type Maintenance.
You create a revision, and then copy both the header and detail rules one at a time into a new book.
Then activate the revision.
8.2 Verify System Agent for Printing
Use the following steps to verify the directory paths for your System Agent to enable printing.
1. Review the paths you specified during the server software installation for the following locations:
• Destination Location
• Print Folder Destination Location
• Server Share Location
2. Launch your Epicor 9.05 application.
3. Navigate to System Management > Utilities > System Agent.
4. Click Agent ID to search for the system agent identifier.
5. The identifiers are listed. Select SystemTaskAgent. Click OK.
6. In the SystemAppServer section, verify your directory paths are accurate. For example:
Directory Description Examples

Server File specifies the local path on the server to the c:\Epicor\EpicorData
print directory
Client File specifies the UNC path to the print directory \\<servername>\EpicorData
Client Program specifies the UNC path to the server directory \\<servername>\Epicor905\Server
8.3 Test System and Repeat Installation
Based on your installation process, you are at one of the following points:
• If you completed the Epicor 9.05 installation in a test environment, you are now ready to test the installed
Epicor 9.05 application in that environment. After your testing is complete, you must repeat the entire
installation in your production environment.
• If you completed the Epicor 9.05 installation in your production environment, you are now ready to use the
installed Epicor 9.05 application in that environment.
Note that while it is possible to install multiple versions of the Epicor application on the same server for testing
purposes, it is not recommended.

Chapter 9: Restore Demonstration Database
Use the following instructions to restore the Epicor 9.05 Demonstration Database, if desired. The Epicor 9.05
Demonstration Database is released with every Service Pack and is used with the Embedded Education Courses. Note
that the Demonstration Database as delivered by Epicor must be used only with the Epicor application version for which
it was released.
9.1 Download Demonstration Database File
Use the following instructions to download the appropriate Demonstration Database file based on your database
platform. Each *.zip file includes a copy of the Demonstration Database that can be restored to replace the
existing Demonstration Database.
You can click this link: https://epicweb.epicor.com/Support/epicor9/Downloads
2. Navigate to Epicor 9 > Version 9.05.700 > Demonstration Database.
3. Download the latest Epicor 9.05 Demonstration Database related to this installation. For example, download
the necessary files, based on your environment:
• SQL (32): Epicor9_Database_90570x_Win32SQL.zip
• SQL (64): Epicor9_Database_90570x_Win64SQL.zip
• SQL Unicode (32): Epicor9_Database_90570x_Win32SqlUnicode.zip
• SQL Unicode (64): Epicor9_Database_90570x_Win64SqlUnicode.zip
9.2 Verify Prerequisites
Use the following instructions to verify the prerequisite steps have been completed.
1. All Appservers and OpenEdge Databases are stopped.
2. Epicor 9.05 Service Pack or Patch has been installed, if available.
3. Epicor 9.05 Post-Installation steps have been completed.
9.3 Restore the Demonstration Database
Use the following instructions to restore the Demonstration Database using SQL Server. These instructions assume
you have an EpicorTrain905 database in SQL Server.
1. Go to the location where you downloaded the zipped files.
2. Open the .zip file. For example, open Epicor9_Database_90570x_WinxxSQLx.zip file. Extract the
Epicor9_Database_WinxxSQLx.BAK file directly into the C:\Epicor\Epicor905\db\Training folder.
3. Navigate to Start > All Programs > OpenEdge 10.2A, right-click ProEnv and select Run as administrator
from the menu. A DOS window opens.

4. At the proenv> prompt, type: Prompt and press Enter.
5. Type: cd\ and press Enter.
6. At the c:\> prompt, type: cd \Epicor\Epicor905\db\Training and press Enter.
7. At the C:\Epicor\Epicor905\db\Training> prompt, run the Prorest command. For example, type one of the
following and press Enter:
• SQL 32 bit: prorest mfgsyssh mfgsyssh32.bkup
• SQL Unicode 32 bit: prorest mfgsyssh mfgsyssh32u.bkup
• SQL 64 bit: prorest mfgsyssh mfgsyssh64.bkup
• SQL Unicode 64 bit: prorest mfgsyssh mfgsyssh64u.bkup
8. At the overwrite message, type Y and press Enter.
9. When the restore is completed, you are returned to the C:\Epicor\Epicor905\db\Training> prompt. Type exit
to close the DOS window.
10. At your server, navigate to Start > Programs > Microsoft SQL Server > SQL Server Management Studio
(SSMS).
11. Within SSMS, verify the Server Type is connected to the database engine.
12. Navigate to the Databases node.
13. Right-click on the EpicorTrain905 database. From the context menu, select Tasks > Restore > Database.
The Database window displays.
14. Click on the General tab. Within the Source for Restore section, select From Device.
15. Click on the [...] button. The Specify Backup window displays.
16. For the Backup Media option, select File.
17. Click the Add button to locate and select the backup file. This file is: Epicor9_Database_WinxxSQLx.BAK
18. Click OK twice to complete the selection.
19. In the Restore column, select the check box for the backup you are installing.
20. Click on the Options tab.
21. Select both the Overwrite the existing database and Leave Database Ready to use (Restore with
Recovery) check boxes.
22. Verify the Restore Database Files As fields match the correct server directory paths where the database
files currently exist. For example:
• C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\ EpicorTrain905.mdf
• C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\ EpicorTrain905_log.ldf
23. Click OK. A dialog box is displayed indicating the database restoration is complete. Click OK.

24. Exit SQL Server Management Studio.
9.4 Start Main AppServer
Use the following instructions to start the main AppServer.
1. Use the Progress Explorer Tool or OpenEdge Explorer Tool to start the main AppServer. For example,
EpicorTrain905.
2. Minimize the Progress Explorer Tool or OpenEdge Explorer Tool. Do not start the other AppServers yet.
9.5 Import License Codes and Enable Modules
Use the following instructions to import the product license codes and enable the modules.
1. Open the Epicor Administration Console. To do this, navigate to Start > All Programs > Epicor Software
> Epicor Administrative Tools > Epicor Administration Console.
2. In the Epicor Administration Console, right-click on the training database, such as EpicorTrain905 and
select Connect to Application Server.
Note If you are unable to connect to the application server, verify that the application server for this
database instance is running. Also confirm that the application server is configured to log in with
Security Manager access. The configuration requires a valid User ID and Password.
3. Right-click on the Licensing node and select Import License File.
4. Browse to the location where you previously downloaded the license code file. Select the file and click Open
to import the file.
5. Specify the imported license file for each company. To do this:
a. Select the Companies node. In the Companies column, right-click on your specific company, such as
Epic01, and select Properties.
b. Click the browse (...) button to search and select your serial number from the list of Available Serial
Numbers. Click OK.
c. Repeat for each of the other companies, such as Epic02 and Epic03.
6. Enable the modules attached to the imported licenses. To do this:
a. From the list, select Licensing.
b. Right-click on the license serial number and select Properties.
c. Click the Modules tab.
d. Select the individual modules to activate, or click the Enable all Licensed button to select all the modules.
The Enabled check box should be selected for the modules you want to activate.
e. Click OK.

7. When finished, exit the Epicor Administration Console.
9.6 Run Manual Conversions
Use the following instructions to run required manual conversions.
1. Use the Progress Explorer Tool or OpenEdge Explorer Tool to verify that your AppServers are not running.
Your AppServers cannot be running when you run conversions.
2. On the server, run the Epicor Admin Tools program as Administrator. To do this, navigate to Start >
Programs > Epicor Software > Epicor 9.05, right-click Epicor Admin Tools and select to Run as
Administrator.
3. Login with a valid Epicor User ID and Password. Note that the user must have Security Manager rights.
4. Select Run Conversion Program.
5. If you use Epicor 9.05.700, 9.05.700A, 9.05.700B, or 9.05.700B2 you must run a conversion to delete
obsolete Local001 records. During the installation of these prior versions, a conversion program was run
which added obsolete records to your database. After installing Epicor 9.05.700C, you must run the conversion
again to delete the obsolete records. Use these steps:
a. Scroll down the list of programs to number 11185 called Delete obsolete Local001 records (cvar0037).
b. Highlight the program to select it.
c. From the Conversion menu, select Run Conversion Program. Click Yes to confirm.
6. Run the manual conversion to reset the sequence table. To do this:
a. Scroll down the list of programs to number 5460 called Re-set DB Sequences.
b. Highlight the program to select it.
c. From the Conversion menu, select Run Conversion Program. Click Yes to confirm.
7. After the conversions finish, exit Epicor Admin Tools.
9.7 Set Up System Agent for Printing (Demo Database)
Use the following instructions to set up your system agent. The paths for the System Agent, which control report
printing, must be reset after a database restore.
These instructions assume your database is set to be the Mfgsys database directly located in this folder: C:\Programs
Files\Epicor Software\Epicor905\db\Training.
1. Review the paths you specified during the server software installation for the following locations:
• Destination Location
• Print Folder Destination Location
• Server Share Location
2. Launch your Epicor 9.05 application.

3. Navigate to System Management > Utilities > System Agent.
4. Click Agent ID to search for the system agent identifier.
5. The identifiers are listed. Select SystemTaskAgent. Click OK.
6. In the Task AppServer section, change the AppServer URL to AppServerDC://localhost:9413.
7. In the System AppServer section, change the AppServer URL to AppServerDC://localhost:9411.
8. The Username defaults to print. Enter the Password as print.
9. In the SystemAppServer section, enter your directory paths. For example:
Directory Description Examples

Server File specifies the local path on the server to the c:\Epicor\EpicorData
print directory usr/epicor/epicordata
Client File specifies the unc path to the print directory \\<servername>\EpicorData
Client Program specifies the unc path to the server directory \\<servername>\Epicor905\Server
10. Save the System Agent changes. Exit System Agent Maintenance.
11. Close the Epicor 9.05 application.
9.8 Start Remaining Appservers
Use the following instructions to start the remaining Appservers.
1. Open the Progress Explorer Tool or OpenEdge Explorer Tool. Start the Appservers in the following order:
• EpicorTrain905TaskAgent
• EpicorTrain905ProcessServer
2. Exit the Progress Explorer Tool or OpenEdge Explorer Tool.
9.9 Test Demonstration Database Update
Use the following instructions to verify that the Demonstration Database was properly updated.
1. Open the Epicor 9.05 application.
2. Log in using a valid User ID and Password. For example, log in as epicor / epicor.
3. From the Help menu, select About Epicor 9.
4. Verify that the version has changed to the correct version you installed.

Chapter 10: Configure Windows Admin Workstation
Use these steps to configure a Windows Admin Workstation. Be sure to review the section on verifying your prerequisites
prior to starting the configuration.
10.1 Verify Prerequisites for Windows Admin Workstation
Use the following steps to verify the requirements on your Windows Admin Workstation.
1. Based on your Epicor application, determine if you need the Windows Admin Workstation:
• If you are running a 64-bit install of the Epicor application, the Windows Admin Workstation is required.
• If you are running a 32-bit install of the Epicor application, the Windows Admin Workstation is not
required.
2. Verify that you have SQL and 32-bit Progress OpenEdge installed on the Windows Admin Workstation if
you plan to run Epicor Admin Tools or Epicor Schema Change on that workstation.
3. Verify that you have access to the SQL Management Tools on this workstation. To do this, open a Command
Prompt and type in "osql.exe". The results should display the file. If an error is displayed the command is
not available, which means the SQL Management Tools are not installed. Review your SQL installation and
verify that SQL Management Tools are installed.
4. Your Windows Admin Workstation can be used as a client or a server machine, but it cannot have a 64-bit
version of OpenEdge installed. Note also that the 32-bit and 64-bit OpenEdge Software cannot be located
on the same machine.
5. Your Windows Admin Workstation operating system can be either 32-bit or 64-bit version of Windows.
6. Verify that the Windows domain user that is logging into the Windows Admin Workstation has full read/write
access to the SQL database that includes the Epicor 9.05 databases. To grant this access, add the Windows
domain user to the SQL Security.
10.2 Install ODBC Driver (SQL Server Native Client 10)
If you use SQL, use these steps to download and install the SQL Server Native Client 10 ODBC driver.
Note The SQL Server Native Client 10 ODBC driver is required if you are installing the Admin Tools and
Schema Change shortcuts from the client workstation onto a Client Server Admin machine. The installation
of this ODBC driver is required for the client to communicate with the database.
1. Go to the Microsoft Download Center website to download the SQL Native Client 10. The SQL Native Client
10 is included in the Feature Pack for Microsoft SQL Server 2008 R2. The link is: http://www.microsoft.com
/en-us/download/details.aspx?id=16978
2. On the Microsoft SQL Server 2008 R2 Feature Pack page, scroll to the download link for Microsoft SQL
Server 2008 R2 Native Client. Download the appropriate version of the SQL Native Client 10 installation file.
3. Install the SQL Native Client 10. Verify that it is installed correctly.

4. If you use SQL Server 2012, you need to update ODBC Data Source configuration to use SQL Server Native
Client 10. To do this:
a. Run ODBC Datasource Administrator. To do this, navigate to Start > Control Panel > Administrative
Tools > Data Sources (ODBC).
b. On the System DSN tab, locate the Epicor905 system data source which uses Native Client 11 ODBC
driver.
c. Create an ODBC connection. To do this, click Add and select SQL Native Client 10. Click Finish.
d. In the Create a New Data Source to SQL Server window, enter the name of the existing Epicor905 system
data source that you located in step 4.b.
e. Enter the data source description.
f. Click the down arrow to select the SQL server that you want to connect to.
g. Click Finish. A message appears asking if you want to overwrite an existing data source. Click Yes.
10.3 Install Progress OpenEdge
1. Verify that your machine does not have a 64-bit version of OpenEdge installed.
2. Install the 32-bit version of Progress OpenEdge 10.2.A. See the Install Progress OpenEdge 10.2A section
of this document for instructions.
Note The OpenEdge 10.2A Service Pack and Service Pack Hot Fix are also installed.
10.4 Install Epicor 9.05 Client
1. Install the Epicor 9.05 Client. See the Install the Epicor 9.05 Client section of this document for instructions.
You must complete all the steps in that section.
Note During the installation, if this Windows Admin Workstation machine is where you plan to run
the Epicor Admin Tools and Epicor Schema Changes, be sure to select the following check boxes to
create the shortcuts: Epicor Admin Tools and Epicor Schema Change.
Note During the installation, if this Windows Admin Workstation machine will also be used as a
normal Epicor 9.05 client machine, you have the option of also selecting the following check boxes
to create additional shortcuts: Epicor 9.05 and Epicor 9.05 MES.

Chapter 11: Troubleshooting
Use the following section if you need assistance in troubleshooting any installation issues.
11.1 Share the Epicor Folders
Use this section to verify that the folders are shared. Note that if you are using Windows Server 2008, the steps
may be slightly different.
1. Verify that the C:\Epicor\Epicor905 folder is shared. To do this:
a. On the C: drive, navigate to the C:\Epicor folder.
b. Right-click the \Epicor\Epicor905 folder icon and select Sharing and Security.
c. Select the option to Share this Folder. Epicor905 displays as the default share name. Do not change
the name. The folder must be named Epicor905.
d. Click the Permissions button. It is recommended that you assign Full Control to the Everyone group.
Click OK to accept the permissions.
e. Click the Security tab. It is recommended that you assign read-only permissions to Users. Read-only
includes Read & Execute, List Folder Contents, and Read. Add an Administrator and assign the
Administrator Full Control. Click OK.
2. Verify that the C:\Epicor\EpicorData folder is shared. To do this:
a. On the C: drive, navigate to the C:\Epicor folder.
b. Right-click the C:\Epicor\EpicorData folder icon and select Sharing and Security.
c. Select the option to Share this Folder. EpicorData displays as the default share name.
d. Click the Permissions button. It is recommended that you assign Full Control to each user folder. Click
OK.
e. Click OK to accept the share options.
11.2 Verify Specific Folders are Not Read-Only
Use these steps to verify that the Client, ClientServer and Server folders are not read-only. These folders need to
have write access so that files can be added to them during the installation.
1. Go to the location where your Epicor 9.05 application is installed. For example, go to C:\Epicor\Epicor905.
2. Right-click on the Client folder. Select Properties.
3. On the General tab, clear the Read Only check box. Click Apply.
4. The Confirm Attribute Changes dialog appears. The Apply changes to this folder, subfolders and
files option is selected by default. Click OK. Click OK to exit the Client Properties folder.

5. Repeat the previous steps for the ClientServer and Server folders.
Note For 64-bit installations, the ClientServer folder is located in the \Epicor\Epicor905\32 directory.
11.3 Review Configuration File Settings
The mfgsys file defines the main settings for server installation and each client installation. If the .exe file can see
the default.mfgsys file, the application is ready to run. The configuration file is an XML file that contains syntax
understood by the application. System Administrators use it to control various installations.
To modify the configuration file settings in the default.mfgsys file, refer to the Application Tools > Configuration
Settings File > Configuration Settings File section within Application Help.
Note You can also create a different configuration file and then have each workstation launch with this
alternate file. You can then keep the original file while you experiment with different configurations. Create
the alternate configuration, and then define the /CONFIG run time argument on each workstation.
11.4 Verify Time Synchronization on Client and Server
If you received the error message "The authorization credential is expired", use these steps to verify the time
synchronization of your client and server. You may receive this error while performing a search from a client
workstation to the Epicor Web Access server if the time values that are set on the client and server are not accurate
according to the time zone.
1. On the client workstation, go to Start > Control Panel > Date and Time. Verify that the time is accurate
according to the time zone.
2. On the Epicor Web Access server, go to Start > Control Panel > Date and Time. Verify that the time is
accurate according to the time zone.
11.5 Known Issue with Turkish Format Culture Display

When the Format Culture is set to Turkish, several items display incorrectly and you may get an unhandled
exception error that causes the application to become unstable. To resolve the unhandled exception error, you
can set the Format Culture to German in order to use the formats for that language instead. To do this:
1. Open your Epicor 9.05 application. Navigate to System Management > Company Maintenance > User.
2. Enter or browse for a specific User.
3. In the Format Culture field, select German. Keep the Language set to Turkish.
4. Save the record. Close the application.

Note While this change resolves most of the issues, it also causes a minor issue with a Crystal Reports
tool bar that cannot be resolved. The reports are now formatted and displayed correctly in Turkish
culture, but the issue may appear in the report tool bar where several icons and text are displayed in
German.

11.6 Configure Environments for Test and Pilot

During the installation of Epicor 9.05, the only two environments completely configured by the installation are
under ports 9401 and 9411 for your main production and Train environments. Use the following steps if you
want to configure additional environments, such as Test and Pilot. The Pilot and Test environments are installed
(including the .ini files, .pf files, and shortcuts), but the schema (for SQL installations) and databases are not
restored. Note that these steps are different for Progress and SQL environments.
1. Copy the files from Epicor905\db\newdb\backup to Epicor905\db\pilot and Epicor905\db\newdb\test.

Note that an empty attachable SQL database or new SQL script database can be found in the same directory
as the schema.
2. Restore the Schema holder backup file. To do this:
a. Navigate to Start > Programs > OpenEdge 10.2A > Proenv.
b. Go to the folder where your schema holder is located. For example, go to \Epicor905\db\newdb\backup.
c. At the prompt type one of the following commands, based on your environment:
• SQL (32 bit): prorest mfgsyssh mfgsyssh32.bkup
• SQL (64 bit): prorest mfgsyssh mfgsyssh64.bkup
• SQL Unicode (32 bit): prorest mfgsyssh mfgsyssh32U.bkup
• SQL Unicode (64 bit): prorest mfgsyssh mfgsyssh64U.bkup
3. Start your Application Server.
4. Restore SQL database. The SQL Script used to create an empty database is located in \db\newdb\backup.
The SQL script name to create empty database name may vary based on which Epicor 9.05 version is being
installed.
5. Create ODBC connections or verify they exist for EpicorPilot905 and EpicorTest905.
6. Start Schema database holder.
7. Run Schema Change tool to update the empty database and to verify the empty database is at the correct
version.
8. Run Admin Tools. Verify login form appears.
9. Start your Application Server.
10. Log into the Administration console.
a. Create Environment connection. For example, create EpicorPilot905 or EpicorTest905
b. Apply the license.
c. Create your company.
11. Run Admin Tools to update the empty database with beginning data.
12. Log into your Epicor application.

11.7 Error Accessing Menu Maintenance

When you launch the Menu Maintenance program, you may receive an error "Access to path is denied". To
avoid the error, verify you run the Epicor Client as Administrator. To do this, right-click the Epicor client icon and
select the Run as Administrator option. Navigate to System Management > Utilities > Menu Maintenance.
11.8 Progress Client Has Stopped Working

During an upgrade to Epicor 9.05.70x, if you receive the error message that your "Progress client has stopped
working", you must use the OpenEdge Explorer tool to stop your database. You received this error because the
database is marked as Read-Only, but the database is running.
11.9 Change or Uninstall Epicor 9.05 Application
Use these steps to add or remove programs and features related to your Epicor 9.05 application. This section
also includes steps to uninstall the Epicor 9.05 application from your server or Epicor 9.05 client from your
workstation.
Note It is highly recommended that you create a backup of all your important files, such as your databases,
prior to uninstalling the application.
11.9.1 Add or Remove Programs and Features
Use these instructions if you want to add or remove programs or features that are related to your Epicor 9.05
application.
1. Navigate to Control Panel > Programs and Features..
2. Right-click on Epicor 9.05 (database) and select Change from the menu. The Install Wizard opens the
Epicor 9.05 installation menu. The dialog may look similar to the following:

3. The Add / Remove Features option is selected by default. Click Next.
4. On the Select Features dialog, select the features you want to add or remove. Click Next. The Epicor 9.05
features you selected are added or removed.
Note When adding features, the components for the Utilities, Server Add-On, and Web Add-On
features are delivered as executable files to a folder on your server. The components are delivered,
but they are not installed. After your installation, you can use the Supplemental Installation section
of this guide for instructions on installing these additional features and programs.
5. If prompted, click Finish.
11.9.2 Repair or Reinstall Epicor 9.05 Application
The Epicor 9.05 installation menu includes an option to Repair / Reinstall the Epicor 9.05 application. While this
is a standard option available in an install wizard process, it is not recommended that you use this option with
your Epicor 9.05 application due to customizations or configuration settings unique to your system.
11.9.3 Uninstall Epicor 9.05 Application
Use these instructions if you need to uninstall the Epicor 9.05 application from your server. It is highly recommended
that you create a backup of all your important folders and files, such as the Epicor905 folder and subfolders
(which includes your databases), prior to uninstalling the application. It is also recommended that you store this
backup in a safe location. Note that the uninstall process deletes everything in the Epicor905 folder. Do not store
your backup in the Epicor905 folder.

1. Create a backup of your important folders and files. For example, at a minimum, create a backup of the
following folders:
• Epicor905\db
• Epicor905\custom
• Epicor905\csg
• Epicor905\server\reports
• Oe102a\properties
2. Navigate to Control Panel > Programs and Features.
3. Right-click on Epicor 9.05 (database) and select Uninstall from the menu. The dialog may look similar to
the following:
4. The Uninstall Epicor 9.05 option is selected by default. Click Next.
5. On the Ready to Update Your System dialog, click Next. The Epicor 9.05 application is uninstalled.
6. If prompted, click Finish.
7. The uninstall process may not delete files that were added or updated since the initial installation. To complete
the uninstall process, go to the location where you initially installed the Epicor application. For example, go
to \Epicor\Epicor905. Manually delete any existing files and folders.

11.9.4 Uninstall Epicor 9.05 Client
Use these instructions if you need to uninstall the Epicor 9.05 client from your workstation.
1. Close all Epicor 9.05 client instances that are running on your workstation.
2. Navigate to Control Panel > Programs and Features.
3. Right-click on Epicor 9.05 Client and select Uninstall from the menu.
4. In the Previous Install dialog, the Update or Uninstall a single instance option is selected by default. Use
the drop-down menu to select the instance. Click Next.
5. On the Shortcut Creation dialog, select the Uninstall this client check box. Click Next.
6. On the Confirmation dialog, click Yes. The Epicor 9.05 client is uninstalled.
7. When it is completed, click Finish.
8. The client uninstall process may not delete all the files that were added or updated since the initial installation.
To complete the uninstall process, go to the location where you initially installed the Epicor client. For
example, go to \Epicor905\Client. Manually delete any existing files and folders.

Epicor 9.05 Installation Guide Supplemental Installations
Part IV: Supplemental Installations

Use the following information to help complete your Epicor 9.05 application set up. Complete the sections
appropriate for the components and products you intend to use.
Navigate to Epicor 9 > Version 9.05.700.
2. In the Available Downloads list, download the Supplemental Installation Guide. Note that this guide is the
same for all platforms.
3. Use the Supplemental Installation Guide to install the components and products you intend to use with your
Epicor 9.05 application.
Supplemental installations can include the following:

• Configure 64-Bit Environment (Windows 2008)
• Install Epicor Administration Console
• Install BPM Server
• Install Epicor Enterprise Search
• Install Embedded Education Courses
• Install Epicor Information Worker
• Install Epicor DB Replication
• Install Epicor SQL Server Reporting (SSRS)
• Install Epicor Mobile Access
• Install Epicor Sharepoint Publisher
• Install and Deploy Epicor Web Access
• Reinstall Epicor Web Services
• Reinstall Country Specific Functionality (CSF)
• Upgrade to Service Connect 9.05
• Upgrade to Epicor Portal 9.05
• Upgrade to Infragistics NetAdvantage
• Install SonicMQ
• Install Progress OpenEdge 10.2A (Advanced/Manual)
• Configure Epicor Online Help
• Set Up Multi-Company Functionality

Supplemental Installations Epicor 9.05 Installation Guide

Additional information is available at the Education and
Documentation areas of the EPICweb Customer Portal. To access
this site, you need a Site ID and an EPICweb account. To create an
account, go to http://support.epicor.com.

Epicor 9.05 Installation Guide: New Install 9.05.702 - SQL

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Epicor 9.05 Installation Guide: New Install 9.05.702 - SQL

Hochgeladen von

Copyright:

Verfügbare Formate

Epicor 9.

New Install 9.05.702 - SQL

Part I: Getting Started......................................................................................7

Chapter 1: Verify Prerequisites...................................................................7

Chapter 2: Perform Pre-Installation Steps...............................................15

Part II: Installation..........................................................................................18

Chapter 3: Install Progress OpenEdge.....................................................18

Chapter 4: Install or Upgrade the Epicor 9.05 Application.....................22

Part III: Post-Installation.................................................................................29

New Install 9.05.702 - SQL 3

Chapter 5: Configure Application Server.................................................29

Chapter 6: Prepare Your Database...........................................................39

Chapter 7: Install Epicor 9.05 Client on a Workstation...........................44

Chapter 8: Log in the First Time...............................................................47

Chapter 9: Restore Demonstration Database..........................................49

4 New Install 9.05.702 - SQL

9.2 Verify Prerequisites...........................................................................................................................49

Chapter 10: Configure Windows Admin Workstation............................54

Chapter 11: Troubleshooting....................................................................56

Part IV: Supplemental Installations...............................................................63

New Install 9.05.702 - SQL 5

6 New Install 9.05.702 - SQL

Part I: Getting Started

Chapter 1: Verify Prerequisites

1.1 Verify Access to EPICweb

1. Verify you have Internet access at your workstation.

1.2 Verify Epicor 9.05 Install Guide Version

2. Navigate to Epicor 9 > Version 9.05.700.

New Install 9.05.702 - SQL 7

1.3 Review Epicor 9.05 Functionality

1.4 Review Software Requirements

8 New Install 9.05.702 - SQL

1.5 Verify SQL Server Installation

New Install 9.05.702 - SQL 9

a. For the Application Server, do the following:

b. For the SQL Server, do the following:

1.6 Review Hardware Requirements

1.6.1 Review Hardware Sizing Guide

2. Navigate to Utilities > Hardware Sizing Guide.

10 New Install 9.05.702 - SQL

5. Open the Epicor9SizingSpreadsheet.9057xx.Template.xls file. Review the entire template, including

6. Use the two documents to assist in understanding your hardware requirements.

1.6.2 Review Hardware Scenarios

SQL Config #1: Two Servers

New Install 9.05.702 - SQL 11

SQL Config #2: Three Servers

12 New Install 9.05.702 - SQL

SQL Config #3: Four or More Servers

1.7 Verify Epicor AEP Requirements

New Install 9.05.702 - SQL 13

1.8 Verify Windows Server 2008 Compatibility

1.9 Verify Temporary Files Do Not Exist

2. In the Temp folder and subfolders, delete the following:

14 New Install 9.05.702 - SQL

Chapter 2: Perform Pre-Installation Steps

2.1 Configure Application Server Role

1. On the server, open Server Manager. Select the Roles node.

3. Click Add Roles and click Next.

4. On the Select Server Roles dialog, do the following:

New Install 9.05.702 - SQL 15

2.2 Disable Error Reporting

Using Windows Server 2008 R2

1. Navigate to Start > Control Panel > System and Security.