Restore Demonstration Database

Use the following instructions to restore the Demonstration Database which is used for educational purposes along with the Epicor Education Module.

1. In the Epicor Administration Console, expand Server Management > [Epicor Server], highlight the name

of the Training Application Server and from the Actions pane, select Stop Application Pool.

2. In the SQL Management Studio, delete the existing Training Database.

3. In the Epicor Administration Console, expand Database Server Management > [Server] and do the

following:

a. Highlight the Training Database, right-click and select Remove Epicor Database.

b. Right-click the name of your SQL Server and select Add Demo DB. Enter the following details: • Name: The exact same name of the previous training database.

• Deployment Server: The installation location of your Epicor ERP 10 environment. For example, enter C:\Epicor\ERP10\ERP10.1.500.x.

Click OK.

4. Click Start. When complete, start the Training Application Server that was stopped in step 1. 5. Import the license file and assign it to your company. To do this:

a. Expand your Server Management > [Server] > [application server]. Right-click the Licensing node and select Import License File.

b. Browse to the location where you previously downloaded the license code file. Select the file and click

c. In the middle pane, double-click on the licensing code file to open it. In the Properties dialog, click the

Modules tab. Select the check box for each module you want enabled. Click OK.

d. Click the Companies node. In the middle pane, double-click your company to open the Properties dialog. Click the Installation browse (...) to search for a list of installation license identifiers. Select the appropriate identifier. Click Select. Click OK to save.

18.3 Increase Number of Threads Available to SQL Server

If you get user traffic related errors, you need to increase the number of threads available to SQL Server for your system to handle larger user traffic. To do this, update the processModel default settings in the machine.config file.

1. Log onto your server. Your user account must have administrator privileges for modifying Microsoft SQL

Server values.

2. Navigate to either the C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Config or C:\Windows\Microsoft.NET\Framework\v4.0.30319\Config directory.

3. Using a text editor, open the machine.config file.

4. Locate the <system.web> section. You should see the <processModel autoConfig="true"/> setting. 5. Update this setting to display the following values:

<processModel autoConfig="false" minIoThreads="600" minWorkerThreads="300" maxIoThreads="1000" maxWorkerThreads="1000" />

6. Save the machine.config file.

7. For this change to activate, reboot the server machine.

8. Repeat these steps so all application servers (AppServers) on your system use this <processModel> setting.

18.4 Change Free Memory Requirement

If your Task Agent Event Viewer log includes the error "Memory gates checking failed because the free memory (xxxxxxxx bytes) is less than 5% of total memory" it indicates that the server is under-resourced for the amount of load on it, which means demand for resources exceeds the available supply.

To prevent this error, you either need to reduce demand (stop any application pool for an Epicor appserver that is not in use and any other process that is not needed) or to increase supply (add more RAM to the server). You can also use the following steps to bypass the free memory requirement check for the system to be able to start services when less than 5% free memory is available.

1. Locate your web.config file. To do this:

a. Start IIS Manager.

b. Navigate to your Epicor application server virtual directory. For example, ERP101500. c. Right-click on the folder and select Explore to open Windows Explorer.

d. Locate the web.config file in the root of the folder that opens. For example, go to C:\inetpub\wwwroot\ERP101500\Server.

2. Create a backup of the web.config file.

3. Use a text editor to open the original web.config file. Search for the <system.ServiceModel> node. 4. Place a cursor at the end of that line and press Enter to add a new line.

5. Paste the following on the new line:

<serviceHostingEnvironment minFreeMemoryPercentageToActivateService="0" />

6. Save the file. Close the text editor.

7. Repeat the steps above for each of your application servers.

8. After this process is complete, it is recommended that you recycle all of your application pools then restart

the Task Agent service.

18.5 Manage LOB Data Replication

The "Length of LOB data (xxxxxx) to be replicated exceeds configured maximum 65536" error may occur when you have the Replication module enabled in SQL Server that hosts your database. You have several options to avoid this error:

1. Exclude a table or column that causes the LOB data error from the Publishing Replication:

a. Log in to your SQL Management Studio.

b. Run the following query to locate the tables and columns that may cause LOB issues: use <YourDatabaseName>

DECLARE @textthreshold int set @textthreshold = 65536 SELECT SCHEMA_NAME(T.schema_id) as Schema_Name, T.Name as Table_Name, C.name as Column_Name, C.max_length as Max_Length, T2.name as Data_Type, MSP.publication as Replication_Publication_Name FROM sys.tables as T

INNER JOIN sys.columns as C ON T.object_id = C.object_id INNER JOIN sys.types as T2

ON C.user_type_id = T2.user_type_id

INNER JOIN Distribution.DBO.MSarticles AS MSA ON MSA.source_object = t.name

AND MSA.source_owner = SCHEMA_NAME(T.schema_id) AND MSA.publisher_db = db_name()

INNER JOIN Distribution.DBO.MSpublications AS MSP ON MSA.publication_id = MSP.publication_id WHERE

AND (C.max_length = -1 OR C.max_length > @textthreshold) ORDER BY 1,2,3

c. Navigate to Replication > Local Publications.

d. Right-click the publication on which the error occurred or may occur and select Properties. e. In the Select a page pane, click Articles.

f. In the Objects to publish window, clear the check boxes of the tables or table columns returned in the query results.

g. Click OK.

2. Change the Max Text Replication Size value:

a. Open your SQL Server Management Studio.

b. Right-click the server with your database and select Properties. c. In the Select a page pane, click Advanced.

d. Under the Miscellaneous title, change the Max Text Replication Size value. You can either change this value to meet the length of LOB data from the error message or use the -1 value.

Note If you use -1, the Max Text Replication size has no limit. This may reduce your system

performance.

this site, you need a Site ID and an EPICweb account. To create an account, go to http://support.epicor.com.