CSV Troubleshooting and Technical Information

Last reviewed: 08/19/2008
Article ID: R11176

The information in this article applies to:

All Versions of STI Server
Version 14.3 Tabs3 and PracticeMaster Client Server Version (CSV) Software
Version 14.1 Tabs3 and PracticeMaster Client Server Version (CSV) Software
Version 12 Tabs3 and PracticeMaster Client Server Version (CSV) Software

Summary

This article contains extensive troubleshooting and technical information for STI Server and the Tabs3 and PracticeMaster CSV software.

Windows and nOVELL

Because separate versions of STI Server are available for Windows and Novell platforms, the following icons will be used where appropriate:

		Indicates the information only applies to Windows.
		Indicates the information only applies to Novell.

Please select your server's operating system. This will dynamically filter the troubleshooting information throughout this article. Selecting Both will display troubleshooting information for both Windows and Novell platforms.

Windows Novell Both

Error Messages
Status Log (CTSTATUS.FCS)
Problems Starting STI Server
Technical Information
FairCom Server Activation Utility
- FairCom Serial Number and Activation Key

Error Messages

"The server 'STI_SERVER@[computer name]' can't be found."

The Tabs3/PracticeMaster CSV software requires direct communication with STI Server in order to function. The following steps may be used to determine the source of the problem.

Verify that STI Server is running on the file server. STI Server needs to be running in order for the Tabs3/PracticeMaster CSV software to function. Information on starting STI Server is available in the STI Server manual.
If you are running STI Server as a Windows application (i.e., by double-clicking CTSRVR.EXE), you will see the Desktop Interactive Program (Fig. 2) on the server's Windows desktop. If you are running STI Server as a Windows service, the current status of STI Server can be confirmed using one of the following methods.
- To determine the current status of STI Server from a command-line prompt
  1. From the server computer, open a command-line window.
  2. Using the DOS "CD" command, change to the Tabs3/PracticeMaster program directory.
  3. Type the following command: ctntinst -status STI Server Service
  4. A message similar to the following will be displayed:
```
	Service Status for STI Server Service
	Current State: RUNNING
	Controls Accepted: STOP SHUTDOWN
	Win32 Exit: 0
	Service Exit: 0
	Checkpoint: 0x0
	WaitHint: 0x0
```
    The line for Current State will indicate the current status of STI Server.
  To determine the current status of STI Server from the Services applet
  1. From the Windows Control Panel, select Administrative Tools.
  2. Double-click Services.
  3. Select the STI Server Service from the list of services. The Status column will show "Started" if the server is running. Otherwise, it will be blank.
On a Novell server, pressing Ctrl+Esc will list the programs currently running on the server. Selecting the menu number for the CTSRVR menu option will display various connection and activity information about STI Server.
Verify that the computer name defined in the first line of the STSRVR.CFG file (i.e., STI_SERVER@[computer name]) matches the computer name of the server. This file is located in the Tabs3/PracticeMaster program directory, and is viewable via a text editor such as Notepad. Information on modifying STSRVR.CFG is available in the STI Server manual. The following procedures may be used to determine the computer name of the server.
Verify that the CTSRVR.CFG file exists in the Tabs3/PracticeMaster program directory. If this file is missing, it can be created by reinstalling the STI Server software.
Verify that the value defined for the SERVER_NAME in the CTSRVR.CFG file matches the name that appears before the "at" (@) symbol in the first line of the STSRVR.CFG file. These two values must match exactly in order for the Tabs3/PracticeMaster CSV software to communicate with STI Server. By default, the SERVER_NAME is STI_SERVER. The CTSRVR.CFG and STSRVR.CFG files are located in the Tabs3/PracticeMaster program directory, and are viewable via a text editor such as Notepad. Information on modifying these files is available in the STI Server manual.
Verify that the workstation receiving the error message can communicate with the server. This can be done using the standard PING command-line utility. The two computers must be able to communicate with each other in order for the software to function properly.
- To "ping" the server from the workstation
  - From a command-line prompt at the workstation, type "ping server_name" where server_name is the computer name of your server as determined from the previous step.
    - If the two computers can communicate with each other, an output similar to the following will be displayed:
      
      C:\> ping FS_SERVER
      Pinging FS_SERVER [192.168.200.55] with 32 bytes of data:
      
      Reply from 192.168.200.55: bytes=32 time<1ms TTL=128
      Reply from 192.168.200.55: bytes=32 time<1ms TTL=128
      Reply from 192.168.200.55: bytes=32 time<1ms TTL=128
      Reply from 192.168.200.55: bytes=32 time<1ms TTL=128
      
      Ping statistics for 192.168.200.55:
      Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
      Approximate round trip times in milli-seconds:
      Minimum = 0ms, Maximum = 0ms, Average = 0ms
    - If the two computers cannot communicate successfully, you will receive a message similar to the following: "Ping request could not find host FS_SERVER. Please check the name and try again."

Check the Windows Firewall settings or other firewall settings on the server computer. If Windows Firewall is turned on, CTSRVR.EXE must be listed as an exception in order to use the STI Server program on a network. If using Version 14.3 Client Server software, T3ACCEL.EXE, PMACCEL.EXE, and STDIRECT.EXE must also be listed as exceptions. Additional details can be found in KB Article R11197 - Opening Ports in Windows Firewall.

To check the Windows Firewall settings
1. From the Windows Control Panel, select Windows Firewall.
2. The current status of Windows Firewall is listed on the General tab of the Windows Firewall window.
  - If Windows Firewall is set to On (recommended), the Don't allow exceptions check box must be cleared in order for the exceptions to work properly.
  - If Windows Firewall is set to Off (not recommended), the exceptions do not need to be defined.
To add STI Server Programs as Windows Firewall Exceptions
1. From the Windows Control Panel, select Windows Firewall.
2. On the Exceptions tab, click the Add Program button.
3. In the Add a Program window, click the Browse button.
4. Browse to the Tabs3/PracticeMaster program directory, and select CTSRVR.EXE.
5. Click Open.
6. Click OK. CTSRVR.EXE will now be listed under Programs and Services.
7. Repeat steps 2 through 6 for T3ACCEL.EXE and PMACCEL.EXE.
8. Repeat steps 2 through 6 for STDIRECT.EXE; however, this file will be located in the Windows System directory (e.g., C:\WINDOWS\SYSTEM32).
9. Click OK to close the Windows Firewall window.
To modify the scope of an STI Server Windows Firewall Exception
1. From the Windows Control Panel, select Windows Firewall.
2. On the Exceptions tab, select CTSRVR.EXE from the Programs and Services list and click the Edit button.
3. Click Change scope.
4. Select My network (subnet) only, or the appropriate option.
5. Click OK.
6. Click OK.
7. Repeat steps 2 through 6 for STDIRECT.EXE, T3ACCEL.EXE, and PMACCEL.EXE.
8. Click OK to close the Windows Firewall window.

Depending on the version of Novell NetWare and how it is configured, it is possible that it will not correctly translate a computer name to an IP address. If this is the case, you will need to modify the first line of the STSRVR.CFG file to include the server's IP address instead of its computer name. Information on modifying STSRVR.CFG is available in the STI Server manual.

To determine a Novell server's IP address
1. From the server, press Ctrl+Esc. A list of programs will be displayed.
2. Select CONSOLE to open a command prompt.
3. Type CONFIG. This will produce an output similar to the following:
4. The server's IP address is listed following the IP address: item in the output. For the sample output above, the server's IP address would be 192.168.103.123. (Note: If more than one network adapter is installed on the server, a separate IP address will be listed for each adapter.)

Verify that the LOCAL_DIRECTORY line in the CTSRVR.CFG file is correct. This file is located in the Tabs3/PracticeMaster program directory, and is viewable via a text editor. This line is required and must specify the volume and path of the Tabs3/PracticeMaster program directory. For example, if your Tabs3/PracticeMaster software resides in SYS:\STI, the LOCAL_DIRECTORY line would read as such:

	LOCAL_DIRECTORY    SYS:\STI\

Note: The trailing backslash is required.

"The server connection limit has been exceeded."

STI Server is available in levels of 8, 16, 32, 64, 128, 256, 512, or 1024 connections. The term "connection" refers to the communication or link to the STI Server that is established for each application a user is running. For example, suppose a firm has 8 users. All 8 users have PracticeMaster running at the same time (i.e., 8 connections), 4 of the same users also have Tabs3 running (i.e., 4 more connections), and 1 of the users also has APS and TAS running (i.e., 2 more connections). This results in 14 combined Tabs3 and PracticeMaster client server version software applications (i.e., connections) running at the same time on the network.

Note: STI Server requires four connections for overhead purposes. These connections are reserved by STI Server and cannot be used by other users. For additional information, see Overhead Connections in Chapter 1 of the STI Server manual.

When the maximum number of connections has been reached, the above message will be displayed. You will be prevented from starting the Tabs3/PracticeMaster software until additional connections are made available. This can be accomplished in several ways:

Have other users close any Tabs3/PracticeMaster software products they are not currently using. Each product that is running counts toward the connection limit, so closing unused Tabs3/PracticeMaster applications will create available connections for other users.
Check the Maximum Connections and Activation Limit numbers in the Tabs3/PracticeMaster Help | About window (Fig. 1). The Activation Limit represents the number of connections you purchased with STI Server (i.e., 8, 16, 32, 64, 128, 256, 512, or 1024). The Maximum Connections represents the maximum number of connections allowed by STI Server. This is defined by the Activation Limit or the CONNECTIONS value in the CTSRVR.CFG file, whichever is lower. (Note: An unspecified CONNECTIONS value is equivalent to a value of 128.)

Fig. 1, Help | About window of Tabs3 CSV

If your Maximum Connections is less than the Activation Limit, the following procedure may be used to increase the maximum number of connections allowed by STI Server.
- To modify the Maximum Connections via the CTSRVR.CFG file
  1. From the Tabs3/PracticeMaster program directory, open the CTSRVR.CFG file via a text editor such as Notepad.
  2. Locate the line that begins with the word CONNECTIONS.
  3. If there is a semicolon (;) in front of the word CONNECTIONS, delete the semicolon.
  4. Change the number following the word CONNECTIONS to match your Activation Limit (i.e., the number of connections you purchased).
  5. Save and close CTSRVR.CFG.
  6. Restart STI Server. (Note: You do not have to restart the server computer.)

Purchase a higher connection limit. If you find that your current connection limit is not adequate, STI Server may be upgraded to a higher connection limit at any time by contacting our Sales Department at (402) 419-2200. Upon receiving a new STI Server CD with the higher connection limit, there are a few simple steps that need to be performed in order to make the new connections available.
- To install an STI Server CD with a higher connection limit
  1. Use the installation instructions provided in the STI Server manual to install the new STI Server software.
  2. Run the FairCom Activation Utility and enter your new FairCom Server Serial Number and Activation Key.
  3. If you upgraded your connection limit to 256, 512, or 1024 connections, modify the CTSRVR.CFG file appropriately.
  4. Restart STI Server. (Note: You do not have to restart the server computer.)
- The new connection limit can be verified in the Help | About window (Fig. 1) of any Tabs3/PracticeMaster CSV software product. The Activation Limit represents the current connection limit.

"The STI Server Service service on Local Computer started and then stopped. Some services stop automatically if they have no work to do, for example, the Performance Logs and Alerts service."

This is a Windows message that is displayed if a service is unable to start. In the case of STI Server Service, this message occurs if STI Server is already running. Because STI Server can be run as either a normal Windows application (i.e., by double-clicking CTSRVR.EXE) or as a Windows service, it is possible to have STI Server already running as a Windows application before attempting to manually start the STI Server Service. [Note: The Windows application mode of STI Server is also known as the Desktop Interactive Program (Fig. 2).]

If STI Server is already running as a Windows application, it is not necessary to start the STI Server Service. Likewise, if the STI Server Service is already running, it is not necessary to run STI Server as a Windows application. To avoid this message and start the STI Server Service, you must shut down the Windows application mode of STI Server before starting the STI Server Service. (Note: STI Server functions identically regardless of whether it is run as a Windows application or as a Windows service.)

"The system cannot find the path specified."

This is a Windows message that is displayed if the system cannot locate the CTSRVR.EXE executable file required to start the STI Server Service. This usually occurs if the service was installed from a mapped drive instead of the actual directory in which STI Server is installed. The following procedure may be used to determine the executable path defined by the STI Server Service.

To determine the executable path of the STI Server Service
1. From the Windows Control Panel, select Administrative Tools
2. Double-click Services.
3. Right-click the STI Server Service from the list of services, and select Properties.
4. In the STI Server Service Properties window, select the General tab.
5. The Path to executable field (Fig. 4) will list the executable path of the STI Server Service.

Fig. 4, STI Server Service Properties window

The executable path defined by the STI Server Service must match the actual path of your Tabs3/PracticeMaster program directory, and cannot include a mapped drive. For example, if your Tabs3/PracticeMaster program directory is "C:\STI" and "K:\" is mapped to "C:\STI"; then the executable path must be "C:\STI\CTSRVR.EXE", not "K:\CTSRVR.EXE".

To resolve this error, you must use the CTNTINST.EXE command-line program to first uninstall, then reinstall the STI Server Service from the correct directory location. Information on how to use the CTNTINST.EXE command-line program is available in the STI Server manual.

"The Database Server may not have been shutdown properly the last time it was used. An improper shutdown can lead to FCRP_ERRs on file opens for non-transaction files (unless the COMPATIBILITY WTHRU_UPDFLG option and WRITETHRU filemode are used). To properly shutdown the Database Server, select the 'Shutdown' option from the server's Control menu."

This is a Windows message that is displayed when starting STI Server. This message is displayed if STI Server was not shut down properly (i.e., due to power loss, hardware failure, etc.). Although only displayed when starting STI Server as a Windows application, it does not matter how STI Server was being run at the time it was shut down improperly (i.e., as a Windows application or as a Windows service). [Note: The Windows application mode of STI Server is also known as the Desktop Interactive Program (Fig. 2).]

If you are able to start STI Server, then this error will be resolved. However, it is important to determine why STI Server was not shut down properly so that it does not become a recurring problem.

"Warning: STSRVR.CFG not found."

This file is required by the Tabs3/PracticeMaster software to communicate with STI Server. If this file is missing, it can be created by reinstalling the STI Server software.

"The STI Server must be at least version 8.27.159" "The STI Server must be at least version 8.27.143" "The STI Server must be at least version 8.27.124"

Version 14.3 Tabs3 and PracticeMaster Client Server Version software cannot be used with STI Server version 6. The most recent versions of Tabs3 and PracticeMaster Client Server Version software (with a release date of 04/10/2008 or greater) require STI Server version 8.27.159. The methods listed here may be used to determine what version of STI Server you are currently using. If you receive this message, you must install the most recent STI Server CD that was shipped to you.

"The Port number for the Tabs3 Accelerator is invalid. Match the IP Address or Hostname specified for the STI Director Service."
"The IP Address or Hostname for the PracticeMaster Accelerator does not match the IP Address or Hostname specified for the STI Director Service."

The computer address of the STI Director Service, which is configured using the STDirector Control Panel applet, does not match the computer address of the specified Accelerator. If the Accelerator and the STI Director Service are both being run from the same server, these addresses should match. Verify that the IP Address or Hostname for the specified Accelerator is correct, and click OK to continue. If this is incorrect, click Cancel and correct the address for the Accelerator.

The General Ledger software contains an invalid GLS Data Path for one or more GLS Clients. As a result, the software is running without Client/Server functionality. Once the GLS Data Path has been manually fixed, you will need to run the CSCONV14.EXE program to convert the data. Detailed information regarding how to resolve the invalid GLS Data Paths can be found in Knowledge Base Article R11176 at www.support.Tabs3.com.

CSV Version 14.3 software requires that the GLS Data Path for all defined GLS clients be relative paths AND be located in a folder under the current working directory. This is required in order for HotBackup to back up data for all GLS clients. Start GLS and run a Data File Integrity Check. There will be one or more Error 25's or Error 28's reported, thus indicating which GLS client has an invalid path. You must address these invalid paths by editing the GLS Data Path, which may require moving the GLS client data. KB Article R11191, How to Move GLS Clients, includes step-by-step procedures regarding how to move GLS client data. Alternatively, if the GLS Client is no longer used, the GLS client can be deleted; however, you will want to make sure that this is the desired course of action. Invalid GLS Data Paths must be addressed before you will be able to use the Client Server version of the software. Once you have addressed the invalid path, rerun the CSCONV14.EXE program from the server (located in the Tabs3 program directory).

Note: As an alternative, if the CSCONV14.EXE program was previously run, you can determine which GLS client(s) have invalid GLS Data Paths by viewing the contents of the CSCONV14.LOG file instead of running a Data File Integrity Check.

"Unable to copy director file to windows directory" message appears at the end of an update.: This message indicates that during the install either the STI Director Service has restarted or STDirect.exe is being held open. To resolve the issue, the user needs to manually shut down the STI Director Service in the Control Panel, and then confirm that STDirect.exe is not running in the Task Manager via the Processes tab. Once this has been done, copy the STDirect.exe file found in the program directory into the Windows directory, and choose Yes to overwrite the file when prompted. You can then restart the STI Director Service in the Control Panel, and begin working in the software again.

Unable to lock the Task File

This message indicates that the STI Director Service is unable to lock the Task File.

Cause: This error occurs if the Client Server Data Directory path is incorrect or the STI Director Service has insufficient rights to the Client Server Data Directory.

Solution: The following is a list of ways to troubleshoot:

Incorrect Client Server Data Directory: Make sure the Client Server Data Directory is valid from the server's point of view. If it is a new install, use the following steps to copy and run HBQ. If it is an existing dataset that has already been working, then use the following steps to edit the DataDirectory registry key.

New Installs - Copy and Run HBQ

On the server where the STI software is installed, insert the STI Server CD.
Close out of the installation window if it automatically runs.
Open My Computer.
Right-click the CD drive and select Explore.
Double-click the Server folder.
Right-click HBQ.EXE and select Copy.
Paste HBQ.EXE into the program directory.
Double-click HBQ.EXE in the program directory to run the program.
Type "Y" and press Enter to run HBQ.EXE, as shown below.

Existing Installs - Edit DataDirectory Registry Key

On the server where the STI software is installed.
1. Click start, and then select Run.
2. Type REGEDIT into the field.
3. Click OK.
Verify that the Data ID in the Registry matches the Data ID in System Configuration.
1. Open System Configuration.
2. Select Utilities | Change Data ID from the System Configuration menu bar.
3. Write down the Data ID found here.
4. Back in the registry editor, expand HKEY_LOCAL_MACHINE.
5. Expand Software.
6. Expand STI.
7. Expand HotBackupV14.
8. Select the key that matches the Data ID written down in step c.
Verify that the DataDirectory String has the correct value. If it does not, edit the value to have the correct Client Server Data Directory path. Also verify that your ExeDirectory String has the correct value. These path's both need to be valid from the server's point of view.

CAUTION: Editing the Windows registry is typically not recommended because of potential problems that can occur when not done properly. Tabs3 and PracticeMaster is not responsible for edits made to the registry. Any registry changes should be made by your network administrator or a qualified professional. (Tabs3 Support personnel do not have the necessary training to help you with Windows registry changes.)

WARNING: The following disclaimer is used by Microsoft regarding editing of the registry: "Using Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk."

IMPORTANT: Microsoft recommends making a back up copy of the registry files before editing the registry. Refer to Microsoft documentation for details on how to back up the registry.

Insufficient Rights: Make sure the STI Director Service is logging on with an account that has sufficient rights to the Client Server Data Directory. We have had instances where the Local System Account permissions have been limited, which prevents the STI Director Service from locking the task file.

To view the log on account the STI Director Service is using, use the following steps:

From the Windows Control Panel, select Administrative Tools.
Double-click Services.
Right-click the STI Director Service from the list of services and select Properties.
Select the Log On tab. Here it will indicate what log on account the STI Director Service is using.

Note:

Unable to modify CTSRVR.CFG

This error occurs because the Web installer is unable to modify the new CTSRVR.CFG file. There are several known causes for this error, and the solution varies depending on the cause and whether or not the Windows or Novell CSV version is being used.

Cause: A former Novell CSV user switches to a Windows CSV system, is on the current server, and then attempts to run the Web Update.

Solution: Delete the CTSRVR.NLM file in the program directory and rerun the Web update.

Cause: A Novell CSV user's CTSRVR.CFG file is modified with the result that the local directory line has been deleted or commented out from the CTSRVR.CFG file;
...OR...
A Novell CSV user's CTSRVR.CFG file is missing as a result of the file having been deleted, renamed or moved. This scenario may be followed by an "Error (12) occurred while attempting to open the xxxxxxx file" error message indicating reindexing files is needed.

Solution: Stop the STI Server. Edit the CTSRVR.CFG file with a text editor by adding the local directory line with the correct location. Restart the server. Restart Tabs3; an error 53 may be displayed. Make a temporary backup. Reindex the file listed in the error 53 message (or reindex all files). Restart PracticeMaster; an error 53 may be displayed. Reindex the file listed in the error message (or reindex all files).

Status Log (CTSTATUS.FCS)

While STI Server is operational, status information is appended to CTSTATUS.FCS. This includes information regarding when STI Server was started, whether any errors occurred, and whether STI Server was shut down properly. The CTSTATUS.FCS file is located in the Tabs3/PracticeMaster program directory, and is viewable via a text editor such as Notepad. Viewing the contents of this file can be very helpful in troubleshooting STI Server, especially if any errors are listed.

Problems Starting STI Server

On a Windows server, STI Server may be started manually from a Command Prompt window, from the Services Applet, or via the Desktop Interactive Program (Fig. 2). [Note: STI Server can only be started from a Command Prompt window or from the Services Applet if it has already been installed as a Windows service (i.e., as the STI Server Service).] On a Novell server, STI Server may be started manually using NetWare's LOAD command.

STI Server Service

If the STI Server Service fails to start, it returns a service-specific error. The following is an example of the output from a failed startup when starting the STI Server Service from a Command Prompt window.

	C:\STI> ctntinst -start STI Server Service
	Starting the FairCom Server service...
	STI Server Service start unsuccessful:
	Current State: STOPPED
	Win32 Exit: 1066
	Service Exit: 2
	Checkpoint: 0x0
	WaitHint: 0x0

The service-specific error is displayed as the Service Exit code. The following table provides information regarding service-specific error codes.

Error Code	Cause	Resolution
0	STI Server is already running as a Windows application (i.e., the Desktop Interactive Program).	Shut down the Desktop Interactive Program, and start the service again.
2	The required CTSRVR.CFG file located in the Tabs3/PracticeMaster directory is invalid, usually due to editing it via a word processor instead of a text editor.	Rename the existing CTSRVR.CFG file, and reinstall the STI Server software to create a new CTSRVR.CFG file (see note below).
6	STI Server has not been activated.	Run the FairCom Server Activation Utility to activate STI Server.

Error Code 2 Note: If you purchased STI Server with a connection limit of 256 or more, you will need to modify the new CTSRVR.CFG file to reflect the connection limit.

Desktop Interactive Program

If an error occurs when attempting to start STI Server via the Desktop Interactive Program (i.e., by double-clicking the CTSRVR.EXE file), the following message will be displayed.

The "Server Operation Now Stopped" message is displayed for one of the following reasons.

The STI Server Service is currently running.
The required CTSRVR.CFG file located in the Tabs3/PracticeMaster program directory is invalid, usually due to editing it via a word processor instead of a text editor.

If the STI Server Service is currently running, it must be stopped before attempting to start STI Server via the Desktop Interactive Program. Information on stopping STI Server Service is available in the STI Server manual. (Note: If the STI Server Service is already running, it is not necessary to run the Desktop Interactive Program. STI Server functions the same regardless of whether it is run as a Windows service or as a Windows application.)

If the required CTSRVR.CFG file is invalid, rename it and reinstall the STI Server software to create a new CTSRVR.CFG file. (Note: If you purchased STI Server with a connection limit of 256 or more, you will need to modify the new CTSRVR.CFG file to reflect the connection limit.)

Novell NLM (Network Loadable Module)

On a Novell server, STI Server is run as a NLM (Network Loadable Module). If STI Server is not running, it may have been stopped via NetWare's UNLOAD command; or the LOAD command in the server's AUTOEXEC.NCF file may be incorrect. STI Server may be started manually using NetWare's LOAD command, but you will also want to verify the contents of the AUTOEXEC.NCF file to ensure STI Server is started automatically each time the server is started.

To start STI Server manually
1. From the server, press Ctrl+Esc. A list of programs will be displayed.
2. Select CONSOLE to open a command prompt.
3. Use NetWare's LOAD command to load the CTSRVR.NLM file. For example, if your Tabs3/PracticeMaster software resides in SYS:\STI, you would type the following command:

If the LOAD command in the server's AUTOEXEC.NCF file is incorrect, STI Server will not be started when the server is started. Before modifying the AUTOEXEC.NCF file, first verify that STI Server can be started manually using the above procedure. Once you have confirmed the correct LOAD command to start STI Server manually, edit the same LOAD command in the AUTOEXEC.NCF file. The next time the Novell server is restarted, STI Server will be running.

Technical Information

This section provides information on common situations that occur with STI Server and Tabs3/PracticeMaster CSV software.

Determining Connection Information

Connection information is shown in the Help | About window (Fig. 1) of all Tabs3/PracticeMaster CSV software. The relevant fields in this window include Current Connections, Maximum Connections, and Activation Limit. The Maximum Connections represents the user-configurable number of connections allowed by STI Server. The Activation Limit represents the number of connections you purchased with STI Server (i.e., 8, 16, 32, 64, 128, 256, 512, or 1024). Detailed connection information is available here.

Increasing Your Connection Limit

STI Server is available in levels of 8, 16, 32, 64, 128, 256, 512, or 1024 connections. This connection limit may be increased at any time by contacting our Sales Department at (402) 419-2200. After receiving a new STI Server CD with the higher connection limit, simply follow the procedure listed here to upgrade STI Server to the higher connection limit.

Determining Your Version of STI Server

Before determining what version of STI Server you are using, it is important to note that there are currently only two versions of STI Server available:

Version 8.27.159 is compatible with Version 14.3 Tabs3 and PracticeMaster Client Server Version software dated after 4/10/2008.
Version 8.27.143 is compatible with Version 14.3 Tabs3 and PracticeMaster Client Server Version software dated on or before 4/10/2008.
Version 6.11.36 is compatible with Version 14.1 and earlier Tabs3 and PracticeMaster Client Server Version software.

One method to determine the version of STI Server you are currently using is via the Desktop Interactive Program (i.e., the Windows GUI for STI Server) (Fig. 2). This program can be run by double-clicking the CTSRVR.EXE file in the program directory. (Note: If STI Server is running as a Windows service, it must be stopped in order to use the Desktop Interactive Program.) The version of STI Server will be displayed in the title bar of the Desktop Interactive Program.

Fig. 2, Desktop Interactive Program window

For Windows and Novell servers, the following method can also be used to determine the version of STI Server you are currently using. On Windows servers, this method does not require the STI Server Service to be stopped, and can also be used regardless of how you normally run STI Server (i.e., as a Windows service or using the Desktop Interactive Program).

In the program directory, open the CTSTATUS.FCS file in a text editor such as Notepad.
Locate the line that contains the phrase "Server Is Operational". If this line appears multiple times, the last one listed will be the most current one. [Note: You can use Notepad's Find feature (Ctrl+F) to facilitate this step.]

The version of STI Server will be indicated by a line similar to the following:

- User#  00011  c-tree(R)  v8.27.159  Server Is Operational         -SN 33213321

Moving to a New Server

Detailed instructions for moving STI Server and the Tabs3/PracticeMaster CSV software to a new server are available in KB Article R11227, "Moving CSV Software from One Computer to Another."

Note: Separate versions of STI Server are available for Windows and Novell platforms. If the server's operating system will be changing from Novell to Windows or vice versa, a different version of the STI Server is required. Please contact our Sales Department at (402) 423-1440 to receive a new version of the STI Server software for your server's operating system.

Alternative Names for the STI Server Service

When installing STI Server as a Windows service, we strongly recommend naming it the "STI Server Service" for troubleshooting purposes. For example, installing STI Server as a Windows service can be done using the following command, where "STI Server Service" is the name given to the service:

	ctntinst  -install  STI Server Service

However, it is possible to simply enter ctntinst -install without providing a name, in which case an alternative name is given to the Windows service. The name given varies depending on which version of STI Server was being used at the time it was first installed:

For STI Server Version 8.27.159 and 8.27.143, the alternative name is "ctreeServer".
For STI Server Version 6.11.36, the alternative name is "FairComServer".

If STI Server is installed as a service and you are unable to locate the "STI Server Service," it is possible that it was installed with an alternative name. Additional information on installing STI Server as a Windows service is available in the STI Server manual.

Faircom Activation Utility

The FairCom Server Activation Utility (Fig. 3) is used to activate STI Server once it is installed. STI Server must be activated in order for it to run. This utility is provided with the STI Server software, and the FairCom Server Serial Number and Activation Key required for activation are included with your STI Server purchase.

Fig. 3, FairCom Server Activation Utility window

During the STI Server installation, the FairCom Server Activation Utility is run automatically, prompting you for your FairCom Server Serial Number and Activation Key. (Note: The FairCom Server Serial Number is not the same as your Tabs3/PracticeMaster serial number.) If you choose not to activate STI Server during the installation, or if you need to enter a new FairCom Server Serial Number and Activation Key to upgrade your connection limit, the utility can be run by executing one of the following files:

FCACTVAT.EXE (Windows or Novell Version)

This file is located in the Tabs3/PracticeMaster program directory.

Note: If you are installing STI Server over an existing STI Server installation, you will not be prompted for a FairCom Server Serial Number and Activation Key.

FairCom Serial Number and Activation Key

The FairCom Serial Number and Activation Key are printed on a label included with the STI Server purchase invoice, and on the STI Server CD case. This label will appear similar to the following.

	STI Server - Windows Version
	Serial #:     123456
	Key:          ABCDE.ABCDE.ABCDE-ABCDE.ABCDE.ABCDE
	Connections:  256

Note: The FairCom Server Serial Number is not the same as your Tabs3/PracticeMaster serial number.

References

STI Server Manual - www.Tabs3.com/support/docs.html
KB Article R11181 - CTSRVR.CFG Configuration File
KB Article R11180 - CTSTATUS.FCS Log File
KB Article R11175 - Transaction Processing
KB Article R11193 - HotBackup Overview
KB Article R11199 - Restoring a HotBackup
KB Article R10712 - Client/Server Overview
KB Article R10838 - Moving Tabs3 & PracticeMaster Software from One Computer to Another
Microsoft KB Article 323527 - How to use Windows Task Manager

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-2008 Software Technology, Inc. All rights reserved. Terms of Use
The maker of Tabs3 and PracticeMaster
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