It is highly recommended to print this CheckList before your EFP installation

The largest part of the software is installed on the server-side. You may install the server software in configuration with multiple servers. The most common configuration for use with ERP systems is to have the ERP-system on one database server and the Planner (EFP) system on another database server:

It is possible to split the Planner installation into two different servers; one database server and one application server with IIS (Internet Information Server). To do this you will later in the installation need this instruction but you may want to have a look at it right now Planner Multi-Server Installation

Important The following pre-requisites need to be met:

  1. Windows Server 2012 R2 or later
    1. .NET 3.5 needs to be installed.
    2. .NET 4.5 needs to be installed.
  2. Server Hardware
    1. 64-bit server only
    2. Minimum 8GB RAM for EFP Service and 32GB RAM for pcPortal Service. - (Application Server)
    3. Minimum 64GB RAM for SQL Server (including Analysis Services). - (Database Server, you can also put the application on the database server, that will be single server installation.)
    4. Disks used by SQL server recommended being SSD.
    5. Please note that if set up in a virtual environment this memory needs permanently allocated to the VM (not dynamically) to avoid significant performance degradation.
    6. The amount of free RAM available for the SQL server is the most important component to get good performance. How much that is needed depends on the size of the databases.
  3. Internet Information Server (IIS) 6 or higher
    1. IIS Windows login service needs to be started.
    2. ASP.NET v4.0.30319 needs to be set to allowed on the top level of default site under the “ISAPI and CGI Restrictions”.
    3. Windows authentication and Basic authentication are not enabled by default and must be enabled.
  4. Microsoft SQL Server 2016, SQL 2017 or SQL 2019 (for a basic EFP installation without pcPortal and Journal drilldown Microsoft SQL Server 2012 R2 is sufficient)
    1. When using SQL 2019 you will need to follow this procedure during installation Microsoft SQL Server 2019 - Scalar UDF workaround
    2. SQL Server needs to be installed with collation SQL_Latin1_General_CP1_CI_AS.
    3. SQL Server services should be setup with Windows domain accounts for multi-server use.
    4. If Planner is installed on another server than where the ERP source system (E10,E9, iScala or P21), the “ERP-server” must be set up as a linked server on the EFP server.
    5. SQL Server Agent needs to be started.
    6. SQL Server Analysis Services needs to be installed with Multidimensional/ OLAP install mode and started.
      1. Collation for AS: Latin 1_General, no sort order
    7. SQL configuration with Dynamic Ports is currently NOT supported unless port UDP 1434 access is enabled.
  5. Local Administrator User access to the server, that can be used as service account with a none changing password
  6. TCP/IP protocol should be enabled for SQL Server in SQL Server Network Configuration (SQL Server Configuration Manager)
    1. Named Pipes protocol should be enabled for SQL Server in SQL Server Network Configuration (SQL Server Configuration Manager, if you use named SQL Instance or multiserver installation)
  7. For version 1.4 or later, SQL Server Client Components
  8. For version 1.4 or later, 2 User IDs (with “Logon as a batch job” for group policy) with below privileges:
    1. User ONE:
      1. With Administrator rights on the server
      2. Administrator rights for SQL Server and SQL Server Analysis Services
    2. User TWO:
      1. With Administrator rights on the server
      2. Full Control right to the installation folder of “Performance Management Server” on the server
      3. Administrator rights for SQL Server (but No rights to SQL Server Analysis Services)

How to check and fulfill the Server Prerequisites

Please install .NET patches with the same credentials that you installed IIS and applied .NET the first time.
Otherwise, sometimes .NET is messing up the internal security for itself.
Worst case you have to reinstall the server to make it work again.
It's recommended to use https for EFP.
You can google “How to Install an SSL/TLS Certificate In IIS”, which gives you choice to use “https” as URL for login EFP.
Example 1
Example 2

If you want to be able to run the excel client on the server, this file wiaaut.dll must be installed. It is by default installed on all Windows client OS, but not by default on any windows server OS.
  1. Microsoft Excel 2013 or later
    1. 32 or 64 bit version.
      1. We recommend to always use 64-bit versions if you are working with larger reports due to Excel 32-bit memory restrictions
    2. Microsoft Excel must be license activated (trial license is too limited).
      • Office Shared Features / Visual Basic for Applications
      • Microsoft Excel / Add-ins / Power View
  2. Minimum physical memory available to Excel
    1. 4 GB RAM (32-bit) (small report sizes)
    2. 8-16 GB RAM (64-bit) (large report sizes)
  3. Windows 8 or later
  4. Basic requirements for Micrsoft office can be found here:

Instruction for how to copy and activate Wiaaut.dll file:

It is highly recommended to print this CheckList before your EFP installation

  • efp/tech/installguide/pre.txt
  • Last modified: 2021/11/29 20:08
  • by pcevli