STCONV14.LOG Information

Last reviewed: 02/10/2009
Article ID: R11086

The information in this article applies to:

• All Version 14 Products

SUMMARY

This article contains an explanation for the messages that may be found in the STCONV14.LOG file created during the Version 14 Conversion. Variable text is placed inside brackets (<>).

LOG FILE MESSAGES

"<xxxxxx> has already been converted to Version 14."

Each program that is being converted will show the following message on the opening window of the Conversion program:

<xxxxxx> files will be converted to Version 14.

If a program that you expect to be converted shows the following message on the opening window of the Conversion program instead, contact our Technical Support Department.

<xxxxxx> has already been converted to Version 14.

"<xxxxxx> is not installed."

Any program not purchased by your firm will be dimmed and will show that it is not installed. If you believe you do have data or a software sublicense for a program showing this message, contact our Technical Support Department.

"<xxxxxx> data not found, will not be converted."

This message indicates the conversion program sees Version 14 program files for this program but it does not find Version 12 data to convert. If you expect to be converting data for this program, restore your full backup and run Data File Integrity Checks in all programs. If you still receive this message, contact our Technical Support Department.

"<xxxxxx> will not be converted. Version 14 is not installed."

This message indicates the conversion program has found data for a program, but does not find the corresponding Version 14 program files. Reinstall the software from the Version 14 CD and make sure all systems are installed. If you still receive this message, contact our Technical Support Department.

"<xxxxxx> will not be converted. Other conversions must be done."

This message indicates that the data in the directory is for a version of the software older than Version 12. If you are converting from a version other than 12, follow the instructions you received for your version. If you are converting from Version 12, contact our Technical Support Department.

Note:  If this message is shown for the PracticeMaster software, click here to read additional information regarding this message for PracticeMaster.

Note:  If this message is shown for the System Configuration software, click here to read additional information regarding this message for System Configuration.

"<xxxxxx> data is for a version later than Version 14."
"System Configuration data is for a version other than Version 12 or 14."

When checking for the version of this program's data, the conversion program was unable to read the version ID. If you are converting from Version 12, restore your full backup and run Data File Integrity Checks in all software. If you still receive this message, contact our Technical Support Department.

"<xxxxxx> files will be converted to Version 14."

This is the message that should be shown for every system that you are converting from Version 12 to Version 14.

"System Configuration will not be converted. Other conversions must be done."

The System Configuration user file in the specified data path does not have a Version 12 signature. This would indicate that the user data is a version older than Version 12 or the user file is corrupt.

• If you are converting from a Tabs3 or PracticeMaster version that is earlier than Version 12, you need to follow the conversion instructions provided to you to convert up to Version 12 first.
• If you are converting from Version 12, make sure that you installed the Version 14 programs into the correct directory. If you are not sure which directory is the correct directory, call our Technical Support Department.
• If you are converting from Version 12 and you did not run the Data File Integrity Check program in all the software packages prior to installing the Version 14 software, you need to restore the FULL backup that was made prior to converting, and follow the conversion instructions provided to you.
• If your Version 12 Data File Integrity Check(s) had no errors, and you are sure that the Version 14 programs were installed into the correct directory, perform the following steps.
  1. From a Command prompt, change to your Tabs3 or PracticeMaster program directory.
  2. Type the following command and then press Enter:  REN  STIUSER.DAT  STIUSER.OLD
  3. Type EXIT and press Enter.
  4. Start the Version 14 conversion again. If you are still receiving the message that System Configuration will not be converted, call our Technical Support Department.
  5. After the conversion is completed, start the System Configuration program. From the menu, select File | Open | Users. Verify that your User IDs are present. If your User IDs are present, continue with the conversion instructions. If your User IDs are not present, contact our Technical Support Department.
     
     

Note:  The user data files were renamed in Version 10 (i.e., from STIUSER.DAT to STUSER.DAT and STUSER.IDX), so it is possible for Version 11 (or later) and Version 9 user data files to be present at the same time in the same directory. This situation has been reported in instances where a firm performed their Version 9 to Version 10 conversion in a different directory and then copied the files from the converted directory back to the original directory. If Version 9 had been converted to Version 10 in the original directory, the old Version 9 user data files would have been deleted after they were converted.

"No GLS data exists for GLS client <###>."

The conversion program couldn't find the G5LOG.DAT file in the GLS client's data path.  If this client should have been converted to Version 14, you will need to call our Technical Support Department. If this GLS client is an old client for which you no longer need to access the information, you can ignore this message.

"Could not find G5CONFIG.DAT. Conversion will proceed."

The conversion program found that the program(s) being converted were set to integrate with the Tabs3 General Ledger Software, but the configuration file for GLS was not present. If you are no longer integrating the software with GLS, you can ignore this message. If you are integrating with GLS, this indicates that GLS is not going to be converted and that the GLS accounts specified on the integration screens of the other software may not be converted correctly. If this is the case, you should restore your full backup and run Data File Integrity Checks in all software, including GLS. If you still receive the message, call our Technical Support Department.

"GLS Log file for Client # in path: <path> has a signature of: <xxxxxx> instead of GLDATA12. Conversion will proceed."

The G5LOG.DAT file in the specified data path has something other than a GLDATA12 signature.  This indicates that the GLS data is a version older than Version 12 or the G5LOG.DAT file is corrupt.  If you are converting from a GLS Version that is earlier than Version 12, you need to follow the conversion instructions provided to you to convert up to Version 12 first.  If you are converting from Version 12, you need to restore the FULL backup that was made before installing Version 14 and follow the conversion instructions provided to you, including running a Data File Integrity Check in GLS for ALL GLS clients.

Note:  Even if there are GLS Clients that you no longer use, they must be configured with a valid data path or deleted; otherwise, the conversion program will abort due to the invalid path.

"GLS data for GLS client <###> has already been converted."

This message may appear during the conversion. The GLS data for this client number has already been converted to a Version 14 format. If more than one client is pointing to the same data path, or you have already converted some GLS clients' data, this message is to be expected. If you are expecting all GLS clients to be converted, you should restore your full backup and verify that the paths of all GLS Clients are valid by printing a GLS Client List (from the GLS menu, select Reports | GLS Client List).

"GLS data for GLS client <###> is not version 12 data. Version ID <xxxxx> - Conversion will not start."

The G5LOG.DAT file in the specified data path has something other than a GLDATA12 signature.  This indicates that the GLS data is a version older than Version 12 or the G5LOG.DAT file is corrupt.  If you are converting from a GLS Version that is earlier than Version 12, you need to follow the conversion instructions provided to you to convert up to Version 12 first.  If you are converting from Version 12, you need to restore the FULL backup that was made before installing Version 14 and follow the conversion instructions provided to you, including running a Data File Integrity Check in GLS for ALL GLS clients.

Note:  Even if there are GLS Clients that you no longer use, they must be configured with a valid data path or deleted; otherwise, the conversion program will abort due to the invalid path.

"PracticeMaster will not be converted. Other conversions must be done."

The PracticeMaster configuration file in the specified data path does not have a Version 12 signature.  This would indicate that the PM data is a version older than Version 12 or the configuration file is corrupted.

• If you are converting from a PracticeMaster or Case Master version that is earlier than Version 12, you need to follow the conversion instructions provided to you to convert up to Version 12 first.
• If you are converting from Version 12, make sure that you installed the Version 14 programs into the correct directory. If you are not sure which directory is the correct directory, call our Technical Support Department.
• If you are converting from Version 12 and you did not run the Data File Integrity Check program in PracticeMaster prior to installing the Version 14 software, you need to restore the FULL backup that was made prior to converting, and follow the conversion instructions provided to you.

Note:  When converting from Case Master Version 2.x to Version 10, several files were renamed. Therefore, it is possible for PracticeMaster Version 14 and Case Master Version 2.x data files to be present at the same time in the same directory, since the names are not the same. This situation has been reported in instances where a firm performed their Version 2.x to Version 10 conversion in a different directory and then copied the files from the converted directory back to the original directory. If Version 2.x had been converted to Version 10 in the original directory, the old Version 2.x data files would have been deleted after they were converted.

"See PMConv14.log for detailed information on the PracticeMaster Conversion."

All information regarding the conversion of PracticeMaster data files is written to the PMCONV14.LOG instead of the STCONV14.LOG file. Most messages are routine in this file and can usually be ignored. However, this file should be reviewed for any issues.

"STCONV14 Reindex Files log begin..."

The conversion program writes this message to the log file when the reindex of Version 14 files is started. The next line in the log file should be "STCONV14 Reindex Files log end". If there are additional messages between the begin and end messages, contact our Technical Support Department.

"Negative Payments Deleted"

Tabs3 Version 14 does not allow negative payments due to changes in how payment allocation is handled. Any negative payment from a prior version will be deleted and a list of any deleted transactions will be generated.

"Payment Status Changed"

Tabs3 Version 14 does not allow a payment to be saved with a status of "Save".  Any payment with a status of "Save" will be changed to "Print" and a list of any changed payment transactions will be generated.

Tabs3 Allocated WIP Payments

Any work-in-process (WIP) payments that are allocated during the conversion process will be listed in the STCONV14.LOG file under the Tabs3 Conversion section. Each payment will be listed indivdually and will include the following information: Client ID, Allocation Date, Allocation Amount (plus allocation breakdown), Payment Date, Payment Amount, and Reference Number. An example is shown below:

Tabs3 Conversion
-------------------
   Client ID  Allocation Date  Allocation Amount  Payment Date  Payment Amount   Ref #
   ---------  ---------------  -----------------  ------------  --------------  ------
      100.01       04/25/2008              30.00    04/25/2008           30.00       1
                               Fees:       30.00

   Client ID  Allocation Date  Allocation Amount  Payment Date  Payment Amount   Ref #
   ---------  ---------------  -----------------  ------------  --------------  ------
      220.00       06/18/2008             233.19    06/18/2008          233.19       6
                               Fees:      210.00
                           Expenses:       23.19

   Client ID  Allocation Date  Allocation Amount  Payment Date  Payment Amount   Ref #
   ---------  ---------------  -----------------  ------------  --------------  ------
      825.78       09/16/2008              78.80    09/16/2008           78.80       5
                               Expenses:   40.00
                               Advances:   25.00
                               Fin Chg:     9.25
                               Exp Tax:     2.80
                               Adv Tax:     1.75

      825.78       10/15/2008              50.00    10/15/2008           50.00       6
                               Fees:       50.00

      825.78       11/16/2008              75.00    11/16/2008           75.00       7
                               Fees:       75.00
Complete
  

Note: The allocation date for WIP payments allocated during the conversion is always the payment date.

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-2010 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