Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
05 Installation Guide
SP Upgrade 9.05.60x to 9.05.700 - SQL
Disclaimer
This document is for informational purposes only and is subject to change without notice. This document and its
contents, including the viewpoints, dates and functional content expressed herein are believed to be accurate as of its
date of publication. However, Epicor Software Corporation makes no guarantee, representations or warranties with
regard to the enclosed information and specifically disclaims any applicable implied warranties, such as fitness for a
particular purpose, merchantability, satisfactory quality or reasonable skill and care. As each user of Epicor software is
likely to be unique in their requirements in the use of such software and their business processes, users of this document
are always advised to discuss the content of this document with their Epicor account manager. All information contained
herein is subject to change without notice and changes to this document since printing and other important information
about the software product are made or published in release notes, and you are urged to obtain the current release
notes for the software product. We welcome user comments and reserve the right to revise this publication and/or
make improvements or changes to the products or programs described in this publication at any time, without notice.
The usage of any Epicor software shall be pursuant to an Epicor end user license agreement and the performance of
any consulting services by Epicor personnel shall be pursuant to Epicor's standard services terms and conditions. Usage
of the solution(s) described in this document with other Epicor software or third party products may require the purchase
of licenses for such other products. Where any software is expressed to be compliant with local laws or requirements
in this document, such compliance is not a warranty and is based solely on Epicor's current understanding of such laws
and requirements. All laws and requirements are subject to varying interpretations as well as to change and accordingly
Epicor cannot guarantee that the software will be compliant and up to date with such changes. All statements of
platform and product compatibility in this document shall be considered individually in relation to the products referred
to in the relevant statement, i.e., where any Epicor software is stated to be compatible with one product and also
stated to be compatible with another product, it should not be interpreted that such Epicor software is compatible
with both of the products running at the same time on the same platform or environment. Additionally platform or
product compatibility may require the application of Epicor or third-party updates, patches and/or service packs and
Epicor has no responsibility for compatibility issues which may be caused by updates, patches and/or service packs
released by third parties after the date of publication of this document. Epicor® is a registered trademark and/or
trademark of Epicor Software Corporation in the United States, certain other countries and/or the EU. All other
trademarks mentioned are the property of their respective owners. Copyright © Epicor Software Corporation 2012.
All rights reserved. No part of this publication may be reproduced in any form without the prior written consent of
Epicor Software Corporation.
Contents
This part of the guide explains how to verify the prerequisites prior to installing or upgrading your Epicor 9.05 installation.
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
3. In the Available Downloads list, locate and download the installation guide for your platform, either SQL,
Progress, or Linux/UNIX. Note that specific guides are available for different installation types, including:
New installation, Upgrading from Epicor 9.04, or Service Pack upgrade from 9.05.60x.
4. Open the file. On the Disclaimer page, verify that the Revision Date is the same as the revision date on the
installation guide you are using.
It is recommended that you become familiar with the features available in the Epicor 9.05 release prior to installing
the Epicor 9.05 application.
1. Review the Epicor 9.05 Feature Summary to learn about the features in the Epicor 9.05 release. To access
the 9.05 Feature Summary, log onto the EPICWeb Documentation site and click the Feature Summaries link.
Note that you can also view the Feature Summary using the online help system.
2. If desired, contact the Services group to learn more about upgrading or migration to Epicor 9.05.
Note To request assistance from Services, fill out the Services Request Form available on the EPICWeb
Services site. You can use this link: https://epicweb.epicor.com/services/Pages/default.aspx.
Use the following instructions to verify that your financial groups have been posted prior to upgrading.
1. In your Epicor application, verify that the following financial groups have been posted:
• AR Cash Receipt Entry groups
• AR Invoice groups
• GL Journal Entry groups
• Payroll Check Entry groups
• AP Payment Entry groups
• AP Invoice groups
2. In your Epicor application, go to Job Management and open the Capture COS/WIP Activity Process.
Run this task to capture and execute the calculation process for work-in-process (WIP) and/or cost of sales
(COS) for standard jobs, project jobs, inventory, receipts, and adjustment transactions.
Software requirements have been updated for this release. Use the following information to update your system.
• Windows Server 2008 or Windows Server 2008 R2 must be installed on the server.
• If you use a Windows XP workstation, you must have Windows XP Service Pack 2 installed.
• You must have the Microsoft Internet Information Services (IIS) installed in order to use several features of
the Epicor application, including Embedded Education Courses, and Epicor Web Access. If you do not have
IIS installed, refer to your operating system documentation for instructions.
• You must have the ASP.NET module of your Windows Internet Information Services (IIS) installation enabled
in order to use several features of the Epicor application, including Epicor Web Access, Epicor Mobile Access,
or Epicor Embedded Education.
• If you are hosting an Epicor Web Access site on the Epicor application server, the IIS Server name must not
include the underscore character. If the IIS Server name has an underscore, the user won't be able to log in.
• To use a SQL or SQL Unicode database with the Epicor 9.05 application, you must have SQL Server 2008 or
SQL Server 2008 R2 installed on your database server. Use the installation instructions that came with SQL
Server 2008 or SQL Server 2008 R2.
• To run the Epicor Administration Console, you must have the latest Microsoft Management Console (MMC)
3.0 or later installed. See the MMC 3.0 download site for download information.
• If you have Customer Connect, the service pack for that product must be installed on your system.
• If you have SQL installed and you are using that SQL database for your transactional database, and you plan
to use Epicor Enterprise Search, you do not need to install Epicor Replication because you can use your SQL
database. See more detail in the Supplemental Installation section for Replication.
Use this section to review prerequisite information regarding the Demand Management and EDI modules.
With the latest release of Epicor 9.05, you must request a new license file if you use the Demand Management
or EDI Modules. To make your request, contact Epicor Customer Service. You can email
customerservice@epicor.com or call 1-800-390-5025.
Note that during a Post Installation step you will be instructed to import this license file.
Use this section to review the Demand Management processing options, including Epicor EDI Direct Import or
Epicor Service Connect Workflows.
Beginning in the Epicor 9.05.607 service pack release, Epicor introduced a new EDI Direct Import method for
Demand Management processing. The EDI Direct Import method removes much of the overhead inherent in the
prior Service Connect Workflows, leverages the embedded BPM framework, and most importantly, provides
significant performance advantages. Initial results from customers who have moved from the Service Connect
Workflow method to the EDI Direct Import method have indicated performance improvements greater than thirty
fold.
The option to continue using Epicor Service Connect workflows for Demand Management exists in both the
Epicor 9.05.607 and Epicor 9.05.700 releases. However, customers are highly encouraged to move to Epicor
Direct Import. As with any upgrade process, any current customizations will need to be reviewed and migrated
therefore, if you’ve customized the existing ESC Workflows then these will need to be addressed accordingly in
the Epicor Direct Import methods using the BPM capabilities. This can be accomplished internally by you or with
assistance from the Epicor Custom Solutions Group.
Be advised that the Epicor Service Connect Workflow methods for Demand Management are planned to be
removed when the Epicor 9.05.701 service pack is released. Additionally, while the option still exists to use the
ESC Workflows through the 9.05.700 release, any issues that existed in 9.05.607B will continue to exist in the
ESC Workflows at 9.05.700 and future improvements will be made only to the Epicor Direct Import methods.
Verify that SQL Server 2008 or SQL Server 2008 R2 is installed on your database server and Windows Admin
Workstation. If necessary, use these steps to install SQL Server 2008 or SQL Server 2008 R2. Note that SQL Server
2008 Express or SQL Server 2008 Express R2 can be installed on the Windows Admin Workstation.
Note It is recommended that you review the SQL Books Online information in order to become familiar
with the SQL Server administration functionality. The documentation is typically installed with the SQL
Server application. To access it, navigate to Start > All Programs > Microsoft SQL Server 2008 >
Documentation and Tutorials > SQL Server Books Online
1. On your database server, install SQL Server 2008 or SQL Server 2008 R2. To do this, use the instructions
that came with your SQL installation. Be sure to install any Microsoft service pack and patch updates related
to your SQL version.
2. On your Windows Admin Workstation, install SQL Server 2008, SQL Server 2008 R2, SQL Server 2008 Express
or SQL Server 2008 Express R2. To do this, use the instructions that came with your SQL installation. Be sure
to install any Microsoft service pack and patch updates related to your SQL version.
If you use CSF (Country Specific Functionality) verify your country upgrade exists prior to upgrading your Epicor
application. If a country upgrade does not exist, do not upgrade your Epicor application.
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
4. Review the available downloads. Verify that the version listed in the filename of the EXE is the same version
as the Epicor application Service Pack you plan to install. For example:
• If the filename is similar to xxCSF905 700-xxx.EXE, the country has an upgrade available for 9.05.700.
Therefore, you can upgrade to the Epicor application Service Pack release 700, and then upgrade your
CSF to 9.05.700.
• If the filename is similar to xxCSF905 607-xxx.EXE, the latest CSF upgrade available for the country is
9.05.607. Therefore, if you aren't at Epicor application release 9.05.607, you can upgrade to that version.
But you cannot upgrade your Epicor application to 9.05.700.
Note During the installation of the Epicor application service pack in a later section, you will be
prompted to review your CSF upgrade information that you verified in this section. Based on the files
available for your country, you may or may not be upgrading your CSF installation.
5. Log out of Epicweb. Do not download any files from Epicweb at this time.
If you use AEP (Advanced Estimating and Pricing) use these steps to verify AEP requirements. Your AEP version
must be at the latest version prior to upgrading your Epicor application. You can only upgrade to AEP 9.05.700
from an Epicor 9.05.607 application that has AEP 9.05.607 installed. If you use Progress, additional manual steps
are required.
3. If you use Progress, several manual steps are required prior to upgrading to the Epicor 9.05.700 application.
These manual steps must be completed by Epicor Technical Support. Contact Epicor Technical Support to
perform these steps.
It is strongly recommended that you set up a separate test environment prior to installing a new Epicor 9.05
application or upgrading from an existing Epicor version. You can use this test environment to test the new
application or to test your current system files, such as custom tools. Prior to upgrading, custom tools such as
personalizations, customizations, global alerts, Business Activity Queries (BAQs), Business Activity Manager (BAM)
events and Business Process Management (BPM) methods need to be tested and maintained prior to upgrading.
By using a separate testing environment, you will know what changes you have to make to your live system after
the upgrade, which helps ensure a successful upgrade.
Important Do not upgrade to Epicor 9.05 without first testing the installation in a separate test
environment.
1. Go to your system Temp folder. The location of the Temp folder differs based on your operating system.
To find the location of this folder, you can do one of the following:
• Select Start > Run. In the command window, type: %temp%. Click OK. The Temp folder location
opens in a browser. For example, the browser could open to C:\Users\[UserId]\AppData\Local\Temp.
• Select Start and right-click on Computer. Select Properties. Click the Advanced System Settings link
or the Advanced tab. Click Environmental Variables. In the User variables section, record the value
for the Temp variable.
Create the following back ups prior to continuing with your installation.
Database and system backups are very important. Do not skip this step.
2. Create a backup of your manufacturing software. In a standard installation, the files are located in the
\oe10xx and \epicor directories.
3. Verify that your backups are valid and can be restored if needed. To test that your backup is valid, restore
your backup to a test area, not your production area.
If you are using customized Crystal Reports, the report files must be backed up. These backups are very important.
Do not skip this step.
2. Save the reports as file names different from the standard report names.
2. Create a backup of all the .mfgsys files. For example, back up the default, train, test, and pilot files.
At the end of the service pack installation, the ClientZipInstaller program will automatically run and replace any
client-side .mfgsys files, such as default, train, and test with the .mfgsys files that currently reside on the server.
The program unpacks the client files, updates the current mfgsys files and then repackages the zip file with the
updated mfgsys files. This ensures that the mfgsys files are ready for the service pack installation. After the
installation, you can run the ClientZipInstaller program anytime you need it.
This part of the guide lists the steps to perform before installing or upgrading Epicor 9.05.
Use the following steps to disable error reporting on your workstation. This step is recommended in order to
save processing time by not automatically reporting software issues during installations. Based on your company
practices, you can enable error reporting after the installation process is complete. Note that the steps differ
based on your operating system.
2. Select Action Center. Select the Change Action Center Settings link.
3. Open Maintenance and then select the Problem reporting settings link.
2. Open the Local Group Policy Editor. To do this, open Start > Search. Type gpedit and press Enter.
3. Navigate to Computer Configuration > Administrative Templates > System > Internet Communication
Management > Internet Communication Settings.
4. From the main window, select Turn Off Windows Error Reporting.
5. On the dialog, select the Enabled check box. Click OK. The change takes place immediately.
Use this information to determine which type of Web Service you will install. Epicor 9.05 is compatible with two
types of Web Services: WCF (Windows Communication Foundation) and WSE (Web Service Enhancements).
start transitioning over to the WCF version. Note that based on Microsoft development, WSE will be
replaced with WCF.
2. If you want to install Web Services Enhancements (WSE) 3.0 Runtime, use the following steps:
b. Download the latest version of Microsoft WSE 3.0 Runtime to your server and Windows Admin
workstation.
c. Use the instructions provided on the website to guide you through the installation process.
Use this section to verify and install Progress OpenEdge 10.2A and the required OpenEdge Service Packs and OpenEdge
Service Pack Hot Fixes on your server.
If you have OpenEdge already installed, use the following steps to stop the AppServers and database prior to
starting the installation.
1. Sign on to the server and/or Windows Admin workstation as Administrator or Administrator equivalent.
2. Use the Progress Explorer Tool or OpenEdge Explorer Tool to stop the following functions in order:
• Stop the AppServer processes in the following order: Epicor905ProcessServer, Epicor905TaskAgent, and
Epicor905.
• Stop the OpenEdge database.
Use these instructions to install Progress OpenEdge 10.2A, SP 03 and SP Hot Fix 23 on your server and/or Windows
Admin workstation. You will need to reboot the server after completing this section. Note that if you already
have OpenEdge 10.2A, SP 03 and SP Hot Fix 23 installed, you can skip this section.
Note If you are using Windows Server 2008, the Progress Explorer Tool is not available. Instead, you must
set up a workstation to act as the Windows Admin Workstation. A remote Progress Explorer Tool connection
must be made from this Windows Admin Workstation to the server running Windows Server 2008 in order
to monitor AppServers and database status using Progress Explorer Tool.
1. Insert your OpenEdge 10.2A for Epicor 9.05.700 DVD in the server's DVD-ROM drive (D:\). The autorun
feature should launch the Installation wizard. If not, choose Start > Run and enter the command:
D:\OEMenu.exe.
2. The OpenEdge Installation option window appears. It may look similar to the following:
5. The installation wizard verifies if the required Progress OpenEdge components are installed on the server.
Review the Current Status of the components and whether an update is required. Click Next to continue.
7. You are returned to the OpenEdge Installation Option window. Click Exit to close the installer.
Note After you have completed your upgrades, you can use the Post-Installation section of this guide
to setup the Progress OpenEdge Explorer Tool and the Supplemental Installation Guide to install Sonic,
if needed.
8. In order to successfully install the Progress OpenEdge Explorer Tool, you need to disable the Admin Service
for OpenEdge service. The service will be automatically re-enabled after the installation is complete. To
disable the service:
a. Select Start > Control Panel > Administrative Tools > Services. Right-click on AdminService for
OpenEdge and select Properties.
b. On the General tab, use the drop-down menu for Startup type to select Disabled. Click OK.
Use these steps to install the latest updates on your server. Updates can include Epicor 9.05 service packs, patches,
and help system patches.
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 2008. If you use a
different operating system you may need to make slight adjustments to the instructions.
Use these steps to download the latest service pack, patch, and help files that will be installed later in the
installation process.
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
3. Download the latest Epicor 9.05 application service pack related to this installation. For example, select the
required file, based on your environment:
• SQL Server: SP90570x-S.EXE
• SQL Unicode: SP90570x-SU.EXE
Note Be sure to also download the Release Notes document for this specific release. The Release
Notes for a service pack is named Epicor905_ReleaseNotes_ 90570x.pdf.
4. Download the latest Epicor 9.05 application patch related to this installation, if one is available. For example,
select one of the following files, based on your environment:
• SQL Server: PA90570xx-S.EXE
• SQL Unicode: PA90570xx-SU.EXE
Note Be sure to also download the Release Notes document for this specific release. The Release
Notes for a patch is called Epicor905_ReleaseNotes_90570xx.pdf.
5. Download the latest Epicor 9.05 help content pack related to this installation. For example, download the
HELP90570x.EXE file.
Use the following instructions to install the Epicor 9.05 service pack on the server.
Use the following steps to install or upgrade your Epicor 9.05 server software. During the installation you are
prompted to select the type of installation: Complete, Standard, Minimum, or Custom. Note that based on the
type selected, different components are delivered (not installed) as executable files to a folder on your server.
2. Double-click on the file to run it. The InstallAware wizard verifies that the setup package content is compatible
with your environment and prepares for your installation. This may take several minutes.
3. The Welcome window appears for installing the Epicor 9.05 server software. Click Next.
4. On the Installation Type dialog, select the type based on which features you want to install. The default
option is Complete. Options include:
Note The components for the Utilities, Server Add-On, and Web Add-On features are delivered as
executable files to a folder on your server. The components are delivered, but they are not installed.
After your installation, you can use the Supplemental Installation section of this guide for instructions
on installing these additional features and programs.
Note The Server Add-On features include BPM Server, Enterprise Search, Epicor Education, Information
Worker, Replication, SSRS. The Web Add-On features include Epicor Mobile Access, Epicor Sharepoint
Publisher, Epicor Web Access, WCF Services, Web Services.
5. If you selected a Custom installation, you are prompted to select the specific features to install and deliver.
Select the features by clicking the down-arrow next to the X and selecting Install. The screen looks similar
to the following:
6. The Ready to Update window appears. Verify the server install directory. Verify the other components you
selected to install and deliver. For a Complete type installation, the screen may look similar to the following:
8. The installation begins. Informational messages appear. The installation process may take several minutes.
Note that when the empty databases are installed, a command box opens and processing messages may
display. This is normal.
Note If prompted with a message that a folder does not exist or cannot be accessed, verify that the
folder is shared and is not Read Only and then click Retry.
9. The Setup Complete window appears when the installation is complete. Click Finish. If prompted to confirm
exiting the setup program, click OK.
Note The two environments configured by the installation are under ports 9401 and 9411. If you
want to configure additional environments, such as for a Test or Pilot database, use the "Configure
Environments for Test and Pilot" instructions located in the Post Installation > Troubleshooting section.
Use these instructions to install the Epicor 9.05 patch on the server, if a patch is available.
2. Double-click on the file to run it. The InstallAware wizard verifies that the setup package content is compatible
with your environment and prepares for your installation. This may take several minutes.
4. Enter the directory where your Epicor program files are located. Click Next.
5. You may be prompted to verify your server name, operating system or database type. If prompted, select
the appropriate option and click Next. Note that this prompt is only displayed if your mfgsys.ver file is
incomplete.
7. A message appears, stating that the application patch installation is complete. Click Finished.
Use the following instructions to install the Epicor 9.05 client on the server where your Epicor application is
installed. Existing customers must run this client installation in order to properly update the shortcuts on your
server.
1. Make sure you are logged in as the Local Administrator on the server.
3. The Setup Information window appears for installing the client software. Click Next. The installation begins.
Use these steps to install the Epicor Help Content Pack on your system. The Help Content Pack contains the
updated online help system available with this release.
1. Go to the directory where you downloaded the latest Epicor 9.05 Help Content pack file.
2. Double-click on the file to run it. A Welcome window appears. Click Next.
3. Enter the directory where the Epicor 9.05 program files are located on the application server. Click Next.
The Start Installation window appears. Click Next.
Use the following instructions to configure your application server after installation.
1. Verify that the AdminService for OpenEdge 10.2A is not running. To do this:
a. Select Start > Control Panel > Administrative Tools > Services.
c. On the General tab, verify the Service status is Stopped. Click OK.
2. Insert your Progress OpenEdge 10.2A for Epicor 9.05.700 DVD in the server's DVD-ROM drive (D:\). The
autorun feature should launch the OpenEdge Installation wizard. If not, choose Start > Run and enter the
command: D:\OEMenu.exe.
Note If you do not have access to the DVD, you can download the required files from EPICweb
Support Downloads.
3. The OpenEdge Installation option window appears. Click the OpenEdge Manage button to begin the
installation.
4. The OpenEdge License Code window appears. It looks similar to the following window. Note that you will
need to enter the Serial Number and Control Number in the next step during the installation. This window
will remain open during the installation so that you can copy the text from the fields into the installer. If
desired, you can also record the license codes. Click Next.
5. The OpenEdge Progress Software installer runs. On the Welcome window, click Next.
Note If you are installing OpenEdge Explorer Management for 64-bit on a Windows 64-bit machine,
you may be exited from the installation. This is a known issue with the Progress OpenEdge Explorer
Management installation. To resolve the issue, close all applications and restart the OpenEdge Explorer
Management installation.
6. Enter the Serial Number and Control Number. You can copy and paste the text from the OpenEdge Install
window that is minimized on your status bar. Be sure to copy the data for your platform.
8. On the Destination and Working Path Directories window, click Next to use the default paths.
9. On the Program Folder window, click Next to select the OpenEdge Explorer.
10. On the Summary window, click Next. The files are installed.
12. You are prompted to reboot your computer. Click Yes. If you click No you are returned to the OpenEdge
Installation option window. Click Exit.
13. Change the starting method for the AdminService for OpenEdge. To do this:
a. Select Start > Control Panel > Administrative Tools > Services.
c. On the General tab, use the drop-down menu for Startup type to select Manual. Click OK.
a. Select Start > Control Panel > Administrative Tools > Services.
15. To configure your OpenEdge Explorer, go to Start > Programs > OpenEdge Explorer > Management
Console. This program launches your web browser with the URL: http://localhost:9090. When prompted
for a username and password, enter admin / admin.
16. To configure the tool, use the OpenEdge Explorer guides. To access the guides, go to Start > Programs >
OpenEdge Explorer > Documentation > OpenEdge Explorer.
Use these steps to update the Host parameter value if you use a multi-server configuration, for example, if you
have your Epicor 9.05 application server installed on a different machine than your SQL server. This parameter
value change is required in order for your system to run properly.
1. On the server where your Epicor application is installed, navigate to the Server\Config folder.
2. With a text editor, open the mfg*TCP.pf parameter file for the database you want to configure. For
example, parameter files include: MfgTCP.pf, MfgTrainTCP.pf, MfgTestTCP.pf, MfgPilotTCP.pf.
3. Locate the -db line. Update the -H value to be your Epicor application server. For example, the line would
look similar to the following:
-disabledeltrig
-T "C:\Epicor\EpicorData"
-db mfgsyssh -H EpicorApplicationServer -S 9400
where "EpicorApplicationServer" is the machine name of your Epicor application server.
5. You now need to update your Epicor Admin Tools client workstation. To do this, on the server where you
run your Epicor Admin Tools, navigate to the Server\Config\cs folder. Repeat the above steps to update
the following files: MfgTCP.pf, MfgTrainTCP.pf, MfgTestTCP.pf, MfgPilotTCP.pf.
Note If you do not use these steps to update the Host (-H) parameter, when you open Epicor Admin
Tools to run the conversion programs, you will be prompted with a message similar to the following:
"Could not connect to server for database mfgsyssh, errno 0 (1432)."
Use these steps to verify the parameter settings that are defined in the *.pf files. Several parameter settings are
required in order for your appservers to start and for your system to run properly. The parameter settings may
differ based on your database type, either Progress or SQL.
Note If the required parameters are not included in the *.pf file, your appservers will not start.
1. On the server where your Epicor application is installed, navigate to the Server\Config folder.
2. With a text editor, open the parameter file for the database you want to configure. For example, parameter
files include: Mfgsys.pf, MfgTrain.pf, MfgTest.pf, MfgPilot.pf.
3. For both SQL and Progress databases, use the following to verify the required parameters in the .pf file.
4. For SQL databases only, use the following to verify the required parameters in the .pf file.
5. For both SQL and Progress databases, use the following to verify the optional parameters in the .pf file.
6. If needed, review the parameter values in the following example .pf files.
• Example: Progress
• Example: SQL
7. Later, when you start your appserver, if the appserver does not start due to parameter validation issues,
review the appserver log file. In a standard installation, the log file is located in the Server\Logs folder.
If you use a non-unicode Epicor environment and you need to display the Euro currency symbol within Epicor
program or reports, you must update the .pf file code page reference to leverage Windows-1252 code.
An optional post-installation step, you can display the Euro currency symbol by adding a code page reference
line to the AppServer .pf file. This reference line causes your Epicor application to use the Windows-1252 code.
1. Navigate to the directory that contains your server configuration files. For example:
C:\epicor\deployment\server\config
2. Locate the AppServer .pf file you use with the Epicor application. For example, locate one of the following
files: Mfgsys.pf, MfgTrain.pf, MfgTest.pf, MfgPilot.pf.
3. Open your .pf file in a text editor like Notepad or a similar application.
Your Epicor application now uses Windows-1252 code. This code set contains the Euro currency symbol, so you
can display this symbol on various programs and reports throughout the Epicor application.
Use the following instructions to prepare your database prior to logging in the first time.
Use these instructions to initialize (for new installations) or convert (for existing installations) your database for
compatibility with the Epicor 9.05 application.
1. Verify that you have SQL and Progress installed on any machine where Epicor Admin Tools is installed.
2. Verify that the following steps are completed on the same server as where your SQL database is located.
The Epicor 9.05 Schema Change process cannot be executed remotely.
3. Use the Progress Explorer Tool or OpenEdge Explorer Tool to verify that your Appservers are not running.
Your Appservers cannot be running when you run schema changes or conversions.
4. Use the Progress Explorer Tool or OpenEdge Explorer Tool to verify that your database is running. Your
database must be running in order to run schema changes or conversions.
5. Verify you created a backup of your database as a step in the Getting Started > Verify Prerequisites section.
If you use Epicor Financial Management functionality, you must use the following sections to complete prerequisite
steps for this release.
1. On the server where your Epicor application is installed, navigate to the \Epicor905\server\cv folder.
3. In the <PostingDefaults> section, locate the <PreviousSP> tag. Enter a value to specify a service pack value
for importing posting rules. The parameter section may look similar to the following:
• <!-- Set value the previous SP if it was less than 9.05.700.
It helps more quickly update old data -->
<PreviousSP>X.XX.XXX</PreviousSP>
where "x.xx.xxx" is the service pack version, such as "9.05.607".
4. Review the mode specified for importing GL Transaction revisions. To do this, locate the <ImportMode>
tag. Review the values, which can be one of the following:
• Update. Conversion will update current active revisions.
• Override. Conversion will import new revisions for all Transaction Types. If this value is entered, you can
also specify a MergeACTRevision value (Yes or No) to determine if you want to merge old versions of
Active ACTRevision with the current versions.
If you are an existing SQL customer, use the following steps to restore your schema holders.
1. If your database and AppServers are running, use the Progress Explorer Tool or OpenEdge Explorer Tool to
stop the OpenEdge database.
2. Make a backup copy of your current schema holder files. To do this, do the following:
a. Go to the folder where your schema holder is located. For example, go to \Epicor905\db\newdb.
b. Make a copy of your current schema holder files. The schema holder files are mfgsyssh.*
3. Navigate to Start > Programs > OpenEdge 10.2A right-click Proenv and select Run as administrator
from the menu.
5. Using cd commands, navigate to the folder where your schema holder is located. For example, navigate to
\Epicor905\db\newdb.
6. In the folder where your schema holder files are located, if any previous schema holder files exist, you must
delete them. For example, in the \Epicor905\db\newdb folder, delete the following files: mfgsyssh.db,
mfgsyssh.d1, mfgsyssh.b1, and mfgsyssh.st.
7. To restore the schema holder backup file, at the prompt type one of the following commands, based on
your environment:
• SQL (32 bit): prorest mfgsyssh \backup\mfgsyssh32.bkup
• SQL (64 bit): prorest mfgsyssh \backup\mfgsyssh64.bkup
• SQL Unicode (32 bit): prorest mfgsyssh \backup\mfgsyssh32U.bkup
• SQL Unicode (64 bit): prorest mfgsyssh \backup\mfgsyssh64U.bkup
1. Change the starting method for the AdminService for OpenEdge. To do this:
a. Select Start > Control Panel > Administrative Tools > Services.
c. On the General tab, use the drop-down menu for Startup type to select Automatic. Click OK. Click
Start to start the service.
2. Use the Progress Explorer Tool or OpenEdge Explorer Tool to do the following:
a. Start the databases which you will be converting to the Epicor 9.05 level.
3. Open the Epicor Schema Change program. To do this, navigate to Start > Programs > Epicor Software
> Epicor 9.05 > Epicor Schema Change icon for the appropriate database.
4. The Schema Change Required window appears. In the Password field, enter CHANGESCHEMA. Click
Continue.
1. Use the Progress Explorer Tool or OpenEdge Explorer Tool to start the main AppServer.
2. Minimize the Progress Explorer Tool or OpenEdge Explorer Tool. Do not start the other AppServers yet.
Use the following steps to import your Epicor 9.05 application license codes.
Note If you are an existing customer using EDI or Demand Management, you must use these steps to
import the new license for those modules.
1. In the Epicor Administration Console, right-click on the desired database and select Connect to Application
Server.
2. Right-click on the Licensing node and select Import License File. Your dialog may look similar to the
following:
3. Browse to the location where you previously downloaded the license code file. Select the file and click Open
to import the file.
4. Double-click on the licensing code to open it. The Properties dialog opens.
5. Click the Modules tab. Select the check box for each module you want enabled.
Note It is recommended that you carefully review the modules that you have selected to enable.
Failure to enable your modules may result in possible data corruption. Also, if you enable a new module
at this time, you are committing to basic configuration and implementation steps within the application.
6. Click OK.
7. Repeat the above steps, if you are importing licensing for multiple databases.
1. Use the Progress Explorer Tool or OpenEdge Explorer Tool to stop the main AppServer.
Use these steps to run the data initializations (for new installations) or data upgrades (for existing installations)
on your Epicor 9.05 application.
1. On the server, run the Epicor Admin Tools program as Administrator. To do this, navigate to Start >
Programs > Epicor Software > Epicor 9.05, right-click Epicor Admin Tools and select to Run as
Administrator.
2. Login with a valid Epicor User ID and Password. Note that the user must have Security Manager rights.
Click OK.
3. If prompted for automatic mandatory conversions, click Yes. Mandatory conversion programs run.
Note If you use posting rules, the conversion process may block posting rules that are invalid. If any
rules cannot be activated, you are prompted with an informational message listing the blocked rules.
It is recommended that you take a screen capture of this message to be used later to review the
blocked rules.
4. To verify that the mandatory conversions or initializations completed successfully, make sure the database
conversion date is the correct date. To do this:
b. Review the list of programs that were run. If necessary, scroll to the right to see the Date the program
was run.
Note If you use Extended UD Table functionality, a schema change was run automatically for those
extended UD tables.
1. Use the Progress Explorer Tool or OpenEdge Explorer Tool to start the main AppServer.
2. Minimize the Progress Explorer Tool or OpenEdge Explorer Tool. Do not start the other AppServers yet.
Use the following instructions to update customized .mfgsys files, if you have customized .mfgsys files.
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.
If you use credit card functionality within the Epicor application, this release includes a PA-DSS validated solution
for securing credit card payments. To be able to use this functionality, you must install and configure the ESDM
(Epicor Secure Data Manager) program. The installation process includes installing Secure Data Service (SDS), Key
Services, and AuthorizationLite Service.
Use these steps to download the ESDM Installation Guide from EPICweb.
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 the product version you have installed. For example, navigate to Epicor 9 > Version Epicor
9.05.700.
3. Locate the ESDM folder. Based on your product version, it may be located under the Third Party Products
folder.
4. Download the Epicor Secure Data Manager Installation Guide file onto your local machine.
5. Use that guide to update the credit card functionality. Be sure to also use the Appendix: Configure Epicor
or Vantage section to complete the Epicor installation.
1. Use the Progress Explorer Tool or OpenEdge Explorer Tool to stop the AppServer processes in the following
order: Epicor905ProcessServer, Epicor905TaskAgent, Epicor905.
2. Use the Progress Explorer Tool or OpenEdge Explorer Tool to start the AppServer processes in the following
order: Epicor905, Epicor905TaskAgent, Epicor905ProcessServer.
3. Verify that the AppServer processes are running before starting the client.
Use the following instructions to install the Epicor 9.05 client on your workstation. New customers or existing customers
who are adding a new client workstation should use the following instructions to install the Epicor 9.05 Client. If you
are an existing customer and you are not adding a new client, you should use the following instructions to update the
version of Crystal Runtime installed on your client workstation.
Note The instructions on Crystal 2008 SP3 Runtime installation can also be used on your server or Windows
Admin workstation, if you plan to print Crystal Reports forms from your server or Windows Admin workstation.
1. Make sure you are logged in as the Local Administrator on the client workstation.
2. Use Windows Explorer to navigate to the server where Epicor 9.05 is installed. Go to the Epicor905 folder.
Double-click to run the Epicor9Client.msi file.
3. The Welcome window appears for installing the client software. Click Next.
4. The Destination Folder window appears. Specify the Client Destination and the Server Share Location path.
a. For the Client Destination, click Browse to navigate to a destination folder. For example, you can use
C:\Epicor\Epicor905.
b. For the Server Share Location, use \\<servername>\Epicor905, where <servername> is the machine name
where the server installation was done.
c. Click Next.
5. The Shortcut Creation window appears. Select the Create Desktop Icons check box to create the following
shortcut icons on your client desktop.
a. Epicor 9.05: Select this checkbox to run your Epicor 9.05 database from this workstation.
b. Epicor 9.05 MES: Select this checkbox to run the Data Collection programs from this workstation.
6. On that same window, you can also select the following check boxes to create icons in your program menu:
• Create Training Icons: Select this checkbox for training icons that can access the training database.
• Create Test Icons: Select this checkbox for test icons that can access the test database.
• Create Pilot Icons: Select this checkbox for pilot icons that can access the pilot database.
7. Click Next.
Use the following steps to uninstall any previous version of Crystal Runtime.
1. Navigate to Start > Control Panel > Programs > Uninstall a Program.
Use the following steps to install Crystal Reports 2008 SP3 Runtime on your client. You can also use these steps
to install Crystal Reports 2008 SP3 Runtime on your server or Windows Admin workstation, if you plan to print
Crystal Reports forms from your server or Windows Admin workstation.
Note You cannot install both Crystal Reports 2008 SP3 Runtime and Crystal Reports 2008 Developer on
the same client.
1. If you have a previous version of Crystal Reports .NET Runtime installed on your client, use the following to
uninstall the previous version:
2. 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
3. Navigate to Epicor 9 > Version 9.05.700 > Third Party Products > Crystal.
4. Download the latest Crystal 2008 SP3 Runtime file. For example, download Crystal_2008_03_Runtime.zip.
5. Navigate to the downloaded file. Open the .zip file and extract the contents.
6. Double-click to run the .exe file. For example, run the CRRuntime_12_3_mlb.exe file.
8. Review the license agreement information. Select I accept the License Agreement. Click Next.
Use the following steps to verify and test your Epicor 9.05 application the first time you log in.
If you are installing Epicor 9.05 for the first time, use these steps to import your posting rules for both Standard
and Extended Rules.
2. Select Financial Management > General Ledger >Setup > GL Transaction Type.
4. Click the Input File Name button. Navigate to the necessary folder based on your posting rules type. For
example, go to one of the following:
• Standard rules: \\<servername>\Epicor905\server\PostingRules\Standard
• Extended rules: \\<servername>\Epicor905\server\PostingRules\Extended
5. Select one or more .XML files. You can select multiple files by pressing the Shift key while you highlight
the files. Click Open to select the highlighted files.
6. Select the Import All check box to specify that you want to import all the selected XML files. To specify
individual XML files instead, you can select the Selected check box for each file.
7. If this is not the first time you are importing posting rule files, you can select the Replace All check box to
replace your existing revision with the same name. To specify to replace individual XML files instead, you
can select the Replace Existing check box for each file.
8. Select the Change All Revision Statuses To Active check box if you want to change the revision from a
draft to active for all transaction types being imported. To specify to activate individual XML files instead,
you can select the Activate check box for each file.
9. Select the Import into all companies check box if you want to import the posting rules into each company.
Note that newly created revisions are automatically set to Active in all companies.
11. You may be prompted with the Book Mapping dialog if any imported revisions contain books with IDs that
do not exist in the company to which you are importing rules. Do the following and click OK:
• Specify the mapping to select which book in the company should receive rules from which book in the
import xml file. The import program verifies if the imported rules use segments that don't exist or are
defined with a different name in the receiving book's Chart of Accounts (COA). If such segments exist,
you must either manually select the correct segment of the receiving COA that should be used or specify
that these segments should be assigned new values during the import.
• If you want to map the selected book identifier to all transaction types, select the Use for all transaction
types check box.
Use the following steps to review GL Transaction Type revisions that were not updated during the conversion, if
any exist. Revisions may have been blocked if the conversion process could not merge mandatory changes into
custom revisions or could not activate the revision. 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.
3. To manually revise the rules and make the necessary adjustments, go to Financial Management > General
Ledger > Setup > GL Transaction Type.
4. In the tree view area, select a revision. Based on the revision, you can do one of the following:
• If you want to import the standard posting rules that came with your Epicor application, follow the
instructions in the previous "Import Posting (Booking) Rules" section. Apply your customizations to the
rules.
• If you want to create a new revision, create it based on your custom posting rule and then apply your
adjustments to it.
Note You can review changes, which conversion applied to the revision, using Action menu >
Change Log. You can also use Action menu > Compare Revisions to review differences between
revisions.
5. After manually revising the rules, click the Revision tab. For the revision that you changed, use the drop-down
menu to select the Active status.
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.
Use the following steps to verify and maintain your customizations and personalizations. Note that the
Customization / Personalization Maintenance program attempts to automatically correct any problems that it
encounters during the verification process.
The verification process checks that each customization includes the following: a valid customization script, valid
custom properties, valid control keys, valid controls that are located on the form and properly docked, and
user-defined controls are added to the form. It also deletes customization properties that are no longer applied,
and cleans up the grid layout to remove obsolete fields.
5. Click Search. The customizations are displayed. Click Select All and then click OK to select all.
8. You are warned that this process may take several minutes. Click Yes.
9. The verification process reviews the selected personalizations and customizations. When complete, you are
returned to the Customization/Personalization Maintenance window.
11. Click the Warnings tab to review any elements that were not validated. Usually warnings are caused by
properties stored in the customization data that cannot be applied. Common warnings that you might see
include:
a. Cannot locate control on form. The key used for the customization is no longer on the form. This could
result from a renamed control or changed EpiGuid.
b. Could not set the property. No code exists that sets this property.
c. EpiBinding is not valid. Identifies the database field that should be used.
12. Use the Run, Modify, and Show Custom Data features from the Actions menu to correct the warnings.
13. After fixing a warning, select the row and click Remove Selected Item.
14. Click the Errors tab to review error messages generated by the selected program. Usually errors are caused
by problems with the customization script.
15. Use the Run, Modify, and Show Custom Data features from the Actions menu to correct the errors.
16. After fixing the errors, from the Actions menus, select Verify Customization.
17. Click the Detail tab to verify that the customization has passed validation. If it is valid, the current
manufacturing version is Valid For and Pass is the Status.
18. Repeat these instructions and select Personalization as the Type to verify and maintain your personalizations,
if necessary.
Use these steps to redeploy your dashboard assemblies that were previously deployed in your Epicor 9.05
application. The dashboard assemblies are deployed to the server.
Note For more information on how to build and deploy a dashboard, see the application help or the Epicor
ICE 2.5 Tools User Guide.
3. Click the Dashboard ID field and then click Search to display the list of dashboards.
4. In the results list, select all of the dashboards that have the Deployed check box selected. These dashboards
were previously deployed. Click OK.
5. From the Actions menu, select Deploy All UI Applications. The selected dashboards are redeployed.
During the Epicor 9.05 installation, unused obsolete fields are automatically deleted. Obsolete fields that are used
in calculations within BAQ are not deleted, but calculations with obsolete fields no longer work.
1. Review your calculations within any BAQs you want to continue using after upgrading your system.
3. Review the Schema Change topic to see which fields have been changed or removed.
After you upgrade, your BAQ reports should work since your fields are valid.
If you use any global alerts that activate procedure (.p) programs, use these steps to compile these programs
using the newly installed Progress 10.2A.
1. Review each BAM event that has a procedure program on your system. Verify that it still has a valid business
reason for being upgraded to the next version.
3. Save each BAM event, including the procedure files, in an archive location.
4. Move these BAM events and their procedure files to a new location.
5. If any schema changes affect the procedure program, update the .p program to reflect the new schema.
Use these instructions to update your outdated BPM directives after upgrading and to identify any that need
special attention due to schema changes or other factors.
Note You must use these steps to properly upgrade your BPM directives. You cannot just copy the BPM
directives in the Epicor905\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. Navigate to System Management > Business Process Management > General Operations > Directive
Update.
2. From the Actions menu, select Recompile All Outdated Directives. As the directives are converted and
re-compiled, an hour glass is displayed.
3. Upon completion, the compile results are displayed. Any Method Directives that failed to compile after the
conversion are listed.
4. Navigate to System Management > Business Process Management > Setup > Method Directives.
5. Use the Method Directives program to search for any Outdated Directives.
8. 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. Research how to update each outdated directive to make it
compatible with Epicor 9.05. This may involve updating your custom 4GL code to reflect the new schema.
9. Repeat these steps for all the outdated directives that you find.
Use these steps to test any custom code programs that were created and updated for you by the Epicor Custom
Solutions Group.
2. Contact the Epicor Custom Solutions Group if you need other custom code upgraded. Note that the Epicor
Custom Solutions Group requires time to review, estimate, schedule, and complete your custom solutions.
Based on your installation process, you are at one of the following points:
• If you completed the Epicor 9.05 installation in a test environment, you are now ready to test the installed
Epicor 9.05 application in that environment. After your testing is complete, you must repeat the entire
installation in your production environment.
• If you completed the Epicor 9.05 installation in your production environment, you are now ready to use the
installed Epicor 9.05 application in that environment.
Use the following instructions to restore the Epicor 9.05 Demonstration Database, if desired. The Epicor 9.05
Demonstration Database is released with every Service Pack and is used with the Embedded Education Courses. Note
that the Demonstration Database as delivered by Epicor must be used only with the Epicor application version for which
it was released.
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.
1. Log on to EPICweb and go to the Customer Portal Page. Navigate to Support > Epicor 9 > Downloads.
You can click this link: https://epicweb.epicor.com/Support/epicor9/Downloads
3. Download the latest Epicor 9.05 Demonstration Database related to this installation. For example, download
the necessary files, based on your environment:
• SQL (32): Epicor9_Database_90570x_Win32SQL.zip
• SQL (64): Epicor9_Database_90570x_Win64SQL.zip
• SQL Unicode (32): Epicor9_Database_90570x_Win32SqlUnicode.zip
• SQL Unicode (64): Epicor9_Database_90570x_Win64SqlUnicode.zip
Use the following instructions to verify the prerequisite steps have been completed.
Use the following instructions to restore the Demonstration Database using SQL Server. These instructions assume
you have an EpicorTrain905 database in SQL Server 2008 R2.
2. Open the .zip file. For example, open Epicor9_Database_90570x_WinxxSQLx.zip file. Extract the
Epicor9_Database_WinxxSQLx.BAK file directly into the C:\Epicor\Epicor905\db\Training folder.
3. Navigate to Start > All Programs > OpenEdge 10.2A, right-click ProEnv and select Run as administrator
from the menu. A DOS window opens.
7. At the C:\Epicor\Epicor905\db\Training> prompt, run the Prorest command. For example, type one of the
following and press Enter:
• SQL 32 bit: prorest mfgsyssh mfgsyssh32.bkup
• SQL Unicode 32 bit: prorest mfgsyssh mfgsyssh32u.bkup
• SQL 64 bit: prorest mfgsyssh mfgsyssh64.bkup
• SQL Unicode 64 bit: prorest mfgsyssh mfgsyssh64u.bkup
9. When the restore is completed, you are returned to the C:\Epicor\Epicor905\db\Training> prompt. Type exit
to close the DOS window.
10. At your server, navigate to Start > Programs > Microsoft SQL Server 2008 > SQL Server Management
Studio (SSMS).
11. Within SSMS, verify the Server Type is connected to the database engine.
13. Right-click on the EpicorTrain905 database. From the context menu, select Tasks > Restore > Database.
The Database window displays.
14. Click on the General tab. Within the Source for Restore section, select From Device.
15. Click on the [...] button. The Specify Backup window displays.
17. Click the Add button to locate and select the backup file. This file is: Epicor9_Database_WinxxSQLx.BAK
19. In the Restore column, select the check box for the backup you are installing.
21. Select both the Overwrite the existing database and Leave Database Ready to use (Restore with
Recovery) check boxes.
22. Verify the Restore Database Files As fields match the correct server directory paths where the database
files currently exist. For example:
• C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\ EpicorTrain905.mdf
• C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\ EpicorTrain905_log.ldf
23. Click OK. A dialog box is displayed indicating the database restoration is complete. Click OK.
1. Use the Progress Explorer Tool or OpenEdge Explorer Tool to start the main AppServer. For example,
EpicorTrain905.
2. Minimize the Progress Explorer Tool or OpenEdge Explorer Tool. Do not start the other AppServers yet.
Use the following instructions to import the product license codes and enable the modules.
1. Open the Epicor Administration Console. To do this, navigate to Start > All Programs > Epicor Software
> Epicor Administrative Tools > Epicor Administration Console.
2. Login with a valid User ID and Password. Note that the user must have Security Manager rights. For example,
login as epicor / epicor.
a. Select the Companies node. In the Companies column, right-click on your specific company, such as
Epic01, and select Properties.
b. Click the browse (...) button to search and select your serial number from the list of Available Serial
Numbers. Click OK.
c. Repeat to for each of the other companies, such as Epic02 and Epic03.
d. Select the individual modules to activate, or click the Enable all Licensed button to select all the modules.
The Enabled check box should be selected for the modules you want to activate.
e. Click OK.
Use the following instructions to run the required manual conversion to reset the sequence table. Your main
appserver must be stopped prior to running the conversions, and then restarted after the conversion has finished.
1. If your main appserver is started, you must stop it prior to running the conversions. For example, use the
Progress Explorer Tool to stop the EpicorTrain905 appserver.
2. Open the Epicor Admin Tools program. To do this, navigate to Start > Programs > Epicor Software >
Epicor 9.05 > Epicor Admin Tools.
3. Login with a valid User ID and Password. Note that the user must have Security Manager rights. For example,
login as epicor / epicor.
5. Scroll down the list of programs to number 5460 called Re-set DB Sequences. Highlight the program to
select it.
6. From the Conversion menu, select Run Conversion Program. Click Yes to confirm.
8. Start your main appserver. For example, use the Progress Explorer Tool to start the EpicorTrain905 appserver.
Use the following instructions to set up your system agent. The paths for the System Agent, which control report
printing, must be reset after a database restore.
These instructions assume your database is set to be the Mfgsys database directly located in this folder: C:\Programs
Files\Epicor Software\Epicor905\db\Training.
1. Review the paths you specified during the server software installation for the following locations:
• Destination Location
• Print Folder Destination Location
• Server Share Location
10. Save the System Agent changes. Exit System Agent Maintenance.
1. Open the Progress Explorer Tool or OpenEdge Explorer Tool. Start the Appservers in the following order:
• EpicorTrain905TaskAgent
• EpicorTrain905ProcessServer
Use the following instructions to verify that the Demonstration Database was properly updated.
2. Log in using a valid User ID and Password. For example, log in as epicor / epicor.
4. Verify that the version has changed to the correct version you installed.
Use these optional steps to configure a Windows Admin Workstation, if one is needed. These steps can be run on a
client or server machine, but they cannot be run on a server that has a 64-bit version of OpenEdge installed. The 32-bit
and 64-bit OpenEdge Software cannot be located on the same machine.
Note For a Windows install, this is an optional step if you want to configure a super-client workstation.
If you use SQL, use these steps to download and install the 32-bit Native Client 10 ODBC driver.
Note The Native Client 10 ODBC driver is required if you are installing the Admin Tools and Schema
Change shortcuts from the client workstation onto a Client Server Admin machine. The installation of this
ODBC driver is required for the client to communicate with the database.
1. Go to the Microsoft Download Center website to download the 32-bit SQL Native Client 10. The 32-bit SQL
Native Client is in a Feature Pack for Microsoft SQL Server 2008. The link is: http://www.microsoft.com/do
wnloads/details.aspx?FamilyId=C6C3E9EF-BA29-4A43-8D69-A2BED18FE73C&displaylang=en
2. In the Feature Pack for Microsoft SQL Server 2008, scroll to the download link for Microsoft 32-bit SQL
Server Native Client. Download the 32-bit SQL Native Client 10.
3. Install the 32-bit SQL Native Client 10. Verify that it is installed correctly.
1. Verify that your machine does not have a 64-bit version of OpenEdge installed.
2. Install the 32-bit version of Progress OpenEdge 10.2.A. See the Install Progress OpenEdge 10.2A section
of this document for instructions.
Note The OpenEdge 10.2A Service Pack and Service Pack Hot Fix are also installed.
1. Install the Epicor 9.05 Client. See the Install the Epicor 9.05 Client section of this document for instructions.
You must complete all the steps in that section.
Note During the installation, if this Windows Admin Workstation machine is where you plan to run
the Epicor Admin Tools and Epicor Schema Changes, be sure to select the following check boxes to
create the shortcuts: Epicor Admin Tools and Epicor Schema Change.
Note During the installation, if this Windows Admin Workstation machine will also be used as a
normal Epicor 9.05 client machine, you have the option of also selecting the following check boxes
to create additional shortcuts: Epicor 9.05 and Epicor 9.05 MES.
Use the following section if you need assistance in troubleshooting any installation issues.
Use the following steps to share the Epicor folders. Note that if you are using Windows Server 2008, the steps
may be slightly different.
1. On the C: drive, create the C:\Epicor\Epicor905 folder if it does not already exist.
b. Select the option to Share this Folder. Epicor905 displays as the default share name. Do not change
the name. The folder must be named Epicor905.
c. Click the Permissions button. It is recommended that you assign Full Control to the Everyone group.
Click OK to accept the permissions.
d. Click the Security tab. It is recommended that you assign read-only permissions to Users. Read-only
includes Read & Execute, List Folder Contents, and Read. Add an Administrator and assign the
Administrator Full Control. Click OK.
b. Select the option to Share this Folder. EpicorData displays as the default share name.
c. Click Permissions. It is recommended that you assign Full Control to each user folder. Click OK.
Use these steps to verify that the Client, ClientServer and Server folders are not read-only. These folders need to
have write access so that files can be added to them during the installation.
1. Go to the location where your Epicor 9.05 application is installed. For example, go to \Epicor\Epicor905.
3. On the General tab, unselect the Read Only check box. Click Apply.
4. The Confirm Attribute Changes dialog appears. The Apply changes to this folder, subfolders and
files option is selected by default. Click OK. Click OK to exit the Client Properties folder.
5. Repeat the previous steps for the ClientServer and Server folders.
Note For 64-bit installations, the ClientServer folder is located in the \Epicor\Epicor905\32 directory.
Use this appendix as a reference when modifying the configuration file settings in the default.mfgsys file. The
mfgsys file defines the main settings for server installation and each client installation. If the .exe file can see the
default.mfgsys file, the application is ready to run.
The configuration file is an XML file that contains syntax understood by the application. System Administrators
use it to control various installations.
Note You can also create a different configuration file and then have each workstation launch with this
alternate file. You can then keep the original file while you experiment with different configurations. Create
the alternate configuration, and then define the /CONFIG run time argument on each workstation.
If you received the error message "The authorization credential is expired", use these steps to verify the time
synchronization of your client and server. You may receive this error while performing a search from a client
workstation to the Epicor Web Access server if the time values that are set on the client and server are not accurate
according to the time zone.
1. On the client workstation, go to Start > Control Panel > Date and Time. Verify that the time is accurate
according to the time zone.
2. On the Epicor Web Access server, go to Start > Control Panel > Date and Time. Verify that the time is
accurate according to the time zone.
1. Open your Epicor 9.05 application. Navigate to System Management > Company Maintenance > User.
3. In the Format Culture field, select German. Keep the Language set to Turkish.
3. Restore Schema holder. To do this, go to \db\newdb\backup. Based on your operating system, use one
of the following files:
• mfgsyssh64u.bkup
• mfgsyssh64.bkup
• mfgsyssh32u.bkup
• mfgsyssh32.bkup
5. Restore SQL database. The SQL Script used to create an empty database is located in \db\newdb\backup.
The SQL script name to create empty database name may vary based on which Epicor 9.05 version is being
installed.
6. Create ODBC connections or verify they exist for EpicorPilot905 and EpicorTest905.
8. Run Schema Change tool to update the empty database and to verify the empty database is at the correct
version.
12. Run Admin Tools to update the empty database with beginning data.
Use these steps to add or remove programs and features related to your Epicor 9.05 application. This section
also includes steps to uninstall the Epicor 9.05 application from your server or Epicor 9.05 client from your
workstation.
Note It is highly recommended that you create a backup of all your important files, such as your databases,
prior to uninstalling the application.
Use these instructions if you want to add or remove programs or features that are related to your Epicor 9.05
application.
2. Right-click on Epicor 9.05 (database) and select Change from the menu. The Install Wizard opens the
Epicor 9.05 installation menu. The dialog may look similar to the following:
4. On the Select Features dialog, select the features you want to add or remove. Click Next. The Epicor 9.05
features you selected are added or removed.
Note When adding features, the components for the Utilities, Server Add-On, and Web Add-On
features are delivered as executable files to a folder on your server. The components are delivered,
but they are not installed. After your installation, you can use the Supplemental Installation section
of this guide for instructions on installing these additional features and programs.
The Epicor 9.05 installation menu includes an option to Repair / Reinstall the Epicor 9.05 application. While this
is a standard option available in an install wizard process, it is not recommended that you use this option with
your Epicor 9.05 application due to customizations or configuration settings unique to your system.
Use these instructions if you need to uninstall the Epicor 9.05 application from your server. It is highly recommended
that you create a backup of all your important files, such as your databases, prior to uninstalling the application.
1. Create a backup of your databases. For example, go to the \Epicor905\DB folder and create a backup of
your database files.
3. Right-click on Epicor 9.05 (database) and select Uninstall from the menu. The dialog may look similar to
the following:
5. On the Ready to Update Your System dialog, click Next. The Epicor 9.05 application is uninstalled.
7. The uninstall process may not delete files that were added or updated since the initial installation. To complete
the uninstall process, go to the location where you initially installed the Epicor application. For example, go
to \Epicor\Epicor905. Manually delete any existing files and folders.
Use these instructions if you need to uninstall the Epicor 9.05 client from your workstation.
2. Right-click on Epicor 9.05 Client and select Uninstall from the menu.
3. In the Previous Install dialog, the Update or Uninstall a single instance option is selected by default. Use
the drop-down menu to select the instance. Click Next.
4. On the Shortcut Creation dialog, select the Uninstall this client check box. Click Next.
5. On the Confirmation dialog, click Yes. The Epicor 9.05 client is uninstalled.
7. The client uninstall process may not delete all the files that were added or updated since the initial installation.
To complete the uninstall process, go to the location where you initially installed the Epicor client. For
example, go to \Epicor905\Client. Manually delete any existing files and folders.
1. Log on to EPICweb and go to the Customer Portal Page. Navigate to Support > Epicor 9 > Downloads.
Navigate to Epicor 9 > Version 9.05.700.
2. In the Available Downloads list, download the Supplemental Installation Guide. Note that this guide is the
same for all platforms.
3. Use the Supplemental Installation Guide to install the components and products you intend to use with your
Epicor 9.05 application.
Note If you are installing a patch upgrade to your Epicor 9.05 application, use the Release Notes
document to review the list of supplemental installations that must be upgraded.