4/6/22, 4:41 PM Knowledge Page - EpicCare

Home  Knowledge Base  Kinetic/ERP 

Checklist after Restoring a Kinetic/ERP Database from a Different Location

Search 

 Add to Favorites
Checklist after Restoring a Kinetic/ERP Database from a Different Actions
Location KB0050119

Create Case
 Authored by Serge Bosque •  1814 Views •  9d ago •     

Issue Related KB
Articles

Examples of issues/question answered by this article No Related Articles

- What steps must be performed after copying a Kinetic or ERP 10 Found
database to a different location (at the same release level)?
- Some functions (BPM, dashboard, printing, URL) are not working
correctly since copying the database. KB Top Rated
- What elements of my ERP system are not stored in the actual
Create a Quick
database?
Search
- How to prevent scheduled tasks to autorun?

- I'm expecting a new license but when I click the "Update License" I Cannot select anyone
get a message "No Updates are Available" from the Person
Picker

AR Write Off and
Adjustment
Error 
EPX Merchant
Account Update
Request
N/A

Request Vista,
Vantage or ERP9

Resolution installation media



WARNING

This solution is not suitable for upgrades, it is only KB Top Viewed

applicable when copying databases at the same release level.
Getting Started with
This article is aimed at the Kinetic / ERP 10 System
EpicCare - Customer
Administrator. Welcome Kit Videos

https://epicorcs.service-now.com/epiccare?id=epiccare_kb_article&sys_id=KB0050119 1/11
4/6/22, 4:41 PM Knowledge Page - EpicCare

 8054 Views

Creating and
SUMMARY Updating Cases on
the EpicCare Portal
When moving or copying a database from one location to another
 7627 Views
(e.g. Production to Test, Pilot to Production), you need to perform
a number of steps and checks, before using the restored Epicor Support
Epicor SoftwareofCorporation
Statement
environment.
TermsServices
of Use | Privacy Policy
The checklist below has been broken down into 5 sections:  6708 Views

A. Schedules & Agents Epicor Software

B. The Identification & Tailoring of Company records Maintenance and
Support Policies
C. Elements stored outside the database
 6172 Views
D. Cleanup and Performance Tuning
E. Country-Specific Functionalities (CSF)

A. SCHEDULES & AGENTS

A1. SCHEDULED TASKS

The Task Agent will run the Schedules and corresponding tasks set in
the System Agent.
In most cases, you will not want all your scheduled tasks to trigger in
the new location, so after the restore, it is safer to:

a. Stop the Task Agent of the target environment (ideally before

restoring the corresponding database, or at least before restarting the
application pool)

b. Disable the schedules/tasks you don't want to run, either

- Automatically: Before you start the application pool run the SQL
script documented in KB0051762 Disabling ERP10 System Agent
Schedules using a Script

- Manually: Starting the application pool, login, open the System

Agent and tick off the 'enabled' box of each schedule you wish to
disable.

A2. SYSTEM AGENT APPSERVER URL (Since 10.1)

a. Open System Agent Maintenance

b. If the Appserver URL is populated, then it means the environment

was using an NLB (Network Load Balancer). If your restored
environment doesn't use NLB then you want to clear that field. If it
does then ensure the value is correct. For more details review the Field
Help.
https://epicorcs.service-now.com/epiccare?id=epiccare_kb_article&sys_id=KB0050119 2/11
4/6/22, 4:41 PM Knowledge Page - EpicCare

A3. SYSTEM AGENT DATA DIRECTORIES

a. Open System Agent Maintenance

b. Ensure that the Server Data Directory and the Client Data
Directory are unique to the environment. This controls the temporary
data and log file locations. You want to ensure your logs are
independent to make it easier to analyze issues.

A4. TASK AGENT REGISTRATION

This is only required if the database you have restored was registered
against a different server name.

If it was, then follow KB0043625 The Task Agent Service has already
been registered with this server the maximum allowed number

Note: The process is also documented in the System Administration

Course > Workshop - Copy Live Data to Test Database > Clear
Source Values.

A5. FILE ROOT DIRECTORY

You need to clear the File Root Directory (FileRootDir) if one or more
of the following situations apply:
you have moved the database to a new server
the database is linked to a file share that no longer exists
you set up a new task agent

To clear the data from the Extended Service Registration

(Ice.ExtServiceRegistration) table:
Within the SQL Server Management Studio, click the
New Query button.
A new query displays in the center pane.
Enter the following query:

--Removes task agent registration

delete ice.ExtServiceRegistration
--Removes System agent file directory
if it refers to a server not on the
network
update ice.SysAgent set FileRootDir =
''
Now from the Database drop-down list, select your
destination db.
Click Execute.
https://epicorcs.service-now.com/epiccare?id=epiccare_kb_article&sys_id=KB0050119 3/11
4/6/22, 4:41 PM Knowledge Page - EpicCare

Impact:
The File Root Directory and the Extended Service
Registration table no longer contain source values from the
original database.
When users access the database and/or you create a new task
agent, the database populates with values that match the test
environment.

B. ENVIRONMENT & COMPANY

TAILORING

B1. PRODUCTION & LIVE FLAGS

Note: these flags were introduced in release 10.2.500.

a. Flag the Application Server in Production

Open the Epicor Administration Console
Expand Server Management > [server name]
Right-click the Application Server you updated
If necessary adjust the status using Set as Production or
Remove Production Status
(A blue icon indicates a running Production, and a green icon
indicates a running Non-Production)

b. Flag each Company as "Live"

Open Company Maintenance

For each company, check whether the Is Live flag needs
adjusting.

For more details on these features, you may review

KB0072567 Update License Says No Updates are Available

B2. COMPANY IDENTIFICATION

It is optional, but usually safer, to put some mark in place, warning

users they are dealing with a different database.

a. Context Indicators (since 10.2.700 - Kinetic UX)

They define a friendly name and the color that will display
on the Kinetic UX, along with the current application server,
user, company, and site.

https://epicorcs.service-now.com/epiccare?id=epiccare_kb_article&sys_id=KB0050119 4/11
4/6/22, 4:41 PM Knowledge Page - EpicCare

It is set in the EAC > Server Management > [deployment] >

Configure Installation Settings.
Here is an example:

b. Company Logo (since 10.2.100)

You can add the company logo within Company
Maintenance.

c. For earlier versions, you can change the company names (from the
EAC), and use a different colored theme or even personalise a theme
to add watermarks.

For more information on Indicators and Logo review the help or the
Implementation Guide.

For more information on Themes review the Customization Guide.

B3. COMPANY INTEGRATION

Company Maintenance contains several setups you may want to

adjust or remove.

a. On the General Settings tab:

Enterprise Search URL
Web Access URL
Web Access Metadata Output Path
Business Intelligence Performance Canvas URL
Social Enterprise URL (Note: No longer available since
10.2.600)
Service Connect: Server, User and Password details

b. On the Email and Reporting tab:

SMTP Server: alter if a test server is required

SSRS Report Server section: check to see if Override
Defaults is set to a specific location

c. On the Attachment tab:

(WARNING: since 10.2.600 this has been moved to a dedicated
Attachment Type Maintenance program)

File System Location: verify the path is correct for the non-
live system

https://epicorcs.service-now.com/epiccare?id=epiccare_kb_article&sys_id=KB0050119 5/11
4/6/22, 4:41 PM Knowledge Page - EpicCare

SharePoint Integration: verify the site is correct for the

non-live system
DocStar Integration: disable or use a non-live system

d. On the BAQ External Datasources tab:

Disable any data sources that should not be available from
the non-live system
NOTE: to change which database the data source is
connecting to, this should be adjusted in External Datasource
Maintenance.

B4. EDD Integration (Data Discovery)

a. To check and adjust the EDD URL use KB0098985 AHP Pointing
To Incorrect EDD URL

b. To restore custom EDD views/dashboards use the Export/Import

feature from the Overflow button (available since 10.2.400)

B5. EXTERNAL SYSTEMS

If you have any External System setup, you may want to review each
External Company record, to check you still wish them to be active.

C. ELEMENTS STORED OUTSIDE THE

DATABASE

Since ERP 10.1

Most elements, including compiled ones, are stored within

the database, or refreshed automatically. For more detail see
KB0047401 BPM and other Custom Solution Storage Location
Regarding Custom SSRS, Document Attachment and
Electronic Interface see the corresponding sections below, and if
you make any change then regenerate the data model.

In 10.0

Custom solutions elements needed regenerating after a copy:

Method Directives, Data Directives, Updatable Business
Activity Queries (UBAQ), Generic Imports, Electronic Data
Interface (EDI), Electronic Interface (EI), Posting Engine (PE)
Rules and Product Configurator (PC).
For BPM and Dashboards see the corresponding sections
below.

https://epicorcs.service-now.com/epiccare?id=epiccare_kb_article&sys_id=KB0050119 6/11
4/6/22, 4:41 PM Knowledge Page - EpicCare

C1. Custom SSRS Reports

While Custom Data Definitions & Report Styles are carried within the
database, the actual SSRS report files (.rdl) will not, because they are
stored inside the SSRS ReportServer database.

You will therefore need to export/import them either using the

Solution Workbench. When doing so ensure you don't overwrite

You can also perform individual download/upload from the Report

Style Maintenance program.

C2. Custom Attachment Files

These are stored in the File System specified by the document.

C3. Custom Electronic Interface (EI) files

These are found in the deployment folder (e.g.

C:\inetpub\wwwroot\ERP102300\Server\Erp\EI).

In 10.0 they had to be imported from Epicweb.

Since 10.1 they are part of the base software, however, custom EI still
needs to be imported after a DB copy.

C4. Data Model

The Data Model represents the database schema.

It is not compiled automatically, so it needs regenerating whenever
you add additional tables, such as Extended UD Tables/Fields.
So after a database copy, if you suspect that Extended UD tables may
differ between your source and target databases, then it is preferable to
do a regen.

File Names:
- Ice.DataModel.dll
- Epicor.DataModel.dll

File Location: Assemblies

e.g. E:\inetpub\wwwroot\ERP10LIVE\Server\Assemblies\

Refresh Process:
a. Open the EAC
b. Expand Database Server Management
c. Expand SQL Server

https://epicorcs.service-now.com/epiccare?id=epiccare_kb_article&sys_id=KB0050119 7/11
4/6/22, 4:41 PM Knowledge Page - EpicCare

d. Select the required database

e. On the Action pane Select "Regenerate Data Model."
f. Restart the Application Pool

C5. BPMs

Since 10.1

Compiled BPMs are stored in the database, you can

therefore ignore this section.
Note: BPM files are still generated in the BPM folder but
only for troubleshooting, they serve no functional purpose.
For more information, see KB0047401 BPM and other
Custom Solution Storage Location

What follows is only applicable to 10.0

Method Directives are held within your database, but the run-time
code produced during the saving is written within the application files.

After a DB is restored, you will need to regenerate those run-time

code files to ensure they reflect the source code from the database.
Make sure each environment (DEV, PILOT, LIVE) has its own
dedicated BPM folder; otherwise, they may conflict.
The setting is in Web.Config:
e.g. <customizationSettings disabled="false"
intermediateFolder="E:\ERP10\Server\BPMLIVE" loadPdb="false">

If you are operating multiple application servers in Load Balancing,

any code files generated during the restore procedure will replicate,
but only if you have employed DFS (or a similar replication package),
or are using a shared location for access to these files.
This topic covered in KB0029182 (Getting BPMs to Trigger
Consistently in a Load-Balanced Environment in ERP 10)

Recompiling all the directives:

a. From the Epicor main menu, navigate to System Management >
Business Process Management > Directive Update.
b. Click on Directive Recompile Setup
c. Tick "Both outdated and up-to-date directive" and Refresh
Signatures
d. Click "Start Recompile" (on the bottom right)
The process will run through all of your BPMs and inform you (on
completion).

If you have BPM linking to Service Connect workflows:

- A backup taken from another database will still point to the
workflows for that database.

https://epicorcs.service-now.com/epiccare?id=epiccare_kb_article&sys_id=KB0050119 8/11
4/6/22, 4:41 PM Knowledge Page - EpicCare

- Review each BPM and ensure the point to the correct workflow to
avoid cross-contamination of databases.
- Alternatively, the suspected BPMs could be disabled.

If you have BPM using C# code:

The code may references locations and paths specific to your source
database so it should be checked and modified to reflect those of your
destination database.
Alternatively, the suspected BPMs could be disabled.

C6. DASHBOARDS (10.0 only)

Assembly Dashboards (not Run-Time ones) need redeploying, in case
they've changed:
a. Open Dashboard Maintenance
b. Using the Search, select All Deployed Dashboards.
c. From the Actions menu, select "Deploy All UI Applications".

Note: This will redeploy all dashboard DLLs to enable them to work
in your new database, and report any failure.

D. CLEANUP AND PERFORMANCE

This is optional but you may want to review the following settings, in
particular if you restoring a production database into a non-production
environment.

D1. SQL RECOVERY MODEL & LOG SHRINKING

The database you've just restored will automatically take the recovery
model of the backed-up (source) database.
If the source database was in a production environment, then the
recovery model is likely to be "Full".
If the target database is not a production environment, then you
probably don't need it to be "Full", which implies
- logging every single transaction
- having a corresponding maintenance plan in place
Set the Recovery Model to 'Simple' for the non-production database
will provide the following benefits:
- no maintenance plan required
- no overhead for populating log files
- saving disk space
To using the Simple model and reclaim the disk space you can use
KB0040270 Shrinking the SQL Log & Troubleshooting

https://epicorcs.service-now.com/epiccare?id=epiccare_kb_article&sys_id=KB0050119 9/11
4/6/22, 4:41 PM Knowledge Page - EpicCare

D2. OLD TASKS

If you wish to purge all the old tasks and reports, including the ones
that may have been running when the backup was taken, then use the
following SQL commands to purge the related table:
/* Purge SysTask tables */

TRUNCATE TABLE [ice].[SysTaskParam]

TRUNCATE TABLE [ice].[SysTaskLog]

DELETE from [ice].[SysTask]

D3. APPLICATION POOL AUTOSTART

If you are restoring the database, you are likely to want some users to
use it straight away.
However, if the database is not in production, you may want to review
the Application Pool AutoStart setting to save resources for the
production environment(s).
This can be checked and adjusted in IIS Manager > Application Pools
> {Pool Name} > Basic Settings > Start application pool immediately.
Note: If the Application Pool is not running, then no resource will be
used by the database, even if it remains attached.

E. COUNTRY SPECIFIC
FUNCTIONALITIES (CSF)
CSF installations impact both the database and the deployed software.
Therefore, if you are restoring a database where a CSF was installed,
into an environment where it was not, then you need to install the CSF
where it was restored.

Notes

NOTE: This article is aimed at the ERP10 System Administrator.

Related Articles

KB0072567 Update License Says No Updates are Available

KB0051762 Disabling ERP10 System Agent Schedules
using a Script
KB0040270 Shrinking the SQL Log & Troubleshooting

https://epicorcs.service-now.com/epiccare?id=epiccare_kb_article&sys_id=KB0050119 10/11
4/6/22, 4:41 PM Knowledge Page - EpicCare

KB0041130 Checklist after Restoring an E9 Database from

a Different Location
KB0047401 BPM and other Custom Solution Storage
Location
KB0051049 Should I Restrict Memory Usage in SQL
Server?
KB0043625 The Task Agent Service has already been
registered with this server the maximum allowed number
KB0098985 AHP Pointing To Incorrect EDD URL
KB0029182 (Getting BPMs to Trigger Consistently in a
Load-Balanced Environment in ERP 10)

Related Training

Building a Solution with the Solutions Workbench

Installing a Solution with the Solution Workbench
Copying Production Database To Test Environment

Helpful? Yes No 75% found this helpful

Add your comment

This area is for suggestions related to the improvement of the above article. If you would
like someone from the support team to work with you, please enter a support case

Rate this article      Submit

https://epicorcs.service-now.com/epiccare?id=epiccare_kb_article&sys_id=KB0050119 11/11