Epicor9 PatchGuide 904506A

Epicor 9 Patch
Installation Guide
Patch 9.04.506A
About this Guide
This manual is provided for informational purposes only. Epicor Software Corporation makes no representations or
warranties with respect to the contents of this manual and specifically disclaims any and all implied warranties
including, but not limited to, merchantability and fitness for any particular purpose.
This manual is subject to change without notice. The contents of this manual are believed to be current and accurate
as of its date of publication. Changes to this manual between reprintings and other important information about the
software products 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.
Disclaimer
© Copyright 2010 Epicor Software Corporation. Epicor is a registered trademark of Epicor Software Corporation.
All other trademarks are the property of their respective owners and are acknowledged. Palm and Palm OS are
trademarks of Palm, Crystal Reports Application Server 9.0 and Crystal Reports Version 9 .NET Server are
trademarks of Crystal, Microsoft Internet Information Server 5.0, Microsoft Message Queue 3.0, WinCE, Microsoft
Project, Microsoft .NET Framework 1.1, Windows 2003 Server, Windows NT, Windows 2000, Windows XP,
Windows 98, Windows ME, Internet Explorer 6.0, Microsoft Office 2000, Microsoft SQL Server 2000, Microsoft
SQL Server 2005, Microsoft XML Core Services 4.0, Microsoft SQLXML 3.0, Soap Toolkit 2.0, Microsoft Outlook,
Microsoft Sharepoint Server, Microsoft Visual Studio Enterprise Architect are all trademarks of Microsoft, McAfee
Virus Scan is a trademark of McAfee, Intel Pentium III is a trademark of Intel and Adobe Acrobat Reader 5.0 is a
trademark of Adobe.
Published in the United States of America. No part of this publication may be reproduced in any form without the
prior written consent of Epicor Software Corporation.
March 2010
Page 2 of 53 Epicor 9 Patch Installation Guide: Patch 9.04.506A

Table of Contents
1. Pre-Installation Steps .................................................................................................. Page 5
2. Install Progress OpenEdge 10.1C Service Pack and Hot Fix ..................................... Page 6
3. Install Epicor 9 Patch for Windows ............................................................................ Page 7
4. Install Epicor 9 Patch for Linux/UNIX....................................................................... Page 9
5. Post-Installation Steps............................................................................................... Page 11
6. Log in the First Time ................................................................................................ Page 16
7. Upgrade Optional Installations ................................................................................. Page 18
8. Re-Install and License Embedded Education Content Pack..................................... Page 40
9. Restore Demonstration Database .............................................................................. Page 44
10. Review Change List ................................................................................................ Page 49

Welcome and Introduction
Welcome to the Epicor 9.04 Service Pack / Patch Installation Guide. Use these
instructions to install the latest service pack or patch. A Service Pack is cumulative. It
includes an entire series of changes, resolved issues and enhancements that have been
completed by the Development team. A Patch is as addition to the Service Pack. Your
system must have the latest Service Pack installed before you can install the Patch.
Use the following graphic to review the installation process flow:
Install the latest

Service Pack and/or Patch
onto my Epicor 9
application
Pre-Installation Steps
Install OpenEdge
Service Pack and Hot Fix
- Download Service Pack and/or Patch files

- Stop the AppServers
Install Epicor 9
- Install Epicor 9 Service Pack
Service Pack and / or Patch
- Install Epicor 9 Patch (if available)
- Install Help Content Pack (if available)
- Convert Your Data

- Verify SQL Performance Enhancing Scripts
- Verify Custom Client MFGSYS Files
Post-Installation Steps
- Copy WebServices Folder
- Reinstall Web Services
- Restart AppServers
- Import Posting (Booking) Rules for Extended

Log in the First Time - Review Blocked Standard Posting Rules
- Test BPM upgrade
- Configure 64-Bit Environments

- Install Crystal Rpts Runtime/Embedded Server
- Upgrade Epicor Admin Console
- Upgrade Epicor Web Access
Upgrade Optional Installations
- Upgrade Epicor Replication Server
- Upgrade Epicor Enterprise Search
- Upgrade Epicor Education Courses
- Restore Demonstration Database
Review Change List
Epicor 9 with
latest SP and/or Patch
is ready!

Pre-Installation Steps
1. Pre-Installation Steps
Use these instructions to complete steps before you begin the actual service pack or
patch installation.
1.1 Review Change List
This release adds changes, resolved issues and enhancements to the Epicor 9.04
application. See the Review Change List section of this document to see the details of
what is included in this service pack or patch.
1.2 Verify Your Epicor Application Version
Your Epicor application version must be 9.04 or higher in order to install this service
pack or patch. If you have not already done so, upgrade to this version.
This release may require a schema change, so please anticipate that this upgrade may
take some time. Also note that if you have Customer Connect, you will need a service
pack for each of those products in order to upgrade the database.
Service packs may recreate SQL indexes. This logic may delete custom indexes that
you have created. It is recommended that you save them and recreate custom indexes
as needed.
1.3 Back Up Database and System
Database and system backups are very important. Do not skip this step!
1. Create a backup of all your databases. In a standard installation, the files are
located in the \Epicor\Epicor904 directory.
2. Create a backup of your Epicor application. The files are located in the \oe101c and
\Epicor directories.
1.4 Back Up Customized Reports
If you are using customized Crystal Reports, the report files must be backed up. These
backups are very important. Do not skip this step!
1. Go to your Crystal Reports directory.
2. Save the reports as file names different from the standard report names.

Install Progress OpenEdge 10.1C Service Pack and Hot Fix
1.5 Test Customizations
We strongly recommend that you use a test environment to test all customizations to
verify that the customizations are working properly in the new environment before
installing them onto a live system.
1. Create a test environment.
2. Test all customizations, including Business Logic, User Interface, and Report.
3. Use the Report Data Definition program to add fields to the Report Dataset for
customized forms and reports. See the online help for more information on using
this program.
1.6 Test Product Configurator
If you use Product Configurator functionality, we recommend that you perform

additional tests verifying your configurations before installing in your live
environment. If you do not use Product Configurator, your regular acceptance tests in
a test environment should be performed.
1. Create a test environment.
2. Test all Product Configurator configurations.
2. Install Progress OpenEdge 10.1C Service Pack and Hot Fix
Use the following instructions to install the latest Progress OpenEdge service pack and
hot fix files. Note that the Progress OpenEdge service pack and hot fix files are
cumulative releases of the preceding service packs and hot fixes.
Note! Do not skip this step!
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 OpenEdge / Version 10.1C.
3. Download and use the OpenEdge Service Pack Install Guide to install the
OpenEdge Service Pack.
4. Download and use the OpenEdge Service Pack Hot Fix Install Guide to install the
OpenEdge Service Pack Hot Fix.

Install Epicor 9 Patch for Windows
3. Install Epicor 9 Patch for Windows
If you use a Windows operating system with a Progress, SQL or SQL Unicode
database, use these instructions to install the Epicor 9 service pack and patch files. In
these instructions, drive C: refers to a local hard drive. If your local hard drive is
assigned to a different letter, substitute that letter during these instructions.
Some of the instructions are based on using Windows Server 2003. If you use a
different operating system, such as Windows Server 2008, you may need to make slight
adjustments to the instructions.
3.1 Download Epicor 9 Patch Files
Use the following instructions to download the appropriate Epicor 9 patch files based
on your database.
2. Navigate to Epicor 9 / Version 9.04.500.
3. Download the latest Epicor 9 patch related to this installation. For example,
download one of the following files, based on your environment:
- Progress on Windows (32 bit): PA904506a-P.EXE

- SQL Server: PA904506a-S.EXE
- SQL Unicode: PA904506a-SU.EXE
4. Download the latest Epicor 9 application Help Content Pack file onto your
machine. For example, download the Help904506A.EXE file.
3.2 Stop the AppServers
Use the following instructions to stop the AppServers. Do not skip this step!
1. Verify all users log out of the system before stopping the AppServers.
2. Select Start — Programs — OpenEdge 10.1C — Progress Explorer Tool. Use

the Progress Explorer Tool to stop the following functions in order:
* Stop all the Appservers.

* Stop all the OpenEdge databases.

Install Epicor 9 Patch for Windows
3.3 Install Latest Epicor 9 Patch on the Server
Use these steps to install the latest Epicor 9 patch, if available, on your system.
1. Go to the directory where you downloaded the latest patch file.
2. Double-click on the file to run it.
3. A Welcome window appears. Click Next.
4. A confirmation window appears. Click Yes to proceed.
5. Enter the directory where your program files are located. Click Next.
6. Enter the directory where your OpenEdge files are located. Click Next.
7. You may be prompted to verify your server name, operating system or database
type. If prompted, select the appropriate option and click Next.
8. The Start Installation window appears. Click Next.
9. A message appears, stating that the application patch installation is complete.

Click Finished.
The Epicor application patch is now installed.
Note! If you are an existing customer, you will complete the post-installation steps
using the Patch guide. If you are a new customer, you will complete the post-
installation steps using the Epicor 9 Installation Guide.
3.4 Install Help Content Pack
Use the following instructions to install the Help Content Pack. This file contains the
updated online help system available with this Epicor 9 patch.
1. Go to the directory where you downloaded the latest Help Content Pack file.
6. A completion message appears. Click Finish.

Install Epicor 9 Patch for Linux/UNIX
The Help Content Pack is now installe
4. Install Epicor 9 Patch for Linux/UNIX
If you use a Linux/UNIX operating system, use these instructions to install the Epicor
9 patch files. If you do not use Linux/UNIX, continue to the Post-Installation section.
4.1 Download Epicor 9 Patch Files
Use the following instructions to download the appropriate Epicor 9 patch files based
on your database. The files must be downloaded to the Linux/UNIX server in the
Epicor904 folder.
2. Navigate to Epicor 9 / Version 9.04.500.
3. Download the latest Epicor 9 patch related to this installation. For example,
download one of the following files, based on your environment:
- Linux (32 bit): PA904506xL32.bin

- Linux (64 bit): PA904506xL64.bin
- UNIX HPUX 11 (32 bit): PA904506xU32.bin
- UNIX HPUX 11 (64 bit): PA904506xU64.bin
- UNIX Itanium (64 bit): PA904506xUI64.bin
Note! After selecting the .bin file, the File Download page opens. Right-click on the
Download Now link and select Save Target As. Browse to select the location.
Click Save. Close the dialog if needed.
4. Download the latest Epicor 9 application Help Content Pack file onto your
machine. For example, download the Help904506A.EXE file.
4.2 Stop the AppServers
Use the following instructions to stop the AppServers on the Windows workstation. Do
not skip this step!
1. Verify all users log out of the system before stopping the AppServers.
Epicor 9 Patch Installation Guide: Patch 9.04.506A Page 9 of 53

Install Epicor 9 Patch for Linux/UNIX

the Progress Explorer Tool to stop the following functions in order:
* Stop all the Appservers.

* Stop all the OpenEdge databases.
4.3 Install Latest Epicor 9 Patch on the Server
Use these steps to install the latest Epicor 9 patch, if available, on your system.
1. Log into your Linux/UNIX server as an Administrator.
2. Navigate to the directory where you downloaded the latest patch file. For example,
go to the \Epicor904 folder.
3. Type “./<filename.bin>” where <filename.bin> is the name of the patch file you
downloaded. Press Enter to start the installation. An Initializing Wizard message
appears.
4. A Welcome window appears. Press ENTER to accept the default to continue.
5. Type in the directory path where your OpenEdge files are located, or press ENTER
to accept the default path.
6. Type in the directory path where your Epicor program files are located, or press
ENTER to accept the default path.
7. Press ENTER to accept the default to continue.
8. A Summary window appears. Verify your directory path to your Epicor program
files. Press ENTER to accept the default.
9. Installation messages appear. When successfully installed, a message reminds you

to run the CZI.EXE file from your Admin Workstation. You will do this in the next
step. Press ENTER to finish.
10. On your Windows Admin workstation, navigate to the Epicor904 folder on the
Linux/UNIX server. For example, go to the \\<server>\Epicor904 folder.
11. Double-click the CZI.EXE file that is located in that folder.
12. The Welcome screen appears. Click Next.
13. Click Browse to enter the location of the Epicor904 folder on the Linux/UNIX
server. For example, enter \\<server>\Epicor904. Click OK. Click Next.
Note! Be sure to use the UNC path and not a mapped drive.

14. The Start Installation window appears. Click Next. The process may run for
several minutes.
15. After the Finished window appears, click Finished.
The Epicor application patch is now installed.
Note! If you are an existing customer, you will complete the post-installation steps
using the Patch guide. If you are a new customer, you will complete the post-
installation steps using the Epicor 9 Installation Guide.
4.4 Install Help Content Pack
Use the following steps to install the Help Content Pack. This file contains the updated
online help system available with this Epicor 9 patch.
1. Go to the directory where you downloaded the latest Help Content Pack file.
6. A completion message appears. Click Finish.

The Help Content Pack is now installed.
5. Post-Installation Steps
Use the following instructions after the service pack installation.
5.1 Convert Your Data
Use these instructions to run the mandatory data conversions.
1. Restart the database you wish to upgrade. To do this, select Start — Programs —
OpenEdge 10.1C — Progress Explorer Tool. Use the Progress Explorer Tool to
start the database.
Note! Do not restart Appservers at this time.
2. On the server, open the Epicor Admin Tools program. To do this, navigate to Start
— Programs — Epicor Software — Epicor 9.04 — Epicor Admin Tools.

3. Login with a valid User Id and Password. Note that the user must have Security
Manager rights.
4. At the prompt for automatic mandatory conversions, click Yes. Mandatory

conversion programs run.
5. If you want to verify that the mandatory conversions completed successfully,

verify that the database conversion date is the correct date.
- For example, Open Epicor Admin Tools in single-user mode. Verify the date
that program number 100 (Update Menu/Security) was run. If the date does not
reflect the correct date, you need to run the conversion program manually. To
run the program manually, highlight the conversion program and select
Conversion - Run Conversion Program. Click Yes to confirm.
- Repeat these steps for each mandatory program that did not complete
successfully, including 130, 140, 150, and 160.
5.2 Verify SQL Performance Enhancing Scripts Installed
If you use SQL or SQL Unicode, use the following steps to verify that each of the
following SQL performance script has been properly applied:
* 904-500DF.sql
* Epicor.9045XX.alter.index.allow_page_locks.sql
* Unique_Index.9045XX.sql
These scripts may need to be run against your database to enhance the performance.
Verify Script: 904-500DF
If the script hasn’t been applied, the “SQL Scripts need to be run” message may appear
when you try to log into your Epicor application.
1. To test that the script has been applied, open SQL Studio and click on your
database to select it.
- Expand the nodes: <database>/ Programmability / Functions / Scalar-

Valued Functions.
- If the “dbo.StringTime” query exists, your SQL script was properly applied.
You can skip to the next verification. If it does not exist, continue with step 2.
2. Click on your database to select it.
3. Click the New Query button. A query window opens.

4. Go to the location where your SQL scripts are located. On a standard installation,
the SQL scripts are located in \Epicor Software\Epicor904\ClientServer\db\SQL.
5. Click on the 904-500DF.sql file to select it. Drag and drop the file into the open
query window. Click the Execute button. This process may take several minutes.
The message “Command completed successfully” displays.
- Expand the nodes: <database>/ Programmability / Functions / Scalar-

Valued Functions.
- The “dbo.StringTime” query should now be listed.
Verify Script: Epicor.9045XX.alter.index.allow_page_locks.sql
- Expand the nodes: <database>/ Tables / dbo.PDMMap / Indexes / PDM.

- Right-click on PDM and select Properties.
- Click Options. If the Use page locks when accessing the index check box is
clear, your SQL script was properly applied. You can skip to the next
verification. If the check box is selected, continue with step 2.
5. Click on the Epicor.9045XX.alter.index.allow_page_locks.sql file to select it.

Drag and drop the file into the open query window. Click the Execute button. This
process may take several minutes. The message “Command completed
successfully” displays.
- Expand the nodes: <database>/ Tables / dbo.PDMMap / Indexes / PDM.

- Right-click on PDM and select Properties.
- Click Options. The Use page locks when accessing the index check box should
now be clear.

Verify Script: Unique_Index.9045XX.sql
1. To test that your SQL script has been applied, open SQL Studio and click on your
- Expand the following nodes: <database>/ Tables / dbo.abccode / Indexes /

abccode#_#progress_recid.
- Right-click on abccode#_#progress_recid and select Properties.
- Click Options. If the Ignore duplicate values check box is clear, your SQL
script was applied properly. You can skip to the next verification. If the check
box is selected, continue with step 2.
5. Click on the Unique_Index.9045XX.sql file to select it. Drag and drop the file into
the open query window. Click the Execute button. This process may take several
minutes. The message “Command completed successfully” displays.
- Expand the following nodes: <database>/ Tables / dbo.abccode / Indexes /

abccode#_#progress_recid.
- Right-click on abccode#_#progress_recid and select Properties.
- Click Options. The Ignore duplicate values check box should now be clear.
7. Close SQL Studio.
5.3 Update Custom Client MFGSYS Files
Use the following instructions to update customized .mfgsys files, if you have
customized .mfgsys files.
1. Double-click the clientzipinstaller.exe file. The default location is

\Epicor\Epicor904\clientzipinstaller.
2. Enter the file path location of the customized .mfgsys file.

By default, the deploymentServer path from the default .mfgsys file is used as the
location of the client zip file. Enter a specific location if you want to install the
client zip file from a different location.
3. You can review changes to the configuration setting files by using the Config file
editor. Select the check boxes for the mfgsys files you want to review.
4. Click Finish. The Config file editor appears, prompting you to view changes that
in the config settings for each mfgsys file that was checked. You can update the
settings as necessary.
5. To accept changes in the Config file editor, click Close. The configuration files are
updated so that they are current, ready to accept the service pack.
5.4 Copy WebServices Folder
If you use Service Connect, and it is installed on a separate server other than your
Epicor application server, use these steps to copy a folder to the Service Connect server.
These steps must be completed each time a Service Pack is installed.
1. On the server where your Epicor application is installed, copy the \WebServices
folder. In a standard installation, the WebServices folder is located at \Epicor
Software\Epicor904. Copy only this folder; do not copy any other folders.
2. Navigate to the server where Service Connect is installed. Paste the \WebServices
folder into a directory of your choice.
5.5 Reinstall Web Services
Use these steps to reinstall your Web Services if your server is also used as a web server
to interface with the Epicor application using Web Services. For example, you need to
reinstall your Web Services if you use Service Connect, AQM, PLM, Epicor Portal or
Information Worker. Instructions for reinstalling your Web Services are located in the
WebServices directory. If your system is installed in \Epicor Software\Epicor904, the
instructions are in \Epicor Software\Epicor904\WebServices.
1. Go to the WebServices directory.
2. Run the WS-Configuration[.Net 2.0 Edition].exe program.
3. Select the Reinstall All check box. Click Update Site.
5.6 Restart the AppServers
Use these instructions to restart the AppServers.

Log in the First Time
1. Use the Progress Explorer Tool to restart the AppServers.
2. Verify that they are running before starting the client.
6. Log in the First Time
Use the following steps to verify and test your Epicor 9 application upgrades the first
time you log in.
6.1 Import Posting (Booking) Rules for Extended Rules
Use these steps to import your posting rules if you use Extended Rules. If you only use
standard rules, this step has already been automatically completed for you when you
converted your data.
1. Open the Epicor 9 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 Extended posting rules folder.
For example, go to the following:
* Extended rules: \\<servername>\Epicor904\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.

Log in the First Time
Note! Newly created revisions are automatically set to Active in the current company
only. In other companies, you need to update the status manually. In order to
make changes, your User Id must have access to the company.
10. Click OK to begin the import.
11. You may be prompted with the Book Mapping dialog. Select the book identifier
you previously defined from the Map Book selection list. If you want to map the
selected book identifier to all transaction types, select the Use for all transaction
types check box. Click OK.
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.
6.2 Review Blocked Standard Posting Rules (if any)
Use the following steps to review any standard posting rules that were not updated
during the conversion. If you were not prompted with an Information message during
the conversion, you can skip this step.
1. Get the screen capture of the Information message that you took during the
conversion process.
2. Select Financial Management - General Ledger - Setup - GL Transaction

Type.
3. Search and select a transaction type that is listed on the Information message.
4. In the Tree View area, select a revision. From the Actions menu, select Change
Log Menu. Review the list of revisions that were added and blocked during the
last conversion process.
5. If a Revision you want is listed as Blocked, you can change it to Active. To do this:
- Click on the Revision to select it.

- From the Status drop-down list, select Active.
- Click Save from the standard toolbar.
6. Repeat the above step for each Revision listed on the Information message.
Note! If you have multiple companies, the Information message may list the same
blocked transaction type for each company. You must review the blocked
posting rules for each company where you have access.

6.3 Test Business Process Management (BPM) Upgrade
Use these instructions to verify that your BPM methods have upgraded successfully. If
a BPM procedure has the Enabled check box selected, it automatically upgrades to
Epicor 9. But, if any procedures run custom 4GL code, you need to verify that this code
compiles properly.
Note! You must use these steps to properly upgrade your BPM directives. You cannot
just copy the BPM directives in the Epicor904\BPM\bo directory to another
directory. You also cannot keep the BPM directives in the current folder, they
must be properly upgraded to a new location.
1. Launch the Method Directives program.
2. Use the Method Search program to search for any Outdated Directives.
3. Open an outdated directive.
4. Click on the Actions menu and select Validate Method.
5. If a directive is outdated, the Pre-Processing, Base Processing and/or Post

Processing sheets display the Outdated icon on each directive's Detail sheet.
6. Research how to update each outdated directive to make it compatible with Epicor
9. This may involve updating your custom 4GL code to reflect the new schema.
7. Repeat these steps for all the outdated directives that you find.
7. Upgrade Optional Installations
Use the following steps to upgrade optional installations.
7.1 Configure 64-Bit Environments (If needed)
If you use a 64-bit environment, you must enable the 32-bit version of ASP.NET 2.0 in
the 64-bit environment in order to install and deploy web based products, such as
Epicor Web Access and the Embedded Education Courses.
Note! When using a 64-bit server, you may encounter login issues when using Internet
Explorer 64-bit. Epicor Web Access allows users to enter login credentials, but
the application may not start. To resolve this security issue, use Internet
Explorer to add the Epicor Web Access site to the server’s trusted site list.

Windows 2008 64-bit Environment
If you have installed a Windows 2008 (64-bit version) environment, use these steps to
enable the 32-bit version of ASP.NET 2.0 in a Windows 2008 64-bit environment.
1. Go to Internet Information Services (IIS) Manager.
2. From the Application Pools node, select DefaultAppPool.
3. From the Action menu, select Advanced Settings.
4. Select the Enable 32-Bit Application check box.
5. Restart the Application Pool.
Windows 2003 64-bit Environment
If you have installed a Windows 2003 (64-bit version) environment and you are running
IIS 6, use these steps to enable the 32-bit version of ASP.NET 2.0 in a Windows 2003
64-bit environment.
1. From the Start menu, select Run. Type cmd and click OK.
2. Type the following command to uninstall all versions of ASP.Net:

%SYSTEMROOT%\Microsoft.NET\Framework64\v2.0.50727\aspnet_regiis -ua
3. Type the following command to enable the 32-bit mode:

cscript %SYSTEMDRIVE%\inetpub\adminscripts\adsutil.vbs SET W3SVC/AppPools/
Enable32bitAppOnWin64 1
4. Type the following command to install and register the version of ASP.NET 2.0
(32-bit) and to install the script maps at the IIS root and under:
%SYSTEMROOT%\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis -i
5. Run iisreset.
6. Open the Internet Information Services Manager.
7. Expand the server node. Select the Web Service Extensions folder in the tree view.
8. In the WS Extensions window, select ASP.Net v2.0.50727 (32 bit). Verify that the
Allow check box is selected.
9. Expand the Default Web Site node in the tree.

10. If you use Embedded Education Courses, right-click on the EpicorEducation

virtual directory and select Properties.
11. On the Virtual Directory tab, click the Configuration button.
12. Select the application extensions for the .htm and .html extensions. Verify that
they are not pointing to the Framework64 directory.
13. If these extensions are not mapped, you must manually add each one separately.
To add the .htm extension, click Add and enter the following:
- Executable:
C:\WINDOWS\microsoft.net\Framework\v2.0.50727\aspnet_isapi.dll
- Extension: .htm
- Verbs: Select All Verbs.
- Click OK.
14. To add the .html extension, click Add and enter the following:
- Executable:
C:\WINDOWS\microsoft.net\Framework\v2.0.50727\aspnet_isapi.dll
- Extension: .html
- Verbs: Select All Verbs.
- Click OK.
7.2 Install Crystal Reports Runtime and Embedded Server
If you use report generation from Epicor Web Access, you must install Crystal Reports
XI R2 Runtime and Crystal Reports XI R2 Embedded Server.
Review Platform Requirements
Use the following to review the specific platform requirements for Crystal Reports XI
R2 Runtime and Crystal Reports XI R2 Embedded Server.
* Crystal Reports XI R2 Embedded Server does not currently support Windows

Server 2008 as a report server platform. If you intend to use Windows Server
2008 (32-bit or 64-bit) as the web server platform for Epicor Web Access, then
the Crystal Reports XI R2 Embedded Server report server must be placed on a
separate server machine running Windows Server 2003 (32-bit or 64-bit).

Install Crystal Reports XI R2. NET 3.0 Runtime
Use the following steps to install the latest version of Crystal Reports XI R2 .Net 3.0
Runtime. This component must be installed on the web server that is hosting Epicor
Web Access. Crystal Reports XI R2 .Net 3.0 Runtime can be installed on Windows
Server 2008.
1. Before you install the latest runtime, you must uninstall any previous version of
Crystal Reports XI R2 .Net 3.0 Runtime.
3. Navigate to Epicor 9 / Version 9.04.500 / Third Party Products / Crystal.
4. Download the latest Crystal Reports Runtime file from EPICweb to your
workstation. For example: Crystal Reports XI R2 .Net 3.0 Runtime SP5.zip.
5. Navigate to the downloaded file. Open the .zip file and extract the contents.
6. Move the extracted files to the report server where the files are to be installed.
7. Navigate to the extracted file folder. Double-click the Setup.exe file.
8. The Crystal wizard Welcome window appears. Click Next.
9. Specify the folder for the installation of Crystal XI R2 .NET 3.0 Runtime, and
select Everyone as the user of the computer. Click Next.
10. A confirmation window appears. Click Next to confirm.
Install Crystal Reports Embedded Server
Use these steps to install the latest version of the Crystal Reports XI R2 Embedded
Server on your server. This component can be installed either on the same server as the
Epicor Web Access forms, or on another server within the trusted domain, if Windows
2003 Server is being used for both Epicor Web Access and Crystal Reports XI R2.
Note! This version of Crystal Reports XI R2 Embedded Server is not compatible with
Microsoft Windows Server 2008 (32-bit or 64-bit) as a report server.
1. Before you install the latest Crystal Reports XI R2 Embedded Server, uninstall any
previous version of Crystal Reports XI R2 Embedded Server.

3. Navigate to Epicor 9 / Version 9.04.500 / Third Party Products / Crystal.
4. Download the latest Crystal Reports Embedded Server file from EPICweb to your
workstation. For example: Crystal Reports XI R2 Embedded Server SP4.zip.
5. Navigate to the downloaded file. Open the .zip file and extract the contents.
6. Move the extracted files to the report server where the file are to be installed.
7. Navigate to the extracted file folder. Double-click the Setup.exe file.
8. The Crystal wizard Welcome window appears. Select the installation language in
the wizard, and review the Installation Guide and Release Notes located in the
extracted files folder.
9. On the Crystal Reports Server Embedded Edition Setup form., click Next.
10. Review the license statement and select to accept it. Click Next.
11. For the Product Keycode, enter your license key. Click Next.
12. Specify the installation folder. Click Next.
13. For the Install Type, select the New checkbox.
14. Click Next to confirm to start the installation. A meter displays the progress.
15. When completed, click Close.
The installation of the Crystal Reports XI R2 Embedded Server is complete.
7.3 Upgrade Epicor Administration Console
Use these steps to upgrade the Epicor Administration Console on your server. The
upgrade process includes uninstalling and then reinstalling your Epicor Administration
Console. These steps must be completed at each Service Pack or Patch release.
Uninstall Epicor Administration Console
1. Uninstall the Epicor Administration Console. To do this, select Start - Control

Panel - Add or Remove Programs.
2. Select Epicor Administration Console and click Remove.

Reinstall Epicor Administration Console
1. Navigate to the directory where your Epicor application is installed. For example,
go to \Epicor Software\Epicor904.
Note! For Linux/UNIX, on your Windows Admin workstation, navigate to the

Epicor904 folder on the Linux/UNIX server. For example, go to
\\<server>\Epicor904.
2. Double-click on the EpicorUtilities.exe file.
3. On the Welcome to the Epicor Utilities Setup wizard, click Next.
4. On the Epicor Utilities Setup dialog, click the Install Administration Console
button to start the installation.
5. On the Welcome dialog, click Next.
6. On the Confirm Installation dialog, click Next. The files are installed.
7. When the installation is complete, click Close.
The Epicor Administration Console is now upgraded.
7.4 Upgrade Epicor Web Access
Use these steps to upgrade your Epicor Web Access. The upgrade process includes
uninstalling and then reinstalling Epicor Web Access. These steps must be completed
at each Service Pack or Patch release. Depending on your server, these steps may take
up to one hour to complete.
Note! It is strongly recommended that you uninstall and then reinstall Epicor Web
Access prior to upgrading. If you run the Epicor Web Access Installer prior to
upgrading, you are prompted with the message "The site: <Site Name> already
exists. Would you like to delete and reinstall the site?" Select Yes. Be aware that
if you select No, the installer will upgrade on top of the existing site, and this
may cause file version errors.
Uninstall and Reinstall Epicor Web Access Utilities 9.0
1. Uninstall Epicor Web Access. To do this, select Start - Control Panel - Add or
Remove Programs. Select Epicor Web Access Utilities 9.0 and click Remove.
2. Reinstall Epicor Web Access Utilities 9.0. To do this, go to the Epicor Web
Access / Epicor Web Access Utilities 9.0 folder. Double-click the Epicor Web
Access Utilities.msi file.

Uninstall Epicor Web Access
1. Uninstall Epicor Web Access. To do this, go to Start - Programs - Epicor

Software - Epicor Administrative Tools - Epicor Web Access Utilities - Epicor
Web Access Uninstaller.
2. Select the EpicorWebAccess check box.
3. Click Uninstall. Click Yes to the warning message.
Note! This process removes all the assemblies from the Global Assembly Cache
(GAC) and can take around 30 minutes, depending on your server.
4. Click Close to exit the window.
Configure Internet Explorer 8 Compatibility
1. If you use Internet Explorer 8, you need to configure Internet Explorer 8 to run in
Internet Explorer 7 compatibility mode. To do this, open Internet Explorer 8.
2. From the Tools menu, select Compatibility View Settings.
3. Add the EWA Server to the list of Internet Explorer 7 Compatible servers.
Note! The default for Internet Explorer 8 specifies all intranet sites as compatible.
4. Click OK to save.
Configure IIS 6 Management Compatibility
1. Configure IIS 6 Management Compatibility for Windows Server 2008 (32-bit and
64-bit version). To do this, in the Programs and Features control panel, select Turn
Windows Features on or off.
2. From Roles - Web Server (IIS), right-click and select Add Role Services.
3. In the Select Role Services window, scroll down to IIS 6 Management

Compatibility, verify that it is selected. If it is not selected, then select it and click
Install.
Reinstall Epicor Web Access
1. Reinstall Epicor Web Access. To do this, navigate to Start - Programs - Epicor

Software - Epicor Administrative Tools - Epicor Web Access Utilities - Epicor
Web Access Installer. The Epicor Web Access Installer windows appears.
2. The Web Setting field values default from the previous installation. Review the
fields and only change the values if necessary.

* Epicor Web Access Site: Your site name.

* Web Forms Package: The location of the EpicorWebAccessForms.zip file,
which stores the files that are related to web forms such aspx, js, and css.
* Web Services Package: The location of the EpicorWebAccessServices.zip
file, which stores the files that are related web services such as asmx, and dll.
* Progress Server: Server name of your Epicor Progress Application Server
(AppServer).
* AppServer Port: The AppServer port number defaults to 3090. Change this
number to identify your primary AppServer port. For example, the Appserver
port for the live database is 9001.
* Optimize Site: Select this check box to improve performance. If selected, the
installer optimizes most of the web service assemblies. If not selected, the
installer installs the web service assemblies in the Bin folder.
Note! Do not select the Optimize Site check box if you have installed Epicor Web
Access on the same server as your Epicor application. Only select this option if
you have installed Epicor Web Access on a different server than your Epicor
application.
* Enable Report: Select this check box if you have Crystal Report XI R2
Embedded Server installed on the same server or on the network. Selection
enables the Report Setting section. Note that this check box is only enabled
when a Crystal Report XI R2 .Net3 Runtime is installed on the server.
* Enable Single Sign On: Select this check box to use Windows authentication
for a single sign on. If it is not successful, it prompts for an EpicorWeb login.
* Report Appserver. The Report Appserver defaults to the name of the
webserver. If the Crystal Report XI R2 Embedded Server is installed on a
different server, change this name to identify the name of the server where it is
installed.
* Other Report Settings: No changes necessary. Accept all field defaults.
3. Click Install.
Note! This process installs all the assemblies to the Global Assembly Cache (GAC)
and can take around 30 minutes, depending on your server.
4. Click OK if prompted regarding multiple .Net versions.
5. Click the red X in the upper right corner to close the installer.
The installation is complete.

Refresh Cache Files on Client Machine
Use the following steps to refresh the cache files on each client machine that runs EWA.
1. Log on to the Epicor Web Access.
2. After the Main Menu appears, press Ctrl-F5 to refresh. This process may take
several minutes.
Assign Resource Folder Properties and Sharing
Use the following steps to assign required properties and sharing to the Resource folder.
1. Navigate to the Epicor Web Access virtual directory. For example, if your Epicor
Web Access was installed to IIS, the default directory would be:
:\inetpub\wwwroot\EWA\Resources
2. Right-click on the Resources folder and select Properties.
3. Click the Security tab. Select the IIS_WPG group from the Group or user names
list.
4. Click the Edit button.
5. Re-select the IIS_WPG group.
6. In the Permissions for IIS_WPG list, select the Modify and Write check boxes in
the Allow column.
Note! The IIS_WPG group now has Allow selected for Modify, Read & Execute, List
Folder Contents, Read, and Write.
7. Click OK until you exit.
8. Right-click on the Resources folder and select Sharing and Security.
9. Select the Share this folder check box. Click OK.
Configure Help System for EWA
Use the following steps to configure your application help system with EWA.
1. Edit the web.config configuration file to use the folder for your web client. To do
this:
- Navigate to the <EWAroot> directory on your workstation.

- Open the web.config file in a text editor, such as Notepad.

- Edit the <helpServer> key line to specify the help folder. For example, the line
would look similar to:
<add key="HelpServer" value="http:/localhost/EpicorWebAccess/Help/" />
2. Copy the entire Help folder from the deployment server to the root of EWA install.
Note! If the HelpServer key is configured with a remote server value, you do not have
to copy the entire Help folder from the deployment server. You only copy the
Help\FieldHelp and Help\HelpLinks folders.
3. To implement server-side search indexes, use the instructions in the following

“ConfigureYour Help System” Appendix section. Be sure to point to the folder
<EWARoot>\Help\ when specifying the EpicorHelp directory path locations.
Configure Embedded Education Courses for EWA
Use the following steps to configure your embedded education courses with EWA.
1. Edit the web.config configuration file to use the folder for your web client. To do
this:
- Navigate to the <EWAroot> directory on your workstation.

- Open the web.config file in a text editor, such as Notepad.
- Edit the <CourseServer> key line to specify the location where the education
courses are installed. For example, if the embedded education courses are
installed on the same server as EWA, the line would look similar to:
<add key="CourseServer" value="http://localhost/EpicorEducation" />
2. Save the web.config file.
Install Full Adobe Reader on Epicor Web Access Client
Use the following steps to install Adobe Reader on your Epicor Web Access client.
Installing the full Adobe Reader installs the appropriate browser add-on that is required
to render and view report .pdf files (from IIS).
1. Go to the Adobe Reader website. The link is: http://get.adobe.com/reader
2. Download the latest version of Adobe Reader.
Configure Epicor Web Access Reporting URL Report Display Feature
If you use Windows Server 2003 (32 or 64) or Windows Server 2008 (32 or 64) for your
web server you must use these steps to configure the Epicor Web Access report display
feature. You need to configure both PDF and XLS report formats.

Crystal Reports XI R2 does not currently support Windows Server 2008 as a report
server platform. If you intend to use Windows Server 2008 (32-bit or 64-bit) as the web
server platform for Epicor Web Access, then the Crystal Reports XI R2 report server
must be placed on a separate server machine running Windows Server 2003 (32-bit or
64-bit).
Note! Epicor Web Access reporting has only been certified with Crystal XI R2
Embedded Server SP4 and Crystal Reports XI R2 .Net 3.0 Runtime SP5. Prior
releases and versions have not been certified or supported.
Configure 1: Windows 2008 64-bit Web Server - PDF
If you use Windows Server 2008 64-bit web services, use the following steps to set up
a PDF configuration.
1. After creating an Epicor Web Access site, open Internet Information Server.
2. Expand the Sites and Default Web Sites nodes.
3. Locate the Epicor Web Site and single-click to enable the Feature view pane.
4. Under IIS section, double-click to open Handler Mappings.
5. In the Actions section, select Add Script Map.
- For the Request path, enter*.pdf.

- For the Executable, browse and select the file:
C:\Windows\Microsoft.NET\Framework\v2.0.50727\aspnet_isapi.dll
- For the Name, enter AboMapperCustom PDF 32.
- Click Request Restrictions.
- Go to the Verbs tab. Select the One of the following verbs checkbox.
- Manually enter GET,HEAD,POST,DEBUG.
- Click OK.
- Review the Edit Script Map setup form. The values should be the same as you
previously entered. Click OK.
- A message appears asking if you want to allow the ISAPI extension. Click Yes.
Configure 2: Windows 2003 64-bit Web Server - PDF

a PDF configuration.
3. Browse to the Epicor Web Access site. Right-click and select Properties.
4. Click the Virtual Directory tab. Select the Configuration button.
5. In the Application Configuration window, click the Add button.

- For the extension, enter *.pdf
- For the Verbs, select the Limit to checkbox.
- Click OK.
Configure 3: Windows 2008 32- or 64-bit Web Server - XLS
If you use Windows Server 2008 32-bit or 64-bit web services, use the following steps
to set up a XLS configuration.
1. Under IIS section, double-click to open Handler Mappings.
2. In the Actions section, select Add Script Map.
- For the Request path, enter*.xls.

- For the Name, enter xlsMappingCustom XLS 32.
- Click Request Restrictions.
- Go to the Verbs tab. Select the One of the following verbs checkbox.
- Click OK.
- Review the Edit Script Map setup form. The values should be the same as you
previously entered. Click OK.
- A message appears asking if you want to allow the ISAPI extension. Click Yes.

Configure 4: Windows 2003 64-bit Web Server - XLS
a XLS configuration.
3. Browse to the Epicor Web Access site. Right-click and select Properties.
4. Click the Virtual Directory tab. Select the Configuration button.
5. In the Application Configuration window, click the Add button.

- For the extension, enter *.xls
- For the Verbs, select the Limit to checkbox.
- Keep the Script Engine and Verify that file exists checkboxes selected.
- Click OK.
7.5 Upgrade Epicor Replication Server
Use these steps to upgrade your Epicor Replication Server on a server that is hosting
one or more subscribing replicated databases. The upgrade process includes
uninstalling and then reinstalling Epicor Replication Server. These steps must be
completed at each Service Pack or Patch release.
Record Existing Configuration Settings
1. Open the Epicor Replication Management Console.
2. Record the subscriber configuration settings. You will need to re-enter these
settings after installing the updated version of Epicor Replication Server.
3. Close the Epicor Replication Management Console.
Uninstall and Reinstall Epicor Replication Server
1. Uninstall the Epicor Replication server. To do this, select Start - Control Panel -
Add or Remove Programs. Select Epicor Replication Server and click Remove.

2. Go to the Replication directory on the server where your Epicor application is

installed. Based on your environment, example paths include:
- For a 32-bit system: Epicor Software\Epicor904\Replication\x86

- For a 64-bit system: Epicor Software\Epicor904\Replication\x64
3. Double-click on the Setup.exe file.
4. On the Database Setup dialog, click Install to install the Epicor Replication
prerequisites.
5. On the Welcome to the Epicor Database Replication SetupWizard, click Next.
6. For the TCP/IP settings, enter the following:
- Accept the default Port 11111 or select another port.

- Accept the default Data storage location or select another location. The default
is c:\Epicor\RepData.
Click Next.
7. Select a Destination Folder and click Next.
8. On the Confirm Installation dialog, click Next to start the installation.
Start the Service
1. Navigate to Start - Control Panel - Administrative Tools - Services.
2. Highlight to select the Epicor Database Replication Server service.
3. Click Start this service.
4. Verify that the status of the service is Started.
Review Configurations using the Epicor Application
Use the following steps to review the Replication Server configurations in the Epicor
application. See the Epicor application help system for more detailed steps, if
necessary.
1. Review your replication profiles. To do this:
- Log into the Epicor application.

- Go to System Management - Replication - Replication Profile Maintenance.

- Review the profiles and description.
2. Review the Replication settings values related to Sonic. To do this:
- Go to System Management - Replication - Replication System

Maintenance.
- From the Tools menu, select Settings. Review the values in the Replication
Settings dialog.
3. Review the company assignments of the replication profiles. To do this:
- Go to System Management - Replication - Replication System

Maintenance.
- Select your company and review the assigned profiles.
4. Review the configurations of the Replication Agent process. To do this:
- Go to System Management - Replication - Replication Agent Process.

- Review the configuration values.
5. Configure the Replication Log Reader process. To do this:
- Go to System Management - Replication - Replication Log Reader Process.

- Review the configuration values.
6. Use the Progress Explorer Tool to stop, and then restart the server.
7. Verify that the log files produced by the Replication Agent and Replication Log
Reader do not contain errors.
Configure using Replication Management Console
Use the following steps to configure Replication Server using the Replication
Management Console. See the Replication Management Console help system for more
detailed steps, if necessary.
Note! For existing installations, use the values you recorded prior to uninstalling
Epicor Replication Server.
1. Open the Replication Management Console.
2. Add a publisher for the Epicor application.

Note! Verify that the Sonic Topic Prefix setting in the Publisher properties matches
the Sonic Topic Prefix indentified as a Replication Setting in the Replication
System Management program.
3. Select a subscribing database. Types include AdHoc, Functional or other.
4. Select a Subscriber Class. The subscribing database is represented by a Subscriber

Class entity.
5. Add a Target Database. A target database includes connection information for the
subscribing database.
6. Add a Subscriber instance. A subscriber instance links the target database to the
publisher.
7. Define filters to specify which tables and companies should be received by the
subscriber instance.
8. Initialize the Subscriber Instance. Initializing the subscriber instance creates tables
in the target database and copies the existing data to the target database.
7.6 Upgrade Epicor Enterprise Search
Use these steps to upgrade your Epicor Enterprise Search. The upgrade process
includes uninstalling and then reinstalling Epicor Enterprise Search. These steps must
be completed at each Service Pack or Patch release.
Verify SQL Server Prerequisites
Use these steps to verify the requirements before you begin the installation and
configuration of Epicor Enterprise Search.
1. Verify that you are using SQL Server 2005.
2. Verify that the SQL Server 2005 installation has SQL and Windows
Authentication enabled.
3. Verify that the server where Enterprise Search is installed also has SQL Server
2005 installed as the named or primary instance. For example, if your server is
named Candy, then SQL Server 2005 must be made available as Candy, and not as
a sub or separate installation.
4. Verify you are running SQL Server locally. Note that the Epicor application SQL
database can be located on a remote server.
5. Verify that the account you used to log into the system is trusted by SQL Server.

Uninstall Epicor Enterprise Search
Use these steps to uninstall Epicor Enterprise Search.
1. Select Start - Control Panel - Add or Remove Programs.
2. Select Epicor Enterprise Search and click Remove.
Reinstall Epicor Enterprise Search
Use these steps to reinstall Epicor Enterprise Search.
1. Log on to the server where you intend to install Enterprise Search.
2. Go to the directory where your Epicor application is installed. For example, go to

\Epicor Software\Epicor904.
3. Double-click on the EpicorUtilities.exe file.
4. On the Welcome to the Epicor Utilities Setup wizard, click Next.
5. On the Epicor Utilities Setup dialog, click the Install Enterprise Search button to
start the installation.
6. On the Welcome dialog, click Next.
7. On the Confirm Installation dialog, click Next. The files are installed.

The Epicor Enterprise Search is now installed.
Configure Replication Server for Epicor Enterprise Search
This section is optional if you are using SQL Server for your Epicor 9 transactional
database. When Epicor 9 is using Progress for its transactional database, you must
replicate the data to a SQL Server database for use by Enterprise Search. The replicated
database must be configured as a Fully Functional (Read Only) Subscribing database,
which means that the database includes the necessary schema and code needed to store
data for a fully working Epicor 9 application.
Note! Refer to Replication Server documentation in the Replication Server snap-in for
Admin Console and in the Epicor 9 application for full details on how to assign
replication profiles, configure replication subscribers, and enable data
replication.
Use the following steps as a basis to create a subscriber database that Enterprise
Search can use for indexing and searching.

1. In your Epicor 9 application, go to System Management - Replication -

Replication System Maintenance.
2. Assign the existing replication profile for Enterprise Search to the companies that
are going to be indexed for searching. Data from the tables defined in the profile
are replicated to the subscriber database for each of the companies that were
assigned the profile.
Note! The Enterprise Search profile only includes the tables needed to support
indexing and searching for Enterprise Search. It is not a profile that replicates
all the necessary data that is needed to run a fully working Epicor 9 application.
This means that the Epicor 9 application, including Epicor Web Access, must
be running using the Epicor 9 transactional database and not using the
replicated database. If you need to run the Epicor 9 application against the
replicated database, you must either create or use an existing replication profile
that includes all of the tables in the transactional database.
3. Create a new Epicor 9 database for use as the subscriber database. To do this, use
the default SQL script located in the directory where your Epicor 9 application
server is installed.
Note! For example, use \Epicor Software\Epicor904\server\sql\Epicor904.sql.
4. Use the Replication Management Console to add this newly created database as a
Functional subscriber.
Configure Epicor Enterprise Search
Use these steps to setup and configure Epicor Enterprise Search. To complete these
steps, you use a Windows command line tool. Note that when you type the commands,
the parameters are case-insensitive.
1. Open a Windows command prompt. For example, select Start - Run.
Note! If you are running on Windows Server 2008 or Windows Vista, you need to run
a Windows command prompt as the local administrator. To do this, navigate to
Start - Programs - Accessories. Right-click on Command Prompt and select
Run as Administrator.
2. Browse to the directory where your Epicor Enterprise Search program installed.
For example, go to Program Files\Common Files\Epicor Software
Corporation\Epicor Enterprise Search. Note that for a 64-bit Windows install, the
default directory begins C:\Program Files (X86)\.
3. Run the ESCmd utility to create the index database. To do this, type the following
command:
* ESCmd INDEXDB CREATE /FileLocation:d:\data /Size:40960 /o

Use the following parameter information for your command:
Parameter Description
/FileLocation Optional. Indicates where to locate the physical database files.
/Size Optional. Indicates the initial size (in KB) of the database MDF file. If the "size"
parameter is omitted, the default size is 40MB. In general, the index database
will be about 7% the size of the Epicor 9 application database. Note that the
index database recovery model is "bulk-logged", so the log file size is not
important.
/o Overwrites any existing index database.
4. Run the ESCmd utility to create an indexed system. To do this, type the following
command:
* ESCmd CreateSystem /host:hostname /port:portNum /moniker:myName

/user:uName /pw:password /o
/host The Epicor 9 server name.
/port The Epicor 9 server port number.
/moniker A single-word name used in the URL for executing searches. It is

recommended that you record the moniker value you select to use, since it will
be used again in a future step when you enter the URL to access the site.
/user The Epicor 9 user name used for managing indexes (should be an admin).
/pw The Epicor 9 login password.
/o Overwrites any existing system definition with the same system code.
Note! In order to successfully run the ESCmd CreateSystem command, Enterprise

Search must be licensed and enabled for the current company of the user
specified above for managing indexes.
5. Set the SQL Server login information for the application database. To do this, type
the following command:
* ESCmd System SetSQLSource /s:host:port /dbServer:sqlServerName

/dbName:sqlDBName /dbUser:sqlLogin /dbPassword:sqlPassword

/s The “system code” that identifies the indexed system, where host is the Epicor
9 server name and port is the Epicor 9 server port number.
/dbServer The name of the SQL server instance containing the target application
database.
/dbName The name of the application database.
/dbUser A login name for accessing the application database.
/dbPassword The SQL Server account password used to access the application database.
Note! The application database that Enterprise Search queries can be either the actual
Epicor 9 database or a replicated Epicor 9 database. When Epicor 9 uses
Progress for its transactional database, you must replicate the data to a SQL
Server database for use by Enterprise Search. Be sure you have already
completed the above steps in the "Configure Replication Server for Epicor
Enterprise Search" section. You can also follow these steps if you are using
SQL Server for the transactional database, however it is recommended to that
you use the main transactional database.
6. Run the indexer. To do this, type the following command:
* ESCmd RunIndexer /s:host:port

7. Go to the Services control panel. Stop and restart the Epicor Search Indexer
service.
8. Use the Task Scheduler in Windows to add a scheduled task to run the command:
ESCmd RunIndexer /s:host:port. The scheduled task is needed so that your data
is indexed on a regular interval.
Enable Enterprise Search for Epicor Application
Use these steps to enable Epicor Enterprise Search functionality from within the Epicor
application. In the configuration file you use to launch the Epicor application, you must
specifiy the EnterpriseSearchURL.

1. With a text editor, open the configuration file you use to launch the Epicor
application. For example, open the default.mfgsys file.
2. Specify the value of the EnterpriseSearchURL node to be

http://Machinename:8098/Search/Hostname.Port where:
* Machinename is the name of the machine on which Enterprise Search is

installed.
* Hostname is the name of the machine for the Epicor 9 application server.
* Port is the Epicor 9 application server port number.
The rest of the URL should be as specified above, so the :8098/Search/ portion is
fixed and should not be changed.
3. Assign security rights to the Epicor application users who need to access
Enterprise Search. To do this:
- Log into the Epicor application.

- Go to System Management - Company - User Security.
- Assign access to Enterprise Search to the user who needs the rights.
- Log out of the Epicor application.
4. Log back into the Epicor application. A search field should appear on the Main
menu toolbar. Click this search button to open Epicor Enterprise Search.
Configure Epicor Enterprise Search Web Site - Optional Steps
Use these steps to configure optional features of Epicor Enterprise Search.
1. If this is an upgrade from an previous installation, run the following command:

ESCmd Web DeleteApplication /site:"Default Web Site" /path:es9
The value specified for the path parameter should be the value that was specified
when the original ESCmd Web CreateApplication command was run.
2. Create the Enterprise Search web site. Creating the web site is optional and is not
needed for Enterprise Search support from within the Epicor application client. To
do this, type the following command:
* ESCmd Web CreateApplication /site:"Default Web Site" /path:es9

/files:c:\es9Files /o

/site The name of the IIS Web Site under which to create the Epicor Enterprise
Search web application.
/path The virtual path for the search site (web application name).
/files A physical location to place the web site files. If the location does not exist, the
system will try and create it.
/o Overwrites any existing application.
Note! If you receive a message similar to "Error creating application: Application

'ES9' already exists in 'Default Web Site'." when running the CreateApplication
command, it is possible you have another web application with the same name.
To resolve this, choose another value for the /path parameter or run the
DeleteApplication command to delete the existing web application, then re-run
the CreateApplication command.
3. Set the Epicor Web Access base url. To do this, type the following command:
* ESCmd SetWebFormUrl /s:host:port /url:EpicorWebAccesBaseUrl

/url The base url for Epicor Web Access may need to include a port setting
depending on your web site configuration. If the site is not on the default port,
then that port setting must be included in the url. For example, http://localhost/
EpicorWebAccess or http://localhost:8080/EpicorWebAccess.
The Enterprise Search web site is now operational. The URL to access the site is
http://machinename/application/moniker/search.htm where:
* Machinename is the name of the machine on which Enterprise Search is

installed. If the default web site is not running on the default port, then append
the actual port number to the machine name in the URL.
* Application is the name of the virtual directory created for Enterprise Search.
This is the value specified for the /path parameter in a previous step.
* Moniker is the value specified in a previous step when you ran the ESCmd
utility to create an indexed system.

Re-Install and License Embedded Education Content Pack
The Enterprise Search web site work only for Epicor users that have single sign-on
enabled in Epicor 9. This means that the Epicor user must have the user's domain user
name and domain name assigned to it.
When you get prompted to enter credentials, enter your domain user name and
password.
8. Re-Install and License Embedded Education Content Pack
Use these steps to re-install and license the Embedded Education Courses. Using the
Embedded Education Courses requires a Windows Server operating system and
Microsoft Internet Information Services (IIS 6 or IIS 7).
Note! Embedded Education Courses must be installed in your training environment,

not in your live production environment.
8.1 Verify 64-Bit Environment (if needed)
If you have installed a Windows 64-bit environment, verify that you completed the
“Configure 64-Bit Environments” instructions in the Post-Installation section. These
steps are required in order for web based products, such as Embedded Education
Courses, to work properly.
8.2 Re-Install Embedded Education Courses
Use these steps to re-install the Embedded Education Courses using the Epicor
Education Course Installer.
1. On the server where your Epicor application is installed, navigate to the Epicor
Education folder. For example, navigate to C:\Program Files\Epicor
Software\Epicor904\Epicor Education.
2. To open the Epicor Education Course Installer, double-click on the

EduCourseInstaller.exe file. The Epicor 9 Education Course Installer dialog
appears. The user interface looks different based on whether you have Windows
Server 2003, Windows Server 2008 or Windows Vista installed.
3. If you have Windows Server 2008 or Windows Vista installed, you must first
select the following:
* Select the Web Site where you want to install the Education courses. It is
recommended that you select the DefaultWebSite.
* Select the App Pool to use for the Education courses. It is recommended that
you select the DefaultAppPool and then verify that it is set to 32-bit and
Integrated. To verify the settings:

- Open the Internet Information Services Manager (IIS 7).

- In the Connections tree view, select Application Pools.
- In the Application Pools list, select the application pool used by the Epicor
Education virtual directory. For example, select DefaultAppPool.
- In the Action panel, click on Advanced Settings.
- Verify that Integrated is selected as the Managed Pipeline Mode.
- Verify that Enable 32-Bit Applications is set to True, if your system is a 64-
bit server.
- Click OK to close the dialog and save your changes.
- Close the IIS Management panel.
4. Enter the Alias you want to use to gain access to the courses. The alias is used as
part of the course server URL. Do not use spaces. The default is EpicorEducation.
Note! It is recommended that you record the Alias that you enter. In the next section,
you are required to configure the client by editing the .mfgsys configuration file.
To edit this file, you will need to enter the Alias and the course server URL.
5. Enter the Directory. The directory can be any folder on the server. For example,
if you have a folder on your server where you host Web content, such as
C:\Inetpub\wwwroot, you can install the courses to a sub-folder under that folder.
For example, enter a directory such as C:\Inetpub\wwwroot\EpicorEducation.
- For new installations, for example enter C:\Inetpub\wwwroot\EpicorEducation.

If you enter a directory that does not exist yet, the installer creates it. In this
example, the EpicorEducation folder will be created for you if it does not
already exist.
- For existing installations of embedded education courses, you should already
have a directory that was created to host the previous content. Browse and select
that same directory location for the updated courses.
6. For the Server Name enter the name of the server where your Epicor application
is installed.
7. Enter the Port used by the AppServer. To find your port number:
- Go to the Config folder on the server where your Epicor application is installed.
For example, go to the Epicor904\client\config folder.
- Open your train.mfgsys file and look at the AppServer node. The port number
should be listed. For example, the default port for the training database is 9011.

Note! The Server Name and Port must point to a training database and not a live
database within your production environment.
8. Enter a valid Epicor application User ID and Password. The course web site uses
this User ID and Password to login to the Training AppServer to verify licensing
information. The default User ID and Password for the Epicor Education database
is manager / manager.
9. Click Create.
Note! If any entries were not valid, a warning icon appears next to the invalid field.
Enter a valid entry in the field and click Create again.
10. After a message displays that the site has been created, close the Epicor Education
Course Installer.
8.3 Configure Embedded Education Course Client
Use these steps to configure the Embedded Education Course client.
1. On your client workstation, navigate to the client\config folder.
2. Open the train.mfgsys file in a text editor, such as Notepad.
3. In the <helpSettings> node, edit the following lines:
* Edit the <courseServer uri="" /> line to specify the location where the
education courses are installed. For example, if the courses are installed on a
server named Company1 and the alias is set to EpicorEducation, the line would
be: <courseServer uri="http://Company1/EpicorEducation/" />.
Note! Be sure to use the Alias that you entered and recorded in a previous step when
you ran the EduCourseInstaller program.
* Edit the <helpServer uri="" /> line to specify the location where the help files
are installed. For example, if the help files are installed on a server named
Company1, the line would be: <helpServer uri="//Company1/Help/" />.
Note! If the help files are installed on the deployment server, it is not necessary to edit
the <helpServer uri="" /> line.
- For example, the <helpSettings> node with the edited lines would look similar
to the following:

<helpSettings>

<helpServer uri="http://Company1/Help/" />
<courseServer uri="http://Company1/EpicorEducation/" />
<E9EducationKeysServer uri="" />
...
</helpSettings>
8.4 License Embedded Education Courses
Use these steps to license the Embedded Education Courses. License keys are specified
by Education Course module, not Epicor 9 modules.
2. On the toolbar, click the Education Course button (student with a graduation cap).
The Education Course program opens.
3. From the Actions menu, select one of the following options:
- Load License from file. Choose this option to enter the name of the license file.
- Enter License Keys. Choose this option to manually enter the key if you were
sent a file that contains your license keys. At the file prompt, browse to the file
and open it. Manually copy the license key information from the file into your
database. This step only has to be completed once and it is saved in the
Education database.
- Retrieve the key from EPICweb. Choose this option to download and install
license key information from EPICweb. Log on to EPICweb by entering your
User Id and Password. Click OK. Your EPICweb login information is verified
and then your embedded education course license keys are automatically
installed on your system.
Note! When a Service Pack is applied, the Education database is updated and the
license key information must be re-imported. If courses are delivered with the
service pack, reinstall them in the same location on the server.
4. Click OK to complete the embedded education course setup.
5. To view the embedded education courses, click the Refresh button from the
toolbar in the application. If the refreshed embedded education courses do not
display, you should close and reopen the application.

Restore Demonstration Database
9. Restore Demonstration Database
Use the following instructions to restore the Epicor 9 Demonstration Database, if

desired. The Epicor 9 Demonstration Database is released with every Service Pack and
Patch and is used with the Education Embedded Courses.
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.
2. Download the latest Epicor 9 Demonstration Database related to this installation.

For example, download one of the following files, based on your environment:
- Progress: Epicor9_Database_904506x_Vx_Progress.zip
- SQL: Epicor9_Database_904506x_Vx_SQL.zip
- SQL Unicode: Epicor9_Database_904506x_Vx_SqlUnicode.zip
- Linux 64: Epicor_Database_904506x_Vx_Linux64.zip
9.2 Verify Prerequisites
Use the following instructions to verify the prerequisite steps have been completed.
* All Appservers and OpenEdge Databases are stopped.

* Epicor 9 Patch has been installed.
* Epicor 9 Post-Installation steps have been completed.
9.3 Restore the Demonstration Database -- Progress
Use the following instructions to restore the Demonstration Database using the
Progress ProRestore command. These instructions assume the Epicor 9 Demonstration
Database is installed in: C:\Program Files\Epicor Software\Epicor904\db\Training.
Note! If you use SQL Server, do not use these instructions. Instead, use the
instructions in the next section: “Restore the Demonstration Database - SQL
Server”.

1. Go to the location where you downloaded the

Epicor9_Database_904506x_Vx_Progress.zip file.
2. Open the .zip file. Extract the Epicor9_Database_904506x_Vx_Progress.ed file

directly into the C:\Program Files\Epicor Software\Epicor904\db\Training folder.
3. Navigate to Start - Program - OpenEdge 10.1C - ProEnv. 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 Program Files\Epicor

Software\Epicor904\db\Training and press Enter.
7. At the C:\Program Files\Epicor Software\Epicor904\db\Training> prompt, run the

Prorest command. For example, for the 9.04.506x database, type: prorest mfgsys
Epicor9_Database_904506x_Vx_Progress.ed and press Enter.
8. At the overwrite message, type Y and press Enter.
9. When the restore is completed, you are returned to the C:\Programs Files\Epicor
Software\Epicor904\db\Training> prompt. Type exit to close the DOS window.
10. To re-import your product license codes, log into Epicor Admin Tools. To do this,
navigate to Start - Programs - Epicor Software - Epicor 9.04 - Epicor Admin
Tools.
11. Login with a valid User ID and Password. Note that the user must have Security
Manager rights. For example, login as manager / manager.
12. Connect to the location of your training environment, such as Epicor Train904.
13. Specify the imported license file for each company. To do this:
- Right-click on Company, such as Epic01, and select Properties.

- Change the license serial number to the imported license file.
- Repeat for each of the other companies, such as Epic02 and Epic03.
14. To reset the sequence table, click Run Conversions.
15. Scroll down the list of programs to number 5450 called “Re-set DB Sequences”.
Highlight the program to select it.

16. From the Conversion menu, select Run Conversion Program. Click Yes to
confirm.
17. After the conversion finishes, exit Epicor Admin Tools.
9.4 Restore the Demonstration Database - SQL Server
Use the following instructions to restore the Demonstration Database using SQL
Server. These instructions assume you have an EpicorTrain904 database in SQL Server
2005.
Note! If you use Progress, do not use these instructions. Instead, use the instructions
in the previous section: “Restore the Demonstration Database - Progress”.
1. At your server, navigate to Start — Programs — Microsoft SQL Server — SQL

Server Management Studio (SSMS).
2. Within SSMS, verify the Server Type is connected to the database engine.
3. Navigate to the Databases node.
4. Right-click on the EpicorTrain904 database. From the context menu, select Tasks
— Restore — Database. The Database window displays.
5. Click on the General tab. Within the Source for Restore section, select From
Device.
6. Click on the [...] button. The Specify Backup window displays.
7. For the Backup Media option, select File.
8. Click the Add button to locate and select the backup file. This file is:
Epicor9_Database_904506x_Vx_SQL.BAK
9. Click OK twice to complete the selection.
10. Select the check box next to the Backup Name field. This defines the back up set
to restore.
11. Click on the Options tab.
12. Select both the Overwrite the existing database and Leave Database Ready to
use (Restore with Recovery) check boxes.
13. 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\

EpicorTrain904.mdf
* C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\
EpicorTrain904_log.ldf
14. Click OK.
15. A dialog box displays indicating the database restoration is complete. Click OK.
16. Exit SQL Server Management Studio.
17. To re-import your product license codes, log into Epicor Admin Tools. To do this,
navigate to Start - Programs - Epicor Software - Epicor Administrative Tools
- Epicor Administration Console.
18. Login with a valid User ID and Password. Note that the user must have Security
Manager rights. For example, login as manager / manager.
19. Connect to the location of your training environment, such as Epicor Train904.
20. Specify the imported license file for each company. To do this:
- Right-click on Company, such as Epic01, and select Properties.

- Change the license serial number to the imported license file.
- Repeat for each of the other companies, such as Epic02 and Epic03.
21. To reset the sequence table, click Run Conversions.
22. Scroll down the list of programs to number 5450 called “Re-set DB Sequences”.
Highlight the program to select it.
23. From the Conversion menu, select Run Conversion Program. Click Yes to
confirm.
24. After the conversion finishes, exit Epicor Admin Tools.
9.5 Restart Database and Main Appserver
Use the following instructions to start the database and main Appserver

the Progress Explorer Tool to start the following functions in order:
* Start the Database: Epicor904

* Start the Appserver: Epicor904

2. Minimize the Progress Explorer Tool. Do not start the other Appservers yet.
3. Activate your module licenses. To do this, follow the steps detailed in the previous
“License Embedded Education Courses” section.
9.6 Set Up System Agent for Printing
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 main Mfgsys database directly located
in this folder: C:\Programs Files\Epicor Software\Epicor904\db\Training.
1. Log into Epicor 9. Use the Username and Password of manager/manager.
2. Navigate to System Management - Utilities - System Agent.
3. In the Task AppServer section, change the AppServer URL to AppServerDC://

localhost:9013.
4. In the System AppServer section, change the AppServer URL to AppServerDC:/

/localhost:9011.
5. For the Password, enter manager.
6. For the Server File Directory, enter \\<your machine>\EpicorData. You can
locate your machine name by selecting Properties - Computer Name.
7. For the Client File Directory, enter \\<your machine>\EpicorData.
8. For the Client Program Directory, enter: \\<your machine>\Epicor

Software\Epicor904\Server.
9. Save the System Agent changes. Exit System Agent Maintenance.
10. Close the Epicor 9 application.
9.7 Restart Remaining Appservers
Use the following instructions to start the remaining Appservers.
1. Open the Progress Explorer Tool. Start the following Appservers in order:
* Epicor904TaskAgent
* Epicor904ProcessServer
2. Exit the Progress Explorer Tool.

Review Change List
9.8 Test Demonstration Database Update
Use the following instructions to verify that the Demonstration Database was properly
updated.
2. Log on using your Username and Password.
3. From the Help menu, select About Epicor 9.
4. Verify that the version has changed to the correct version you installed.
10. Review Change List
Use the following list to review the Software Change Requests (SCRs) that have been
resolved with this release.
The Summary Description for each SCR starts with an SCR Type, which describes the
nature of the change. A Detail Description is included if further explanation is needed.
10.1 Changes and Resolved Issues in 9.04.506A
Financial Management
Module SCR Type Description
Accounts 67646 Application Payment Entry - Edit list sorting by Supplier ID not for Name, Invoice
Payable column not wide enough with 9+ digits
71389 Application AP Invoice - Miscellaneous line can post without a required GL

reference
72632 Application Bank Funds - Transfer uses the Posted Currency amount instead of
the Bank Currency amount
72969 Application Invoice Entry AP - AP Invoice Entry Group out of balance based on
number of lines on the first invoice entered
Accounts 64860 Application Invoice Entry AR - Missing Sales Order number when Get Shipment is
Receivable used
66460 Application Invoice Entry AR - When printing Shipment Invoice, the first contact
name is also printed in the second invoice
68918 Rule Invoice Entry AR - Invoice Posting is switching Division and

Department Segment values
69309 Application Invoice Entry AR- Unit price field always shows the price converted
into Base currency, instead of Document Currency
70915 Application Aged Receivables - Invoice Adjustment does not affect the report for
the date of the adjustment

Review Change List
71553 Application AR Invoice - Intrastat problems still posts to GL
71755 Application Cash Receipt - Cannot change a cash receipt if the company does not
have Currency Management
71815 Application Invoice Entry AR - Intrastat error causes double posting to GL
Cash 67408 Application Payroll Check Entry - Incorrect Overtime General Ledger Account
Management when printing check register
Currency 54863 Application Currency Revaluation Process - Currency Revaluation Report does
Management not show the Reporting Currency revaluation data
Fixed Assets 71861 Application Asset Posting Process - Asset depreciation posted multiple times
General 49688 Application COA/ General Ledger account - GL account with inactive segment
Ledger stays active
66362 Application Posting Engine - AR Invoices do not post to Product Group's GL

Control on an upgraded database from Vista 8.03 using the Standard
Rules
71601 Application Verify Balances - Changes the Fiscal Period of GLJrnDtl record
based on JEDate
71819 Application GL Period End - Custom Posting rules allows transactions with invalid
accounts to post
72081 Application General Ledger - MS LAB:Lock wait timeout of 180 seconds expired
due to hardcoded key value
72236 Application Posting Engine - Cannot Activate Revision with BAQ calling Decimal
or Date type field
72482 Application Journal Entry - Single Book posting error in the log:
"abtMoveABTToHistory" was not found
73459 Application Posting Engine - Duplicate Journal Numbers being assigned with
Multi-Book Posting
Production Management
Data 71065 Application End Activity - Does not update Part Location Quantity field on an
Collection issued material when Auto Receive is selected
Engineering 32705 Application Engineering Workbench - Tree has refresh issues
72319 Application Engineering Workbench - When an Alternate Method is created,

Reference Designators are not being copied
Job 57254 Application Job Manager - WipQty column in Job Manager label reads Number11
Management
57822 Application Job Tracker - Several cosmetic UOM issues in grids
59367 Application Job Entry - A warning message does not display when the Production
Quantity does not match the lot size calculation
Material 71783 Application Process MRP - Deletes all part quantity allocations in fulfilment
Requirements
Planning

Review Change List
Scheduling 56961 Application Resource Scheduling Board - Job did not move on the board and after
refreshing, does not appear
72273 Application Schedule Board - When the job has more than one labor record, the
board marks the whole operation as complete
Sales Management
Demand 69652 Application Demand Entry - Demand Line List sheet displays two columns with
Management the label 'Rev'
72046 Application Bill of Lading Entry - Create a new RDD for Bill of Lading for EDI
72135 Application Demand Entry - Releases are not closed If they are updated with less
or equal than the Shipped Qty
72360 Application Demand Entry - Error Logs are not displayed for schedules that are
not yet posted
EDI 60123 Application Demand Entry - Sales Order Header is created when Demand is
rejected due to a price discrepancy
61592 Application EDI Inbound - When an EDI inbound file is imported, lines that have
the same Part are joined
65045 Application EDI Inbound - Demand Detail Extra Charge lines cause constraint
errors in the workflow
Order 67419 Application Fulfillment Work Bench - Does not accept dd/mm/yy date format when
Management selecting the date for search
71089 Application Fulfillment Work Bench - Credit Hold check box is still checked even
though order is no longer on credit hold
71781 Application Cross Dock- Unhandled Exception when refreshing form after
Adjustment
Quote 72369 Application Opportunity / Quote Entry - Validate reference designators is not
Management working between subassemblies and materials
Supply Chain Management
Inventory 48454 Application Time Phased Mtl Requirements - The 'Ignore if needed by' field only
Management works if the date is the latest related to a Sales Order
67866 Rule Inventory / WIP Reconciliation Report - Does not disburse costs to
proper WIP G/L Accounts
72577 Application Cost Adjustment - Effects Supplier Managed Inventory Costs
Purchasing 52417 Application Purchase Order Entry - When changing PO Suggest to a PO, the Unit
Management Price is reverted to value of Supplier Price List
56668 Application Purchase Order Entry - Duplicating PO's does not enable "Buy for"
options and allows to approve it without a job

Review Change List
67778 Application Generate Suggestions - Ship Via on a sales order is not brought over
to the PO Suggestion
68429 Application Purchase Order Entry - Does not print Part Number if the supplier part
is manually entered in PO Suggestion
Shipping / 51181 Application Customer Shipment Entry - Job Ship Qty shows too many decimals
Receiving when Mass Ship is used to generate the line
68106 Application Customer Shipment Entry - Does not pull in weight UOM from picked
orders
70261 Application Customer Shipment Entry - Unable to select Serial Numbers in Pack
Out when processed from Material Queue
71142 Application Customer Shipment Entry - Ex Buy to Order releases display error
when shipping
71345 Application Receive Transfer Order - Leaves orphaned costs
72163 Application Customer Shipment Entry - Kit Component lines are removed after
editing previous line using Mass Ship
Tools and Technology
Epicor Web 66468 Tools Web Forms Chart Tracker - Clicking Retrieve on Movement Summary/
Access (EWA) Total clears the specific sheet
66472 Tools Web Forms Chart Tracker - Pressing Retrieve on the Journal Detail
sheet does not return data
Replication 72212 Tools Replication Server - Initialization message processing failure

Server
Software 72312 Tools BL Tester - Unhandled exception: Bad URL Format: Invalid numeric
Development port number
Kit (SDK)
General 70885 Tools BPM - BPM Server raises an exception when processing a .net action
if the BO dataset contains data in more than one table
10.2 Enhancements in 9.04.506A
Financial Management
General 71542 Application General Ledger Account - GL Import Utility add features for FC
Ledger transactions into FC Accounts

Review Change List
Sales Management
Demand 66334 Application Demand Entry - Provide the ability to use the customer price received
Management in the inbound file
73625 Demand Entry performance is slow adding a detail
EDI 62006 Application EDI Inbound - Workflow validation should check again after an invalid
part is re-submitted
Order 67239 Application Project Entry - Build Project Analysis doesn't honor Enable Mfg Cost
Management Elements checkbox
Quote 69397 Application Opportunity / Quote Entry - Slow performance when loading the
Management search screen

Epicor9 PatchGuide 904506A

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Epicor9 PatchGuide 904506A

Uploaded by

Copyright:

Available Formats

Epicor 9 Patch

Page 2 of 53 Epicor 9 Patch Installation Guide: Patch 9.04.506A

1. Pre-Installation Steps .................................................................................................. Page 5

3. Install Epicor 9 Patch for Windows ............................................................................ Page 7

4. Install Epicor 9 Patch for Linux/UNIX....................................................................... Page 9

5. Post-Installation Steps............................................................................................... Page 11

6. Log in the First Time ................................................................................................ Page 16

7. Upgrade Optional Installations ................................................................................. Page 18

8. Re-Install and License Embedded Education Content Pack..................................... Page 40

9. Restore Demonstration Database .............................................................................. Page 44

10. Review Change List ................................................................................................ Page 49

Page 3 of 53 Epicor 9 Patch Installation Guide: Patch 9.04.506A

Use the following graphic to review the installation process flow:

Install the latest

- Download Service Pack and/or Patch files

- Convert Your Data

- Import Posting (Booking) Rules for Extended

- Configure 64-Bit Environments

Review Change List

Page 4 of 53 Epicor 9 Patch Installation Guide: Patch 9.04.506A

1.1 Review Change List

1.2 Verify Your Epicor Application Version

1.3 Back Up Database and System

1.4 Back Up Customized Reports

1. Go to your Crystal Reports directory.

Page 5 of 53 Epicor 9 Patch Installation Guide: Patch 9.04.506A

1.5 Test Customizations

1. Create a test environment.

1.6 Test Product Configurator

If you use Product Configurator functionality, we recommend that you perform

1. Create a test environment.

2. Test all Product Configurator configurations.

2. Install Progress OpenEdge 10.1C Service Pack and Hot Fix

Note! Do not skip this step!

Note! You can use this link: https://epicweb.epicor.com/Support/epicor9/Downloads

2. Navigate to OpenEdge / Version 10.1C.

Page 6 of 53 Epicor 9 Patch Installation Guide: Patch 9.04.506A

3. Install Epicor 9 Patch for Windows

3.1 Download Epicor 9 Patch Files

Note! You can use this link: https://epicweb.epicor.com/Support/epicor9/Downloads

2. Navigate to Epicor 9 / Version 9.04.500.

- Progress on Windows (32 bit): PA904506a-P.EXE

3.2 Stop the AppServers

2. Select Start — Programs — OpenEdge 10.1C — Progress Explorer Tool. Use

* Stop all the Appservers.

Page 7 of 53 Epicor 9 Patch Installation Guide: Patch 9.04.506A

3.3 Install Latest Epicor 9 Patch on the Server

1. Go to the directory where you downloaded the latest patch file.

2. Double-click on the file to run it.

3. A Welcome window appears. Click Next.

4. A confirmation window appears. Click Yes to proceed.

8. The Start Installation window appears. Click Next.

9. A message appears, stating that the application patch installation is complete.

The Epicor application patch is now installed.

3.4 Install Help Content Pack

2. Double-click on the file to run it.

3. A Welcome window appears. Click Next.

5. The Start Installation window appears. Click Next.

6. A completion message appears. Click Finish.

Page 8 of 53 Epicor 9 Patch Installation Guide: Patch 9.04.506A

The Help Content Pack is now installe

4. Install Epicor 9 Patch for Linux/UNIX