/
Additional Install Instructions For Fall 2021

Additional Install Instructions For Fall 2021

Owned by Geraldine Polster
Jul 19, 2023
15 min read

TraCS FAQ—Additional Instructions for Fall 2021

NOTE: These instructions revised 3/9/2022. Please replace any previous version with this one.

 

The Fall 2021 Update adds significant new functionality to TraCS. As a result, some additional follow-up steps are required to fully install the update. *

The special one-time instructions below replace the standard update instructions found in Task 5.2 of the Badger TraCS Maintenance Guide. Once these special instructions have been performed you may go back to using the standard procedures found in Task 5.2 of the Badger TraCS Maintenance Guide for future WI Pack updates.

*NOTE: The Additional Instructions for Fall 2020 must be completed before completing the instructions found in this document. If you have not completed the Additional Instructions for Fall 2020 or if you are unsure whether you have or not, please contact Badger TraCS for assistance.

*Note: SQL Server Agencies: TraCS supports version 2012 and above. If your SQL server is a version lower you need to upgrade the server to a newer version. This will not install properly with lower versions.

 

Read through the entire task before beginning. All steps must be done in order. All computers need to be updated together as there could be issues with Agency Tables being out of sync.

 

The following Guides have been updated and are available for download.

 

  • The Installation Guide contains significant updates. We recommend that you download a new copy and destroy all previous copies.

  • The Maintenance Guide has been updated. It places all the tasks that you might do on an ongoing basis in one convenient location. We recommend that you download a copy.

  • The User Guide has been updated. It places all the tasks that you might do on an ongoing basis in one convenient location. We recommend that you download a copy.

  • The Office Guide has been updated. It places all the tasks that you might do as an office administrator. We recommend you download a copy.

 

Additional documentation and software are available as well.

  • The “As-Built” documentation template that you can use to document key configuration settings in TraCS. It is available here: https://trust.dot.state.wi.us/tracs/documentation/tracsdocumentationtemplates.zip

  • Training Software— the training software has been updated. It is permissible to install the training software on a computer that is also running the production version of TraCS; the two may now run side-by-side. We do not recommend installing the training software on your master computer. See Task 4.4 in the Maintenance Guide for information on downloading and installing the new version of the training software.

Task: Upgrading TraCS Software to Fall 2021 Release

  1. Get an updated copy of TraCS10.zip

    1. Download latest version of tracs10.zip: https://trust.dot.state.wi.us/tracs/software/tracs10.zip

    2. Extract the contents of the file to a folder of your choosing on your network or to a USB Flash Drive.

    3. Copy the TraCS - Baseline Install XX.XX.exe, and InstallTraCS.bat to your distribution folder.

    4. Remove any older baseline installation files in your distribution folder.

  2. Ensure that all TraCS Office users are logged out. (Field units, or squad cars, running the mobile version may continue to operate during the upgrade.)

  3. If your agency uses TraCS in Web Services mode you must email TraCS badgertracs@dot.wi.gov to enable update and, follow step 1 of Task 5.2(c) of the Maintenance Guide and then continue as below. Important: If you use Web Services, the new version of TraCS—Server Edition must be installed on your TraCS server prior to downloading any updates. Failing to do this may cause your TraCS server to become inoperable.

  4. SQL Server Only: Create new Database called Custom-->NOTE: This is new for this year and needs to be completed prior to starting the update (Agencies using Access Databases can skip down to step #5)

    1. This follows task 1.4(c) in the installation guide.

      1. Start SQL Server Management Studio (SSMS).

      2. Copy the following script in and run it. (Also attached)

-- This query should be run against the tracs_log database. -- This query is to fix the following error during a Database Upgrade: "THE CREATE UNIQUE INDEX statement terminated because a duplicate key was found for the object name 'dbo.TransLog.' -- and the index name 'Primary Key.' USE tracs_log; WITH CTE AS ( SELECT id, RN = ROW_NUMBER()OVER(PARTITION BY id ORDER BY id) FROM translog ) -- Identify duplicate records. SELECT * FROM CTE WHERE RN > 1; WITH CTE AS ( SELECT id, RN = ROW_NUMBER()OVER(PARTITION BY id ORDER BY id) FROM translog ) -- Delete duplicate records, leaving one (the original) of each duplicated record. DELETE FROM CTE WHERE RN > 1;

iii. Create the following databases

tracs_custom

  • use the same permissions as the other 4 databases

  • use the same user id and password in SQL Server that will be used for all TraCS generated SQL commands. The user ID needs the following permissions for SQL Server databases:

    • Select, insert, delete, and update permissions for all tables in the TraCS databases

    • Create table, alter table, create column, and alter column (for successful pack installation and migration of users)

    • Alter database (for successful pack installation)

  1. MS Access Only: Copy custom database to your network share.

    1. Follow link Custom Database

    2. Highlight Custom.mdb

    3. Download the file to your Network share

      1. \\myserver\TraCS\DBData

      2. This is the place all your other databases are stored.

  2. Open TraCS configuration Manager

    1. In the Setup Ribbon, Click the Database Connections button.

    2. Select Database Connection Strings.

    3. Click Add.

      1. Name should = Custom

      3. Choose SQL Server or Access. (HINT: It should be the same as your support database)

      4. Click OK.

  3. Edit the database connection for the Custom database. In the Database Location field, prefix the network folder, using the UNC naming convention, to the file path. Example: \\myserver\sharename\TraCS\DBData\Custom.mdb

  4. Access example NOTE: the access database will not be created yet so the test function will not work properly until after the update.

  5. SQL example

  6. Add custom Field Unit

    1. If you have Field Units Database Connections added

    2. Click Add

      1. Name = Custom_FieldUnit

      2. Database = Access

    3. Enter Location \DBData\Custom.mdb

    4. Click OK.

    5. Close the configuration manager.

  7. Install new update on the master computer.

    1. Start TraCS and click OK when you receive this dialog box.

    2. Log into TraCS with your System Admin account.

    3. You will receive notifications in your Windows task bar that files are downloading.

    4. and the second message

    5. When you receive the notification that the download is complete, close the TraCS application.

    6. Restart TraCS by right clicking and choosing the ‘Run as Administrator’ option.

    7. Log into TraCS with your System Admin account.

    8. Click Yes to start the update.

    9. The update will now begin to run.

    10. Special Note: If you get either of the first two error messages, screenshots below; simply press the ‘OK’ button and let the update continue to run. These errors have been identified and we are working at getting it corrected. This does not affect the installation and update. The third screenshot shows an error message where you should email Badgertracs@dot.wi.gov

  1. TraCS will automatically restart.

    1. Log into TraCS and Choose No to prevent additional computers from receiving the update.

    2. We will allow the other clients to update once the additional instructions are completed.

  2. SQL Server only: Database scripts are required for this update to add new tables and columns to your TraCS database. The Delta scripts are set on auto-run but, if you receive the following message upon logging into TraCS they did not run properly and need to be completed manually. If you did not receive this message, you may skip this step. (Agencies using Access Databases can skip down to step #14)

    1. Start SQL Server Management Studio (SSMS)

    2. Create additional tables in the tracs_data database needed for the new Supplement, Incident, and Evidence forms along with any form that contains statute information by running the new “Delta” SQL script. The script will be in the TraCS network folder (from Task 1.2, step 6b in the Installation Guide) under the DBData\SQLScripts folder. The name of the script takes the form of <Timestamp> Delta.sql. If there is more than one “Delta” script present, run the one with the most current timestamp.

  3. REQUIRED: This fall the agency tables will be upgraded and move to a separate database called custom. All agency tables will reside in this database separating the agency tables from state tables. There are 2 steps to moving to the custom database.

    1. The First step is to move the agency table data from support to custom.

      1. Log into TraCS as an administrator.

      2. In the Tools Ribbon navigate to |Maintenance| Move Support Tables 2021|

      3. Click Yes when the Create Distribution window appears.

      4. Click OK

  4. SQL SERVER ONLY: The Second Step Covert the data to the correct format per the TraCS vendor. (Agencies using Access Databases can skip down to step #16)

    1. In the Tools Ribbon Navigate to | Maintenance| Convert Support/Data to 2021 format|

      1. Click Yes

      2. Click OK

      3. If you have any more popup messages please email Badger TraCS

    2. Start SQL Server Management Studio (SSMS)

      1. Open \\Networkshare\DBData\SQLScripts\update_tracs_data.sql

      2. Complete a find and replace

        1. AgencyTracsServer with your agencies database server name

        2. Find and replace database name if not tracs_data or tracs_custom

        3. Find and replace primekey with CodeValue

        4. Run

          1. SQL server 2016 and below will get the following error message

            1. 'trim' is not a recognized built-in function name

            2. This function optimizes the data but is not required.

          2. Do a find and replace TRIM with nothing

          3. Run again.

      3. This sql script can be run multiple times. If your Field Units do not update quickly your Ordinances will come in without descriptions, if this happens run the script again to fix.

        1. It is best to get all your machines updated as soon as possible.

  5. Import new export instructions. NOTE: This is required if you plan on exporting the Incident, Supplement and Evidence forms to your RMS.

    1. Log into TraCS Configuration Manager with the System Admin access Level.

      1. Navigate to Transmission | Import/Export.

      2. Expand Export Instructions and Select Export RMS.

      3. Click the Import button.

      4. Select No, Let me Choose.

      5. Click OK

    2. Expand Forms.

      1. Hold down the CTRL key and select:

        • incidentV2.frm.exml

        • supplement.frm.exml

        • propertyV2.frm.exml

      2. Click OK.

      3. Click OK.

  6. REQUIRED if exporting to RMS: If you export crash data or citation data to your Records Management System (RMS), you are required to configure the export rules for new forms to match the requirements of your RMS. Refer to Task 3.14 in the Badger TraCS Maintenance Guide and your RMS Documentation for more information on configuring RMS export instructions.

    • The Incident and Property/Evidence forms have been updated to version 2.

    • Use the incident.frm.exml and property.frm.exml, respectively, as samples for setting up version the next version.

Put the similar forms together by using the up/down arrows (e.g. incident.frm.exml next to incidentV2.frm.exml)

If form is Active, ensure the new version of the form is Active as well (match the settings from the old version of the form).

Verify the report type using the Reports button (shown below), ensuring the file type, file name extension, and all other settings are the same (needed for ImageToRMS settings.)

NOTE: The new Incident and Property/Evidence forms only supports exporting data in the TraCS 10 format.

  1. Import new Communications Instructions. NOTE: Required if you export the supplement form to your RMS. The other 2 forms would have been set up last year.

    1. Select the Transmission ribbon menu.

    2. Click the Communications button.

    3. Expand Communications Instructions.

    4. Highlight the instruction named TransComm

    5. Set up the new form to RMS

      1. Click the Import button.

      2. Choose No, Let Me Choose.

    6. Click OK.

    7. Expand Instructions.

    8. Select multiple items by holding down the ctrl key while you select.

      1. supplementToRMS

    9. Click OK.

    10. Click OK.

    11. If your agency defined a web proxy server in Task 1.4 of the Installation Guide, you will need to enable its use for transmissions to the state. If you do not use a web proxy server, you may skip this step.

      1. Expand Communication Instructions and then TransComm.

      2. Select the all previous forms item.

      3. Click the Communications Options tab.

      4. Check the Use Defined Proxy box.

  2. ***DO NOT SKIP THIS STEP*** Create new distribution file. ***DO NOT SKIP THIS STEP*** Note this distribution is to export new user files.

    1. If you do not complete this step your field units will receive the following error message.

    2. Start the Configuration Manager if it is not already running.

    3. Export user files so that they may be distributed to field units. (Note: this step is not needed for Web Services units).

    4. Click the Users tab and then click the User Editor button.

      1. Clear the Inactive User field.

    5. Click the Search button.

    6. Select user accounts to export.

    7. If you use TraCS to manage your users, click the Select All button to select all users.

    8. If you use Active Directory to manage your users, only select the #AD_AU_USER# and #AD_TEMPLATE_USER# users. IMPORTANT NOTE: DO NOT SELECT ALL USERS

    9. Click the User Files button.

      1. The file path will be preselected to your TraCS user folder.

      2. Click OK.

      3. Wait for confirmation that the user files have been created.

    10. Start TraCS

    11. Sign in with a System Administrator account.

    12. Click the Configuration and Distribution button in the Tools ribbon menu.

    13. Click Create Distribution.

    14. Enter your agency’s 3-digit Location ID number and click OK. (NOTE: Some agencies have a different name for their distribution configuration form; use whatever is appropriate for your agency).

    15. Press the Edit button, notice the Version Number field automatically updates.

    16. Now press the Validate button to create the distribution. (There is no longer a need to press the New button to generate the version number, this is done automatically once you press the Edit button.)

      1. NOTE: Each successive distribution that runs on a computer must have a higher version number than the previous distribution. Distribution files that have a lower version number than the previously installed distribution files will not install on the target computer.

      2. NOTE: The version number that is created when you press the new button is based on the current date. If for some reason you wind up needing to create two different distributions on the same day, for example, because you made an error in the first distribution, press the new button again to increment the last digit of the version number.

      3. NOTE: This version of TraCS includes settings requested by the Forms Advisory Committee on using the TLT. These steps are required and both an office and a mobile distribution needs to be completed for the settings to take affect agency wide.

    17. REQUIRED: Ensure the Distribution Type field has both Mobile and Office. (NOTE: You do not have to complete both office and mobile distributions on one form).

    18. Ensure the Automatic Download field has both Mobile and Office if distributions are downloaded automatically. (If your Agency is using a USB (thumb drive) to end shift, you can ignore this step.)

    19. Press the validate button. If the form validates without error, you will receive a message requesting to create the distribution files. Click Yes to generate the distribution files and place them in the distribution folders for deployment.

       

    20. Click OK when the deployment message appears.

    21. Start TraCS on your master computer. Click Yes to allow other computers to begin receiving the update.

NOTE: Field units will receive a warning that their installation is incomplete until they run the new distribution. If this message persists after running the new distribution, it means that user files were not exported correctly when the distribution was made. The user files contain the new access level for the 2021 crash form and this error message must be cleared up before they can use the new form. Contact badgertracs@dot.wi.gov for assistance if you are having difficulties getting this error message to go away.

  1. Alternative Install Instructions for Fields Units

    1. If your agency normally receives updates over the Internet, but you are concerned about the size of this update, you may use theses instructions for your field units.

      1. NOTE: We strongly encourage you to use the TraCS Update server on your TraCS Mobile computer if possible since it is automatic and much faster and easier than the manual download method. The update files are smaller and take less time to install compared to the full WIPack.

    2. In your distribution folder, create a new folder called WIPack

    3. Go to https://trust.dot.state.wi.us/tracs/extranet.htm, click on the software link, and scroll to the WI Pack section.

    4. Download WIPack.zip.

    5. Unzip (extract the files) WIPack.zip to the Distribution\WIPack.

      1. IMPORTANT: do not unzip to your Distribution Mobile folder.

    6. You should now have the newest pkg file in the Distribution\WIPack folder: WIPackYYMMDD -WIPackYYMMDD.tracspack.pkg, WIMapPackYYMMDD -Full-WIMapPackYYMMDD -Full.tracsmap.pkg (where YYMMDD is the most recent patch number) and WIPack.bat file.

    7. Delete any older pack numbers in the Distribution\WIPack folder that are present from the last time you did this task.

    8. On each field unit with no connectivity:

      1. Run InstallTraCS.bat, which can be found in the Distribution folder. (See task 3-12, step 6b for location.)

      2. Accept all defaults and click next on all subsequent dialog boxes

      3. Click Finish on the final screen.

      4. Open the distribution folder.

      5. Double click MobileDistribution.bat to run it. The customizations from the master computer will be copied to the machine.

      6. Run Distribution\WIPack\WIPack.bat.

      7. The update will run.

    9. After running the install on each of your field units, start TraCS on your master computer. Click Yes to allow other computers to begin receiving the update.

 

Related content