Professional Documents
Culture Documents
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 2014.
All rights reserved. No part of this publication may be reproduced in any form without the prior written consent of
Epicor Software Corporation.
Contents
Contents
Part I: Getting Started......................................................................................7
Chapter 1: Verify Prerequisites...................................................................8
1.1 Verify Access to EPICweb....................................................................................................................8
1.2 Review Release Documents.................................................................................................................8
1.3 Verify Microsoft Tools Installation.....................................................................................................10
1.4 Verify Windows Operating System Requirements..............................................................................11
1.5 Verify SQL Server Install and Features................................................................................................12
1.6 Verify SQL Server Reporting Services (SSRS) Prerequisites...................................................................14
1.7 Verify Temporary Files Do Not Exist...................................................................................................15
1.8 Verify CSF Requirements (Optional)...................................................................................................16
Contents
Contents
Contents
Getting Started
Getting Started
Getting Started
2. In the Available Downloads list, locate and download the following four (4) release documents. Note that
the installation guide is available in three versions and you only need to download one version.
Release Documentation
Description
3. If you are on Vantage 8.03x, you must also download the Epicor Data Upgrade Utility (DUU) Guide
which is located on the EPICweb customer portal site under Epicor ERP version 9 > Documentation > Release
9.05.700. This guide includes instructions for upgrading from Vantage 8.03x to Epicor 9.05.702x. After
upgrading to Epicor 9.05.702x you would then use the Epicor ERP 10 Installation Guide (Migration version)
to upgrade your Epicor 9.05 application to Epicor ERP 10 and migrate your existing database into an Epicor
ERP 10 database.
4. If you previously downloaded any of the above release documents prior to following the steps in this section,
you must verify that you are using the latest version of the document. To do this:
Getting Started
a. On your release document (Release Notes, Architecture Guide, Installation Guide, or Supplemental Guide)
locate the Disclaimer page, which is before the Table of Contents.
b. Verify that the Revision date on that page is the same as the Revision date on the file that is currently
available from the EPICweb customer portal site.
c. If the Revision date is not the same, follow the above steps to download the release document from
EPICweb customer portal site.
10
Getting Started
4. If you want to use the Epicor Administration Console to remotely administer machines, you need to enable
the IIS Management Service. To do this:
Using Windows 7: Navigate to Start > Control Panel > Programs > Turn Windows features on or
off. In the Windows Features window, navigate to Internet Information Services > Web Management
Tools and select the IIS Management Service check box. Click OK. Click Close.
Using Windows 8: Navigate to Settings > Control Panel > Program and Features > Turn Windows
features on or off. In the Windows Features window, navigate to Internet Information Services >
Web Management Tools and select the IIS Management Service check box. Click OK. Click Close.
11
Getting Started
5. For the Epicor Administration Console, verify that port 8172 is open in the firewall. To do this, if you are
using the built-in Windows firewall, navigate to Start > Control Panel > Administrative Tools > Windows
Firewall with Advanced Security.
6. For the Epicor Administration Console, verify that in the Windows Firewall, the inbound rule "Web
Management Server (HTTP Traffic-In)" is enabled. To do this, open your Windows Firewall. Locate the
inbound rule named "Web Management Service (HTTP Traffic-in)". Right-click on the rule and select
Properties. Enter the following:
a. In the General tab, select Allow the connection in the Action group box.
b. In the Advanced tab, in the profiles section, clear the Public check box. This option should not be selected.
c. Keep the Domain and the Private options enabled.
Note The inbound rule "Web Management Server (HTTP Traffic-In)" should be enabled, if it exists.
If that rule is not present, then create your own inbound rule that opens port 8172 for TCP traffic.
7. With Windows Server 2008 R2 (SP1), a firewall is installed. The firewall must be disabled in order for
connectivity from other machines to allow for administering of the Epicor ERP 10 Application Servers. Based
on your company practices, you can enable your firewall after the installation process is complete.
12
Getting Started
3. If your SQL Server is hosted on a different machine than the Epicor ERP 10 Application Server, verify that
network connectivity exists between the servers. To do this, complete the following steps on the two
machines:
a. For the Application Server, do the following:
Add a domain account with Administrator permissions.
Log into the Application Server using the domain account with Administrator permissions.
b. For the SQL Server, do the following:
Add the domain account login (with Administrator permissions) to the Administrators group.
Verify the SQL Server service properties specifies "Log On As" that specific domain account.
In SQL Server Management Studio, create the domain account as a SQL login account with sysadmin
rights.
4. Verify that the Full-Text Search feature is installed on your SQL Server instance. Full-Text Search is required
in order to create databases using the Epicor ERP 10 application. To verify if the feature is installed:
a. Open SQL Server Management Studio. Right-click on your server/instance and select New Query.
Enter the following query:
SELECT fulltextserviceproperty('IsFulltextInstalled')
IF (1 = FULLTEXTSERVICEPROPERTY('IsFullTextInstalled')) print 'INSTALLED' else print 'NOT INSTALLED'
b. Click Execute. If the query returns 1 or INSTALLED it means that Full-Text Search is installed.
13
Getting Started
c. If the query returns 0 or NOT INSTALLED, you must install the Full-Text Search component. To do this:
Select Start > Control Panel > Programs and Features. In the list of programs, right-click MS SQL
Server installation and select Uninstall/Change. Click Add.
Use you MS SQL Server installation media to run SQL setup wizard.
In the Installation Type window, select the option to Add features to an existing instance of
SQL Server and specify the SQL Server instance you want to modify.
In the Feature Selection window, select the Full-Text Search check box. Click Next several times,
then click Complete to finish the component installation.
Note As an alternate method to verify if the Full-Text Search feature is enabled on your SQL Server,
you can review the list of services. To do this, on your SQL Server select Start > Control Panel >
Administrative Tools > Services. Verify that SQL Full-text Filter Daemon Launcher (SQL Server
Instance Name) service is listed, for example (MSSQLSERVER). Note that if your SQL Server has multiple
instances, you must verify that the service is available for the specific SQL Server instance.
14
Getting Started
Note For more information on installing Reporting Services Native Mode Report Server, review
the Microsoft SQL Server Documentation Online. You can use this link: http://technet.microsoft.c
om/en-us/library/ms143711.aspx
d. Verify that Report Server Status is Started.
e. On the left navigation pane, select Report Manager URL. In the Report Manager Site Identification
section that displays, do the following:
In the URLs field, click the URL to verify that it is valid. Your browser should open the SQL Server
Reporting Services home page.
Open a text editor, such as Notepad, and enter the URL exactly as it is displayed in the URLs field. For
example, your URL may look similar to: http://ServerName:xx/Reports. Save the notepad file. Note
that you will need to enter this URL later when you are adding an Epicor Application Server and
configuring SSRS on the SSRS Configuration > SSRS Base URL field.
f. Click Exit to close the Reporting Services Configuration Manager.
6. If you want to create custom reports, verify that you have one of the following installed on the machine
where you plan to customize the reports:
Business Intelligence Development Studio (BI Dev Studio). A component of a Visual Studio installation
that is used to develop reporting service projects.
Microsoft SQL Server Report Builder. A report authoring tool that uses a Microsoft Office-like authoring
environment that is simpler to use than Business Intelligence Development Studio. Note that you should
use Report Builder 2.0 if you use SQL Server 2008 R2 and Report Builder 3.0 if you use SQL Server 2012.
15
Getting Started
16
Getting Started
Use these steps to configure the Application Server role and the Web Server role using Windows Server 2012.
Note that if the roles already exist, you can still review the list of role features to verify that your roles are configured
properly.
1. On the server, open Server Manager.
2. To verify if the roles already exist:
a. In the left pane, select the App Servers node.
b. In the Roles and Features section, verify if the Application Server and the Web Server (IIS) roles are
listed. Your dialog may look similar to the following:
3. If the Server roles are listed, in the same Roles and Features section verify that the required Server roles
services have been installed. You can find the list of required Server roles services in steps 11 and 13 below.
17
Getting Started
4. If the Server roles are not listed, from the Manage menu, select Add Roles and Features. Your dialog
may look similar to the following:
5. The Add Roles and Features Wizard appears. In the Before You Begin section, review the information and
click Next.
6. In the Installation Type section, keep the default Role-Based or Feature-Based Installation option selected.
Click Next.
7. In the Server Selection section, verify your server is selected in the Server Pool list. Click Next.
8. In the Server Roles section, select the Application Server role and the Web Server (IIS) role.
The IIS Management Console is required for the Web Server role installation. Click Add Features to confirm
the installation. Click Next.
9. In the Features section, verify that .NET Framework 4.5 is selected. Click Next.
10. In the Application Server section, click Next.
11. In the Role Services section, select the following options and click Next.
COM+ Network Access
TCP Port Sharing
Windows Process Activation Service Support
HTTP Activation
Message Queuing Activation
Named Pipes Activation
TCP Activation
Distributed Transactions
Incoming Network Transactions
Outgoing Network Transactions
18
Getting Started
In the Add Roles and Features Wizard, confirm installation of the selected services. Your screen may look
similar to the following:
19
Getting Started
In the Add Roles and Features Wizard, confirm installation of the selected services. Click Next.
14. In the Confirmation section, click Install. The Web Server role and features are installed.
15. Close the Server Manager.
Use these steps to configure the Application Server role and the Web Server (IIS) role using Windows Server 2008
R2. Note that if the server roles already exist, you can still review the list of role features to verify that your roles
are configured properly.
1. On the server, open Server Manager. Select the Roles node.
2. Go to the Roles Summary section and verify if the Application Server and the Web Server roles are listed.
3. If the Server roles are listed, click the Add Role Services link on the right side. Then use the step below
regarding the Application Server dialog to verify that the required Application Server role services are installed.
4. If the Server roles are not listed, click Add Roles. The Add Roles Wizard appears. Click Next.
5. On the Server Roles dialog, do the following:
a. Select Application Server.
b. Select Web Server (IIS).
Click Next.
6. On the Application Server dialog, review the noted comments and click Next. On the Role Services dialog,
notice that .NET Framework 4.5 is already selected for you. Select these additional services and then click
Next:
COM+ Network Access
TCP Port Sharing
Windows Process Activation Service Support
Message Queuing Activation
TCP Activation
Named Pipes Activation
Distributed Transactions
Incoming Remote Transactions
Outgoing Remote Transactions
7. On the Web Server dialog, review the noted comments and click Next. On the Role Services dialog, select
the following services to be installed:
Common HTTP Features
Default Document
20
Getting Started
Directory Browsing
HTTP Errors
Static Content
Application Development
ASP.NET
ISAPI Extensions
ISAPI Filters
.NET Extensibility
Health and Diagnostics
HTTP Logging
Tracing
Performance
Static Content Compression
Security
Request Filtering
Windows Authentication
Click Next.
8. Confirm installation of the selected services. Click Install.
9. The Application Server Role and features are installed. Click Close.
21
22
2. Double-click on the file to run it. The install wizard verifies that the install executable is compatible with your
environment and then prepares for your installation. This verification may take several minutes.
3. The Welcome window appears for installing the Epicor ERP 10 server software. Click Next.
4. The Select Components window appears. Select the program features you want to install, such as the
Application Server and Supplemental Installs. In the Install Epicor ERP 10.0 to field accept the default
location of C:\Epicor\ERP10 or click Change to browse and select a different location. Your dialog may look
similar to the following:
5. After selecting the components to install and specifying the installation location, click Next.
23
6. The Completing the Epicor Install window appears. To begin the configuration of Epicor ERP 10, click Next.
The installation begins. The process may take several minutes. Your dialog may look similar to the following:
7. After the Epicor ERP 10.0 Server is installed, the following installations are processed:
Expanding Epicor ERP 10.0 Client Installer
Expanding Epicor ERP 10.0 Administration Console Installer
Expanding Epicor ERP 10.0 Education Courses
Expanding Epicor ERP 10.0 Reporting Services
Expanding Epicor ERP 10.0 Supplemental Installs (Mobile Access, Sharepoint Publisher, Social Enterprise,
Enterprise Search, Task Agent, and Web Access)
Installing Administration Console
8. The Install Complete window appears when the installation is complete. Based on the availability of an
Update release, do one of the following:
If an Update release (10.0.700.x)is available, clear the Launch the Epicor Administration Console
check box. You will need to install the Update release prior to launching the Epicor Administration
Console.
If an Update release (10.0.700.x) is not available, keep the Launch the Epicor Administration Console
check box selected. You will now use the instructions in the following sections to complete the
configuration using the Epicor Administration Console.
Your dialog may look similar to the following:
24
25
On the server, press <Windows> + F to display the Charms bar and select Apps. Alternatively, on the
Start screen, right-click the background and in the lower right corner select all Apps. On the Apps screen,
select Epicor Software > Epicor Administration Console.
On the server, navigate to Start > All Programs > Epicor Software > Epicor Administrative Tools
> Epicor Administration Console.
2. In the left-hand Tree View, select the Database Server Management node. Your dialog may look similar
to the following:
26
3. Right-click on the Database Server Management node and select Add Epicor Database Server. Your
dialog may look similar to the following:
4. In the Server\Instance field, enter the SQL Server name and the SQL Instance ID. For example, enter your
local server or the network server to which you will be connecting.
5. Select the Authentication mode to connect to the SQL Server. For example, select Windows Authentication
or SQL Authentication. If you select SQL Authentication you must also enter your SQL User ID and Password.
Note The SQL User ID and Password you specify will be passed to the configuration when you add
a new Epicor database.
6. Click the Verify Server button to verify that your server name and connection details are valid. Click OK
to the message. Click OK again.
7. After the server is added, the server/instance is displayed as a node under Database Server Management in
the Tree View. Your dialog may look similar to the following:
After the server is added, you are now ready to add your Epicor database. For example, you can add a new
database (for production) or add the demo database (for training).
27
28
b. Enter the Deployment Server path to specify the deployment share location. This path is used by the
Epicor Administration Console to verify that it has the required components to service the database.
These components can then be downloaded from this location.
If you are on the deployment server, enter a fully qualified path such as C:\Epicor\ERP10\ERP10.0.xxx.
c. Click OK.
5. The Create Database on Server dialog displays. If the database creation process does not start by default,
click the Start button. A status bar displays the creation process. This may take a few minutes. Your dialog
may look similar to the following:
6. If you selected Add New Database, the database is ready to be created using the default values. If you
want to change the default values and configure the database properties before it is created, from the
Action menu on the Create Database on Server dialog, select Configuration. Your dialog may look similar
to the following:
7. For the Target database, verify the Master Database File (MDF) Information. Note that for more
information on MDF settings, refer to your Microsoft SQL Server user guides and online help.
a. In the MDF Location field, verify the default path to the master database file.
b. Review the Initial MDF File Size in GB value. Epicor recommends to set this value close to the size of
the future master database file.
29
c. Keep the Autogrowth check box selected if you want the file to increase automatically when new data
is added. In the Autogrowth settings section, use the MDF File Growth fields to specify the file growth
rate. Select the Restricted File Size Growth option and set the maximum size for the MDF file if you
want to limit this value, or keep the Unrestricted File Size Growth option selected. If you use MDF
autogrowth and do not restrict the file size, the MDF file should be regularly monitored and managed
by a database administrator.
8. For the Target database, verify the Log Database File (LDF) Information. Note that for more information
on LDF settings, refer to your Microsoft SQL Server user guides and online help.
a. In the LDF Location field, verify the path to the log database file.
b. Specify the Initial LDF File Size in GB value. Epicor recommends to set this value close to the size of
the future log database file.
c. Keep the Autogrowth check box selected if you want the file to increase automatically when new data
is added. Define Autogrowth settings. Use the LDF File Growth fields to specify the file growth rate.
Select the Restricted File Size Growth option and set the maximum size for the LDF file if you want
to limit this value, or keep the Unrestricted File Size Growth option selected. If you use LDF autogrowth
and do not restrict the file size, the LDF file should be regularly monitored and managed by a database
administrator.
9. Click Test Connection to verify. Click OK to the validation message.
10. Click OK to save the configuration values. The Configuration dialog closes.
11. Back on the Create Database on Server dialog, click Start. The processing begins. This may take a bit of
time. If you want to view the processing messages, click the Show More button. If you want to hide the
processing messages, click the Show Less button. Your dialog may look similar to the following:
Note If the database name already exists you are prompted with a message to enter a password to
confirm that the existing database should be deleted in order for the new database to be created. Your
dialog may look similar to the following:
30
12. During the creation of the database, progress is displayed using green check marks next to the task. Note
that if a task is not successful, a red X is displayed. After the database is created a green check mark is
displayed next to each task. Verify that your tasks have all completed. Your dialog may look similar to the
following:
13. After completion, click the Show Log button to display the DB Migration log. Review the information. Your
dialog may look similar to the following:
31
16. Verify that your new database displays under your Server in the tree node. Your dialog may look similar to
the following:
7. Click OK.
32
33
8. In the Permissions for <file name> window, click the Add button.
9. In the Enter the object names to select field, enter Everyone. Click OK.
10. Click Everyone in the Group or user names list. In the Permissions for Everyone pane, select the Allow
check box against the Full control permission. Click OK.
11. Click OK in the Properties window and exit the MachineKeys folder.
3. Enter the Name of your server. Click Ping Server to verify your server name. A message displays that it is
successful. Click OK.
4. Verify that your Epicor Server is added under the Server Management node. You can now add an Epicor
Application Server to this Epicor Server.
34
2. Right-click on the Epicor server and select Add Application Server. The Application Server Setup dialog
opens. Your dialog may look similar to the following:
35
b. Enter the Deployment Directory that contains the Epicor server installation. For
example:\\EpicorServer\Epicor\ERP10\ERP10.0.700.
Note You must be a member of the Administrators group on the server specified.
c. The Web Site Directory identifies the server machine that will contain the application server. The
application server is installed in this location. Verify that the path includes the Application Name that
you just entered. For example: C:\Inetpub\wwwroot\EpicorERP100700.
d. Use the drop-down menu to select your Net TCP Binding Configuration to define how this application
server checks for authentication certificates through Internet Information Services (IIS). When a user logs
into the application, the selected method verifies the communications are encrypted and checks whether
the user can access the Epicor application. Options include:
UsernameWindowsChannel. Select this option to authenticate using an Epicor Username and
Password on a Windows Domain. Windows ensures communications are encrypted while the username
and password are managed in Epicor. You can use this method for both smart client and Epicor Web
Access (EWA) installation.
UsernameSSLChannel. Select this option to authenticate using an Epicor Username and Password
on a non-Windows Domain or across two untrusted Windows Domains. A Secure Sockets Layer (SSL)
X509 certificate is used to encrypt the communications while the username and password are managed
in Epicor.
When you select this option, you may need to define a DNS Endpoint Identity if your SSL certificate
and server name are different. You can use this method for both smart client and Epicor Web Access
(EWA) installations.
Note If you plan to use Digital Certificates, you must select UsernameSSLChannel. Refer to
the Technology Strategies > SSL: Review Digital Certificates for Epicor 10 section in the Epicor
Architecture Guide for more information on the digital certificate options available in your
Epicor ERP application.
Windows. This type of authentication replaces the Epicor 9.05 Single Sign On method. It authenticates
and encrypts communications using Windows Domains. Select this method for AppServers that handle
client installations where users access the application through the same domain. If you select this
option, you do not enter a Username/Password for the task agent; instead you define this domain
user account on the Windows service. You can only use this method on smart client installations.
4. In the Server Information group box, use the fields to update your Epicor ERP 10 application to an updated
version. Fields include:
a. Version. Use the drop-down to select your update version from the list of updates that are available on
your server. You previously installed these updates using the steps in the Install Epicor ERP 10 Update
(10.0.700.x) section. For example, select 10.0.700.x to select to update your Epicor ERP version to
10.0.700.x. It is recommended that you select the latest update available. If no updates are available,
you can select Base. Note that when you click OK, the application server updates the Epicor ERP 10
application to the selected version. If prompted that all users will be disconnected while the system is
being updated, verify that all users have logged out of the system and then click Yes to continue.
b. Custom Directory. If you have custom programs to incorporate with the Epicor application, browse
and select the Custom Directory that contains these custom .dll files. After you click OK on this window,
these custom .dll files are included in the Epicor application.
36
Note When you finish creating or modifying the application server and click OK, the application
server checks each folder (in sequential order) to determine what version to install:
Base Directory. This directory contains the primary installation for the Epicor application. The update
process always starts with this base version.
Custom Directory. The application lastly checks if customizations are available. If custom programs
are in this directory, the Epicor application applies these customizations over the base version.
c. Shared Assembly Location. Select this check box if you have a network load balanced (NLB) environment,
for example if you have the Epicor ERP 10 application installed on more than one server. This is the
location that will include the Assemblies and BPM folders. After selecting the check box, you must select
a Shared Directory in the next field.
d. Shared Directory. Select the directory of the Shared Assembly Location. This directory can be a
network shared location or a local file path. Note that if your appservers will be on separate machines
you must select a network shared location.
5. In the Application Pool group box, enter the following fields:
a. By default the Application Pool Name uses the value you entered in the Application Name field. You
cannot change this value. This value defines the name of the application pool associated with the new
application server. An application pool defines a group of related URLs that use the same process or set
of processes. The new application server must be placed in an application pool.
b. Use Custom Account. Select this check box when you need to enter a specific user account for the
Internet Information Services (IIS) application pool this application server uses. If you select to use a
custom account, you must also enter the following:
Application Pool Username. Enter the domain and the user account. For example,
MyDomain\UserName.
Application Pool Password Enter the password associated with the user account for this application
pool.
Note If you do not select this check box, the application pool uses a default user account. This
default account depends on whether you use an SSRS server. If you use an SSRS server, the
connection uses the LocalSystem account. This is the default user account available through the
Windows operating system. If you do not use an SSRS server, the connection uses the
ApplicationPoolIdentity account. This is the default user account available through Internet
Information Services (IIS).
Do not click OK yet. You must complete the other tabs before submitting the information. If you click
OK, you may receive a message that your data entry is not complete on the other tabs.
37
6. Select the Database Connection tab. Your dialog may look similar to the following:
38
7. Navigate to the Admin Console Settings tab. Your dialog may look similar to the following:
c. Enter the Operation timeout value you want for the application server. This value determines the wait
time until an incomplete operation is stopped by the application server. The default value is 300 seconds.
d. Select or clear the Validate WCF Certificate check box. This indicates whether the client application
and WCF service need to validate their connection through a certificate. If this check box is selected, a
certificate is required for the client installation to communicate with the WCF service.
e. For DNS Identity value, enter the expected DNS server name. There are two scenarios where you need
to enter a value in this field:
UsernameSSLChannel Selected in Endpoint Binding. When authenticating using message-level
or transport-level Secure Sockets Layer (SSL) with X.509 certificates, WCF ensures that the certificate
provided during the SSL handshake contains a DNS or Common Name (CN) attribute equal to the
value specified in this field.
Windows Selected in Endpoint Binding. When the service authenticates using message-level or
transport-level SSL with a Windows credential for authentication, and negotiates the credential, then
the negotiation passes the service principal name (SPN) so that the DNS name can be checked. The
SPN is in the form host/<dns name>.
39
f. In the Epicor Application Launcher group box, select one of the following options to define how you
want to access the client from within the Epicor Administration Console:
Do not allow access to user details. No method is used to launch the Epicor client. The default
value, the client is launched as normal from within the Epicor Administration Console.
Use Epicor Smart Client. If you select Use Epicor Smart Client, you must click the Browse (...) button
to find and select the Epicor.exe file that you will use to launch the Epicor client.
Use Epicor Web Access. If you use Epicor Web Access, select this option and click the drop-down
list to define the URL for the web access. This drop-down list contains the web access values defined
in the company configuration data for Epicor Web Access (set within the client).
8. Navigate to the SSRS Configuration tab. Your dialog may look similar to the following:
40
c. Optionally, enter the SSRS Root Folder location. This directory defines the root folder location where
you will deploy the reports. For example, enter Epicor if you want the reports to deploy to the
Epicor/Reports folder. If you leave the field blank, this root folder will be the directory that contains the
report server home page file, and the reports will deploy to the /Reports sub-folder in this directory.
9. In the SSRS Database Connection group box, enter the following:
a. In the Server Name field enter the name of the database for the Report Server. The value you enter in
this field depends on how you have set up your system. This database can be:
The same database used by the Epicor application -- Although this set up is not recommended, your
report server database can be the same as your main database.
A separate database on the SQL Server -- This set up method is most common, as the report data
then populates this separate database on the server.
A database on a different SQL Server -- The report data from the Epicor application is sent to another
server dedicated to SSRS report processing. If you are a larger organization, you may set up your
system in this way to improve performance.
b. Click the Authentication drop-down list and select either the Windows Authentication or SQL Server
Authentication option.
If you select Windows Authentication, the User and Password default to your current login values.
If you select SQL Server Authentication, enter the User and Password you use to log into SQL
Server.
c. In the Database Name field enter the name of the database that will hold the temporary data used by
reporting. Click the Down Arrow next to this drop-down list; select the database you need from the list
of options.
d. To create a database for SSRS, select the Create DB check box. When you select this option and click
OK, a new report database is generated using the name you entered in the Server Name field.
e. When you finish defining your SSRS options, click the Test Connection button. A message should display
indicating that this application server is connected to SSRS. If you receive an error, check your values to
make sure they are accurate and then test the connection again.
10. In the SSRS Deployment group box, enter the following:
a. Verify the Import Reports check box is selected. This indicates you are ready to import your reports.
Note that if you are updating the application server and you do not need to import the SSRS reports,
you must clear the Import Reports check box.
b. For the SSRS Location, select the directory that contains the latest SQL Server SSRS ReportServer
installation. Depending on your SQL Server version, this location is similar to the following example
directories. Your specific directory path will be the name your system administrator assigned to the SQL
Server instance during installation.
SQL Server 2012. C:\Program Files\Microsoft SQL Server\MSRS11.MSSQLSERVER\Reporting
Services\ReportServer
SQL Server 2008 R2. C:\Program Files\Microsoft SQL Server\MSRS10_50.MSSQLSERVER\Reporting
Services\ReportServer
If the SSRS server is on a separate machine, enter the UNC path to the ReportServer directory. The current
user account must have permissions to write to this remote directory. Typically this directory is:
41
11. After completing all the tabs, click OK. A status window displays progress through the application server
setup steps. After the server files are extracted, your display may look similar to the following:
12. When setup server environment is complete, a message appears saying the setup is successful. Click OK. If
you receive an error message, resolve the issue and restart these steps to add an Epicor Application Server.
13. If you have selected to use the UserNameSSLChannel endpoint binding, you now must edit the web.config
file to enter a value. To do this:
a. Navigate to your Epicor ERP 10 application server web.config file. To do this, go to Start > Run and
type inetmgr. Under the Sites node, right-click on your application server and select Explore. Open the
web.config file with a text editor.
b. Remove the comment identifiers on the serviceCredentials node.
Currently, the node with the comment identifiers looks similar to:
<!-- <serviceCredentials>
<serviceCertificate x509FindType="FindBySubjectName"
findValue="<servername>.name.local" storeLocation="LocalMachine"
storeName="My" />
<userNameAuthentication userNamePasswordValidationMode="Custom"
customUserNamePasswordValidatorType="Ice.Security.UsernameValidator,
Epicor.Ice, Culture=neutral, PublicKeyToken=5d3fa3c7105d7992" />
<clientCertificate>
<authentication revocationMode="NoCheck"
certificateValidationMode="PeerTrust" />
</clientCertificate>
</serviceCredentials>
-->
42
After editing, the node without the comment identifier looks similar to:
<serviceCredentials>
<serviceCertificate x509FindType="FindBySubjectName" findValue="certificate
name" storeLocation="LocalMachine" storeName="My" />
<userNameAuthentication userNamePasswordValidationMode="Custom"
customUserNamePasswordValidatorType="Ice.Security.UsernameValidator,
Epicor.Ice, Culture=neutral, PublicKeyToken=5d3fa3c7105d7992" />
<clientCertificate>
<authentication revocationMode="NoCheck"
certificateValidationMode="PeerTrust" />
</clientCertificate>
</serviceCredentials>
c. Locate the <serviceCertificate> line. Change the value of the findValue attribute. The findValue is the
name of the certificate you just created. For example, enter the fully qualified domain name.
d. Save the file.
14. Verify that your new Epicor Application Server is listed under the Server node in the Tree View. Click the
application server. The Epicor Administration Console connects to the application server and the property
details are displayed in the center pane. Your display may look similar to the following:
43
4. Browse to the location where you previously downloaded the license code file. Select the file and click Open
to import the file.
5. In the middle pane, double-click on the licensing code file to open it. The Properties dialog opens.
6. Click the Modules tab. Select the check box for each module you want enabled. Click OK.
Note It is recommended that you carefully review the modules that you have selected to enable.
Failure to enable your modules may result in possible data corruption. Also, if you enable a new module
at this time, you are committing to basic configuration and implementation steps within the application.
7. Repeat the above steps, if you are importing license files for multiple databases.
You are now ready to add a company and assign the license file to that company.
44
45
4. Click OK to save. Your new company is created. It may take a period of time to finish processing.
5. After the company is created, you can select the Companies node to view your company and properties.
6. Repeat these steps to add additional companies, if desired.
46
5. Click the Country Specific Functionality tab. Select the check box for each country you want enabled.
Click OK.
Your dialog may look similar to the following:
Note It is recommended that you carefully review the CSFs that you have selected to enable. Failure
to enable your CSFs may result in possible data corruption. Also, if you enable a new CSF, you must
perform CSF configuration and implementation steps within the application. For more information
on how to perform additional configurations, review Epicor 10 Supplemental Guide and CSF
Functionality Guides.
47
Post-Installation
48
Post-Installation
2. Navigate to System Setup > System Maintenance > System Agent. Your System Agent name and
properties are displayed. Your screen may look similar to the following:
3. Complete one of the following steps depending on the application server you are viewing:
If you are verifying your Epicor Application Server, in the System App Server section, for your User
Name you must reset the Password by clearing the field. Then, reenter your valid password.
Important Do NOT skip this step! After the migration process, your System Agent user account
password is not valid. You MUST reenter the System Agent password for your Epicor application
to work properly.
If you are verifying your Demonstration Database, the Username in the System App Server section
defaults to print. Enter the Password as print.
4. Verify your directory paths are accurate. For example:
Directory
Description
Examples
Server File
Client File
\\<servername>\ERP10.0.xxx\EpicorData
Client Program
\\<servername>\ERP10.0.xxx\Server or
C:\inetpub\wwwroot\<IIS Site Name>\server
(See note below)
Note It is recommended that you set up your Task Agent using C:\inetpub\wwwroot\<IIS Site
Name>\server for your Client Program directory path.
5. Click Save.
49
Post-Installation
6. You must now configure the client program Server directory so that the user IIS_IUSRS has read and write
permissions. The steps differ based on your environment:
Windows Server 2008 R2
a. Right-click the Server folder and select Properties.
b. On the Sharing tab, click the Share button. After the share is complete, click Done.
c. On the Security tab, select the IIS_IUSRS group from the Group or user names list.
d. Click the Edit button. Re-select the IIS_IUSRS group.
e. In the Permissions for IIS_IUSRS list, select the Write check box in the Allow column.
Note The selected group now has Allow selected for Read & Execute, List Folder Contents, Read,
and Write.
Windows Server 2012
a. On the Server folder, click Select Folder. Click Next.
b. On the Share Name dialog, do not change the share name. Note the local path and the remote path
displayed. Click Next.
c. On the Other Settings dialog, keep the default settings. Click Next.
d. On the Permissions dialog, click the Customize Permissions button.
e. On the Permissions tab, assign Write permissions to IIS_IUSRS group. The IIS_IUSRS group should
have Allow selected for Read & Execute, List Folder Contents, Read, and Write.
f. On the Share tab, select to share this folder.
g. Click OK to accept the permissions. Click Next.
h. On the Confirmation dialog, review the settings and click Create. Then click the Close button to close
the New Share Wizard.
7. Click OK until you exit.
50
Post-Installation
installed on the same machine. Through this feature, you can have multiple versions of the service running at
the same time. In the control panel, each instance of the service displays as a separate icon identified by its version
number.
1. Navigate to the Task Agent folder in the path where your Epicor application is installed. For example, go
to C:\Epicor\[product]\[product version]\SupplementalInstalls\Task Agent.
Note If you have installed an update to the base Epicor ERP 10 application, for example, Epicor ERP
10.0.700.x, you must use the updated installer. For example, go to C:\Epicor\[product]\[product
version]\Updates\[update version]\SupplementalInstalls\Task Agent.
2. Double-click the Task Agent Service Installer.exe file to run it. An Epicor Task Agent Service Setup window
appears. Click Next. Your dialog may look similar to the following:
3. In the Choose Folder dialog, select the folder where the Task Agent should be installed. The default path is
C:\Program Files (x86)\Epicor Software\Task Agent Service. Click Next. Your dialog may look similar to the
following:
4. In the Program Group Name dialog, enter a Program Group Name. The default is Task Agent Service
x.x.x.x., where x.x.x.x is the ICE version installed with the service.
5. Select whether to create shortcuts for all users of this computer or only for yourself. Click Next.
6. In the Ready to Install dialog, click Next to proceed. The Epicor Task Agent Service is installed.
51
Post-Installation
9. To add a task agent service, from File, select New Task Agent. Your dialog may look similar to the following:
10. In the Add Task Agent dialog, enter a unique Name for your Task Agent. For example, ERP10TaskAgent.
11. Enter the AppServer URL to define the URL that connects the task agent to the application server (AppServer).
To locate this URL, you can open the *.sysconfig file for your application and locate the AppServerURL node.
Copy the value from that node to this AppSeverURL field. For example, your AppServer URL may look similar
to the following: net.tcp://<app server name>/ERP10/
Note A correct URL format in the Add Task Agent dialog must end with a / (forward slash) symbol.
Verify that the / symbol is at the end of the AppServer URL.
52
Post-Installation
12. Use the drop-down menu to select the Endpoint Binding for the task agent. This binding must match
what you previously defined in the Setup Environment screen when adding the Epicor Application Server.
13. Enter the Epicor ERP 10 User ID and User Password that the Task Agent uses to access the Epicor application.
Note In addition to the User ID being a valid user for accessing the Epicor application, it must also
have rights to Allow Session Impersonation. Note that you set up your Task Agent User Id using
the steps in the previous section.
14. Select the Operation Timeout value to define how long, in seconds, it takes a server call to generate an
error and fail.
15. If an error occurs, the task agent will try to send the call back to the server. Select the Max Connection
Attempts value to define how many times the task agent will attempt to send the call again.
16. Select the Max Concurrent Tasks value to define how many calls the task agent can send to the application
server at the same time. Change the value to reflect the capacity of your application server.
17. If you selected UsernameSSLChannel for the Endpoint Binding, the following two check boxes become
active:
Validate WCF Certificate. Select this check box to specify that the task agent service must verify that
the Secure Sockets Layer (SSL) Certificate is valid. If you use a self-signed certificate, do not select this
check box.
DNS Endpoint Identity. Enter the expected Domain Name System (DNS) identity of the server. When
the system runs X509 SSL Certificate authentication, it uses this identity value to validate the server. If
the SSL certificate contains a DNS Endpoint Identity with the same value, the server is valid and can be
accessed by the task agent.
18. When all the fields are complete, verify that the Enabled check box is selected.
19. Click Save. Your Task Agent is now added and enabled. A green icon indicates it is active. Your dialog may
look similar to the following:
53
Post-Installation
Note If a task agent already exists for this application server and you attempt to save, you will receive
an error. To create a new task agent for this database, you must first delete the existing task agent.
After the task agent is removed, repeat these steps.
54
Post-Installation
a. Select Start > All 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, verify if Windows Search has a status of installed. If not, click Add Role Services,
select Windows Search Service and click Install.
3. Verify that Windows Search is installed on the server (Windows Server 2012). To verify (and install if needed),
do the following:
a. Select Start > All Programs > Administrative Tools > Server Manager.
b. Under Local Server, view Roles and Features. If Windows Search Service is not listed, continue to the
next step.
c. Under Roles and Features, click Tasks > Add Roles or Features. In the wizard that opens, select
Server Selection (making sure your local server is selected) and then select Features. Scroll to and select
the Windows Search Service check box. Finish the wizard to complete the installation.
55
Post-Installation
7. Click Create Virtual Directory. A virtual directory is created for the physical directory listed as the Physical
directory of Help folder.
8. Click Switch to Windows Indexed Search. The help files are now set to be 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 30 minutes before expecting
a successful test of the help search. Test by clicking the Test button and entering a search term (such
as "Epicor") in the help.
9. Edit each client .sysconfig configuration file to use the help URL you just created. Alternatively, you can
edit the sysconfig file on the server if you have processes in place that push updated server files to your
client workstations.
To edit the sysconfig file:
a. On your workstation, navigate to the Client\Config folder or on your server, navigate to the
ClientDeployment folder.
b. Open the .sysconfig 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 as the Help URL for client configuration file in the Epicor Help Search Setup. For example, if
your web server has an alias or DNS name of EpicorOne, the edited line would look like <helpServer
uri="http://EpicorOne/EpicorHelp/" />
d. Save and close the sysconfig file.
56
Post-Installation
57
Post-Installation
b. On the Share tab, it is recommended that you assign Full Control to the Everyone group.
c. Click OK to accept the permissions. Click Next.
10. On the Confirmation dialog, review the settings and click Create. Then click the Close button to close the
New Share Wizard.
58
Post-Installation
5. The Shortcut Creation window appears. Select the check boxes for the client shortcuts that you want to
create. Select the Create Desktop Icons check box to create the icons. Click Next. Your dialog may look
similar to the following:
6. The Ready to Install window appears. Click Next. Your dialog may look similar to the following:
59
Post-Installation
7. The client installation begins. A status bar displays the progress of the installation. Your dialog may look
similar to the following:
8. When the installation is complete, click Finish to complete. If prompted, reboot the workstation.
9. You can now log in to the Epicor ERP client. Note that when you log in for the first time, the client files are
extracted. This may take a few minutes.
10. If you want to install the client on additional workstations, you can use the following steps to run a batch
file that installs the client without any manual intervention.
a. Navigate to the client installer location. For example, go to Epicor\ERP10\ERP10.0.xxx\Utilities\ClientInstaller.
b. Run the E10Client.exe file. After running this file for the first time, the silent.bat file is created. This
batch file stores the parameter information that was used when you ran the E10Client.exe file.
c. To run the client installation without any manual intervention, you can double-click the silent.bat file,
located in the same directory as the E10Client.exe. The batch file runs the E10Client.exe file without
requiring any manual intervention to answer prompts.
Note If you move the E10Client.exe file to a different directory, you must also edit the silent.bat
run command to specify the new path. For example, if you move the file to c:\epicor, you must
update the path from E10Client.exe /s to \\server\epicor\clientinstaller\E10Client.exe /s.
60
Troubleshooting
2. Right-click the Setup.exe file and select Run as Administrator. A Welcome window appears. Click Next.
Your dialog may look similar to the following:
61
Troubleshooting
5. Select one or more .XML files. You can select multiple files by pressing the Shift key while you highlight
the files. Click Open to select the highlighted files.
6. Select the Import All check box to specify that you want to import all the selected XML files. To specify
individual XML files instead, you can select the Selected check box for each file.
7. If this is not the first time you are importing posting rule files, you can select the Replace All check box to
replace your existing revision with the same name. To specify to replace individual XML files instead, you
can select the Replace Existing check box for each file.
8. Select the Change All Revision Statuses To Active check box if you want to change the revision from a
draft to active for all transaction types being imported. To specify to activate individual XML files instead,
you can select the Activate check box for each file.
9. Select the Import into all companies check box if you want to import the posting rules into each company.
Note that newly created revisions are automatically set to Active in all companies.
10. Click OK to begin the import.
11. You may be prompted with the Book Mapping dialog if any imported revisions contain books with IDs that
do not exist in the company to which you are importing rules. Do the following and click OK:
Specify the mapping to select which book in the company should receive rules from which book in the
import xml file. The import program verifies if the imported rules use segments that don't exist or are
defined with a different name in the receiving book's Chart of Accounts (COA). If such segments exist,
you must either manually select the correct segment of the receiving COA that should be used or specify
that these segments should be assigned new values during the import.
62
Troubleshooting
If you want to map the selected book identifier to all transaction types, select the Use for all transaction
types check box.
12. Click Save to save your imported financial data.
Note To copy the rules from one book to another, you can use GL Transaction Type Maintenance.
You create a revision, and then copy both the header and detail rules one at a time into a new book.
Then activate the revision.
If it is not listed, expand erp = Tables and select the matching table that you previously selected in
the Current Data Source. Note that in some cases, Crystal cannot map a column and the Map Field
window opens and you have to manually map the column. If the column does not exist, make sure
you did not select Match type. You may need to try several times to match an unmapped field.
63
Troubleshooting
Note Typically you must match with the View before you match the table since the View includes
all the Extended Columns. If you are matching against a table and the next table name has the
exact table name plus "_UD", you are matching against the wrong table. In this case you should
match against a View.
d. Repeat the above steps until each table is moved to the new datasource.
4. Click on Preview the report. View the report
Note If you are prompted with a message that "Boolean is required here" change 1 to true and 0
to false to match the datatype used in Epicor ERP 10.
64
Troubleshooting
\Epicor\ERP10\custom
\Epicor\ERP10\csg
\Epicor\ERP10\server\reports
2. Navigate to Control Panel > Programs and Features.
3. Right-click Epicor ERP 10.0 and select Uninstall from the context menu.
4. On the Uninstall Epicor ERP 10.0 dialog, click Next.
5. On the confirmation dialog, click Yes to confirm the removal of the Epicor ERP application. The Epicor ERP
application is uninstalled.
6. On the completion window, 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\ERP10. Manually delete any existing files and folders.
65
Troubleshooting
Possible Resolution
During the installation, you may receive this error if the attributes
of the file being processed are read-only.
When adding a new application server, you may receive this error
if your server does not have the required roles configured. Refer
to the section "Getting Started > Perform Pre-Installation Steps >
Configure Server Roles" for instructions on configuring your server
roles.
MSDTC on server 'servername' is unavailable Error occurs when a stand-alone instance of Microsoft SQL Server
exists in a cluster environment and is set to start automatically. If
the host node is re-booted, you may receive this error, as the
MSDTC service is shut off. To resolve, navigate to Control Panel >
Administrative Tools > Services and start the Microsoft Distributed
Transaction Coordinator (MSDTC) service. In Windows 8, press the
<Windows> +F keys to display the Search bar. Select the Apps
icon, launch the Component Services application and Start the
service.
System Out of Memory
If you are using the 32-bit client, you may be trying to process too
many dashboards or BAQs at one time. To resolve this issue,
consider using the 64-bit client since it uses more than 2GB memory
which should avoid memory issues.
System Configuration problem. No default As a post-installation step, you must install and configure the Task
agent defined.
Agent.
The authorization credential is expired
WCF http activation is enabled (system hangs While creating or updating an application server, the Setup
on this task)
Environment dialog process hangs on the "WCF http activation is
enabled" task when Microsoft Updates are available and haven't
been applied. To resolve the issue, install the Microsoft Updates
and reboot your system.
66
Troubleshooting
67
Troubleshooting
data, you may consider editing the web.config file to increase the time allowed by modifying the configuration
setting that defines time out values for processing transactions.
1. Open your web.config. file. To do this:
a. Start IIS Manager.
b. Navigate to your Epicor application server virtual directory. For example, ERP100700.
c. Right-click on the folder and select Explore to open Windows Explorer.
d. Open the web.config file in the root of the folder that opens. For example, go to
C:\inetpub\wwwroot\ERP100700\Server.
2. Locate the <system.transactions> node in the <configuration> section. Your file may look similar to the
following:
<system.transactions>
<defaultSettings timeout="00:05:00" />
</system.transactions>
</configuration>
3. Edit the <defaultSettings timeout="00:05:00"> which defaults to five minutes. You can increase this
value up to ten minutes (00:10:00).
Note This maximum transaction length value is superceded by the value set in the machine.config
file. By default, the value in the machine.config is 10 minutes.
4. If you require more time than 10 in the <system.transactions> value, you can modify the machine.config
file. But be aware that modifying the setting in the machine.config file changes the maximum timeout values
for all transaction processing on the server. To do this:
a. Log onto your server. Your User Id must have elevated administrator privileges.
b. Navigate to the C:\Windows\Microsoft.NET\Framework\v4.0.30319\Config or to the
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Config folder.
c. With a text editor, open the machine.config file.
Note The machine.config file only lists settings that differ from the pre-defined defaults. If a
setting is not listed, it means the default is being used. If you want to change a default, you will
need to add the key element and specify the value.
d. With a text editor, open the machine.config file.
e. Locate the <configuration> section.
f. In the <configSections> section, locate the system.transactions section group.
g. Add the allowExeDefinition="MachineToApplication" ending in the machineSettings section name
element. Your file may look similar to the following:
</sectionGroup>
<sectionGroup name="system.transactions"
type="System.Transactions.Configuration.TransactionsSectionGroup,
System.Transactions, Version=4.0.0.0, Culture=neutral,
PublicKeyToken=b77a5c561934e089, Custom=null">
<section name="defaultSettings"
68
Troubleshooting
type="System.Transactions.Configuration.DefaultSettingsSection,
System.Transactions, Version=4.0.0.0, Culture=neutral,
PublicKeyToken=b77a5c561934e089, Custom=null"/>
<section name="machineSettings"
type="System.Transactions.Configuration.MachineSettingsSection,
System.Transactions, Version=4.0.0.0, Culture=neutral,
PublicKeyToken=b77a5c561934e089, Custom=null" allowDefinition="MachineOnly"
allowExeDefinition="MachineToApplication"/>
</sectionGroup>
h. In the <configuration> section, add the <system.transactions> section if it does not exist.
i. In the <system.transactions> section, add the <machineSettings maxTimeout > element if it is not
already listed. The default maxTimeOut value is "00:10:00", which is 10 minutes. Change the default
max timeout to the appropriate value needed for your transaction load. For example, to change the 10
minutes to 3 hours, use maxTimeout = "03:00:00". Your file may look similar to the following:
<system.transactions>
<machineSettings maxTimeout="03:00:00"/>
</system.transactions>
j. Save and close the file.
k. Open the web.config file. Set the <system.transactions> value to match the timeout value that you
just set in the machine.config file. Save and close the web.config file.
12.5 MRP Processing and Job Scheduling Fail Due to WCF Operation Timeout
If you cannot run an MRP process or schedule a job, it means your WCF operation exceeds the maximum amount
of time allotted for processing. This error may happen if you attempt to process too much data at one time and
the processing time exceeds the default timeout setting. If you need to process large amounts of data, you may
consider increasing the time allowed by modifying the configuration setting that defines time out values for WCF
operations.
Important Modifying this setting changes the maximum timeout values for all WCF operations on the
server.
1. Use a text editor to open the *.sysconfig file. In a standard installation, the file is located in the
C:\Epicor\ERP10\ERP10.0.xxx\ClientDeployment\Client\Config directory. In the file, locate the
<appSettings> section.
2. in the <appSettings> section, locate the <Timeout for WCF operations> entry and change the value to
7200. Your file may look similar to the following:
<!-- Timeout for WCF operations -->
<OperationTimeOut value="7200" />
3. Save and close the file.
4. In the root of the Epicor application server virtual directory, locate the web.config file. Use a text editor to
open the file.
69
Troubleshooting
5. In the <customBinding> section, change the sendTimeout and receiveTimeout values to 12:00:00. Your
file may look similar to the following:
<customBinding>
<binding name="TcpCompressedUsernameSslChannel"
receiveTimeout="12:00:00" sendTimeout="12:00:00">
<CompressionEncoder>
<binaryMessageEncoding>
<readerQuotas maxDepth="50" maxArrayLength="2147483647"
maxBytesPerRead="2147483647" />
</binaryMessageEncoding>
</CompressionEncoder>
<security authenticationMode="UserNameOverTransport" />
<sslStreamSecurity />
<tcpTransport maxReceivedMessageSize="2147483647"
maxBufferSize="2147483647" transferMode="Buffered" />
</binding>
<binding name="TcpCompressedWindows" receiveTimeout="12:00:00"
sendTimeout="12:00:00">
<CompressionEncoder>
<binaryMessageEncoding>
<readerQuotas maxDepth="50" maxArrayLength="2147483647"
maxBytesPerRead="2147483647" />
</binaryMessageEncoding>
</CompressionEncoder>
<windowsStreamSecurity />
<tcpTransport maxReceivedMessageSize="2147483647"
maxBufferSize="2147483647" transferMode="Buffered" />
</binding>
<binding name="TcpCompressedUsernameWindowsChannel"
receiveTimeout="12:00:00" sendTimeout="12:00:00">
<CompressionEncoder>
<binaryMessageEncoding>
<readerQuotas maxDepth="50" maxArrayLength="2147483647"
maxBytesPerRead="2147483647" />
</binaryMessageEncoding>
</CompressionEncoder>
<security authenticationMode="UserNameOverTransport"/>
<windowsStreamSecurity/>
<tcpTransport maxReceivedMessageSize="2147483647"
maxBufferSize="2147483647" transferMode="Buffered" />
</binding>
</customBinding>
6. Save and close the file.
70
Troubleshooting
71
Supplemental Installations
1.
Log on to EPICweb and go to the customer portal website. Navigate to Products > Epicor ERP version 10
> Downloads > Epicor ERP > Version 10.0.
You can use this link: https://epicweb.epicor.com/products/epicor-erp/downloads.
2.
In the Available Downloads list, download the Epicor ERP 10 Supplemental Installation Guide. Note that this
guide is the same for all platforms.
3.
Use the Epicor ERP 10 Supplemental Installation Guide to install the components and products you intend
to use with your Epicor ERP 10 application.
72