Epicor905 Supplemental Install 905701

Epicor 9.
05 Supplemental Installations
9.05.701
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.
9.05.701
Revision: December 19, 2012 11:09 a.m.
Total pages: 82
sys.ditaval
Epicor 9.05 Supplemental Installations Contents
Contents
1 Welcome and Introduction.................................................................................................6
2 Configure 64-Bit Environment (Windows 2008)................................................................7
2.1 Enable ASP .NET 2.0 Application (64-bit only)............................................................................................7
3 Install Epicor Administration Console................................................................................8
3.1 Uninstall Epicor Administration Console.....................................................................................................8
3.2 Install Epicor Administration Console.........................................................................................................8
4 Install BPM Server................................................................................................................9
4.1 Review BPM Server Prerequisites................................................................................................................9
4.2 Install BPM Server Components................................................................................................................10
5 Install Epicor Enterprise Search........................................................................................11
5.1 Verify SQL Server Prerequisites.................................................................................................................11
5.2 Create Back Ups (if Previous Version).......................................................................................................12
5.3 Uninstall Epicor Enterprise Search (if Previous Version)..............................................................................12
5.4 Install Epicor Enterprise Search Process.....................................................................................................12
5.5 Configure Replication Server for Epicor Enterprise Search.........................................................................13
5.6 Configure Epicor Enterprise Search..........................................................................................................13
6 Install Embedded Education Courses...............................................................................15
6.1 Install Embedded Education Courses........................................................................................................15
6.2 Configure Embedded Education Courses Client.......................................................................................17
6.3 License Embedded Education Courses......................................................................................................17
7 Install Epicor Information Worker....................................................................................19
7.1 Review Information Worker Server System Requirements.........................................................................19
7.2 Review Information Worker Client System Requirements..........................................................................19
7.3 Uninstall Previous Version........................................................................................................................20
7.4 Install Information Worker Components...................................................................................................20
7.4.1 Generate Server Components........................................................................................................20
7.4.2 Install Information Worker Server...................................................................................................21
7.4.3 Install Information Worker Configuration Manager........................................................................22
7.4.4 Set Up Information Worker Server.................................................................................................22
7.4.5 Set Up Information Worker Clients................................................................................................22
7.4.6 Troubleshooting Installation Errors.................................................................................................23
8 Install Epicor DB Replication.............................................................................................24
9 Install Epicor SQL Server Reporting (SSRS)......................................................................25
9.1 Verify SSRS Prerequisites..........................................................................................................................25
9.2 Enable IIS 6 Management Compatibility...................................................................................................26
9.2.1 Using Vista and Windows 7...........................................................................................................26
9.2.2 Using Server 2008.........................................................................................................................26
9.3 Install Microsoft Report Viewer 2010 Redistributable Package..................................................................26
9.4 Configure Epicor SQL Report Monitor......................................................................................................27
9.5 Maintain Epicor SQL Report Monitor Configuration..................................................................................30
9.05.701 3
Contents Epicor 9.05 Supplemental Installations
9.6 Manually Install Custom Assembly DLL File (Report Server).......................................................................30

10 Install Epicor Mobile Access............................................................................................32
10.1 Uninstall Epicor Mobile Access...............................................................................................................32
10.2 Install Crystal .NET SDK Runtime and Crystal Reports Server 2011..........................................................32
10.2.1 Install Crystal .NET SDK Runtime..................................................................................................32
10.2.2 Install Crystal Reports Server 2011...............................................................................................33
10.3 Enable IIS 6 Management Compatibility.................................................................................................34
10.3.1 Using Vista and Windows 7.........................................................................................................34
10.3.2 Using Server 2008.......................................................................................................................35
10.4 Install Epicor Mobile Access Process.......................................................................................................35
10.5 Configure Epicor Mobile Access.............................................................................................................36
10.5.1 Configure EMA User....................................................................................................................36
10.5.2 Configure EMA Reporting............................................................................................................36
10.5.3 Assign Data Folder Properties and Sharing...................................................................................36
11 Install Epicor Sharepoint Publisher.................................................................................38
11.1 Uninstall Epicor Sharepoint Publisher......................................................................................................38
11.2 Install Epicor Sharepoint Publisher..........................................................................................................38
12 Install and Deploy Epicor Web Access............................................................................39
12.1 Install Crystal .NET SDK Runtime and Crystal Reports Server 2011..........................................................39
12.1.1 Uninstall Previous Versions of Crystal Runtime..............................................................................39
12.1.2 Install Crystal .NET SDK Runtime..................................................................................................39
12.1.3 Uninstall Previous Version of Crystal Embedded Server.................................................................40
12.1.4 Install Crystal Reports Server 2011...............................................................................................40
12.2 Configure Forms and Components........................................................................................................41
12.3 Install Epicor Web Access.......................................................................................................................42
12.4 Deploy Epicor Web Access.....................................................................................................................45
12.5 Configure Epicor Web Access................................................................................................................46
12.6 Assign Resource Folder Properties and Sharing.......................................................................................46
12.7 Install Full Adobe Reader on Epicor Web Access Client...........................................................................47
12.8 Update Epicor Lightweight Client Installer File........................................................................................47
12.9 Configure EWA Reporting URL Display Features.....................................................................................48
12.9.1 Configure: Windows 2008 64-bit Web Server - PDF.....................................................................48
12.9.2 Configure: Windows 2008 32- or 64-bit Web Server - XLS...........................................................48
12.10 Generate Web Forms for Customized Epicor 9.05 Forms......................................................................49
12.11 Generate Web Forms for User Dashboards...........................................................................................49
12.12 Review Supported Browsers and Configuration....................................................................................50
12.13 Set Up Compression for Performance Tuning.......................................................................................50
12.14 Set EWA Server Timeout......................................................................................................................51
13 Reinstall Web Services.....................................................................................................52
14 Reinstall CSF Functionality..............................................................................................53
15 Upgrade to Service Connect 9.05...................................................................................54
16 Upgrade to Epicor Portal 9.05.........................................................................................54
17 Upgrade to Infragistics NetAdvantage..........................................................................54
18 Install SonicMQ................................................................................................................55
4 9.05.701
Epicor 9.05 Supplemental Installations Contents
18.1 Install Sonic on Windows.......................................................................................................................55

18.2 Install SonicMQ on Linux/UNIX...............................................................................................................56
18.2.1 Determine Your Security..............................................................................................................56
18.2.2 Install SonicMQ With Security Enabled.........................................................................................56
18.2.3 Install SonicMQ Without Security Enabled....................................................................................57
18.2.4 Download Latest Update File.......................................................................................................58
18.2.5 Install Sonic SP for Linux and UNIX...............................................................................................58
18.3 Set Up Sonic Test Environment...............................................................................................................59
18.4 Review Possible Installation Messages....................................................................................................59
18.4.1 Adapter .jms error in the AppServer log.......................................................................................59
18.4.2 Javax.jms Exception error in the AppServer log.............................................................................60
18.4.3 Javax.jms Security error in the AppServer log................................................................................60
18.4.4 General Error Message.................................................................................................................60
19 Install Progress OpenEdge 10.2A (Advanced/Manual).................................................61
19.1 Install Progress OpenEdge 10.2A............................................................................................................61
19.2 Install Progress OpenEdge 10.2A SP.......................................................................................................62
19.3 Install Progress OpenEdge 10.2A SP Hotfix.............................................................................................62
20 Configure Epicor Online Help.........................................................................................64
20.1 Configure Help for Virtual Directory and Server-side Search....................................................................64
21 Set Up Multi-Company Functionality.............................................................................66
21.1 Verify Multi-Site Management License....................................................................................................66
21.2 Verify SonicMQ Broker Status................................................................................................................66
21.3 Configure an External System Record.....................................................................................................67
21.4 Configure an External Company Record.................................................................................................68
21.5 Verify Your Startup Schedule.................................................................................................................69
21.6 Schedule the Multi-Company Server Process..........................................................................................70
21.7 Start the Multi-Company Process...........................................................................................................70
21.8 Review Multi-Company Log File.............................................................................................................72
21.9 Test the Communication........................................................................................................................72
21.10 Review Sonic Container Information....................................................................................................73
21.11 Review Validation Errors.......................................................................................................................73
21.12 Review Automatic Data Translations....................................................................................................74
21.13 Review Integrated Workbench.............................................................................................................75
21.14 Review Multi-Company Functionality...................................................................................................75
22 Troubleshooting..............................................................................................................77
22.1 Share the Epicor Folders.........................................................................................................................77
22.2 Verify Time Synchronization on Client and Server...................................................................................77
22.3 Change or Uninstall Epicor 9.05 Application..........................................................................................78
22.3.1 Add or Remove Programs and Features........................................................................................78
22.3.2 Repair or Reinstall Epicor 9.05 Application...................................................................................79
22.3.3 Uninstall Epicor 9.05 Application.................................................................................................79
22.3.4 Uninstall Epicor 9.05 Client..........................................................................................................80
9.05.701 5
Welcome and Introduction Epicor 9.05 Supplemental Installations
1 Welcome and Introduction
Welcome to the Epicor 9.05 Supplemental Installations Guide - Version 9.05.700. This guide helps you with the
supplemental installations after you have installed the Epicor 9.05 application system.
6 9.05.701
Epicor 9.05 Supplemental Installations Configure 64-Bit Environment (Windows 2008)
2 Configure 64-Bit Environment (Windows 2008)
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. This version must be enabled 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.
2.1 Enable ASP .NET 2.0 Application (64-bit only)
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. Select Enable 32-Bit Application from the drop-down
list.
4. Restart the Application Pool.
5. Expand the Default Web Site node. In the middle column, click Handler Mappings.
6. If these extensions are not mapped, you must manually add each one separately. To add the .htm extension,
in the right column, click Add Script Map.
a. Request path: *.htm
b. Executable: C:\Windows\Microsoft.NET\Framework\v2.0.50727\aspnet_isapi.dll
c. Name: htm.
d. Click OK.
7. To add the .html extension, in the right column, click Add Script Map.
a. Request path: *.html
b. Executable: C:\Windows\Microsoft.NET\Framework\v2.0.50727\aspnet_isapi.dll
c. Name: html.
d. Click OK.
8. Within IIS, right-click on Default Website and select Manage Web Site > Restart.
9.05.701 7
Install Epicor Administration Console Epicor 9.05 Supplemental Installations
3 Install Epicor Administration Console
Use these steps to install 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.
3.1 Uninstall Epicor Administration Console
If you have a previous version of Epicor Administration Console installed on your server, use these steps to uninstall
Epicor Administration Console.
1. Navigate to Start > All Programs > Epicor Software > Epicor 9.05 and select Epicor Utilities Installers.
2. In the Welcome to the Epicor Utilities Setup wizard, click Next.
3. In the Epicor Utilities Setup dialog, click the Install Administration Console button.
4. In the Welcome dialog, select the Remove Epicor Administration Console option. Click Finish.
Epicor Administration Console is uninstalled.
3.2 Install Epicor Administration Console
Use these steps to install the Epicor Administration Console on your server and/or on your Windows Admin
Workstation.
Note For Linux/UNIX environment, perform the following steps on your Windows Admin Workstation.
3. In the Epicor Utilities Setup dialog, click the Install Administration Console button to start the installation.
4. In the Welcome dialog, click Next.
5. In the Confirm Installation dialog, click Next. The files are installed.
6. When the installation is complete, click Close.
The Epicor Administration Console is now installed.
8 9.05.701
Epicor 9.05 Supplemental Installations Install BPM Server
4 Install BPM Server
Use these steps to install and configure your Epicor BPM Server.
4.1 Review BPM Server Prerequisites

Use this section to review the BPM Server component install prerequisites and options. The installation of BPM
Server components are required by .NET actions. See the Epicor application help topics for BPM Server if you
need more information on using .NET actions in BPM directives.
1. Verify that you have Microsoft Message Queuing (MSMQ) installed on your machine.
2. Review the BPM Server components. The components include:

• Web Services - Useful if you intend to expose BPM server functionality outside the intranet. In such a
configuration, the machine with BPM server resides behind the firewall and only HTTP protocol is available
for interaction with BPM server.
• Win Service - Used when the BPM server works in an internal enterprise network.
• Console Application - Recommended for debugging .NET actions in BPM directives.
3. When installing the BPM Server component on Windows Server 2008, Windows 2008 R2, or other Windows
64-bit operating system, the DefaultAppPool must be set to allow applications to run in 32-bit mode.
Prior to installing the BPM Server component, use the following steps to set the DefaultAppPool to run
applications in 32-bit mode:
a. Navigate to Start > Run.
b. Type inetmgr and click OK. Internet Information Services (IIS) Manager 7.0 starts. Version 7.0 is the
default version on the latest Windows operating systems.
c. In the Connections area, select Application Pools.
d. Right-click on DefaultAppPool and select Set Application Pool Defaults from the menu.
e. Set the Enable 32-Bit Applications setting to True.
f. Click OK.
4. If you want to use the BPMService without the Web Services, you can select to not install the Web Services
during the Epicor 9.05 installation. To do this:
a. In the Installation Type dialog, select the Custom option.
b. In the Custom Setup screen, clear the BPM Server Web Service feature to prevent the components
from being delivered.
9.05.701 9
Install BPM Server Epicor 9.05 Supplemental Installations
4.2 Install BPM Server Components

Use these steps to install Epicor BPM Server.
1. Navigate to the folder where the BPM Server components were delivered during the Epicor 9.05 installation.
For example, in a standard installation, the path is C:\Epicor\Epicor905\BPMServer.
Note If the BPM Server folder does not exist, navigate to Control Panel > Programs and Features.
Right-click on Epicor 9.05 and select Change. Use the Install Wizard to add the BPM Server feature
from the list of installable components.
2. If you want the BPM Server to be available on a different server, copy the BPM Server folder to another
server. If you want to run the BPM Server from the current server, you do not need to copy it.
3. Based on the operating system (32-bit or 64-bit) of your installation , double-click on

Epicor_BPM_Server_9_x64.msi or Epicor_BPM_Server_9_x86.msi. If you are on the Epicor server use
Epicor_BPM_Server_9_x64.
4. The installation programs starts. Follow the onscreen prompts to install the components.
Note If you are prompted with a message that "An attempt was made to load a program with an
incorrect format," then the server you are installing on does not have ASP.NET installed and enabled
for the default web site. See your Microsoft documentation for installing and enabling ASP.NET on
the server, and then run the BPM Server installation again.
10 9.05.701
Epicor 9.05 Supplemental Installations Install Epicor Enterprise Search
5 Install Epicor Enterprise Search
Use these steps to install and configure your Epicor Enterprise Search.
5.1 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 one of the following:

• SQL Server 2008 or SQL Server 2008 R2
• SQL Server 2008 Express
• SQL Server 2012
Note If you plan to use Epicor Replication Server, you must use SQL Server 2008, SQL Server 2008
R2 or SQL Server 2012. Epicor Replication Server does not support the SQL Server 2008 Express version.
2. Verify that the SQL Server installation has SQL and Windows Authentication enabled.
3. Verify that the server where Enterprise Search is installed also has SQL Server installed as the named or
primary instance. For example, if your server is named Candy, then SQL Server must be made available as
Candy, and not as a sub or separate installation. Note that the Epicor application SQL database can be
located on a remote server.
4. Verify you are running SQL Server locally.
5. Verify that the account you used to log into the system is trusted by SQL Server.
6. If you use SQL Server 2012, use the following steps to verify that the NT AUTHORITY\SYSTEM login account
has System Admin rights enabled.
a. Open SQL Server Management Studio and connect to your database.
b. Expand Security > Logins. Right-click on NT AUTHORITY\SYSTEM and select Properties.
c. In the Login Properties dialog, select Server Roles. In the server roles list, verify that sysadmin is selected.
Click OK.
d. Close SQL Server Management Studio.
9.05.701 11
Install Epicor Enterprise Search Epicor 9.05 Supplemental Installations
5.2 Create Back Ups (if Previous Version)
If you have a previous version of Epicor Enterprise Search installed, and you made modifications to existing
templates or created your own templates, use the following steps to create back ups.
1. On the server where Enterprise Search is installed, navigate to the folder where the Enterprise Search program
data files are located. For example, go to C:\ProgramData\EpicorSearch.
2. Create a backup of the following folders: Templates, Profiles, and Tuning.
5.3 Uninstall Epicor Enterprise Search (if Previous Version)
If you have a previous version of Epicor Enterprise Search installed on your server, use these steps to uninstall
Epicor Enterprise Search.
1. On the server where Epicor Enterprise Search is installed, navigate to Start > All Programs > Epicor
Software > Epicor 9.05 and select Epicor Utilities Installers.
3. In the Epicor Utilities Setup dialog, click the Install Epicor Enterprise Search button.
4. In the Welcome dialog, select the Remove Epicor Enterprise Search option. Click Finish.
Epicor Enterprise Search is uninstalled.
5.4 Install Epicor Enterprise Search Process
Use these steps to install Epicor Enterprise Search.
1. Log on to the server where you intend to install Enterprise Search.
3. On the Welcome to the Epicor Utilities Setup wizard, click Next.
4. On the Epicor Utilities Setup dialog, click the Install Enterprise Search button to start the installation.
5. On the Welcome dialog, click Next.
6. On the Confirm Installation dialog, click Next. The files are installed.
Epicor Enterprise Search is now installed. The installation location is C:\Program Files (x86)\Common Files\Epicor
Software Corporation\Epicor Enterprise Search.
12 9.05.701
Epicor 9.05 Supplemental Installations Install Epicor Enterprise Search
5.5 Configure Replication Server for Epicor Enterprise Search
This section is optional if you are using SQL Server for your Epicor 9.05 transactional database. When Epicor 9.05
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.05 application.
Note Refer to Replication Server documentation in the Replication Server snap-in for Admin Console and
in the Epicor 9.05 application for full details on how to assign replication profiles, configure replication
subscribers, and enable data replication. You can also refer to the Epicor Replication Server Install Guide,
available from the EPICweb Documentation site, for additional information.
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.05 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.05 application. This means that the Epicor 9.05 application, including Epicor
Web Access, must be running using the Epicor 9.05 transactional database and not using the replicated
database. If you need to run the Epicor 9.05 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.05 database for use as the subscriber database. To do this, use the default SQL script
located in the directory where your Epicor 9.05 application server is installed. For example, use \Epicor
Software\Epicor905\server\sql\Epicor905.sql.
4. Use the Replication Management Console to add this newly created database as a Functional subscriber.
Review the Epicor Database Replication Installation Guide for additional information.
5.6 Configure Epicor Enterprise Search
Use these steps to setup and configure Epicor Enterprise Search. To complete most of these steps, you use
Enterprise Search Management from the Epicor Administration Console.
1. Login to the Epicor Administration Console as a user who can authenticate to the Enterprise Search Server.
2. Open the Epicor Administration Console. To do this, navigate to Start > Programs > Epicor Software
> Epicor Administrative Tools > Epicor Administration Console.
3. If you did not previously have Enterprise Search installed or installed to a new search server, from the Help
menu, select Help Topics and follow the instructions in the Initial Configuration > Start Here topic. You
9.05.701 13
Install Epicor Enterprise Search Epicor 9.05 Supplemental Installations
are done with this procedure. However, if you previously installed Enterprise Search on the same server,
start instead with the remaining steps:
4. If the search server is not registered, right-click Enterprise Search Management and select Register
Search Server. Use the configuration wizard to enter the following:
a. On the Welcome page, review the process details. Click Next.
b. For the Server Registration, enter the Name of the server where the Enterprise Search Server components
are installed. Click Ping Server to validate the server name. For the Port enter the port number of the
Enterprise Search Server service. Keep the default of 9098 unless the server has been manually configured
to a different port. Click Validate Service to Continue to validate the port. If both validations are
successful, you can click Next.
c. You are prompted to deploy Web Application. Click Next.
d. Review the Search Database details, including the search Server Name and the Database used to build
the search index. Click Finish.
5. Right-click the computer name of the registered search server and select Delete Database. Right-click the
computer name of the registered search server and select Create Database.
Note You only need to create one database per Enterprise Search server. One database stores all
search data. Using the above step, a database named SearchIndexversion is created on the default
SQL Server instance on the server where the Enterprise Search server components are installed. If you
want to choose the SQL Server instance used for the search database and/or choose its name, see the
"Set SQL Server for Search Indexing" topic in the online help.
6. Right-click the computer name of the registered search server and select Delete Web Application (if the
web application exists). Right-click the computer name of the registered search server and select Create
Web Application.
7. In the online help, go to the Initial Configuration > Start Here topic.
a. Begin with step 2 if you creating a new search index definition
b. Begin with step 4 to create a new search index from a previous version search template. Your old
template definitions should be available if you installed the search server components to the same location
as you previously installed search server components. Old template definitions cannot necessarily be
expected to work without some adjustments.
14 9.05.701
Epicor 9.05 Supplemental Installations Install Embedded Education Courses
6 Install Embedded Education Courses
Use these steps to 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) with the
ASP.NET module enabled. If you are upgrading the Embedded Education Courses, you do not need to configure
the Embedded Education Courses client and license the Embedded Education Courses. Note that the Embedded
Education Courses must be installed in your training environment, not in your live production environment.
Note If you have a Linux / UNIX installation, you must first download the Epicor Education zipped package
prior to installation. To do this, log on to EPICweb and go to the Customer Portal Page. Navigate to Support
> Epicor 9 > Downloads > Epicor 9 > Version 9.05.700. Download the EpicorEducation.zip file into
the Epicor905 folder on your Epicor server. Extract the zip file. Verify that the Epicor Education folder is
extracted and is located in the Epicor905 folder. You can now use the steps in the following section to
install the Embedded Education Courses.
6.1 Install Embedded Education Courses
Use these steps to install the Embedded Education Courses using the Epicor Education Course Installer.
1. Verify that the ASP.NET module of your Windows Internet Information Services (IIS) installation is enabled.
Note If you want to install the Embedded Education Courses on a separate server, go to that server
and use remote access to navigate to the shared Epicor905 folder on your Epicor server. From that
remote shared folder, run the Epicor Utilities Installer.
4. On the Epicor Utilities Setup dialog, click Install Epicor Education Courses to open the Epicor Education
Course Installer.
Note You can also open the Epicor Education Course Installer by navigating to the Epicor Education
folder and running the EduCourseInstaller.exe file.
5. Verify that the Epicor 9.05 Education Course Installer program opens. The user interface looks different
based on your operating system.
6. Select the Web Site where you want to install the Education Courses. It is recommended that you select
the DefaultWebSite.
7. Select the App Pool to use for the Education Courses. You can either select an App Pool from the drop-down
list or create a new App Pool specific for the Embedded Education Courses.
If you are running IIS 6, you need to verify the App Pool settings. To do so:
a. Open the Internet Information Services Manager (IIS 6).
b. In the Connections tree view, select Application Pools.
9.05.701 15
Install Embedded Education Courses Epicor 9.05 Supplemental Installations
c. In the Application Pools list, select the application pool used by the Epicor Education virtual directory.
d. In the Action panel, click on Advanced Settings.
e. Verify that Integrated is selected as the Managed Pipeline Mode.
f. Verify that Enable 32-Bit Applications is set to True, if your system is a 64-bit server.
g. Click OK to close the dialog and save your changes.
h. Close the IIS Management panel.
8. 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 alias 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.
9. Enter the Directory. The directory can be any folder on the server. For example, if you have a directory on
your server where you host Web Content, such as C:\Inetpub\wwwroot, you can enter
C:\Inetpub\wwwroot\EpicorEducation to install the courses to that directory. If the directory does not
exist, the installer creates it. You can install a new batch of courses to an existing directory by using the
Browse button.
10. For the Server Name, enter the name of the server where your Epicor application is installed.
11. Enter the Port used by the AppServer. To find your port number:
a. Go to the Config folder on the server where your Epicor application is installed. For example, go to the
Epicor905\client\config folder.
b. 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 9411.
Note The Server Name and Port must point to a training database and not a live database within
your production environment.
12. 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 epicor / epicor.
13. 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.
14. After a message displays that the site has been created, close the Epicor Education Course Installer.
16 9.05.701
Epicor 9.05 Supplemental Installations Install Embedded Education Courses
6.2 Configure Embedded Education Courses 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:
a. 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 the previous section when you
ran the Education Course Installer program.
b. 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>
6.3 License Embedded Education Courses
Use these steps to license the Embedded Education Courses. License keys are specified by Education Course
module, not Epicor 9.05 modules.
Note You must retrieve your license information for your embedded courses when you access the embedded
education courses for the first time.
1. Open the Epicor 9.05 application.
2. On the Standard toolbar, click the Education Course button (student with a graduation cap). The Education
Course program opens.
9.05.701 17
Install Embedded Education Courses Epicor 9.05 Supplemental Installations
3. From the Actions menu, select one of the following options:
a. Load License from file. Choose this option to enter the name of the license file.
b. Enter License Keys. Choose this option to manually enter the key if you were sent a file that contains
your license keys. At the prompt, browse to the file and open it. Manually copy the license key details
from the file into your database. This step only has to be completed once and it is saved in the database.
c. 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 a Service Pack, reinstall them in the
same location on the server.
4. Click OK to complete the Embedded Education Courses 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.
18 9.05.701
Epicor 9.05 Supplemental Installations Install Epicor Information Worker
7 Install Epicor Information Worker
Use these tasks to install Epicor Information Worker.
7.1 Review Information Worker Server System Requirements
Verify that the server on which Information Worker Server will be installed complies with these requirements.
Tip Information Worker Server can be installed on the Epicor application server or on a separate server.
Item Requirement
Processor Pentium 4 or better. Dual processor recommended.
RAM 1 GB minimum, 2 GB recommended
Operating system Windows Server 2008 (32 or 64 bit) with the latest updates (R2 is supported). The
server should belong to a domain.
Required software Internet Information Service (IIS) and ASP.NET Windows components. See the
Windows documentation if you need help installing these components.
In the IIS configuration:
• Choose the Web Server role for the server.
• Select all of the IIS 6 Management Compatibility items when you are configuring
the web server features.
• Make sure you have not prohibited IIS from running ASP.NET under the Web
Service Extensions.
Required Software Microsoft .NET Framework Redistributable 4.0 (available from Microsoft Windows
update). Important: Install IIS before installing the .NET Framework.
7.2 Review Information Worker Client System Requirements
Verify that Information Worker Client workstations comply with these requirements.
Important The Information Worker Client installation must be run with local Administrator privileges.
Item Requirement
Processor PC with a Pentium 4 class processor, 1.4 GHz
9.05.701 19
Install Epicor Information Worker Epicor 9.05 Supplemental Installations
Item Requirement
RAM 1 GB
Operating system Windows XP Professional, Windows Vista Business or Windows 7.
Required software Microsoft .NET 4.0 Client Profile
Required software Microsoft Office 2007 or Microsoft Office 2010 (32 or 64 bit version)
Depending on which applications you wish to use with Information Worker,
install Outlook, Word and/or Excel during your Office installation.
Required software Microsoft Visual Studio 2010 Tools for Office. Note that this is provided
through the Epicor installation.
Connectivity http access to Information Worker Server
Optional software Epicor client to enable additional functionality.
7.3 Uninstall Previous Version
If you have a previous version of Epicor Information Worker Installed, use these steps to uninstall Information
Worker Server and the Information Worker Configuration Manager.
1. On the server where the Information Worker Server components are installed, select Start > Control Panel
> Programs > Uninstall a Program.
2. Select Epicor Information Worker Configuration Manager and click Uninstall.
3. Select Epicor Information Worker Server for Epicor and click Uninstall.
4. Select Epicor Information Worker Server Framework and click Uninstall.
5. Verify that the uninstallation was completed successfully.
7.4 Install Information Worker Components
7.4.1 Generate Server Components
Use these steps to generate server-side components required for the updatable Information Worker BAQs.
1. Log in to Epicor as an administrative user and navigate to System Management > Utilities > Updatable
BAQ Maintenance
2. Click ExportID.
20 9.05.701
3. For Basic Search, in the Query ID Starts With field type zIW.
4. Click Search. Click Select All and click OK.
5. Click the List sheet. From the Actions menu, select Regenerate All.
6. Repeat Steps 1 through 5 for each company in your Epicor installation.
7.4.2 Install Information Worker Server
Use these steps to install Information Worker Server Framework and Information Worker Server.
1. Log on to the server where you intend to install Information Worker Server.
4. On the Epicor Utilities Setup dialog, click the Install Epicor Information Worker Server button to start
the installation.
5. Click Install on the screen that states the Server Framework component will be installed.
The Framework Setup Wizard displays.
6. On the Welcome screen, click Next.
7. On the Select Installation Address screen:
a. For Site, leave the Default Web Site selected or choose a different web site.
b. For Virtual directory, leave the default name, or type the name you want to be used for the information
worker virtual directory (the name is not visible to end users).
c. Click Next.
8. On the Error Form Email Address screen:
a. Type a single email address that will go to a person or group responsible for administrating the Information
Worker installation.
b. Leave the subject line as is or change as desired. Click Next.
9. Click Next to start the installation.
10. Click Close when the Information Worker Framework installation finishes.
The Information Worker Server for Epicor installation Welcome screen displays.
11. Click Next begin the installation.
12. Click Next on the Confirm Installation screen.
13. Click Close when the Information Worker Server installation finishes.
9.05.701 21
Install Epicor Information Worker Epicor 9.05 Supplemental Installations
7.4.3 Install Information Worker Configuration Manager
Use these steps to install Information Worker Configuration Manager.
1. Log on using a Windows account that is a member of the Administrators group on the domain of the
server on which Information Worker Server is installed.
2. Insert the Information Worker product compact disc. Optionally copy the installation files from the disc to
the server.
3. Open Windows Explorer and navigate to the location of the installation files. Open the
ConfigurationManager folder and double-click Setup.exe.
4. If you are prompted for the MMC 3.0 pre-requisite:
a. Click Yes to go the Microsoft site.
b. Download and run the MMC update.
c. Go back to Step 3 and restart the Information Worker Configuration Manager installation.
5. Click Next on the Welcome screen.
6. Click Next on the Confirm Installation screen.
7. Click Close when the Information Worker Configuration Manager installation finishes.
7.4.4 Set Up Information Worker Server
These steps guide you to using the procedures in the Information Worker Configuration Manager Online Help
to perform the initial setup of Information Worker Server.
1. To start Information Worker Configuration Manager, navigate to Start > (Settings) Control Panel >
Administrative Tools > Information Worker Configuration Manager.
2. From the Help menu, select Help Topics.
3. Expand Information Worker Configuration Manager in the table of contents.
4. Follow the procedures under the Initial Configuration topic.
7.4.5 Set Up Information Worker Clients
Use these steps to configure client workstations to run Information Worker.

Important The Information Worker client installation must be run with local Administrator privileges.
1. In your Epicor installation, ensure each Information Worker user is set up as an Epicor user and that the
Domain and Domain ID in their user record matches the domain and login name of their Windows credentials.
2. Ensure each client workstation has Office 2007 or 2010 installed.
22 9.05.701
Note During the installation, the user will be given an opportunity to select the Office applications
(Outlook, Word, and/or Excel) that will be configured to interact with Information Worker.
3. The web address you chose when installing the Information Worker Server, should be sent to the email
accounts on the prepared workstations. Direct the users to go to the web address and to follow the installation
instructions found there.
Note If you accepted the defaults when installing the Information Worker Server, the web address
would be: http://servername/informationworker.
Note There are links on the client installation download site for troubleshooting a client install
7.4.6 Troubleshooting Installation Errors
This table provides solutions to common Information Worker Server installation errors.
Problem Cause Possible Resolutions
During the server Install could not Go to C:\Inetpub\wwwroot\InformationWorker\App_Data\

installation, an error set error email
Note that you may have changed the InformationWorker portion
displays similar to: properties.
of the above address during installation. Use Notepad.exe to edit
"There were errors setting the Configuration.xml file.
configuration values.
Search for ErrorFormEmailAddress and change the value of the
Installation will attempt to
email address to reflect the email account you want to use. Exit
complete, but you may
Notepad and save the file.
need to manually correct
some of the configuration
values."
Warning that ASP.NET Your IIS Run the aspnet_regiis.exe command for .NET 4.0 as detailed in
does not appear to be metabase is the Microsoft Knowledge Base article
registered in IIS. missing the http://support.microsoft.com/default.aspx?scid=kb;en-us;306005.
entries for the
ASP.NET .dll
filters.
During the server Anonymous Click Start > Run > inetmgr to open IIS manager. Go to the
installation, an error access is not virtual directory you configured for Information Worker (default
displays similar to: enabled or the name: InformationWorker).
Information
"There were errors setting • Make sure Anonymous access is enabled under
Worker virtual
web site values. Authentication.
directory is not
Installation will attempt to
using the • Under Basic Settings verify that the Information Worker
complete, but you may
Information application pool is selected.
need to manually set the
Worker
ASP.NET version, Directory
application pool.
Security, and/or create an
application pool."
9.05.701 23
Install Epicor DB Replication Epicor 9.05 Supplemental Installations
8 Install Epicor DB Replication
Use these steps to install Epicor DB Replication.

Note Based on the release, you may have to also install an Epicor DB Replication Hot Fix after installing
Epicor DB Replication.
1. Log on to EPICweb and go to the Customer Portal Page. Navigate to Documentation > Epicor 9.
Note You can use this link: https://epicweb.epicor.com/doc/Pages/Epicor9.aspx
2. Expand the release. For example, expand Release 9.05.70x
3. Download the Epicor Replication Server Install Guide to your workstation.
4. Use the instructions in the Epicor Replication Server Install Guide to install and configure Epicor DB
Replication.
24 9.05.701
Epicor 9.05 Supplemental Installations Install Epicor SQL Server Reporting (SSRS)
9 Install Epicor SQL Server Reporting (SSRS)
Use these steps to install Epicor SQL Server Reporting Service (SSRS). During the installation, the report portal
and Report Service Monitor Service are created. Epicor SQL Server Reporting Services (SSRS) is a reporting
technology that provides additional functionality not currently available with the current Crystal Reports client
runtime. The installation of SSRS is optional.
9.1 Verify SSRS Prerequisites
Use these steps to verify the requirements before you begin the installation of SSRS.
1. Verify that you are using SQL Server 2008 or SQL Server 2012.
2. Verify that your SQL Server 2008 or 2012 installation has Reporting Services enabled. Reporting Services
must be installed in Native mode. To do this:
a. Navigate to Start > All Programs > Microsoft SQL Server 20xx > Configurator Tools > Reporting
Services Configuration Manager.
b. Connect to the Reporting Services.
c. In Current Report Server information, verify that Report Server Mode = Native.
3. Specify your SSRS configuration for your company. To do this:
a. Open the Epicor 9.05 application. Select System Management > Company Maintenance > Company.
Select the System sheet. Locate the Form Print Options section.
b. If you want your company name to display on each report, select the Print Company Name check box.
c. Enter a value in the Text Report Lines/Page to specify the number of lines to print on each page for
text-based reports.
d. In the Allowed Report Style field, specify which reporting styles are available for your company. For
example, you can select Crystal and SSRS, SSRS Only or Crystal Only.
e. In the Work Station Method field, select an option to define your work station method, such as User
ID or Machine Name + User ID.
f. Enter your Epicor SSRS URL. This URL defines the SSRS Server used by your company. For example, your
URL may look similar to the following: http://SSRS905/EpiSSRSPortal.
9.05.701 25
Install Epicor SQL Server Reporting (SSRS) Epicor 9.05 Supplemental Installations
9.2 Enable IIS 6 Management Compatibility
If you are running IIS 7, use these steps to enable IIS 6 Management Compatibility. The steps are different based
on your operating system.
9.2.1 Using Vista and Windows 7
1. Open the Control Panel. Click Programs or Programs and Features.
2. Select the Turn Windows features on or off option
3. Expand Internet Information Services > Web Management Tools > IIS 6 Management Compatibility.
4. Verify that IIS Metabase and IIS 6 configuration compatibility is selected.
5. Exit the Control Panel.
9.2.2 Using Server 2008
1. Run Server Manager.
2. From Roles > Web Server (IIS), right-click and select Add Role Services. Note that this node is only present
when IIS is already installed.
3. Expand Management Tools > IIS 6 Management Compatibility.
4. Verify that IIS 6 Metabase Compatibility is installed.
5. Exit the Server Manager.
9.3 Install Microsoft Report Viewer 2010 Redistributable Package
Use the following steps to download and install the latest Microsoft Report Viewer 2010 Redistributable Package
from the Microsoft Download Center website.
1. Go to the Microsoft Download Center to download the Microsoft Report Viewer 2010 Redistributable
Package. You can use this link: http://www.microsoft.com/downloads/en/confirmation.aspx?familyId=a941
c6b2-64dd-4d03-9ca7-4017a0d164fd&displayLang=en
2. Download the latest version of the Microsoft Report Viewer 2010 Redistributable Package to your server.
3. Use the instructions provided on the website to guide you through the installation process.
26 9.05.701
9.4 Configure Epicor SQL Report Monitor
Use these steps to configure the Epicor SQL Report Monitor.
1. Go to the SSRS directory on the server where your Epicor application is installed. Example:
C:\Epicor\Epicor905\SSRS.
2. Copy the EpiSSRS.msi file to the server where your Microsoft SQL Server 2008 or SQL Server 2012 is located.
3. Double-click the EpiSSRS.msi file on the server where your Microsoft SQL Server 2008 or SQL Server 2012
is located.
5. On the Select Installation Address dialog, enter the following:
a. Site. Enter the web location site to install Epicor SQL Report Monitor. The default is Default Web Site.
b. Virtual Directory. Enter the virtual directory. For example, EpiSSRSPortal. The virtual directory is created
under inetpub/wwwroot, unless a specific path is specified.
c. Application Pool. From the drop-down list, select your application pool. Note that only integrated .NET
AppPool types are displayed. For IIS 7 and above, if the drop-down is empty, use your IIS Manager to
create an integrated . NET application pool.
d. Click Next. The web location is created.
7. The Configuration Utility opens to begin the SSRS configuration. On the Set up the Epicor SQL Report
Monitor Service User Account dialog, select Local System Account or This Account. If you select This
Account, you must define the user name, domain, and password. For example, create a user name such
as Administrator. Click Next.
8. If prompted with the Configure the SQL Server Report Portal dialog, enter the following:
a. Epi SSRS site. Enter a site that is a valid URL. For example, http://localhost/EpiSSRSPortal.
b. Epi SSRS path. Enter a path that already exists and contains a web.config file. For example,
C:\inetpub\wwwroot\EpiSSRSPortal\.
c. Click Next.
9. On the Configure the SQL Report Server dialog, enter the following information:
a. SSRS ReportServer site. This site was created when you installed Microsoft SQL Server with Reporting
Services enabled (SSRS). For example, enter a URL such as: http://localhost/reportserver. This is listed as
the Web Service URL in the Reporting Services Configuration Manager.
b. User name. Enter a user name that has administrative rights.
c. Domain. Enter your domain identifier. For example, localhost.
d. Password. Enter a password and confirmation password for the user.
9.05.701 27
e. Rendered Format. Use the drop-down to select a format type. Types include HTML, PDF, Excel and
Word.
f. Show Report Parameters. Select this check box if you want the report parameters to display on the
report. Note that you can also modify this setting by editing the "IsShowRptParameters" parameter in
the web.config file, which is located in the root of the EWA web site.
g. Developer mode. Select this check box if you want to run SSRS in developer mode.
h. Click Next.
10. On the Enter the application server information dialog, enter the following:
a. Application Server. Enter the URL for the Epicor application. For example, enter Epicor9servername.
b. Port. Enter the port for the application server.
c. User name. Enter a user name for logging into the Epicor application.
d. Password. Enter a password and confirmation password for the user.
e. Click Next.
11. On the Enter the mail configuration information dialog, enter your company's SMTP values. If you do not
know your this information, use your Epicor application to open Company Configuration and review the
System values.
a. SMTP server. Enter the name of the SMTP server.
b. SMTP port. Enter your port number. The port value is >0 and < 65536.
c. Email from. Enter the originating email address.
d. Click Next.
12. To configure the Windows Service, you can accept the defaults, or enter your own values. The defaults
include:
a. Concurrent agents. Specifies the number of agents allowed to run simultaneously. Default is 5. Value
is > 0 and <=20.
b. Polling interval. Specifies the number of seconds to wait between listening for activity. Default is 3.
Values are >0 and <1200 seconds, or 20 minutes.
c. Login interval. Specifies the number of seconds to wait before checking on the Appserver, if it is not
started. Default is 100. Values are >0 and <1200 seconds, or 20 minutes.
d. Purge interval. Specifies the number of days to wait before the system automatically deletes the data.
Default is 10. Values are >1 and <99 days.
e. Click Next.
13. To configure the server printers, do the following:
a. Click on the printer button (paper and green plus sign) on the right.
b. Enter the print identifier. For example, enter \\servername\printername
28 9.05.701
c. Click OK.
d. Click Next.
14. On the Configure the Epicor SQL Report Monitor dialog, enter the following:
a. SSRS Script Location. Enter the server location where your script file, such as the RS Scripter Load All
Items.cmd, is located. For example, enter C:\Epicor\Epicor905\SSRS\.
b. RS.EXE Location. Enter the location where the report service file (RS.EXE) is located. For example, enter
C:\Program Files x86\Microsoft SQL Server\100\Tools\Binn\RS.EXE
c. SSRS Root Folder. Enter the root folder location where you want to deploy the reports. For example,
enter "905700" if you want the reports to deploy to the 905700\Reports folder. If you leave the field
blank, the root folder will be the home page of the report server and the reports will deploy to the
Reports folder.
d. To deploy all the reports that are in the SSRS Script location, select the Deploy Epicor SSRS Reports
Now check box.
e. SSRS Install Location. Enter the location of the SSRS installation. For example, based on your SQL
version, enter one of the following:
• SQL Server 2008. C:\Program Files\Microsoft SQL Server\MSRS10.MSSQLSERVER\Reporting
Services\ReportServer
• SQL Server 2008 R2. C:\Program Files\Microsoft SQL Server\MSRS10_50.MSSQLSERVER\Reporting
• SQL Server 2012. C:\Program Files\Microsoft SQL Server\MSRS11.MSSQLSERVER\Reporting
Note If you enter an SSRS Install Location, the SSRS server will be configured with the following:
edits the rssrvpolicy.config file, creates a LAN folder for the language files, and copies the
CLSEpicor.dll and EpiNum2Words.dll files into the bin folder.
f. Click Finish.
15. If you selected the Deploy Epicor SSRS Reports Now check box, you are prompted with the message
stating that deploying the Epicor SSRS Report to Microsoft SQL Service Report Service may take a long time.
You are asked whether you want to run this process in a separate thread and not display the log file.
a. Yes. Click Yes to run the process now in a separate thread. After clicking Yes, the process exits and the
Epicor SSRS reports are deployed on a separate thread. To verify the report deployment, review the RS
Scripter Load Log file. This log file is located in the same location as the RS Scripter Load All Items.cmd
file, for example C:\Epicor\Epicor905\SSRS.
b. No. Click No to wait until the deployment of the Epicor SSRS reports is complete. After clicking No, the
process waits for the reports to complete and then the RS Scripter Load Log file is displayed.
16. If prompted, click Close to exit the Epicor SQL Report Monitor installation.
17. To verify the installation was successful, start the Epicor SQL Report Monitor Service. To do this:
a. Navigate to Start > Control Panel > Administrative Tools > Services.
b. Select Epicor SQL Report Monitor Service.
9.05.701 29
c. Click Start this Service.
d. Navigate to Start > Control Panel > Administrative Tools > Event Viewer.
e. Expand the Applications node.
f. Verify that EpiSSRS is available.
18. To verify that your reports open correctly, open a report. To do this:
a. Go to your Reports site. For example, http://localhost/Reports
b. Click on the Reports folder. This folder was populated with all the reports located in SSRS\Reports folder.
c. Select a report to open. Verify it opens correctly.
9.5 Maintain Epicor SQL Report Monitor Configuration
After the installation, if you need to make additional changes to the Epicor SQL Report Monitor configuration
settings, you can use the Epi SSRS Service utility.
1. Verify that you have Administrator rights. If you run the utility with UAC turned on, you are prompted to
login as an Administrator to run the application
2. Go to Start > Programs > Epicor Software > Epicor SQL Report Monitor. Select the Configure Epi
SSRS Service.
3. Navigate to Start > Control Panel > Administrative Tools > Event Viewer. Select EpiSSRS and verify it
says Service is starting and Initial login to AppServer.
4. Exit from the Configure Epi SSRS Service.
9.6 Manually Install Custom Assembly DLL File (Report Server)
If you did not specify the SSRS Install Location during the SSRS installation, you need to use these steps to
manually install custom assembly DLL file. Manual installation includes copying the .dll file and editing the .config
file.
1. Go to the Assembly folder on the server where SSRS is installed. For example, go to
C:\Epicor\Epicor905\SSRS\Epicor SSRS Assembly.
2. Copy the CLSEpicor.dll file to the location where your Microsoft SQL Server Reporting Server files are
installed. For example, copy the file to: C:\Program Files\Microsoft SQL Server\<Instance Name>\Reporting
Services\ReportServer\bin folder.
Note The name of your <Instance Name> folder depends on your installation location or other Epicor
tools that have already been installed.
3. Go to the C:\Program Files\Microsoft SQL Server\<Instance Name>\Reporting Services\ReportServer folder.
30 9.05.701
4. Locate the rssrvpolicy.config file. Create a backup copy of the file.
5. Open the rssrvpolicy.config file with a text editor. In the config file, locate the following code:
<CodeGroup class="FirstMatchCodeGroup" version="1"
PermissionSetName="Nothing">
<IMembershipCondition class="AllMembershipCondition"
version="1"/>
6. Paste the following code right below the code you located in the previous step:
<CodeGroup
class="UnionCodeGroup"
version="1"
PermissionSetName="FullTrust"
Name="MyCodeGroup"
Description="Code group for my data processing extension">
<IMembershipCondition
class="UrlMembershipCondition"
version="1"
Url="C:\Program Files\Microsoft SQL Server\MSRS10.MSSQLSERVER\Reporting Ser
vices\ReportServer\bin\CLSEpicor.dll"/>
</CodeGroup>
Note You may need to change the URL based on the location where the ReportServer\bin folder
is located on your server.
7. In the code, locate the description:

Description="This code group grants default permissions for code in report
expressions and Code element."
8. In the line above this description, change PermissionsSetName = Execution to PermissionSetName =

FullTrust. This enables the expressions in the report to access the configuration file and call the .dll file.
9.05.701 31
Install Epicor Mobile Access Epicor 9.05 Supplemental Installations
10 Install Epicor Mobile Access
Use these steps to install and configure Epicor Mobile Access.
10.1 Uninstall Epicor Mobile Access
If you have a previous version of Epicor Mobile Access installed on your server, use these steps to uninstall Epicor
Mobile Access.
3. In the Epicor Utilities Setup dialog, click the Install Epicor Mobile Access button.
4. In the Welcome dialog, select the Remove Epicor Mobile Access option. Click Finish.
Epicor Mobile Access is uninstalled.
10.2 Install Crystal .NET SDK Runtime and Crystal Reports Server 2011
If you use report generation from Epicor Web Access or Epicor Mobile Access, you must install Crystal .NET SDK
Runtime and Crystal Reports Server 2011. Note that Crystal Reports Runtime must be installed on the web server
that is hosting Epicor Web Access or Epicor Mobile Access.
10.2.1 Install Crystal .NET SDK Runtime
Use the following steps to install Crystal .NET SDK Runtime. This component must be installed on the web server
that is hosting Epicor Web Access or Epicor Mobile Access. Crystal .NET SDK Runtime can be installed on Windows
Server 2008.
1. Log on to EPICweb and go to the Customer Portal Page. Navigate to Support > Epicor 9 > Downloads.
Note You can use this link: https://epicweb.epicor.com/Support/epicor9/Downloads
2. Navigate to Epicor 9 > Version 9.05.700 > Third Party Products > Crystal.
3. Download the latest Crystal .NET SDK Runtime file from EPICweb to your workstation. For example, download
Crystal Reports Runtime for EWA-EMA.zip.
4. Navigate to the downloaded file. Based on your environment, extract one of the following files:
• For 32-bit environments, extract SBOP BI PLATFORM 4.0 SP2 ENTER.NET SDK RUNTIME WIN (32B).ZIP
32 9.05.701
Epicor 9.05 Supplemental Installations Install Epicor Mobile Access
5. In the extracted SBOP* folder, navigate to DATA_UNITS\BusinessObjectsRuntimeXX folder and run the
setup.exe file.
6. Select the setup language. For example, select English. Click OK.
7. In the Prerequisite checking window, review the statuses of the required prerequisite components.
Installation cannot proceed until all critical required prerequisites are met.
• If one or more statuses are "Missing", click the prerequisite component to see the instructions on how
to resolve the issue.
• If all statuses are "Succeeded", click Next to continue the installation.
8. A Welcome to the installation wizard window appears. Click Next. Click Next.
9. Review the license agreement, and select the I accept the License Agreement check box. Click Next.
10. In the Specify the destination window, you can click Browse to select the location where the application
will be installed, or you can select the default location: C:\Program Files (x86)\SAP BusinessObjects\. Click
Next.
11. In the Start Installation window, click Next.
12. The installation proceeds. When it is finished, click Finish.
10.2.2 Install Crystal Reports Server 2011
Use these steps to install the latest version of the Crystal Reports Server 2011 SP2 on your server. This component
can be installed either on the same server as the Epicor Web Access forms, if Windows 2008 is used for both
Epicor Web Access and Crystal Reports, or on another server within the trusted domain.
3. Download the latest Crystal Reports Embedded Server file to your workstation. For example, download
Crystal Reports 2011 Embedded Server SP2.zip .
4. Navigate to the downloaded file. Extract the .zip file contents.
5. Move the extracted files to the report server where the file are to be installed.
6. Navigate to the extracted file folder. Run the Setup.exe file.
7. The Setup window appears. Select your language. Click OK.
8. The Welcome window appears. Click Next.
9. If prompted with a prerequisite checklist, review the status of each component. Click Next.
10. Review the license statement and select to accept it. Click Next.
9.05.701 33
11. In the User Information dialog, enter your Full Name, Organization and Product Keycode.
Note The Product Keycode is listed in the license key.txt file which is located in the same folder
as the Setup.exe file.
12. Specify the destination installation folder. Click Next.
13. Select one or more language packs to install. The English language is selected by default. Click Next.
14. Select which features you would like to install. Click Next.
15. Click Next to confirm to start the installation. A meter displays the progress.
16. When completed, click Close.
17. You need to set the Report Directory of the Central Configuration Manager. To do this, do the following:
a. Navigate to Start > BusinessObject XI 3.1 > Crystal Report Embedded Server 2011 > Central
Configuration Manager.
b. Stop the Report Application Server 12.
c. Right-click on Report Application Server 12 and select Properties.
d. In the Report Application Server 12 Properties window, select Parameter.
e. In Option Type, select Server.
f. For the Report Directory enter the value: C:\.
g. Restart the Report Application Server 12.
The installation of the Crystal Reports Server 2011 is complete.
10.3 Enable IIS 6 Management Compatibility
If you are running IIS 7, use these steps to enable IIS 6 Management Compatibility. The steps are different based
on your operating system.
10.3.1 Using Vista and Windows 7
1. Open the Control Panel. Click Programs or Programs and Features.
2. Select the Turn Windows features on or off option
3. Expand Internet Information Services > Web Management Tools > IIS 6 Management Compatibility.
4. Verify that IIS Metabase and IIS 6 configuration compatibility is selected.
5. Exit the Control Panel.
34 9.05.701
10.3.2 Using Server 2008
1. Run Server Manager.
2. From Roles > Web Server (IIS), right-click and select Add Role Services. Note that this node is only present
when IIS is already installed.
3. Expand Management Tools > IIS 6 Management Compatibility.
4. Verify that IIS 6 Metabase Compatibility is installed.
5. Exit the Server Manager.
10.4 Install Epicor Mobile Access Process
Use these steps to install Epicor Mobile Access.
1. In order to use Epicor Mobile Access, a license must be imported. Verify that the Epicor Mobile Access license
was imported using the Epicor Administration Console. For new installations, the instructions for importing
the license are located in the Epicor 9.05 Installation Guide in the Post-Installation > Prepare Your Data >
Import License Codes section.
4. On the Epicor Utilities Setup dialog, click Install Epicor Mobile Access to open the Epicor Mobile Access
Installer.
5. On the Welcome to the Epicor Mobile Access Setup wizard, click Next.
6. On the Application Server Connection dialog, enter the name of the Application Server. For example,
enter the server name that is hosting the Epicor application.
7. Enter the Port number for the Epicor application connection. This port must allow communication between
the Epicor Mobile Access server and the Epicor application server. Click Next.
8. On the Select Installation Address dialog, use the drop-down menu to select a Site. This is the site configured
in IIS. The default is Default Web Site.
Note If you need to create a site in IIS, refer to your Microsoft documentation.
9. Enter the Virtual Directory name for the Epicor Mobile Access application. The default is EpicorMobileAccess.
The name can be changed to any name allowed in IIS. If the default is accepted, a virtual directory is created
in IIS with a physical path and folder located under the \inetpub\wwwroot folder.
10. Use the drop-down menu to select an Application Pool that is configured in IIS. Click Next.
Note If you need to create an application pool in IIS, refer to your Microsoft documentation.
9.05.701 35
11. On the Confirmation dialog, click Next to begin the installation. Epicor Mobile Access is installed.
10.5 Configure Epicor Mobile Access
Use these steps to configure Epicor Mobile Access.
10.5.1 Configure EMA User
Use these steps to configure Epicor Mobile Access User options.
1. Open the Epicor 9.05 application.
2. Navigate to System Management > Company Maintenance and open the User program.
3. Select a User Id that requires ability to use Epicor Mobile Access on supported mobile devices. Click the
Options tab.
4. Select the Allow Mobile Access check box.
5. Click Save on the Standard toolbar.
6. If you want to make an Epicor application dashboard available for a mobile device, review the Create Mobile
Device Dashboards in the Epicor application help.
10.5.2 Configure EMA Reporting
Use these steps to configure Epicor Mobile Access reporting options so that BAQ reports can be added to the
Epicor Mobile Menu.
1. Navigate to the Epicor Mobile Access virtual directory. For example, if your Epicor Mobile Access was
installed to IIS, the default directory is: c:\inetpub\wwwroot\EpicorMobileAccess.
2. With a text editor, open the web.config file. Edit the following nodes:
a. <add key="ReportAppServer" value=""/>; edit the value with the Crystal Report Application Server
name
b. <add key="EmailHostName" value=""/>; edit the value with the SMTP server name
3. Save and close the web.config file.
10.5.3 Assign Data Folder Properties and Sharing
Use the following steps to assign required properties and sharing to the Data folder so that the ASP.NET account
has write access. Note that the group names may be different for IIS6 and IIS7.
1. Navigate to the Epicor Mobile Access\Data virtual directory. For example, if your Epicor Mobile Access
was installed to IIS, the default directory is: C:\inetpub\wwwroot\EpicorMobileAccess\Data.
36 9.05.701
2. Right-click on the Data folder and select Properties.
3. Click the Security tab. Select the IIS_WPG group (IIS6) or IIS_IUSRS group (IIS7) from the Group or user
names list.
4. Click the Edit button. Re-select the IIS_WPG group (IIS6) or IIS_IUSRS group (IIS7).
5. In the Permissions for [group] list, select the Modify and Write check boxes in the Allow column.
Note The selected group now has Allow selected for Modify, Read & Execute, List Folder Contents,
Read, and Write.
6. Click OK until you exit.
7. Right-click on the Data folder. Based on your operating system, do one of the following:
• Select Share. Select the Share button. After the share is complete, click Done
• Select Sharing and Security. Select Share this folder. Click OK.
9.05.701 37
Install Epicor Sharepoint Publisher Epicor 9.05 Supplemental Installations
11 Install Epicor Sharepoint Publisher
Use these steps to install Epicor Sharepoint Publisher on your server. Note that if you create a new Web Application
on the Sharepoint Server after Epicor Sharepoint Publisher has already been installed, you must reinstall Epicor
Sharepoint Publisher in order for the new site to see Epicor web parts.
11.1 Uninstall Epicor Sharepoint Publisher
If you have a previous version of Epicor Sharepoint Publisher installed on your server, use these steps to uninstall
Epicor Sharepoint Publisher.
1. Select Start > Control Panel > Programs > Uninstall.
2. Select Epicor Sharepoint Publisher and click Remove.
11.2 Install Epicor Sharepoint Publisher
Use these steps to install Epicor Sharepoint Publisher on your server.
1. Log on to the server where you intend to install Epicor Sharepoint Publisher.
Note If you want to install Epicor Sharepoint Publisher on a separate server, go to that server and
use remote access to navigate to the shared Epicor905 folder on your Epicor server. From that remote
shared folder, run the Epicor Utilities Installer.
4. On the Epicor Utilities Setup dialog, click the Sharepoint Publisher 32 Bit or Sharepoint Publisher 64
Bit button to start the installation.
6. Specify the folder for the installation of Epicor Sharepoint Publisher. Select Everyone as the user of the
computer. Click Next.
The Epicor Sharepoint Publisher functionality is now installed.
38 9.05.701
Epicor 9.05 Supplemental Installations Install and Deploy Epicor Web Access
12 Install and Deploy Epicor Web Access
Use these steps to install and deploy Epicor Web Access using a Windows 2008 based Internet Information Server
(IIS). The Epicor Web Access forms and components are an optional installation and are required only if
Browser-based access to your Epicor 9.05 environment is desired.
Note While it is possible to deploy the Epicor Web Access forms on your Windows based Epicor 9.05
Server, it is not recommended. For optimal performance and ease of maintenance, a separate Internet
Information Server is recommended.
12.1 Install Crystal .NET SDK Runtime and Crystal Reports Server 2011
If you use report generation from Epicor Web Access or Epicor Mobile Access, you must install Crystal .NET SDK
Runtime and Crystal Reports Server 2011. Note that Crystal Reports Runtime must be installed on the web server
that is hosting Epicor Web Access or Epicor Mobile Access.
12.1.1 Uninstall Previous Versions of Crystal Runtime
Use the following steps to uninstall any previous version of Crystal Runtime.
1. Navigate to Start > Control Panel > Programs > Uninstall a Program.
2. Select Crystal Reports .NET Runtime and click Uninstall.
12.1.2 Install Crystal .NET SDK Runtime
Use the following steps to install Crystal .NET SDK Runtime. This component must be installed on the web server
that is hosting Epicor Web Access or Epicor Mobile Access. Crystal .NET SDK Runtime can be installed on Windows
Server 2008.
3. Download the latest Crystal .NET SDK Runtime file from EPICweb to your workstation. For example, download
Crystal Reports Runtime for EWA-EMA.zip.
4. Navigate to the downloaded file. Based on your environment, extract one of the following files:
9.05.701 39
Install and Deploy Epicor Web Access Epicor 9.05 Supplemental Installations
5. In the extracted SBOP* folder, navigate to DATA_UNITS\BusinessObjectsRuntimeXX folder and run the
setup.exe file.
6. Select the setup language. For example, select English. Click OK.
7. In the Prerequisite checking window, review the statuses of the required prerequisite components.
Installation cannot proceed until all critical required prerequisites are met.
• If one or more statuses are "Missing", click the prerequisite component to see the instructions on how
to resolve the issue.
• If all statuses are "Succeeded", click Next to continue the installation.
8. A Welcome to the installation wizard window appears. Click Next. Click Next.
9. Review the license agreement, and select the I accept the License Agreement check box. Click Next.
10. In the Specify the destination window, you can click Browse to select the location where the application
will be installed, or you can select the default location: C:\Program Files (x86)\SAP BusinessObjects\. Click
Next.
11. In the Start Installation window, click Next.
12. The installation proceeds. When it is finished, click Finish.
12.1.3 Uninstall Previous Version of Crystal Embedded Server
Use the following steps to uninstall any previous version of Crystal Embedded Server.
1. Navigate to Start > Control Panel > Add or Remove Programs.
2. Select Crystal .NET Embedded Server and click Remove.
12.1.4 Install Crystal Reports Server 2011
Use these steps to install the latest version of the Crystal Reports Server 2011 SP2 on your server. This component
can be installed either on the same server as the Epicor Web Access forms, if Windows 2008 is used for both
Epicor Web Access and Crystal Reports, or on another server within the trusted domain.
3. Download the latest Crystal Reports Embedded Server file to your workstation. For example, download
Crystal Reports 2011 Embedded Server SP2.zip .
4. Navigate to the downloaded file. Extract the .zip file contents.
5. Move the extracted files to the report server where the file are to be installed.
40 9.05.701
6. Navigate to the extracted file folder. Run the Setup.exe file.
7. The Setup window appears. Select your language. Click OK.
9. If prompted with a prerequisite checklist, review the status of each component. Click Next.
10. Review the license statement and select to accept it. Click Next.
11. In the User Information dialog, enter your Full Name, Organization and Product Keycode.
Note The Product Keycode is listed in the license key.txt file which is located in the same folder
as the Setup.exe file.
12. Specify the destination installation folder. Click Next.
13. Select one or more language packs to install. The English language is selected by default. Click Next.
14. Select which features you would like to install. Click Next.
15. Click Next to confirm to start the installation. A meter displays the progress.
16. When completed, click Close.
17. You need to set the Report Directory of the Central Configuration Manager. To do this, do the following:
a. Navigate to Start > BusinessObject XI 3.1 > Crystal Report Embedded Server 2011 > Central
Configuration Manager.
b. Stop the Report Application Server 12.
c. Right-click on Report Application Server 12 and select Properties.
d. In the Report Application Server 12 Properties window, select Parameter.
e. In Option Type, select Server.
f. For the Report Directory enter the value: C:\.
g. Restart the Report Application Server 12.
The installation of the Crystal Reports Server 2011 is complete.
12.2 Configure Forms and Components
The Epicor Web Access forms and components are delivered as part of the Epicor application server installation.
Use the following steps to configure those forms and components.
1. Go to the /Epicor Web Access folder on your server. It is located at the same folder level as the
/Administration, /Client, /Server, and /Help folders.
9.05.701 41
2. Copy the entire /Epicor Web Access folder to the machine with the Internet Information Server (IIS) that
will host your Epicor Web Access web site.
3. Run the pre-installation configuration process. To do this, go to the /Epicor Web Access Utilities 9.0 folder
and run the Epicor Web Access Utilities.msi file.
12.3 Install Epicor Web Access
Use the following steps to complete the installation of your Epicor Web Access Forms.
1. Navigate to Start > Programs > Epicor Software > Epicor Administrative Tools > Epicor Web Access
Utilities > Epicor Web Access Installer.
Note To run the Epicor Web Access installer on Server 2008 or Windows 7, you must launch the
installer as an Administrator. To do this, right-click on the Epicor Web Access Installer icon, and
select Run as Administrator from the menu.
2. The Epicor Web Access Installer windows appears. Click Next.
3. The Basic Installer Settings dialog opens. Enter the following information:
a. Web Forms Package: Select EpicorWebAccessForms.zip which is located in the /Epicor Web Access
folder. The .zip file stores the files that related to web forms such aspx, js, and css.
b. Web Services Package: Select EpicorWebAccessServices.zip which is located in the /Epicor Web
Access folder. The .zip file stores the files that are related web services such as asmx, and dll.
c. Click Next.
4. The Site Settings dialog opens. It looks similar to the following:
Enter the following information:
42 9.05.701
a. Epicor Web Access Site: Enter your site name.
b. Install Path: Enter the directory path where the EWA files will be located. The final installation directory
uses both the Install Path and the Epicor Web Access Site values. For example, if you enter "EWATest"
as your Epicor Web Access Site, and "C:\temp" as your Install Path, then the final installation path would
be "C:\temp\EWATest". The Install Path is available for entry for both IIS 6 and IIS7 environments.
c. Web Site: Select the IIS web site where the application will get created. For example, in IIS, the web site
Default Web Site is always available. If you want to select a different web site, you can create one using
the IIS Admin Console. The Web Site is available only when installing in an IIS 7 environment.
d. App Pool: Select the Application Pool that will be used by the Epicor Web Access application. The
drop-down list displays only the application pools that are set to use Integrated Pipeline mode. If the list
is empty, click the New button to create a new application pool that uses an Integrated pipeline. The
App Pool is available only when installing in an IIS 7 environment.
e. Progress Server: Enter the name of your Epicor Progress Application Server (AppServer).
f. AppServer Port: The AppServer port number defaults to 3090. Change this number to identify your
AppServer port. For example, the Appserver port for the live database is 9401.
g. 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.
h. Click Next.
5. The Reporting Settings dialog opens. It looks similar to the following:
Enter the following information:
a. Enable Reporting: Select this check box if you have Crystal Reports 2008 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 Reports 2008 Runtime is installed on the server.
b. Report Appserver. The Report Appserver defaults to the name of the webserver. If the Crystal Reports
2008 Embedded Server is installed on a different server, change this name to identify the name of the
server where it is installed.
c. Report Monitor Polling for Server (ms): Select the number of milliseconds for report polling from the
web server.
9.05.701 43
d. High Priority Interval For Client (ms): Select the number of milliseconds the process waits immediately
after the report is submitted. When the time is greater than High Priority Duration for Client time, the
process shifts it to Low Priority Interval for Client.
e. Low Priority Interval For Client (ms): Select the number of milliseconds the process waits between
process after the time specified for the High Priority Duration for Client is done.
f. Auto Purge Older Reports For Server (days): Select the number of days the report is available before
it is automatically delete from the server.
g. High Priority Duration for Client (ms): Select the number of milliseconds for the duration time that
the reports check for new reports. This setting is similar to the System Monitor in the Win Client. When
the duration times out, it sets it to Low Priority Interval For Client.
h. NLB Report Repository: Specify the NLB (Network Load Balancing) report repository location. This
location is a shared repository that can be accessed by other EWA installations. This is an optional field.
i. Click Next.
6. The Summary dialog opens. Review the information. Click Finish. The Epicor Web Access installation
proceeds.
7. If you entered an Epicor Web Access Site name that already exists, the Install Options dialog opens. Review
the options and click the button that specifies your desired installation option. Options include:
• Install New Site. Select this button to install a new Epicor Web Access site using the name you specified.
The installation will remove all the web forms and assemblies that were previously installed in the site,
and it will install new web forms and new assemblies.
• Upgrade Site. Select this button to keep the existing Epicor Web Access site in place. The installation
will overwrite all Epicor web forms and replace any changed assemblies. Custom forms will be kept in
place.
• Cancel. Select this button to cancel the installation.
8. To verify that the installation was successful, in Windows Explorer enter the Epicor Web Access URL.
For example, enter http://<your server>/<your site name>/default.aspx where <your server> is the name
you specified as your Progress server and <your site name> is the name you specified as your Epicor Web
Access Site.
9. If your Epicor Web Access installed successfully, a window similar to the following should appear:
10. Enter a valid User ID and Password that you use to log into your Epicor application. This sign-in consumes
a user license.
44 9.05.701
Note If you want to use a Time and Expense (TE) or Customer Relationship Management (CRM)
license, go to the login page using the following URLs respectively: http://<your server>/<your site
name>/default.aspx?LicenseType=TE or http://<your server>/<your site
name>/default.aspx?LicenseType=CRM. During deployment of EWA, direct users of TE and CRM
license types to set up browser Favorites using the appropriate style of URL.
11. Click Login.
12.4 Deploy Epicor Web Access
Use these steps to deploy Epicor Web Access. The delivered web forms are generated at the same version as the
Epicor application software deployed in the release. The Web Menu includes the forms that are available for
Epicor Web Access.
1. Epicor Web Access includes the majority of the Epicor application forms, with a few exceptions of the
drag-and-drop scheduling forms and most of the system setup forms. Review the form exceptions, which
include:
• Job Scheduling Board
• Multi Resource Scheduling Board
• Resource Scheduling Board
• Business Activity Query Designer
• BPM Method and Data Directive Maintenance
• Financial Report Designer
• Menu and Security Maintenance
• Mobile, Customer and Supplier Connect Maintenance
• Translation Maintenance
• System Agent
• W2 Processing
2. Determine if you need further control over web forms that you need to exclude from Epicor Web Access.
To exclude a form, use Menu Maintenance (using the Epicor Smart Client) and on the Security sheet,
select the Exclude Epicor Web Access check box associated with each menu option.
Note Epicor Web form supports group access security so this exclusion is only required when a form
should be available to users from the Epicor Smart client but not the Epicor Web Client.
3. Determine if you need to customize any forms or create any user dashboards since these must be specially
generated for Epicor Web Access.
Note A prerequisite for generation is that any customization script must be supported in C# rather
than VB.Net code. This is due to the fact that the process converts customization code from C# into
Java Script for Browser deployment. This process is not possible from VB.Net code. Although VB.Net
is supported for backward compatibility with the Epicor 9.05 application, it is not recommended that
new customizations are created using VB.Net with the Epicor 9.05 application since they do not
generate for Web Access without conversion to C#.
9.05.701 45
4. Determine how to process the customizations and dashboards containing customization code in VB.Net
that were created prior to upgrading to the Epicor 9.05 application. You must either recreate those
customizations using C#, or manually convert code either by hand or using a commercially available VB.Net
to C# conversion routine. Instructions are available in a the document entitled Guidelines for Conversion
of VB.Net to C# Customization Code in Epicor 9.05. Contact Epicor Support for this documentation.
5. If you want certain users to use a Time and Expense (TE) or Customer Relationship Management (CRM)
license, direct them to use the following URL style to get to the login page: http://<your server>/<your site
name>/default.aspx?LicenseType=TE or http://<your server>/<your site name>/default.aspx?LicenseType=CRM.
Direct users of TE and CRM license types to set up browser Favorites using the appropriate URL.
12.5 Configure Epicor Web Access
Use these steps to configure Epicor Web Access within your Epicor application.
1. Navigate to System Management > Company Maintenance and open the Company program.
2. Click the System > Epicor Everywhere tab.
3. Enter your Epicor Everywhere URL. For example, enter http://<your server>/<your site name>.
4. Enter your Metadata Output Path. This is from the perspective of a client PC that might be generating
Epicor Web Access forms.
For example, enter: \\<your server>\<shared site name> where <your server> is the name of your web server
and <shared site name> is a share on that server to your Web Access site name. Example:
c:\inetpub\wwwroot\<your site name>.
5. Click Save on the Standard toolbar.
12.6 Assign Resource Folder Properties and Sharing
Use the following steps to assign required properties and sharing to the Resource folder. Note that the group
names may be different for IIS6 and IIS7.
1. Navigate to the Epicor Web Access virtual directory. For example, if your Epicor Web Access was installed
to IIS, the default directory should be C:\inetpub\wwwroot\EWA\Resources
2. Right-click on the Resources folder and select Properties.
3. Click the Security tab. Select the IIS_WPG group (IIS6) or IIS_IUSRS group (IIS7) from the Group or user
names list.
4. Click Edit.
5. Re-select the IIS_WPG group (IIS6) or IIS_IUSRS group (IIS7).
6. In the Permissions for [group] list, select the Modify and Write check boxes in the Allow column.
46 9.05.701
Note The selected 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.
12.7 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.
12.8 Update Epicor Lightweight Client Installer File
Use the following steps to update the lightweight Epicor Web Access client installer .msi file. A lightweight
client allows a local smart client to work in conjunction with the EWA browser client to provide functionality not
available from EWA forms.
1. Verify that your Epicor Web Access site has been created.
2. Open the Epicor Web Access Utilities. To do this, navigate to Start > Programs > Epicor Software > Epicor
Administrative Tools > Epicor Web Access Utilities.
3. Select the Epicor Lightweight Client Install Updater program.
4. Enter or browse for the Installer File Name. The file is called SmartClientInstall.msi file and it is located
in the following folder: C:\inetpub\wwwroot\<EWA site>\SmartClientInstaller.
5. Enter the Deployment server URL. To find the value, do the following:
a. On the smart client, go to the \config directory.
b. Open the configuration file for that smart client. For example, open the default.mfgsys file.
c. Locate the line: <Deployment server uri = [value]>.
d. Copy the value and paste it into the Deployment server URL field.
6. Enter your Configuration file name. For example, enter the configuration file used by your smart client,
such as default.mfgsys. Click OK.
7. When the installation is finished, click OK.
9.05.701 47
8. To test that the Epicor Lightweight Client Installer file was updated, do the following:
a. Open Epicor Web Access.
b. Click on the Download Smart Client Installer icon that is located in the toolbar.
c. The Epicor Lightweight Client Installer is downloaded to your machine.
12.9 Configure EWA Reporting URL Display Features
If you use 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.
12.9.1 Configure: 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.
a. For the Request path, enter *.pdf.
b. For the Executable, browse and select the file:

C:\Windows\Microsoft.NET\Framework\v2.0.50727\aspnet_isapi.dll
c. For the Name, enter AboMapperCustom PDF 32.
d. Click Request Restrictions.
e. Go to the Verbs tab. Select the One of the following verbs checkbox.
f. Manually enter GET,HEAD,POST,DEBUG.
g. Click OK.
h. Review the Edit Script Map setup form. The values should be the same as you previously entered. Click
OK.
i. A message appears asking if you want to allow the ISAPI extension. Click Yes.
12.9.2 Configure: 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.
48 9.05.701
2. In the Actions section, select Add Script Map.
a. For the Request path, enter *.xls.
b. For the Executable, browse and select the file:

C:\Windows\Microsoft.NET\Framework\v2.0.50727\aspnet_isapi.dll
c. For the Name, enter xlsMappingCustom XLS 32.
d. Click Request Restrictions.
e. Go to the Verbs tab. Select the One of the following verbs checkbox.
f. Manually enter GET,HEAD,POST,DEBUG.
g. Click OK.
h. Review the Edit Script Map setup form. The values should be the same as you previously entered. Click
OK.
i. A message appears asking if you want to allow the ISAPI extension. Click Yes.
12.10 Generate Web Forms for Customized Epicor 9.05 Forms
Use these steps to generate Web Forms for customized Epicor 9.05 application forms.
1. Click on the User Security tab. Verify that the Customization Privileges check box is selected.
2. From the Options menu, select the Developer Mode check box.
3. Run the Customized form under the customization that you wish to Generate.
4. From the Tools menu of the customized form, select Generate Web Form.
5. Click OK. The customized form is generated to the Epicor Web Access site.
12.11 Generate Web Forms for User Dashboards
Use these steps to generate Web Forms for user Dashboards:
1. Click on the User Security tab. Verify that the Customization Privileges check box is selected.
2. Open the Dashboard that you wish to generate a web form.
3. From the Tools menu, select Developer.
4. From the Tools menu, select Application Builder > Deploy UI Application. This deploys the dashboard
as a UI form.
5. Select Application Builder > Generate Web Form. This deploys the UI Dashboard to the Epicor Web
Access site
9.05.701 49
12.12 Review Supported Browsers and Configuration
Use these steps to review the browsers and browser configurations that are supported with Epicor Web Access.
1. Verify that one of the following browsers is installed on your system. Note that Epicor 9.05 supports only
the latest releases of these browsers.
• Internet Explorer
• Mozilla Firefox
• Apple Safari
Note Microsoft Silverlight cannot be used in browsers running in 64-bit mode.
2. If you use Firefox, complete the following steps to change your security settings to support Java popups
such as the search dialog box:
a. In the Navigation bar, type about:config.
b. In the Filter text box, type signed.applets.codebase_principal_support.
c. Double-click on the entry. The value changes from false to true.
d. Restart Firefox.
3. If you use Firefox, complete the following steps to access some Microsoft plug-in files to support Window
Authentication:
a. In Firefox, browse to the following: http://www.microsoft.com/genuine/diag/default.aspx?displayLang=en
b. Click the Start Diagnostics button.
c. Follow the online instructions to add the plug-in files.
12.13 Set Up Compression for Performance Tuning
If you use Windows Server 2008, use the following steps to set up compression. With IIS 7, compression is enabled
at the site level. Mime types are enabled globally and are applied to the applicationHost.config.
1. Create a backup of the metabase. To do this:
a. To create the backup, run this command: %windir%\system32\inetsrv\appcmd.exe add backup

"My Backup Name"
b. To restore the backup, run this command: %windir%\system32\inetsrv\appcmd.exe restore backup

"My Backup Name"
c. To delete the backup, run this command: %windir%\system32\inetsrv\appcmd.exe delete backup

"My Backup Name"
50 9.05.701
2. Enable Compression in IIS. To do this:
a. In IIS, under Default Web Site, select the web site to be enabled.
b. From the available IIS features, open the Compression feature.
c. Select the Enable dynamic content compression and Enable static content compression check
boxes.
d. Click Apply. Exit from IIS, and save settings.
3. The EWA extensions do not need to be modified. However, if you want to apply compression to specific
extensions, you can do the following:
a. Open the file: C:\Windows\System32\Inetsrv\Config\applicationHost.config
b. Locate the httpCompression section.
c. Edit the dynamicTypes and staticTypes sections to control which content gets compressed. IIS6 controls
by file extension, IIS7 controls by mimeType. The "*" character is a wildcard and can be used in any
combination. The easiest setup is to enable all with types */*.
Here are some examples of enabling selective mimetype(s):

dynamicTypes:
<mimetype="text/*" enabled="true">
<mimetype="message/*" enabled="true">
<mimetype="application/x-javascript" enabled="true">
<mimetype="*/*" enabled="false">
staticTypes
<mimetype="text/*" enabled="true">
<mimetype="message/*" enabled="true">
<mimetype="application/x-javascript" enabled="true">
<mimetype="*/*" enabled="false">
12.14 Set EWA Server Timeout
Use these steps to set the session timeout values for the server. The timeout values are entered in minutes.
1. Using a text editor, such as Notepad, open the web.config file located in the root of the EWA web site.
2. Locate the <sessionState> line. For example, the line may look similar to the following: <sessionState
mode="InProc" stateConnectionString="tcpip=127.0.0.1:42424" sqlConnectionString="data
source=127.0.0.1;Trusted_Connection=yes" cookieless="false" timeout="20" />
3. Edit the timeout string portion that is in quotes. For example, change timeout = "20" to timeout = "60"
to increase the timeout value from 20 minutes to 60 minutes.
4. Save and close the file.
9.05.701 51
Reinstall Web Services Epicor 9.05 Supplemental Installations
13 Reinstall Web Services
If you are an existing customer and you use Epicor Service Connect, AQM, Epicor PLM, Epicor Portal, or Information
Worker, you must use these steps to reinstall your Web Services if Epicor Service Connect is installed on a separate
server to your Epicor application server. The instructions for reinstalling your Web Services are located in the
WebServices directory. In a standard installation, the instructions are in \Epicor Software\Epicor905\WebServices.
Note These steps must be completed each time you upgrade your Epicor 9.05 application with a new
Service Pack or Patch.
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\Epicor905. Copy only this folder; do not
copy any other folders.
2. Navigate to the server where your web services are installed. Paste the WebServices folder into a directory
of your choice.
3. Go to the WebServices directory.
4. Run the WS-Configuration[.Net 2.0 Edition].exe program.
5. Select the Reinstall All check box. Click Update Site.

Your Web Services are now reinstalled.
52 9.05.701
Epicor 9.05 Supplemental Installations Reinstall CSF Functionality
14 Reinstall CSF Functionality
If you use Country Specific Functionality (CSF), use the following steps to reinstall your CSF product. Your CSF
must be reinstalled after you upgrade your Epicor application with a patch or service pack.
Note You can use this link:https://epicweb.epicor.com/Support/epicor9/Downloads
2. Navigate to Epicor 9 > Version 9.05.700 > Country Specific Functionality. Expand your country.
3. Download the Country Specific Functionality Install Guide.
4. Use the guide for instructions on reinstalling your CSF product.
9.05.701 53
Upgrade to Service Connect 9.05 Epicor 9.05 Supplemental Installations
15 Upgrade to Service Connect 9.05
If you use Epicor Service Connect, you must upgrade to the latest version. Use the following instructions to
upgrade to the latest version of Service Connect, such as Service Connect 9.05.
1. Go to the directory where your system is installed.
2. Run the runtime version of Service Connect 9.05.
3. Test your system to verify that Service Connect works successfully.
16 Upgrade to Epicor Portal 9.05
If you use Epicor Portal, you must upgrade to the latest version. Use the following instructions to upgrade to the
latest Epicor Portal version, such as Epicor Portal 9.05.
1. Locate the Epicor Portal 9.05 Installation Guide. Click this link to access EPICweb:
https://epicweb.epicor.com/Support/epicor9/Downloads
2. Complete the instructions to upgrade your portal installation. Be sure to install any Epicor Portal service
packs after the portal installation.
3. Test your system to verify that Epicor Portal works successfully.
17 Upgrade to Infragistics NetAdvantage
If you use Epicor's Software Developer's Kit (SDK) to modify or extend the application forms, you may need to
upgrade the Infragistics NetAdvantage version that is used by your Epicor application. See the SDK documentation
for specific version information.
1. Review the SDK documentation that came with Epicor 9.05. The document includes recommended steps
for a successful migration.
2. Follow the Infragistics Upgrade instructions and, as a minimum, choose to install the Infragistics .Net 2.0
components.
54 9.05.701
Epicor 9.05 Supplemental Installations Install SonicMQ
18 Install SonicMQ
Use this appendix to install SonicMQ 7.6.2.
18.1 Install Sonic on Windows
For Windows, use the following instructions to install Sonic 7.6.2. During the installation, Sonic 7.6 is installed
and then updated with a Service Pack to 7.6.2.
1. Insert the Progress OpenEdge 10.2A for Epicor 9.05.700 DVD into the server's DVD drive (D:\). The autorun
feature should launch the OpenEdge Installation wizard. If not, choose Start > Run and enter the command:
D:\setupSonic.exe.
Note If you do not have the Progress OpenEdge DVD, and you already have Sonic 7.6 installed, you
can upgrade to 7.6.2 by downloading the required Sonic Service Pack from EPICweb Support
Downloads. The Sonic Service Pack files are located in the Third Party Products > Progress Sonic folder.
2. On the OpenEdge Installation option window, select the Sonic option.
3. The Epicor Software Sonic 7.6.2 Installer window appears. Click Next.
4. 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 needed. Click Next to begin the
installation of the components requiring updates.
5. The Sonic 7.6 Install Type window appears. It is recommended that you select the Sonic 7.6
Typical/Automatic Install option. Click Next.
6. The Sonic 7.6 Install folder window appears. Select the directory where you want to install Sonic 7.6. The
default directory is C:\Sonic. Click Next. Sonic 7.6 is installed.
7. The Progress Sonic Updater 7.6.2 window appears. Click Next.
8. The Sonic 7.6.2 Updater Install folder window appears. Select the folder where you previously installed Sonic
7.6. Click Next.
9. The Installation wizard verifies the current version of Sonic installed. Click Next.
10. The Progress SonicMQ V7.6.2 Readme window appears. Review the information and click Next.
11. The Progress Sonic Version 7.6.2 End User Product License Agreement window appears. Review the License
Agreement, select I accept the terms of the license agreement option and click Next.
12. To install Sonic on the primary Directory Service, select the Primary Directory Service check box. Click
Next.
13. Enter the Domain Name.
14. Enter or browse for the Directory Service Bootstrap File. Click Next.
9.05.701 55
Install SonicMQ Epicor 9.05 Supplemental Installations
15. Enter the Broker Name, and then enter or browse for the Database Location. Click Next.
16. Review the summary information. Click Install. The Sonic Updater is installed.
17. When the Installation is finished, click Finish.
18.2 Install SonicMQ on Linux/UNIX
For Linux/UNIX environment, use the following steps to install Sonic 7.6.2.
Important For Linux/UNIX environment, Sonic must be installed on the Windows Admin workstation, as
it is only supported on Windows Admin workstation.
18.2.1 Determine Your Security
Sonic Software has the ability to function with username/password security. In an effort to increase the security
of the software, customers are able to turn security on if they want.
1. Determine if you want to enable SonicMQ security during installation.

Note For Sonic Security to be enabled, it must be implemented during installation. If you already
have Sonic installed without security, then you must uninstall and reinstall of Sonic.
2. Be aware that the installation instructions differ based on whether you enable security:
• Use the following Install SonicMQ with Security Enabled instructions if you have decided to install SonicMQ
with the security functionality.
or
• Skip to the following Install Sonic MQ without Security instructions if you have decided NOT to install
Sonic MQ with the security functionality.
18.2.2 Install SonicMQ With Security Enabled
Use the following instructions to install SonicMQ as an advanced installation, which includes enabling the security
functionality.
Note If you do not want to install SonicMQ with security enabled, skip to the next section.
1. Insert the SonicMQ DVD into the drive.
2. Run the SETUP.EXE file in the root directory of the SonicMQ DVD.
3. Enter the directory where the Progress Client Software is installed. Click Next.
4. Select the SonicMQ software Advanced Install option. Click Next.
5. Click Next.
56 9.05.701
Files are copied from the SonicMQ install into your Progress directory. The Progress Sonic MQ Adapter
accesses these files to communicate with SonicMQ.
6. Begin the installation of SonicMQ. Click Next.
7. Read the registration and license information. Click Next. Read the license agreement, accept the terms.
Click Next.
8. Enter the SonicMQ License Key provided. Click Next.
9. Perform a new installation. Click Next.
10. Enter the directory where you would like SonicMQ to be installed.
11. If the directory does not exist, you will be prompted to create a new directory. Click Yes.
12. Select the Custom installation. Click Next.
13. By default, all features are installed. The first five are mandatory for Mobile Connect. Enter the program
group folder you want to use. Click Next.
14. Install the JRE. Click Next.
15. Keep the defaults for the Management Connection information. If you would like to change the defaults,
please contact Support before doing so. Click Next.
16. Keep the defaults for the Broker Options information, with the exception of checking the Enable Security
checkbox. If you would like to change the other defaults, please contact Support before doing so. Click
Next.
17. Review the installation. Click Next.
18. Monitor the progress of the install. Click Finish.
19. Reboot the server.
18.2.3 Install SonicMQ Without Security Enabled
Use the following instructions to install SonicMQ as a typical installation, which does not include enabling the
security functionality. If you want to install SonicMQ with security enabled, use the previous section instead.
1. Insert the SonicMQ DVD into the drive.
2. Click Next.
3. Select the Progress Client Software directory and click Next.
4. Select SonicMQ software, Typical install, and click Next.
5. Click Next.
6. SonicMQ is installed silently on your server. A command window may appear. Keep the window open until
the install is complete.
9.05.701 57
7. Run the post-install process. To do this, double-click 76postinstall.exe on the CD-ROM, or choose Start
> Run and enter the command: D:\76postinstall.exe
9. The SonicMQ Install Location window appears. Enter the location where SonicMQ has now been installed.
The default is C:\epicor\SonicMQ76.
10. Click Next. Do not check the box that this is an upgrade.
11. Click Install.
12. Click Finished.
13. Reboot the server.
18.2.4 Download Latest Update File
Use the following instructions to download the latest Sonic updates.
2. Navigate to Epicor 9 > Version 9.05.700.
3. Go to the Third Party Products / Progress Sonic directory. Based on your environment, download the
latest Sonic service pack file onto your machine, if any are available.
18.2.5 Install Sonic SP for Linux and UNIX
Use the following instructions to install the Sonic updates.
1. Log into your server as root.
2. Set the DLC environment variable to the directory containing the Sonic Service Pack installation you want
to install. Type the command: DLC=/usr/epicor/sonic ; export DLC
3. Change directory into the temporary folder containing the service pack .tar file. (i.e. /usr/epicor/temp). Type
the command: cd /usr/epicor/temp
4. Extract the contents of the Tar archive into the temp directory. At the prompt, type the following command:
tar -xvf <filename>
5. Change directory back to /usr/epicor. At the prompt, type: cd /usr/epicor
6. To begin the installation of the Service Pack, type the following command at the prompt: ./temp/proinst
7. At the Introduction screen, click Next.
8. Review the ReadMe information. Click Next.
58 9.05.701
9. Review the License Agreement. Click Next.
10. To install Sonic on the primary Directory Service, select the This is the primary Directory Service check
box. Click Next.
11. Enter the Directory Name for the Directory Service. If you are updating an SDM installation, specify the
location of the Directory Service Bootstrap file. Click Next.
12. Enter the name of the broker and the location of the database. Click Next.
13. Review the summary information. Click Install. The Sonic update is installed.
14. When the Installation is finished, exit the installer.
15. The service pack contents of the /usr/temp folder can now be deleted.
18.3 Set Up Sonic Test Environment
If you use a test environment, it is recommended that you make a copy of your live data and put it in a completely
isolated environment on a test server.
This separation ensures that prototyping and testing is done in a quarantine area without the possibility of
inadvertent data being sent to your live environment. The precaution of a separate environment is recommended
where Sonic messaging is used since the test data has the same company id and messaging ports as your live
system. The separate environment minimizes the risk of human error when moving databases around for testing
and training purposes.
To set up a test environment, you will need the following:
• Test Server. A low-cost test server can be a low-end server or a XP Professional workstation with a minimum
of 2GB of RAM.
• Sonic Installation. The test server must have its own installation of Sonic.
• Progress Database. If the base database is Progress, the entire database and Epicor application must be on
the test server.
• SQL Database. If the base database is SQL, then the Epicor application is on the test server and the database
is located on the SQL server where the Epicor databases currently reside. This will save on SQL license cost.
Note Be sure to place your training database and your live database on separate servers. If you do not
and you run test multi-company processes, the shared records populate both the training and the live
databases.
18.4 Review Possible Installation Messages
Use the following troubleshooting tips to help resolve issues you may encounter.
18.4.1 Adapter .jms error in the AppServer log
Error: Application Service adapter.progress.jms not found at NameServer at Host 127.0.0.1 Port 5162. (8245)
Error connecting to the JMS AppServer Service.
9.05.701 59
Problem: The SonicMQ Adapter is not started.

Resolution: The SonicMQ Adapter "sonicMQ1" is created by default for you when you install the AppServer
license. If you go to the properties, it needs to contain a unique port number and be set to Auto start (which
means it starts when the Admin Service starts), otherwise it must be started manually from the Progress Explorer
Tool or OpenEdge Explorer Tool. If the SonicMQ Adapter is started properly, when you check the Status, status
information appears in the sonicMQ1 Status dialog box.
18.4.2 Javax.jms Exception error in the AppServer log
Error: javax.jms.JMSException: java.net.ConnectException: Connection refused: no further information:

TCP://localhost:2506. Error connecting to JMS AppServer service.
Problem: The SonicMQ broker cannot start. The SonicMQ Container is not started.
Resolution: Start the SonicMQ Container.
18.4.3 Javax.jms Security error in the AppServer log
Error: javax.jms.JMSSecurityException: Inauthentic Client. Error connecting to the JMS AppServer service
Problem: The SonicMQ "Administrator" Password is not correct, or the Device Username/Password is not correct.
Resolution: Enter a correct username and/or password.
18.4.4 General Error Message
Error: Not Accepting Messages at this Priority

Problem: The program UpdateDBIni.exe was not run properly following the installation of SonicMQ.
Resolution: All Sonic and Progress processes must be stopped. Run the fix program and reboot the server.
60 9.05.701
Epicor 9.05 Supplemental Installations Install Progress OpenEdge 10.2A (Advanced/Manual)
19 Install Progress OpenEdge 10.2A (Advanced/Manual)
Use these instructions to manually install Progress OpenEdge 10.2A on your server and/or Windows Admin
workstation. You will need to reboot the server and/or Windows Admin workstation after completing this section.
Note You need the Progress OpenEdge 10.2A for Epicor 9.05.700 DVD in order to install Progress
OpenEdge 10.2A Service Pack and Hot Fix.
19.1 Install Progress OpenEdge 10.2A
1. After you selected the Advanced/Manual Install option, the OpenEdge 10.2A window appears. Click
Install.
3. Enter the serial numbers for the products that you will be using. Click Next.
4. On the Before You Start window, click Next.
5. On the Select Server Engines window, click Both. Click Next.
6. On the Previous Installation Settings, click No.
7. On the Destination and Working Path Directories window, select the destination and working path
directories. Recommended paths are \Epicor\oe102A and \Epicor\oe102A_wrk. Click Next.
8. On the Setup Type window, click Complete. Click Next.
9. On the Configuring/Installing Components window, clear the Sonic ESB option. Click Next. If you leave
the settings blank, click OK at the alert message.
10. On the Program Folder window, select the OpenEdge 10.2A group. Click Next.
11. On the Web Server Type window, select the Microsoft Web Server (IIS) or ISAPI - compatible check
box. Browse and select the Web Server Script directory and the Web Server Document Root directory.
Recommended paths are C:\InetPub\adminscripts and C:\InetPub\wwwroot. If these are unknown, for each
directory select C:\Epicor. Clear the Copy static HTML files to Document Root directory check box. Click
Next.
12. On the Language window, select the default language. Click Next.
13. On the International Settings window, select your settings. Click Next.
14. If you have configured the web server, configure the web services adapter settings. If not, accept the defaults.
Click Next.
15. On the Admin Server Authorization Options window, select the security options for the Admin Server.
Click Next.
9.05.701 61
Install Progress OpenEdge 10.2A (Advanced/Manual) Epicor 9.05 Supplemental Installations
16. On the Summary window, click Next. The installation begins. The installation can take up to 45 minutes
on older machines.
17. Click Finish. The Commit Shared Files window appears.
18. Reboot your server or/and Windows Admin Workstation.
19.2 Install Progress OpenEdge 10.2A SP
Use the following instructions to install the latest Progress OpenEdge Service Pack file on your server and Windows
Admin workstation.
Important Do not skip this step.
1. If you are an existing user, perform the following steps before you install the Progress OpenEdge 10.2A SP.
a. Stop any OpenEdge App Servers or databases that may be currently running. To do so, use the Progress
Explorer Tool or OpenEdge Explorer Tool to stop any OpenEdge App Servers or databases that may be
currently running.
b. Select Start > Control Panel > Administrative Tools > Services. The Services window appears.
c. Right-click on AdminService for OpenEdge 10.2A, and select Properties. The AdminService dialog
box appears. On the General tab, click Stop. Click OK.
2. On your Progress OpenEdge 10.2A for Epicor 9.05.700 DVD double-click the OpenEdge service pack
file. The installation program opens.
4. Click Next to confirm you have backed up your system files.
5. Click Next to confirm the summary information. The installation proceeds.

Note You may be prompted with registry warnings if the following file extensions have already been
registered as file types: .I, .DB, .UDF, .CLS. When prompted to overwrite the registry entry and register
this file extension as a Progress file, select Y
6. Click Finish. The Service Pack installation is now complete.
19.3 Install Progress OpenEdge 10.2A SP Hotfix
Use the following instructions to download and install the latest Progress OpenEdge service pack hot fix.
Note You can use this link:https://epicweb.epicor.com/Support/epicor9/Downloads
62 9.05.701
Epicor 9.05 Supplemental Installations Install Progress OpenEdge 10.2A (Advanced/Manual)
2. Navigate to Version 9.05.700 > Third Party Products > OpenEdge > 10.2A.
3. Based on your environment, download the latest OpenEdge hotfix file onto your machine. For example,
download one of the following files:
• Windows 32: Rl102asp0329hf.EXE
• Windows 64: Rl102asp0329hf-64.EXE
4. Right-click on the file and select Run as Administrator. The installation program opens.
6. Click OK to confirm you have stopped the OpenEdge related functions.

Note If you have not stopped the AppServer, database and AdminServices functions, click No and
then stop the functions before continuing.
7. Select the OpenEdge 10.2A directory as your Destination directory. For example, select C:\Epicor\oe102A.
Click Next.
8. The Ready to Install window appears. Click Next. The installation proceeds.
9. Click Finish. Depending on your selection, the files appear for review.
9.05.701 63
Configure Epicor Online Help Epicor 9.05 Supplemental Installations
20 Configure Epicor Online Help
After you run the basic Epicor Help installation, your help system is ready to access from within the application
by pressing F1 or selecting Contents from the Help menu. The field-specific help is also available by selecting
Field Help from the Help menu. However until you perform the configuration steps in this section, the help is
accessed from the file system which is not efficient.
The following steps are optional, but highly recommended if you want to improve the performance and efficiency
of the help system.
Most installations would perform these steps:
• Host Help System in a Web Site. By default the help system (a large collection of non-compiled html files)
is installed to be accessed from the file system. This does not function well over a WAN installation. Host the
help on a web site to improve the speed of accessing the help.
• Implement Server-side Searching. By default, the help system searching capability relies on (large) index
files that are downloaded to each client workstation. Alternately, you can implement server-side searching
which uses Windows Search and provides a more robust search and a faster help experience. In addition to
having natural language searches, users can do advanced searches using Boolean operators, and/or choose
to search only among help topic titles. See the application help for more information on advanced help system
searches.
20.1 Configure Help for Virtual Directory and Server-side Search
Use these steps to host the online help in a virtual directory and enable the server-side searching of online help.
1. Verify that the Epicor 9.05 Help Content Pack has been installed. To install the help content pack, use the
instructions in the Installation section called "Install Epicor 9.05 Help Content Pack".
2. Verify that you will be running the EpicorHelpSearchSetup.exe locally on the machine where the Help is
installed. You may need to use Remote Desktop to access the server.
3. Verify that ASP.NET is enabled on the web server. See your Internet Information Services (IIS) documentation
for information on how to make the verification.
4. Verify that Windows Search is installed on the server. To verify, do the following:
a. Select Start > Programs > Administrative Tools > Server Manager.
b. Under Roles Summary, click File Services. Add the File Services role if it does not already exist.
c. Under Role Services, check for Windows Search having a status of installed. If it is not, click Add Role
Services, select Windows Search Service and click Install.
5. In Windows Explorer, navigate to the Setup folder directly under where you installed the Epicor online help.
The default path is C:\Epicor\Epicor905\Help\Setup.
6. Right-click on EpicorHelpSearchSetup.exe and select Run as Administrator.
7. For Web site to use for help, select the web site on which you want to host the Epicor help. In most cases,
this is the Default Web Site.
64 9.05.701
Epicor 9.05 Supplemental Installations Configure Epicor Online Help
8. Click Create Virtual Directory.

A virtual directory is created for the physical directory listed under Physical directory of the help folder.
9. Click Switch to Windows Indexed Search.

The help files are now being indexed by Windows Search, and the search page for Epicor online help has
been changed to use the server-side search.
Important Indexing the help files can take over an hour. Wait at least an hour before clicking the
Test button to test a search (try to search for the word Epicor).
10. Edit each client .mfgsys configuration file to use the help URL you just created. To do this:
a. Navigate to the Client\Config folder on your workstation.
b. Open the .mfgsys file in a text editor, such as Notepad.
c. Edit the <helpServer uri=" " /> line to add the new help URL between the empty quotes. Use the URL
listed for Help URL for default.mfgsys in the Epicor Help Search Setup. However, replace localhost with
the actual machine name or alias of the web server. For example, if your web server has an alias of
EpicorOne, the edited line would look like <helpServer uri="http://EpicorOne/EpicorHelp/" />
9.05.701 65
Set Up Multi-Company Functionality Epicor 9.05 Supplemental Installations
21 Set Up Multi-Company Functionality
Use this appendix to set up your Epicor 9.05 application to support multi-company functionality. You can also
review the Multi-Site Technical Reference Guide for this information. This guide is located within the application
help under the Multi-Site Management > Working With > Multi-Site Technical Reference Guide topic.
Note You must install the SonicMQ application before you can run Consolidation processing. This application
is required in order to pass data between multiple companies and databases.
21.1 Verify Multi-Site Management License
Verify you have the Multi-Site Management license module codes for both companies participating in
Multi-Company communication. If the companies reside on different databases, a separate serial number is
required.
21.2 Verify SonicMQ Broker Status
Use the following steps to verify the SonicMQ Broker status. The SonicMQ Broker is a batch file that enables a
TCP port to listen for messages being passed between two Epicor companies. The SonicMQ Broker must be
running in order for two companies to communicate in a Multi-Company environment.
The executable files used to start the SonicMQ Broker can be configured to start as a Windows service. Contact
Support for the batch file required to set up the Windows service.
1. Select Start > Programs > Sonic Software > SonicMQ 7.6 > Start [Machine Name].
2. Verify that the SonicMQ Broker is running. A successful startup of the SonicMQ Broker looks like the following:
66 9.05.701
Epicor 9.05 Supplemental Installations Set Up Multi-Company Functionality
21.3 Configure an External System Record
Use the following steps to configure an external system record.
1. Verify the status of External System Maintenance. To do this, select System Management > External
System Integration > Setup > External System Maintenance.
2. Search by clicking the External System button, and selecting the Multi record.
3. On the detail sheet, enter the information necessary for the Epicor application to know how to communicate
with Sonic. The fields include:
a. Sonic LAN Hostname & Sonic WAN Hostname. Enter the Hostname or IP Address of the machine
where the Sonic Container is running. If the value is left blank, the default localhost is used.
b. Sonic Security Enabled & Sonic Administrator Password. Use these fields if Sonic password security
was enabled during installation. Select the Sonic Security Enabled checkbox and enter a Sonic
Administrator Password. Note that the values in Sonic are case-sensitive. If the value is left blank, the
default "Administrator" is used.
c. Sonic Session Port. Enter a value that corresponds to the port number of the Progress NameServer.
This is used to find the SonicMQ Adapter, which is the software that Progress uses to communicate with
Sonic. If the value is left blank, the default 5162 is used. If more than one version of Progress/OpenEdge
is installed on the server, one of the two installations must use a different port number.
d. Sonic Broker Port. Enter the value that corresponds to the port number of the SonicMQ Container. If
the value is left blank, the default 2506 is used.
e. Sonic Listener Pause (sec). Enter the amount of time required for Progress to wait before it assumes
Sonic has finished sending all incoming messages. If the value is left blank, the default 10 is used.
f. Sonic Communication Protocol. Enter the following values: TCP - Transmission Control Protocol - this
is the default value; SSL - Secure Socket Layer; HTTP - Hypertext Transfer Protocol; HTTPS - Secure
Hypertext Transfer Protocol
The External System record would look similar to the following:
9.05.701 67
21.4 Configure an External Company Record
Use the following steps to configure an external company record.
1. Configure an External Company record for each company that will communicate with the current company.
For example, if you have three companies in your multi-company setup, each company will have two external
company records set up. In a two company multi-company setup, each company will have one external
company record.
2. Open External Company Maintenance. To do this, select System Management > External System
Integration > Setup > External Company Maintenance.
3. In the drop-down selection list at the top, select Multi-Company.
4. Search to see if any multi-company records already exist.
5. If the record does not exist, enter in the external company ID with which you will be exchanging information.
This is not the current company you are logged into. You cannot enter the current company ID as an external
company.
6. Enter the applicable information into the external company record. The External Company record would
look similar to the following:
7. Optionally, click on the available tabs and enter the following information:
• Connection. If you are connecting to a multi-company dashboard, enter connection options for the
servers so that you are allowed to view information between companies.
• External Plant. If you using consolidated purchasing, enter the external plant detail information.
• External Warehouse. If you are using consolidated purchasing, enter the external warehouse detail
information.
• Multi-Company. If you are using consolidated purchasing, multi-site GL journals, or AP allocations,
enter the necessary information.
68 9.05.701
8. If you use multi-site GL journals, or AP allocations, you need to initialize your GL accounts. To do this, from
the Actions menu, select Initialize > Send Multi-Company G/L Accounts.
9. Save the record. Close the External Company Maintenance window.
10. Switch companies. To do this, select Options > Change Companies.
11. Select the other company that will be used in this Multi-Company configuration.
12. Go back into External Company Maintenance and set up an external company record for this company
pointing to the original company.
As a result, each of the two companies in this example have an external company record pointing to each
other company in this Multi-Company setup.
21.5 Verify Your Startup Schedule
Use the following step to verify if you have a Startup Schedule.
1. Determine if a startup schedule has been created. To do this, select System Management > Utilities >
System Agent.
2. Click on the Agent ID button.
3. Perform a search, and open the only record returned. Expand the tree on the left until you see a list of
schedules. This may be blank.
The screen should look similar to the following if you have a startup schedule already created. Notice the
schedule type of StartUp.
4. If you do not have a startup schedule created, create one by selecting File > New > New Schedule.
5. Enter the Startup Task Schedule description and select StartUp as the Schedule Type.
6. Save the record. You now have a startup task schedule to which you can assign tasks, such as the
Multi-Company Server process.
9.05.701 69
21.6 Schedule the Multi-Company Server Process
Use the following steps to put the Multi-Company process on a Startup schedule:
1. Select System Management > Utilities > Multi-Company Server Process. The screen should look similar
to the following:
2. Select Startup Task Schedule (the schedule that already existed, or the one just created) from the Schedule
drop-down selection list.
3. Select Continuous and Recurring.
4. Click the Submit button in the toolbar.
Now the process is submitted to run. If you look at your system monitor, the Scheduled Tasks tab would look
similar to the following:
21.7 Start the Multi-Company Process
The Multi-Company process is attached to a startup schedule so it will not run until the server starts. Use the
following steps to mimic this server action, which will start and stop the process server and task agent in the
Progress Explorer Tool or OpenEdge Explorer Tool for this database.
1. Open the Progress Explorer Tool or OpenEdge Explorer Tool. Connect to the server, and go to AppServers.
For example, if a database was named custdb15, then the process server could be custdb15ProcessServer,
and the task agent could be custdb15TaskAgent.
70 9.05.701
2. Right-click on each entry and choose Stop, or press the Stop button at the top when the Appserver is
selected. Your screen would look similar to the following:
3. The task agent may take a minute to fully stop. To check to see if it stopped, right-click on it and select
Status. If you see the status screen, the process is still stopping. Once this screen goes away, the process
has stopped.
4. Restart the processes after they have stopped. To do this, right-click on each one and click Start, or highlight
the Appserver and press the Start button at the top.
5. After you have restarted both processes, check the task agent status to verify it is running. Broker Status
= Active, Active Server = 1 and Busy Server = 1.
6. Return to the System Monitor. The Multi-Company Process instance that was scheduled appears in the
Active Tasks tab. It will also still be in the Scheduled Tasks tab. When Multi-company functionality is
running, your System Monitor should look similar to the following:
9.05.701 71
21.8 Review Multi-Company Log File
Use these steps to review the informative log file that is created during processing. The file is located by default
in the working directory of the database, or wherever you specified during process scheduling.
1. Open the log file. Activity in the log file will look similar to the following:
2. Notice the messages stating there was a Sonic Session Failure. This message can be a result of any of the
following:
a. SonicMQ Container not installed, configured or running properly
b. SonicMQ Adapter not installed, configured or running properly
c. SonicMQ Security installed, but password value is not entered correctly
d. Inability to reach SonicMQ Container using the hostname and/or port numbers provided
After the issue is resolved, the session failure messages stop.

Note In a Multi-Company environment, the Multi-Company Server Process needs to be running only once.
In a Multi-Site environment, the process must be running for each database.
21.9 Test the Communication
Use the following steps to test the Multi-Company environment is communicating properly. You need to create
a Global Customer and verify that the customer is transmitted to the other companies.
1. Verify that the main (Epicor904) AppServer logging level is set to Verbose or Extended. This will also
increase the logging level for the Multi-Company log.
2. In one company (for example VN10T), create a new customer and select the Global checkbox.
The Multi-Company Process transmits Customer and ShipTo records from that company and sends it to
the other companies (for example VN20C and VN30C).
3. Save the record.
72 9.05.701
4. Review the MultiCompany.log file to verify that the record was sent to the Sonic Container. The log file
could look similar to the following
• If the outbound transmission is working properly, the Multi-Company log will include the message:
Processing Outbound Customer (VN10T/VN20C).
• If the inbound transmission is working properly, the Multi-Company log will include the message:
Processing Inbound Customer (VN20C).
If the records are being sent and received, your Multi-Company functionality is configured and running.
21.10 Review Sonic Container Information
Use the following steps to login to the Sonic Management Console, which provides an in-depth look into the
Sonic Container.
1. Open the Sonic Management Console. Enter your login information. The default information will work if
the management console is opened from the server that is also running the Sonic Container. Click OK.
2. Click on the Manage tab. Expand the tree on the left to the broker level.
3. Right-click on a subscription on the left and click Browse Local Subscriptions. Available message are
displayed. Click on the Body tab to view the message contents in XML format.
This same methodology for viewing contents in a sonic container apply for any Sonic application.
21.11 Review Validation Errors
Use these steps to review the validation errors. Careful examination is required when sharing information between
two companies. The companies may have different sets of codes, and intervention is needed during the transmission
process.
1. Review the log file for errors. With errors, your log file may look similar to the following:
9.05.701 73
2. Notice that the Company record, Quote Markup, Allocation Priority, Tax Region, Customer Group, and FOB
sent from company VN10T were invalid when the company arrived in company VN20C. On the ShipTo
record, the Territory and Tax Region were invalid.
3. Find out why the records were invalid. Correct the issues.
21.12 Review Automatic Data Translations
Use these steps to review the results of the automatic translation that runs during the inbound portion of the
transmission process. The translation process compares the code sets of the two companies and synchronizes
the data in order to save manual steps.
1. Review the translation data. Your data could look similar to the following:
74 9.05.701
For example, if the Terms Code NET30 exists in company VN10T, but the same code is N30 in company
VN20C, the inbound customer will fail validation. A translation should be set up in company VN20C on the
external company record for VN10T with Source Value NET30 and Target Value N30.
If company VN10T sends Customer records where the Terms Code is blank, and your system needs inbound
Customer records to have the Terms Code default to N30, create a record indicating the default value.
21.13 Review Integrated Workbench
When a Validation Error occurs, manual intervention is required. Most of the functions within Multi-Company
have a specially designed screen for handling these errors. Functions include Link Customer, Link Part, Link
Vendor, Incoming Intercompany PO Suggestions, and Add Intercompany Receipt.
1. If you are unable to fix a validation error using one of these screens, use the Integrated Table Workbench
to access the record. Your workbench could look similar to the following:
2. Modify the required values.
21.14 Review Multi-Company Functionality
Use the following programs to review Multi-Company functionality.
1. Global Table. Using Global Part, Global Customer, and Global Supplier functionality, a child company has
the ability to control which fields they want to be maintained by the Global Parent company. This can be
controlled for all external companies or can be maintained separately for each external company
9.05.701 75
2. Global Part. Use the Link Part tab in Part Maintenance.
3. Global Customer. From the Actions menu within Customer Maintenance, select the Link Customer
option.
4. Global Supplier. From the Actions menu within Supplier Maintenance, select the Link Supplier option.
5. Inter-Company Trading. Use the Incoming Intercompany PO Suggestions options from the Main Menu
or the Incoming Linked PO Suggestions in Customer Maintenance.
6. Global BAQ. Global BAQs are visible within Business Activity Query.
7. Consolidated Purchasing. Consolidated Purchase Orders are handled using the normal functionality in
Purchase Order Entry, Receipt Entry, and AP Invoice Entry.
76 9.05.701
Epicor 9.05 Supplemental Installations Troubleshooting
22 Troubleshooting
Use the following section if you need assistance in troubleshooting any installation issues.
22.1 Share the Epicor Folders
Use this section to verify that the folders are shared. Note that if you are using Windows Server 2008, the steps
may be slightly different.
1. Verify that the C:\Epicor\Epicor905 folder is shared. To do this:
a. On the C: drive, navigate to the C:\Epicor folder.
b. Right-click the \Epicor\Epicor905 folder icon and select Sharing and Security.
c. Select the option to Share this Folder. Epicor905 displays as the default share name. Do not change
the name. The folder must be named Epicor905.
d. Click the Permissions button. It is recommended that you assign Full Control to the Everyone group.
Click OK to accept the permissions.
e. Click the Security tab. It is recommended that you assign read-only permissions to Users. Read-only
includes Read & Execute, List Folder Contents, and Read. Add an Administrator and assign the
Administrator Full Control. Click OK.
2. Verify that the C:\Epicor\EpicorData folder is shared. To do this:
a. On the C: drive, navigate to the C:\Epicor folder.
b. Right-click the C:\Epicor\EpicorData folder icon and select Sharing and Security.
c. Select the option to Share this Folder. EpicorData displays as the default share name.
d. Click the Permissions button. It is recommended that you assign Full Control to each user folder. Click
OK.
e. Click OK to accept the share options.
22.2 Verify Time Synchronization on Client and Server
If you received the error message "The authorization credential is expired", use these steps to verify the time
synchronization of your client and server. You may receive this error while performing a search from a client
workstation to the Epicor Web Access server if the time values that are set on the client and server are not accurate
according to the time zone.
1. On the client workstation, go to Start > Control Panel > Date and Time. Verify that the time is accurate
according to the time zone.
9.05.701 77
Troubleshooting Epicor 9.05 Supplemental Installations
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.
22.3 Change or Uninstall Epicor 9.05 Application
Use these steps to add or remove programs and features related to your Epicor 9.05 application. This section
also includes steps to uninstall the Epicor 9.05 application from your server or Epicor 9.05 client from your
workstation.
Note It is highly recommended that you create a backup of all your important files, such as your databases,
prior to uninstalling the application.
22.3.1 Add or Remove Programs and Features
Use these instructions if you want to add or remove programs or features that are related to your Epicor 9.05
application.
1. Navigate to Control Panel > Programs and Features..
2. Right-click on Epicor 9.05 (database) and select Change from the menu. The Install Wizard opens the
Epicor 9.05 installation menu. The dialog may look similar to the following:
3. The Add / Remove Features option is selected by default. Click Next.
4. On the Select Features dialog, select the features you want to add or remove. Click Next. The Epicor 9.05
features you selected are added or removed.
78 9.05.701
Note When adding features, the components for the Utilities, Server Add-On, and Web Add-On
features are delivered as executable files to a folder on your server. The components are delivered,
but they are not installed. After your installation, you can use the Supplemental Installation section
of this guide for instructions on installing these additional features and programs.
5. If prompted, click Finish.
22.3.2 Repair or Reinstall Epicor 9.05 Application
The Epicor 9.05 installation menu includes an option to Repair / Reinstall the Epicor 9.05 application. While this
is a standard option available in an install wizard process, it is not recommended that you use this option with
your Epicor 9.05 application due to customizations or configuration settings unique to your system.
22.3.3 Uninstall Epicor 9.05 Application
Use these instructions if you need to uninstall the Epicor 9.05 application from your server. It is highly recommended
that you create a backup of all your important folders and files, such as the Epicor905 folder and subfolders
(which includes your databases), prior to uninstalling the application. It is also recommended that you store this
backup in a safe location. Note that the uninstall process deletes everything in the Epicor905 folder. Do not store
your backup in the Epicor905 folder.
1. Create a backup of your important folders and files. For example, at a minimum, create a backup of the
following folders:
• Epicor905\db
• Epicor905\custom
• Epicor905\csg
• Epicor905\server\reports
• Oe102a\properties
2. Navigate to Control Panel > Programs and Features.
3. Right-click on Epicor 9.05 (database) and select Uninstall from the menu. The dialog may look similar to
the following:
9.05.701 79
Troubleshooting Epicor 9.05 Supplemental Installations
4. The Uninstall Epicor 9.05 option is selected by default. Click Next.
5. On the Ready to Update Your System dialog, click Next. The Epicor 9.05 application is uninstalled.
6. If prompted, click Finish.
7. The uninstall process may not delete files that were added or updated since the initial installation. To complete
the uninstall process, go to the location where you initially installed the Epicor application. For example, go
to \Epicor\Epicor905. Manually delete any existing files and folders.
22.3.4 Uninstall Epicor 9.05 Client
Use these instructions if you need to uninstall the Epicor 9.05 client from your workstation.
1. Close all Epicor 9.05 client instances that are running on your workstation.
2. Navigate to Control Panel > Programs and Features.
3. Right-click on Epicor 9.05 Client and select Uninstall from the menu.
4. In the Previous Install dialog, the Update or Uninstall a single instance option is selected by default. Use
the drop-down menu to select the instance. Click Next.
5. On the Shortcut Creation dialog, select the Uninstall this client check box. Click Next.
6. On the Confirmation dialog, click Yes. The Epicor 9.05 client is uninstalled.
7. When it is completed, click Finish.
80 9.05.701
8. The client uninstall process may not delete all the files that were added or updated since the initial installation.
To complete the uninstall process, go to the location where you initially installed the Epicor client. For
example, go to \Epicor905\Client. Manually delete any existing files and folders.
9.05.701 81
Additional information is available at the Education and
Documentation areas of the EPICweb Customer Portal. To access
this site, you need a Site ID and an EPICweb account. To create an
account, go to http://support.epicor.com.

Epicor905 Supplemental Install 905701

Caricato da

Informazioni sul documento

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Epicor905 Supplemental Install 905701

Caricato da

Copyright:

Formati disponibili

Epicor 9.

9.6 Manually Install Custom Assembly DLL File (Report Server).......................................................................30

18.1 Install Sonic on Windows.......................................................................................................................55

1 Welcome and Introduction

2 Configure 64-Bit Environment (Windows 2008)

2.1 Enable ASP .NET 2.0 Application (64-bit only)

1. Go to Internet Information Services (IIS) Manager.

2. From the Application Pools node, select DefaultAppPool.

4. Restart the Application Pool.

a. Request path: *.htm

a. Request path: *.html

3 Install Epicor Administration Console

3.1 Uninstall Epicor Administration Console

2. In the Welcome to the Epicor Utilities Setup wizard, click Next.

Epicor Administration Console is uninstalled.

3.2 Install Epicor Administration Console

2. In the Welcome to the Epicor Utilities Setup wizard, click Next.

4. In the Welcome dialog, click Next.

6. When the installation is complete, click Close.

The Epicor Administration Console is now installed.

4 Install BPM Server

4.1 Review BPM Server Prerequisites

2. Review the BPM Server components. The components include:

a. Navigate to Start > Run.

c. In the Connections area, select Application Pools.

e. Set the Enable 32-Bit Applications setting to True.

a. In the Installation Type dialog, select the Custom option.

4.2 Install BPM Server Components

3. Based on the operating system (32-bit or 64-bit) of your installation , double-click on

5 Install Epicor Enterprise Search

5.1 Verify SQL Server Prerequisites

1. Verify that you are using one of the following:

4. Verify you are running SQL Server locally.

a. Open SQL Server Management Studio and connect to your database.

b. Expand Security > Logins. Right-click on NT AUTHORITY\SYSTEM and select Properties.

d. Close SQL Server Management Studio.

5.2 Create Back Ups (if Previous Version)

2. Create a backup of the following folders: Templates, Profiles, and Tuning.

5.3 Uninstall Epicor Enterprise Search (if Previous Version)

2. In the Welcome to the Epicor Utilities Setup wizard, click Next.

Epicor Enterprise Search is uninstalled.

5.4 Install Epicor Enterprise Search Process

Use these steps to install Epicor Enterprise Search.

1. Log on to the server where you intend to install Enterprise Search.

3. On the Welcome to the Epicor Utilities Setup wizard, click Next.

5. On the Welcome dialog, click Next.

7. When the installation is complete, click Close.

5.5 Configure Replication Server for Epicor Enterprise Search

5.6 Configure Epicor Enterprise Search

a. On the Welcome page, review the process details. Click Next.

c. You are prompted to deploy Web Application. Click Next.

a. Begin with step 2 if you creating a new search index definition

6 Install Embedded Education Courses

6.1 Install Embedded Education Courses

3. On the Welcome to the Epicor Utilities Setup wizard, click Next.

a. Open the Internet Information Services Manager (IIS 6).

b. In the Connections tree view, select Application Pools.

d. In the Action panel, click on Advanced Settings.

e. Verify that Integrated is selected as the Managed Pipeline Mode.

g. Click OK to close the dialog and save your changes.

h. Close the IIS Management panel.

13. Click Create.

6.2 Configure Embedded Education Courses Client

Use these steps to configure the Embedded Education Course client.