EBS - Installation Guide EN


Entersoft applications®

In order to complete an Entersoft EBS/EXPERT installation we can follow specific steps, necessary for every installation.

In general

To proceed with a new installation, the Hardware and Software system requirements must be met.

We have drafted a relevant form with the minimum and recommended specifications. For large installations, we recommend making a special study / proposal.

The Windows user we will use to make the installations should have Administrator privileges.

Installation of EBS, for Server and clients, should not be done in a system folder such as Program Files but directly on the disk (eg E:\Entersoft\Entersoft Business Suite)

The reason for this is that otherwise you may experience issues with the write/modify rights for files in the installation folder.

Also, the full version of.NET Framework 4.6.2 or later must be installed on the server and clients.

Finally, it is recommended:

  1. Servers should be Entersoft dedicated either for common or distinct roles, so there is better control of resources.

  2. Using virtual machines for servers so it is easier to resize resources and migrate to another physical machine.

  3. The virtual Entersoft servers should have static and not dynamically allocated resources

SQL Server Installation

In general

The file system of the disk used for SQL databases is recommended to be formatted to 64k allocation unit size.


Due to high demands on IOPs, special write, the discs must be high-speed and in proper configuration (eg: SSD or SAS 15k on Raid-10)

Ideally, we would like to have the binaries on the system drive and on the independent ones:

  • data files (mdf)
  • log files (ldf)
  • tempdb
  • Backup files

We will need to install some version of SQL Server 2012 or later (the latest version is recommended) and always the latest updates.

SQL Server Installation

In the left side of the screen, select Installation and New SQL Server stand-alone installation ... unless you are upgrading or installing SQL failover cluster.


The Setup support rules are automatically executed, making the necessary checks to proceed with the installation.

This step searches for update files on the internet and continues the installation.

Depending on the version of SQL Server that we will install, we also have the appropriate capabilities. If you install the free express edition (always the version with Advanced Services), there are specific restrictions depending on the 2012, 2014, etc.

For example, 10 GB database size, 1 socket 4 CPU cores, 1gb RAM, no SQL Agent (maintenance plans etc).
In the ISV versions distributed by Entersoft, the key is automatically inserted during setup.


You will then be prompted to choose the features of our installation (SQL Server feature installation)


It is recommended to de-select R, reporting & analysis services, Polybase query service as well as reporting services for SharePoint & distributed replay controllers unless required by the customer's needs.

We recomment giving a name for the SQL Server instance (eg ENTERSOFT)


Next we configure the services that will be created and their startup type.


Services should run under specific SQL service accounts.

For companies that implement company policies, these accounts should either be declared as allowed to run as services, or we may change them with the account that will be given to us by IT (eg Local System or domain account).

From SQL 2016 and later versions there is the option "Grant perform maintenance task privilege" which we do not select.

In server configuration for collation we use Greek_CI (we don’t need to select Ascent)


During the installation, we will be asked to set Server users who will have access to the SQL Server instance as well as the authentication mode (windows only or mixed). It is recommended to have both authentication modes (mixed mode).

We also need to declare to the users, the account we chose in the previous step of the SQL server database engine service. In order to bring NT Authority / System into the options we must select Add ... and then enter system and click Check Names to select the option System. As soon as we select it, the NT Authority / System will appear in SQL Administrators as shown in the figure below.


We can also change the directories used by SQL Server depending on the server's storage configuration.

It is important that the database files are hosted in a properly configured directory and not in the default path (see Screenshot below).


For TempDB it is recommended to follow the logic one data file per CPU core, at least up to 8 cores and set autogrowth in megabytes


Depending on the features we have selected, the following steps appear and end we get to the final installation step.

Restore an Entersoft database and SQL Server and Databases configuration

In order to do the database installation and SQL Server configuration it is recommended to use SQL Server Management Studio (SSMS).

By opening SSMS we choose the SQL Server instance created to serve Entersoft.


We can log in either with Windows authentication or with SQL Server Authentication since we set up Mixed Mode during installation as mentioned earlier.

We see the following image and by right-clicking on the selected point, we can see the SQL Server properties.


We check the SQL Server settings


When we first install a new SQL Server instance, there is no limit to the size of memory that it is allowed to use. We should go to the memory as shown above in the Maximum Server Memory field and change the size (in megabytes).

The amount of memory we will make available to SQL Server is based on a number of factors.

  • The operating system requirements.
  • Whether this Database Server is also the Entersoft Application Server.
  • Any other roles that this server serves.

Our aim is to count all of these parameters before we set the maximum memory size after SQL Server is designed so that it does not release the memory it needed for a job.


We enable the option Boost SQL server priority if we are dealing with a dedicated database server.


TempDB can be configured either via UI or via script. Attention, every data file must have the same initial & autogrowth size.


USE [master]


ALTER DATABASE [tempdb] ADD FILE ( NAME = N'temp2', FILENAME = N'E:\DBData\temp2.ndf' , SIZE = 1376256KB , FILEGROWTH = 65536KB )


ALTER DATABASE [tempdb] ADD FILE ( NAME = N'temp3', FILENAME = N'E:\DBData\temp3.ndf' , SIZE = 1376256KB , FILEGROWTH = 65536KB )



When we have a new installation, we need a database, which is usually the latest ZeroDb unless some work has been done by Entersoft prior to installation and the project manager gives us a different customer database. The database we have available for the new installation should be installed using the “Restore” option. To restore the database, right-click the folder databases and select Restore database. The window below opens and we make our choices as shown in the picture.


In the Destination Database field, we provide a customer-related name (eg company name, EBS, or whatever the customer's manager indicates).

Also on the above screen selecting “select a page”-> files we set the filepath and name for the database files (mdf, ndf and ldf).

Once we have completed the database restore, we need to check its configuration settings, page verification, auto shrink, auto update, ...


  1. The Recovery Model has a simple value unless there is a reason to become full, such as transaction log backups, database mirroring, etc.
  2. The Compatibility level is recommended to be set at the last level..
  3. Options “Automatic” should have the true / false settings as they are shown in the picture except for Auto Update Statistics for which there are instances that we want it true, such as:
  1. Installation of SQL Server Express or any other case without scheduled update capabilities

  2. Installations that have to be available 24x7 (like e-shops)

In these cases, we select asynchronously auto update.


  1. Page Verify must have CHECKSUM value.

In the size and growth settings, we select an initial log file size of 2gb and at least 1/10 of the size of the Data file over that.

An increase in size of 10% is preferred in starting installations, while it is good to set in megabytes for larger databases (eg over 50gb)

Finally, we recommend that you set a maximum file size, depending on the available storage, so as to avoid unpleasant consequences of having no space left on the disk.


Another important step is the creation, in consultation with the IT of the company, of a Maintenance plan for our database. This is a process that is not available in case SQL Server Express is installed. In such cases, we can set Backup and update statistics through the application, and with an EMI we can even program rebuild indexes.

Recommended Backup Plan (Usually run daily in the evening at the times indicated by the company's IT):

  1. Check Database Integrity Task *
  2. Full Back up Database Task
  3. Maintenance Cleanup Task, depending on the retention policy that the customer will suggest
  4. Send email **

Recommended Optimization Plan (Usually run once a week on the day and time the company’s IT will suggest):

  1. Check Database Integrity Task *
  2. Rebuild Index Task
  3. Update Statistics Task
  4. History Cleanup Task
  5. Maintenance Cleanup Task (Maintenance Plan Text Reports .txt files)
  6. Send email **

Some additional elements to be taken into account are:

  • Possible need for daily optimization
  • Possible need for smart reindexing to minimize downtime
  • Ability to Online reindexing in Enterprise Edition
  • Database Compression capability in Enterprise Edition
  • Compress database backup capability in Enterprise Edition
  • There is also the ability to run custom integrity check with email on failure where exactly the point (table, index, ...) with the problem is mentioned.
    • Activation required for SQL Database Mail and creation of SQL Operators




With these actions, we have completed the process of installing SQL Server and our Database.


  • MDF
  • LDF
  • NDF
  • TRN
  • LOG
  • BAK
  • DAT
  • SQL
  • TRC

In addition, he should allow the sqlservr.exe in firewall as well as ports TCP 1433 & UDP 1434

C:\Users\smp\AppData\Local\Microsoft\Windows\Temporary Internet Files\Content.IE5\5ERD3D13\MCj04421290000[1].png Note that…

If the SQL Browser service is not running, we will have to declare the SQL TCP port through the configuration manager.


C:\Users\smp\AppData\Local\Microsoft\Windows\Temporary Internet Files\Content.IE5\5ERD3D13\MCj04421290000[1].png Note that…

If the Application server is on a different machine, we need to set both MSDTC in the Database and Application Server Firewall Exceptions for TCP 135, UDP 445 & msdtc.exe. Start-> run-> dcomcnfg


EBS installation on the Server

Once we have successfully completed the SQL Server installation and the Database section, we are ready to proceed with the installation of the Application Server

First, we need to have the latest version (depending on the installation of EBS, EXP, CRM, WMS) of the application and necessarily the Hotfixes that will be available for this release.

We create an Entersoft folder and a subfolder accordingly to the application example: E:\Entersoft\Entersoft Business Suite

Inside, we extract to zip file that we have with the release (be careful not to be blocked), and then copy the hotfixes.


We create desktop shortcuts for ESMainApp.exe named "Entersoft <application>" and for ESConfig.exe named "Entersoft configuration panel"

We run the 2nd and select a computer role (Application and Base Server).


DB administration

We create the connection to the database that we have installed on SQL Server.


Initially, by pressing the green + we can create a new connection to the database. We give a desired code and base description.

From Drop Down, we select the <SQL Server>\<instance name> that has our base (If it does not bring us the SQL Server as an option, we will write it manually).

We select the authentication method in SQL Server.

We select our database from the Drop Down menu of the Database.

We complete this process that creates the connection to the database by clicking on Check Connection and the message we need to get is the connection was successful.

Essentially this procedure creates the ESDBDef file in the application's CSCONFIG folder.

Server Settings


The port we choose is usually one of the 8090, 8091, 8092 etc. The ip we give is always and we also activate the WCF Duplex Channel port preferably by giving the next port.

In any case, for the ports we will use, the IT of the company we are installing has been informed and has excluded them from firewall (TCP).

To create the service, we need to run Run As Administrator a Command Prompt Window and execute the following command:

sc create [service name] binpath= [path] start= [?] DisplayName= [?]
sc description [service name] [Description]


sc create ESERPAPPSRV-EL02 binpath= "C:\Entersoft\Entersoft Business Suite\ESERPServer.exe" start= delayed-auto DisplayName= "Entersoft Business Suite Application Server (ESERPAPPSRV-EL02)"
sc description ESERPAPPSRV-EL02 "Entersoft Business Suite Application Server Service (ESERPAPPSRV-EL02)"

Obviously, the path must be changed and we should define the one in which we have installed the application. We must also, depending on whether the installation is EBS or EXP or CRM, give the corresponding name to the Service.

If we have made a mistake, we can delete the service by running the Command Prompt Window (Run As Administrator) again.

sc delete [service name] 

If we want to install a second service from the same directory, we need to give a different name for each service and for each additional one we will add the desired gate path (path spaceport).

As a WCF port in every next service, the next service is always used.


sc create ESWEBAPPSRV binpath= "C:\Entersoft\Entersoft Business Suite\ESERPServer.exe 8093" start= delayed-auto DisplayName= "Entersoft Business Suite Web Application Server (ESWEBAPPSRV)"
sc description ESWEBAPPSRV "Entersoft Business Suite Web Application Server (ESWEBAPPSRV)"

After we create the service, we start it through the configuration panel


Client settings

As shown in the following figure, we provide a desired ID and description for the server while in the server field we select the server name or IP and the communication port.

Check connection should be successful.


Additional setups from the root folder of the application

  1. Entersoft Document Printer (ESDocPrinterSetup) | 32 or 64bit depending operation system
  2. Entersoft Client Addon (ESClientAddOn)
  3. Entersoft Client Addon (ESClientAddOn x64)

The first two are necessary for creating and reading crystal reports while EDP for saving documents in pdf format.

Because the installation of the 1st client addon is likely to fail (failed to register dll), it is a good idea to have with us and pre-install vcredist_x86 also available in Entersoft FTP Server.

Finally, it is recommended that we execute the batch file ESFileAssociations from the root of the application so that the Entersoft file extensions can be registered with the corresponding executables of our application.

Scheduled Tasks

The tasks programmed through the application's application server can and should be configured in detail through windows scheduled tasks.

E.g.: run without login first, run with high privileges, change the account running the task and configure it for a windows version that supports extra settings



Installation of IIS Web Server

Installation manuals for mobile & e-Commerce web services are available, but the best practice is to install each web service as a separate site.

This allows us to have proper management with separate application pool, binding settings (name, port, certificate), directories, etc. for each site.




In addition, as in DB & Application server we have to inform the IT department to allow in firewall TCP 80 & 443 (default) for domain, private & public networks.

If the customer has windows firewall and is informed, we can adjust the settings by ourselves.


Clients Installation

Once we have successfully completed all previous procedures and the application is running successfully on the Server we are ready to proceed with the installation on clients.

First thing we should do is to get a copy of the application folder just as it is on the server and transfer it to each client.

After copying is completed on the clients, we will continue with the additional installations and in the application server, we will create a Desktop shortcut for ESMainApp.exe

PDF Version