Installation Procedures Guide EPSi 16 · 2019. 8. 28. · 5 December 2017 EPSi™ 16.3 Installation Procedures Guide 2 Publish Date: 12/5/2017 for release 16.3 of Allscripts EPSi™

EPSi™ 7.5x, 8.x, and 16.x

December 5, 2017

Installation Procedures

Guide

5 December 2017 EPSi™ 16.3 Installation Procedures Guide 2

Publish Date: 12/5/2017 for release 16.3 of Allscripts EPSi™ (Version 1.0 of this document) For further information about this manual or other Allscripts Healthcare Solutions, LLC products, contact Global Product Support Services, as follows: Allscripts

Website http://www.allscripts.com/en/client-login.html (Client Support login is required. Contact information varies by product.) Telephone:1.800.877.5678 EPSi

Telephone: 877.623.5702 (Toll Free) Telephone: 636.532.8907 Email: [email protected] Allscripts Healthcare Solutions, LLC welcomes your opinion regarding this document. Please e-mail your comments and suggestions to [email protected]. Proprietary Notice

© 2017 Allscripts Healthcare Solutions, LLC and/or its affiliates. Allscripts Healthcare Solutions, LLC All Rights Reserved. This document contains confidential and proprietary information protected by trade secret and copyright law. This document, the information in this document, and all rights thereto are the sole and exclusive property of Allscripts Healthcare Solutions, LLC and/or its affiliates, are intended for use by customers and employees of Allscripts Healthcare Solutions, LLC and/or its affiliates and others authorized in writing by Allscripts Healthcare Solutions, LLC and/or its affiliates, and are not to be copied, used, or disclosed to anyone else, in whole or in part, without the express written permission of Allscripts Healthcare Solutions, LLC and/or its affiliates. For authorization from Allscripts to copy this information, please call Allscripts Global Product Support Services at 888 GET-HELP or 888 438-4357. Notice to U.S. Government Users: This is "Commercial Computer Software Documentation" within the meaning of FAR Part 12.212 (October 1995), DFARS Part 227.7202 (June 1995) and DFARS 252.2277014 (a) (June 1995). All use, modification, reproduction, release, performance, display, and disclosure shall be in strict accordance with the license terms of Allscripts Healthcare Solutions, LLC and/or its affiliates. Manufacturer is Allscripts Healthcare Solutions, LLC, and/or its affiliates, 222 Merchandise Mart Plaza, Suite #2024, Chicago, IL 60654. For authorization from Allscripts Healthcare Solutions, LLC to copy this information, please call Allscripts EPSi Support Services at 636-532-8907 or contact at [email protected]. IMPORTANT NOTICE REGARDING GOVERNMENT USE

The software and other materials provided to you by Allscripts include "commercial computer software" and related documentation within the meaning of Federal Acquisition Regulation 2.101, 12.212, and 27.405-3 and Defense Federal Acquisition Regulation Supplement 227.7202 and 52.227-7014(a). These materials are highly proprietary to Allscripts and its vendors. Users, including those that are representatives of the U.S. Government or any other government body, are permitted to use these materials only as expressly authorized in the applicable written agreement between Allscripts and your organization. Neither your organization nor any government body shall receive any ownership, license, or other rights other than those expressly set forth in that agreement, irrespective of (a) whether your organization is an agency, agent, or other instrumentality of the U.S. Government or any other government body, (b) whether your organization is entering into or performing under the agreement in support of a U.S. Government or any other government agreement or utilizing any U.S. Government or any other government funding of any nature, or (c) anything else. EPSi™ is a trademark of Allscripts Healthcare Solutions, LLC and/or its affiliates. All other products are trademarks of their respective holders, all rights reserved. Reference to these products is not intended to imply affiliation with or sponsorship of Allscripts Healthcare Solutions, LLC and/or its affiliates. The names and associated patient data used in this documentation are fictional and do not represent any real person living or otherwise. Any similarities to actual people are coincidental. CPT ©2010 American Medical Association. All rights reserved. Fee schedules, relative value units, conversion factors and/or related components are not assigned by the AMA, are not part of CPT, and the AMA is not recommending their use. The AMA does not directly or indirectly practice medicine or dispense medical services. The AMA assumes no liability for data contained or not contained herein. CPT is a registered trademark of the American Medical Association. International Statistical Classification of Diseases and Related Health Problems (ICD) is copyright 2009 World Health Organization (WHO). Microsoft® Excel and Microsoft® Word are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. Adobe, the Adobe logo, Acrobat, PDF, and Reader are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States and/or other countries. iPhone® and iPad® are trademarks of Apple Inc., registered in the U.S. and other countries.

mailto:[email protected]




Table of Contents

1 Introduction ..................................................................................................................................................................................................... 7

1.1 Overview .................................................................................................................................................................................................. 7

1.2 Assumptions and Notes ............................................................................................................................................................................ 7

1.3 Using SQL Server 2016 During 16.3 Upgrades ....................................................................................................................................... 7

2 EPSi Down Time Begins: Final Web Server(s) Preparation .......................................................................................................................... 7

3 Running the 16.3 Web Server Installation (WebServerBundle.exe) ............................................................................................................ 15

4 Running the Database Update Utility Independent from WebServerBundle. .............................................................................................. 31

5 Payment and Charge Conversions (8.X Upgrades) ...................................................................................................................................... 38

5.1 Errors in Payment and Charge Conversion Processes ........................................................................................................................... 39

5.1.1 Run SQL Script ............................................................................................................................................................................... 39

5.1.2 Run SQL Server Agent Jobs ........................................................................................................................................................... 40

5.2 Monitoring Data Conversions (SQL) ..................................................................................................................................................... 41

6 Running the Report Conversion Utility ........................................................................................................................................................ 43

6.1 Monitoring Report Conversions ............................................................................................................................................................. 48

7 Setup Workstations ....................................................................................................................................................................................... 49

7.1 Desktop Applications Setup ................................................................................................................................................................... 50

7.1.1 Assumptions .................................................................................................................................................................................... 50

7.1.2 Minimum Desktop Requirements ................................................................................................................................................... 50

7.1.3 DTC – Distributed Transaction Coordinator Settings .................................................................................................................... 51

7.1.4 Desktop Installation ........................................................................................................................................................................ 52

12) Double-Click on the DesktopBundle.MSI to launch the Setup Wizard. ................................................................................................ 53

7.1.5 Desktop Application INI files ......................................................................................................................................................... 62

7.2 Setting Up New EPSi Workstation Accounts ........................................................................................................................................ 63


8 Post Installation Technical Tasks .................................................................................................................................................................. 65

8.1 Prior to 16.1.01 CU3: Run Patient-Merge Trigger Script ...................................................................................................................... 65

8.2 General Technical Tasks ........................................................................................................................................................................ 65

8.3 Optional: Check Allscripts Windows Services Log Files & Windows Event Viewer .......................................................................... 66

8.4 Suggested Check: Check IIS DefaultAppPool ....................................................................................................................................... 67

8.5 Suggested: Manually Check FileShares on the Report/Web Server ...................................................................................................... 70

8.6 Post Installation Data Validation: Charges and Payments SQL Scripts ................................................................................................ 72

8.7 Active Directory Setup & Log-In........................................................................................................................................................... 72

8.8 If SSL Used on Web or Report Server: Enable SSL Certificate for EPSi ............................................................................................. 73

8.9 Final Configuration of SSRS and G/L Reporting .................................................................................................................................. 74

8.10 Defining Data Studio Network Shares ............................................................................................................................................... 77

8.11 Configuring Data Studio, The Task Engine (Part 1) .......................................................................................................................... 79

8.12 Configuring DataStudio (Part 2) – Configuring the Data Store ......................................................................................................... 82

8.13 Configuring DataStudio After ‘Separate Restore of PMDataStudio’ ................................................................................................ 85

8.13.1 Restore of PMDataStudio (or equivalent) Completed .................................................................................................................... 85

8.13.2 Launch SSMS and connect to the EPSi Database Instance ............................................................................................................ 85

8.13.3 Edit the TaskEngines Table ............................................................................................................................................................ 86

8.13.4 Edit the Locations Table ................................................................................................................................................................. 86

8.13.5 Edit the NetworkShares Table ........................................................................................................................................................ 87

8.13.6 After Data Edits, Verify PMDataStudio ServiceBroker is Functioning ......................................................................................... 87

8.13.7 Restart the Data Studio Task Engine Service ................................................................................................................................. 87

8.14 SQL Server Maintenance Plan ........................................................................................................................................................... 88

8.15 Re-Running Report Conversion Utility .............................................................................................................................................. 88

8.16 Access SSRS Log Files ...................................................................................................................................................................... 90

8.17 Configuring EPSi Report Auto-Email Functionality .......................................................................................................................... 90

8.18 Duplicate MSDTC CIDs on Servers .................................................................................................................................................. 90

9 Perform Functional Sanity Checks ............................................................................................................................................................... 92


9.1 Perform Checks on the Applications in the EPSi Portal – Send BasicFunctionalityTest Document .................................................... 92

9.2 Test Workstation Applications on Database Server ............................................................................................................................... 96

9.3 Test a Workstation Application.............................................................................................................................................................. 96

10 Appendix A: Current EPSi Version is 7.X – Additional Tasks .................................................................................................................... 97

10.1 Current EPSi Version is 7.5.124 ......................................................................................................................................................... 97

10.2 Current EPSi Version is 7.5.125 ......................................................................................................................................................... 97

10.3 Current EPSi Version is 7.5.126 or 7.5.127 ..................................................................................................................................... 97

11 Appendix B: Known Installation Issues and Errors .................................................................................................................................... 102

11.1 Checking Table Partitioning ............................................................................................................................................................. 102

11.2 Wix Log: Error … Failed to install MSI Package ........................................................................................................................... 102

11.3 Uninstall Issues ................................................................................................................................................................................. 102

11.4 PLA Patient Search Issues ................................................................................................................................................................ 105

11.4.1 Error Message: “No Active Execution Server Could Be Found” ................................................................................................. 105

11.5 Trouble-shooting Legacy Reporting ................................................................................................................................................. 107

11.5.1 Multiple Web Servers Environment: Legacy Reporting Does Not Work .................................................................................... 107

11.5.2 Portal Log-In Account Gets Locked Out ...................................................................................................................................... 107

11.6 Installation Fails: Failed to Execute/Install MSI package EpsiWebServerProduct ......................................................................... 108

11.7 GL Reporting Issues: Recreate SSAS Database ............................................................................................................................... 109

11.8 Cube Reporting Failing with “An Error Occurred Within the Report Server Database” (CLI Mentioned) .................................... 109

11.9 Data Studio Data Loads Not Working: Network FileShare Changed .............................................................................................. 110

11.10 EXECUTE Permission Denied on object 'xp_sqlagent_notify', database 'mssqlsystemresource', schema 'sys' .............................. 113

11.11 Clearing DataStudio Schedule Hung/Canceled ................................................................................................................................ 114

11.12 SSRS/GL-Reports Fail: Logon failed for unattended execution account ......................................................................................... 116

11.13 Report Server Event Log Message: The found version is xxxx; The expected version is xxxx ..................................................... 116

11.14 SSRS and/or GL Reports Error: Cannot create a connection to data source EPSIWork ................................................................. 117

11.15 Reporting Services SSRS: Removing SSL Configuration ............................................................................................................... 120

11.16 G/L and Cube Reports Don’t Process............................................................................................................................................... 122


11.17 EPSi Reports Don’t Save: Transaction Manager is Disabled ........................................................................................................... 123

11.18 MS-DTC Issues: Duplicate CIDs ..................................................................................................................................................... 124

11.19 RPC Server NOT Available ............................................................................................................................................................. 125

11.19.1 Overview ................................................................................................................................................................................... 125

11.19.2 Error RPC Server Not Available ............................................................................................................................................... 126

11.20 Problem with Legacy (Costing) Reporting: “Login failed for user EpsiSupport” ........................................................................... 126

11.21 Login Account Cannot Connect to DB Server From Remote Server/Client .................................................................................... 127

12 Appendix C: 8.X Upgrade Procedures........................................................................................................................................................ 131

12.1 Checking the Status of Report Conversions ..................................................................................................................................... 139

13 Appendix D: SSL Configuration within EPSi ........................................................................................................................................... 140

13.1 Viewing SSL Setup for EPSi ............................................................................................................................................................ 140

13.2 Appendix E: Viewing SSL Certificates with MMC Utility ............................................................................................................. 143

14 Appendix F: Creating SSAS Database ....................................................................................................................................................... 144

14.1 To remove a SSAS Database ............................................................................................................................................................ 144

14.2 To create a new SSAS Database ....................................................................................................................................................... 144

15 Appendix G: Migrating / Upgrading EPSi Versions Using SQL Server 2016 ........................................................................................... 147

15.1 Client Upgrade is Migrating from EPSi Version 7.5FP1 ................................................................................................................. 147

15.2 Client Upgrade is Migrating from EPSi Version 7.5FP2 ................................................................................................................. 147


1 Introduction

1.1 Overview

This document is intended to be used as guide and checklist for the installation of EPSi Version 16.3. Please verify that the pre-installation and configuration tasks are completed before beginning the EPSi installation. At least one month prior to any EPSi installation, please consult the “EPSi_16_3_PreInstall_Guide” before beginning the procedures listed in this document.

1.2 Assumptions and Notes

All pre-installation tasks have been completed successfully.

If a remote installation is to occur, install technicians will have remote access to all servers involved in the installation.

Installation technicians have administrator privileges for all applicable EPSi servers (login account is in the Local Administrators group.

The Windows account of the person running the install must be SQL Server sysadmin role member.

Current EPSi Version must be 8.X or higher. If the EPSi Version is less than 8.X, See Appendix A.

Install technicians have familiarity with Installing applications on Windows Servers.

Install technicians have familiarity with SQL Server operation and configuration.

Install technicians have familiarity with SSAS and SSRS installation and configuration.

Previous experience with the EPSi configuration, operation, and trouble-shooting.

1.3 Using SQL Server 2016 During 16.3 Upgrades

If the current EPSi version is 7.5FP1 or higher, and the installation is defined to upgrade to EPSi 16.3+ and the client is using SQL Server

2016, see appendix (Appendix G) involving upgrades using SQL Server 2016.

2 EPSi Down Time Begins: Final Web Server(s) Preparation If the installation involves a production environment, there are several tasks that require EPSi operations to be stopped:

Step

# Task Web-Server 1 Web-Server 2

1. Send out announcement to all EPSi users to exit the system. You may want to

verify that all users are out of the system. (DBA can do this, or use CITRIX server

Computer Management to forcibly remove user connections to EPSi. Prevent users

from accessing EPSi by disabling URL access to the portal. (rename, redirect, etc.)


Step #

Task Web-Server 1 Web-Server 2

WARNING: Any user attempts to access the EPSi system during an installation may

cause installation failure. 2. Verify all EPSi batch jobs and other batch jobs that affect EPSi are disabled.

3. Verify all applicable EPSi Database jobs are disabled and scheduled database

backups are disabled.

4. Verify all system administrators are aware of the EPSi implementation and will not

interfere with the EPSi installation.

5. Un-install the current EPSi system (if it has not been completed) by opening the

“Add and Remove Applications” window; then right click on Allscripts EPSi

Server Software and select “uninstall.” You may perform “simultaneous”

uninstalls on multiple web servers.

Once the uninstall is successfully complete, refresh the screen to verify ALL

components of EPSi software have been uninstalled.

6. If you experience difficulty uninstalling EPSi, refer to Appendix B (Trouble-

shooting steps). One item to check: the login account you are using to uninstall

EPSi should be the same account that was used to run the previous installation. We

believe some registry settings are not removed if you use a different account to

uninstall EPSi than was used to install EPSi.

7. On each web/report server, go to: [drive]\inetpub\wwwroot\epsi. Verify that the

“DLL” folder has been removed. If the “DLL” folder is present, delete it

8. If you are upgrading the EPSi system that is currently on 7.5FP1, you must

upgrade the environment to 7.5FP2 before you can continue. If you are

upgrading the EPSi system that is currently on 7.5FP2, you must upgrade the

environment to 8.X and then 16.1 before you can continue with the 16.3

Installation. If you have not already upgraded the EPSi environment to 8.X,


Step #


you must refer to Appendix A (or 8.X Installation documents) to perform that

upgrade. Once the 8.X upgrade is successful, return to the Pre-Install checks in

the previous sections of this document and verify the pre-install checks and

tasks have been completed. 9. REBOOT / Restart each web server AFTER the EPSi Un-install is successful.

10. Verify all EPSi COM components have been removed: Under Administrative Tools /

Component Services / Computers / MyComputer / COM+ Applications: EPSi

Components Should Not Be Present

11. NOTE: if multiple web servers are part of the EPSi server architecture, which

web server will have the Output Share? (only one can be designated)

In 16.2 the EPSi Install Configuration Manager application was added. This utility is used to build the client configuration file that will be

referenced during the installation process. Previoulsy, these fields were populated durign the install. By using the utility, many of the fields

required for the install will be populated. The installer will read the saved configuration file. This will help reduce errors during the process.

Configuration files can be built for TEST or PROD environments.


Click Install to start the Config Server Software Setup


Click Next to start the pre-install validation


The pre-install process is validating user accounts, server settings, and third party configurations.

This screen may not display if there were no Errors or Warnings. All Errors would need to be addressed.


1. User will need to log into the web server with the Service Account and/or Install account.

2. The configuration file needs to be located in the same folder as the web and/or config bundle.

3. The config bundle can be executed as a stand-alone option to preconfigure required third party applications.

If you want the install to honor the configuration file, the configuration file must be in that same folder as the install.

If not, it will just populate the third party applications. Items below will be automatically set up based on configuration file and if

they can be done without the config they will be.

ActiveReportViewer.msi

ApplicationInitialization.exe

install_flash_player_22_active_x.msi

Silverlight_x64.exe

NET 4.6.1 (Currently it seems like a reboot is in order to fully install)


IIS

DTC

App Pools

.NET 4.0 ISAPI & CGI

Powershell


3 Running the 16.3 Web Server Installation (WebServerBundle.exe)

This is the WebServerBundle.exe that installs EPSi software on each of the web servers. This bundle will reference the values that were

entered in the configurator utility.

Step

# Task Web-Server 1 Web-Server

2 After the web server has been rebooted and all previous EPSi software has been

removed, login into the web server with the appropriate login account.

To prevent EPSi client connections from interfering with the upgrade/ installation,

open IIS and STOP the Default-App-Pool. Remember to restart this App Pool before

doing sanity checks of the EPSi system.

To start the installation EXE: locate WebServerBundle.exe, and launch this

executable.

The following dialog appears: Select the Install Button

The EPSi Web Server Setup Wizard dialog displays; select the Next Button

(see below)


Step #


Designate the installation directory on the webserver. C:\inetpub\wwwroot\EPSi is a

common location, but this location should have been identified a day or so prior to

the install. If you want to disable the Database Updater Install, you can do so, it is

only required to be installed on one server and run once..


Step #


If a subset of EPSi features will be installed, this is a step where you may identify

what features will/ will not be installed. After making the desired selections and

identifying the install directory, select the Next Button

Type in the SQLServer name and the EPSi Database Name in the text boxes

provided in this dialog:

If an admin account other than EPSiAdmin will be used for the installation, select

the option “Use Specific SQL Server Account” and type in the account name and

password. Then select the Next Button to proceed.

This option will be pre – populated based on the configuration file. For each web

server installation, this URL will be the primary web server URL. Do NOT

reference the Load Balance Server. Example: http://stl-webk2qa Select the Next

Button to proceed.

http://stl-webk2qa/


Step #


The next dialog, will be pre-populated based on the configuration file.

Name\Domain-ServicesAccount being used by the installation. Example

MyDomain\ServerAccountId Select Next Button:

The SSAS (Analysis Server) will be pre-populated based on the configuration file.

Select the Next Button to proceed


Step #


EPM Portal Server and Database designation: Select Next to Proceed

EPM Reporting Software Server and Database designation: Select Next to Proceed


Step #


EPM Data Studio Server and Database: verify the correct server and database and

Select Next to Proceed


Step #


The next dialog completes the dialog prompts for the initial installation information.

If you need to return to a previous screen, you can select the Back Button. If you

need to cancel the entire process you can select the Cancel Button.

If you are ready to proceed with the installation, select the Install Button. From this

point on, if you need to stop the installation you will need to run the Add/ Remove

Programs process if you need to restart the install process from the beginning.

The Web Server process should proceed and notify you of any issues or errors. If

issues do occur, the EPSi Install provides log files in following folder:

C:\Users\<userAccount>\AppData\Local\Temp\Allscripts_EPSi_Server_Software

_yyyymmddtime.log. There may be a series of Allscripts log files. Make sure to

check the date/timestamp for the date and time of the current installation.

All web servers will need the installation to run successfully until the EPSi Database

Update Utility (EPSi DBUpdater) is ready to launch. (the following dialog presents

the initial screen of the EPSi Database Update Utility.)

The first part of the EPSi installation is complete when the “Database Update Utility”

dialog displays. At this point in the installation, EPSi files and folders have been

copied to the web server, web services have been setup, and general EPSi

configuration has been completed.


Step #


The Database Update Utility can be stopped by selecting the Close Button. Close the

utility only if you have already run the Database Update Utility on another web

server.

If you want to continue the installation with EPSi Database Update Utility, Enter the

DB Server name and instance and provide the EPSi main database name. In many

cases this name is similar to XXXXX_System. Select the Next Button.

The following dialogs will display if you are closing out of the EPSi Database

Update Utility without proceeding to run the DB Updater part of the install:


Step #


The above two dialogs will present indications of errors or will present the messages

that the installation is successful. If errors occur, investigate and resolve issues

before proceeding with the installation.

The next screen verifies what database version the install sees and what the next

database version will be.


Step #


In the next screen confirm the names of the Portal, Reporting, and DataStudio database:

The next screen confirms Data Studio share and paths:


Step #


The next screen displays the partitioning method that the installation will use. In order to use Table Partitioning, the SQL Server must be Enterprise Edition or Developer Edition.

The next screen will display the results of the Database Validation processes. If any of these checks return as failed, you should not proceed with the installation until the issues are resolved:

The next screen displays a summary of all of the options and selection-choices made in the DBUpdater screens. Review the options presented


Step #


and choose the back button to change any of the selections: Last Chance to Change DB Updater Settings!

The next screen displays the progress and results of the database

updates for all EPSi databases. If a warning or failure occurs, you may click on the buttons for the perspective database and view information on the related issue. If a warning occurs, you should take note of the details of the warning. These warnings indicate information related to issues that do not prevent a successful installation. However, any failure or error indications dictate cause for issue resolutions before the installation can be regarded as complete and successful.


Step #


If no errors or failures have occurred, you may consider the DB Updater

complete. Click the “Close” button and, unless you are running the DB Updater independently of the EPSi installation, the installation will continue with very important installation tasks. It is possible the install could still fail.

If the installer completes successfully you will see a screen similar to this:


Step #


And a follow on screen will

display. You may see this screen if background tasks are in-process:

The last setup screen to display will look similar to this:

Remember: this screen may display successful even though the DB Updater

indicated errors. If this is the case, you may launch the DB Updater independently of


Step #


the overall installation: correct the DB Updater Issues and rerun only DBUpdater.

See the next section to run DB Updater independently of the WebServiceBundle. ?? Re-Establish the Reporting Output in IIS: (for legacy reporting & load balancing

server configuration)

1. Start IIS (Administration Tools)

2. Navigate down to the Default Web Site\Output Folder

3. Right click on the Output Folder

4. Select Manage Application \ Advanced Settings

1. In the Advanced Settings Dialog, edit the Physical Path to specify the UNC

to the Web Servers Output Folder. (all web servers should use the same UNC

and path designation). Select the OK Button to save.


Step #


2. Restart IIS

1. Within IIS – Select the Web Server in the Tree

2. Under the Actions Menu Select “Restart”


4 Running the Database Update Utility Independent from WebServerBundle. This utility can be run as a stand-alone installation or as part of the overall EPSi installation. The database update utility may be run on a web

server or on the database server. When doing an EPSi upgrade, the utility only needs to be run once - on one web or report server. This

executable will update EPSi databases with settings and configuration required for the current EPSi version.

Step

# Task Web-Server 1 WS 2

1) If the Database Update Utility is being run independently from the at-large EPSi Installation,

verify it is launched after the Web Server installation is successfully complete.

To run the utility manually, locate & launch the EPSi Database Update Utility: located in

XX\inetpub\wwwroot\EPSi\ Tools\DBUpdate\ EPSiDBUpdater.exe The following screen will

appear when you launch the EPSi DB Updater.

2) You may choose to stop the installation at this point: the above screen indicates the EPSi

Database Update Utility is beginning. When multiple web servers are part of the installation,

you may choose to install the code-only and stop at the above screen (click the Close button).

3) If you choose to continue with the DB Updater installation, the rest of the screens and dialogs are

shown in the previous section. Please refer to those instructions.

4) When EPSi Database Update Utility has completed updating all databases, the installation

displays a grid of database update results. It is possible that a single database update may fail

while others succeed. If all updates are successful, select Next to Proceed. Otherwise,

troubleshoot any problems that should occur: Select “View Log” to view the log file for the

updating of each DB section: EPSi, Reporting, DataStudio, EMD, PRD, etc. Depending on the

size of the EPSi – EMD – PRD – Reporting – DataStudio databases, the database updates may

take from 10 minutes to 3 or 4 hours.


Step #

Task Web-Server 1 WS 2

5) EPSi Database Update Utility creates log files in the following path:

<drive>:\inetpub\wwwroot\EPSi\Tools\DBUpdate.

6) If EPSi Database Update Utility completes successfully, but the overall install indicates the

SetUp Failed, click the link on the SetUp Failed dialog box. This action should open a log file

(a WIX log). Scan through the log file until you find the text “ <error>” or <err>. If the log file

indicates that the EpsiWebServerProduct.msi failed to install, this issue has occurred


Step #


intermittently during 8.0.11 installs in the QA environment. One solution to this issue: make

sure all users cannot access EPSi while the installation is in progress. The error is likely due to

EPSi services attempting to process while the installation is in progress. For further guidance on

handling “msi” failing to load errors, consult the Trouble-shooting section in Appendix B. 7) If EPSi Database Update Utility completes successfully and the overall install indicates Setup

Successful, then you may proceed to the “Post Installation Technical Tasks” section in this

document before setting up Desktop Applications on workstations. Remember, to install and

configure a few workstations to verify workstation access to EPSi. This can be done as part of

the “Sanity Check” process.

1) The first part of the EPSi installation is complete when the “Database Update Utility” dialog displays. At this point in the installation, EPSi files and folders have been copied to the web server, web services have been setup, and general EPSi configuration has been completed. The start of the DB updater process begins with the following dialog:

Enter in the EPSi Database Server Name and the EPSi main database name (PM_System) and click the next button.

2) The next screen verifies what database version the install sees and what the next database version upgrades to:


3) In the next screen confirm the names of the Portal, Reporting, and DataStudio database:


4) The next screen confirms Data Studio share and paths:

5) The next screen provides you with the opportunity to specify the server name and database name for the HIPAA Audit Logging Database. If your institution uses the HIPAA logging functionality, EPSi recommends that you place this database on a separate server from the EPSi main databases.


6) The next screen displays the partitioning method that the installation will use. In order to use Table Partitioning, the SQL Server must be Enterprise Edition or Developer Edition.

7) The next screen will display the results of the Database Validation processes. If any of these checks return as failed, you should not proceed with the installation until the issues are resolved:


8) The next screen displays a summary of all of the options and selection-choices made in the DBUpdater screens. Review the options presented and choose the back button to change any of the selections:

9) The next screen displays the progress and results of the database updates for all EPSi databases. If a warning or failure occurs, you may click on the buttons for the perspective database and view information on the related issue. If a warning occurs, you should take note of the details of the warning. These warnings indicate information related to issues that do not prevent a successful installation. However, any failure or error indications dictate cause for issue resolutions before the installation can be regarded as complete and successful.


10) If no errors or failures have occurred, you may consider the installation as complete. Click the “Close” button

11) If the installation is regarded as successful, DBUpdater will present the following final screen. If the install has detected major issues, this final screen will present an “Installation Has Failed screen”.

Any errors that have occurred during the updates should be addressed as soon as possible. Warnings should be carefully addressed as well. Consult Appendix B in this document for trouble-shooting assistance. Possible issues: there may be configuration steps missed or not completed correctly: please consult the Pre-Installation Guide for configuration procedures. Please contact EPSi Support for any issues or concerns that you cannot solve.

5 Payment and Charge Conversions (8.X Upgrades) If you are running and 8.X Upgrade, the payment and charge conversion processes would occur after the DB Updater completes successfully.

You can check on the status of the conversion processes by running the following query on the EPSi ‘main’ database:


select * from dbo.T_PARTITIONED_TABLE_CONVERSION_LOG order by stepid desc

5.1 Errors in Payment and Charge Conversion Processes

If an error occurs during the P&C Conversion Processes, rerunning the DB Updater will not rerun P&C Conversion. Multiple DB Updater

runs will not re-initiate P&C Conversions. If you need rerun or complete P&C Conversions, here are some steps to follow:

5.1.1 Run SQL Script Run this script to alter a stored procedure.

SET ANSI_NULLS ON

GO

SET QUOTED_IDENTIFIER ON

GO

ALTER PROCEDURE [dbo].[EPSI_CNV_TableHasRows]

(@TableName varchar(256), @HasRows bit OUTPUT)

AS

/*

ProcName: EPSI_CNV_TableHasRows

Author: Dan Carter

Function: Determines if a table has rows by checking SQL Server system tables. This is for use in the conversion of patient

partition data in 8.0. Since system tables are used, the row count is approximate, but since this is for conversion,

there are no data updates going on in the system.

Parameters: @TableName - Table to check to see if it has rows.

@HasRows - OUTPUT parameter set to 1 if the table has rows, 0 if it does not.

Modified: 01/18/2017 - Created.

03/14/2017 - Dan Carter Updates to not use system tables since get deadlocks when multiple conversion are running.

*/

BEGIN

SET @HasRows = 0;

DECLARE @Sql nvarchar(max);


DECLARE @ReturnValue int;

SET @Sql = ' if exists(select 1 from ' + @TableName + ') SET @Valout = 1; else SET @Valout = 0;'

EXEC @ReturnValue = [sp_executesql]

@Sql

, N'@Valout INT OUTPUT'

, @Valout = @HasRows OUTPUT

END

5.1.2 Run SQL Server Agent Jobs Run this SQL to determine what conversions failed: select * from dbo.T_PARTITIONED_TABLE_CONVERSION_STATUS

In SSMS, SQL Server Agent Tree, find and run the following agents (if not successful) by:

1. Right click on the job, and choose the START JOB AT STEP command

2. Monitor the processing in the window that appears

3. Make sure all steps of the job complete successfully

4. If a job failure occurs, investigate and correct the data or other situation


(reference the above figure for the following steps)

1. Run the Encounter Conversions (steps 1 & 2): verify successful completion.

2. Run the Actual Payments and EncounterRemits(steps 3 & 4): verify successful completion. (these two can be run simultaneously)

3. Run the IP and OP Encounter Conversions(steps 5 & 6): verify successful completion (these two can be run simultaneously)

4. Run Step # 7; verify successful completion.

5. Run Step # 8: verify successful completion.

5.2 Monitoring Data Conversions (SQL)

While Data Conversion is in process, monitor the job progress with the following:

use [] (Main EPSi Database)

select * from dbo.T_PARTITIONED_TABLE_CONVERSION_STATUS order by StatusChangeDateTime desc

select * from dbo.T_PARTITIONED_TABLE_CONVERSION_STATUS_DETAIL

order by StatusChangeDateTime desc


select * from dbo.T_PARTITIONED_TABLE_CONVERSION_STATUS_DETAIL where status = 'Converting'


6 Running the Report Conversion Utility After the DBUpdater completes successfully the WebServerBundle may launch the Report Conversion Utility (INETPUB\WWWROOT\

EPSi\TOOLS\REPORTCONVERSION\REPORTCONVERSION.EXE). Similar to the 7.5FP2 Upgrade process, this utility will allow the

install technician to define reports are converted and specify some parameters around the conversion process.

Before running the Report Conversion Utility:


Step #

Task Status /

Notes 1. Launch the EPSi Web Portal. Navigate to the menu Applications – Reporting Applications – Product Line

Analysis

2. Choose Report Administration – Reporting Services Configuration – Configuration. The Reporting Configuration Panel will Open.

3. Update any information in the panel as needed

4. Report Service Location. To update the url, there are two

components.


Step #

Task Status /

Notes 1 – The name of the server that has SSRS installed (This entry will be variable for each client): http://client-

Report-Server/

2 – The name of the virtual directory that was created during the SSRS configuration. Recommended

directory: ReportServer_EPSi. (Refer to the SSRS configuration guide for additional information/setup).

5. Report Builder Location. The URL entered in this field will be the repository for all of the custom built reports

in V7.5. Similar to the prior step, two entries are combined.

1- The Report Service location - http://client-report-server/ReportServer_EPSi/

2 – The default Report Builder path - ReportBuilder/ReportBuilder_3_0_0_0.application

The entry will be (the blue test will be variable for each client):

http:// client-report-server /ReportServer_EPSi/ReportBuilder/ReportBuilder _3_0_0_0.application

6. Apply the name of the (SQL) server that will be used to run SSAS – SQL Analysis Services. In most cases, it

will be the same as the SSRS server.

7. Apply the Domain, User ID, and Password for the EPSi service account.

8. Report Base Path. Please apply the entry: EPSi Reports.

9. After applying the correct values, please Save the settings (disk Icon).

Note – in some installations, the domain field is not required. If the configuration settings do not save, please

remove the domain and re-save the screen.

http://epsitst-db01/ReportServer_EPSi/ReportBuilder/ReportBuilder


Step #

Task Status /

Notes 10. Within the Report Configuration Menu: If multiple servers will be used to run reports, they can be added to

this node. It is recommended that all Reporting servers are added, web servers are optional. Select “Add.”

Enter the values as needed.

11. Once this Report Configuration is saved, proceed to the Report Conversion step. Note - Please verify with EPSi Support if any updated Report Conversion files are required before initiating

the PLA Report Conversion. If so, please download the files and apply them based on the instructions in the

accompanying ReadMe

12. Select the System to Convert, ‘Perform Detailed Logging’, and conversion details

The System to Convert selections that need to be converted are based on the original EPSi version that is being updated from.

Original EPSi version being updated

Systems that require Conversion

7.2 or earlier G/L Budgeting; Capital Budgeting; Activity Costing; Payroll Budgeting; Product Line Analysis; Common

7.5 - 7.5 FP1 (7.5.0 - 7.5.124)

G/L Budgeting; Capital Budgeting; Activity Costing; Payroll Budgeting; Common

7.5 FP2 - 16.1 (7.5.125 – 16.1.01)

Capital Budgeting; Activity Costing; Common

16.2 or later No conversion needed


Step #

Task Status /

Notes

13. Here are recommended selections for each system to convert:

G/L Budgeting Payroll Budgeting

Product Line Analysis

Capital Budgeting

Activity Costing

Common

Global Templates Global Templates Global Templates Custom Columns Custom Columns Custom Columns Custom Column

Predefined Populations



Reports – Convert all reports


Reports – Convert all

reports




Report Schedule Groups






Report Security Report Security Report Security Report Security Report Security Report Security Product Lines Clinical Analysis Contract

Modeling

External Lists Data Manager

14. When all selections are made, click the Convert button Conversion Tip: Not every item in the conversion will be successful. Most likely, this is caused by a format/data condition within the custom column or custom report. Please refer to Step 30 on how to complete/review the Legacy Conversion Report.

15. If only certain reports need to be converted, choose the “Select Reports” options. Move the necessary reports to the right side and choose “Convert.”

16. Log files will be created at INETPUB\WWWROOT\ EPSi\TOOLS\REPORTCONVERSION

17. If you are running a 7.5FP2 Upgrade and a prior release of V7.5 was applied, the Product Line Analysis conversion utility has already been executed, select the Product Line Analysis conversion, then select the “Mark System Complete” option, to remove the PLA conversion from the list of available processes.

18. If you need to undo a conversion complete, you can refer to the PMReporting DB, mark the following table with zeros:


Step #

Task Status /

Notes use [pmreporting]

update t_rs_md_system_module_site_info set [IsLegacyConversionComplete] = 0 where SystemModuleID = 6

6 = payroll

1 = gl

6.1 Monitoring Report Conversions


7 Setup Workstations

Step #

Task Workstation Names If the EPSi desktop software is to be installed directly on

workstations: copy the desktop installation exe to each EPSi

workstation. (The client is responsible for installing this software

on their workstations.)

DesktopBundle_16_X.EXE is to be used for installing the EPSi

desktop software.

Verify the installation of the desktopbundle on at least one workstation. You can perform a connection check to the EPSi portal as well as other sanity checks to verify the proper operation of desktop functionality.

If the EPSi Environment uses a Citrix server to provide desktop

access to EPSi, consider the following:

1. Has the Citrix server been successfully used with other

EPSi installations? If not, additional tasks may be

required to verify the proper operation of Citrix

connections. Also, (if not), DataLoader.ini and

DeptManager.ini will need to be configured to point to the

correct database server, database name, and web server

URL.

2. If the Citrix server has been used previously to configure

EPSi workstations, copy the Desktop Application

Software from the source location to the correct folder on

the Citrix server.

If there is a problem copying desktop application software to the

Citrix server, there may be end users still connected to EPSi. To

remove existing Citrix connections:

1) Open Administrative Tools, ComputerManagement,

Shared Folders, Sessions. Identify any open sessions

there and an administrator should be able to close any

open sessions.

2) If you are unable to close sessions via the Computer

Management tool, you may need to launch the Citrix

Delivery Services Console to close any open EPSi

workstation sessions.


7.1 Desktop Applications Setup

This section is intended to provide detailed instructions for the installation of the EPSi Desktop Applications.

7.1.1 Assumptions All prior versions of the Desktop Applications have been removed via the Control Panel.

The SQL Server and Database Names will be needed during the Installation.

Please have the Network share directory path if you are installing the EPSi applications on a Network drive.

7.1.2 Minimum Desktop Requirements 1. Windows 7.X, 8.1.X, or 10.X 2. “Client for Microsoft Networks” installed as a network client. 3. IE 11 is required. 4. TCP/IP protocol 5. Microsoft .NET Framework 4.6.1 (Note – if the user/workstation will not be using click-once applications (console

applications such as Clinical Analysis, Balance Sheet, and Product Line Analysis), the workstation may not need 4.6.1. Contact EPSi Support for detailed analysis.

6. Smaller Display – Set to 100% within the Control Panel.


7.1.3 DTC – Distributed Transaction Coordinator Settings In order to successfully use the EPSi Console applications, user PC’s will need to have two DTC settings applied.

DTC Setting 1 – Component Services 1) Go to the Control Panel and double click the Administrative Tools. Double click Component Services.

2) Expand Component Services->Computers->My Computer->Distributed Transaction Coordinator -> Local DTC.

3) Right click on Local DTC and select Properties.

4) Click on the Security Tab.

5) Check the 5 highlighted checkboxes below and click Apply, then OK.


When prompted with a warning that all MSDTC services will be stopped and restarted, click Yes to proceed. 6) Click OK on the MSDTC restart confirmation screen stating the MSDTC service has been restarted.

7) Close the Component Services.

DTC Setting 2 – Windows Firewall 1) Go to Start – Search. Enter “Firewall’ 2) Select Allow a Program through Windows Firewall

3) Select Change Settings

4) Check the boxes for:

i. Distributed Transaction Coordinator

ii. Domain

iii. Home/Work

iv. Public

5) Close the Application.

7.1.4 Desktop Installation

Download the Desktop Client Full Install from the EPSi updates site and save to the desktop or insert the EPSi installation CD. Double-click on DesktopBundle.msi. This will initiate the setup for the suite of desktop applications and install the necessary files to the computer.

Notes:

The version of the Desktop Applications on the installation CD may not always reflect the most recent version available.

If there are any questions about the version of the Desktop Applications that should be installed, please contact EPSi Support.


12) Double-Click on the DesktopBundle.MSI to launch the Setup Wizard.

The Desktop Install will verify that all prerequisites are present

Click “Install”


Click “Next”

13) Select the EPSi installation directory and the Modules that will be installed. Note – All modules are defaulted to be installed.


Click “Next”


14) Please insert the required variables:

a. EPSi SQL Server Name (Include any Instances).

b. EPSi database Name.

c. SQL Server user account user name

d. SQL Server user account password

Click “Next”


15) Enter the name of the URL (typically name of Report Server or Load Balanced Web Server URL name)

16) Please choose between a “Local” and “Network” installation of Desktop Applications Software.

Local Installation – All files will be installed on the client computer.

o Note – The user must have R/W access to the install location on the computer.

Network Installation – Support files are installed on the client computer and shortcuts to EPSi Application shortcuts are created.

o Note – If a Network Installation is chosen, the shared path must be set up prior to install. All users will need R/W access to this location.


Click “Next”


17) The installation process will begin.

Click “Next”



Choose “Finish.”

18) The Desktop Install will complete the process. Choose “Close.”


19) Please launch the desktop applications by accessing them from the install location.

20) Please apply any necessary HotFixes to the desktop applications.

Note – A HotFix may not exist for every release, or may be posted to the download website as needed.

21) No reboot of the web server is necessary, but it is recommended. If you don’t reboot the web server, you may have to manually launch the EPSi services (Administrative Tools\ Services).

7.1.5 Desktop Application INI files If a client needs to edit the setup of the EPSi Desktop applications you accomplish this by editing the Dataloader and Deptmanager INI files.

Usually these are located in the C (or D or E):\Program Files (x86)\Sunrise folder, along with the EXE files for all the EPSi Desktop

Applications. You can edit these files with the correct DB Server name, main EPSi database name, and Web URL name. Here is an example

of what these files can be contain:


If the client is using SSL (Secure Socket Layer) authentication on the Web and Report servers, then the URLHost definition in the Desktop Application INI files must specify the fully qualified web server name along with the https prefix. Example:

UrlHost=https://Svdclepsitstt01.domainname.org

7.2 Setting Up New EPSi Workstation Accounts

When setting up new EPSi users, you can define a new EPSi user account in the Security Application. Make sure the user account has a

corresponding SQL Server user account.

You may need to run the stored procedure to give all user accounts the roles they need: exec EPSI_SEC_MoveUsersToRoles <main db>

If you are creating/configuring a new EPSi account, in addition to the above steps, you will also need to give the account access to data in the

EPSi system.

1) Launch the Security Application as an admin.

2) Select the “System Access” menu item

3) Choose the User Privileges Option

4) Choose one System Modules

5) Select the Rows (of data on the left) and transfer them to the right side (Privileges List)

6) Click the Save Button to save the data access

7) Repeat for other System Modules

See screen capture following:


If data is not provided/matched to a user, an error message like the following can occur:


8 Post Installation Technical Tasks These are post installation configuration checks and tests that the installation technician should perform to verify the proper operation of the

EPSi architecture.

8.1 Prior to 16.1.01 CU3: Run Patient-Merge Trigger Script

In late May 2017, we found that two triggers needed updated. The SQL script is named 161 Encounter Trigger Patch.sql. This script is found

in all the 16.1 install file folders under the EpsiInstallers share. Please run the script for all installation versions prior to 16.1.01 CU3.

8.2 General Technical Tasks Step

# Task Web-Servers

1) Verify in IIS that the Default App Pool is running (you may have STOPPED it.)

2) Check the EPSi main database, T_VERSION table to insure the correct installation version is

now listed in the table.

3) Check the Portal database, T_MODULE table and verify the module version is correct for all

the applicable EPSi modules.

4) Verify the Appropriate Windows Services are running on each Web/Report Server. (only one

set of Allscripts Services are running among all Web/Report Servers). You should “Disable”

Allscripts services on any web or report servers where fileshares do not exist (see next

section). Some EPSi services can run concurrently on two or more servers, but caution should

be used. Analysis should be done before the installation to identify what services run on

which servers.


Step #

Task Web-Servers

5)

When the EPSi installation is complete, NO Allscripts services will be set to a RUNNING

status(unless you reboot the server). In a typical single web server setup, all of the Allscripts

services are running. If there are multiple EPSi web servers, the usual EPSi configuration

specifies that each Allscripts windows service be running on only ONE web server; therefore,

disable Allscripts services on all web servers except one server.

NOTE: if Legacy Reporting does not work during Sanity Checks, you may need to start the

Report Refresh Service on the server(s) where services are disabled. Let the service run for

approximately 30 seconds. Then shut the service down and disable again.

8.3 Optional: Check Allscripts Windows Services Log Files & Windows Event Viewer Step

# Task Web-Servers

1) Each of the Allscripts Windows Services writes log files to log files under the ..inetpub\ wwwroot\

EPSi\Services\<service-name> (see screen capture to the right). As users access the EPSi system,

verify these logs are being updated.


Step #

Task Web-Servers

2) Open the Event Viewer and check for any Web Server Errors that may have occurred on each Web

Server during the installation of the EPSi System.

8.4 Suggested Check: Check IIS DefaultAppPool

One server must have three fileshares setup allowing the ‘Everyone’ user to have read, write, and execution permissions. These fileshares are

used by the EPSi System for various reporting and output functions. These fileshares should exist on the server where the Allscripts

Windows services are enabled and running.

Step

# Task Web-Servers

1) In IIS, check that the Services Domain Account is setup for the DefaultAppPool in IIS.

2) DefaultAppPool, Advanced Settings:

1) 32 Bit Applications are Enabled


Step #

Task Web-Servers

3) IIS Services Check

Folders to check after EPSi Installation


Step #

Task Web-Servers

Each web/report server should have EPSi files copied in sub directories under ..inetpub\wwwroot\EPSi The Tools folder contains DBUpdater path. DBUpdater logs are located in this folder.


8.5 Suggested: Manually Check FileShares on the Report/Web Server

There are three file shares that should be setup co-located with server containing the EPSi Windows Services:

Step

# Share Name Servers

1) If the EPSi installation is setting

up EPSi on a web or report server

that has never contained EPSi, it

is likely that the file-share and

security setup will need to be

done on each fileshare folder.

These impact the operation of

Legacy Reporting.

Verify the Services Domain Account has FULL CONTROL privileges for each share and that

the Everyone Account has read, write, and execution permissions for each share

2) \\<server-name>\Output

On the server where the EPSi Scheduling Executor Service runs, this share must exist with EPSi Service Account having Full Control and the Everyone Account having read/write permissions.

(Usually C:\inetpub\wwwroot\Epsi\AspReportingManager\Output)

3) \\<server-name>\TaskOutputs

On the server where the Allscripts Data Studio Task Engine Service is running this share must exist with the EPSi Service Account having Full Control and the Everyone Account having read/write permissions. For EPSi 8.X and prior versions:

<Drive>:\inetpub\wwwroot\Epm\Services\AllscriptsEpmDataStudioTask-

EngineWinService\TaskOutputs For EPSi 16.1 and later versions:

<Drive>:\Inetpub\wwwroot\EPSI\Services\EPSIDataStudioTaskEngineWinService (this

should provide access to both subfolders TaskOutputs and Uploads

In general, these shares and services will all be located on the same server. The EPSi installation usually sets up these shares, but the rights

and permissions for each share are usually NOT setup. So, manually check these shares. To create shares on a Windows 2012 operating

system:


1) Open the Server Manager

2) Within the left Menu area, select File and Storage Services

3) Select the Shares Menu (on the left)

4) Select the Tasks Drop-Down Menu and choose ‘New Share’


8.6 Post Installation Data Validation: Charges and Payments SQL Scripts

Remember to perform the post-installation data validation SQL Scripts. Store the results in the same file (spreadsheet) that the pre-install data

was saved in. These queries are run against the main EPSi database; it can be name differently on client servers. (e.g. XXX_SYSTEM)

------------------------ C H A R G E S C H E C K S. Before and after

Select sum(numberOfUnits), sum(DetailTotalCharges) from T_IP_CHARGES

where postingdate >= '01/01/1900'

and postingdate <= '12/31/2017'

Select sum(numberOfUnits), sum(DetailTotalCharges) from T_OP_CHARGES

where postingdate >= '01/01/1900'

and postingdate <= '12/31/2017'

------------------------ P A Y M E N T C H E C K S. Before and after

Select count(*), sum(amount) from T_ACTUAL_PAYMENTS

where paymentdate >= '01/01/1900'

and paymentdate <= '12/31/2017'

8.7 Active Directory Setup & Log-In

The values in Italics are unique to each client.

Step #

Task Web-Servers

4) In SQL Management Studio, go to the EPSi database: CLIENT_SYSTEM.

5) Open the table: T_ACTIVE_DIRECTORY_LOGIN.

6) Insert the Domain Name (EX: DOMAIN.ORG).

7) Insert LDAP Value (EX: LDAP://LDAPSERVERNAME.DOMAIN.ORG). Please make the entry in CAPS and include the LDAP://

8) Inform all users to the following change. The new log-in page will be: http://WebServerName/homepage/aspx/loginAD.aspx.

NOTES:


By design, Active Directory (AD) will only authenticate against the web applications, NOT the desktop applications.

The EPSi user id in the users table must be the same as the active directory login id.

The userid will authenticate against the EPSi/AD id, the p/w will authenticate against the AD password.

If multiple entries are necessary in the table, the web application will have a domain dropdown that the users will also need to select.

8.8 If SSL Used on Web or Report Server: Enable SSL Certificate for EPSi

If SSL is setup for this EPSi environment, after the EPSi upgrade you will need to enable the SSL certificate for each EPSi web and report

server

1) Verify the client has obtained a valid SSL Certificate and has been configured IIS (on each web and

report server for this certificate). See Appendix for SSL Setup and Configuration.

2) In order to enable the SSL certificate, the Install-Config tool will need to launched (by the following steps) 3) Launch the command prompt (by running as an administrator) 4) If necessary, change the drive reference to reference the drive on the web / report server that was used to

install EPSi All examples below use the assuming of C:

5) Navigate to: C:\inetpub\wwwroot\epsi\tools\installconfigtool

V8.0 and V7.5 FP1 & FP2

1 - EPM: installconfigtool sslwebconfig /enablessl true /installdir c:\inetpub\wwwroot\epm

2 - EPSI: EPSi

V16.1.0.16348 & 16.1.0.1738

1 - EPSI: installconfigtool sslwebconfig /enablessl true /installdir c:\inetpub\wwwroot\epsi

V16.1.1.17108 and later (must specify DB Server Name and Main EPSi Database (Change made April 2017)

1 - EPSI: installconfigtool sslwebconfig /enablessl true /installdir c:\inetpub\wwwroot\epsi /databaseservername SQLSERVERNAME /databasename EPSIMAINDATABASE


6) If commands returned success messages, perform an IISReset command within the command window Verify the reset completes successfully

7) Attempt to login to the web based applications using the HTTPS protocol along with the certificate binding that was applied to the server. Example: https://Vap0216.Win.RWJUH.EDU/homepage/aspx/login.aspx (

Example of Log-in URL

i. Protocol: Https:// ii. Certificate binding: EPSI.corp.allscripts.com

iii. Web url: /homepage/aspx/login.aspx iv. Concatenated URL:

https://epsi.corp.allscripts.com/homepage/aspx/login.aspx v. Concatenated URL with Active Directory: https://epsi.corp.allscripts.com/homepage/aspx/loginAD.aspx

If SSL Activation needs to be removed: (EPM Changes applies to V8.0 and V7.5 FP1 & FP2)

8) Navigate to: C:\inetpub\wwwroot\epm\tools\installconfigtool 9) This will launch the tool that will allow for enabling / disabling SSL / HTTPS within EPSI 10) Please run the Disable commands for both folder sets (EPM & EPSI), as follows: 11) EPM installconfigtool sslwebconfig /enablessl false /installdir c:\inetpub\wwwroot\epm Success Message?

12) EPSi installconfigtool sslwebconfig /enablessl false /installdir c:\inetpub\wwwroot\epsi Success Message?

13) If both command returned success messages, perform an IISReset command within the command window Verify the reset completes successfully

8.9 Final Configuration of SSRS and G/L Reporting

Many upgrades or installations may utilize restored databases from another EPSi server region. In these cases, the SSRS databases are

restored into the new environment and tables. SSRS databases are usually included in the data restore process. Usually, the SSRS databases

are named ReportServer, ReportServerTempDB, or ReportServer_EPSI. The data from these tables will provide the information for SSRS

templates and folders.

https://epsi.corp.allscripts.com/homepage/aspx/login.aspx

https://epsi.corp.allscripts.com/homepage/aspx/loginAD.aspx


The setup of the Base Path (e.g. EPSi REPORTS) and all its contents may require setup via the EPSi Portal after the installation is complete.

This section will explain the tasks to configure and trouble-shoot G/L reports and SSRS during post-installation.

To configure and check G/L Reporting perform the following steps and checks: Step # Task Web-Servers

1) Launch the EPSi Portal

Example:

https://servername.domain/epsiportal/login.aspx

2) Access Reporting Applications, GL/Payroll/PLA

3) Select the Report Administration Menu (at the

bottom of the palette)


Step # Task Web-Servers

4) Expand the Reporting Services Configuration

folder, and select the Configuration Option… this

displays the Reporting Services Configuration menu

(see right)

5) In many cases, you will only need to open the

Reporting Services Configuration menu and click

the Save Command in order to set the base path

properly. Make sure the values in this display are

correct.

The values in this display are imported from the PMReporting database,

T_RS_MD_SERVER_CONFIG table. When you change the values in the

Reporting Services Configuration menu the changes are saved in this table.

The SSAS report displayed must in the screen (above) must be the SSAS

displayed in SSMS, and the service account must be an administrator of this

DB. 6) Check the Report Service Location URL in (UI)

Reporting Services Configuration (RSC) menu with

the Virtual Directory Value in Reporting Services

Configuration Manager (see right display)


Step # Task Web-Servers

7) The SSRS database is defined in Reporting Services

Configuration Manager, as well as the Service

Account that SSRS uses to connect to the database.

In the example, the ReportServer DB, must exist in

the EPSi Database Server and the service account

displayed in SSRS configuration (right screen) must

be an administrator/user of the database. This can

be checked in SSMS 8) In the (portal) Report Administration, Reporting

Servers display confirm the server that contains

SSRS is identified and “Enabled.” (see right)

9) If the SSRS databases have been restored from

another environment, you ensure the Custom RDL

gets published to the restored SSRS databases by

running the following query:

update T_RS_MD_SYSTEM_RDL_SITE_INFO Set LastPublishDate = '1/1/2000' After running this query, navigate back to the Portal Reporting Services Configuration display, verify the data is correct and Re-Save the display.

8.10 Defining Data Studio Network Shares

Frequently after upgrades, you may need to define new Network shares for DataStudio to use for data loads. Follow these steps to define new

shares:

1) Launch DataStudio (see screens on next page)

2) Launch the DataStudio Control Panel (See first red arrow)

3) In the bottom right corner find and click on the View Network Shares link (second red arrow)

4) Click on the Button at the top of the screen “Add Network Share”

5) Type in the pathing for the share \\servername\sharename\folder\folder and click OK



8.11 Configuring Data Studio, The Task Engine (Part 1)

This task can be accomplished when the client has a file that they want to load into EPSi:

1) Log into the EPSI web portal

**Note – Users must first have EPSI – Security module access to the Data Studio application before logging in. 2) Go to Applications – Admin Tools – Data Studio

3) Select the “Control Panel” button

4)

5) Go to Task Engines – View Task Engines (to check an existing engine) or Add Task Engine to add a new one

6) If you are viewing an existing task engine, the display should look like the following:


7)

8) To add a new Task Engine, Complete the fields on the New Task Engine screen and select OK to save the changes.

Name: Name of the Task Engine

Description: Brief Description of the Task Engine.

Name of the Server running the Data Studio: There should only be one web/report server running the service:

Allscripts Data Studio Task Engine Service. It should be disabled on all other servers.

MEF Path: Apply the following path – D:\Inetpub\wwwroot\EPM\Services\AllscriptsEPMDataStudioTaskEngineWinService,D:\inetpub\wwwroot\EPSI\Services\DataStudioTaskEngineTasks

This Status Icon indicates the Task

Engine ‘umcl’ is running on the

web server UMCPROD-EpsiW01


*** If the web software was applied to a different drive on the server, please ensure the correct drive reference is applied.

9) Return to the Task Engines Screen and select View Task Engine. The Red “S” in the status field means that the Engine

is not ready.

10) To make the Task Engine active, go to Start – Admin Tools – Services.

11) Restart the service: Allscripts Data Studio Task Engine Service

12) Return to the Task Engines Screen and select View Task Engine. Note the change in the Status field. The Task Engine

is now connected and is “Polling” the Allscripts Data Studio Task Engine Service.

13) Status field Key:


8.12 Configuring DataStudio (Part 2) – Configuring the Data Store

The second step in configuring the Data Studio is to direct the utility to the correct database. 1) Log into the EPSI web portal

2) Go to Applications – Admin Tools – Data Studio

3) Select the “Control Panel” button

4) Select the “View Data Stores” option by double-clicking.

5) Select (or filter) the “EPSI Database” entry by double-clicking.

6) Select “Add Location.”


7) Enter the values for the Location (any name, SQL Server, Instance – if necessary, EPSIAdmin userid, & PW for the

EPSIAdmin account. Test the connection, if it passes, select OK.

8) Return to the Control Panel. Select Data – Add Data Store

9) Change the reference to “File.”

These fields will need to be updated:


Once all of the fields are applied, select “Test Connection.”

The Test will fail if:

The servername\filepath\filename are not in the format displayed above.

The file path is not set up as a share with the correct permissions.

The file does not exist.


The file extension is not included.

8.13 Configuring DataStudio After ‘Separate Restore of PMDataStudio’

Some upgrades that move an EPSi System from 7.5.X to 16.X. When this happens, clients may not have worked with datastudio until 16.X is

installed in their TEST environment. When the EPSi Production upgrade occurs, their ‘live’ production environment may not have any

datastudio data and configuration, but their new TEST environment may have been configured with data that the client wants to include in the

new production environment. In these situations, install technicians may need to have the PMDataStudio database restored from a TEST

environment in order to provide the jobs and schedules configured in their TEST environment. This section describes the tasks that may need

to be completed after an explicit restore of the PMDataStudio database.

8.13.1 Restore of PMDataStudio (or equivalent) Completed Client DBAs can restore the datastudio database at several different points in the upgrade process. If the restore is completed after all EPSi

upgrades are performed, then some of the references in datastudio tables will need to be changed to reflect the different DB server name, the

possible different data studio share names, etc.

8.13.2 Launch SSMS and connect to the EPSi Database Instance You may want to check the data studio settings with the GUI application before this step – just to verify that data studio settings are now out-

of-synch with the new (restored) environment. If data studio settings are out-of-synch, data studio will not be polling, jobs/schedules will fail,

etc.

After verifying settings need changes, using SSMS connect to the EPSi database and expand the PMDatatudio database tree so you can

expose all the tables that are part of the PMDataStudio database.


8.13.3 Edit the TaskEngines Table When the PMDataStudio DB is restored the HostServer field will need to be updated to reflect the new host server (the server where the Task

Engine Service runs).

8.13.4 Edit the Locations Table The Locations Table will have at least one record designating a host database server. That record or two will need to be edited. In addition,

the name field in this table can be updated to reflect the correct server name. This is cosmetic and does not affect functionality.


8.13.5 Edit the NetworkShares Table The NetworkShares Table will have at least one record that will need the proper database server name applied.

8.13.6 After Data Edits, Verify PMDataStudio ServiceBroker is Functioning There may be other DataStudio Tables that need attention. After editing all tables, verify the DataStudio database service broker is running.

Without it running, the DataStudio service cannot communicate with the DataStudio database.

8.13.7 Restart the Data Studio Task Engine Service As always, after any changes to EPSi functionality, make sure you RESTART the appropriate EPSi service. For DataStudio functionality, the

appropriate EPSi service is the “Allscripts Data Studio Task Engine Service.”


8.14 SQL Server Maintenance Plan

The following tasks should be set up within a SQL Maintenance Plan.

8.15 Re-Running Report Conversion Utility

There may be times that certain reports to convert correctly. If you did not mark reports as COMPLETE by clicking the button “Mark

System’s Conversion Complete” then you should be able to launch the EPSi Report Conversion Utility manually (as administrator).

You will find the ReportConversion.Exe in the inetpub\wwwroot\epsi\tools\ReportConversion folder. This same folder contains detailed logs

of each of the report conversions.

If you marked reports as COMPLETE during the running of the Report Conversion utility, you can go back to the PMReporting database and

reset conversion as incomplete with the following:


1. Open SSMS and launch a Query Window for the PMReporting database (name may different for some clients)

2. update t_rs_md_system_module_site_info set [IsLegacyConversionComplete] = 0 where SystemModuleID = 6 (Payroll Reports) 3. For GL Reports adjust the Where clause to where SystemModuleID = 1


8.16 Access SSRS Log Files

For many issues involving SSRS, SSRS log file review can be a significant resource. SSRS log files are found SSRS Log Files at C or

D:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\LogFiles.

8.17 Configuring EPSi Report Auto-Email Functionality

1) Create an EPSI e-mail account within the domain (ex. [email protected]).

2) Within SQL Management Studio, open the email account table (T_EMAIL_ACCOUNT) within the main EPSI DB.

3) The following fields need to be populated:

EmailAccountID - This field will be automatically populated by SQL Server

SMTPServer – Please enter your organization’s SMTP Server

Account – Please enter the EPSI email address created in Step 1 above (ex. [email protected])

FromEmail -Please enter the complete email address for the account. (ex. [email protected])

FromDisplayName – Please enter the display name you wish to appear on emails sent from this account. ((ex. EPSI Info)

8.18 Duplicate MSDTC CIDs on Servers

PowerShell can check if there are duplicate MS-DTC CIDs on a list of servers:

$CIDs = Invoke-Command -ComputerName $servers -ScriptBlock { gci Microsoft.PowerShell.Core\Registry::HKEY_CLASSES_ROOT\CID | foreach { $_.Name } | Out-String -Stream } #Array of all CIDs on all servers $UniqueCIDs = $CIDs | select -Unique if($CIDs.Length -eq $UniqueCIDs.Length){ Write-SuccessMessage "All Server CIDs are Unique for Servers: $servers"; } else { Write-FailMessage "Found duplicate CIDs(4perServer), Investigate MSDTC on all Epsi-Servers!: $CIDs"; foreach ($cid in $CIDs){


Write-InfoMessage $cid; } }

Duplicate CIDs can cause DTC communication to fail among EPSi servers. Using the logic above you will be able to determine if duplicates

exist (there are four CIDs per server). Once you find which servers have duplicate CIDs, you can perform the following commands in a

command window, run as an Administrator:

1) On the server that has the duplicate CIDs, launch a Command Window as an Administrator

2) Run the command: MSDTC -UNINSTALL

3) Run the command: MSDTC -INSTALL

The above steps should reset the CID’s to a different set. You may have to run the reset process (above) on all servers that have duplicates.

Note also, that in some cases, you may have to manually delete CID entries in the Registry. The following procedures found at

http://www.wadewegner.com/2007/08/warning-the-cid-values-for-both-test-machines-are-the-same/

1. Use Add Windows Components, and remove Network DTC. 2. Go to the command line and run: MSDTC -uninstall 3. Go to the registry and delete the MSDTC keys in HKLM/Software/Microsoft/Software/MSDTC,

HKLM/System/CurrentControlSet/Services/MSDTC, and HKEY_CLASSES_ROOTCID (if they’re still there). 4. Reboot 5. Go to the command line and run: MSDTC -install 6. Use Add Windows Components, and add Network DTC. 7. Go to the command line and run: net start msdtc

http://www.wadewegner.com/2007/08/warning-the-cid-values-for-both-test-machines-are-the-same/


9 Perform Functional Sanity Checks

9.1 Perform Checks on the Applications in the EPSi Portal – Send BasicFunctionalityTest Document

A technician may connect to the EPSi Portal from any of the EPSi servers. It would be most helpful to connect to the EPSi Portal via a

workstation.

Step

# Task Web-Server 1 WS2

11-1 Can you login to Portal?

http://EpsiWebTest/EPSiPortal/Login.aspx?portalid=1

https://Vap0216/homepage/aspx/login.aspx

http

Can you launch a legacy/Standard report? (Security, User ID?Name)

Can you create a GL/PLA Report?

http://epsiwebtest/EPSiPortal/Login.aspx?portalid=1

https://vap0216/homepage/aspx/login.aspx


Step #

Task Web-Server 1 WS2

Will a Cube Report Run (see Deduction Payor Summary Report)? Can you launch PLA (Product Line Analysis and do a Patient Search?

If PLA has trouble launching, make sure the end user clears their cache system cache (especially if the EPSi version number you are installing is the same version number of a previous installation)

To clear workstation cache, on the workstation, open Windows Explorer and Navigate to the C:/Users/<username>/AppData/Local/Apps folder and remove the ‘2.0’ folder.

Patient Data \ Encounters Menu:


Step #


Patient Search Window:

The Patient Search table may take 60 seconds or more to display. Once the Search Results table displays, double click on one of the rows to display the Patient Encounter Detail window. This window verifies that a “Patient Search” is complete.

- Note: a known error return is: No Active Execution Server Could Be Found. If this occurs, try

o Clearing workstation cache o Restarting the Allscripts Scheduling Executor Windows Service on the web server

where Allscripts Windows Services are running. (only one server should have them running)


Step #


o Close the EPSi Portal, and relaunch the portal. Then attempt to do a PLA Patient Search again.

If the above steps do not resolve PLA Patient Search issues, refer to Appendix B on page 102. While the PLA Patient Search is running, you may perform other checks. Can you launch Data Access Administrator (from Admin Tools Menu) – merely launching the

application is a sufficient test.

Can you launch a DataStudio job? 1. Launch DataStudio 2. Find a Job that is quick running 3. Click the launch job icon.

Can you launch a Desktop Application / Enterprise Analyst?


Step #

Task Web-Server 1 WS2 Check DataStudio Database , TaskEngines Table

9.2 Test Workstation Applications on Database Server

In many test environments, the DeskTopBundle.exe can be installed so the “Workstation/Desktop Applications” can be tested by a technician.

The DeskTopBundle will install its applications (normally) on C:\Program Files (x86)\Sunrise EPSi.

Here are the applications to test, and links to these applications can be created on the desktop:

1) DataLoader.exe (client version)

2) EMDAdministrator.exe

3) EnterpriseAnalyst.exe

4) Productivity.exe

5) Security.exe

9.3 Test a Workstation Application

This test assumes that a workstation has been verified as compliant with the EPSi System Requirements. Use the Pre-Install Worksheet to

check the system configuration of a workstation with system requirements.

You will need to have at least one workstation setup correctly in order to test EPSi workstation operations. You may need to run the

DesktopBundle.exe on a workstation or on the designated Citrix Server.

After one workstation has been checked, configured, and has an EPSi DeskTopApplication successfully installed, try to run one of the

desktop applications (like Enterprise Analyst) on the workstation. Make sure the application can successfully launch and operate in the new

EPSi environment.


10 Appendix A: Current EPSi Version is 7.X – Additional Tasks There are some known additional tasks needed when upgrading an installation to 8.X from EPSi Version 7.X. This section identifies tasks

that need to be performed prior to running the 8.0.11 installation/upgrade.

10.1 Current EPSi Version is 7.5.124

Before running an upgrade for 8.X, the T_DISCHARGE_STATUS table will need to be updated.

Step # Task Notes

Connect to the main EPSi database that is targeted for the installation. Run the SQL:

alter table t_discharge_status

add [ID] [int] identity(1,1) NOT NULL

10.2 Current EPSi Version is 7.5.125

No additional tasks are needed.

10.3 Current EPSi Version is 7.5.126 or 7.5.127

The following steps will need to be applied before attempting an upgrade to EPSi 8.X.

1) On each web / report server, please remove any existing installation of:

a. EPSi Web Server (v7.5)

b. Sunrise EPSi Web Server (v7.2)

2) Configure the Web / Report servers according to the V7.5 FP2 Config / Install document

3) Update the pw for the SQL Authentication Accounts: EPSiADMIN & EPMADMIN

a. Database scripts to update the two accounts should be transferred to the

i. 2/18/15 - Scripts for Step 4 are currently unavailable

4) Manually Updating the SQL Authentication accounts: EPSiAdmin & EPMAdmin

a. Launch SQL Management Studio. Connect to the necessary database.

b. Expand: Security – Logins – Locate the accounts: EPSiAdmin & EPMAdmin

c. Right click on one of the accounts, select “Properties.”

d. Update the password that was provided (copy-paste) is recommended and select OK.


e. Repeat the steps for the EPSiAdmin account.

5) Update the SQL Reporting Database account

a. Launch the SQL Reporting Configuration Manager

b. Select the Database option.

c. If the credentials in the “Current Report Server Database Credential” is referencing EPSiAdmin or EPMAdmin, please update

the password or change the credential.

d. If the credentials are a different account, please skip this step.

6) Update the SQL Reporting Service Datasource Password for the EPMAdmin Account

a. Launch the SQL Reporting Configuration Manager

b. Select the Report Manager URL option and launch the url

c. Locate the folder housing the EPSi application (Default Name: EPSi Reports).

d. Click on EPSi Reports, select Data Sources, select EPSiWork

e. Update the password for the EPMAdmin account & test the connection

f. When successful, choose “Apply” then close the application.



7) Update the SQL Analysis Service Datasource Password for the EPMAdmin account.

a. Using SQL Management Studio, launch the SQL Analysis Service

b. Once, connected, expand the following fields:

i. Databases – PMReporting_Work – Datasources

c. Select the PMReporting_Work datasource object

d. Right-Click on Properties

e. Select the ellipse on the line: Connection String

f. Update the password for the SQL Authentication Account: EPMAdmin

g. Test the connection. If successful, select OK.

h. Close the application.


8) Once steps 1-5 have been completed, please resume the upgrade/ installation for 16.3

9) After the upgrade, one final password change within the Data Studio module will need to be applied.

a. Note – if Data Studio has not been configured, please skip the steps below.

b. Log into the web-based modules. Select Applications – Admin Tools – Data Studio.

c. Within Data Studio, select the Control Panel icon (upper left of screen) – View Data Stores – EPSi Database (double-click to

open).

d. The Location screen will appear.

e. Double-click on the location with name of the EPSi Database server.

f. Within the Database details, update the Password field, tab to a different field, then Save.

g. Once saved, select Test Connection.


11 Appendix B: Known Installation Issues and Errors This appendix includes information about any 16.3 installation issues that have occurred in testing, QA, or with client environments.

11.1 Checking Table Partitioning

Check the EPSi Database, T_PARTITION_FUNCTIONS Table for records. If this table has records, table partitioning setup was completed.

11.2 Wix Log: Error … Failed to install MSI Package

The exact error is: Error 0x80070643: Failed to install MSI package. See paragraph 9.6 in this document.

In general, this error is caused by improper security credentials (account running the install does not have permissions to copy EPSi files to

the server) or some process interfered with the copying of EPSi files to the server. Paragraph 9.6 addresses an invalid service account. It is

possible an old EPSi client connection exists or an EPSi client attempted to connect while the upgrade/installation was in progress. To

prevent this later issue, you may stop the Default App Pool within IIS.

This error has occurred when there is a problem with the credentials of the Windows Login (Domain) Account.

This error message has already appeared when the current EPSi version is 7.5.124 or 7.5.125 and the EpsiAdmin account and or EPMAdmin

account need additional configuring (see paragarphs 8.1 or 8.2 in Appendix A of this document).

The log file where this error occurs: Allscripts_EPSi_Server_Software_YYYYMMDDhhmmss.log.

All the Wix logs will be found in: <Drive>:\Users\<login_account>\AppData\Local\Temp on the server where the installation processes.

11.3 Uninstall Issues

If the EPSi programs were not uninstalled correctly, you may need to stop Allscripts services via the Task Manager.

Preferred Uninstall Program Order: uninstall EPSi Web Server before uninstalling the Allscripts EPSi Server Software

If the order is not followed you might get this message:


To clean up an uninstall of EPSi, try stopping all Allscripts services (on all web servers) via the Task Manager. Then, attempt the uninstall of

any remaining Allscripts applications.

Typically you can go to Services and try to stop the Allscripts Service erroring. A 1061 Error message may occur when attempting to stop

services thru normal procedures. Use the Windows Task Manager on the server and click the Services tab, then stop the Allscripts Data

Studio task that way. Then proceed with the uninstall.

Step

# Task Web-Server 1 Web-Server 2

1. Un-install the current EPSi system:

1) Right click on “Allscripts EPSi Server Software” and choose Uninstall.

2 You may choose to simultaneously uninstall EPSi on multiple webservers if they

exist.


Step #


2. On each web/report server, go to: [drive]\inetpub\wwwroot\epsi. Verify

that the “DLL” folder has been removed. If the “DLL” folder is present, delete it

3. If you are upgrading an EPSi system that is currently on 7.X, you must

upgrade the environment to 8.X before you can continue with the 16.1

Installation. If you have not already upgraded the environment to 8.X, you

must refer to Appendix A to perform that upgrade. Once the 8.X upgrade is

successful, return to the Pre-Install checks in previous section of this

document and verify the pre-install checks and tasks have been completed.

4. Reboot / Restart each web server after the EPSi Uninstall

5. Verify all EPSi COM components have been removed: Under Administrative

Tools / Component Services / Computers / MyComputer / COM+ Applications:

EPSi Components Should Not Be Present


Step #


6. Remember: you must completely uninstall EPSi components BEFORE attempting

an EPSi installation.

7. REBOOT THE SERVER after you have successfully completed an uninstall

of the EPSi System.

11.4 PLA Patient Search Issues

11.4.1 Error Message: “No Active Execution Server Could Be Found” Here are some steps to do to try to resolve the issue:

1. Clearing workstation cache 2. Restarting the Allscripts Scheduling Executor Windows Service on the web server where Allscripts Windows Services are running. (only one

server should have them running) 3. Close the EPSi Portal, and relaunch the portal. Then attempt to do a PLA Patient Search again.

If the above steps do not resolve the error message “No Active Execution…”, then consider the following:

1. In the EPSi main database, check the table T_SCHEDULE_SERVICE.


2. In this table, find the record with the server name of the web server that is part of the current installation. This record should reveal a

“LastHeartbeat” value of a very recent time-stamp. This recent time-stamp indicates the Allscripts Scheduling Executor service is

running and looking to resolve PLA Search requests.

3. If the heartbeat is recent (with the last 10 or 20 minutes), you know the Scheduling Executor service is working and looking for PLA

data requests to process.

4. If the heartbeat value is not recent and doesn’t update after a few minutes, there are few steps you can take to get the service back to

work.

5. Right click the mouse pointer on the EPSi database icon in SQL Server Management Studio and choose the Properties option.

6. Verify that the “Broker Property” is enabled. If it is not enabled, you can manually update the database properties with the following

SQL statement

a. alter database <database Name> set new_broker with rollback immediate


7. Then restart the Allscripts Scheduling Executor Windows Service.

8. Attempt to perform a PLA Patient Search.

11.5 Trouble-shooting Legacy Reporting

This section addresses Legacy Reporting general architecture and common items to check when Legacy Reporting is not functioning

correctly.

Legacy Reporting Architecture

Legacy Reporting functionality is accessed by selecting the “Reporting Applications, Costing/Capital/Security” in the UI Menu of the EPSi

Portal. When a user selects a report, EPSi code collects input information along with the specs for the selected report and calls the

EPSiReportRefreshService. The service creates an XML file and places that file in the ASPReportingManager\Output folder share. No

matter what web server processes the report, all web servers will place the XML file in the folder designated as the “Output” share. The

service calls other web server programs to process the report: each report has a template file that must be in the web server ..\EPSi\REPORTS

folder (RPX files). Web Server programs use the RPX files along with the XML file to generate an RDF file. The RDF files are placed in the

Output folder share. At this point, Report Viewer will take the RDF file and present the report to the user.

11.5.1 Multiple Web Servers Environment: Legacy Reporting Does Not Work 11.5.1.1 EPSi Services Should Run on Only One Web Server Make sure you have disabled EPSi services on all but one server. Normally, we set EPSi services on Automatic setting on one web server

only, but the virtual Output folder must be setup on all web servers with the same share and folder name (i.e. \\webserver1\Output).

11.5.1.2 Cycle the Report Refresh Service on ‘Non-Active’ web servers if Issues Persist If Legacy Reporting does not work during Sanity Checks (in a multi-web-server environment), you may need to start the Report Refresh

Service on the server(s) where services are not running /disabled. Let the service run for approximately 30 seconds. Then, shut the service

down and disable the service again. This procedure has proven helpful during the Blessing EA Installations.

11.5.2 Portal Log-In Account Gets Locked Out If the account you are using to login to EPSi Portal gets locked and will not allow further use of the account, remember you can reset the

account to active status by accessing the EPSi main database (PM_System), T_USERS table; set the ActiveStatus field value to “-1”. You

should find all inactive EPSi accounts display an ActiveStatus field as “0”.


11.6 Installation Fails: Failed to Execute/Install MSI package EpsiWebServerProduct

A symptom of this issue is that EPSi Files cannot be saved under <drive>:\Inetpub\wwwroot. The EPSi folder and possibly the EPM and

OLAP folders don’t save.

There are a few known reasons for this issue:

1) The Login / Install Account Doesn’t have the authority to install / configure files on this server

2) Make sure .Net Versions 3.5 and 4.6.1 are installed on the server

3) Some user or process is interfering with the installer.exe in its efforts to configure and copy files

Take Note: By default, Inetpub\Wwwroot is specified on the C drive. These folders may be found on the C drive but not used by the web

server. If you see the Inetpub folder on multiple drives of a web server, verify with the customer which drive is used by the operating web

server.

If the EPSi install process cannot create and copy folders under .\Inetpub\Wwwroot, the likely cause is a permission issue with the EPSi

installation. The installation uses the Windows Service Account as security authorization to copy files and perform numerous installation

configuration tasks.

This issue will be logged as the following lines in the Wix log created by installer. [0D0C:0DEC][2016-08-26T14:36:56]i323: Registering package dependency provider: {2B374BCE-4414-4B07-97AC-0B699F200DFC}, version: 16.1.0.16238, package: EpsiWebServerProduct

[0D0C:0DEC][2016-08-26T14:36:56]i301: Applying execute package: EpsiWebServerProduct, action: Install, path: C:\ProgramData\Package Cache\{2B374BCE-4414-4B07-97AC-

0B699F200DFC}v16.1.0.16238\EPSI_16_1_0_16238.msi, arguments: ' MSIFASTINSTALL="7"'

[0D0C:0DEC][2016-08-26T14:43:25]e000: Error 0x80070643: Failed to install MSI package.

[0D0C:0DEC][2016-08-26T14:43:25]e000: Error 0x80070643: Failed to execute MSI package. [1194:124C][2016-08-26T14:43:25]e000: Error 0x80070643: Failed to configure per-machine MSI package.

[1194:124C][2016-08-26T14:43:25]i319: Applied execute package: EpsiWebServerProduct, result: 0x80070643, restart: None

[1194:124C][2016-08-26T14:43:25]e000: Error 0x80070643: Failed to execute MSI package. [0D0C:0DEC][2016-08-26T14:43:25]i329: Removed package dependency provider: {2B374BCE-4414-4B07-97AC-0B699F200DFC}, package: EpsiWebServerProduct

The log file name: Allscripts_EPSi_Server_Software_YYYYMMDDhhmmss.log

All the Wix logs will be found in: Drive:\Users\<login_account>\AppData\Local\Temp:

Example:


Solution:

Verify that the Windows Service Account you are using has the admin rights required. You can do this by:

1) configuring the Corda Service to use the client supplied Windows Services Account

2) run the Corda Service using the account. If the service will not run, the Windows Services Account is not correct (either name or

password or both).

Note: EPSi Versions 16.1.01 and later do not use Corda Software and does not include a Corda Service.

11.7 GL Reporting Issues: Recreate SSAS Database

In GL Reporting is reporting that reporting services are not available, one cause could be a SSAS database that is corrupt or non-extent.

Using SSMS you can check that there is an SSAS database under the SSAS Server connection. If a SSAS database does not exist, or you

want to drop and re-create it, refer to the Creating A SSAS Database Appendix.

11.8 Cube Reporting Failing with “An Error Occurred Within the Report Server Database” (CLI Mentioned)


11.9 Data Studio Data Loads Not Working: Network FileShare Changed

This error may be due to a new environment being set up, and the data-load fileshare location has changed to a different server

If all or some of the mapping in Data Studio are still pointing to an old server, as shown in the screen shot below in the Server Name: entry,

follow the steps below.

In the DataStudio Database, there is a LOCATIONS table where the locations of server, fileshare can be seen.


In the ServerName column, we can see the server name designated for data loads, if the environment has changed and the server name has

been migrated to another server, then this table can be updated (in the new environment) and as long as the fileshare has the same pathing

(same folder tree structure and same fileshare name) then the new environment can be corrected just by changing the server name(s) in the

SERVERNAME column.

If the pathing to the file share has changed, then values in the FILEPATH column and even the FILENAME column might need to be

corrected.



11.10 EXECUTE Permission Denied on object 'xp_sqlagent_notify', database 'mssqlsystemresource', schema 'sys'

This error has appeared in conjunction with Legacy Reporting (EPSi 16.1) Trouble-Shooting.

In one client installation, this error appeared and the following web page indicated that database permissions were not correctly given to the

agent xp_sqlagent_notify:

https://social.msdn.microsoft.com/Forums/sqlserver/en-US/444c3bab-985b-40a0-8362-2742df1a6577/error-viewing-the-execution-option-of-

a-report?forum=sqlreportingservices

The following SQL was used to grant correct permissions:

USE master GO

GRANT EXECUTE ON master.dbo.xp_sqlagent_notify TO RSExecRole GO

GRANT EXECUTE ON master.dbo.xp_sqlagent_enum_jobs TO RSExecRole GO

GRANT EXECUTE ON master.dbo.xp_sqlagent_is_starting TO RSExecRole GO

USE msdb GO

-- Permissions for SQL Agent SP's

GRANT EXECUTE ON msdb.dbo.sp_help_category TO RSExecRole GO

GRANT EXECUTE ON msdb.dbo.sp_add_category TO RSExecRole GO

GRANT EXECUTE ON msdb.dbo.sp_add_job TO RSExecRole GO

GRANT EXECUTE ON msdb.dbo.sp_add_jobserver TO RSExecRole GO

https://social.msdn.microsoft.com/Forums/sqlserver/en-US/444c3bab-985b-40a0-8362-2742df1a6577/error-viewing-the-execution-option-of-a-report?forum=sqlreportingservices

https://social.msdn.microsoft.com/Forums/sqlserver/en-US/444c3bab-985b-40a0-8362-2742df1a6577/error-viewing-the-execution-option-of-a-report?forum=sqlreportingservices


GRANT EXECUTE ON msdb.dbo.sp_add_jobstep TO RSExecRole GO

GRANT EXECUTE ON msdb.dbo.sp_add_jobschedule TO RSExecRole GO

GRANT EXECUTE ON msdb.dbo.sp_help_job TO RSExecRole GO

GRANT EXECUTE ON msdb.dbo.sp_delete_job TO RSExecRole GO

GRANT EXECUTE ON msdb.dbo.sp_help_jobschedule TO RSExecRole GO

GRANT EXECUTE ON msdb.dbo.sp_verify_job_identifiers TO RSExecRole GO

GRANT SELECT ON msdb.dbo.sysjobs TO RSExecRole GO

GRANT SELECT ON msdb.dbo.syscategories TO RSExecRole GO

11.11 Clearing DataStudio Schedule Hung/Canceled

When a DataStudio schedule is hung and not responding, or when the schedule is canceled but not responding perform the following SQL

(replacing name with the correct schedule name)

-- Change Status for Schedule SELECT * FROM [dbo].[Schedules] where name ='2016 !CW Automation Schedule' update [dbo].[Schedules] set [LastRunStatus] = 'Success', [ForceExecuteImmediately] = 0 where name ='2016 !CW Automation Schedule' --Change Status for Job SELECT * FROM [dbo].[Jobs]


where scheduleid = ( SELECT scheduleid FROM [dbo].[Schedules] where name ='2016 !CW Automation Schedule' ) SELECT * FROM [dbo].[Jobs] where jobId in( SELECT jobId FROM [dbo].[Jobs] where scheduleid in ( SELECT scheduleid FROM [dbo].[Schedules] where name ='2016 !CW Automation Schedule' ) ) update [dbo].[Jobs] set [LastRunStatus] = 'Success' where jobId in ( SELECT jobId FROM [dbo].[Jobs] where scheduleid in ( SELECT scheduleid FROM [dbo].[Schedules] where name ='2016 !CW Automation Schedule' ) ) -- Change status for task select * from tasks where jobId in ( SELECT jobId FROM [dbo].[Jobs] where scheduleid in ( SELECT scheduleid FROM [dbo].[Schedules] where name ='2016 !CW Automation Schedule' ) ) update [dbo].[Tasks] set [LastRunStatus] = 'Success' where Jobid in ( SELECT jobId FROM [dbo].[Jobs] where scheduleid in ( SELECT scheduleid FROM [dbo].[Schedules] where name ='2016 !CW Automation Schedule' ) )


11.12 SSRS/GL-Reports Fail: Logon failed for unattended execution account

This is could occur for other EPSi functionality in addition to EPSi Reporting. An example screen capture:

The error description “the user name or password is incorrect” is misleading. The issue occurs because the EpsiAdmin account cannot

REMOTELY connect to the database server or database instance. Ask client IT staff to ensure that EpsiAdmin (or its equivalent) can

remotely connect to the EPSi databases. One way to check this is to open SQL Server SSMS on a report or web server, and use the

EpsiAdmin account to connect to the database server/instance.

11.13 Report Server Event Log Message: The found version is xxxx; The expected version is xxxx

Sometimes, scheduled server updates occur during EPSi Upgrades, when this happens SSRS or SSAS operations between database server and

report server can be broken. In this case, updates to SSRS on one server may break the SSRS operation with another server. The Application

Event Log or System Event Log may report the following:

The version of the report server database is either in a format that is not valid, or it cannot be read. The found version is '163'. The expected version is '162'.

(rsInvalidReportServerDatabase

The error cause and possible solution steps:

Occasionally fixes are made to the product that require a change to the Reporting Services schema. When this happens, the Schema version is incremented. This may

happen in a cumulative update. If you have applied a cumulative update then upgrade to a later service pack, you must also check the release dates carefully. You may need

to apply a cumulative update for the new service pack to get to the same (or later) Reporting Services database schema.

For example:

Version 163 was introduced in the following versions


SQL Reporting Services 2012 SP2 CU5

SQL Reporting Services 2012 SP3

SQL Reporting Services 2014 CU7

So upgrading from any version later than the first to 2014 would encounter this issue.

Version 164 was introduced in the following versions


SQL Reporting Services 2012 SP3 CU5 (avoid and go to at least CU6)



PLEASE NOTE:

If schema changes have been performed on a table or database, these changes cannot be automatically undone.

11.14 SSRS and/or GL Reports Error: Cannot create a connection to data source EPSIWork


The above error occurs when the datasource configuration for SSRS is not able to make a connection to the PMReporting_Work database.

During an upgrade the EpsiAdmin account password usually migrates, but sometimes it does not. When this happens the configuration of the

EpsiWork datasource may need to be updated – and the EpsiAdmin password needs to be entered or re-entered correctly.

To address this issue:

1) Follow the SSRS Configuration Steps to the EpsiWork screen (within ReportManager link)

2) Click the “Test Connection” button and verify that the connection is working

3) Re-enter the EPSiAdmin password if needed

4) Apply the changes – if changes were made

(see screen capture below)



11.15 Reporting Services SSRS: Removing SSL Configuration

Clients use a preconfigured template to install and setup SSRS. If the configured SSRS has defined usage of SSL Certificates, there is a

known bug in SSRS when trying to remove SSL certificates from the SSRS configuration.

First of all, you may encounter an error similar to the following when running an upgrade/installation and SSRS database connectivity fails.

This failure may occur for several reasons and it may not be related to SSL.

Message: EPSi Database Update Utility Error, Error Occurred During PublishSystemRdl.

In Reporting Services Configuration Manager, you may see SSL certificates defined in a couple different screens:

The following are screens from Web Service URL and Report Manager URL displays.


The above links will be specified with an “https” prefix if SSL certificates are involved in the access to these web pages. You may try to

remove references to SSL certificates from either or both of the above displays, but the changes may not be saved. This is a known bug with

SSRS configuration (4/10/17). You will be able to remove SSL certificate configuration by:

1. Find the rsreportserver.config file in C:\Program Files\Microsoft SQL Server\MSRS11.MSSQLSERVER\Reporting

Services\ReportServer\rsreportserver.config

2. Edit the config file by changing the “Value=number” parameter

3. Restart the SSRS Windows Service after making and saving the change.

The lines in the file that need changed are:

<Add Key="SecureConnectionLevel" Value="2"/>

to be this:


<Add Key="SecureConnectionLevel" Value="0"/>

Reference web page:

https://connect.microsoft.com/SQLServer/feedback/details/686214/removing-ssl-cert-in-config-manager-doesnt-properly-modify-

rsreportserver-config

11.16 G/L and Cube Reports Don’t Process

Recent 8.X and 16.X upgrades have shown that the SSAS Datasource doesn’t seem to get the EpsiAdmin account and password setup

correctly (object in the DataSource folder). In some cases the CLI version is wrong or not consistent with the installed CLI version. More

often, the EpsiAdmin (database account) has not been specified / is blank.

To check for the missing account and password:

1. Right click on the datasource (V80_11_Reporting_Work)

2. Select the Properties Menu

3. In the general section, within the “Connection String” line, click on the Ellipsis Icon to open a menu

4. After clicking on the ellipsis button, the following menu appears:

https://connect.microsoft.com/SQLServer/feedback/details/686214/removing-ssl-cert-in-config-manager-doesnt-properly-modify-rsreportserver-config

https://connect.microsoft.com/SQLServer/feedback/details/686214/removing-ssl-cert-in-config-manager-doesnt-properly-modify-rsreportserver-config


5. Sometimes the EpsiAdmin account and password are missing. Add them if needed.

6. Remember to ‘Test Connection’

11.17 EPSi Reports Don’t Save: Transaction Manager is Disabled

This issue occurred on May 25th at a client. The following screen shot shows the message in the “Save As MyReport” dialog box:


The resolution to the above problem was the Database Server (16.X) did not have DTC configured (at all). Once DB Server was configured

users were able to save reports. All server DTC settings should be checked.

11.18 MS-DTC Issues: Duplicate CIDs

Some DTC issues could be caused by duplicate MS-DTC CIDs existing on two or more servers. PowerShell can check if there are duplicate

MS-DTC CIDs on a list of servers:


$CIDs = Invoke-Command -ComputerName $servers -ScriptBlock { gci Microsoft.PowerShell.Core\Registry::HKEY_CLASSES_ROOT\CID | foreach { $_.Name } | Out-String -Stream } #Array of all CIDs on all servers $UniqueCIDs = $CIDs | select -Unique if($CIDs.Length -eq $UniqueCIDs.Length){ Write-SuccessMessage "All Server CIDs are Unique for Servers: $servers"; } else { Write-FailMessage "Found duplicate CIDs(4perServer), Investigate MSDTC on all Epsi-Servers!: $CIDs"; foreach ($cid in $CIDs){ Write-InfoMessage $cid; } }

Duplicate CIDs can cause DTC communication to fail among EPSi servers. Using the logic above you will be able to determine if duplicates

exist (there are four CIDs per server). Once you find which servers have duplicate CIDs, you can perform the following commands in a

command window, run as an Administrator:

1) On the server that has the duplicate CIDs, launch a Command Window as an Administrator

2) Run the command: MSDTC -UNINSTALL

3) Run the command: MSDTC -INSTALL

The above steps should reset the CID’s to a different ID. You may have to run the reset process (above) on all servers that have duplicates.

Note also, that in some cases, you may have to manually delete CID entries in the Registry. Consult the WWW for suggestions on this.

11.19 RPC Server NOT Available

Short Description: EPSi relies on technologies(DTC, SQL, Microsoft Exchange) that require the RPC protocol and RPC Server to be running

on the EPSi servers.

11.19.1 Overview If you run any PowerShell scripts that try to remote connect to other servers then RPC services must be running on any remote servers.

Remote Procedure Call (RPC) is an inter-process communication protocol and a technique to allow client and server software to communicate

over a network. RPC is used by several components in Windows Server, such as the File Replication Service (FRS), Active Directory

Replication, Certificate services, DCOM, domain join, DCPromo and RDP, NLB and Cluster, Microsoft Operations Master, Exchange and

SQL.


11.19.2 Error RPC Server Not Available You may find this error in the Windows Event Logs or as a result of PowerShell scripts. If this error occurs, the server may need to be

rebuilt. Most Windows servers will have RPC Server installed and running since it is used by numerous processes in a client-server

environment.

11.20 Problem with Legacy (Costing) Reporting: “Login failed for user EpsiSupport”

This issue occurred at UH Cleveland in July 2017. After installing EPSi, we used the EpsiSupport account to login into the Portal and test

basic functionality. Even though we are able to login in the EPSi Portal, and most functionality works, legacy / costing reports will not run.

The symptom is the legacy report spinner continues to spin without returning an error. But the SQL server logs display the following:

In this situation I checked the following:

1) The EpsiSupport SQL server account (server level)

2) The T_USERS table – and updated the password for the EpsiSupport account

3) The EpsiSupport account at the Main EPSi DB level.

We fixed the problem by running this EPSi Stored Proc

1) Dropping the EPSiSupport account from the Server level and DB level

2) Running Exec EPSi_SEC_MoveUsersToRoles ‘main EPSi DB name’


11.21 Login Account Cannot Connect to DB Server From Remote Server/Client

This issue occurred with a client in July 2017. The login account should be a local administrator on all EPSi servers: in this case it was. The

login account should be a SysAdmin and DBCreator on EPSi DB Servers; in this case it was. With these credentials, the login account should

not have any problem connecting to the EPSi DB Server or any of its databases.

Symptoms and log entries for this problem.

1) The login account could NOT connect to the DB Server(instance) from remote servers, but the login account could connect to the DB

Server while logged into the host server for SQL Server.

2) While attempting to login to the DB Server with the login account (from a remote server), the following windows message appears :

The target principal name is incorrect. Cannot generate SSPI context. (Microsoft SQL Server)

3) Event logs on the remote server may indicate Kerberos Client errors like the following informational message:


The Kerberos client received a KRB_AP_ERR_MODIFIED error from the server sqladm. The target name used was

MSSQLSvc/epsidbprd.adnmhc.nmmc.com:1433. This indicates that the target server failed to decrypt the ticket provided by the client. This can occur when

the target server principal name (SPN) is registered on an account other than the account the target service is using. Ensure that the target SPN is only

registered on the account used by the server. This error can also happen if the target service account password is different than what is configured on the

Kerberos Key Distribution Center for that target service. Ensure that the service on the server and the KDC are both configured to use the same password.

If the server name is not fully qualified, and the target domain (ADNMHC.NMMC.COM) is different from the client domain (ADNMHC.NMMC.COM), check

if there are identically named server accounts in these two domains, or use the fully-qualified name to identify the server.

4) The client network technicians recreated the Service Principal Name (SPN) for the service MSSQLSVC\EPSIDBPRD on the DB

Server. They followed this general outline:

a. Changed SQL Server service to run as local (I believe this is SQL Server service MSSQLSERVER)

b. Restarted the SQL Server service

c. Logged in as EPSi Login Account and were able to launch SSMS with Windows Auth.

d. Changed SQL Server service back to run as sqladm account (was it is on TST and was before step 1.

e. Performed some SPN updates on EPSIDBPRD (production DB Server)

f. Changed the SQL Server service back to run as sqladm.

g. Re-started the DB server.

5) A more detailed description follows:

We recreated the SPN for MSSQLSVC/EPSIDBPRD to be created with the service account that the SQL Server was starting with. The

below steps were performed when recreating the SPN. We have NEVER had to do this with any of our other SQL servers so I’m not sure

what caused this to have to happen on EPSIDBPRD.

Before

C:\Users\e02444.ADNMHC>setspn -l EPSIDBPRD

Registered ServicePrincipalNames for CN=EPSIDBPRD,OU=EPSi,OU=Servers,OU=NMHC,DC=ADNMHC,DC=NMMC,DC=COM:

CmRcService/EPSIDBPRD

CmRcService/EPSIDBPRD.ADNMHC.NMMC.COM

MSSQLSvc/EPSIDBPRD.ADNMHC.NMMC.COM

MSSQLSvc/EPSIDBPRD.ADNMHC.NMMC.COM:1433

WSMAN/EPSIDBPRD.ADNMHC.NMMC.COM

WSMAN/EPSIDBPRD

TERMSRV/EPSIDBPRD.ADNMHC.NMMC.COM

TERMSRV/EPSIDBPRD

RestrictedKrbHost/EPSIDBPRD

HOST/EPSIDBPRD


RestrictedKrbHost/EPSIDBPRD.ADNMHC.NMMC.COM

HOST/EPSIDBPRD.ADNMHC.NMMC.COM

Remove the SPN for MSSQLSvc from the local Server

setspn -D MSSQLSvc/EPSIDBPRD.ADNMHC.NMMC.COM EPSIDBPRD

setspn -D MSSQLSvc/EPSIDBPRD.ADNMHC.NMMC.COM:1433 EPSIDBPRD

After the SPN Removal

C:\Users\e02444.ADNMHC>setspn -l EPSIDBPRD

Registered ServicePrincipalNames for CN=EPSIDBPRD,OU=EPSi,OU=Servers,OU=NMHC,DC=ADNMHC,DC=NMMC,DC=COM:

CmRcService/EPSIDBPRD

CmRcService/EPSIDBPRD.ADNMHC.NMMC.COM

WSMAN/EPSIDBPRD.ADNMHC.NMMC.COM

WSMAN/EPSIDBPRD

TERMSRV/EPSIDBPRD.ADNMHC.NMMC.COM

TERMSRV/EPSIDBPRD

RestrictedKrbHost/EPSIDBPRD

HOST/EPSIDBPRD

RestrictedKrbHost/EPSIDBPRD.ADNMHC.NMMC.COM

HOST/EPSIDBPRD.ADNMHC.NMMC.COM

Manually create the SPN for MSSQLSvc for the Service Account

setspn -a MSSQLSVC/EPSIDBPRD:1433 ADNMHC\sqladm

setspn -a MSSQLSVC/EPSIDBPRD.ADNMHC.NMMC.COM:1433 ADNMHC\sqladm


After registering the SPN to the Service Account

C:\Users\e02444.ADNMHC>setspn -l sqladm

Registered ServicePrincipalNames for CN=sqladm,CN=Users,DC=ADNMHC,DC=NMMC,DC=COM:

MSSQLSVC/EPSIDBPRD.ADNMHC.NMMC.COM:1433

MSSQLSVC/EPSIDBPRD:1433


12 Appendix C: 8.X Upgrade Procedures This section contains an abbreviated list of instructions for the 8.X Installation & Upgrade. For a complete list of instructions reference

EPSi_8_0_Config-Install.docx.

Step

# Task Web-Server 1 WS 2

1) Verify the EPSi environment meets or exceeds the system requirements for the 8.X

Installation and Upgrade.

2) The pre-installation checks in Sections 2, 3, 4, and 5 of this document are generally applicable

to an 8.X installation/upgrade. Verify the system configuration for SSRS, SSAS, IIS are

complete and configured for the EPSi installation.

3) Remove any existing of version of EPSi Web Application software on all web servers and

reboot servers after the EPSi software has been removed.

4) Copy the 8.X installation files to a web server. (all web / reporting servers)

5) Launch the WebServerBundle.exe (will be required on each web server)

6) Select Install

7) Select the Next button a successive screens until the following dialog:


Step #


This screen allows the installer to

customize the location where EPSi files will be stored. In general, EPSi should be installed in

<drive>:\Inetpug\wwwroot. Usually the drive is C:. 8) In the current screen you may choose to disable the execution of EPSiDBUpdater or web

services. Normally, these options are left intact.

9) In the following screen, designate the server and DB name for the main EPSi database. The

Default SQL Server account is usually selected. These will be verified after “Next.”


Step #

Task Web-Server 1 WS 2 10) In the Web URL Dialog box, enter the URL for the primary web server. The prefix http:// is

optional.

11) In the next dialog enter the domain-name, account name, and password for the (domain)

services account. This is the account that EPSi services and other processes will use to access

file locations, databases, file shares, etc. throughout the EPSi system. This account should be

a local administrator on each server.


Step #

Task Web-Server 1 WS 2 12) In the following screen you will check or enter the SSAS server name

13) Similar dialogs will appear prompting you to change or confirm the names of the Portal DB,

the Reporting DB, and the DataStudio DB. Verify the spelling of each name and change as

necessary.

14) This dialog provides the install tech one last chance to back-track and change any previous

selections. Once the Install button is clicked, the installation will proceed and settings can

only be done by uninstalling the software.


Step #

Task Web-Server 1 WS 2 15) During this phase of the installation, installation settings and configuration settings are

applied.

16) The next phase of the installation is the Performance Management Database Update Utility.

This is the EPM DB Updater installation. This installation can be run separately once the

previous installation phase has been completed successfully. The EXE for this install can be

found in ..\inetpub\wwwroot\EPM\Tools\DBUpdater\Eclipsys.EPM.DBUpdater.exe

17) The install will present confirmation screens for the Portal DB, Reporting DB, DataStudio

DB, and the web (upload) server.

18) The next phase of the installation is the EPSi DBUpdater or Database Update Utility. Several

screens will again prompt the user to verify many of the same databases and other settings

already specified. If you see a name that is wrong, you should navigate back through the

install to the original screen where that settings was defined. Then, the subsequent screens

will be filled with the correct information.

19) The EPSi DBUpdater can be executed separately after all the previous phases are successful.

The DBUpdater.EXE is located at ..\inetpub\wwwroot\epsi\tools\dbupdater\

EPSiDBUpdater.exe


Step #

Task Web-Server 1 WS 2 20)

21) Always choose the “Typical” Installation type.

22)


Step #

Task Web-Server 1 WS 2 23) Note the HIPAA Settings Screen. The HIPAA Audit Logging Database is the HIPAA EAS

database. This database can have a custom DB name and location while the HIPAA_staging

DB cannot be named or relocated.

24) Once you have supplied name and configuration information, the DBUpdater will present a

grid for database update progress. Each row contains links that allow the user to view logs

and compare reports.

25) Verify that each database phase completes successfully (Update Result column) before

proceeding with the installation.

26) Note that there are two screens that confirm that the installation has been completed

successfully. The first screen verifies that the EPSi Web Server Setup Wizard is complete.


Step #


27) The second screen will verify that the entire installation (including WIX processing) is

successful.

28) Remember the WebServerBundle.exe must be executed on each web server, but the EPM and

EPSi DBUpdaters need to be executed only once. The EPM updater must be completed

before the EPSi DBUpdater.

29) If the installation uses ClientID features, contact EPSi Support.


Step #

Task Web-Server 1 WS 2 30) After the installation is complete, you may want to perform some of the same post installation

steps list in this document for version 16.3 (See page 65)

31) You may want to confirm that the database changes for the 8.X installation are in place.

32) If the installation is using HIPAA functionality, then HIPAA logging can be configured by

launching the following utility: ..\inetpub\wwwroot\epsi\tools\EpsiInstallUtility\

EpsiInstallUtility.exe. Before you run the utility, you will need to know how you want to

configure HIPAA (EAS etc.).

33) If the 16.3 Installation will be applied to the EPSi configuration, then functional “Sanity”

checks are usually not performed.

12.1 Checking the Status of Report Conversions

The following query will display notes and tasks being accomplished in the (7.5FP2) report conversion processing:

select * from dbo.T_PARTITIONED_TABLE_CONVERSION_LOG order by stepid desc


13 Appendix D: SSL Configuration within EPSi

13.1 Viewing SSL Setup for EPSi i. A named SSL certificate must be applied to the necessary web / report servers

a. The certificate must be applied and visible within the MMC Console as well as within IIS ii. Install the EPSI application on the server.

iii. Once the installation is complete, iv. Open IIS on the necessary web / report servers. v. Navigate to Server - Sites - Default Web Site

vi. Select Bindings. (From Actions Tab on the right side of the screen)


vii. When the Site Bindings screen opens, highlight 'https' and choose edit (or double-click to open).

viii. Under the SSL Certificate section change the certificate from localhost to the named certificate that was applied in step 1.

ix. Save / Apply the certificate

(see next page for more instructions)


x. In order to enable the SSL certificate, the Install-Config tool will need to launched. a. Launch the command prompt (by running as an administrator). b. If necessary, change the drive reference to reference the drive on the web / report server that was used to install EPSI.

i. All examples below use the assuming of C:\ c. Navigate to: C:\inetpub\wwwroot\epm\tools\installconfigtool

xi. Command line for SSL (the lines below can be copy-pasted for accuracy). a. Please run the command for both folder sets (EPM & EPSI).

i. When applied, a success or failure message will be returned.

b. Activation:

1 - EPM: For Version 8.X ONLY: installconfigtool sslwebconfig /enablessl true /installdir c:\inetpub\wwwroot\epm

2 - EPSI: installconfigtool sslwebconfig /enablessl true /installdir c:\inetpub\wwwroot\epsi

C:\inetpub\wwwroot\EPSI\Tools\InstallConfigTool>installconfigtool sslwebconfig /enablessl true /installdir c:\inetpub\wwwroot\epsi /databaseServerName Vap0215 /databaseName RWJ_System

iii. The above commands will update various configuration files within the EPSI & EPM folder structure

iv. Removal:

1 - EPM: installconfigtool sslwebconfig /enablessl false /installdir c:\inetpub\wwwroot\epm

2 - EPSI: installconfigtool sslwebconfig /enablessl false /installdir c:\inetpub\wwwroot\epsi

xii. When the EPM and EPSI directories are both applied, please perform an IISRESET on the server xiii. Attempt to log in to the web-based applications using the HTTPS protocol along with the certificate binding that was applied to the

server. a. Example of log-in URL

i. Protocol: Https:// ii. Certificate binding: EPSI.corp.allscripts.com

iii. Web url: /homepage/aspx/login.aspx iv. Concatenated URL:

https://epsi.corp.allscripts.com/homepage/aspx/login.aspx v. Concatenated URL with Active Directory: https://epsi.corp.allscripts.com/homepage/aspx/loginAD.aspx

https://epsi.corp.allscripts.com/homepage/aspx/login.aspx

https://epsi.corp.allscripts.com/homepage/aspx/loginAD.aspx


13.2 Appendix E: Viewing SSL Certificates with MMC Utility

A common type of credential is the X.509 certificate. When creating secure services or clients, you can specify a certificate be used as the client or service

credential by using methods such as the SetCertificate method. The method requires various parameters, such as the store where the certificate is stored

and a value to use when searching for the certificate. The following procedure demonstrates how to examine the stores on a computer to find an

appropriate certificate. For an example of finding the certificate thumbprint, see How to: Retrieve the Thumbprint of a Certificate.

To view certificates in the MMC snap-in

1. Open a Command Prompt window.

2. Type mmc and press the ENTER key. Note that to view certificates in the local machine store, you must be in the Administrator role.

3. On the File menu, click Add/Remove Snap In.

4. Click Add.

5. In the Add Standalone Snap-in dialog box, select Certificates.

6. Click Add.

7. In the Certificates snap-in dialog box, select Computer account and click Next. Optionally, you can select My User account or Service account.

If you are not an administrator of the computer, you can manage certificates only for your user account.

8. In the Select Computer dialog box, click Finish.

9. In the Add Standalone Snap-in dialog box, click Close.

10. On the Add/Remove Snap-in dialog box, click OK.

11. In the Console Root window, click Certificates (Local Computer) to view the certificate stores for the computer.

12. Optional. To view certificates for your account, repeat steps 3 to 6. In step 7, instead of selecting Computer account, click My User account and

repeat steps 8 to 10.

13. Optional. On the File menu, click Save or Save As. Save the console file for later reuse.

https://msdn.microsoft.com/en-us/library/system.servicemodel.security.x509certificateinitiatorclientcredential.setcertificate(v=vs.110).aspx

https://msdn.microsoft.com/en-us/library/ms734695(v=vs.110).aspx


14 Appendix F: Creating SSAS Database There are situations where reporting functionality may not be working in the EPSi. In these cases, reconfiguring and recreating aspects of EPSi may resolve issues. One action that may be helpful is the removal and re-creation of the SSAS database.

14.1 To remove a SSAS Database Step

# Task

1) Login in to SSMS and Connect to the SSAS server. Usually the SSAS server has the same or similar name as the

database server. 2) Expand the tree: Databases, Data Sources to expose the XXX_Reporting_Work DB 3) Right click on the DB and Select ‘Delete’

14.2 To create a new SSAS Database

Step

# Task

1) Login in to SSMS and Connect to the SSAS server. Usually the SSAS server has the same or similar name as the

database server. 2) Select the SSAS Server name and click on the ‘New Query’ Button (top left) 3) Execute the following:

<Create xmlns="http://schemas.microsoft.com/analysisservices/2003/engine">

<ObjectDefinition>

<Database xmlns:xsd="http://www.w3.org/2001/XMLSchema"

xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

xmlns:ddl2="http://schemas.microsoft.com/analysisservices/2003/engine/2"

xmlns:ddl2_2="http://schemas.microsoft.com/analysisservices/2003/engine/2/2"



xmlns:ddl200_200="http://schemas.microsoft.com/analysisservices/2010/engine/200/200">

<ID>PMReporting_Work</ID>

<Name>PMReporting_Work</Name>

<Language>1033</Language>

<Collation>Latin1_General_CI_AS</Collation>

http://schemas.microsoft.com/analysisservices/2003/engine

http://www.w3.org/2001/XMLSchema

http://www.w3.org/2001/XMLSchema-instance

http://schemas.microsoft.com/analysisservices/2003/engine/2

http://schemas.microsoft.com/analysisservices/2003/engine/2/2





Step #

Task

<DataSourceImpersonationInfo>

<ImpersonationMode>Default</ImpersonationMode>

</DataSourceImpersonationInfo>

</Database>

</ObjectDefinition>

</Create> 4) In the Query Window, clear out the existing test and copy the following into the window:

<Create xmlns="http://schemas.microsoft.com/analysisservices/2003/engine">

<ParentObject>

<DatabaseID>PMReporting_Work</DatabaseID>

</ParentObject>

<ObjectDefinition>

<DataSource xmlns:xsd="http://www.w3.org/2001/XMLSchema"

xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"






xsi:type="RelationalDataSource">

<ID>PMReporting_Work</ID>

<Name>PMReporting_Work</Name>

<ConnectionString>Provider=SQLNCLI11.1;Data Source=<SSAS-Server-Name>;Persist Security

Info=True;User ID=EPSIAdmin;Password=@@iSPE2##;Initial Catalog=PMReporting_Work;server=<SSAS-Server-

Name>;</ConnectionString>

<ImpersonationInfo>

<ImpersonationMode>Default</ImpersonationMode>

</ImpersonationInfo>

<Timeout>PT0S</Timeout>

</DataSource>

</ObjectDefinition>

</Create>

5) Replace this text <SSAS-Server-Name> with the correct SSAS Server Name 6) Execute this code

http://schemas.microsoft.com/analysisservices/2003/engine

http://www.w3.org/2001/XMLSchema

http://www.w3.org/2001/XMLSchema-instance







Step #

Task 7) Find the EPSi Windows Services (probably on the Report Server) 8) Restart the Data Mining Windows Service 9) Connect to the SSAS Server and confirm the PM_Reporting_Work database exists.


15 Appendix G: Migrating / Upgrading EPSi Versions Using SQL Server 2016 EPSi version 16.2+ is compatible with SQL Server 2016, so upgrades migrating data from EPSi versions 7.5FP1+ can be peformed with SQL

Server 2016 as long as the final EPSi version of the migration is 16.2+ (as of October 5, 2017).

Only EPSi Versions 8.0.11 CU10 and 16.1.01 CU7 can be used as part of the migration from EPSi 7.5FP1 to EPSi 16.3.X.

15.1 Client Upgrade is Migrating from EPSi Version 7.5FP1

1) Copy the EPMDBUpdater folder and the EPSIDBUpdater folder from \\stl-

epsishares\epsiinstallers\7.5FP2_WithOrigEPSIAdminPwd_SupportsSQL2014And2016_ForUpdatingToLaterVersions

2) As an Administrator, run the Eclipsys.EPM.DBUpdater.exe. Verify it completes successfully before proceeding.

3) As an Administrator, run the EPSIDBUpdater.exe. Verify it completes successfully before proceeding.

4) Notes:

a. As with any client coming from 7.5 FP1, the Report Conversion for Payroll and GL modules is still needed. This can be done

after installing 8.0.11 or 16.1

b. This version uses the original default password for the EPSIAdmin SQL account (which is the default used by versions 8.0.11

and later) and not the changed on that was in the previous latest 7.5 FP2 version. This significantly helps upgrading clients

from 7.5 FP1 up to 16.3.

c. Only use the Db Updaters/install from this 7.5 FP2 version for upgrading a client to 16.3, it should be used for any client that

will remain on 7.5 FP2.

5) Copy the 8.0.11 CU10 (or later) installation files from \\stl-epsishares\epsiinstallers\8.0.11 CU10

6) Run the 8.0.11 CU10 upgrade successfully.

a. Charge Conversions Are Still Required

7) Copy the 16.1.01 CU7 (or later) installation files from \\stl-epsiahres\epsiinstallers\16.1.01 CU7

8) Run the 16.1.01 CU7 upgrade successfully

9) Copy the 16.3 installation files from the appropriate 16.3 CUX folder

10) Run the 16.3 installation as documented (Note: 16.2 does not need to be installed, EPSi 16.3 can be installed directly from an EPSi

16.1 installation)

a. Run Report Conversions for Costing and Capital Modules

15.2 Client Upgrade is Migrating from EPSi Version 7.5FP2

1) Copy the 8.0.11 CU10 (or later) installation files from \\stl-epsishares\epsiinstallers\8.0.11 CU10


2) Run the 8.0.11 CU10 upgrade successfully.

a. Charge Conversions Are Still Required

3) Copy the 16.1.01 CU7 (or later) installation files from \\stl-epsiahres\epsiinstallers\16.1.01 CU7

4) Run the 16.1.01 CU7 upgrade successfully

5) Copy the 16.3 installation files from the appropriate 16.3 CUX folder

6) Run the 16.3 installation as documented (Note: 16.2 does not need to be installed, EPSi 16.3 can be installed directly from an EPSi

16.1 installation)

a. Run Report Conversions for Costing and Capital Modules

Documents

Installation Procedures Guide EPSi 16 · 2019. 8. 28. · 5 December 2017 EPSi™ 16.3 Installation Procedures Guide 2 Publish Date: 12/5/2017 for release 16.3 of Allscripts EPSi™