Upgrades

You can upgrade to CampusNexus CRM from earlier versions. Be sure to confirm that the upgrade path from one version to another is tested and certified.

Note: In CampusNexus CRM the Talisma Server is referred to as the Database component.

Before Upgrading

Ensure that your current environment meets the minimum hardware and software requirements as specified in Minimum System Requirements.
The Data Management Utility cannot be upgraded from earlier versions and must be installed afresh after uninstalling earlier versions.
Ensure that all CampusNexus CRM Services are stopped before you start the upgrade process.
Uninstall and reinstall the MSDTC service on the computer where you plan to install the Database component. To do so:
1. Log on as the administrator of the computer.
2. Open the command prompt and run the MSDTC -uninstall command.
3. Type Services.msc in the Run dialog box. The Services screen is displayed.
4. Ensure that the Distributed Transaction Coordinator service is removed from the list.
5. Restart the computer.
6. Open the command prompt and run the MSDTC -install command.
7. In Services.msc, set the Startup type for the Distributed Transaction Coordinator service to Automatic.
If the Subscriber databases (Analytics/Media/WebTrak) are installed on different servers, run the upgrade process individually on every server for all Subscriber DB Servers.
Ensure that all users have logged off from the Database component prior to the upgrade process. In addition, ensure that you have taken a backup of all Server components, and that all the servers on which components are installed conform to the minimum system requirements.
The Database, Subscriber databases, and Archive upgrade must be performed only after you ensure that replication has been configured, and is running properly. Otherwise, the upgrade process will fail.
Ensure that all the steps of Talisma-Media-CustomScript Job are completed successfully before you start the upgrade process.
Ensure that the SQLServerAgent Service is not running during the upgrade process. In a distributed server scenario, ensure that the SQLServerAgent Service is stopped on all the servers.
Ensure that all the Services are running under the same domain User Account on all computers.
'Log On As' should not be under the Local System Account for these Services.
If Database or Archive is installed on a named instance of Microsoft SQL, ensure that the related MS SQL Services are running.
Upgrade Application Servers before upgrading Web Components. If you upgrade Web Components before upgrading Application Servers, information relating to Web Servers is not updated in the relevant databases.
Set the value of Linked Servers, Data Access option to True. To do so:
1. Navigate to Microsoft SQL Management Studio, open Server Objects, and select Linked Servers.
2. Select Properties from the shortcut menu. The Linked Server Properties screen is displayed.
3. Click Server Options in the left pane.
4. In the right pane, ensure that the value of the Data Access option is set to True.
5. Perform steps a through d for all Linked Servers.

For the following databases, ensure that you run the indicated scripts. They can be run before upgrading or attaching the database, or at any time after the databases are upgraded.

Database	Script
Archive	PreSetup_Archive.sql
Media	PreSetup.Chat.sql
Main	PreSetup.Main.sql
Analytics	PreSetup.Reports.sql

The scripts are available in the Scripts folder on the Anthology Inc. FTP site.

Notes:

Before running the scripts, ensure that SQL Server Agent is stopped on the database computers.
The scripts may take a long time to run depending on the size of the databases or the number of index entries in specific tables.
Run the scripts only once when upgrading from any version to the current version. If they were run when the databases were previously upgraded, it is not required to run the scripts again.
Any customizations on the Target ID column need to be updated to use the BIGINT data type to support a bigger range of values in the Target ID column.
To resolve issues that occur in custom views or relationships of the Target object created in a previous version, see the Troubleshooting Tips section of Administrator Help.

For enhanced Mailer Tab performance in the Web Client, run the following code snippet in the Main Database. It can be run before upgrading or attaching Main database, or at any time after the database is upgraded:
```
IF NOT EXISTS(SELECT TOP 1 1 FROM sys.indexes WHERE name = 'IX_tblOBMReportMailer_nOBMailerID_nTargetID' AND object_id = OBJECT_ID('tblOBMReportMailer'))
BEGIN
       CREATE INDEX IX_tblOBMReportMailer_nOBMailerID_nTargetID ON tblOBMReportMailer (nOBMailerID, nTargetID ) 
       INCLUDE (nSentStatus, dtDateOfAction, nBounceType)
END
GO
```
Notes:
- Before running the code snippet, ensure that SQL Server Agent is stopped on the Main database computer.
- The code may take a long time to run depending on the number of rows in the tblOBMReportMailer table.
If you are upgrading Main Database, run the following script if Higher Ed is installed:
```
CREATE NONCLUSTERED INDEX [IX_tblObjectType20005_bDeleted_nMergedWithID_aID_nTeamID_tName]
ON [dbo].[tblObjectType20005] ([bDeleted],[nMergedWithID],[aID],[nTeamID])
INCLUDE ([tName])
GO
```
Notes:
- Before running the script, ensure that SQL Server Agent is stopped on the Main database computer.
- The script may take a long time to run depending on the number of rows in the tblObjectType20005 table.
If your institution uses the Campaign module, run the following scripts on the Main database computer before upgrading or attaching the database or after it is upgraded:
- Create_clustered_index_on_tblOBMReportMailer.sql
- Create_clustered_index_on_tblCampaignTarget.sql
- Create_clustered_index_on_tblTargetHistory.sql
Running these scripts improves the performance of campaign processing.
Note:

Before running the script:
- Ensure that SQL Server Agent is stopped on the Main database computer.
- Campaign Dispatcher Services are stopped.
It’s recommended to run the following index script on Main database to avoid deadlocks while processing campaigns:
```
IF EXISTS(SELECT TOP 1 1 FROM sys.indexes WHERE name = N'IDX_tblCampaignTarget_nPreviousElementID')
BEGIN
       DROP INDEX IDX_tblCampaignTarget_nPreviousElementID ON tblCampaignTarget
END
GO

CREATE NONCLUSTERED INDEX [IDX_tblCampaignTarget_nPreviousElementID] ON [dbo].[tblCampaignTarget] ([nPreviousElementID])
INCLUDE ([bMoved])
GO
```
Notes:
- Before running the script, ensure that SQL Server Agent is stopped on the database computers.
- The scripts may take a long time to run depending on the size of the databases or the number of index entries in specific tables.
- Run the scripts only once when upgrading from any version to the current version. If they were run when the databases were previously upgraded, it is not required to run the scripts again.
To improve CTI performance in Web Client, it’s recommended to run the following scripts before upgrading or attaching the following databases or after they are upgraded:
- Create_clustered_index_on_tblRequest_Main.sql - On the Main database computer
- Create_clustered_index_on_tblRequest_Media.sql – On the Media database computer
Apply the following index script on each of the above computers. If both databases are installed on the same computer, apply the index only once.
```
IF NOT EXISTS(SELECT TOP 1 1 FROM sys.indexes WHERE name = 'tblSessionParticipants_nUserID_nStatus')
BEGIN
       CREATE NONCLUSTERED INDEX [tblSessionParticipants_nUserID_nStatus]
       ON [dbo].[tblSessionParticipants] ([nUserID],[nStatus])
       INCLUDE ([nRequestID])
END
```
The above script will be available in the Scripts folder on the Anthology Inc. FTP site.

Note: The Notes of the previous step also apply to this step.
It’s recommended to apply the following index script on the Main database if campaigns include the Create Object step. The script will improve any slowness that may occur in campaign processing and in the overall system due to high data volumes in the tblCampaignCreatedObjects table.

Run the script before upgrading or attaching the Main database, or at any time after the database is upgraded:
```
IF NOT EXISTS(SELECT TOP 1 1 FROM sys.indexes WHERE name = 'PK_tblCampaignCreatedObjects')
BEGIN
       ALTER TABLE dbo.tblCampaignCreatedObjects 
       ADD CONSTRAINT PK_tblCampaignCreatedObjects PRIMARY KEY CLUSTERED (aID ASC)
END
GO

IF NOT EXISTS(SELECT TOP 1 1 FROM sys.indexes WHERE name = 'IX_tblCampaignCreatedObjects_nTargetID_nObjectType_nPropID_nBaseObjectType')
BEGIN
       CREATE NONCLUSTERED INDEX [IX_tblCampaignCreatedObjects_nTargetID_nObjectType_nPropID_nBaseObjectType]
       ON [dbo].[tblCampaignCreatedObjects] ([nTargetID],[nObjectType],[nPropID], [nBaseObjectType])
END
GO
```
Notes:
- Before running the script, ensure that SQL Server Agent is stopped on the database computers.
- The script may take a long time to run depending on the number of rows in the tblCampaignCreatedObjects table.

It’s recommended to run the following index script on the Main database to avoid slowness of operations in Desktop and Web Client due to data growth in the tblCampCommTargetMergeValueResultSet table:


IF NOT EXISTS(SELECT TOP 1 1 FROM sys.indexes WHERE name = N'IX_tblCampCommTargetMergeValueResultSet_nTargetBatchResultSetID')
BEGIN
       CREATE INDEX IX_tblCampCommTargetMergeValueResultSet_nTargetBatchResultSetID
       ON dbo.tblCampCommTargetMergeValueResultSet (nTargetBatchResultSetID)
END
GO

Run the following index scripts on the Main database to prevent SMS dispatchers from occasionally switching to a hung state:


IF NOT EXISTS(SELECT TOP 1 1 FROM sys.indexes WHERE name = 'IX_tblObjectType20042_nCommunicationType_nTargetID_nElementID')
BEGIN
       CREATE NONCLUSTERED INDEX [IX_tblObjectType20042_nCommunicationType_nTargetID_nElementID]
       ON [dbo].[tblObjectType20042] ([nCommunicationType],[nTargetID],[nElementID])
       INCLUDE ([aID],[nDeliveredStatus],[nStatus])
END
GO

IF NOT EXISTS(SELECT TOP 1 1 FROM sys.indexes WHERE name = 'IX_tblOutboundSMS_nCampaignID_nTargetID_nCustID')
BEGIN
       CREATE NONCLUSTERED INDEX [IX_tblOutboundSMS_nCampaignID_nTargetID_nCustID]
       ON tblOutboundSMS ([nCampaignID], [nTargetID], [nCustID])
       INCLUDE ([aSMSMessageID])
END
GO

IF NOT EXISTS(SELECT TOP 1 1 FROM sys.indexes WHERE name = 'IX_tblSMSDetails_nMsgId')
BEGIN
       CREATE NONCLUSTERED INDEX [IX_tblSMSDetails_nMsgId]
       ON tblSMSDetails (nMsgId)
END
GO

Apply the following scripts on the Main Database computer. They will improve any slowness in Business Administrator performance during rule modification. Additionally, the rule log clean-up process is optimized, and the maximum limit for deleting rule log records is increased:
- Create_clustered_index_on_tblActionTrace_Main.sql
- Create_clustered_index_on_tblRuleTrace_Main.sql
- Create_clustered_index_on_tblConditionTrace_Main.sql
The above scripts are available in the Scripts folder on the Anthology Inc. FTP site.
Note:
- Before running the scripts, ensure that SQL Server Agent is stopped on the Main database computer.
- The scripts may take a long time to run depending on the size of Main database or the number of index entries in specific tables.
- Run the scripts only once when upgrading to the current version. If they were run when Main database was previously upgraded, it’s not required to run the scripts again.

Upgrade to CampusNexus CRM

Perform the steps described in this procedure if you are upgrading to CampusNexus CRM from a version prior to Talisma 9.2.

To upgrade to CampusNexus CRM, follow this sequence:

Stop the SQLServerAgent Service. In a distributed server scenario, ensure that the SQLServerAgent Service is stopped on all servers.
If you are using Print Templates, upgrade Print Templates before upgrading the Database component.
Upgrade to CampusNexus CRM Database. Upgrade the Main database before upgrading the Subscriber database on a distributed environment.
Check the error log file to ensure that the upgrade is successful. This file is located in the <Drive name>:\Program Files\Common Files\Talisma Shared\Setuplog\<database name>\dbupdatelog folder on your computer. Check all output files in the dbupdatelog folder for errors.
Check the Setup log files. These files are located in the <Drive name>:\Program Files\Common Files\Talisma Shared\Setuplog\<database name> folder on your computer.
Upgrade Application Server.
Upgrade all other CampusNexus CRM components.
If the Database component and CRM Services are installed on the same computer, upgrade the CRM Services by running the ServiceUpgrade setup.
After the upgrade process, ensure that all computers are restarted.

Notes:

If you upgrade Web Components, the following error message is displayed when users log on to Business Administrator:

The directory '/bizadmin/App_GlobalResources/' is not allowed because the application is precompiled.

Solution: Navigate to the path <Drive name>:\Program Files\Talisma Web Components\BusinessAdministrator on the Web Components computer and delete the precompiledapp.config file.

This step is not required if you upgrade from a fresh 9.X installation.

Upgrade the Database Component

This section describes the procedure to the Database component in a distributed server scenario.

Example

The Database component is installed on two different computers with Main database on one computer (A) and Distributor, Analytics, Media, and WebTrak databases on another computer (B).

Before upgrading the Database component, perform the steps described in the following procedures:

Run the Sproc_GetRulesAndCampaignWithFireEvent.sql Script

The following features are deprecated in CampusNexus CRM:

The Fire external action option in the Automatic Step and Manual Task Campaign Actions in Client
The Fire Event <Text> action in rules in Business Administrator

Perform the following steps before upgrading to CampusNexus CRM:

Run the Sproc_GetRulesAndCampaignWithFireEvent.sql script on the computer where the Main database is available.

It lists campaigns in which the Fire external action option is selected and rules in which the Fire Event <Text> action is included.
Use the information to clear the following:
- In Client – Clear the Fire external action option in the Automatic Step and Manual Task Campaign actions.
- In Business Administrator – Delete the Fire Event <Text> action in rules.
Review and modify business flows of the affected campaigns and rules, if required.

The script is available in the path Scripts\Sproc_GetRulesAndCampaignWithFireEvent.sql.

Notes:

If the script is not run, and the deprecated Campaign and Rule features are in use when you upgrade the Main database, the upgrade process aborts and the following content is logged in the TLSetupDBErrors_<Date>_<Time>.log file:

Following Rules are associated with FireEvent Action Type:<<Rule name>>

Following Campaigns Steps are associated with FireExternalEvent Option:<<Campaign name>>-<<Step name>>

Use the information in the log file to clear Campaign and Rule settings as described in step 2 above.

Impact of Upgrading the Database

Perform the steps described in this procedure if you are upgrading to CampusNexus CRM from a version prior to Talisma 9.2.

Note: In a scenario where you want to upgrade the Database component prior to Talisma 9.2 version, and install databases of multiple customers on a single SQL Server instance, you must first detach any previous versions of databases and then install the Database component afresh by attaching the databases. Databases of multiple customers can then be attached or installed afresh on the same SQL Server instance.

When you upgrade a previous version of the Database component, the following changes are reflected:

Consider a scenario where a single CampusNexus CRM database named tlmain is upgraded to CampusNexus CRM. The name of the customer is tlmain.

While upgrading the Database component using the Installation Manager, specify the name of the Main database, for example, tlmain.
When the upgrade process is completed successfully:
- A folder named tlmain is created under Talisma Shared folder.
- All files related to Database Administrator will be removed from Talisma Shared and Talisma Server folders. You must install Database Administrator afresh using Installation Manager. It is recommended to install Database Administrator on the computer where you want to create the CRM Services.
- Registry key folder is suffixed by the database name.
When you run the Database setup, only the Database component will be upgraded. To upgrade CRM Services, you must run the CRM Services Upgrade setup. This procedure is applicable if the Database component and CRM Services are available on the same computer or multiple computers.
- The Job Service and Campaign Dispatcher services will continue to remain as is. You must run the CRM Services Upgrade setup to upgrade these services.
- The Offline Sync and HealthCheck Services will be deleted. You must use Database Administrator to create Webform Sync (previously known as Offline Sync Service) and HealthCheck Services.
- The Notification Service will be deleted; however, the Notification feature will continue to function as is. You can change the Notification frequency using the Global Options in Business Administrator.
- In addition, Scheduled Report (TLRptXL.exe) will be removed. You can create this service using Database Administrator on any computer.