The information in this article applies to:
This article describes the steps involved in moving Tabs3 and PracticeMaster Client Server Version (CSV) software from one computer to another (e.g., from one server to another).
Note: As of Version 16, Tabs3 and PracticeMaster Platinum are the new names for the Client Server Versions (CSV) of the software. For information on moving Platinum software to another computer, please see KB Article R11375 - Moving Platinum Software from One Computer to Another.
Note: If your firm is using the Single User or Multi-User version of the software, refer to KB Article R10838, "Moving Tabs3 and PracticeMaster Software from One Computer to Another," for step-by-step instructions.
Sometimes it becomes necessary to move all Tabs3 and PracticeMaster software applications from one server to another. For example, a firm may purchase a new file server and therefore will need to move everything from the old server to the new one.
IMPORTANT STI Server Note: If you use the Client Server Version of the software and are changing network operating systems (i.e., Windows to Novell or vice versa), you must use a different version of the software. Please contact our Sales Department at 402-419-2200 for an update to your current software. Once the new software is received, perform the following steps but skip steps 8 thru 11.
* These steps are only required under specific circumstances.
Note: The information in this article assumes that you are familiar with Windows Explorer, data paths and drive mappings. If you are not comfortable with basic file and folder operations in Windows, please consult your network administrator or a qualified technician for assistance.
The first step is to make sure that no users are in any Tabs3 or PracticeMaster software application. All users must remain out of all systems for the duration of this procedure. It is recommended to use the Lock Out All Users feature (File | Lock Out All Users). When the software is locked, all other users will be prevented from starting any Tabs3 or PracticeMaster software product. Users who are already using the software will be allowed to finish their current tasks but cannot start any new tasks.
Note: You must have Manager Access Rights to use the Lock Out All Users feature.
It is also recommended that you physically verify that none of the workstations have the software open. After you do this, if the Active User List still shows that a user is in the system, reset that User ID.
Note: A User ID should NEVER be reset unless you are certain no one is logged into the system with that User ID.
Before moving the systems to a new location, run the Data File Integrity Check program (Utilities | Data File Integrity Check) in ALL systems. If the systems to be moved include Tabs3, run the Archive Data Integrity Check program (Utilities | Archive Integrity Check) as well. If GLS is among the systems that will be moved, be sure to run the Data File Integrity Check for each GLS client. Any errors reported by the integrity checks MUST be resolved before proceeding.
The next step is to make sure you know where all program files and data files are located. To determine the current working directory for each system, log in to each system and select Help | About from the menu. Either write down the location or click Print at the bottom right corner of the window, then select the Print option and click OK to print the information shown. The Current Working Directory field is the third field from the top of the first scroll window.
Note: The default data paths can be found in the Single User and Multi-User Instructions.
If you will be moving the HotBackup folder, it will be necessary to copy both the Recent and Archived HotBackup folders to the new file server. If you have a valid external copy of the folder stored in case of a system failure, it is not required that the HotBackup folder be moved.
Note: System Configuration settings for the HotBackup Schedule, HotBackup Notification, and HotBackup Folders (Client/Server | Client Server Configuration) are stored in the registry. If you want to maintain these preferences, they will have to be reentered in System Configuration at the new location. Therefore, you may want to write this information down before proceeding.
After you have determined the locations of the program and data files, use Windows Explorer to determine how much disk space is taken up by the applications and data. Then, check the target location (i.e., the location to which everything will be copied) to ensure that there is sufficient hard disk space available there. If there is not enough disk space at the new location, you will have to free up additional space before you move the systems.
Note: If moving the HotBackup folder, include its size requirement when determining if sufficient hard disk space is available.
The STI Server is available for both Windows and Novell systems. The STI Director is only utilized by Windows systems. Based on the version you currently utilize, perform the procedures below.
Note: It is strongly recommended that you do not stop the STI Server when active connections are present. Doing so can cause data corruption.
- or -
CTNTINST -STOP STI SERVER SERVICE
UNLOAD CTSRVR
Note: The STI Director is not utilized by Novell systems.
After you have prepared the new location to receive the systems by checking the available disk space and creating any additional folders required (for any data stored outside the program folder in the current location), you are ready to begin the transfer. If a network connects the computers, you can use Windows Explorer to copy all of the files from the current working directory to the new location. If a network does not connect the computers, you can copy all files onto an external hard drive or other removable media, and then copy from the media to the new location.
Note: Because of the read only nature of CD and DVD media, files copied from such media may be flagged with the read only attribute by default. If you use a CD or DVD to copy the data, you must remove the read only attribute from all files after they are copied to the new location. This can be accomplished in Windows Explorer, or by executing the following MS-DOS command inside the new current working directory:
ATTRIB /S -R *.*
You will also need to ensure that sharing is enabled for the new folder, and that users who will be accessing the folder have all rights to the program directory. You can use the following steps to configure sharing on your Windows Server:
Note: Determine if you need to copy the current HotBackup folder to the new computer, and if so, include it in the transfer process. If you will not be moving the HotBackup folder, it may be necessary to copy, at minimum, the Recent folder to the new computer. It is not required that the HotBackup folder be moved, however, as long as you have a valid external copy of the folder stored in case of a system failure.
Note: This step should only be completed if you are moving from a Novell to Windows server, or vice versa. If you are not changing the server type and are moving the Windows CSV Software, skip to the next step. If you are not changing the server type and are moving the Novell CSV Software, skip to step 11.
Separate versions of STI Server are available for Windows and Novell platforms. Therefore, you must have the appropriate version to match your server's operating system (i.e., Windows or Novell). To receive a new version of the STI Server software for your server's operating system, please contact our Sales Department at (402) 419-2200.
Before installing the new STI Server software, the following files must be removed from the new current working directory:
Important Next Steps: After removing these files, use the installation instructions provided with the STI Server manual for the remainder of the installation to the new location. Essentially you will need to install the software and then activate the STI Server as directed in Chapter 2 of the STI Server manual. Once that has been accomplished, skip to step 12 and perform the remaining steps.
HBQ is an installation helper program located on the STI Server CD for Version 14.3, and the software installation CD for Version 15. It is used to create all necessary registry entries for HotBackup/CSV installations. It also installs and starts the STI Director (STdirect.exe) as a Windows Service. When moving a CSV system to a new location, this program must be copied from the CD into the new current working directory, and then run manually.
Note: Before running HBQ, there are a few requirements that must be met to ensure the program runs correctly. Refer to the Knowledge Base article R11206, "All about HBQ," to view these requirements.
|
To copy and run HBQ.EXE |
|
|
Version 15 |
Version 14.3 |
|
|
After HBQ has finished, the window will automatically close.
For Windows-based servers, we recommend installing the STI Server as a Windows Service.
CTNTINST -INSTALL STI SERVER SERVICE
Edit the STSRVR.CFG file in the current working directory to have the correct computer name. This can be done with any text-based editor, such as Notepad or the command-line EDIT command. The STSRVR.CFG file is an ASCII text file and consists of two lines. These lines include the network name of the file server where STI Server is installed and the computer name with the port number. The first line should consist of "STI_SERVER@", followed by the name (or IP Address) of the server. An example of this line might be:
STI_SERVER@SYS1
The second line should consist of the name (or IP Address) of the server and the port number. An example of this line might be:
Sys1:1779
For a Novell-based Server, you must also edit the CTSRVR.CFG file in the new current working directory so the LOCAL_DIRECTORY points to the new location. The CTSRVR.CFG file is an ASCII text file that contains several lines of configuration settings. The line which begins LOCAL_DIRECTORY is followed by the volume and directory where STI Server is installed. Do not use drive letters. The trailing backslash is required. An example of this line might be:
LOCAL_DIRECTORY SYS1:\STI\
Note: It is important to perform this step, because skipping it will generate errors. If you are not sure of the correct computer name, you can delete the STSRVR.CFG and CTSRVR.CFG files and install the STI Server software into the new location, which will create new STSRVR.CFG and CTSRVR.CFG files with the correct computer name.
Depending on whether you use a Windows or Novell server, perform one of the following steps:
- or -
CTNTINST -START STI SERVER SERVICE
LOAD <SYS:\DIRECTORY\>CTSRVR.NLM CTSRVR_CFG <SYS:\DIRECTORY\>CTSRVR.CFGWhere <SYS:\DIRECTORY\> is where STI Server was installed (e.g., LOAD SYS:\TABS3\CTSRVR.NLM CTSRVR_CFG SYS:\TABS3\CTSRVR.CFG)
After copying all files to the correct folders at the new location, run the Data File Integrity Check (DFIC) program (Utilities | Data File Integrity Check) in all systems to ensure that the transfer process was successful. If the systems that you moved include Tabs3, run the Archive Data Integrity Check (Utilities | Archive Integrity Check) as well. If GLS is among the systems that were moved, be sure to run the DFIC for each GLS client. Any errors reported by the integrity checks MUST be resolved before proceeding.
Note: If there were no DFIC errors prior to moving the systems, there should be no errors after moving them. Therefore, if you receive DFIC errors at this point in the procedure, something has gone wrong and you should remove the systems from the new location and start over beginning with Step 6.
Program shortcuts must be updated for each user on a network who will be accessing the new location of the systems. Go to each workstation and do the following:
If you are using Windows Firewall on the server and/or the workstations, you may also need to create exceptions for the following programs found on the new server: CTSRVR.EXE, T3ACCEL.EXE, PMACCEL.EXE, and STDIRECT.EXE. For more information, see KB Article R11197 - Opening Ports in Windows Firewall.
Note: It will be necessary to reenter your HotBackup settings inside of System Configuration (Client/Server | Client Server Configuration), including scheduling regular HotBackups, confirming the location of your HotBackup folder, and setting up the HotBackup e-mail notifications.
Once you have confirmed that everything has been moved successfully, access the old location of the software and remove all program files therein.
You can temporarily retain the old data files in the old location as a backup.
Visit our Web site at http://www.Tabs3.com/support/update.html to update your program files to the most current release. This will verify that you are running the most current version of Tabs3 and PracticeMaster CSV software.
Note: As always, you can only download version updates for programs that were on maintenance at the time of the version release, and all programs must be on the same version in order to integrate.
* These steps are only required under specific circumstances..
THE INFORMATION PROVIDED IN THE SOFTWARE TECHNOLOGY, INC. KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. SOFTWARE TECHNOLOGY, INC. DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL SOFTWARE TECHNOLOGY, INC. OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF SOFTWARE TECHNOLOGY, INC. OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.
© 1999-2012 Software Technology, Inc. All rights
reserved. Terms of Use
The maker of Tabs3 and PracticeMaster
Tabs3, PracticeMaster, and the “pinwheel” symbol (
) are registered trademarks of Software Technology, Inc.
e-Mail Suggestions for the Knowledge Base to: kb@Tabs3.com
Technical Support via e-mail is not available.
Knowledge Base: http://support.Tabs3.com
Web Site: http://www.Tabs3.com
){kind=link}
){kind=link}
){kind=link}
){kind=link}
){kind=link}
){kind=link}
){kind=link}
){kind=link}