Skip to content
English
More support Sign in
Contact us
  • There are no suggestions because the search field is empty.

Manual Core Clubspeed Upgrade

Manual Core Clubspeed Upgrade

This article will walk you through the steps to upgrade the core Clubspeed version manually. 

PLEASE BACKUP SQL!!!!!!!!

TABLE OF CONTENTS

Step 1: Create Upgrade Sheet


  1. Google Drive > Shared with Me > Support > Upgrades folder
  2. Ensure there is a folder created that is named the license name of the location you are upgrading. Create one if it is missing.
  3. Go into the **Base File** folder and make a copy of the upgrade form.
  4. Move the new copy into the location's folder
  5. Rename it todays date and the version you are going to be upgrading the location to
  6. Edit the file and fill out the top section
  7. Check the boxes of the respective fields as you work through the upgrade

Step 2: Check to see if they have custom result sheet images and results sheets

  1. Navigate to https://{License Name}.clubspeedtiming.com/sp_center/register.aspx

  2. View it on dbo.ControlPanel>SettingName: UrlResultSheet
    • The name of the result sheet they are using is indicated after privatewww/[...]
    • The default speedsheet is speedsheet.aspx
      • Speedsheets can be viewed in C:/clubspeedapps/wwwroot/PrivateWWW
    • Note if they have any customizations so that we know to replace them back later.
  3. Navigate to https://{License Name}.clubspeedtiming.com/cs-registration
    • Note if they have custom images so that we know to replace them back later


Step 3: Download upgrade files


  • Check with support management for the latest files
  • Extract them to the C drive

Step 4: Check to make sure that they are not going to be using the system

Step 4: Check to make sure that they are not going to be using the system

    

    
  • Make sure that you check multiple terminals for use as well as all the activity calendars to ensure that there has been sufficient time since the last activity was ran and that they don't have any other activities scheduled later.
  • The upgrade can take multiple hours so ensure there will be no service interruption for the customer

Step 5: Stop Services

Step 5: Stop Services
  • Stop all FireDaemon services
  • Stop and disable the replication task in Task Scheduler if the location is replicating
  • Stop IIS Service
    • Look up IIS Manager in 'Windows Administrative Tools'
    • Can be done in (IIS) Manager (not the 6.0 program)by clicking on the server and then on the column at the top right hand side clicking the stop button.
    • Can be done by running command 'iisreset stop' in CMD
  • Stop SQL Service MSSQLSERVER AFTER YOU HAVE BACKED UP SQL (Step 6: Back up) 
    • Search for 'Microsoft SQL Server Configuration Manager' (this is to find them in all PCs excluding VMs)
      • For VMs got to Control Panel>System and Security > Administrative Tools > Services.msc
    • Stop in 'Sql Server Configuration Manager' or 'Services.msc'
    • Stop service 'SQL Server MSSQLSERVER'
AFTER YOU HAVE BACKED UP SQL ()

Step 6: Back up VERY IMPORTANT!

  • Clubspeed:
    1. Create a folder at C:\CSBack named YYYYMMDD_HHMM(AM/PM) if not already created.
    2. Copy the entire C:\ClubSpeed folder into the newly created folder with the exception of the CustomerPictures, CustomerSignatures, CustomerSignatures2, CustomerWaivers, CustomerWaivers2, and PaymentSignatures folders
      • If you run into an issue with a mdl file or other sql files not able to be copied over, make sure that SQLMSSERVICES is off () then 'Try Again'.
        • If using SQL Config. Manager right-click and refresh then turn off the service.,
  • Back up SQL
    1. Create a folder at C:\CSBack named YYYYMMDD_HHMM(AM/PM) if not already created.

    3. Turn on SQL services if they are off.
    4. Open Sql > Clubspeedv8 > right click >  Tasks > Back Up...
    5. Remove the back up in the box located beneath Destination.
    6. For the backup type make sure it is set to disk.
    7. Press the Add.. button and name the file: MMDDYYYYHHMM(AM/PM).bak
      • Needs to be labeled as .bak when creating backup otherwise it will not work.
    8. Press OK and the backup file should appear in the C:\CSBACK folder created when completed. 

Step 7: Restart SQL and IIS Services

  •  Restart SQL on 'Sql Server Configuration Manager' or 'Services.msc'
    • Restart SQL Server MSSQLSERVER 
    • If it does not show as Running on State column in 'Sql Server Config...' refresh 
      • Refresh by clicking on white area in 'Sql Server config..' and clicking the refresh button.
  • Restart IIS by pressing start in IIS or running command 'iisreset' or 'iisreset start' in CMD

Step 8: Start upgrade script


  1. In the upgrade files folder, run the install.bat as administrator
  2. Once the script opens your will be prompted to enter the directory of the Clubspeed folder. If the directory of the Clubspeed folder is C:\Clubspeed, just go ahead and press enter.
  3. Press Y to run the extra cultures unless told otherwise
  4. Let the upgrade script run. Keep an eye on it to make sure it runs well.

Step 9: Check log files


  • In the upgrade folder there will be log files that are created while an upgrade is running.
  • Open all the log files and ensure there were no errors, failures, or exceptions.
  • If there are any issues in the logs get with support management to address them

Step 10: Turn services back on


  • Start all FireDaemon services.
  • Enable the replication task in Task Scheduler if the location replicates

Step 11: Test the system

***ADD THE INSTALLED VERSIONS CSA FILES FOUND ON THIS LINK HERE ***

Always Back up the CSApps folder beforehand adding CSA files from google doc.   

Always add the upgrade versions' most recent CSA Files to installed version.

Ex: Version 22.1.5 is not on the google doc link. So, 22.1.3 CSA files will be added to the 22.1.5 upgrade

  • Add the CSA file prior to testing out the rest of the system. 
  • There are a number of boxes on the sheet that are referencing parts of the system to test. Make sure you test them all and check their boxes (Upgrades - Support - Google Drive)
  • For Asian locations, you will want to keep an eye out to ensure that their symbols show up fine on the receipt and result sheet. If they do not, follow this article.

Step 12: Check for SQL logs


  • After testing the system ensure that you check for SQL logs to ensure that there are no failures, errors, or exceptions

Step 13: Log the upgrade


  • Open this Sheet
  • If there is not a tab for the week you are scheduling, make a copy of the template and rename it for the week you are needing. The name should be the date of the Monday that week.
  • Fill out a row on the day on which you are scheduling the upgrade. The day is going to be the local server time.

Step:14 Make a 'Clubspeed Internal Task' Ticket

- Just so what we know who ran the upgrade 


If you have any issues regarding the upgrade that you are not able to resolve ensure that you get Support management involved asap.



Related Articles