Installation & Upgrade Guide

Transcription

1 Whitepaper Installation & Upgrade Guide SDL Campaign Manager 3.0.0

2 Version Management Version history Version Date Author Distribution Feb 2014 Lisa Watts Release Associated Documents Name SDL Campaign Manager Release Notes.pdf SDL Campaign Manager Administration Guide.pdf SDL Campaign Manager Supported Architectures.pdf SDL Campaign Manager Load Process Guide.pdf SDL Campaign Manager Backup Requirements and Data Structure.pdf Configuring Pentaho Kettle for use with SDL Campaign Manager Location Supportal Supportal Supportal Supportal Supportal Supportal Installation and Upgrade Guide ii

3 Table of Contents 1 Introduction Supported Engine Version Supported Manager Version Installation Prerequisites Common Domain User Account Common Prerequisites (All Servers) Prepare App Server Prepare Engine Server Prepare SQL Server Pre-Installation Checklist SDL Campaign Manager Platform Installer Run CM.Deployer.exe Post Installation Configuration Configure Engine Server Configure SQL Server Configure Client Machines Advanced Configuration Identity Providers Upgrading to Campaign Manager Upgrade Pre-Requisites Single Sign On Pausing Campaign Activity Backup Pre Upgrade Configuration Run CM.Deployer.exe Post Upgrade Configuration Installing Kettle Uninstalling Campaign Manager Troubleshooting Fail: Upgrade from CM v 2.8.x to v3.0.0 is not valid Installation and Upgrade Guide iii

4 8.2 Fail: OS is Invalid Fail: Server is not accessible Fail: User Credentials are invalid Fail: Framework version is invalid Fail: SQL is not valid Fail: IIS is invalid Fail: Engine or later must be installed Fail: Manager Account Link Name must be specified Fail: Manager unable to validate URL Fail: Alchemy Service Credentials are invalid (or) Fail: Service Credentials failed DB Connection Fail: AltEngineCampaign.DLL locked; Fail: EMTools.DLL locked; Fail: APIClientDLL locked; Fail: EngineMutex.DLL locked Fail: Inaccessible xxxx Component (ID n) Fail: Java not installed Fail: Kettle not installed Fail: CreateNewClient.sql is not installed Fail: Install Folder cannot be created and shared Appendixes Appendix A Adding EM URLs Installation and Upgrade Guide iv

5 1 Introduction This document provides step-by-step guidance for the installation or upgrade to Campaign Manager For an overview of common Campaign Manager architecture configurations and guidelines for planning a system, please refer to the document Campaign Manager Architecture Guide.pdf. If you require further assistance, please contact your SDL account representative. The following sections are included in this document: Installation Pre-requisites on a server by server basis Step by step instructions on running the installer wizard Post Installation Configuration Upgrades Uninstalls Troubleshooting 1.1 Supported Engine Version SDL Campaign Manager is supported for use with Engine Suite or later. The latest available hotfixes should always be installed. 1.2 Supported Manager Version SDL Campaign Manager is supported for use with SDL Manager or later. Installation and Upgrade Guide 1

6 2 Installation Prerequisites 2.1 Common Domain User Account Regardless of the installation approach, on a single machine, or spread across multiple machines, a common user account must be created. We strongly recommend a domain service account that is accessible from each of the server roles. This account is established as the owner for all related Windows services, the IIS app pool, and SQL Server database connections. This account must be a local admin for each box that SDL Campaign Manager is used on. It is NOT necessary for it to be a domain admin. Grant this account the Log on as a service right on each machine. The actual account can have any name, but is referred to as the Common Domain User Account in this document. 2.2 Common Prerequisites (All Servers) NOTE The following prerequisites apply to all servers. 1. All servers must be running English-language versions of Windows Server 2008 R2 SP1 64 bit Enterprise or Data Center Editions. Web Server edition can be used for a dedicated Web Server 2. Disable Windows firewall service Note on a single box install you can leave the windows firewall on, however you must allow http(s) traffic through. Note: Windows firewall can be enabled after the installation is complete. Please see the SDL Campaign Manager Architecture guide for a list of ports that need to be opened. 3. Change User Account Control (UAC) settings to Never Notify. (Server restart is usually required.) 4. Ensure Data Execution Prevention (DEP) is turned on for essential Windows programs and services only. (Sever restart is usually required). This can be done as follows: Right click on Computer > Properties > Advanced System Settings > Advanced tab > Performance > Settings > Data Execution Prevention tab Installation and Upgrade Guide 2

7 5. The Deployer makes extensive use of Windows Management Instrumentation (WMI) to communicate between servers during the installation. If there are non-windows firewalls between servers then for a period while the deployer runs all ports must be open. 6. All machines must be able to ping each other. ICMP needs to be allowed access to all the machines through any firewall. 2.3 Prepare App Server Login to the App Server using the Common Domain User Account. It must be a local machine administrator. 1. Open Server Manager (Start > Administrative Tools > Server Manager) Right click on Roles and select Add Roles. This opens a wizard. Select Web Server (IIS) and make the following selections under each heading: Common HTTP Features select Static Content, Default Document, Directory Browsing, and HTTP Errors. Application Development - select all options. Health and Diagnostics - select HTTP Logging and Request Monitor. Security select Basic, Windows Authentication and leave Request Filtering checked. Performance - select all options. Management select IIS Management Console and IIS 6 Management Compatibility, and all child settings. (IIS 6 is necessary for the Deployer tool) Complete wizard and select [Install]. Wait for installation to complete. Select [Close]. 2. Open Server Manager (Start > Administrative Tools > Server Manager) right click on Features and select Add Features. This will launch a wizard. Select.Net framework features, select all options. When prompted click [Add Required Features]. 3. If not already present, download and install the.net Framework 4.0 Client Profile from Microsoft. 4. Ensure that the system is up-to-date by performing a Windows update. 5. Configure DCOM as follows. Select Start > Administrative Tools > Component Services expand the Component Services node > expand the Computers node > right click on My Computer and select Properties. Installation and Upgrade Guide 3

8 6. On the COM Security tab, verify that the following accounts have all options allowed for Access Permissions and Launch and Activation Permissions for both Limits and Default: INTERACTIVE, NETWORK, SYSTEM, and the Common Domain User Account. 7. On the Default Protocols tab select Properties and configure a port range for DCOM usage, typically this is Install Engine Suite 5.3. (Note installation of Engine on the App Server role does not require a license.) 9. Apply the latest Engine Suite hotfixes (if any) 10. Disable the Connection Broker service using the Control Panel Local Services option. 11. Run: the following commands to register the.net Framework 4 with IIS. C:\windows\microsoft.net\framework64\v \aspnet_regiis.exe /u C:\windows\microsoft.net\framework64\v \aspnet_regiis.exe /r 12. Recheck for Windows updates. 13. To test the install on the App server, after running the Deployer, you must install Silverlight 5.(Silverlight 4 not supported). 2.4 Prepare Engine Server 1. Login to the Engine Server using the Common Domain User Account. It must be a local machine administrator. 2. Ensure the Domain User Account acts as part of the operating system, from the same place as you grant log in as a service rights. 3. Open Server Manager (Start > Admin Tools > Server Manager) right click on Features and select Add Features. This will launch a wizard. Select.NET framework features. When prompted, click [Add Required Role Services]. Continue through the wizard selecting the defaults and select Install on the final step. 4. Run Windows update and accept all updates. If not already present, download and install the.net Framework 4.0 Client Profile from Microsoft. 5. Configure DCOM as follows. Select Start > Administrative Tools > Component Services expand the Component Services node > expand the Computers node > right click on My Computer and select Properties. 6. On the Default Protocols tab select Properties and configure a port range for DCOM usage, typically this is Installation and Upgrade Guide 4

9 7. On the COM Security tab, verify that the following accounts have all options allowed for Access Permissions and Launch and Activation Permissions for both Limits and Default: INTERACTIVE, NETWORK, SYSTEM, and the Common Domain User Account. 8. Install the Engine Suite or later (refer to the Engine Installation and Configuration Guide for further detail.) 9. Ensure that Engine has a valid license. Contact Support for further detail. 10. Apply the latest Engine Suite Hot Fixes (if any) 11. Modify the Properties of the Connection Broker Service and set it to Log on using the Domain Service Account. (Optional) Install AMS If using AMS as well as SDL Campaign Manager against the same Engine server then AMS will need to be installed on the Engine server before any new additional Engine projects are created. 2.5 Prepare SQL Server 1. Login to the App Server using the Common Domain User Account. It must be a local machine administrator. 2. Open Server Manager (Start > Admin Tools > Server Manager) right click on Features and select Add Features. This will launch a wizard. Select.Net framework features. When prompted, click [Add Required Role Services]. Continue through the wizard selecting the defaults and select Install on the final step. 3. Run Windows update and accept all updates. If not already present, download and install the.net Framework 4.0 Client Profile from Microsoft. 4. Install SQL Server 2008 R2 SP2 or SQL Server 2012 SP1 Enterprise or Standard Edition. Please note that SQL Clustering is not supported. 5. On the Feature Selection screen select: Database Engine Services Management Tools (Basic and Complete) 6. On the Instance Configuration screen, select the appropriate instance name, for example Default Instance. 7. On the Server Configuration screen on the Service Accounts tab enter the Common Domain User Account s credentials. 8. On the Database Engine Configuration screen on the Account Provisioning tab, under Authentication Mode, select Mixed Mode Authentication. Installation and Upgrade Guide 5

10 9. On the Database Engine Configuration screen on the Account Provisioning tab specify the SQL Server administrator. 10. On the FILESTREAM tab - select Enable FILESTREAM for Transact-SQL access and check all child options. 11. Finish the install. 12. Run Windows update and apply latest SQL Service Pack. Note: At the time this document was produced writing, Service Pack 2 is available. 13. Open SQL Server Configuration Manager. Expand the SQL Server Network Configuration node. Double click on Protocols and Enable Named Pipes and TCP/IP. 14. Under SQL Server Services ensure the SQL Server Agent is started and set to Automatic Start mode. 15. Stop and restart the SQL Server Service. 16. Connect to SQL via SQL Server Management Studio (SSMS) and verify you can connect. Select Windows Authentication. 17. In SQL Management Studio connect to the Server and expand Security->Logins. Ensure the Common Domain User Account has a valid SQL Login with Default Language=English and Server Roles=public, sysadmin 18. The Windows account for the user running the deployer should have an SQL Login with Server Roles=public,sysadmin. The deployer required this access to create databases on new install, and also to create and remove MSDB jobs on upgrade and uninstall. Installation and Upgrade Guide 6

11 2.6 Pre-Installation Checklist The following conditions must be met for the installation to successfully complete: Condition: Checked Notes Has the Common Domain User Account been created? Can you ping all machines from each other? Does ICMP allow access to all machines through firewall? Are all servers running Windows Server 2008 R2 SP14 bit latest Service Pack? Has the Common Domain User Account been added to each server s local Administrator group? Installation and Upgrade Guide 7

12 3 SDL Campaign Manager Platform Installer STOP: Before running the Campaign Manager Installer, be sure that for each of the server roles, you have met the list of prerequisites found in section 2. These instructions relate to a new, clean installation of SDL Campaign Manager. For upgrade instructions, please refer to section Run CM.Deployer.exe Log onto the App Server as the Domain Service Account, save the Deployer package to the App Server and unzip. Run the CM.Deployer.exe file using the Run as Administrator option (by right clicking on the exe file). This will launch the Deployer wizard, which contains approximately 24 steps, depending on the configuration options that you select. The number of machines added will depend on your planned architecture. For each machine added, there are a number of standard steps that are required. The following example details a three-box architecture, so machine configuration steps are repeated for the SQL, App and Engine machines. Step 1 Welcome Screen Click Next. Step 2 Select Installation Type Installation and Upgrade Guide 8

13 This section relates to a New Environment. See section 5 for upgrades. Step 3 Add Machine The number of machines added will depend on your planned architecture. For each machine added, there are a number of standard steps that are required. The following example details a three-box architecture, so machine configuration steps are repeated for the SQL, App and Engine machines. Click [Add Machine] to configure the first machine. Step 4 Specify SQL Server Name Installation and Upgrade Guide 9

14 Enter the SQL Server name that will host the databases. Step 5 Assign Roles to SQL Host This server by default will be the SQL Server host. You can assign additional roles to this machine here or, as in this example, they can be assigned to different machines later in the process. Installation and Upgrade Guide 10

15 Step 6 Identify SQL Instance This screen is used to assign the SQL Server instance where it is not the Default. It is recommended that you use the [Test Connection] button to confirm that you are able to connect to the configured SQL Server Instance. The CM History Export Destination Folder is where iloader will retrieve history files for import into Engine. The Staging Folder is where CM tactic output files will be stored prior to FTP. Installation and Upgrade Guide 11

16 Step 7 Specify Install Folder (SQL) This screen applies to the SQL Server machine only and is used to specify where the installation files should be placed. If there is any other SDL/ Alterian software installed on the machine, ensure that the selected folder does not conflict with an existing Alterian folder. Step 8 Add Additional Machines You would have now added the SQL Host Server and have looped back to the Add Machine step. We can now add additional machines for App Server and Engine. Installation and Upgrade Guide 12

17 Step 9 - Add Server Details (App) Step 10 Specify Server Role (App) Installation and Upgrade Guide 13

18 Step 11 Specify Install Folder (App) If enabling external agents, the Kettle install location (containing kitchen.bat and pan.bat) should be specified. This location needs to be the Drive\Kettle Folder\Data Integration in order for Kettle to be enabled. The deployer validation will check the App server contains Java Runtime and Kettle files so they must be installed prior to Validation (step 21). Step 12 Add Machine (Engine) Installation and Upgrade Guide 14

19 Step 13 Enter Server Details (Engine) Step 14 Specify Server Role (Engine) Installation and Upgrade Guide 15

20 Step 15 Specify Install Folder (Engine) Step 16 Check Machines Check that all required machines have been set up. For a three-server architecture, the screen will appear as above. Additional Engine Servers can be added if required. Installation and Upgrade Guide 16

21 Step 17 Configure Manager Link Where you will be using the Manager application to deliver messages in Campaigns, populate the following screen with applicable Manager account details. The following Manager URLs are available: These are regional, based on the data center where your account is hosted: Location Bristol Denver Sydney EM URL http(s)://uk56.em.sdlproducts.com http(s)://us56.em.sdlproducts.com http(s)://au56. em.sdlproducts.com Click [Test Connection] to test the connection. Note: The Account details shown in the screenshot are for example purposes only. Additionally, you must use a regular login and password in the EM Login\Password above. You may NOT use an SA account. The account you use will associate the install with the EM client associated with the login\password provided. Installation and Upgrade Guide 17

22 Step 18 Configure Notifications Step 19 Enter Domain Service Account Details Leaving the Campaign Manager Services should use Integrated Security when connecting to the database checkbox checked is recommended. Installation and Upgrade Guide 18

23 Step 20 Assign URLs If you select SSL then this has to be the same for both SDL Campaign Manager and Manager. The integration will not work if they do not share a protocol. Note that the CM Deployer will configure SSL settings in the website web.config files, as well as in the database. However, you will need to install the SSL certificate in IIS, as well as add the necessary bindings to the hosting site. If you would like to use Windows Authentication check the Configure NTLM Authentication check box. Please see the Enabling Windows Authentication section of the SDL Campaign Manager Administration Guide.pdf for further information on how to configure Windows Authentication. Note that the above URLs are for example purposes only. Installation and Upgrade Guide 19

24 Step 21 Validate Installation Click the [Validate Installation Plan] button to perform final validation of the configured parameters. If successful, a Validation Succeeded message will be displayed. Step 22 Save Set Up Click the [Save This Setup] button to save the setup to a secure location. Installation and Upgrade Guide 20

25 Step 23 Terms and Conditions Click [Next] to agree to the Terms and Conditions Step 24 Perform Installation Once the install is validated, click [Install] to start the process using the parameters entered in previous steps. A confirmation message will be displayed once the installation is complete. Installation and Upgrade Guide 21

26 Launching the Installation To launch the installation: 1. Select the URL configured in step The User Name is SYSTEM 3. The Password is password Installation and Upgrade Guide 22

27 4 Post Installation Configuration This section details the extra configuration steps that must be taken on the App Server once the installation has successfully completed. Assuming that the Deployer has setup the IIS sites and App pool, and that all required certificates and services are installed, you will need to configure external DNS to point to external IP for the FQDN of host headers. If the URL scheme {http or https) differs between the Silverlight hosting applications and the image you want you must verify the app server has access to the image urls. This may include editing the web.config file to include proxy settings. 4.1 Configure Engine Server This section details the extra configuration steps that must be taken on the Engine Server once the installation has successfully completed. The following Engine configuration changes should be made: Or: 1. We recommend you configure Engine to use external surrogates when used with Campaign Manager to increase resilience. To do this: Use AMC -> Engine and Server Configuration -> Process Configuration. Then in machine settings change the machine name from to Click [Update Machine] then [Save]. 2. Use AMC to set the following configuration option using the Engine Configuration Applet: AllowDuplicateColumnsInTemplate=TRUE 3. To be able to use the pause/resume and attribution features the Application server must be accessible via hhtp:// or (step 20) from the Engine server. If it is not accessible you can either: Adjust DNS to properly resolve the FQDN of the application server Add a host entry to the Engine server Installation and Upgrade Guide 23

28 Please note that running anti-virus software on certain Engine server folders can severely impact system performance and Engine functionality. The following Engine folders should be excluded from any anti-virus scan: Main Repository Folders for any Engine projects Engine temp folders: internal temp folders and machine settings temp folders (located under Process configurations). 4.2 Configure SQL Server This section details the extra configuration steps that must be taken on the SQL Server once the installation has successfully completed. To lockdown SQL permissions: for the SQL login used for the AlchemyDSA On Server Roles tab o o o The bulkadmin and public roles should be checked. The dbcreator role should be checked if planning to create additional client databases. The sysadmin server role can be cleared. On User Mapping tab: o Check the public and db_owner roles checked for Alchemy, AlchemyStore, almain, AlterianAuth, and any additional client databases You must provide access to the alchemy domain service account to xp_cmdshell. In SQL Management Studio, click the master database and [new query] and enter: EXEC sp_xp_cmdshell_proxy_account 'DOMAIN\user','password' GRANT exec ON xp_cmdshell TO [DOMAIN\user] Change DOMAIN\user and password to the username and password for the alchemy domain service account. 4.3 Configure Client Machines The optimum screen resolution for accessing the Campaign Manager client is 1440 x 900. The application can still be used at lower resolutions, but note that usability issues may be experienced, for example scroll bars not displaying correctly. Install Silverlight 5 on each client machine that will be using the software. Installation and Upgrade Guide 24

29 5 Advanced Configuration 5.1 Identity Providers Single sign on, with SDL authentication, will work without the need for any configuration. Active Directory/Windows Authentication is documented in the Enabling Windows Authentication section of the SDL Campaign Manager Administration Guide.pdf. For all other SAML2.0 external identity providers please contact Support. Installation and Upgrade Guide 25

30 6 Upgrading to Campaign Manager The SDL Campaign Manager Installer can be used to upgrade existing systems, provided those systems were originally installed using the Installer. 6.1 Upgrade Pre-Requisites Before upgrading to Campaign Manager ensure that you have already upgraded to the previous major release, 2.9.0, or a hot fix or service release. 6.2 Single Sign On Please note if you are not currently using single sign on, and wish to, we recommend you perform the upgrade and then contact support for information on how to add single sign on. If you already use NT Authentication you will need to change the value of the following held in the Alterian\Alchemy\Alterian.Alchemy.HostingSite\web.configfolder: <add key="authservice" value=" To: <add key="authservice" value=" DOMAIN>/auth/AlterianAuthentication.svc/httpscert"/> 6.3 Pausing Campaign Activity It is necessary to pause campaign activity prior to carrying out any software upgrade. Please see the SDLCampaign Manager Load Process Guide.pdf for information on how to do this. 6.4 Backup SDL recommends that that the following are backed up prior to beginning the upgrade. Campaign Manager websites SQL Server databases: o o o o All client databases AlchemyStore AlMain AlterianAuth Installation and Upgrade Guide 26

31 6.5 Pre Upgrade Configuration The installer for CM assumes you have already converted to a single site configuration as part of CM install or upgrade. Before upgrading the Engine Server we recommend that you run the CM Deployer up to, and including, the orderly shutdown step (step 5). This will stop the CM sites and services to prevent connections to Engine during upgrade. Save the Installer package to the App Server. 6.6 Run CM.Deployer.exe Run the CM.Deployer.exe file using the Run as administrator option. This will launch the Installer wizard. Step 1 Welcome Screen Click Next. Step 2 Select Installation Type For an upgrade, select Upgrade Existing. Installation and Upgrade Guide 27

32 Step 3 Enter SQL Server Credentials Type in the SQL Server name and click the [Test Connection] button to confirm that it is valid. Step 4 Check Server Credentials The configured Application, SQL, and Engine servers will be displayed. For a standard upgrade there should be no need to edit server credentials. Click [Next]. Installation and Upgrade Guide 28

33 Step 5 Perform Orderly Shutdown This process will shut down the CM sites and services, however if you need to upgrade Engine we recommend you do this at this point. Step 6 Confirm Orderly Shutdown Installation and Upgrade Guide 29

34 Step 7 - Validate Click [Validate] to confirm all entered credentials and configuration settings. You will not be able to click [Next] until the validation has successfully completed. Installation and Upgrade Guide 30

35 Step 8 Upgrade Click the [Upgrade] button to start the upgrade. You will receive a message when the upgrade is completed. Installation and Upgrade Guide 31

36 If Manager account links have been created as part of the upgrade procedure to Campaign Manager they will be visible to all users. Please see the SDL Campaign Manager Administration guide.pdf for information on how to change the permissions of these links. Click [Upgrade] The deployer will attempt to create Manager links for existing Manager accounts. Please see the SDL Campaign Manager Administration Guide for details on how to verify the link details. Installation and Upgrade Guide 32

37 6.7 Post Upgrade Configuration To lockdown SQL permissions: for the SQL login used for the AlchemyDSA Within SQL server management studio select Security > Logins > [AlchemyDSA] On Server Roles tab o o o The bulkadmin and public roles should be checked. The dbcreator role should be checked if planning to create additional client databases. The sysadmin server role can be cleared. On User Mapping tab: o Check the public and db_owner roles checked for Alchemy, AlchemyStore, almain, AlterianAuth, and any additional client databases You must provide access to the alchemy domain service account to xp_cmdshell. In SQL Management Studio, click the master database and [new query] and enter: EXEC sp_xp_cmdshell_proxy_account 'DOMAIN\user','password' GRANT exec ON xp_cmdshell TO [DOMAIN\user] Change DOMAIN\user and password to the username and password for the alchemy domain service account. 6.8 Installing Kettle Kettle is an optional installation required in order for external agents to be used. Installing Kettle takes place after you have upgraded to Campaign Manager For information on how to install kettle and configure Campaign Manager to use Kettle please see the Configuring Pentaho Kettle for use with SDL Campaign Manager guide. Installation and Upgrade Guide 33

38 7 Uninstalling Campaign Manager A full uninstall of Campaign Manager can be carried out using the Deployer. Note that this will remove all SQL Server databases, all shares and system files, and all related services. Please ensure that the bcp folder has been removed from the SQL server, and the temp folder has been removed from the App Sever. Backups should be taken if there is a requirement to retain any of these files. Prior to uninstall, the administrator should shut down Engine. To perform an uninstall of Campaign Manager 1. Ensure that Engine has been shut down and that nucleus.exe and atom.exe are not running. 2. Save the Installer package to the App Server. 3. Run the CM.Deployer.exe file. This will launch the Installer wizard. 4. Select the Uninstall option and run navigate the wizard selecting applicable options. Installation and Upgrade Guide 34

39 8 Troubleshooting For each deployer run, a CM.DeployerLog txt file is created in the same folder as the deployer EXE. This contains information logged during usage of the wizard and execution of the install/upgrade/uininstall. If reporting an issue with SDL Support, please also include the log file to assist with investigation. The validation step also performs a range of checks, to highlight potential issues with the install/upgrade. The section provides additional information, to help with resolving error messages that may appear. 8.1 Fail: Upgrade from CM v 2.8.x to v3.0.0 is not valid Check that version 2.9 is installed. It is not possible to upgrade to version without firstly upgrading to the previous major release, 2.9.0, or a hotfix. 8.2 Fail: OS is Invalid Check all servers have Microsoft Windows Server 2008 R2 Standard, Enterprise, Datacenter installed. Microsoft Windows 7 Professional is also allowable, but not supported 8.3 Fail: Server is not accessible This indicates the server cannot be accessed via Ping. Check the items in Section 3 of the install guide e.g. firewall configuration between servers; Check the common domain account has local administrator access to all servers; Check the servers are accessible on the domain e.g. by using the command line Ping utility to verify accessible. 8.4 Fail: User Credentials are invalid Check the common domain account has local administrator access on all servers. 8.5 Fail: Framework version is invalid Check all servers have Microsoft.Net framework v4 64 bit installed. 8.6 Fail: SQL is not valid The deployer expects SQL 2008 R2 Standard or Enterprise Edition product version nnnn.n or SQL Server 2012 Installation and Upgrade Guide 35

40 To check the product version use SELECT on the SQL Server. 8.7 Fail: IIS is invalid The deployer expects IIS Fail: Engine or later must be installed Check the Engine version meets this requirement on both the App Server and Engine server/s. 8.9 Fail: Manager Account Link Name must be specified The link name must be completed in Step 17 Configure Manager link. Clicking the [Test Connection] button will populate this with a default link name, based on the EM account details Fail: Manager unable to validate URL Check the Manager URL is reachable from the App server (e.g. using Internet Explorer) 8.11 Fail: Alchemy Service Credentials are invalid (or) Fail: Service Credentials failed DB Connection Check the service account has local admin rights on each server see section 3.1. Check the account has a corresponding login on the SQL Server. On a clean install, this should be a member of the sysadmin role, before proceeding with locking down the permissions after the install Fail: AltEngineCampaign.DLL locked; Fail: EMTools.DLL locked; Fail: APIClientDLL locked; Fail: EngineMutex.DLL locked The CM Deployer needs to update files that can be held open by Engine sessions. At the validation stage, the CM Deployer should have already completed an orderly shutdown of CM sites and services. To release locked Engine files, wait for active processing to complete, before using the AMC Orderly shutdown option on the affected Engine server/s. The Microsoft Windows Process Monitor tool can also be used to confirm which process is holding the file open. Installation and Upgrade Guide 36

41 8.13 Fail: Inaccessible xxxx Component (ID n) The deployer checks that each component is accessible prior to upgrade. The component information is obtained from the Almain.AL.ProcessIndex table, which contains an ID, hostname, and networkpath for each component. The validation message will provide an ID for a component entry that cannot be reached. This may be due to an accessibility problems (e.g. the deployer cannot reach the file share indicated by the networkpath). To verify this, use Windows Explorer to ensure the networkpath can be reached, and is writeable (e.g. create a temp file). If the component entry is invalid (e.g. the networkpath doesn t exist) please contact Support. This may be due to a previously failed install, and the component should be reviewed and removed if necessary before retrying validation Fail: Java not installed If the Enable External Agents option has been selected in Step 11, the deployer will check if the Java Runtime Environment (32 or 64bit) is present on the App server. Checked that JRE is present via Control Panel -> Programs -> Programs and Features, and install if missing Fail: Kettle not installed If the Enable External Agents option has been selected in Step 11 when installing Campaign Manager, the deployer will check for the existence of kitchen.bat and pan.bat in the specified Kettle Installation Folder. Check the Kettle zip has been extracted to the location specified in Step 11, and the kettle and pan.bat files are present. Correct the location and/or setting if necessary Fail: CreateNewClient.sql is not installed This fail occurs when trying to copy this file on a SQL Cluster environment. The file can be manually copied to the location, after the deployer has finished, if required Fail: Install Folder cannot be created and shared This fail occurs if the deployer cannot create or share the installation folder due to insufficient permissions. Perform the following checks: Installation and Upgrade Guide 37

42 That the deployer was started using the Run as Administrator option The deployer user is a local admin That the File and Print sharing feature is enabled on the server That the firewall is disabled Installation and Upgrade Guide 38

43 9 Appendixes 9.1 Appendix A Adding EM URLs This appendix documents how to add an EM URL to Campaign Manager if the EM URL was not created at the time Campaign Manager was deployed. db_owner access to Almain, AlterianAuth and CM client databases are needed to run the utility. The utility uses Windows Authentication to connect with the SQL Server. Adding an EM URL 1. Run the SysAdminApp.exe utility located in the PauseResume folder under the CM install location on the Engine Server. 2. Open a command prompt and change directory to the PauseResume folder location. 3. Run the utility using the following command: Sysadminapp /sqlserver=sqlservername /addemsite If you have multiple CM URLs configured the utility will ask which CM URL to associate the new EM site with. Please replace sqlservername based on your SQL Server name. If the CM SQL Server isn t the default instance, supply the sqlserver as sqlservername\instancename. If SQL Server is installed as the default instance, please use the machine name rather than (local) or. The utility only adds an EM site if an EM site has not already been configured. Installation and Upgrade Guide 39