Copyright...5. Acumatica ERP and Acumatica Framework Installation Guide...6. System Requirements for Acumatica ERP 2017 R2... 7

Transcription

1

2 Contents 2 Contents Copyright...5 Acumatica ERP and Acumatica Framework Installation Guide...6 System Requirements for Acumatica ERP 2017 R... 7 System Requirements for Acumatica Framework 2017 R Typical Hardware and Virtual Machine Configurations for PCS and PCP Licenses Preparing for Installing Acumatica ERP Configuring Web Server (IIS) Features Setting Up an HTTPS Service in Web Server (IIS) Enabling Semantic Search for Microsoft SQL Server Installing Acumatica ERP Installing Acumatica ERP Locally To Install the Acumatica ERP Tools...22 To Deploy an Acumatica ERP Instance To Change the Password at the First Sign-In Setting Up Acumatica Self-Service Portal To Deploy a Self-Service Portal Instance...27 To Specify the Company Available for Self-Service Portal Users Installing Acumatica ERP in a Data Center Deploying the Acumatica ERP Service on Windows Azure Installing Acumatica ERP on Amazon Web Services Installing Acumatica Framework...41 To Install Acumatica Framework Tools To Deploy an Acumatica Framework Instance To Change the Password at the First Sign-In To Install Acumatica Framework Templates Licensing and Activating Acumatica ERP...46 To Activate the License for an Acumatica ERP Instance Maintaining Acumatica ERP...48 To Check the State of Application Instances and Databases...48 To Turn On Snapshot Isolation Mode for a Database...49 To View the Details of an Acumatica ERP Instance To Change the Database of an Instance To Perform Database Maintenance...51 To Configure the Session Time-Out... 53

3 Contents 3 To Configure the Report Time-Out...54 To Configure the Query Time-Out To Select Roles That Will Have Administrative Privileges...55 To Shorten the Names of the Customization Folders To Turn On Reminders To Turn On the My Tasks and Events Button To Enable Push Notifications Maintaining Acumatica Framework Managing Companies Multi-Company Instances To Add a New Company To Delete an Existing Company Updating Acumatica ERP Updating Acumatica ERP by Using the Web Interface...65 Updating Acumatica ERP by Using the Configuration Wizard Updating Your Acumatica ERP Service on Windows Azure To Schedule the System Lockout To Update Acumatica ERP by Using the Web Interface To Update the Acumatica ERP Tools To Update the Database and Site of an Acumatica ERP Instance To Update the Database of an Acumatica ERP Instance...70 To Update the Site of an Acumatica ERP Instance To Download the Acumatica ERP Service Configuration File...71 To Update Your Acumatica ERP Service on Windows Azure To Update a Client Application that Uses Screen-Based Web Services...74 To Unlock an Acumatica ERP Instance Troubleshooting Acumatica ERP...76 Troubleshooting Performance Step 1: Check the Most Basic Causes Step 2: Investigate Application Server Time and Database Server Time in the Request Profiler...81 Step 3: Check the Configuration of the Application Server Step 4.1: Check the Configuration of Microsoft SQL Server and Run Reports Step 4.2: Check the Configuration of MySQL Database Server Step 5: Collect More Information Step 6: Submit a Case to Acumatica Support...91 Using Logs Using Profilers...95 Using Built-In Debugging Tools Using Third-Party Tools To Optimize Memory Consumption During Startup...97 Uninstalling Acumatica ERP... 99

4 Contents 4 To Delete an Acumatica ERP Application Instance...99 Using the Command-Line Tool The Command-Line Tool Possible Parameters and Values To Create a Configuration File Examples of the Configuration String...109

5 Copyright 5 Copyright 2018 Acumatica, Inc. ALL RIGHTS RESERVED. No part of this document may be reproduced, copied, or transmitted without the express prior consent of Acumatica, Inc SE 6th, Suite 140 Bellevue, WA Restricted Rights The product is provided with restricted rights. Use, duplication, or disclosure by the United States Government is subject to restrictions as set forth in the applicable License and Services Agreement and in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS or subparagraphs (c)(1) and (c)(2) of the Commercial Computer Software-Restricted Rights at 48 CFR , as applicable. Disclaimer Acumatica, Inc. makes no representations or warranties with respect to the contents or use of this document, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Acumatica, Inc. reserves the right to revise this document and make changes in its content at any time, without obligation to notify any person or entity of such revisions or changes. Trademarks Acumatica is a registered trademark of Acumatica, Inc. HubSpot is a registered trademark of HubSpot, Inc. Microsoft Exchange and Microsoft Exchange Server are registered trademarks of Microsoft Corporation. All other product names and services herein are trademarks or service marks of their respective companies. Software Version: 2017 R2 Last updated: June 29, 2018

6 Acumatica ERP and Acumatica Framework Installation Guide 6 Acumatica ERP and Acumatica Framework Installation Guide This guide provides system requirements and detailed instructions for installing, maintaining, updating, and deleting Acumatica ERP and Acumatica Framework. This guide covers the following topics: System Requirements for Acumatica ERP 2017 R2 System Requirements for Acumatica Framework 2017 R2 Preparing for Installing Acumatica ERP Installing Acumatica ERP Installing Acumatica Framework Licensing and Activating Acumatica ERP Maintaining Acumatica ERP Maintaining Acumatica Framework Uninstalling Acumatica ERP Using the Command-Line Tool

7 System Requirements for Acumatica ERP 2017 R2 7 System Requirements for Acumatica ERP 2017 R2 Acumatica ERP contains the following parts: web interface, the server part and the database. For proper work of each of these parts the environment where you install and use Acumatica ERP, should meet particular requirements that are described in this topic. : Before you start the installation process, install at least all critical updates (or, preferably, all available updates) for the operating system and the required software. You should also make sure that all required third-party components listed in this topic are properly installed and configured on your computer. Workstations Workstations that are used by employees of your organization to work with Acumatica ERP should meet hardware and software requirements listed in the table below. Hardware/Software Requirements Display resolution Minimum , Typical 1920x1080 Adobe Reader (to open Acumatica ERP PDF documents) XI and higher Microsoft Office (to view documents exported from Acumatica ERP) with the Microsoft Office 2007 compatibility pack Web Browsers Microsoft Internet Explorer 9, 10, and 11 with Compatibility View turned off. Microsoft Edge 38 and higher Mozilla Firefox 47 and higher Apple Safari 9 and higher Google Chrome 52 and higher : For Microsoft Internet Explorer 10 the hotfix for the ASP.NET browser definition files in the Microsoft.NET Framework 4.0 should be installed. For more information, see Server Part The environment where you install the server part of the Acumatica ERP should meet hardware and software requirements listed in the table below. Hardware/Software Operating systems Requirements Windows Server bit edition Windows Server bit edition

8 System Requirements for Acumatica ERP 2017 R2 8 Hardware/Software Requirements Windows Server 2012 R2 64-bit edition Windows Server bit edition Windows Server 2008 R2 64-bit edition : You can install the server part of Acumatica ERP on non-server operating systems, such as Windows Vista 64-bit edition, Windows bit edition, Windows bit edition, Windows bit edition, and Windows bit edition, but only for testing purposes. For production you must use a server operating system. Microsoft.NET Framework 4.7 Microsoft Internet Information Services 7.0, 7.5, 8.0, 8.5, or 10 depending on the underlying operating system. : You must set the Enable 32-bit Applications option to False in IIS settings. : Acumatica ERP 2017 R2 supports only the Integrated mode of the application pool. The Classic mode is not supported. If you try to upgrade an earlier version of Acumatica ERP with Classic mode of the application pool to 2017 R2, upgrade will not be performed, and a corresponding error message will be displayed. Memory 4 GB RAM Hard Disk Space 1 GB available hard disk space plus 200 MB for each additional instance of Acumatica ERP Database You can find system requirements for the Acumatica ERP database in the following table. Hardware/Software Microsoft SQL Server Requirements bit edition bit edition MySQL Community Edition Server bit edition Memory 4 GB RAM Hard Disk Space For each database, 1 GB available hard disk space. Depending on the number of transactions, additional hard disk space may be required to store large numbers of transactions. Code Authoring Environments To create stand-alone applications with Acumatica ERP or develop customizations and add-on solutions on top of Acumatica ERP, you need one of the integrated development environments (IDEs) listed in the table below.

9 System Requirements for Acumatica ERP 2017 R2 9 IDE Microsoft Visual Studio with Microsoft Web Developer Tools Requirements 2015: Community, Professional, and Enterprise editions

10 System Requirements for Acumatica Framework 2017 R2 10 System Requirements for Acumatica Framework 2017 R2 Acumatica Framework is a Web 0 application development platform you use to develop business applications, such as enterprise resource planning (ERP) systems. Acumatica Framework includes server software and a database. For proper work of each of these parts the environment where you install and use Acumatica Framework, should meet particular requirements that are described in this topic. : Before you start the installation process, install at least all critical updates (or, preferably, all available updates) for the operating system and the required software. You should also make sure that all required third-party components listed in this topic are properly installed and configured on your computer. Server Part The environment where you install the server part of Acumatica Framework should meet hardware and software requirements listed in the table below. Hardware/Software Operating systems Requirements Windows Server bit edition Windows Server bit edition Windows Server 2012 R2 64-bit edition Windows Server bit edition Windows Server 2008 R2 64-bit edition : You can install the server part of Acumatica ERP on non-server operating systems, such as Windows Vista 64-bit edition, Windows bit edition, Windows bit edition, Windows bit edition, and Windows bit edition, but only for testing purposes. For production you must use a server operating system. Microsoft.NET Framework 4.7 Microsoft Internet Information Services 7.0, 7.5, 8.0, 8.5, or 10 depending on the underlying operating system. : You must set the Enable 32-bit Applications option to False in IIS settings. : Acumatica ERP 2017 R2 supports only the Integrated mode of the application pool. The Classic mode is not supported. If you try to upgrade an earlier version of Acumatica ERP with Classic mode of the application pool to 2017 R2, upgrade will not be performed, and a corresponding error message will be displayed. Memory 4 GB RAM Hard Disk Space 1 GB available hard disk space plus 200 MB for each additional instance of Acumatica ERP Database You can find system requirements for the Acumatica ERP database in the following table.

11 System Requirements for Acumatica Framework 2017 R2 11 Hardware/Software Microsoft SQL Server Requirements bit edition bit edition MySQL Community Edition Server bit edition Memory 4 GB RAM Hard Disk Space For each database, 1 GB available hard disk space. Depending on the number of transactions, additional hard disk space may be required to store large numbers of transactions. Code Authoring Environments To create stand-alone applications with Acumatica Framework, you need one of the integrated development environments (IDEs) listed in the table below. IDE Microsoft Visual Studio with Microsoft Web Developer Tools Requirements 2015: Community, Professional, and Enterprise editions

12 Typical Hardware and Virtual Machine Configurations for PCS and PCP Licenses 12 Typical Hardware and Virtual Machine Configurations for PCS and PCP Licenses This topic contains typical configurations for Private Cloud Subscription (PCS) and Private Cloud Perpetual (PCP) licenses that depend on the volume of documents that business will process by using Acumatica ERP. You may use this topic as follows: Find an appropriate volume of documents the business is going to process with Acumatica ERP in Estimation of Resource Level License and Hardware Needed. Read about licensing limitations that correspond to the hardware configuration in License Parameters for Resource Levels. Find the typical hardware configuration that corresponds to the License Resource Level in Server Configurations. 4. Read about the software requirements for the server part of the system in Software Requirements for the Server Part and system requirements for workstations in System Requirements for Workstations. Estimation of Resource Level License and Hardware Needed Before determining the type of server configuration you should use you first need to make sure that you have selected the appropriate Acumatica ERP License Resource Level which is directly related to the type of server environment you will use. Instead of charging for every user that needs to use the system, Acumatica ERP uses a Resource Level size licensing system that is based on overall the Usage and Load levels you will have on the system. The more transaction volume (usage) and users you expect (load), the larger the resource level license you will require. When determining your expected usage level, identify the maximum number of commercial transactions you expect to process during your busiest month over the life of your contract. If your business needs to process most of your transactions over a few days, then you also need to determine how many commercial transactions you process during your peak hour. For guidance, a commercial transaction is completing a sale from start to finish through the system including all associated operational transactions. For example, on Acumatica ERP a Small Resource Level license with appropriate hardware you can process up to 3,000 transactions per month. That means in your busiest month you can create 3,000 sales orders, ship them, invoice them, accept payments, and procure and receive inventory required. If your business has spikes in production, then you also need to verify that you do not process over 100 commercial transactions per hour to maintain adequate throughput on a small resource level. The following table will help you to find an appropriate hardware resource level that depends on the usage (number of transactions during peak time) and load (approximate number of users who initiate the transactions). License Resource Level Guidance Resource Level Maximum Number of Transactions per Hour Maximum Commercial Transactions per Month Concurrent Users or Number of Medium/ Heavy* Users Total Number of Users Small 100 3, Medium 200 7,

13 Typical Hardware and Virtual Machine Configurations for PCS and PCP Licenses 13 Resource Level Maximum Number of Transactions per Hour Maximum Commercial Transactions per Month Concurrent Users or Number of Medium/ Heavy* Users Total Number of Users Large , X-Large , , ,500 2X-Large *Medium Users are users that rely on the system every day and tend to use the system generally once every 10 minutes. Heavy Users tend to use the system 20+ times during their daily peak hours. : The number of users can be less than shown in the table above if automated processing is set up on the customer s side (that is, transactions are initiated not by a user but by API methods). If import or export of data by using integration with external systems will be used (such as OData export, import and export by using Web API, scheduled import and export), we recommend that you select the resource level higher than the level that was defined by the number of transactions. (For example, if you have 200 transactions per hour and use integration with external systems, you should select the Large resource level.) License Parameters for Resource Levels Currently, Acumatica ERP PCS and PCP license validation system places limits to the number of logical CPU cores the Acumatica ERP application will use on the server. You can find license limitations by CPU cores in the table below. The limitation of CPU core number in the license should be equal to or more than the typical number of CPU cores in hardware requirements (see Server Configurations). Your operating system will still utilize the additional cores for OS related tasks. License Limitations for Logical CPU Cores License Parameter/ Resource Level Number of logical CPU cores Small Medium Large X-Large 2X-Large : Currently the actual throughput you can achieve can highly vary based on system hardware, usage patterns, and many other factors. Acumatica ERP does expect to introduce a more precise and adaptive in-product Resource Level Manager which will monitor and maintain optimized performance for all users of the system. The resource level manager will balance resource usage across all resource requests and eliminates excessive resource monopolization by individual sessions. Therefore please use the License Resource Level Guidance table shown earlier to determine resource level license you select. Once the new Resource Level Manager is in place, improved hardware will only help response times so long as you are below the transaction volume and user load guidance levels. Once you pass the guidance level, user may begin to see significant performance degradation. Server Configurations This section describes typical hardware specifications for servers used to host Acumatica ERP (which includes the application server and the database) for each type of resource levels defined in Estimation of Resource Level License and Hardware Needed. You should install the application server and the database on separate virtual machines or physical servers. In the following subsections, you can find typical specifications for each of these configurations.

14 Typical Hardware and Virtual Machine Configurations for PCS and PCP Licenses 14 Virtualization on VMWare or Hyper-V: Typical Specifications Based on Resource Levels In this table, you can find typical specifications for the physical server where virtual machines (VM) for Acumatica ERP server part will be installed, and resources that should be allotted for these virtual machines. Resource Level License/ Typical Configuration Small Basic Medium Large Advanced Basic Advanced Basic Advanced Physical Server Specification Number of physical CPUs Total number of physical CPU cores Xeon E Xeon E Xeon E Xeon E Xeon E Xeon E OFF OFF OFF OFF OFF OFF 32GB 64GB 64GB 128GB 128GB 256GB Hard drive size* 250GB 500GB 500GB 500GB 750GB 1TB Hard drive type SSD Sata3 SSD Sata3 SSD Sata3 90K+ IOPS 90K+ IOPS 90K+ IOPS SSD PCIE3x4 SSD PCIE3x4 SSD PCIE3x4 500MBps + R/W 500MBps + R/W 500MBps + R/W 300K + IOPS 300K + IOPS 300K + IOPS 2000MBps + R/W 2000MBps + R/W 2000MBps + R/W GB 24GB 24GB 32GB 32GB 96GB GB 32GB 32GB 64GB 64GB 128GB Typical processor Hypervisor RAM RAID Application Server VM VM Allotted CPU Cores VM RAM Database Server VM VM Allotted CPU Cores VM RAM * You need two hard drives: one for the Application Server VM and one for the Database Server VM. : Contact your partner for hardware guidance on XL and higher resource level licenses. When you install Acumatica ERP on virtual machines, you should consider the following: You should install the application server and the database on separate virtual machines. You should allocate these virtual machines for Acumatica ERP only (no other software should be installed there, including antivirus software). Virtual machines decrease hardware performance by approximately 15%. For maximum performance, you could eliminate VMs and run directly on the node OS, however, you will lose benefits and flexibility of VMs. Most clients choose VMs for this reason.

15 Typical Hardware and Virtual Machine Configurations for PCS and PCP Licenses 15 Make sure that Hypervisor is off in your BIOS as Acumatica ERP will only use the licensed number of logical cores reported by the system and you want each logical core to be mapped 1:1 to your physical cores. Turning on Hypervisor can reduce your Acumatica ERP performance by factor of 50% and each CPU core reported by your OS will use a fraction of your physical cores on the server. You should not use dynamic memory for virtual machines. You need to allocate a required RAM capacity for each virtual machine. Each virtual machine should use a separate physical hard drive. That is, you should not share one physical hard drive between multiple virtual machines. If you use hard drives with low writing speed, then increasing RAM will not improve the database performance. We recommend that you use hard drives with high writing speed for the database server. : You should not use the RAID 5 level for hard drives because of low writing speed. Separate Physical Servers: Typical Specifications Based on Resource Levels In this table, you can find typical specifications for the Acumatica ERP Application Server and the Database Server. Resource Level License/ Typical Configuration Small Medium Large Basic Advanced Basic Advanced Basic Advanced Number of physical CPUs Total number of physical CPU cores Xeon E Xeon E Xeon E Xeon E Xeon E Xeon E OFF OFF OFF OFF OFF OFF 32GB 64GB 64GB 128GB 128GB 256GB Hard drive size 250GB 500GB 500GB 500GB 500GB 500GB Hard drive type SSD Sata3 SSD Sata3 SSD Sata3 SSD Sata3 SSD Sata3 SSD Sata3 Application Server Typical processor Hypervisor RAM 90K+ IOPS 90K+ IOPS 90K+ IOPS 90K+ IOPS 90K+ IOPS 90K+ IOPS 500MBps + R/W 500MBps + R/W 500MBps + R/W 500MBps + R/W 500MBps + R/W 500MBps + R/W Number of physical CPUs Total number of physical CPU cores Xeon E Xeon E Xeon E Xeon E Xeon E Xeon E RAID Database Server Typical processor

16 Typical Hardware and Virtual Machine Configurations for PCS and PCP Licenses 16 Resource Level License/ Typical Configuration Small Medium Large Basic Advanced Basic Advanced Basic Advanced ON ON ON ON ON ON 32GB 64GB 64GB 128GB 128GB 256GB Hard drive size 250GB 500GB 500GB 500GB 750GB 1TB Hard drive type SSD Sata3 SSD Sata3 SSD Sata3 SSD PCIE3x4 SSD PCIE3x4 SSD PCIE3x4 300K + IOPS 300K + IOPS 300K + IOPS 2000MBps + R/W 2000MBps + R/W 2000MBps + R/W Hypervisor RAM 90K+ IOPS 90K+ IOPS 90K+ IOPS RAID 500MBps + R/W 500MBps + R/W 500MBps + R/W : Contact your partner for hardware guidance on XL and higher resource level licenses. When you install Acumatica ERP on separate physical servers, you should consider the following: You should install the application server and the database on separate servers. You should allocate these servers for Acumatica ERP only (no other software should be installed there, including antivirus software). Network latency between an application server and a database should be less than 1 millisecond (both servers should be in the same data center). If you use hard drives with low writing speed, then increasing RAM will not improve the database performance. We recommend that you use hard drives with high writing speed for the database server. : You should not use the RAID 5 level for hard drives because of low writing speed. Amazon Web Services: Recommended Instances Based on Resource Levels In this table, you can find recommended parameters of standard instances provided by Amazon Web Services (AWS) where Acumatica ERP will be hosted. Resource Level License/ Typical Configuration Small Medium Large Basic Advanced Basic Advanced Basic Advanced m4.large r4.large m4.xlarge r4.xlarge m4.2xlarge r4.4xlarge vcpu* RAM (GB)* gp2 gp2 gp2 gp2 gp2 gp2 250GB 500GB 500GB 500GB 750GB 1TB Moderate Up to 10 Gigabit High Up to 10 Gigabit High Up to 10 Gigabit Application Server VM AWS instance type Hard drive type** Hard drive size Network performance

17 Typical Hardware and Virtual Machine Configurations for PCS and PCP Licenses 17 Resource Level License/ Typical Configuration Small Medium Large Basic Advanced Basic Advanced Basic Advanced m4.large r4.xlarge r4.xlarge r4.2xlarge r4.2xlarge r4.4xlarge vcpu* RAM (GB)* io IOPS io IOPS io IOPS io IOPS io IOPS io IOPS 250GB 500GB 500GB 500GB 750GB 1TB Database Server VM AWS instance type Hard drive type** Hard drive size * Number of CPUs and RAM size are defined by the instance type; these parameters are provided in the table for reference. **The IOPS parameter for a hard drive of the gp2 type is calculated automatically by AWS according to hard drive size. When you deploy Acumatica ERP in AWS, you should consider the following: All AWS instances should be EBS-optimized. If you want to increase speed of storage, you need to select the higher network performance between the Database Server VM and the Application Server VM. Microsoft Azure: Recommended Instances Based on Resource Levels In this table, you can find recommended parameters of standard instances provided by Microsoft Azure (Azure) where Acumatica ERP will be hosted. Resource Level License/ Typical Configuration Small Medium Large Basic Advanced Basic Advanced Basic Advanced DS11_v2 Standard DS12_v2 Standard DS12_v2 Standard DS12_v2 Standard DS13_v2 Standard DS14_v2 Standard GB 500GB 500GB 500GB 750GB 1TB F4 Standard DS12_v2 Standard DS12_v2 Standard DS13_v2 Standard DS13_v2 Standard DS14_v2 Standard vcpu* RAM (GB)* Hard drive type 3000 IOPS 4000 IOPS 5000 IOPS 8000 IOPS 8000 IOPS IOPS Hard drive size 250GB 500GB 500GB 500GB 750GB 1TB Application Server VM Azure instance type vcpu* RAM (GB)* Hard drive size Database Server VM Azure instance type

18 Typical Hardware and Virtual Machine Configurations for PCS and PCP Licenses 18 * Number of CPUs and RAM size are defined by the instance type; these parameters are provided in the table for reference. Software Requirements for the Server Part The environment where you install the server part (the Application Server and the Database Server) of the Acumatica ERP should meet software requirements listed in the table below. Application Server Software Operating systems Requirements Windows Server bit edition Windows Server bit edition Windows Server 2012 R2 64-bit edition Windows Server bit edition Windows Server 2008 R2 64-bit edition Note: You can install the server part of Acumatica ERP on non-server operating systems, such as Windows Vista 64-bit edition, Windows bit edition, Windows bit edition, Windows bit edition, and Windows 1064-bit edition, but only for testing purposes. For production you must use a server operating system. Microsoft.NET Framework 4.6, Microsoft Internet Information Services 7.0, 7.5, 8.0, 8.5, or 10 depending on the underlying operating system. : You must set the Enable 32-bit Applications option to False in IIS settings. : Acumatica ERP 2017 R2 supports only the Integrated mode of the application pool. The Classic mode is not supported. If you try to upgrade an earlier version of Acumatica ERP with the Classic mode of the application pool to 2017 R2, upgrade will not be performed, and a corresponding error message will be displayed. Database Server Software Microsoft SQL Server MySQL Community Edition Server Requirements bit edition bit edition bit edition System Requirements for Workstations Workstations that are used by employees of your organization to work with Acumatica ERP should meet hardware and software requirements listed in the table below.

19 Typical Hardware and Virtual Machine Configurations for PCS and PCP Licenses 19 Hardware/ Software Requirements Display resolution Minimum , Typical 1920x1080 Adobe Reader (to open Acumatica ERP PDF documents) XI and higher Microsoft Office (to view documents exported from Acumatica ERP) with the Microsoft Office 2007 compatibility pack Web Browsers Microsoft Internet Explorer 9, 10, and 11 with Compatibility View turned off. Microsoft Edge 38 and higher Mozilla Firefox 47 and higher Apple Safari 9 and higher Google Chrome 52 and higher : For Microsoft Internet Explorer 10 the hotfix for the ASP.NET browser definition files in the Microsoft.NET Framework 4.0 should be installed. For more information, see

20 Preparing for Installing Acumatica ERP 20 Preparing for Installing Acumatica ERP Before you start installing Acumatica ERP, you may have to configure your system, including the following: Configuring Web Server (IIS) Features Setting Up an HTTPS Service in Web Server (IIS) Enabling Semantic Search for Microsoft SQL Server Configuring Web Server (IIS) Features Before you install the Acumatica ERP server software, make sure that the following Web Server (IIS) features are turned on: Web Management Tools > IIS Management Console World Wide Web Services > Application Development Features >.NET Extensibility World Wide Web Services > Application Development Features > ASP.NET World Wide Web Services > Application Development Features > ISAPI Extensions World Wide Web Services > Application Development Features > ISAPI Filters World Wide Web Services > Common HTTP Features > Default Document World Wide Web Services > Common HTTP Features > Static Content World Wide Web Services > Performance Features > Dynamic Content Compression World Wide Web Services > Performance Features > Static Content Compression World Wide Web Services > Security > Request Filtering Attention: Make sure, that for each application pool you are planning to use with Acumatica ERP 2017 R2 version or higher, the Enable 32-bit Applications parameter is set to False (the parameter is located under the IIS Manager > Application Pools > Edit Application Pool > Advanced Settings menu). Setting Up an HTTPS Service in Web Server (IIS) HTTPS is a secure communications channel that is used to exchange information between a client computer and a server. You may need to set up an HTTPS service in Web Server (IIS) for example, if your users export data to Microsoft Excel and want to update the data automatically, or you want to use single sign-on (SSO). To enable SSL in Web Server (IIS), you must first obtain a certificate that is used to encrypt and decrypt the information that is transferred over the network. You receive a certificate file from the certification authority, and then register the certificate with your Web Server (IIS). For instructions, refer to the documentation of your Web Server (IIS). Enabling Semantic Search for Microsoft SQL Server To access the full-text search functionality, you have to install the Semantic Search for the Microsoft SQL Server. For more information on searching in Acumatica ERP, see Managing Search in the Acumatica ERP User Guide. To install Semantic Search, do the following:

21 Preparing for Installing Acumatica ERP 21 Select Full-Text and Semantic Extractions for Search on the Features to Install page during Microsoft SQL Server setup. For details, see the documentation to Microsoft SQL Server.

22 Installing Acumatica ERP 22 Installing Acumatica ERP Acumatica ERP is a web-based application that users can access from any computer by using a web browser. The following topics (and the topics beneath them) describe the Acumatica ERP installation and deployment options: Installing Acumatica ERP Locally Setting Up Acumatica Self-Service Portal Installing Acumatica ERP in a Data Center Installing Acumatica ERP Locally You can install Acumatica ERP locally where you want it to be installed. Before you install Acumatica ERP, make sure that the server computer and software meet the system requirements specified in System Requirements for Acumatica ERP 2017 R To install an Acumatica ERP instance locally, you perform the following steps: Install the Acumatica ERP Tools on a server. For more information, see To Install the Acumatica ERP Tools. Deploy an Acumatica ERP instance on the server by using the Acumatica ERP Configuration Wizard. For more information, see To Deploy an Acumatica ERP Instance. Start working with Acumatica ERP by changing the password of the default user. For details, see To Change the Password at the First Sign-In. Acumatica ERP Tools The Acumatica ERP Tools include the following: The Acumatica ERP Configuration Wizard: A required software component that gives you the ability to deploy new application instances, delete application instances, and perform application and database maintenance. The Acumatica Report Designer: An optional software component that provides visual tools that you can use to design custom reports for Acumatica ERP. For more information, see Acumatica Report Designer Guide. The Debugger Tools: An optional set of software components that gives you a limited ability to debug the deployed Acumatica ERP instances. If you choose to install the Debugger Tools, in the installation directory, the installer adds the Sources folder and.pdb files to the bin folder. The Sources folder contains core files from Acumatica Framework which you can use when debugging the application. To Install the Acumatica ERP Tools To install the Acumatica ERP Tools, run the Acumatica ERP installation package and follow the instructions of the Acumatica ERP Installer wizard: On the Welcome page, click Next. On the License Agreement page, read the license agreement. To accept the license agreement, click I Agree. Click Next. 4. On the Main Software Configuration page, specify the following options:

23 Installing Acumatica ERP 23 Launch the Acumatica ERP Configuration Wizard: Select this check box to continue deploying the Acumatica ERP application instance once you install the Acumatica ERP Tools. Install Report Designer: Select this check box to install the optional Acumatica Report Designer. For more information, see Acumatica Report Designer Guide. Install Debugger Tools: Select this check box if you want to install the optional Debugger Tools component. 5. Click Next. 6. On the Select Installation Folder page, specify the location where you want to install Acumatica ERP Tools, and then click Next. : Click Disk Cost to view the list of the drives where you can install Acumatica ERP, along with the available and required disk space on each drive. 7. On the Confirm Installation page, click Next. 8. If you did not select the Launch the Acumatica ERP Configuration Wizard check box in Step 4, click Close when you're prompted. : You can run the Acumatica ERP Configuration Wizard anytime by selecting Start > Acumatica > Acumatica ERP Configuration. To Deploy an Acumatica ERP Instance You deploy an Acumatica ERP instance by using the Acumatica ERP Configuration Wizard. To Deploy a New Acumatica ERP Application Instance Run the Acumatica ERP Configuration Wizard. For example, select Start > Acumatica > Acumatica ERP Configuration. On the Welcome page, click Deploy New Application Instance. Alternatively, on the Welcome page of the Acumatica ERP Configuration Wizard, click Perform Application Maintenance, and then click New on the Application Maintenance page. On the Database Server Connection page, specify the database server that will be used by the Acumatica ERP instance: In the Server Type box, choose the server type. The following options are available: Microsoft SQL Server or MySQL Server. Select a server to connect to. Do one of the following: In the Server Name box, type the name or the address of the server machine. : For a MySQL server, the port number defaults to You can specify the custom port number after a comm If you are using a Microsoft SQL server, select the server in the Available Servers list. If the server list does not include the server you are looking for, you should click Update the List to rescan your network. The list of database servers may not have a particular server even after your network is rescanned (if, for instance, the server blocks broadcasts). If the problem persists, contact your network administrator for assistance. : If you use Microsoft SQL Server Express, the (local) option will not work even if the database server is running on the same machine. To use the server, start the SQL Browser service first, and then update the list of servers and select your server. Note

24 Installing Acumatica ERP 24 that Microsoft SQL Server Express should not be used in a production environment due to its limitations. c. Select the authentication method to be used to connect to the database server. If you select the SQL Server Authentication option, specify an account with sufficient rights for creating the databases or making changes to them. Keep the following points in mind as you select an authentication method: The selected authentication method must be supported by the database server. By default, Microsoft SQL Server 2005 is installed with Windows authentication disabled. Windows authentication works only for a local Microsoft SQL Server or when both application and database servers are members of the same Windows domain. Windows authentication doesn't work for a MySQL Server. 4. Click Next. 5. On the Database Configuration page, select the appropriate option as follows: To create a new database, click Create a new database and then type the name in the New database's name box. To connect to an existing database, do the following: Click Connect to an existing database. In the Available databases on server list, select a database name. Depending on the schema of the database you have selected, select the relevant check box to update, repair, or set up the database, if required. 4. If you want to shrink data after the database maintenance, select the Shrink data check box. 6. Click Next. 7. On the Company Setup page, do the following: 8. Configure the new company (named Company) that the Acumatica ERP Configuration Wizard created by default: To rename the company, double-click the company name in the Login Company Name column, type a new company name, and press Enter. If you want to fill the database with demo data, select SalesDemo in the Insert Data column. Optional: Add more companies if you want to create a multi-company Acumatica ERP instance. For more information about company setup, see Managing Companies. c. Optional: For a multi-company Acumatica ERP instance, if you want to restrict the list of companies a user can see only to the companies the user has access to, select the Secure Company on Login Form check box. In this case, the Company box does not appear on the Welcome screen by default and all users first authenticate themselves by entering their login and password. d. Optional: For a multi-company Acumatica ERP instance, if you want to configure data sharing between companies, select the Advanced Settings check box. For more information, see Multi-Company Instances. Click Next.

25 Installing Acumatica ERP Optional: On the Table Configuration page (which is displayed only if you have selected the Advanced Settings check box on the Company Setup page), configure data sharing between companies, and then click Next. : Table configuration is a dangerous operation that can result in database corruption. Any changes you make are at your own risk. If you configure tables, be sure to first back up the database. 10. On the Database Connection page, specify the authentication method that this instance of Acumatica ERP will use to connect to the database, which is one of the following options: Windows Authentication: The Acumatica ERP Configuration Wizard will use the default anonymous user account used by Internet Information Services (IIS). : Windows authentication doesn't work for a MySQL Server. SQL Server Authentication: Select Create new login to create a new SQL login, or select Use existing login and specify an existing login. The login must have at least the following rights: For a Microsoft SQL server, read, write, execute, and ddl_admin For a MySQL server, create, alter, drop, select, delete, insert, update, create temporary tables, and execute 1 Click Next. 1 On the Instance Configuration page, specify the following options: Instance Name: Type a name for this Acumatica ERP instance. Create Portal: Leave this check box cleared. c. Local Path to the Instance: Enter the path on the local computer to this application instance. 1 Click Next. 14. On the Web Site Configuration page, do the following: In the Web Site Settings section, configure the list of websites and create a virtual directory. To use the URL of the IIS default site (that is, clear the Create Virtual Directory check box. In the Application Pool Settings section, specify the application pool. You may want to use a dedicated application pool to better isolate instances and fine-tune resources that are allocated for the instance by IIS. To specify the dedicated application pool, select one of the following options: To create a new application pool, click Create New Application Pool and type the name in the Application Pool Name box. To use an existing application pool, click Use Existing Application Pool and select the name of the application pool in the list of available application pools. The list of application pools includes all the application pools you can use to install Acumatica ERP from the list of pools configured in Web Server (IIS), either classic or integrated. : Acumatica ERP employs the application pools that use one of the supported.net Framework versions. For the list of supported.net Framework versions, see System Requirements for Acumatica ERP 2017 R 15. Click Next. 16. On the Confirm Configuration page, do the following:

26 Installing Acumatica ERP 26 Check the configuration settings you have specified. Optional. To make any changes, click Back to return to the required wizard page, and then make necessary changes. c. If you want to save the configuration settings in an XML file on your computer, click Save Configuration. d. Click Finish to deploy this Acumatica ERP instance. To Change the Password at the First Sign-In Every Acumatica ERP instance comes with an active default user account that you use to sign in to the system. You start working with Acumatica ERP by changing the password for the default user. To Change the Password for the Default User Launch the application instance you have deployed by doing one of the following: On the Welcome page of the Acumatica ERP Configuration Wizard, click Perform Application Maintenance. On the Application Maintenance page, select the instance you have deployed and click Launch. Use the link created automatically in the Acumatica ERP program group. Navigate to in the web browser, where Instance_Name is the name that you specified in the Virtual Directory Name box on the Web Site Configuration page during configuration. (If you used the default name for the virtual directory during the deployment of the instance, you would use the following URL: : The URL works only on the local computer where you have installed Acumatica ERP Tools. To access the Acumatica ERP instance remotely, use the fully qualified domain name (FQDN) of the server instead of localhost in the URL. On the Welcome page, type the following default credentials: My User Name: admin My Password: setup Click Sign In. 4. Type the new password in the New Password and Confirm Password boxes. 5. If your Acumatica ERP instance is configured so that you need to agree to the terms of the Acumatica User Agreement, do the following: 6. Click the Acumatica User Agreement link, and read the user agreement. Select Check here to indicate that you have read and agree to the terms of the Acumatica User Agreement, if you agree to these terms. If you don't agree to the terms of the user agreement, you cannot start using the software. Click Sign In. Setting Up Acumatica Self-Service Portal Acumatica Self-Service Portal is designed to be the site where your customers can view all the relevant information about their interaction with your company as a vendor and perform common activities online.

27 Installing Acumatica ERP 27 To give your customers limited access to your Acumatica ERP instance, you deploy a Self-Service Portal instance connected to your Acumatica ERP instance. For details, see To Deploy a Self-Service Portal Instance. If you deploy a multi-company Acumatica ERP instance, after you deploy the Self-Service Portal instance, you must specify the company that the Self-Service Portal users can access. For details, see To Specify the Company Available for Self-Service Portal Users. : If you want different companies to be available through Self-Service Portal, you must deploy a SelfService Portal instance for each company. To Deploy a Self-Service Portal Instance After you install the Acumatica ERP instance, you use the Acumatica ERP Configuration Wizard to deploy the Self-Service Portal instance and connect it to the database used by the Acumatica ERP instance. By doing this, you can give your customers limited access to the Acumatica ERP instance. To Deploy a Self-Service Portal Instance Run the Acumatica ERP Configuration Wizard. Select Start > Acumatica > Acumatica ERP Configuration. On the Welcome page, click Deploy New Application Instance. On the Database Server Connection page, specify the database server that is used by the Acumatica ERP instance: In the Server Type box, select the server type. The following options are available: Microsoft SQL Server or MySQL Server. Select a server to connect to. Do one of the following: In the Server Name box, type the name or the address of the server machine. : For a MySQL server, the port number defaults to You can specify the custom port number after a comm If you are using a Microsoft SQL server, select the server in the Available Servers list. If the server list does not include the server you are looking for, you should click Update the List to rescan your network. The list of database servers may not have a particular server even after your network is rescanned (if, for instance, the server blocks broadcasts). If the problem persists, contact your network administrator for assistance. : If you use Microsoft SQL Server Express, the (local) option will not work even if the database server is running on the same machine. To use the server, start the SQL Browser service first, and then update the list of servers and select your server. Note that Microsoft SQL Server Express should not be used in a production environment due to its limitations. c. Select the authentication method to be used to connect to the database server. If you select the SQL Server Authentication option, specify an account with sufficient rights for creating the databases or making changes to them. Keep the following points in mind as you select an authentication method: The selected authentication method must be supported by the database server. By default, Microsoft SQL Server 2005 is installed with Windows authentication disabled. Windows authentication works only for a local Microsoft SQL Server or when both application and database servers are members of the same Windows domain.

28 Installing Acumatica ERP 28 Windows authentication doesn't work for a MySQL Server. 4. Click Next. 5. On the Database Configuration page, connect to the database that is used by the Acumatica ERP instance: Click Connect to an existing database. In the Available databases on server list, select the database that is used by the Acumatica ERP instance. c. If the schema of the database you have specified is outdated, select the Update database check box. d. If you want to shrink data after the database maintenance, select the Shrink data check box. 6. Click Next. 7. On the Company Setup page, check the companies used by the Acumatica ERP instance and click Next. 8. On the Database Connection page, specify the authentication method that the instance of SelfService Portal will use to connect to the database, which is one of the following options: Windows Authentication: The Acumatica ERP Configuration Wizard will use the default anonymous user account used by Internet Information Services (IIS). : Windows authentication doesn't work for a MySQL Server. 9. SQL Server Authentication: Select Create new login to create a new SQL login, or select Use existing login and specify an existing login. The login must have at least the following rights: For a Microsoft SQL server, read, write, execute, and ddl_admin For a MySQL server, create, alter, drop, select, delete, insert, update, create temporary tables, and execute Click Next. 10. On the Instance Configuration page, specify the following options: Instance Name: Type a name for this Self-Service Portal instance. Create Portal: Select this check box. c. Local Path to the Instance: Enter the path on the local computer to this application instance. 1 Click Next. 1 On the Web Site Configuration page, do the following: In the Web Site Settings section, configure the list of websites and create a virtual directory. To use the URL of the IIS default site (that is, clear the Create Virtual Directory check box. In the Application Pool Settings section, specify the application pool. You may want to use a dedicated application pool to better isolate instances and fine-tune resources that are allocated for the instance by IIS. To specify the dedicated application pool, select one of the following options:

29 Installing Acumatica ERP 29 To create a new application pool, click Create New Application Pool and type the name in the Application Pool Name box. To use an existing application pool, click Use Existing Application Pool and select the name of the application pool in the list of available application pools. The list of application pools includes all the application pools you can use to install Acumatica ERP from the list of pools configured in Web Server (IIS), either classic or integrated. : Acumatica ERP employs the application pools that use one of the supported.net Framework versions. For the list of supported.net Framework versions, see System Requirements for Acumatica ERP 2017 R 1 Click Next. 14. On the Confirm Configuration page, do the following: Check the configuration settings you have specified. Optional. To make any changes, click Back to return to the required wizard page, and then make necessary changes. c. If you want to save the configuration settings in an XML file on your computer, click Save Configuration. d. Click Finish to deploy this Acumatica ERP instance. If you use a multi-company configuration, now you must specify the company that the Self-Service Portal instance will be connected to, as described in To Specify the Company Available for Self-Service Portal Users. To Specify the Company Available for Self-Service Portal Users If you use a multi-company Acumatica ERP configuration, after you deploy a Self-Service Portal instance, you must specify the company that will be available for the Self-Service Portal users. To Configure the Companies Available for Self-Service Portal Users Open the weconfig file for the Self-Service Portal instance. This file is usually located in %Program Files%\Acumatica ERP\<instance name>, where <instance name> is the name of the Self-Service Portal instance site. In the file, find the providers section, which has the following settings: <add name="pxsqldatabaseprovider"... companyid="".../> Change the following key value: companyid="x" where x is the ID of the company you want to make available to the Self-Service Portal users. 4. Save the weconfig file; this automatically restarts the website. Installing Acumatica ERP in a Data Center You can install Acumatica ERP in a data center in which the system and the associated databases are hosted by the hosting provider. With most host providers, you follow the installation procedure described in Installing Acumatica ERP Locally. If you choose to deploy Acumatica ERP on Windows Azure as a service, you need to create the

30 Installing Acumatica ERP 30 Acumatica ERP Service package and deploy it on Windows Azure, as described in a later section of this document. Installing Acumatica ERP in a Data Center You can install Acumatica ERP on a hosting or cloud services provider because these providers provide persistent, durable storage in the cloud. If you are provided with a web service where you can launch an operating system with Microsoft SQL Server available, follow the installation procedure described in Installing Acumatica ERP Locally. Deploying the Acumatica ERP Service on Windows Azure You can deploy Acumatica ERP as a cloud service in Windows Azure. In this case, you create an Acumatica ERP Service package and upload it to the cloud service. For details, see Deploying the Acumatica ERP Service on Windows Azure. Installing Acumatica ERP on Amazon Web Services with Independent Database Server You can install the Acumatica ERP Tools on an Amazon Elastic Compute Cloud (Amazon EC2) virtual machine and use the Amazon Relational Database Service (Amazon RDS) to host the databases. For detail, see Installing Acumatica ERP on Amazon Web Services. Deploying the Acumatica ERP Service on Windows Azure Acumatica ERP can be deployed on Windows Azure, which is a cloud services platform hosted through Microsoft data centers. The platform includes the Windows Azure operating system and a set of developer services. Also, you can access the storage services that are provided through the Windows Azure Management Portal. To use them, you must have a storage account. System Requirements Deploying Acumatica ERP on Microsoft Azure imposes additional limitations to Acumatica ERP system requirement, described in System Requirements for Acumatica ERP 2017 R The performance and capabilities of Microsoft Azure SQL databases depend on the service tier you select for the database, with the performance levels expressed in database throughput units (DTUs). To successfully run Acumatica ERP on Azure, the database must have at least 50 DTUs. Taking into account the requirement for databases, you should select at least Standard S2 service tier. For more information on service tiers, see Service Tiers on Microsoft Azure. Before You Begin To deploying Acumatica ERP instance on Windows Azure, you will need the following: An Azure account. For more information, see Microsoft Azure. An SSL service certificate that has been signed by a Certificate Authority, a trusted third-party who issues certificates. If you do not already have one, you will need to obtain one from a company that sells SSL certificates. If you have the certificate imported in the system, you can export the certificate into a PFX file by using the Internet Information Services (IIS) Manager or OpenSSL command-line tools. Deployment To deploy the Acumatica ERP Service on the Windows Azure platform, you perform the following steps: Download the service package file To Download the Configuration Package

31 Installing Acumatica ERP 31 Prepare for deployment on Windows Azure. For more information, see To Prepare for Deployment on Windows Azure. Set up the database options and create an Acumatica ERP Service package on your local computer. For the detailed procedure, see To Create an Acumatica ERP Service Package. 4. Deploy the Acumatica ERP Service package on Windows Azure. For the detailed procedure, see To Deploy the Acumatica ERP Service on Windows Azure. To Download the Configuration Package Before you begin installing Acumatica ERP as a service on Windows Azure, you need to get the Azure service package file that you can download on the Partner Portal. The package file should correspond to the version of Windows Azure that you purchased as shown in the following table. Azure Deployment Acumatica ERP Edition Configuration Package Small Standard SmallService.cspkg Medium Advanced MediumService.cspkg Large Enterprise LargeService.cspkg 90 day free trial Unlicensed SmallService.cspkg To Download the Configuration Package On the Downloads tab of the Partner Portal, click on the service package you plan to use. The Azure service package file (.cspkg) is downloaded on your computer. To Prepare for Deployment on Windows Azure Before you deploy an Acumatica ERP instance on Windows Azure, you configure your Windows Azure account. To prepare for deployment, perform the following steps: Create a new cloud service on Windows Azure as follows: In Management Portal, click New, Cloud Service, and then Quick Create. In URL, enter your company name to use in the public URL for accessing your cloud service in production deployments. The URL format for production deployments is where mycompany is the company name. c. In Region/Affinity Group, select Acumatica Group. d. Click Create Cloud Service. Add an SSL service certificate to the certificate store on Windows Azure. Before you can use a Windows Azure service certificate, you must upload it to a cloud service. Export a new certificate into a PFX file by using the Internet Information Services (IIS) Manager or OpenSSL command-line tools, and then upload this file to Windows Azure by using the Windows Azure Management Portal or the Windows Azure Service Management API. The uploaded certificate can then be used by a service or stored in the hosted services certificate store. To add the certificate, do the following: In Management Portal, click Cloud Services. Then click the name of the cloud service you created in Step 1 to open the dashboard. Open the Certificates page and click Add new certificate. The Add a Certificate dialog box opens. c. In Certificate file, use Browse to select the certificate (PFX file) to use.

32 Installing Acumatica ERP d. In Password, enter the private key for the certificate. e. Click OK. f. Copy and paste the thumbprint of the certificate into a file; you will need it during a later step, when you're configuring database settings. Configure remote access to the role instance as follows: In Management Portal, select Cloud Services. Then click the name of the cloud service you created in Step 1 to open the dashboard. Open the Configure page for the cloud service, and click Remote. c. On the Configure Remote Desktop Settings page, make the following changes: Select the Enable remote desktop check box. Create an account to use in Remote Desktop connections to the role instances. In the Certificates dialog box, select the certificate you uploaded in the previous step. d. Click OK. e. Connect to a role instance as follows: Click Instances to open the Instances page. Click the role instance that has Remote Desktop configured to select the instance. c. Click Connect, and follow the instructions to open the desktop of the virtual machine. Create a SQL database on Windows Azure: Click +NEW at the bottom of the page. Click Data Services. c. Click SQL Database. d. Click Custom Create. e. In Name box, enter a name for the new database. f. In the Edition box, select the WEB edition. g. Select the Subscription box, depending on your company contract. h. In the Service Tiers and Performance Level boxes, choose the service tier you want to use. : For running Acumatica ERP you should select at least the Standard S2 service tier. i. In the Collation box, specify the collation for your database. The SQL_Latin1_General_CP1_CI_AS collation is selected by default. j. In the Server box, select New SQL Database Server. k. Click the check mark to go to the next page. l. In the Server Settings box, enter a SQL Server authentication login name and password. m. Click the check mark at the bottom of the page when you are finished.

33 Installing Acumatica ERP 33 To Create an Acumatica ERP Service Package You install the Acumatica ERP Tools on the local computer and use the Acumatica ERP Configuration Wizard to set up database options and create an Acumatica ERP Service package as follows: To Set Up Database Options and Create an Acumatica ERP Service Package Install the Acumatica ERP Tools on the local computer, as described in To Install the Acumatica ERP Tools. Open the Acumatica ERP Configuration Wizard. On the Welcome page of the Acumatica ERP Configuration Wizard, click Generate Azure Configuration File. 4. On the Database Server Connection page, enter the host name of the Microsoft Azure SQL server and the administrator account credentials. 5. Click Next. 6. On the Database Configuration page, do one of the following: 7. To create a new database, click Create a new database and then type the name in the New database's name box. To connect to an existing database, do the following: Click Connect to an existing database. In the Available databases on server list, select a database name. Depending on the schema of the database you have selected, select the relevant check box to update, repair, or set up the database. 4. If you want to shrink data after the database maintenance, select the Shrink data check box. On the Company Setup page, do the following: Do the following to configure the new company (named Company) that the Acumatica ERP Configuration Wizard created by default: To rename the company, double-click the company name in the Login Company Name column, type a new company name, and press Enter. If you want to fill the database with demo data or template data, select Demo or Template in the Insert Data column. Optional: If you want to create a multi-company Acumatica ERP instance, add more companies. For more information about company setup, see Managing Companies. c. Optional: For a multi-company Acumatica ERP instance, if you want to restrict the list of companies a user can see only to the companies the user has access to, select the Secure Company on Login Form check box. In this case, the Company box does not appear on the Welcome screen by default and all users first authenticate themselves by entering their login and password. d. Optional: For a multi-company Acumatica ERP instance, if you want to configure data sharing between companies, select the Advanced Settings check box. For more information, see Multi-Company Instances 8. Click Next. 9. Optional: On the Tables Configuration page, you can specify whether you want the database tables to be shared by different companies, and then click Next.

34 Installing Acumatica ERP 34 : This page is displayed only if you have selected the Advanced Settings check box on the previous page. 10. On the Instance Configuration page, specify the following options: Instance Name: Enter a name for this application instance of Acumatica ERP. Local Path to the Instance: Enter the local path to the configuration files folder. c. SSL Certificate Thumbprint: Enter the thumbprint of the SSL service certificate that you saved to a text file in To Prepare for Deployment on Windows Azure. 1 Click Next. 1 On the Confirm Configuration page, verify the configuration settings, and then click Finish. 1 On the Confirm Configuration page, do the following: Check the configuration settings you have specified. Optional. To make any changes, click Back to return to the required wizard page, and then make necessary changes. c. Click Finish. The service package (.cspkg) file is generated and stored on your computer. To Deploy the Acumatica ERP Service on Windows Azure To deploy the Acumatica ERP Service on Windows Azure, use the Windows Azure Management Portal to upload the following files: The service package file (.cspkg) that you downloaded from the Partner Portal. For more information, see Deploying the Acumatica ERP Service on Windows Azure. The service configuration file (.cscfg) you created in To Create an Acumatica ERP Service Package To Deploy the Packaged Acumatica ERP Service on Windows Azure In the Management Portal, click Cloud Services. Then click the name of the cloud service to open the dashboard. Click Quick Start to open the Quick Start page. Click New Production Deployment or New Staging Deployment. 4. In Upload a Package, make the following changes: 5. In Deployment name, enter a name for the new deployment. In Package, use Browse to select the service package file (.cspkg) to use. c. In Configuration, use Browse to select the service configuration file (.cscfg) to use. Click OK (check mark) to begin the cloud service deployment. Uploading the service package file and the service configuration file may take several minutes. You can track the upload progress on the Azure Management Portal. : For more information about deploying a cloud service, see How to Create and Deploy a Cloud Service on Microsoft Azure portal. When you create an application in Windows Azure, Windows Azure provides a friendly subdomain on the cloudapp.net domain so your users can access your application by using a URL such as <myurl>.cloudapp.net. However, you can also expose your application and data on your own domain

35 Installing Acumatica ERP 35 name. For more information, see Configuring a custom domain name for a Windows Azure cloud service or storage account on Microsoft Azure portal. Installing Acumatica ERP on Amazon Web Services You can launch Acumatica ERP on Amazon Web Services (AWS). In this case, you use the Amazon Elastic Compute Cloud (Amazon EC2) to host the web server and Amazon Relational Database Service (Amazon RDS) to host the databases. This section includes our recommendations for configuring the EC2 and RDS instances and the details about deploying Acumatica ERP on AWS. Before You Begin Before you start deploying Acumatica ERP on Amazon Web Services, make sure you have completed the following tasks: Sign up for Amazon Web Services. Create a key pair. Create a security group that will specify your EC2 instance, which can access your RDS instance. To Launch Acumatica ERP on Amazon Web Services Launch an Amazon EC2 instance. For more information, see To Launch an Amazon EC2 Instance. Create a database instance by using Amazon RDS. For details, see To Create a Database Instance on Amazon RDS. Install Acumatica ERP Tools and deploy a new application instance. For more information, see To Deploy Acumatica ERP on Amazon EC To Launch an Amazon EC2 Instance When you launch your Amazon EC2 instance, you secure it by specifying a key pair and security group. When you connect to your instance, you must specify the private key of the key pair that you specified when launching your instance. To Launch an Amazon EC2 Instance Sign in to the AWS Management Console and open the Amazon EC2 console. In the top right corner of the Amazon EC2 console, select the region for your EC2 instance. : You must select the same region for your EC2 and RDS instances and for the key pair you use to sign in to your instances. From the console dashboard, click Launch Instance. 4. On the Select an Amazon Machine Image (AMI) page, select the Windows Server 2012 Base 64bit AMI. 5. On the Select an Instance Type page, select the mmedium hardware configuration for your instance. 6. On the Security Groups page, select the security group that you've prepared to launch Acumatica ERP. 7. On the Review Instance Launch page, review the settings for your instance, and then click Launch. 8. In the Select an existing key pair or create a new key pair dialog box, select Choose an existing key pair, and then select the prepared key pair. 9. When you are ready, select the acknowledgment check box, and then click Launch Instances.

36 Installing Acumatica ERP 36 A confirmation page lets you know that your instance is launching. 10. Click View Instances to close the confirmation page and return to the console. 1 On the Instances page, view the status of your instance. It takes a short time for an instance to launch. When you launch an instance, its initial state is pending. After the instance starts, its state changes to running, and it receives a public DNS name. 1 On the Instances screen, select the instance and click Connect. 1 In the Connect to Your Instance dialog box: Select the prepared key. Download the Remote Desktop file. 14. Run the Remote Desktop file you've downloaded in Step 13 to access the web server you have launched. 15. For the operating system of the virtual machine, turn on the Microsoft Internet Information Services (IIS) and make sure the required IIS features are turned on, as described in System Requirements for Acumatica ERP 2017 R To Create a Database Instance on Amazon RDS After you set up the EC2 instance, you can create a database instance by using the RDS console. To Create a Database Instance on Amazon RDS Sign in to the AWS Management Console and open the Amazon RDS console. In the top right corner of the Amazon RDS console, select the region in which you want to create the database instance. : You must select the same region for your EC2 and RDS instances and for the key pair you use to sign in to your instances. In the navigation pane, click Instances. 4. Click Launch DB Instance to start the Launch DB Instance wizard. The wizard opens on the Engine Selection page If you want to use MS SQL database, do the following: In the Launch DB Instance Wizard window, click the Select button for the MS SQL Server Web Edition. On the DB Instance Details page, specify your database instance information, including the following settings: DB Instance Class: dmmedium Allocated Storage: 20 GB DB Instance Identifier Master User Name Master Password If you want to use MySQL database, do the following: In the Launch DB Instance Wizard window, click the Select button for the MySQL Community Edition.

37 Installing Acumatica ERP 37 On the DB Instance Details page, specify your database instance information, including the following settings: DB Engine: as specified in System Requirements for Acumatica ERP 2017 R2 DB Instance Class: dmmedium Allocated Storage: 20 GB Multi-AZ Deployment: No DB Instance Identifier Master User Name Master Password 7. Click Next Step. 8. On the Additional Configuration page, provide the additional information that RDS uses to launch the SQL Server database instance, including the following setting: 9. DB Security Groups: Select the prepared security group you used when launching the EC2 instance. Click Next Step. 10. On the Management Options page, you can specify backup and maintenance options for your database instance. 1 Click Next Step. 1 On the Review page, review the options for your database instance. When you're certain of all the settings, click Launch DB Instance. 1 On the final page of the wizard, click Close. 14. On the RDS console, the new database instance appears in the list of instances. The database instance will have a status of creating until it is created and ready for use. When the state changes to available, you can connect to the database instance. Depending on the database instance class and store allocated, it could take several minutes for the new instance to be available. 15. On the RDS console, select the database and check the DNS name of the instance in the Endpoint box; you will need this name during Acumatica ERP installation. To Deploy Acumatica ERP on Amazon EC2 After you launch the Amazon EC2 and RDS instances, you can install Acumatica ERP Tools and deploy application instances. To Deploy Acumatica ERP on the Amazon EC2 Instance Use the Remote Desktop Connection to connect to the web server running on your Amazon EC2 instance. Copy the Acumatica ERP installation package to the web server. Install the Acumatica ERP Tools, as described in To Install the Acumatica ERP Tools. 4. On the Welcome page of the Acumatica ERP Configuration Wizard, click Deploy New Application Instance. 5. On the Database Server Connection page, specify the database server that will be used by the Acumatica ERP instance:

38 Installing Acumatica ERP 38 In the Server Type box, choose the server type you used to deploy the database on Amazon RDS. The following options are available: Microsoft SQL Server or MySQL Server. In the Server Name box, enter the DNS name of the Amazon RDS database instance you've launched. Also, you can specify a custom port number after a comm : If you cannot connect to the server, check the security groups you've selected for the EC2 and RDS instances: You must select the same group for both services. : For a MySQL server, the port number defaults to c. Select the SQL Server Authentication method, and specify the login that you created while you set up the Amazon RDS database instance (in Step 5 or 6 of the To Create a Database Instance on Amazon RDS procedure, depending on the database type): Login: Master User Name Password: Master Password 6. Click Next. 7. On the Database Configuration page, connect to the database that you've launched on Amazon RDS. Do the following: Click Connect to an existing database. In the Available databases on server list, enter the database name. c. Depending on the schema of the database you have selected, select the relevant check box to update, repair, or set up the database, if required. d. If you want to shrink data after the database maintenance, select the Shrink data check box. 8. Click Next. 9. On the Company Setup page, do the following: Configure the new company, named Company, that the Acumatica ERP Configuration Wizard created by default: To rename the company, double-click the company name in the Login Company Name column, type a new company name, and press Enter. If you want to fill the database with demo data or template data, select Demo or Template in the Insert Data column. Optional: Add more companies if you want to create a multi-company Acumatica ERP instance. For more information about company setup, see Managing Companies. c. Optional: For a multi-company Acumatica ERP instance, if you want to restrict the list of companies a user can see only to the companies the user has access to, select the Secure Company on Login Form check box. In this case, the Company box does not appear on the Welcome screen by default and all users first authenticate themselves by entering their login and password. d. Optional: For a multi-company Acumatica ERP instance, if you want to configure data sharing between companies, select the Advanced Settings check box. For more information, see Multi-Company Instances. 10. Click Next.

39 Installing Acumatica ERP 39 1 Optional: On the Tables Configuration page (which is displayed only if you have selected the Advanced Settings check box on the Company Setup page), configure data sharing between companies, and then click Next. : Table configuration is a dangerous operation that can result in database corruption. Any changes you make are at your own risk. If you configure tables, be sure to first back up the database. 1 On the Database Connection page, specify the authentication method that this instance of Acumatica ERP will use to connect to the database. Do the following: Select the SQL Server Authentication authentication method. Select Use Existing Login option and specify the login you created while you set up the Amazon RDS database instance (in Step 5 or 6 of the To Create a Database Instance on Amazon RDS procedure, depending on the database type): Login: Master User Name Password: Master Password 1 Click Next. 14. On the Instance Configuration page, specify the following options: Instance Name: Type a name for this Acumatica ERP instance. Create Portal: Leave the check box cleared. Local Path to the Instance: Enter the path on the local computer to this application instance. 15. Click Next. 16. On the Web Site Configuration page, do the following: In the Web Site Settings section, configure the list of websites and create a virtual directory. To use the URL of the Internet Information Services (IIS) default site (that is, clear the Create Virtual Directory check box. In the Application Pool Settings section, specify the application pool. You may want to use a dedicated application pool to better isolate instances and fine-tune resources that are allocated for the instance by IIS. To specify the dedicated application pool, select one of the following options: To create a new application pool, click Create New Application Pool and type the name in the Application Pool Name box. To use an existing application pool, click Use Existing Application Pool and select the name of the application pool in the list of available application pools. The list of application pools includes all the application pools you can use to install Acumatica ERP from the list of pools configured in Web Server (IIS), either classic or integrated. : Acumatica ERP employs the application pools that use one of the supported.net Framework versions. For the list of supported.net Framework versions, see System Requirements for Acumatica ERP 2017 R 17. Click Next. 18. On the Confirm Configuration page, do the following: Check the configuration settings you have specified. Optional: To make any changes, click Back to return to the required wizard page, and then make necessary changes.

40 Installing Acumatica ERP 40 c. If you want to save the configuration settings in an XML file on your computer, click Save Configuration. d. Click Finish to deploy this Acumatica ERP instance.

41 Installing Acumatica Framework 41 Installing Acumatica Framework Acumatica Framework is a Web 0 application development platform that you use to develop business applications, such as enterprise resource planning (ERP) systems. Installing Acumatica Framework To install Acumatica Framework, perform these steps: Install the Acumatica Framework Tools on a server computer. For more information, see To Install Acumatica Framework Tools. Deploy an Acumatica Framework instance on the server by using the Acumatica Framework Configuration Wizard. For more information, see To Deploy an Acumatica Framework Instance. Start working with Acumatica Framework by changing the password of the default user. For details, see To Change the Password at the First Sign-In. Installing Acumatica Framework Templates For details on the installation of Acumatica Framework Templates, see To Install Acumatica Framework Templates. Using Acumatica Framework Tools You use the Acumatica Framework Configuration Wizard to deploy the Acumatica Framework instances. Acumatica Framework Tools include the Acumatica Framework Configuration Wizard and the Acumatica Report Designer. The Acumatica Framework Configuration Wizard gives you the ability to deploy new application instances and perform application and database maintenance. The Acumatica Report Designer provides visual tools that you can use to design custom reports for Acumatica ERP. For more information, see Acumatica Report Designer Guide. To Install Acumatica Framework Tools To install Acumatica Framework, run the Acumatica Framework installation package and follow the instructions of the Acumatica Framework Installer wizard: On the Welcome page, click Next. On the License Agreement page, read the license agreement. To accept the agreement, click I Agree, and then click Next. On the Main Software Configuration page, specify the option that you want: Launch the Configuration Wizard (Recommended): Select this check box if you want to continue deploying Acumatica Framework once you install it. Install Report Designer: Select this check box if you want to install the optional Acumatica Report Designer component. For more information, see Acumatica Report Designer Guide. 4. Click Next. 5. On the Select Installation Folder page, specify the location where you want to install Acumatica Framework Tools.

42 Installing Acumatica Framework 42 : Click Disk Cost to view the list of the drives where you can install Acumatica Framework, along with the available and required disk space on each drive. 6. Click Next. 7. On the Confirm Installation page, click Next. 8. If you did not select the Launch the Acumatica Framework Configuration Wizard check box in Step 3, click Close when you're prompted. : You can run the Acumatica Framework Configuration Wizard anytime by selecting Start > Acumatica > Acumatica Framework Configuration. To Deploy an Acumatica Framework Instance During this step, you deploy an instance by using the Acumatica Framework Configuration Wizard. To deploy a new Acumatica Framework instance, do the following: Run the Acumatica Framework Configuration Wizard. For example, select Start > Acumatica > Acumatica Framework Configuration. On the Welcome page of the wizard, do one of the following: Click Deploy New Instance of Acumatica Application Template to deploy a new application instance or an application instance with training templates. Click Deploy New Instance of Acumatica Training Application to deploy a training application instance of Acumatica Framework with all demo dat On the Database Server Connection page, specify the database server that will be used by the Acumatica Framework instance: In the Server Type box, choose the server type. The following options are available: Microsoft SQL Server or MySQL Server. Select a server to connect to. Do one of the following: In the Server Name box, type the name or the address of the server machine. Also, you can specify the custom port number after a comm : For a MySQL server, the port number defaults to If you are using a Microsoft SQL server, select the server in the Available Servers list. If the server list does not include the server you are looking for, you should click Update the List to rescan your network. The list of database servers may not have a particular server even after your network is rescanned (if, for instance, the server blocks broadcasts). If the problem persists, contact your network administrator for assistance. : If you use Microsoft SQL Server Express, the (local) option will not work even if the database server is running on the same machine. To use the server, start the SQL Browser service first, and then update the list of servers and select your server. Note that Microsoft SQL Server Express should not be used in a production environment due to its limitations. c. Select the authentication method to be used to connect to the database server. If you select the SQL Server Authentication option, specify an account with sufficient rights

43 Installing Acumatica Framework 43 for creating the databases or making changes to them. Keep the following points in mind as you select an authentication method: The selected authentication method must be supported by the database server. By default, Microsoft SQL Server 2005 is installed with Windows authentication disabled. Windows authentication works only for a local Microsoft SQL Server or when both application and database servers are members of the same Windows domain. Windows authentication doesn't work for a MySQL Server. 4. Click Next. 5. On the Database Configuration page, select the appropriate option as follows: To create a new database, click Create a new database, and then type the name in the New database's name box. To connect to an existing database, do the following: Click Connect to an existing database. In the Available databases on server list, click a database name. Depending on the schema of the database you have selected, select the relevant check box to update, repair, or set up the database. To shrink data after the database maintenance, select the Shrink data check box. 6. Click Next. 7. On the Database Connection page, specify the authentication method that this application instance of Acumatica Framework will use to connect to the database, which is one of the following options: Windows Authentication: The Acumatica Framework Configuration Wizard will use the default anonymous user account used by Internet Information Services (IIS). : Windows authentication doesn't work for a MySQL Server. SQL Server Authentication: Select Create new login to create a new SQL login, or select Use existing login and specify an existing login. The login must have at least the following rights: For a Microsoft SQL server, read, write, execute, and ddl_admin For a MySQL server, create, alter, drop, select, delete, insert, update, create temporary tables, and execute 8. Click Next. 9. On the Instance Configuration page, specify the following options: Instance Name: Type a name for this Acumatica Framework instance. Local Path to the Instance: Enter the path on the local computer to this application instance. 10. Click Next. 1 On the Web Site Configuration page, do the following: Configure the list of websites and create a virtual directory. To use the URL of the IIS default site (that is, clear the Create Virtual Directory check box.

44 Installing Acumatica Framework 44 Specify the application pool. You may want to use a dedicated application pool to better isolate instances and fine-tune resources that are allocated for the instance by IIS. To specify the dedicated application pool, select one of the following options: To create a new application pool, click Create New Application Pool and type the application pool name. To use the existing application pool, click Use Existing Application Pool and select the name of the application pool. The list of application pools includes all the application pools you can use to install Acumatica Framework from the list of pools configured in Web Server (IIS), either classic or integrated. : Acumatica Framework employs the application pools that use one of the supported.net Framework versions. For the list of supported.net Framework versions, see System Requirements for Acumatica ERP 2017 R 1 Click Next. 1 On the Confirm Configuration page, do the following: Check the configuration settings you have specified. Optional. To make any changes, click Back to return to the required wizard page, and then make necessary changes. c. To save the configuration settings in an XML file on your computer, click Save Configuration. d. Click Finish to deploy this Acumatica Framework instance. : You can deploy an Acumatica Framework instance by using the command line. For more information, see Using the Command-Line Tool. To Change the Password at the First Sign-In Every Acumatica Framework instance comes with an active default user account that you use to sign in to the system. You start working with the Acumatica Framework instance by changing the password for the default user. To Change the Password for the Default User Launch the application instance you have deployed by doing one of the following: On the Welcome page of the Acumatica Framework Configuration Wizard, click Perform Application Maintenance. On the Application Maintenance page, select the instance you have deployed and click Launch. Use the link created automatically in the Acumatica Framework program group. Navigate to in the web browser, where Instance_Name is the name that you specified in the Virtual Directory Name box on the Web Site Configuration page during configuration. (If you used the default name for the virtual directory during the deployment of the instance, you would use the following URL: : The URL works only on the local computer where you have installed Acumatica Framework Tools. To access the Acumatica Framework instance remotely, use the fully qualified domain name (FQDN) of the server instead of localhost in the URL.

45 Installing Acumatica Framework 45 On the Welcome page, enter the following default credentials: My User Name: admin My Password: setup Click Sign In. 4. Type the new password in the New Password and Confirm Password boxes. 5. If your Acumatica Framework instance is configured so that you need to agree to the terms of the Acumatica User Agreement, do the following: 6. Click the Acumatica User Agreement link, and read the user agreement. Select Check here to indicate that you have read and agree to the terms of the Acumatica User Agreement, if you agree to these terms. If you don't agree to the terms of the user agreement, you cannot start using the software. Click Sign In. To Install Acumatica Framework Templates To install Acumatica Framework Templates, which consist of Microsoft Visual Studio templates, do the following: Run the Acumatica Framework Configuration Wizard. For example, select Start > Acumatica > Acumatica Framework Configuration. On the Welcome page of the wizard, click Deploy Acumatica Framework Tools. On the Confirm Configuration page, if you want to save the configuration settings in an XML file on your computer (which you can use later for an unattended installation from the command line), click Save Configuration. 4. Click Finish.

46 Licensing and Activating Acumatica ERP 46 Licensing and Activating Acumatica ERP By default, Acumatica ERP is installed in trial mode. Although in this mode all features are available, the mode has the following restrictions: You can create no more than 10 companies per instance. All companies that you create have the Test status. Only two users can concurrently use the system. Each time a third user signs in to Acumatica ERP, one of the current users is forcibly signed out. For details on test companies, see Support of Multiple Companies in the Acumatica ERP User Guide. You remove the trial mode restrictions when you obtain and activate the license for using Acumatica ERP. A license is applied to an Acumatica ERP instance defining the number of companies you can add to the instance, the number of concurrent users, and the set of features you can activate for the instance. You can create additional trial companies. For details on applying a license, see To Activate the License for an Acumatica ERP Instance. If you use Acumatica Self-Service Portal you have to obtain a license for the Self-Service Portal instance, activate the license, and then activate the required Self-Service Portal features. For details, see Configuring Acumatica Self-Service Portal. To Activate the License for an Acumatica ERP Instance To activate your Acumatica ERP instance, you obtain a product key and then register the key by using the Activate License (SM201510) form. To Activate the Product License : Before you proceed with activation, make sure that all Acumatica ERP users have saved their work and signed out of the system. During licensing and activation, the Acumatica ERP instance is restarted, and any unsaved work is lost. Obtain a product key by creating a support case through the Partner Portal. Submit the following information: Installation ID: The installation ID is available on the About dialog box of the Acumatica ERP application instance. To open this dialog box, on any Acumatica ERP form, select Help > About. Contract ID: You can find this ID on your Acumatica ERP sales invoice. On the Configuration tab, click Common Settings. In the left pane, navigate to Licensing > Activate License. Depending on the license type that you have obtained from your sales representative, do one of the following: If you have obtained a license key, click Enter License Key on the form toolbar, enter the license key in the Activate New License dialog box, and click OK. The system contacts the licensing server and validates the license online. Each license can be used to activate a predetermined number of instances. If you reach the limit for your license, you generally won't be able to use this license. Alternatively, depending on your license settings, the system may offer to deactivate the license from the oldest instance.

47 Licensing and Activating Acumatica ERP 47 : To validate your license, the licensing server requires port 443 to be opened on the computer running the Acumatica ERP instance you use to enter the key. You may have to open port 443 if the computer has a firewall enabled. If you have obtained a license file, click Upload License File on the form toolbar, and then select and upload the license file by using the Upload New License File dialog box. If you use a license file, the system validates the license without contacting the licensing server. 4. In the Agree to Proceed dialog box, which opens, click the link to read the license agreement, and if you agree to the terms of the agreement, click Agree to proceed with activation and close the dialog box. 5. In the table, review the features that this license supports, and make sure that the feature list is correct. 6. Click Apply License to activate your instance.

48 Maintaining Acumatica ERP 48 Maintaining Acumatica ERP The topics in this section describe how to perform maintenance tasks that are associated with the Acumatica ERP instances and their databases: To Check the State of Application Instances and Databases To Turn On Snapshot Isolation Mode for a Database To View the Details of an Acumatica ERP Instance To Change the Database of an Instance To Perform Database Maintenance To Configure the Session Time-Out To Configure the Report Time-Out To Configure the Query Time-Out To Select Roles That Will Have Administrative Privileges To Shorten the Names of the Customization Folders To Turn On Reminders To Turn On the My Tasks and Events Button To Enable Push Notifications You can also perform database and application maintenance tasks by using the command-line tool. For more information, see Using the Command-Line Tool. To Check the State of Application Instances and Databases You can check the state of your application instances and databases and see which instances and databases you need to update. To Check the State of Application Instances and Databases Run the Acumatica ERP Configuration Wizard on the server where Acumatica ERP is installed. For example, select Start > Acumatica > Acumatica ERP Configuration. On the Welcome page, click Perform Application Maintenance. On the Application Maintenance page of the Acumatica ERP Configuration Wizard, the system flags each instance in the list of installed sites with one of the following icons: Green check mark: Indicates that the instance and the associated database are up to date (the versions of the application instance, the database, and the Acumatica ERP Configuration Wizard are the same). Yellow triangle with exclamation point: Indicates that the instance and the instance database are outdated (the version of the application instance is same as the version of the database and is older than that of the installed Acumatica ERP Configuration Wizard). You may need to update the application instance and the database. : After you update the Acumatica ERP Tools, all your instances installed before the update are marked in this way.

49 Maintaining Acumatica ERP 49 Red circle with a white X: Indicates that the instance or the database (depending on which has an older version) requires update; that is, the versions of the instance and the instance's database are different. You must update the one whose version is older. Also, this marking may indicate that the instance and the database versions are newer than the version of the installed Acumatica ERP Configuration Wizard. You won't be able to downgrade the instance or the database. For example, the following screenshot shows three instances. The z instance has been updated. The database of the v3 instance has been updated and the site needs to be updated. The v2 instance is a working instance that may be updated if required. Figure: Checking the state of the application instances and databases To Turn On Snapshot Isolation Mode for a Database In order for an Acumatica ERP instance that uses a SQL Server database to work properly, snapshot isolation must be turned on for the instance database. In this topic, you can find information about how to use SQL Server Management Studio to check if snapshot isolation mode is turned on and how to turn on this mode for your database. To Check If Snapshot Isolation Mode Is Turned On Run the following query in SQL Server Management Studio: SELECT is_read_committed_snapshot_on FROM sys.databases WHERE name = '<database name>' where <database name> is the name of the database whose settings you want to check. If the is_read_committed_snapshot_on parameter is set to 1, snapshot isolation mode is turned on. If not, you have to turn on snapshot isolation mode. To Turn On Snapshot Isolation Mode for a Database In SQL Server Management Studio, right-click the database and click Properties to open the Database Properties dialog box. Select the Options page. In the Miscellaneous section, set Is Read Committed Snapshot On to True. 4. Click OK to save the settings and close the dialog box.

50 Maintaining Acumatica ERP 50 To View the Details of an Acumatica ERP Instance You can view such details of an Acumatica ERP instance as the local path to configuration files, the database the application is connected to, the virtual directory name, the website name, and the current version of the site and database. To View the Details of an Acumatica ERP Instance On the server where the Acumatica ERP Tools are installed, run the Acumatica ERP Configuration Wizard. For example, select Start > Acumatica > Acumatica ERP Configuration. On the Welcome page of the wizard, click Perform Application Maintenance. On the Application Maintenance page, click Instance Info. To Change the Database of an Instance You can change the database of an Acumatica ERP instance for example, if you want to switch to a backup database. To Change the Database of an Instance On the server where Acumatica ERP is installed, run the Acumatica ERP Configuration Wizard. For example, select Start > Acumatica > Acumatica ERP Configuration. On the Welcome page, click Perform Application Maintenance. On the Application Maintenance page, do the following: 4. In the Installed Sites list, click the instance for which you want to specify another database. On the bottom area of the page, click Change Database. On the Database Server Connection page, specify the Microsoft SQL Server that will be used by the Acumatica ERP instance: In the Available Servers list, select a server to connect to. If the server list does not include the server you are looking for, you should click Update the List to rescan your network. The list of database servers may not have a particular server even after your network is rescanned (if, for instance, the server blocks broadcasts). In this case, you can type the name or the address of the Microsoft SQL Server machine in the Server Name box. If the problem persists, contact your network administrator for assistance. : If you use Microsoft SQL Server Express, the (local) option will not work even if the database server is running on the same machine. To use the server, start the SQL Browser service first, and then update the list of servers and select your server. Note that Microsoft SQL Server Express should not be used in a production environment due to its limitations. Select the authentication method to be used to connect to the database server. If you select the SQL Server Authentication option, specify an account with sufficient rights for creating the databases or making changes to them. : The selected authentication method must be supported by the database server. Note that by default, Microsoft SQL Server 2005 is installed with Windows authentication disabled.

51 Maintaining Acumatica ERP 51 Windows authentication works only for a local Microsoft SQL Server or when both application and database servers are members of the same Windows domain. 5. Click Next. 6. On the Database Configuration page, select the appropriate option as follows: To create a new database, click Create a new database, and then type the name of the database. To connect to an existing database, do the following: Click Connect to an existing database. In the Available databases on server list, click a database name. Depending on the schema of the database you have selected, select the relevant check box to update, repair, or set up the database. 4. To shrink data after the database maintenance, select the Shrink data check box. 7. Click Next. 8. On the Company Setup page, make any necessary changes to the list of companies. For more information, see Managing Companies. 9. Click Next. 10. Optional: On the Tables Configuration page (which is displayed only if you have selected the Advanced Settings check box on the Company Setup page), specify whether you want the database tables to be shared by different companies, and then click Next. : Table configuration is a dangerous operation that can result in database corruption. Any changes you make are at your own risk. If you configure tables, be sure to first back up the database. 1 On the Database Connection page, specify the authentication method that this application instance of Acumatica ERP will use to connect to the database, which is one of the following options: Windows Authentication: The Acumatica ERP Configuration Wizard will use the default anonymous user account used by Internet Information Services (IIS). SQL Server Authentication: Select Create new login to create a new login with read, write, execute, and ddl_admin rights, or select Use existing login and specify an existing login with read, write, execute, and ddl_admin rights. 1 Click Next. 1 On the Confirm Configuration page, do the following: Check the configuration settings you have specified. Optional. To make any changes, click Back to return to the required wizard page, and then make necessary changes. c. If you want to save the configuration settings in an XML file on your computer, click Save Configuration. d. Click Finish to deploy the Acumatica ERP instance. To Perform Database Maintenance You can create a new Acumatica ERP database, upgrade an existing database with a current version of the database schema, repair the database schema, and set up companies. To perform these tasks,

52 Maintaining Acumatica ERP 52 you use the Perform Database Maintenance option on the Welcome page of the Acumatica ERP Configuration Wizard. To Perform Database Maintenance Run the Acumatica ERP Configuration Wizard. For example, select Start > Acumatica > Acumatica ERP Configuration. On the Welcome page, click Perform Database Maintenance. On the Database Server Connection page, specify the Microsoft SQL Server that will be used by the Acumatica ERP instance: In the Available Servers list, select a server to connect to. If the server list does not include the server you are looking for, you should click Update the List to rescan your network. The list of database servers may not have a particular server even after your network is rescanned (if, for instance, the server blocks broadcasts). In this case, you can type the name or the address of the Microsoft SQL Server machine in the Server Name box. If the problem persists, contact your network administrator for assistance. : If you use Microsoft SQL Server Express, the (local) option will not work even if the database server is running on the same machine. To use the server, start the SQL Browser service first, and then update the list of servers and select your server. Note that Microsoft SQL Server Express should not be used in a production environment due to its limitations. Select the authentication method to be used to connect to the database server. If you select the SQL Server Authentication option, specify an account with sufficient rights for creating the databases or making changes to them. : The selected authentication method must be supported by the database server. Note that by default, Microsoft SQL Server 2005 is installed with Windows authentication disabled. Windows authentication works only for a local Microsoft SQL Server or when both application and database servers are members of the same Windows domain. 4. Click Next. 5. On the Database Configuration page, select the appropriate options as follows: To create a new database, click Create a new database and then type the name of the new database. To connect to an existing database, do the following: Click Connect to an existing database. In the Available databases on server list, select a database. Depending on the schema of the database you have selected, select the relevant check box to update, repair, or set up the database, if required. 4. If you want to shrink data after the database maintenance, select the Shrink data check box. 6. Click Next. 7. On the Company Setup page, configure companies. For more information, see Managing Companies. 8. Click Next.

53 Maintaining Acumatica ERP Optional: On the Table Configuration page (which is displayed only if you have selected the Advanced Settings check box on the Company Setup page), specify whether you want the database tables to be shared by different companies, and then click Next. : Table configuration is a dangerous operation that can result in database corruption. Any changes you make are at your own risk. If you configure tables, be sure to first back up the database. 10. On the Confirm Configuration page, do the following: Check the configuration settings you have specified. Optional. To make any changes, click Back to return to the required wizard page, and then make necessary changes. c. If you want to save the configuration settings in an XML file on your computer, click Save Configuration. d. Click Finish to perform database maintenance. To Configure the Session Time-Out You can configure the session time-out value for your Acumatica ERP website. To change the timeout value, you change the session time-out and cookie time-out values in the weconfig file of the application instance website. Also, you must make sure that the Application Pool Idle Time-out value in the Internet Information Services (IIS) Manager is greater than the session time-out and cookie timeout values for your website. This step is required, because IIS can recycle the application pool before the session has expired. : Make sure that all users of your website are warned about the site restart so that they can save all documents. To Configure the Session Time-Out Open the weconfig file for the instance. Usually it can be located in %Program Files% \Acumatica ERP\<instance name>, where <instance name> is the name of the application instance website. Change the session time-out to the appropriate value (in minutes), as shown below. <sessionstate timeout="90"> : By default, the session time-out is set to 60 minutes. Change the cookie time-out to the appropriate value (in minutes), as shown in the following code line. <formsauth loginurl="frames/login.aspx" timeout="90" /> : By default, the cookie time-out is set to 60 minutes. 4. Save the weconfig file, which automatically restarts the website. 5. Select Start > Administrative Tools > Internet Information Services (IIS) Manager. 6. In the Connections pane, double-click the site name and then select Application Pools. 7. On the feature page, select the application pool that you use on your website. 8. In the Actions pane, click Advanced Settings.

54 Maintaining Acumatica ERP In the Advanced Settings dialog box, in the Idle Time-out (minutes) box, set the Application Pool Idle Time-out value (in minutes) so that this value is greater than the session and cookie time-out values that you set in Steps 2 and 10. Click OK to save the settings. To Configure the Report Time-Out When you have to run a report that takes a long time to complete (for example, a General Ledger report that covers multiple periods), the report can time out before it finishes. To avoid this error, you can increase the report time-out value. By default, the report time-out is set to 300 seconds. : Make sure that all users of your website are warned about the site restart so that they can save all documents. To Configure the Report Time-Out Open the weconfig file for the site instance. Usually it is located in %Program Files% \Acumatica ERP\<instance name>, where <instance name> is the name of the application instance website. In the file, find the following line, where... represents the other parameters, which depend on your website settings. <add name="pxsqldatabaseprovider" type="px.datpxsqldatabaseprovider, PX.Data"... /> Add the reportquerytimeout parameters to the line and specify the report timeout time (in seconds). <add name="pxsqldatabaseprovider" type="px.datpxsqldatabaseprovider, PX.Data"... reportquerytimeout="600" /> 4. Save the weconfig file, which automatically restarts the website. To Configure the Query Time-Out By default, the query time-out is set to 30 seconds. If you need to, you can increase the query timeout. : Make sure that all users of your website are warned about the site restart so that they can save all documents. To Configure the Query Time-Out Open the weconfig file for the site instance. Usually it is located in %Program Files% \Acumatica ERP\<instance name>, where <instance name> is the name of the application instance website. In the file, find the following line, where... represents the other parameters, which depend on your website settings. <add name="pxsqldatabaseprovider" type="px.datpxsqldatabaseprovider, PX.Data"... /> Add the querytimeout parameter to the line and specify the query timeout time (in seconds). <add name="pxsqldatabaseprovider" type="px.datpxsqldatabaseprovider,

55 Maintaining Acumatica ERP 55 PX.Data"... querytimeout="100" /> 4. Save the weconfig file, which automatically restarts the website. To Select Roles That Will Have Administrative Privileges In Acumatica ERP, the Administrator role has administrative privileges. For your instance, you can change the default settings and assign administrative privileges to one role or multiple roles whenever you need to. Prerequisites Configure the roles to which you want to give administrator privileges in your instance. For more information on role configuration, see Managing User Access Rights. To Select a Role or Multiple Roles That Will Have Administrative Privileges : Make sure that all users of your website are warned about the site restart so that they can save all documents. Open the weconfig file for the site instance. Usually it is located in %Program Files% \Acumatica ERP\<instance name>, where <instance name> is the name of the application instance website. In the file, find the Providers section in pxaccess, which has the following settings. <providers> <remove name="pxdatabaseaccessprovider" /> <add name="pxdatabaseaccessprovider" type="px.datpxdbfeatureaccessprovider, PX.Data" applicationname="/" administratorrole="administrator" /> </providers> The administratorrole="<role>" parameter defines which roles have the administrator privileges. List the roles you want to have the administrative privileges in the administratorrole parameter, as shown below. administratorrole="<roles>" Where Roles is the comma-separated (without spaces) list of roles to which you want to grant administrative privileges. 4. Save the weconfig file, which automatically restarts the website. To Shorten the Names of the Customization Folders In Acumatica ERP, the names of the Validation and Website customization folders start with the name of the application instance website. For example, a path to the Website folder of the InstanceName instance may be as follows. C:\Program Files (x86)\acumatica ERP\Customization\InstanceName\ InstanceNameValidation\InstanceNameWebsite Because the Customization folder includes the folder with the instance name, you can configure the system to shorten the names of the Validation and Website folders by excluding the <instance_name>

56 Maintaining Acumatica ERP 56 prefix, that is, the name of the application instance website. The paths to the Validation and Website folders remain unique. To Shorten the Names of the Customization Folders : Make sure that all users of your website are warned about the site restart so that they can save all documents. Open the weconfig file for the site instance. Usually it is located in %Program Files %\Acumatica ERP\<instance_name>, where <instance_name> is the name of the application instance website. In the file, add the following sections. <add key="cstsolutionname" value="solutiondev"/> <add key="cstwebsitename" value="dev"/> Save the weconfig file, which causes the website to automatically restart. To Turn On Reminders In Acumatica ERP, you can use reminders to draw users' attention to upcoming tasks and events. By default, these reminders are turned off. For more information about reminders, see Managing Your Tasks and Events. : After you save changes to the weconfig file, the website is automatically restarted. Make sure that all users are warned about the restart so that they can save their documents in advance. To Turn On Reminders Open the weconfig file for the site instance. Usually it is located in %Program Files% \Acumatica ERP\<instance name>, where <instance name> is the name of the application instance website. In the file, find the Reminder section, which has the following settings. <add key="remindervisible" value="false" /> <add key="reminderrequestperiod" value="60" /> <add key="reminderactivemode" value="false" /> 4. Change the following key values: ReminderVisible to true ReminderActiveMode to true Save the weconfig file, which automatically restarts the website. Post-requisites After you turn on the reminders, you should configure access to the Reminder Dialog Box form for roles whose users use reminders. For more information on roles configuration, see Access Rights for Roles. To Turn On the My Tasks and Events Button In Acumatica ERP, you can use My Tasks and Events menu in the top right corner of the screen to draw users' attention to their tasks and events and to quickly navigate to the task or event in question. By default, this menu is hidden. For more information, see Info Area in the Acumatica ERP Interface Guide.

57 Maintaining Acumatica ERP 57 : After you save changes to the weconfig file, the website is automatically restarted. Make sure that all users are warned about the restart so that they can save their documents in advance. To Turn On Reminders Open the weconfig file for the site instance. Usually it is located in %Program Files% \Acumatica ERP\<instance name>, where <instance name> is the name of the application instance website. In the file, find the following section. <add key="activitytotalsvisible" value="false" /> Change the ActivityTotalsVisible key value to true. 4. Save the weconfig file, which automatically restarts the website. To Enable Push Notifications Acumatica ERP can send push notifications that make it possible for the external applications to track the changes in the data in Acumatica ERP. For more information on push notifications, see Configuring Push Notifications. If you have installed a new version of Acumatica ERP or updated your Acumatica ERP instance by using the Acumatica ERP Configuration Wizard, the push notifications are enabled in Acumatica ERP automatically. You can configure the notifications on the Push Notifications (SM302000) form, as described in To Configure Push Notifications in the User Guide. If you have updated your Acumatica ERP instance through the web interface, before configuring push notifications, you need to manually enable push notifications in Acumatica ERP, as described in To Enable Push Notifications Manually in this topic. If you need to enable push notifications on the Acumatica ERP instances in a cluster, you should follow the instructions in To Enable Push Notifications in a Cluster in this topic. To Enable Push Notifications Manually Install Microsoft Message Queuing (MSMQ) on the Acumatica ERP server. For instructions, see the Microsoft documentation. Open the weconfig file for the site instance. Usually this file is located in %Program Files %\Acumatica ERP\<instance name>, where <instance name> is the name of the application instance website. In the appsettings section of the weconfig file, set the EnablePushNotifications key to true. 4. Save the weconfig file, which automatically restarts the website. To Enable Push Notifications in a Cluster For each Acumatica ERP instance in the cluster, make sure the instance has push notifications enabled. (Push notifications are enabled if you can open the Push Notifications (SM302000) form in the instance.) If necessary, enable the notifications manually, as described in To Enable Push Notifications Manually. Create a private queue of the Microsoft Message Queuing (MSMQ) service. In the properties of the queue, configure the access permissions so that the Acumatica ERP instances can send messages to the queue. For information on how to perform these tasks, see the Microsoft documentation.

58 Maintaining Acumatica ERP 58 For the Acumatica ERP instance that you want to dispatch the notifications, do the following: Open the weconfig file for the site instance. Usually this file is located in %Program Files%\Acumatica ERP\<instance name>, where <instance name> is the name of the application instance website. In the primaryqueuesettings section of the weconfig file, specify the following values for the attributes of the primaryqueue section: url: The address of a local or remote private MSMQ queue in the following format: <ComputerName>\private$\<QueueName>, where <ComputerName> is the name of the computer, and <QueueName> is the name of the queue. For example, the following address specifies the QueueForPushNotifications queue on the MyComputer computer: MyComputer\private$ \QueueForPushNotificatons. This queue is used as the internal queue of push notifications in Acumatica ERP. enabledispatcher: true. The following fragment of the weconfig file shows an example of the configuration of the primaryqueuesettings section for the dispatcher instance. <primaryqueuesettings> <primaryqueue url="mycomputer\private$\queueforpushnotificatons" enabledispatcher="true"/> </primaryqueuesettings> c. 4. Save the weconfig file, which automatically restarts the website. For all the other Acumatica ERP instances in the cluster, do the following: Open the weconfig file for the site instance. Usually this file is located in %Program Files%\Acumatica ERP\<instance name>, where <instance name> is the name of the application instance website. In the primaryqueuesettings section of the weconfig file, specify the following values for the attributes of the primaryqueue section: url: The same address of the MSMQ queue that you specified for the dispatcher instance enabledispatcher: false The following fragment of the weconfig file shows an example of configuration of the primaryqueuesettings section for the instances other than the dispatcher instance. <primaryqueuesettings> <primaryqueue url="mycomputer\private$\queueforpushnotificatons" enabledispatcher="false"/> </primaryqueuesettings> c. Save the weconfig, which automatically restarts the website.

59 Maintaining Acumatica Framework 59 Maintaining Acumatica Framework Maintenance of the Acumatica Framework application instance site and database is similar to maintenance of the Acumatica ERP application instance. Follow the procedures described in Maintaining Acumatica ERP to perform maintenance tasks that are associated with application instances of Acumatica Framework and their databases.

60 Managing Companies 60 Managing Companies Acumatica ERP is an application with multi-tenancy architecture, in which a single instance of an application can serve multiple tenants. Each such tenant is a separate company. By running one instance of the application with one instance of a database, you can give multiple companies web access to the same database. You can manage companies locally or by using the web interface. Managing Companies Locally By using the Company Setup page of the Acumatica ERP Configuration Wizard, you can do the following: Add a new company to the selected instance. For more information, see To Add a New Company. Delete an existing company. For details, see To Delete an Existing Company. Managing Companies by Using the Web Interface You can create new companies directly from the Acumatica ERP application without using the Acumatica ERP Configuration Wizard. For more information, see Management Overview. Managing Multi-Company Instances Multiple companies can use the same application instance with completely isolated dat The application looks identical to all tenants, but each company has exclusive access to only its dat For more information, see Multi-Company Instances. Multi-Company Instances Multiple companies or tenants can work on the same application instance with completely isolated dat The application looks identical to all tenants, but each company has exclusive access to only its dat When you deploy the Acumatica ERP instance, you create at least one tenant company. You can create more companies with the help of the Acumatica ERP Configuration Wizard or directly from the Acumatica ERP application by using the Companies (SM203520) form. The System Company When you install Acumatica ERP, the System company (with Company ID = 1) is always created automatically. This company contains the predefined system data, such as preconfigured roles and numbering sequences, as well as wiki-based documentation. The system data is used by all tenants of the same application instance. By default, the System company is hidden. All other user-created companies inherit the initial configuration and system data (predefined data) from the System company. That is, all the data available in System is visible to other companies in the same database. An application update or upgrade replaces all the data available in the System company. The data created by users in user-created companies remains unchanged. Parent and Child Companies If you would like to replace the preconfigured data, such as roles and numbering sequences, similarly for multiple new companies, you can create a parent company that will serve as a system company for your new companies.

61 Managing Companies 61 To configure a custom parent company, create a new company and provide a name that clearly indicates how this company will be used for example, Parent This company inherits all the data from the System company. In the Parent company, override the preconfigured settings as needed and specify other configuration settings to be used in all the new companies. Then, when you create a new company by using the Acumatica ERP Configuration Wizard, you specify Parent1 as the new company's parent company; the new company will inherit all the data from the Parent company rather than from the System company. You can create a virtually unlimited number of parent companies; a parent company can be a child of another parent company. Users won't be able to sign in to a parent company. You can create new companies based on the parent company only by using the Acumatica ERP Configuration Wizard. You can create a virtually unlimited number of child companies, which cannot be parents to any other company. Users can sign in to a child company. Data Sharing Between Companies Acumatica ERP provides shared data access in a multi-tenant configuration. You can set up the data sharing mode for all companies on a per-table basis and the mode is applied to every company immediately. : Table configuration is a dangerous operation that can result in database corruption. Any changes you make are at your own risk. If you configure tables, be sure to first back up the database. You can select one of the available data sharing modes: Split, Shared, or Separate. Signing in to a Specific Company In a multi-company Acumatica ERP instance, the Company box appears on Welcome screen by default. Thus, the users can select the company to sign in to from the list of all available companies. If you want to restrict the list of companies a user can see only to the companies the user has access to, select the Secure Company on Login Screen check box on the Company Setup page. In this case, the Company box does not appear on the Welcome screen by default and all users first authenticate themselves by entering their login and password. Depending on the user, one of the following occurs: A user who has access to only one company will be automatically signed in to this company after entering the login and password. A user who has access to multiple companies and has the same credentials in these companies must select a company in the Company box, which appears after the user has been authenticated and contains the list of companies available for the user. A user who has access to multiple companies and has different credentials for different companies is signed in to the company whose credentials the user entered on the Welcome screen. A user who has access to multiple companies and logs in to Acumatica ERP instance using single sign-on with an external identity provider, is signed in to the first company with enabled single sign-on. To Add a New Company You can add a virtually unlimited number of companies to an application instance. To Add a New Company Run the Acumatica ERP Configuration Wizard on the server where Acumatica ERP is installed. For example, select Start > Acumatica > Acumatica ERP Configuration. On the Welcome page, click Perform Application Maintenance.

62 Managing Companies 62 On the Application Maintenance page, do the following: In the Installed Sites list, select the appropriate Acumatica ERP instance. Click Company Maintenance. 4. In the SQL Server Authentication dialog box, select the authentication method to be used to connect to the database. 5. Click OK. 6. On the Company Setup page, click New to add a new company. A new row is appended to the table with the New check box selected. 7. To rename the company, double-click the company name in the Login Company Name column, type a new company name, and press Enter. : This name is used only when there are multiple companies; otherwise, the Logon screen will not have an option to select a company. 8. If you want to fill the database with demo data or template data, select Demo or Template in the Insert Data column. 9. Optional: For each company, specify the following: Visible: Select this check box to have this company displayed on the logon screen. Parent Company ID: Select the ID of the company you want to use as the parent for this company. The following view-only parameters are also displayed for each company: ID: The numerical identifier of the company. New: A check box that, if selected, indicates that this company is newly created and has not been deployed yet. If the check box is cleared, the company has been deployed. Additional Info: The company name in the database. If you want to delete a company that you just added (that is, one with the New check box selected), do the following: In the Installed companies list, select the row of the newly added company. Click Delete. 10. Optional: Select the Advanced check box to configure the data sharing mode for the database tables. 1 Optional: On the Tables Configuration page (which the system displays only if you have selected the Advanced Settings check box on the previous page), specify whether you want the database tables to be shared by different companies, and then click Next. : Table configuration is a dangerous operation that can result in database corruption. Any changes you make are at your own risk. If you configure tables, be sure to first back up the database. 1 On the Confirm Configuration page, do the following: Check the configuration settings you have specified. If you want to save the configuration settings in an XML file on your computer, click Save Configuration. c. Click Finish to deploy the new company.

63 Managing Companies 63 To Delete an Existing Company If you need to delete an existing company by using the Acumatica ERP Configuration Wizard, you open the instance for company maintenance and delete the company in advanced mode. : Because any company you see on the Company Setup page can be a live company, you may want to create backups before making any changes. To Delete an Existing Company Run the Acumatica ERP Configuration Wizard on the server where Acumatica ERP is installed. For example, select Start > Acumatica > Acumatica ERP Configuration. On the Welcome page, click Perform Application Maintenance. On the Application Maintenance page, do the following: In the Installed sites list, click the appropriate Acumatica ERP instance. In the bottom area of the page, click Company Maintenance. 4. In the SQL Server Authentication dialog box, select the authentication method to be used to connect to the database, and then click OK. 5. On the Company Setup page, select the company row in the Installed companies list. 6. Click Delete. 7. When you're prompted, click OK to delete the selected company. 8. On the Table Configuration page, check the data sharing modes for the database tables, and then click Next. 9. On the Confirm Configuration page, do the following: Check the configuration settings you have specified. If you want to save the configuration settings in an XML file on your computer, click Save Configuration. c. Click Finish to delete the company.

64 Updating Acumatica ERP 64 Updating Acumatica ERP Updates for Acumatica ERP provide functional enhancements and new functionality. You need to use an installation package to update your Acumatica ERP instances. In this topic, you will read about the ways to update Acumatica ERP and the schedule for locking out the system during the time of update. Updating Acumatica ERP You can update your instance of Acumatica ERP to a new product version or build in one of the following ways: By using the Acumatica ERP web interface By using the Acumatica ERP Configuration Wizard The easiest way of updating Acumatica ERP is by using the web interface. : If you have deployed your instance on Windows Azure, you won't be able to update this instance though the web interface. You must instead use the procedures described in Updating Your Acumatica ERP Service on Windows Azure. If a server with Acumatica ERP is connected to the Internet, the system can download installation packages directly from the Acumatica ERP update server during installation. If the server is not connected to the Internet, you can download the update package from another computer, upload the package to Acumatica ERP, and install it by using the web interface. For more information, see Updating Acumatica ERP by Using the Web Interface. Alternatively, you can update Acumatica ERP by using the Configuration Wizard if you cannot update it by using the web interface (for example, for security reasons). For details, see Updating Acumatica ERP by Using the Configuration Wizard. You can forbid the users of your Acumatica ERP instance to update the system by using the web interface. This might be useful, for example, when you want to avoid an unwanted update of a large database on Amazon Web Services. To prevent users from updating the system through the web interface, you set the RestrictUpdates parameter value to True in the appsettings section of the weconfig file. With this setting, a message conveying this restriction appears on the Apply Updates (SM203510) form, all update actions on this form are blocked, and you can update Acumatica ERP by using the Configuration Wizard only. : The system deletes all custom files from the Acumatica ERP site folders during an update. You can keep custom files in the Bin folder by doing one of the following: Including all custom files in a customization package and publishing this customization package on the site Adding the file names to the file with the.preserve extension in the same folder Scheduling the Lockout of the System We recommend that you switch on maintenance mode when you are updating the system. In this mode, users cannot access the system and process documents; therefore, it is safe to apply updates. To switch on maintenance mode, you schedule the system lockout by using the Apply Updates form, specifying when the system will be unavailable. When the lockout is in effect, non-administrative users will see a message on the Welcome page indicating that the site is under maintenance. After finishing the update, you must manually switch off maintenance mode (that is, unlock the system) on the Apply Updates form.

65 Updating Acumatica ERP 65 : When the lockout is in effect the following happens in the system: Only users that have the Administrator role can sign in to the system The system stops all processes that were run by schedule For details, see To Schedule the System Lockout and To Unlock an Acumatica ERP Instance. Updating Acumatica ERP by Using the Web Interface You can use the Acumatica ERP web interface to remotely update Acumatica ERP (which is installed on the premises of your organization or on Amazon EC2) to a newer version or build. : If you have deployed your instance on Windows Azure, you won't be able to update this instance though the web interface. You must instead use the procedures described in Updating Your Acumatica ERP Service on Windows Azure. In this topic, you will find an upgrade policy, a description of the update process when you use the web interface and recommended update preferences. Upgrade Policy On the Apply Updates (SM203510) form, only minor updates for your current version of Acumatica ERP are available. You should upgrade your Acumatica ERP from previous versions of the system to Version 2017 R2 manually on the server (upgrade by using the web interface is not supported due to significant changes in customizations). For details, see Updating Acumatica ERP by Using the Configuration Wizard. Before You Proceed We strongly recommend that before you update Acumatica ERP to a newer product version, you do the following: Back up all configuration files and databases used by the application instances. If you have created any custom views with the SCHEMABINDING clause in the Acumatica ERP database, remove them. (You can create these views anew after update.) If you have been replicating the Acumatica ERP database, turn off the replication. (Otherwise, the system cannot be updated.) If you developed a client application by using the screen-based SOAP API, follow the procedure described in To Update a Client Application that Uses Screen-Based Web Services to prevent a failure of your application that can happen because of the UI changes in the system. On the Automation Schedules (SM205030) form, make sure that no processes are scheduled for the update time. If you find any scheduled processes reschedule them so that they start after the update. On the Companies (SM203520) form, click Optimize Database to check your Acumatica ERP database for orphaned snapshots and delete them if the system finds any orphaned snapshots. Overview of the Update Process When you update Acumatica ERP by using the web interface, both the site and the database of the application are updated at the same time. To update Acumatica ERP by using the web interface, you will perform the following steps: If necessary, notify users about the upcoming update and automatically lock out the system at the time of update, as described in To Schedule the System Lockout.

66 Updating Acumatica ERP 66 If you want to upload a custom installation package (which was released especially for your organization) with an update from a local computer, on the Apply Updates (SM203510) form, click Upload Custom Package and select the custom package file. Update the instance by using the Apply Updates form, as described in To Update Acumatica ERP by Using the Web Interface. 4. If you are upgrading your system from a version that did not include the search indexes, build the search indexes. For details, see To Build Search Indexes in the Acumatica ERP User Guide. 5. If you have locked out the system, unlock the system, as described in To Unlock an Acumatica ERP Instance. Configuration of Update Preferences If a server with Acumatica ERP is connected to the Internet, the system can download installation packages directly from the Acumatica ERP update server during installation. To make the system download installation packages from the update server and to display the most recent information about Acumatica ERP updates, you need to do the following on the Update Preferences (SM203505) form: Select the Use Update Server check box to download installation packages directly from the Acumatica ERP update server. Select the Check for Updates check box to automatically check for new updates. When a new product update (a major version or a build) has been approved and released by the Acumatica Quality Assurance team, a notification appears in the About Acumatica dialog box. (To open this dialog box, sign in to the system, and on the form toolbar, click About on the Help menu.) Updating Acumatica ERP by Using the Configuration Wizard If you have the installation package file available on your computer, you can update Acumatica ERP locally on the server where the previous version of the system is installed. You can also use this method of updating if for some reason you cannot use the Acumatica ERP web interface to update the application. You perform the update procedure on the server where the current version of the Acumatica ERP Tools is installed. : To run the installation package, you must have the Administrator role on your local computer. In this topic, you can find a brief description of the update process on a local server and on Microsoft Azure. Before You Proceed We strongly recommend that before you update Acumatica ERP to a newer product version, you do the following: Back up all configuration files and databases used by the application instances. If you have created any custom views with the SCHEMABINDING clause in the Acumatica ERP database, remove them. (You can create these views anew after update.) If you have been replicating the Acumatica ERP database, turn off the replication. (Otherwise, the system cannot be updated.) If you developed a client application by using the screen-based SOAP API, follow the procedure described in To Update a Client Application that Uses Screen-Based Web Services to prevent a failure of your application that can happen because of the UI changes in the system.

67 Updating Acumatica ERP 67 On the Automation Schedules (SM205030) form, make sure that no processes are scheduled for the update time. If you find any scheduled processes reschedule them so that they start after the update. On the Companies (SM203520) form, click Optimize Database to check your Acumatica ERP database for orphaned snapshots and delete them if the system finds any orphaned snapshots. Overview of the Update Process on a Local Server To update Acumatica ERP locally, perform the following steps: If necessary, notify users about the upcoming update, and automatically lock out the system for the time of update, as described in To Schedule the System Lockout. Use the installation package file available on your computer to update the Acumatica ERP Tools. For details, see To Update the Acumatica ERP Tools. Start updating the database and the site of your application instance. The system will automatically perform the following actions: For instances that contain published customization projects, validate the compatibility of the currently published customization code with the code of the new product version. Update the database of the instance. c. Update the site of the instance. For details, see To Update the Database and Site of an Acumatica ERP Instance. If you need to update the database without updating the site or to update the site without updating the database, see Divided Update of the Database and the Site. : We strongly recommend that you use the common procedure described in this step for a usual update of your Acumatica ERP instance. 4. If you are upgrading your system from a version that did not include the search indexes, build the search indexes. For details, see To Build Search Indexes in the Acumatica ERP User Guide. 5. If you locked out the system, unlock the system, as described in To Unlock an Acumatica ERP Instance. Divided Update of the Database and the Site If (for strong reasons) you need to update the Acumatica ERP database without updating the site, to update the site without updating the database, or to consequently update the database and the site, you can use the Update only Website and Update only Database commands, which you can find in the drop-down list to the right of the Upgrade button in the Application Maintenance page of the Acumatica ERP Configuration Wizard. For details, see To Update the Database of an Acumatica ERP Instance and To Update the Site of an Acumatica ERP Instance. : When you update your Acumatica ERP instance by using the Update only Website or Update only Database commands, the system does not validate the customization compatibility. If you have published customization in your Acumatica ERP instance, the instance may stop working after update due to incompatible customization code. Updating Your Acumatica ERP Service on Windows Azure If you have deployed your Acumatica ERP Service on Windows Azure and want to update this service with a new installation package, you need to do this on the Windows Azure portal. In this topic, you will find an overview of the update process on the Windows Azure portal.

68 Updating Acumatica ERP 68 : If you change the Windows Azure deployment size (for example, when you extend your subscription from Small to Medium), you also need to update your Acumatica ERP Service by using the steps described in this topic. The Update Process on Windows Azure To update your Acumatica ERP Service that was deployed on Windows Azure, you need to perform the following steps: Download the service package file of the Acumatica ERP version to which you want to update your Acumatica ERP Service, as described in To Download the Configuration Package. Download the configuration file of your Acumatica ERP Service, as described in To Download the Acumatica ERP Service Configuration File. If necessary, notify users about the upcoming update, and automatically lock out the system for the time of update, as described in To Schedule the System Lockout. 4. Update your Acumatica ERP Service on Windows Azure, as described in To Update Your Acumatica ERP Service on Windows Azure. 5. If you are updating your system from a version that did not include the search indexes, build the search indexes. For details, see To Build Search Indexes in the Acumatica ERP User Guide. 6. If you locked out the system, unlock the system, as described in To Unlock an Acumatica ERP Instance. To Schedule the System Lockout To notify users about the upcoming update and automatically lock out the system at the time, you can schedule a lockout by using the Apply Updates (SM203510) form. A message alerting users to the system lockout will be displayed on the Welcome screen. : When the lockout is in effect the following happens in the system: Only users that have the Administrator role can sign in to the system The system stops all processes that were run by schedule To Schedule the System Lockout If you are not already signed in to the system, sign in to Acumatica ERP. Navigate to System > Management > Process > Apply Updates. On the form toolbar, click Schedule Lockout. 4. In the Schedule Lockout dialog box, specify the date and time when the system will be locked out and the reason for the lockout. : If you want to update the system immediately, specify the current date and time. 5. If you want to lock out only the current site (but not all sites that use the same database) clear the Lock Out All Sites check box. 6. Click OK to lock out the system at the specified time.

69 Updating Acumatica ERP 69 To Update Acumatica ERP by Using the Web Interface To update an Acumatica ERP instance by using the web interface, you use the Apply Updates (SM203510) form. For more information, see Updating Acumatica ERP by Using the Web Interface. To Update an Acumatica ERP Instance by Using the Web Interface If you are not already signed in to the system, sign in to Acumatica ERP. Navigate to System > Management > Process > Apply Updates. Install the new product version. On the Updates tab, do the following: In the Major Version box, select the product version to which you want to update your Acumatica ERP instance. In the table of available updates, select the latest product build of the selected version, and then click Download Package in the table toolbar. When the download is complete, the Ready to Install check box is automatically selected. c. If you have published customization projects in your Acumatica ERP instance, in the table toolbar, click Validate Customization to start the process of validating the compatibility of the currently published customization code with the code of the selected product version. For details, see To Validate the Compatibility of the Published Customization with a New Version Before an Upgrade. d. If the validation has succeeded, in the table toolbar, click Install Update. A background process starts that copies Acumatica ERP software components to the server computer and then updates the application instances and databases. If you locked the instance before the update, you should unlock the instance, as described in To Unlock an Acumatica ERP Instance. To Update the Acumatica ERP Tools You perform the update procedure on the server where the current version of the Acumatica ERP Tools is installed. For an overview of the update procedure, see Updating Acumatica ERP by Using the Configuration Wizard. : To run the installation package, you must have the Administrator role on the local computer. To Update the Acumatica ERP Tools If necessary, back up the configuration files and databases maintained by the application instances. Run the latest version of the installation package, and follow the procedure for installing Acumatica ERP Tools. For more information, see To Install the Acumatica ERP Tools. To Update the Database and Site of an Acumatica ERP Instance After you have updated the Acumatica ERP Tools, you need to update the database and the site of your Acumatica ERP instance. For an overview of the update procedure, see Updating Acumatica ERP by Using the Configuration Wizard.

70 Updating Acumatica ERP 70 To Update the Database and Site of an Acumatica ERP Instance Run the Acumatica ERP Configuration Wizard on the server where the Acumatica ERP Tools are installed. On the Welcome page, click Perform Application Maintenance. On the Application Maintenance page, do the following: In the Installed Sites list, click the Acumatica ERP instance whose version you want to update. You can see the current versions in the Site Version and DB Version boxes. Click Upgrade. 4. When you're prompted, click Yes to continue the update. 5. In the SQL Server Authentication dialog box, do the following: Select the authentication method to be used to connect to the database. If you have selected the SQL Server Authentication option, specify an account that has sufficient rights to make changes to the database. c. If you want to shrink data after the database maintenance, select the Shrink data check box. d. Click OK to start the update. For instances that contain published customization projects, the system first validates the compatibility of the currently published customization code with the code of the selected product version. If the validation is successful, the system updates the database and the site. If the validation fails, the Validation Failed window opens to display the list of the executed checks and the discovered errors, and the update process is interrupted. To resolve any issues that were discovered, see To Resolve an Issue Discovered During the Validation. The time required for the update depends on the performance of your database server, the differences between the old and current versions of the database schema, the hardware configuration of the server, and the current system load. When the update of the instance is finished, the Acumatica ERP Configuration Wizard updates the list of instances. To Update the Database of an Acumatica ERP Instance You update the databases after you update the Acumatica ERP Tools. : You must update the application instances as well. To Update the Database of an Application Instance Run the Acumatica ERP Configuration Wizard on the server where Acumatica ERP is installed. For example, select Start > Acumatica > Acumatica ERP Configuration. On the Welcome page, click Perform Application Maintenance. On the Application Maintenance page, do the following: 4. In the Installed Sites list, click the Acumatica ERP instance whose database you want to update. You can see the current version in the DB Version box. In the drop-down menu next to the Upgrade button, select Update only Database. When you are prompted, click Yes to continue the update.

71 Updating Acumatica ERP In the SQL Server Authentication dialog box, specify the authentication method to be used to connect to the database. If you select the SQL Server Authentication option, specify an account that has sufficient rights to make changes to the databases. 6. If you want to shrink data after the database maintenance, select the Shrink data check box. 7. Click OK. The time required for the update depends upon your database server performance and the differences between the old and current versions of the database schem After you have updated the database you should update the site, as described in To Update the Site of an Acumatica ERP Instance. To Update the Site of an Acumatica ERP Instance You update an application instance after you update the Acumatica ERP Tools. : You must update the database of the application instance as well. For details, see To Update the Database of an Acumatica ERP Instance. To Update the Site of an Acumatica ERP Instance Run the Acumatica ERP Configuration Wizard on the server where the Acumatica ERP Tools are installed. On the Welcome page, click Perform Application Maintenance. On the Application Maintenance page, do the following: 4. In the Installed Sites list, click the Acumatica ERP instance whose version you want to update. You can see the current version in the Site Version box. In the drop-down menu next to the Upgrade button, select Upgrade only Site. When you're prompted, click Yes to continue the update. The update process takes a few minutes, depending on the hardware configuration and the current system load. When the update of the instance is finished, the Acumatica ERP Configuration Wizard updates the list of instances. To Download the Acumatica ERP Service Configuration File Before you update your Acumatica ERP Service deployed on Windows Azure, you should download the configuration file (*.cscfg) that you will use for update, as described in this topic. To Download the Acumatica ERP Service Configuration File Sign in to the Windows Azure portal. On the left pane, click Cloud Services (classic). In the Cloud Services (classic) blade, click the name of the Acumatica ERP Service you want to update. 4. In the left part of your Acumatica ERP Service blade, click Configuration. 5. On the Configuration blade toolbar, click Download to download the *.cscfg configuration file (see the following screenshot).

72 Updating Acumatica ERP 72 Figure: Windows Azure portal: Downloading a configuration file After you have downloaded the configuration file for your Acumatica ERP Service, you can start the update procedure. For details, see To Update Your Acumatica ERP Service on Windows Azure. To Update Your Acumatica ERP Service on Windows Azure To update your Acumatica ERP Service deployed on Windows Azure, you need to follow the procedure described in this topic. For the overview of the update procedure, see Updating Your Acumatica ERP Service on Windows Azure. To Update Your Acumatica ERP Service on Windows Azure Sign in to the Windows Azure portal. On the left pane, click Cloud Services (classic). In the Cloud Services (classic) blade, click the name of the Acumatica ERP Service you want to update. 4. On the toolbar of your Acumatica ERP Service blade, click Update (see the following screenshot).

73 Updating Acumatica ERP 73 Figure: Windows Azure portal: Opening the Update you deployment blade 5. In the Update your deployment blade, do the following (see the screenshot below): In the Package box, select the *.cspkg package file that you downloaded from the Partner Portal. In the Configuration box, select the *.cscfg configuration file that you downloaded on the Configuration blade. c. Specify other settings to meet your needs. d. Click OK to start updating the service.

74 Updating Acumatica ERP 74 Figure: Windows Azure portal: Updating your Acumatica ERP Service Uploading the service package file and the service configuration file and updating the service may take several minutes. To Update a Client Application that Uses Screen-Based Web Services To prevent application failures and omit the regeneration of the WSDL description for each change of the user interface of the system, we recommend that you follow the procedure described in this topic before you update your Acumatica ERP instance. To Update a Client Application that Uses Screen-Based Web Services To prevent application failures with the update to a newer version of Acumatica ERP, perform the following steps before you install the update: Create a test copy of your production Acumatica ERP instance. Make changes to your client application, as described in To Use the Screen-Based API Wrapper. Test the client application with the test copy of your Acumatica ERP instance. 4. Update the test copy of your Acumatica ERP instance to a new version of Acumatica ERP. 5. Test the client application with the updated test copy of your Acumatica ERP instance. 6. Update the production instance of Acumatica ERP to the new version.

75 Updating Acumatica ERP 75 : You should distribute the client application along with the XML schema file that is generated by the screen-based API wrapper. For details, see Screen-Based API Wrapper. To Unlock an Acumatica ERP Instance If you have locked your instance before updating Acumatica ERP, you should use the Apply Updates (SM203510) form to unlock the instance after you finish updating it. : When the lockout is in effect the following happens in the system: Only users that have the Administrator role can sign in to the system The system stops all processes that were run by schedule To Unlock an Acumatica ERP Instance If you are not already signed in to the system, sign in to Acumatica ERP. Navigate to System > Management > Process > Apply Updates. On the form toolbar, click Stop Lockout to unlock the system.

76 Troubleshooting Acumatica ERP 76 Troubleshooting Acumatica ERP This chapter explains how you can use various tools and methods to troubleshoot Acumatica ERP, both during installation and later, during production use. In This Chapter Troubleshooting Performance Using Logs Using Profilers Using Built-In Debugging Tools Using Third-Party Tools To Optimize Memory Consumption During Startup Troubleshooting Performance In this topic and the steps within it, you can find a detailed description of the steps you need to perform to resolve performance issues on the client side and, if necessary, to gather information to provide it to the Acumatica support team. Performance issues fall into two broad categories: Overall performance is slow The whole site is slow, and you cannot identify a particular process for which the slowdown occurs. Some process works slowly The site works slowly when a user is working with particular forms or executing specific actions. The category your client s performance issues fall into dictates the steps and substeps you should perform to find the reasons for the performance slowdown and resolve the issue. For each category, the following table shows these steps and substeps; the + symbol indicates that you should perform the step or substep. You can find detailed descriptions of the steps and substeps in the applicable topics. Performance Troubleshooting Overall performance is slow Some process works slowly Step 1: Check the most basic causes Check whether the site is licensed + Skip this substep Check the speed from other browsers + + Check the speed from other locations Check automation schedules Explore the running processes + +

77 Troubleshooting Acumatica ERP 77 Overall performance is slow Some process works slowly 6. Check whether antivirus software is blocking some functionality of the site + Skip this substep Step 2: Investigate application server time and database server time in the Request Profiler + Skip this step Step 3: Check the configuration of the application server + Skip this step Step 4.1: Check the Configuration of Microsoft SQL Server and Run Reports Check the configuration of the database server + + Run performance reports + + Check the SQL Activity Monitor for locks + + Step 4.2: Check the Configuration of MySQL Database Server + + Investigate requests in the Request Profiler + + Collect additional information from the logs + + Use external tools + + Step 6: Submit a case to Acumatica support + + Step 5: Collect more information Step 1: Check the Most Basic Causes To exclude the reasons that lead to performance slowdown most frequently, you should perform the substeps described in the sections that follow. Check Whether the Site Is Licensed The slowdown may be caused by the site not being licensed. Sites in trial mode allow only two concurrent users and limit the usage of hardware resources. If you have already registered the site, it could become unlicensed for the following reasons: A user may be using a URL of an unregistered site for example, if the user is accessing the site through a bookmark with that URL. Some hardware changes have been made to the application server for example, more CPUs have been added, or the application pools have been changed. Perform the following task to check whether the site is licensed. To check whether the site is licensed: Check if the site is licensed in one of the following ways:

78 Troubleshooting Acumatica ERP 78 Make sure there is no message in the bottom of the browser window that says Your product is in the trial mode. Only two concurrent users are allowed. Activate. See the message in the following screenshot. On the Activate License (SM201510) form, check the value of the Status element. An unregistered site has the Invalid status, as shown in the following screenshot. Figure: Invalid license Depending on the results of the previous instruction, do one of the following: If the site is not licensed, activate the license by following the instructions in Licensing and Activating Acumatica ERP. If the site is licensed, continue with the next substep. Check the Speed from Other Browsers Another possible reason for the slowdown is that some properties of the browser may be preventing the site from running faster. Perform the following task to see whether this is the reason for the slowdown. To check the speed from other browsers: Try to access the site from another browser. Depending on the results of the previous instruction, do one of the following: If the issue is reproduced in only one browser, check the version of the browser, and try to reproduce the issue in the latest version of the browser. You can also try to turn off plugins in the browser. Collect more information on the slowdown, and send it to the Acumatica support team, as described in Step 5: Collect More Information and Step 6: Submit a Case to Acumatica Support. If the issue is reproduced in all browsers, continue with the next substep. Check the Speed from Other Locations Some network or internet service provider issues at the user s end may be causing a performance slowdown. Perform the following task to see whether this is the reason for the slowdown. To check the speed from other locations: Try to reproduce the slowdown issue on some computers at a different location.

79 Troubleshooting Acumatica ERP 79 Depending on the results of the previous instruction, do one of the following: If the issue is not reproduced on other computers, the problem is probably in the client s network. Ask the client to check the network settings. If the issue is reproduced on multiple computers, continue with the next substep. 4. Check Automation Schedules Slowdowns may be caused by errors on active schedules, unprocessed s, or insufficient time for a scheduled processes to complete before others begin. Perform the following tasks to check the automation schedules. To look for errors on the active schedules: On the Automation Schedules (SM205030) form, look for errors on the active schedules. (For each schedule, see the Status and the Last Execution Result columns.) Depending on the results of the previous instruction, do one of the following: If you found an error, either correct the error in the scheduled process or deactivate the schedule. If there are no errors in automation schedules, continue with the next task. To check the frequency of schedules: On the Automation Schedules form, make sure there are no schedules starting at the same time or within short intervals. Depending on the results of the previous instruction, do one of the following: If you have found some overlap in the schedules, correct the execution times of any needed schedules. For example, we recommend that you leave at least 5 minutes between Send and Receive schedules, as shown in the following screenshot. Figure: Send and Receive schedule If there is enough time for each process to finish before the start of the next scheduled process, continue with the next task.

80 Troubleshooting Acumatica ERP 80 To look for failed and old unprocessed s: On the All s (CO409070) form, look for failed and old unprocessed s. Depending on the results of the previous instruction, do one of the following: If you have found failed or old unprocessed s, delete them. If there are no failed or unprocessed s, continue with the next substep. 5. Explore the Running Processes The slowdown could be caused by some process that is hung and is running in an endless loop. Perform the following tasks to check the running processes. To Check the Running Processes in Acumatica ERP On the Running Processes (SM201530) form, check the list of all ongoing processes for all users as follows: Look for processes that have been going on for a long time (typically you should look for processes running longer than 30 minutes) to see if the process is hung and running in an endless loop. Depending on the results of the previous instruction, do the following: If some process is hung, select the process and click Abort on the form toolbar to end the process, as shown in the following screenshot. If the situation repeats, collect more information on the slowdown and send it to the Acumatica support team, as described in Step 5: Collect More Information and Step 6: Submit a Case to Acumatica Support. Figure: Abort button If no process is hung, continue with the next task. To check the running processes in the operating system: In Task Manager, review the running processes as follows: Check the memory consumption of the w3wp.exe process. : Acumatica ERP runs under the w3wp.exe process, with the username that is the name of the application pool. Check whether other processes are executed at the same time and review their memory consumption.

81 Troubleshooting Acumatica ERP 81 Depending on the results of the previous, do one of the following: If w3wp.exe is using almost all memory, create a process dump, as described in If your site is completely non-responsive or extremely slow in Step 5. Try to restart the process. If another process takes too much time, either investigate the reasons or end the process. If memory consumption of the w3wp.exe is normal and no other processes are taking too much time or using too much server memory, continue with the next substep. 6. Check Whether Antivirus Software Is Blocking Some Functionality of the Site Some settings of antivirus software could be preventing the site from working normally. Perform the following task to see whether antivirus software is the reason for the slowdown. To check whether the antivirus software is blocking the site: Check the antivirus logs, and try to turn off the antivirus software, if any. Depending on the results of the previous instruction, do one of the following: If the antivirus software is blocking the site, change the antivirus settings. If the antivirus software is not blocking the site, continue with Step 2: Investigate Application Server Time and Database Server Time in the Request Profiler. Step 2: Investigate Application Server Time and Database Server Time in the Request Profiler Either the application server or the database server may be working slowly, causing performance issues. Perform the following task to check the reason for the slowdown by using the Request Profiler, an Acumatica ERP tool. To detect which of the servers works slowly: On the Request Profiler (SM205070) form, start the Request Profiler by clicking Start on the form toolbar. Reproduce the slowdown in the system. Back on the Request Profiler form, click Refresh Results on the form toolbar to upload to this form all the new activities since the last refresh. : You must click Refresh Results to get the new rows in the profiler table. Pressing F5 does not provide the same result Review the values in the Server Time, ms and SQL Time, ms columns of the profiler table: SQL Time is the time taken by SQL Server, in milliseconds. Server Time is the time taken by the request, in milliseconds. To get the time taken by the application server, use the formula Time taken by application server = Server Time SQL Time. Depending on the results of the previous instruction, do one of the following: If the time taken by application server is too long for most of the requests, proceed with Step 3: Check the Configuration of the Application Server. If the time taken by SQL server is too big for most of the requests, proceed with Step 4.1: Check the Configuration of Microsoft SQL Server and Run Reports.

82 Troubleshooting Acumatica ERP 82 Step 3: Check the Configuration of the Application Server Several settings of the application server may be configured incorrectly, leading to the performance slowdown. If correction of the application server settings does not improve the performance, collect more information on the slowdown and send it to the Acumatica support team, as described in Step 5: Collect More Information and Step 6: Submit a Case to Acumatica Support. Perform the following tasks to check the configuration of the application server. To enable dynamic compression: You should enable dynamic content compression, which is disabled by default. The HTTP compression setting on Internet Information Services (IIS) can provide faster transmission times between IIS and the client browser. Click Start > Control Panel > Programs > Turn Windows features on or off. In the Windows Features dialog box, which opens, select the Dynamic Content Compression check box (Internet Information Services > World Wide Web Services > Performance Features), which is shown in the following screenshot. Figure: Dynamic Content Compression option To use a dedicated application pool: All Acumatica ERP instances should use their own application pools, which are not shared with any other applications. When you are creating a new instance in Acumatica ERP Configuration Wizard, you should always use the Create New Application Pool setting, which is shown in the following screenshot.

83 Troubleshooting Acumatica ERP 83 Figure: Create New Application Pool setting You can change the application pool of an already-configured application in Internet Information Services (IIS) Manager as described in cc731755(v=ws.10).aspx. To check the IIS configuration on a 64-bit server: You should make sure the application pool does not enable 32-bit applications on a 64-bit application server, which can slow down the performance of a 64-bit server. In the Connections pane of Internet Information Services (IIS) Manager, click Application Pools. Right-click the needed application pool, and in the pop-up menu, click Advanced Settings. Make sure the Enable 32-Bit Applications setting in the General group is set to False. Step 4.1: Check the Configuration of Microsoft SQL Server and Run Reports To make sure that Microsoft SQL Server works correctly, you should perform the substeps described below. Check the Configuration of the Database Server Settings of Microsoft SQL Server may not be configured properly, leading to the performance slowdown. If correction of Microsoft SQL Server settings does not improve the performance of the site, continue with Run Performance Reports. Perform the following tasks to check Microsoft SQL Server configuration. To ensure that Microsoft SQL Server is not restricted on memory usage: In Microsoft SQL Server Management Studio, right-click the database server instance and select Properties. In the Server Properties dialog box, click Memory. Set the value in the Maximum server memory (in MB) box to 75 to 80 percent of the total physical memory of the server, but leave at least 4 GB available for the operating system. For example, if your server has a total memory of 16 GB, you can set the maximum server memory to 12 GB (which is 75 percent but leaves 4 GB for the operating system). To schedule the weekly maintenance plan: By using the Maintenance Wizard in Microsoft SQL Server Management Studio, schedule the following tasks: Database Integrity Check: Checks the logical and physical integrity of the database Rebuild Index: Helps remove gaps in data pages and eases the data retrieval process

84 Troubleshooting Acumatica ERP 84 Shrink Database: Removes space by moving pages from the end of the file to the front, and then deallocates the excess space back to the file system Update Statistics: Internally updates statistical information about tables and indexes used by SQL Query Optimizer during data retrieval requests You can find more information on creating maintenance plans in library/ms18995aspx. See an example of the schedule of the recommended maintenance plans in the following screenshot. Figure: Weekly maintenance plan Run Performance Reports Some SQL queries consume too many resources. To find out the top resource-consuming SQL queries, you should perform either or both of the following tasks. You should collect data on the resource-consuming SQL queries as quickly as possible after a performance slowdown occurs, because information in such reports is updated frequently during the process of server work. To find out the top resource-consuming SQL queries by using a standard report: In the Object Explorer of Microsoft SQL Server Management Studio, right-click the server instance, and select Reports > Standard Reports > Performance - Top Queries by Average CPU Time. Microsoft SQL Server Management Studio opens the report. Right-click the report, select Export, and select the format of the exported report. Send this report, along with other information on the slowdown, to the Acumatica support team. (See the list of information that you should provide to support in Step 6: Submit a Case to Acumatica Support.) To find out the top resource-consuming SQL queries manually: Perform the following SQL query to get the performance report. By using this report, you get the same information that is provided in the standard report but in a table format, which can be more convenient. Moreover, as a result of this request, you get not only average CPU time (AvgCPU) but also the number of times the process was executed (execution_count).

85 Troubleshooting Acumatica ERP 85 Therefore, you can find out not only which process is taking the longest but also which process is being executed the most. SELECT top 100 total_worker_time AS TotalCPU, total_elapsed_time/execution_count AS AvgDuration, total_elapsed_time AS TotalDuration, (total_logical_reads+total_physical_reads)/execution_count AS AvgReads, (total_logical_reads+total_physical_reads) AS TotalReads, execution_count, SUBSTRING (st.text, (qs.statement_start_offset/2)+1, ( (CASE qs.statement_end_offset WHEN -1 THEN datalength(st.text) ELSE qs.statement_end_offset END - qs.statement_start_offset)/2)+ 1 )AS txt, convert(nvarchar(max),query_plan), CONVERT(int, depvalue) FROM [master].[sys].[dm_exec_query_stats] AS qs WITH (NOLOCK) cross apply [master].[sys].[dm_exec_sql_text](qs.sql_handle) AS st cross apply [master].[sys].[dm_exec_query_plan] (qs.plan_handle) AS qp cross apply [master].[sys].[dm_exec_plan_attributes](qs.plan_handle) depa WHERE (depattribute = 'dbid') ORDER BY 1 DESC; Send the results of the query, along with other information on the slowdown, to the Acumatica support team. (For the list of information that you should provide to support, see Step 6: Submit a Case to Acumatica Support.) Check the SQL Activity Monitor for Locks In the Object Explorer of Microsoft SQL Server Management Studio, right-click the instance name, and then select Activity Monitor. Review the Recent Expensive Queries section. Send the data from the SQL Activity Monitor, along with other information on the slowdown, to the Acumatica support team. (For the list of information that you should provide to support, see Step 6: Submit a Case to Acumatica Support.) Step 4.2: Check the Configuration of MySQL Database Server In this topic, you can find general recommendations for optimal performance of a MySQL database and a list of common problems and solutions. For more detailed information on MySQL settings, see the MySQL Reference Manual. General Recommendations To optimize the performance of a MySQL database, do the following: Back up the database regularly. Change the default values of the parameters in the my.cnf file as follows (for numerical parameters, the minimum recommended values are specified, and you should specify values appropriate to your processing load): max_allowed_packet=10m For this parameter, you specify the maximum size of a file that can be stored in the database. It is important that you limit the file size to prevent the database from becoming overfilled with large files.

86 Troubleshooting Acumatica ERP 86 innodb_buffer_pool_size=256m For this parameter, you specify the size of the buffer pool, which should be 70 to 80 percent of the available RAM. c. innodb_log_file_size=64m For this parameter, you specify the size of the transaction log file for InnoDB. Large InnoDB transaction logs are crucial for good and stable writing performance, but larger log files mean that the recovery process will be slower if a crash occurs. You should find a balance between a reasonable recovery time and high performance in your system. d. innodb_log_buffer_size=16m For this parameter, you specify the size of the buffer for the transaction log. InnoDB writes the changed data records into its log buffer, which is kept in memory. This buffer saves disk input and output operations for large transactions because it is not necessary for InnoDB to write the log of changes to disk before it commits a transaction. e. innodb_flush_method=o_direct For this parameter, you specify the method MySQL uses to flush files from RAM to a hard drive. When you use the O_DIRECT flush method, you avoid double buffering and reduce swap pressure, which improves performance. f. key_buffer_size=64m For this parameter, you specify the amount of RAM you reserve for the database key buffer. This parameter is very important if you use MyISAM tables. You should specify the value of this parameter as 30 to 40 percent of available RAM if you use MyISAM tables exclusively. g. read_rnd_buffer_size=1m For this parameter, you specify the size of the buffer that the database uses after a sort, when it is reading rows in sorted order. When the database is reading rows from a MyISAM table in sorted order following a key-sorting operation, the rows are read through this buffer to avoid disk seeks. If you use many queries with ORDER BY, you can increase this parameter value to improve performance. h. query_cache_size=0 For this parameter, you specify the RAM amount allocated for the query cache. The caching mechanism works ineffectively; therefore, we recommend that the query cache be switched off. i. innodb_flush_log_at_trx_commit=2 For this parameter, you specify how often the log buffer is flushed on disk. The default value of this parameter is 1, which means that each UPDATE transaction will be flushed to a hard drive and therefore this mode is resource-demanding. When you set this parameter to 2, the log buffer is flushed to the OS file cache on every transaction commit, which significantly increases the speed of writing to the database. The drawback of this mode is that the database can lose transactions for the last second or two if OS crashes. Common Problems and Solutions Problem Solution The Out of memory error message occurs Check that at least 20% of the hard drive on which the Acumatica ERP database is installed is free. Not all requests are completed Check that enough free space is allocated for the folder with temporary files.

87 Troubleshooting Acumatica ERP 87 Problem Solution The Too many connections error message occurs Increase the value of the max_connections parameter in the my.cnf file. Step 5: Collect More Information If you have not found the reason for the performance slowdown while performing the previous steps or you need to collect more details about it, perform the following substeps. Investigate Requests in the Request Profiler Do the following to isolate queries leading to errors and performance lags: On the Request Profiler (SM205070) form, specify the following settings, which are shown in the screenshot below: Log SQL Requests: Selected SQL Time Threshold: 2000 SQL Count Threshold: 1000 : You have specified two thresholds for the requests. Therefore, the profiler will record the URL requests that meet either of these conditions (the logical OR is applied). Figure: Request Profiler settings If the Request Profiler has not been started yet, click Start on the form toolbar. Reproduce the slowdown in the system. 4. On the Request Profiler form, click Refresh Results on the form toolbar to upload to the form all the new activities since the last refresh. 5. Review the list of requests as follows: 6. Find requests that have a value other than LongRun in the Command Target column with a server time greater than 2000 milliseconds. Find requests that have more than 1000 milliseconds in the SQL Count column. For each request that meets either or both of the criteria above, select the corresponding row in the table, and click SQL on the table toolbar to see the queries being executed, as shown in the following screenshot.

88 Troubleshooting Acumatica ERP 88 Figure: SQL button 7. In the SQL Profiler dialog box, which opens, review the TimeMs column, which shows the time taken by each step, and find the row with the biggest value in this column, as shown in the following screenshot. Figure: SQL Profiler dialog box 8. Double-click on this row to see the actual SQL statement, an example of which is shown in the following screenshot. Figure: SQL statement 9. Copy and paste the statement into SQL Server Management Studio, run the query with the Execution Plan enabled, and see whether any suggestions are provided by the SQL Server. The following screenshot demonstrates SQL Server suggesting that the problem is a missing index.

89 Troubleshooting Acumatica ERP 89 Figure: SQL Server suggestion 10. Report the issue to the Acumatica support team, as described in Step 6: Submit a Case to Acumatica Support. You can save the Request Profiler log to an Excel file by clicking Export to Excel on the table toolbar on the Request Profiler form. : You can perform the solution suggested by SQL Server as an interim fix after consultation with the Acumatica support team. However, we recommend that such issues are always reported via a support case for a permanent solution. Collect Additional Information from the Logs You should collect the information from the needed log files depending on the situation, which can be one of the following: The performance slowdown appeared after an update Your site is completely non-responsive or extremely slow You need to track a randomly reproducible error If the performance slowdown appeared after an update Get information on the update that was performed and the errors that occurred during update by using the following resources: Update history and errors On the Update History tab of the Apply Updates (SM203510) form, get the information on the history of updates and the errors that occurred during update. You can get the same information from the UpHistory and UpErrors database tables of the site database, which you can view in the SQL Server Management Studio. Maintlog.txt This log file contains the update history for the instance and all the errors that were logged during the update. The log file can be used to review the cause when you are unable to log in due to a failed update through the Acumatica ERP Configuration Wizard. You can find the file in the folder <Acumatica ERP Installation Folder>\<Site Folder> \App_Dat By default, the folder is C:\Program Files (x86)\acumatica ERP\<Site Folder>\App_Dat Provide this information to the Acumatica support team, along with other information on the performance slowdown issue. (For the list of information that you should provide to support, see Step 6: Submit a Case to Acumatica Support.) If your site is completely non-responsive or extremely slow: Create a dump file as follows: In Task Manager on the application server, find the w3wp.exe process that is run under the username that is the name of the application pool.

90 Troubleshooting Acumatica ERP 90 Right-click on the process, and select Create Dump File, as shown in the following screenshot. Figure: Creation of a dump file : A process dump is a snapshot of an application showing what processes were executing and which modules were loaded at the time it was taken. The dump must be created only when the site is completely non-responsive or extremely slow. While you are creating a dump file, the process goes into a suspended mode, which will disconnect users from the site and lose any unsaved work. Provide the dump file to the Acumatica support team, along with other materials related to the performance slowdown issue. (For the list of information that you should provide to support, see Step 6: Submit a Case to Acumatica Support.) If you need to track a randomly reproducible error Enable the first-chance exception log as follows: Ensure that there is enough hard drive space on the Acumatica ERP installation drive (which by default is drive C). : The first-chance exception log grows quite quickly in size and should be enabled for only short periods of time. In the weconfig file in the Acumatica ERP site folder, find the EnableFirstChanceExceptionsLogging key, and change its value to true, as shown in the following screenshot. Figure: Fragment of weconfig c. Reproduce the problem. d. Find the first-chance exception log file in the site folder. By default, it is C:\Program Files (x86)\acumatica ERP\<Site Folder>\firstchanceexceptions.log. : The first-chance exception log is a powerful mechanism to track all exceptions in the system, but especially randomly reproducible errors. The difference between the first-chance exception log and the exception log that you can obtain by using the Request Profiler in Acumatica ERP (if you select Log Trace Messages, Log Exceptions, or both on the Request Profiler (SM205070) form) is that the first-chance exception log tracks not only committed transactions but also transactions that resulted in errors.

91 Troubleshooting Acumatica ERP 91 Provide the first-chance exception log file to the Acumatica support team, along with other materials related to the performance slowdown issue. (For the list of information that you should provide to support, see Step 6: Submit a Case to Acumatica Support.) Use External Tools You can use different external tools to get more information about the reasons for the performance slowdown. For example, you can use the dottrace performance profiler to create a process snapshot. If you use external tools to investigate performance issues, include the information obtained from these tools when you contact the Acumatica support team. (For the list of information that you should provide to support, see Step 6: Submit a Case to Acumatica Support.) Step 6: Submit a Case to Acumatica Support If you have not found a solution for your issue, create a case for the Acumatica support team and provide as much information in it as you can, which may include the following information: Basic points to reproduce the issue Version and build of Acumatica ERP Troubleshooting steps taken so far (provide screenshots where applicable): Have you checked whether the site is licensed? Have you checked the speed from other browsers? If the issue is reproduced in only one browser, specify the browser and its version. Have you checked the speed from other locations? Have you checked automation schedules? Have you checked the list of running processes in Acumatica ERP and in the operating system? Have you checked whether antivirus software is blocking the site? Have you checked the configuration of the application server? Specify whether dynamic content compression is enabled in the system. Specify whether the application uses its own application pool. Specify the mode in which IIS is running. Specify the parameters of the application server (total physical memory, number of CPU cores, operating system, and number of concurrent users in the system). Have you checked the configuration of the database server? Specify whether the application server and database server are on separate hosts. Specify the maximum server memory specified in SQL Server settings. Specify whether weekly maintenance plans are scheduled. Specify the parameters of the database server (total physical memory, number of CPU cores, and operating system). Provide the performance reports of SQL Server. Specify whether you have found any locks in the SQL Activity Monitor. Have you used the Acumatica ERP Request Profiler?

92 Troubleshooting Acumatica ERP 92 Provide the log of the Request Profiler exported to Excel. Specify whether you have found any long-running requests. Have you obtained any additional information? Include memory dump file. Include update history and errors. Include maintlog.txt. Include first-chance exception log. Include dottrace snapshot. Access credentials Convenient times to reset the system without contacting the client (if any) Using Logs Acumatica ERP stores logs in a number of files and database tables. This topic contains information about the following logs: Trace: You can use this standard Acumatica ERP log for browsing issues that occur in the application. First-chance exception log: This mechanism for catching and logging exceptions can be very helpful when you are facing a problem of an unknown origin. Configuration Wizard logs: These logs provide information related to issues occurring in the Acumatica ERP Configuration Wizard or Acumatica Framework Configuration Wizard. Maintenance logs: In these logs, you can find details about issues that occur when you perform an upgrade in the Acumatica ERP application. Acumatica ERP logs: These logs, which are stored in database tables, provide historical data for various operations. Windows logs: These logs provide details for issues related to ASP.NET (for example, frequent application restarts or unhandled exceptions). IIS logs: In these logs, IIS keeps records of all requests. SQL Server logs: These logs, kept by SQL Server, contain details for issues related to database accessibility and server maintenance operations. Trace The Acumatica ERP trace log is the first place you should look when you face an issue in the application. You can view the trace log by clicking Help > Trace on the form title bar. When you are working with reports or generic inquiries, the trace log contains relevant SQL statements that you can use for SQL debugging purposes. By default, the trace log is stored only in the current user session. However, you can also store the trace log in the file system. This possibility is useful when you are dealing with errors that cause Internet Information Services (IIS) to become unresponsive and result in a web server restart. To make the trace log stored in a file as well as in the current user session, edit the pxtrace section of the weconfig file (which is located in the folder that contains the application instance website) similarly to the code block shown below. <pxtrace defaultprovider="pxsessiontraceprovider"> <providers> <remove name="pxsessiontraceprovider" />

93 Troubleshooting Acumatica ERP 93 <add name="pxsessiontraceprovider" type="px.datpxsessiontraceprovider, PX.Data" url="../frames/trace.aspx" /> <remove name="pxfiletraceprovider" /> <add name="pxfiletraceprovider" type="px.datpxfiletraceprovider, PX.Data" file = "C:\Out\AcumaticaTraceInfo.txt" /> </providers> </pxtrace> In this case, the log file will be stored in C:\Out\AcumaticaTraceInfo.txt. You should create the folder for the log file manually. : You will have to monitor the size of the log file manually and delete its contents from time to time to avoid excessive growth of the file. If you prefer to store the trace log only in a file and not in the current user session, edit the pxtrace section of the weconfig file similarly to the code block shown below. <pxtrace defaultprovider="pxfiletraceprovider"> <providers> <remove name="pxfiletraceprovider" /> <add name="pxfiletraceprovider" type="px.datpxfiletraceprovider, PX.Data" file = "C:\Out\AcumaticaTraceInfo.txt" /> </providers> </pxtrace> First-Chance Exception Log Acumatica ERP has a mechanism for catching and logging all exceptions in the system. You can activate it by editing the appropriate line in the appsettings section of the weconfig file (which is located in the folder that contains the application instance website) to read as follows. <add key="enablefirstchanceexceptionslogging" value="true" /> You can edit the file name for the log in the following line of the same section. (By default, the log will be stored in <Site_Folder>\App_Data\firstchanceexceptions.log, where <Site_Folder> is the path to the folder that contains the application instance website.) <add key="firstchanceexceptionslogfilename" value="firstchanceexceptions.log" /> : The first-chance exception log contains records of all exceptions, including those that the system has already caught and handled without issues, so the log file will grow rapidly and may reach an unmanageable size in minutes. Because of this, we recommend that you activate this logging mechanism for only short periods of time. In addition, you may want to erase the contents of the file once the error has been replicated and you have determined the required call stack. When you are facing a problem of an unknown origin, we recommend that you use this logging mechanism before trying other solutions that is, you enable the mechanism, replicate the error, disable the mechanism to stop the log file from growing too much, and view the resulting log. Configuration Wizard Logs If an error occurs when you are using the Acumatica ERP Configuration Wizard or Acumatica Framework Configuration Wizard, you can find the details of the error in the corresponding wizard log: Acumatica ERP Configuration Wizard: <Application_Installation_Folder>\log.txt Acumatica Framework Configuration Wizard: <Framework_Installation_Folder>\log.txt In particular, if you are performing an upgrade by using the Acumatica ERP Configuration Wizard, the log contains all errors that have occurred during the upgrade, including all failed SQL statements.

94 Troubleshooting Acumatica ERP 94 : If a log file becomes too large, you can create a backup and delete the file. Maintenance Logs In the maintenance logs, you can find details for issues that occur when you perform an upgrade in the Acumatica ERP application. The maintenance logs are stored in the following locations: The UPErrors database table: This table contains all errors that occur during an update of the database performed in the Acumatica ERP application. The table is displayed on the Update History tab of the Apply Updates (SM203510) form. The maintenance log file (<Site_Folder>\App_Data\maintlog.txt): This file contains all errors that occur during a site upgrade performed in the Acumatica ERP application. In addition, the file contains all failed SQL statements. You can view this file in Acumatica ERP by clicking Show Log File on the Update History tab of the Apply Updates form. Acumatica ERP Logs Other logs that may be useful are stored in the following database tables: LoginTrace: All login, logout, form opening, session expiration, and customization publishing events UPSnapshotHistory: All snapshot restore operations UPHistory: All application updates AUScheduleHistory: All schedule execution events AuditHistory: All field changes (if auditing is enabled) SyncLog: All exchange synchronization operations AUNotificationHistory: All notification operations PushNotificationsErrors: Errors during creation of push notifications PushNotificationsFailedToSend: Information on the push notifications that Acumatica ERP failed to send to the notification destination within the last two days Windows Logs You may need to check the Windows logs if any of the following is occurring: Your application restarts frequently. There are unhandled exceptions in the application. The system shows the Session has expired message too often. ASP.NET Core records various exceptions and maintenance operations to these logs. The two Windows logs you need to check are the Application and System logs. To do this, open Windows Event Viewer and, in the navigation pane, select: Windows Logs > Application for the Application log. Windows Logs > System for the System log. We recommend that you search the logs for the following events:.net Runtime events ASP.NET events IIS events

95 Troubleshooting Acumatica ERP 95 Network events IIS Logs Records of all requests are stored in the IIS (Internet Information Services) log files. To find the log files for your site, open IIS Manager, navigate to the site, and double-click Logging. On the Logging feature page that opens, in the Directory box, you can find the path to the folder with the log files. SQL Server Logs In Microsoft SQL Server, storage of system logs is enabled by default. These logs contain information about database accessibility and server maintenance operations. To view the logs, open Object Explorer in Microsoft SQL Server Management Studio and navigate to <Your_Server> > Management > SQL Server Logs. Using Profilers To monitor the state of your Acumatica ERP server at any given moment, you can use the following profilers and related tools, each of which is described in a section in this topic: Acumatica ERP request profiler: A tool for monitoring the performance of requests in Acumatica ERP Acumatica ERP SQL profiler: A tool for monitoring the performance of SQL queries Acumatica ERP running processes: A form for monitoring batch processing operations SQL Server profiler: A tool for tracing SQL queries Browser profilers: Tools for monitoring requests, catching JavaScript errors, and obtaining network timing data Stack trace snapshot: A method for investigating website-related issues Acumatica ERP Request Profiler On the Request Profiler (SM205070) form, you can monitor the performance of Acumatica ERP and find out which requests are taking too much time. By using the filters on the form, you can identify the periods of slow performance and isolate its root cause. For details, see the Request Profiler topic. : For a simple operation (such as opening a screen, adding a new record, or deleting a record), the standard duration of the execution of the request on the server (server time) is about 500 milliseconds. You can also monitor exceptions by using this form. To activate this functionality, select the Log Trace Messages check box (for documented exceptions) and the Log Exceptions check box (for undocumented exceptions). To view exceptions that occurred during the execution of a request, select the request in the table and click Trace on the table toolbar. Acumatica ERP SQL Profiler You can analyze SQL queries by using the built-in SQL profiler of Acumatica ERP. To activate the SQL profiler, select the Log SQL Requests check box on the Request Profiler (SM205070) form. To view the SQL profiler log, click SQL on the table toolbar of the same form. For details, see the Request Profiler form reference topic. : We recommend that you activate the Log SQL Requests mode for only a limited period because it can degrade system performance.

96 Troubleshooting Acumatica ERP 96 Acumatica ERP Running Processes On the Running Processes (SM201530) form, you can monitor all batch processing operations that are currently being performed in the system, such as the release of multiple transactions at once, preparation of dunning letters, generation of a report, creation of a company snapshot, or use of an import or export scenario. Your server may be slow because of a large number of such operations running simultaneously. SQL Server Profiler Microsoft SQL Server Profiler is a tool for tracing SQL queries. To find problematic queries more easily, you can select only particular events to be traced and use various filters. Sometimes it may be helpful to identify the actual SQL query by using the profiler and then execute the query in Microsoft SQL Server Management Studio to investigate the problem. Browser Profilers Most modern browsers offer debugging tools, which you can use to monitor requests, catch JavaScript errors, and obtain network timing dat Combined with the Acumatica ERP Request Profiler, these tools can help you analyze the network latency. Stack Trace Snapshot If your site is unresponsive and you are unable to establish the reason, you can create a dump of the stack trace of the running process. To do this, right-click the IIS worker process (w3wp.exe) in Windows Task Manager and select Create Dump File. You can then open the dump file in Visual Studio and analyze all threads and their stack traces. Using Built-In Debugging Tools The following built-in debugging tools, described in the sections of this topic, may help you get more information from Acumatica ERP: Automation debugging: A mechanism for debugging automation steps and definitions ShowError URL parameter: A parameter for viewing the details of errors in Acumatica ERP without direct access to the file system of the server Automation Debugging If you encounter a problem with automation steps or definitions that you have configured in Acumatica ERP, you can use automation debugging. You can activate it by adding the following line in the appsettings section of the weconfig file (which is located in the folder that contains the application instance website). <add key="automationdebug" value="true" /> After you have activated automation debugging, you can view the information about the current automation step in the form title bar on any form in Acumatica ERP. ShowError URL Parameter If Acumatica ERP displays a generic error message (for example, We're sorry! An error has occurred while processing your request. A report has been generated for our technical staff to investigate the problem. Please try to repeat your request later. Thank you for understanding.) and you do not have direct access to the file system of the Acumatica ERP server (as in the case of public hosting), you can use the special URL parameter ShowError=true. As a result, the system will display the specific message for the error that has occurred instead of the generic message.

97 Troubleshooting Acumatica ERP 97 The full URL with the parameter looks as follows: showerror=true, where <website_address> is replaced with the address of your site. Using Third-Party Tools This topic describes the following third-party tools, which may be useful for troubleshooting: JetBrains dottrace: A tool for analyzing the application performance.net Memory Profiler: A tool for analyzing an application's memory usage WinDbg: A powerful tool for analyzing process dump files JetBrains dottrace JetBrains dottrace is a tool for analyzing the performance of your application. In particular, by using this tool, you can view the average running time for the methods in your application..net Memory Profiler.NET Memory Profiler is another tool for monitoring and analyzing issues on your server. By using this tool, you can take snapshots of the Acumatica ERP memory and isolate memory leaks. WinDbg WinDbg is a powerful tool that can open and analyze process dump files. To use WinDbg, you first need to obtain two.dll files from the.net Framework version installed on the machine where the dump file was created. You then load these files into WinDbg by using the.load command, and use the.symfix system command to set the symbol storing path, as shown below..load c:\sos\sos.dll.load c:\sos\mscordacwks.dll.symfix You can then analyze all objects in the memory by using the following commands:!dumpheap -stat (summary for objects of all types)!dumpheap -type System.DatSqlClient.SqlConnection (objects of a specific type)!do feeeca24a0 (object at a specific address) By exploring the memory this way, you can obtain the value of each object instance in the current process, which may help you find the reason why the application is not working correctly. To Optimize Memory Consumption During Startup On initialization of the domain, the system compiles every page from the site map and stores the pages in the web server cache. This gives users the ability to quickly open any page without having to wait for it to compile when the page is opened for the first time. The downside of compiling every page during startup is the significant increase in memory consumption for a short period after the initialization. To avoid this increase in memory consumption, you can disable the compilation of all pages during startup. To Optimize Memory Consumption During Startup Open the weconfig file for the instance. Usually it can be located in %Program Files% \Acumatica ERP\<instance name>, where <instance name> is the name of the application instance website.

98 Troubleshooting Acumatica ERP 98 Set the CompilePages setting to False in the appsettings section of the weconfig file, as follows. <appsettings>... <add key="compilepages" value="false"/>... </appsettings> With the CompilePages flag set to False, a page will be compiled on the first request by a user. Hence, the page will be opened slowly the first time. However, after the first request, the page will be opened as quickly as it is when CompilePages is set to True. Save the weconfig file, which automatically restarts the website.

99 Uninstalling Acumatica ERP 99 Uninstalling Acumatica ERP To uninstall an Acumatica ERP application instance, you perform the following steps: Delete application instances on the server by using the Acumatica ERP Configuration Wizard. For details, see To Delete an Acumatica ERP Application Instance. Uninstall the Acumatica ERP Tools on a server computer by using the standard Windows procedure. The relevant registry data is cleaned, and the program group item is removed. The above procedure does not affect the following entities: Databases created by the application: If you need to delete a database, do so manually by using SQL Server tools. Directories on the file system used by the application: If needed, manually delete the empty directories on the file system and the program group items. To Delete an Acumatica ERP Application Instance When you delete an instance by using the Application Maintenance page, you delete applications created under the default site in Internet Information Services (IIS) when installing Acumatica ERP. To Delete an Acumatica ERP Application Instance Run the Acumatica ERP Configuration Wizard on the server where Acumatica ERP is installed. For example, select Start > Acumatica > Acumatica ERP Configuration. On the Welcome page, click Perform Application Maintenance. On the Application Maintenance page, do the following: In the Installed Sites list, click the Acumatica ERP instance that you want to delete. Click Delete. c. When you're prompted, click OK. The Acumatica ERP instance files are deleted from the file system, and the virtual directory of the instance is removed from IIS configuration. The database of the instance remains untouched when you delete the instance; if you want to delete the database, you must do so manually.

100 Using the Command-Line Tool 100 Using the Command-Line Tool You can use the command-line tool (executable name ac.exe) to deploy a new application instance of Acumatica ERP and to perform database and application maintenance. By default, ac.exe is located in the folder on the computer that has Acumatica ERP installed, which is C:\Program Files (x86)\acumatica ERP\Data\. The Command-Line Tool Possible Parameters and Values To Create a Configuration File Examples of the Configuration String The Command-Line Tool When you run ac.exe, you supply a set of command-line parameters where each parameter must be presented in the following form. -parameter:"parameter value" Use the following syntax. ac.exe [-f -file:"path to configuration file"] [-cm -configmode:"main scenario"] [-s -dbsrvname:"server name"] [-sw -dbsrvwinauth:"true False"] [-u -dbsrvuser:"user name"] [-p -dbsrvpass:"user password"] [-d -dbname:"database name"] [-n -dbnew:"true False"] [-b -dbupdate:"true False"] [-dm -dbmode:"regular Template Demo"] [-dz -dbsize:"database size in GB"] [-ds -dbskip:"skip database setup"] [-dc -dbshrink:"shrink database"] [-i -iname:"instance name"] [-io -ioldname:"old instance name"] [-h -ipath:"instance directory"] [-is -vmsize:"small Medium Large ExtraLarge"] [-it -trumbprint:"x.509 thumbprint"] [-ip -project:"vs project name"] [-w -swebsite:"web site name"] [-v -svirtdir:"virtual directory"] [-po -spool:"application pool"] [-a -sactions:"anonymoususer SelectedUser"] [-k -suser:"user name"] [-m -spass:"user password"] [-dw -dbwinauth:"true or False"] [-dn -dbnewuser:"true False"] [-du -dbuser:"user name"] [-dp -dbpass:"user password"] [-wc -wscompany:"company ID"] [-wu -wsuser:"user account"] [-ww -wswiki:"portal Wiki"] [-cs -securemode:"true False"] [-sp -split:"[t Table=table name]; [o Option=Separate Split Shared]"] [-c -company:"[ci CompanyID=company ID]; [cp ParentID=parent company ID] [cv Visible=True];[ct CompanyType=True]; [cn LoginName:user name]; [cd Delete:True]"] [-vst -vstemplates:"true False"] [-vsc -vscontrols:"true False"] [-op -output:"normal Quiet Forced"] All parameter values are case-sensitive and must be enclosed in quotation marks. Each parameter for the command line also has a short form that you can use instead of the full parameter name. If you have specified a parameter more than once in a command line, the last parameter value will be used. You can run ac.exe in one of three modes: Command-line: Parameters are passed to ac.exe from the command line. Batch: The path to the configuration file with parameters is passed to ac.exe from the command line.

101 Using the Command-Line Tool 101 Mixed: Some parameters are passed to ac.exe through the configuration file, while other parameters are passed from the command line. In this mode, command-line parameters have a priority over those specified in the configuration file. Possible Parameters and Values The following table lists all available command-line parameters and values and a brief description of each parameter. Parameter Values Description -file path to configuration file Specifies the directory where the XML configuration file is stored. By default, the file is stored in C:\Program Files (x86)\acumatica ERP\Data\. or -f Example: -file:"c:\program Files (x86)\program Folder\Data\" -configmode NewInstance or DBMaint -cm DBConection (Mandatory) Specifies the maintenance scenario for which you are using the command-line tool. The possible values and applicable scenarios follow: ToolsInstall NewInstance: Installs a new application instance. You can also use the following command-line parameters in this scenario: NewCompanyPortal -company DeleteSite -dbname RenameSite -dbnew UpgradeSite -dbnewuser CompanyConfig -dbpass -dbsrvname -dbsrvpass -dbsrvuser -dbsrvwinauth -dbupdate -dbuser -dbwinauth -iname -ipath -sactions -spass -split -spool -suser -svirtdir -swebsite

102 Using the Command-Line Tool 102 Parameter Values Description DBMaint: Creates a new database or updates an existing database with a current version of the database schem You can also use the following command-line parameters in this scenario: -company -dbname -dbnew -dbsrvname -dbsrvpass -dbsrvuser -dbsrvwinauth -dbupdate -split DBConection: Modifies database connection settings. You can also use the following command-line parameters in this scenario: -company -dbname -dbnew -dbnewuser -dbpass -dbsrvname -dbsrvpass -dbsrvuser -dbsrvwinauth -dbupdate -dbuser -dbwinauth -split CompanyConfig: Adds new companies or deletes existing ones. You can also use the following commandline parameters in this scenario: -company -dbname -dbnew -dbsrvname -dbsrvpass -dbsrvuser -dbsrvwinauth -dbupdate

103 Using the Command-Line Tool 103 Parameter Values Description -split ToolsInstall: Installs Acumatica ERP controls and templates for Microsoft Visual Studio; this option is available in the Acumatica ERP Configuration Wizard. You can also use the following command-line parameters in this scenario: -vscontrols -vstemplates NewCompanyPortal: Installs a new company portal; this option is available in the Acumatica ERP Configuration Wizard. You can also use the following command-line parameters in this scenario: -dbname -dbnew -dbnewuser -dbpass -dbsrvname -dbsrvpass -dbsrvuser -dbsrvwinauth -dbupdate -dbuser -dbwinauth -iname -ipath -sactions -spass -spool -suser -svirtdir -swebsite -wscompany -wsuser -wswiki DeleteSite: Deletes an existing Acumatica ERP instance. You can also use the -iname parameter in this scenario. RenameSite: Renames an existing Acumatica ERP instance. You can also use the following command-line parameters in this scenario: -iname

104 Using the Command-Line Tool 104 Parameter Values Description -ioldname UpgradeSite: Upgrades the files of an existing Acumatica ERP instance. You can also use the -iname command-line parameter in this scenario. Example: -configmode:"newinstance" -dbsrvname server name or -s Example: -dbsrvname:"(local)" -dbsrvwinauth True or Specifies the name of the SQL server that will be accessed by this application instance of Acumatica ERP. The default setting is (local). False -sw Specifies whether Windows or SQL Server authentication will be used by the configuration tools to access SQL Server. Select one of the following values: True: Uses Windows authentication. This is the default value. False: Uses SQL Server authentication. Example: -dbsrvwinauth:"true" -dbsrvuser user name or -u Specifies the user name of the account used to access SQL Server. You must add this parameter if the SQL Server authentication method is used (and the dbsrvwinauth parameter value is set to False). Example: -dbsrvuser:"sqladmin" -dbsrvpass user password or -p Specifies the user password for the account used to access SQL Server. You must specify this parameter if the SQL Server authentication method is used (and the dbsrvwinauth parameter value is set to False). Example: -dbsrvpass:"<user_password>" -dbname database name or Required. Specifies the name of the database maintained by this application instance of Acumatica ERP. Example: -dbname:"hsbc_db" -d -dbnew True or False -n -dbupdate True or False -b Specifies whether you want to create a new database in SQL Server. The default setting is True. Example: -dbnew:"false" Specifies whether you want to update an earlier version of the database with a newer one. You can also use this parameter to repair an existing database of the current version. The default setting is True. Example: -dbupdate:"false" -dbmode Regular or Template Specifies the database creation mode. This parameter is valid for Acumatica Framework only. Select one of the following possible values:

105 Using the Command-Line Tool 105 Parameter Values -dm Demo Description Regular: Creates a regular Acumatica Framework application. Template: Creates a template for an Acumatica Framework training application. Demo: Creates an Acumatica Framework training application. Example: -dbmode:"demo" -dbsize 1 or 5 -dz Specifies the maximum size of the database on Azure SQL and therefore is used only for Acumatica ERP deployed on Windows Azure. The available values correspond to the standard database size values in GB. The default setting is Example: -dbsize:"50" dbskip True or False -ds Specifies whether the database setup steps are skipped. If they are, the database will be set up by the Acumatica ERP instance in run time. The default setting is False. Example: -dbskip:"false" -dbshrink True or False -dc Specifies whether you want the utility to shrink the database once it has been configured. This parameter is used only for Acumatica ERP deployed on Windows Azure. The default setting is False. Example: -dbshrink:"true" -iname instance name Example: -iname:"hsbc Main ERP" or -i -ioldname old instance name or Specifies the current name of an Acumatica ERP instance when you rename this instance. Example: -ioldname:"hsbc_hq" -io -ipath Required. Specifies the name of the Acumatica ERP instance. instance directory or -h Required. Specifies the directory where the application instance files will be stored. The default setting is C: \Program Files\Acumatica ERP\. Example: -ipath:"c:\program Folder\" -vmsize Small or Medium -is Large ExtraLarge Specifies the relative size of the Windows Azure virtual machine. This parameter is used only for Acumatica ERP deployed on Windows Azure. The default setting is Small. Example: -vmsize:"extralarge"

106 Using the Command-Line Tool 106 Parameter Values Description -thumbprint X.509 thumbprint Specifies the thumbprint of the maintenance certificate uploaded to the hosted service on Windows Azure. For more information on finding the thumbprint, see Deploying the Acumatica ERP Service on Windows Azure. Visual Studio project name Specifies the name of the Visual Studio project. This parameter is used in Acumatica Framework only. or -it -project or Example: -project:"<project_name>" -ip -swebsite website name Specifies the name of the existing Internet Information Services (IIS) website on the local computer. virtual directory Specifies the name of the IIS virtual directory. If there is no such virtual directory in IIS, this directory will be created on the local IIS. or -w -svirtdir or -v -spool Example: -svirtdir:"<virtual_directory_name>" application pool or -po Specifies the name of the IIS application pool. If there is no such application pool in IIS, this pool will be created on the local IIS. Example: -spool:"<application_pool_name>" -dbwinauth True or False -dw Specifies whether Windows or SQL Server authentication will be used by this Acumatica ERP instance to access SQL Server. These are the possible values: True: Uses Windows authentication. (This is the default value.) False: Uses SQL Server authentication. Example: -dbwinauth:"true" -dbnewuser True or False -dn -dbuser user name or -du Specifies whether a new SQL Server account must be created. The default setting is True. Example: -dbnewuser:"true" Specifies the name of the user account used by this Acumatica ERP instance to access SQL Server. You must add this parameter if the SQL Server authentication method is used (and the dbwinauth parameter value is set to False). Example: -dbuser:"sqladmin" -dbpass or -dp user password Specifies the password of the user account used by this Acumatica ERP instance to access SQL Server. You must add this parameter if the SQL Server authentication method is used (and the dbwinauth parameter value is set to False). Example: -dbpass:"sqladmin"

107 Using the Command-Line Tool 107 Parameter Values Description -wscompany company ID Specifies the ID of the company that will be used for the company portal. This parameter is used only in the Company Portal configuration mode. or -wc -wsuser Example: -wscompany:"<company_id>" user name or -wu -wswiki Specifies the user account that will be used for the company portal. This parameter is used only in the Company Portal configuration mode. Example: -wsuser:"<company_id>" portal Wiki or -ww Specifies the Wiki article that will be used for the company portal. This parameter is used only in the Company Portal configuration mode. Example: -wswiki:"<company_id>" -securemode True or False -cs Specifies whether the company ID is displayed on the logon screen. The default setting is False. Select one of these possible values: True: Hides the company ID. False: Displays the company ID. Example: -securemode:"false" -split table split options or -sp Specifies split options for a table stored in an existing database. If you want to configure more than one table, you need to specify this parameter for each of the tables. This parameter contains two subparameters: Table (short form: t) and Option (short form: o). For the Table subparameter, you specify the name of the database table. For the Option subparameter, you specify one of the three values that indicate the available split modes: Separate Split Shared Example: -Split:"Table=AccountClass; Option=Shared; " -Split:"Table=AccessInfo; Option=Split; "-Split:"Table=APContact; Option=Separate;" -company or -c company options Specifies company options. If you want to configure options for more one company, specify this parameter for each of the companies. This parameter contains the following subparameters: CompanyID: Specifies the company ID. To modify the settings of an existing company, specify its ID here. ParentID: Specifies the ID of the company's parent company.

108 Using the Command-Line Tool 108 Parameter Values Description Visible: Allows users to sign in to the company if you specify the True value. CompanyType: Inserts demo data into the company's database if you specify the True value. LoginName: Displays the company name on the Acumatica ERP logon screen. Delete: Deletes the company if you specify the True value. Example: -company:"companyid=kc; ParentID=1; Visible=True; CompanyType=True; LoginName=Company; Delete=True" -vstemplates True or False -vst Specifies whether Acumatica Framework Templates for Microsoft Visual Studio must be installed. This parameter is used with Acumatica Framework only. To install the templates, add this parameter and specify the True value. Example: -vstemplates:"true" -vscontrols True or False -vsc Specifies whether Acumatica Framework Controls for Microsoft Visual Studio must be installed. This parameter is used with Acumatica Framework only. To install the controls, add this parameter and specify the True value. Example: -vscontrols:"true" -output Normal or Quiet -op Forced Specifies the command-line execution mode. Select one of the following possible values: Normal: The command line acts as a dialog. When you run the ac.exe utility, you will answer questions related to the parameters. Quiet: All warnings are ignored. Any error forces the ac.exe utility to stop and exit. Forced: All warnings are ignored. If you do not specify any mandatory parameters, they are automatically configured with default values. Minor errors are ignored, while critical errors force the ac.exe utility to stop and exit. Example: -output:"forced" -dbcollation or Microsoft SQL Server collation name -dl Example: -dbcollation:french_ci_ai -dboptimize True or False -do Specifies a collation that will be used for a database that is created during Acumatica ERP instance deployment instead of the default SQL_Latin1_General_CP1_CI_AS collation. Specifies whether the Optimize Tables command should be applied to MySQL database tables during deployment of an Acumatica ERP instance. The default value of this parameter is False because the process of table optimization may take a lot of time. To apply the Optimize Tables command, add this parameter and specify the True value.

109 Using the Command-Line Tool 109 Parameter Values Description Example: -dboptimize:"true" : For all command-line parameters that have the False and True values, you can also use No instead of False and Yes instead of True. To Create a Configuration File You can create a configuration file for the unattended deployment and maintenance of application instances. You can create this configuration file manually or create it automatically by running the Acumatica ERP Configuration Wizard. To Create the Configuration File by Using the Acumatica ERP Configuration Wizard Run the Acumatica ERP Configuration Wizard. For example, select Start > Acumatica > Acumatica ERP Configuration. Use the wizard to specify all the options that you want. On the final page of the wizard, click Save Configuration to save the configuration file. Figure: Saving configuration parameters to a file The configuration data is saved in this file in XML format and as a command-line command using both the short and full forms of the parameters. Examples of the Configuration String In this topic, you can find examples of the configuration string. The following command-line command creates an application instance. ac.exe -configmode:"newinstance" -dbsrvname:"gp" -dbname:"jpmorgan" -company:"companyid=1;companytype=;loginname=;" -company:"companyid=2;companytype=;parentid=1;visible=yes; LoginName=JPMorgan;" -iname:"jp Morgan" -ipath:"c:\program Files\Program Folder\JP Morgan\\" -swebsite:"default Web Site" -svirtdir:"jpmorgan" -spool:"jpmorgan" -sactions:"selecteduser" -suser:"gp\administrator"