STCONV11.LOG Information

Last reviewed: 03/26/2004
Article ID: R10921

The information in this article applies to:

SUMMARY

This article contains an explanation for the messages that may be found in the STCONV11.LOG file. These messages are classified as warnings. Warnings are for informational purposes and will not cause the conversion program to abort. Variable text is placed inside brackets (<>).

LOG FILE MESSAGES

"<xxxxxx> will be converted to Version 11."
This message will be shown in the log file for every program that is converted. Each program will be listed in a separate section with the status of "Complete" shown under the section heading.


"<xxxxxx> has already been converted to Version 11."
Each program that is being converted will show the following message on the opening window of the Conversion program: 
<xxxxxx> will be converted to Version 11
If a program that you expect to be converted shows the following message on the opening window of the Conversion program instead, contact the Technical Support Department. 
<xxxxxx> has already been converted to Version 11.
Note: If you are receiving this message for the GLS Program, click here to read this topic in the GLS section of the article.


"<xxxxxx> is not installed."
Any program not purchased by your firm should be dimmed and should show that it is not installed. If you believe you do have data for a program showing this message, contact the Technical Support Department.


"<xxxxxx> data not found, will not be converted."
This message indicates the conversion program sees version 11 program files for this program but it does not find Version 10 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 the Technical Support Department.


"<xxxxxx> will not be converted. Version 11 is not installed."
This message indicates the conversion program has found data for a program, but does not find Version 11 program files for this same program. Reinstall the Version 11 CD and make sure all systems are installed. If you still receive this message, contact the 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 10. If you are converting from a Version other than 10, follow the instructions you received for your version. If you are converting from Version 10, contact the Technical Support Department.


Note: If this message is shown for the PracticeMaster software, click here to read this topic in the PracticeMaster section of the article.


Note: If this message is shown for the System Configuration software, click here to read this topic in the System Configuration section of the article.


"<xxxxxx> data is for a version later than Version 11."
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 10, restore your full backup and run Data File Integrity Checks in all software. If you still receive this message, contact the Technical Support Department.


"<xxxxxx> files will be converted to Version 11."
This is the message that should be shown for every system that you are converting from Version 10 to Version 11.


"System Configuration will not be converted. Other conversion must be done."
The System Configuration user file in the specified data path does not have a Version 10 signature.  This would indicate that the User data is a version older than Version 10 or the user file is corrupted. 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 10 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 was converted to Version 10 in the original directory, the old Version 9 user data files would have been deleted after they were converted.


"The Archive Path specified in Tabs3 Customization is invalid: <path> - Conversion will not start."
Tabs3 Version 10 allows you to specify a path to store your archive data in. Tabs3 Version 11 no longer uses a path, the archive files are always stored in the program directory. In order to convert the data correctly, the Tabs3 Version 10 archive path must be valid. The conversion checks for a valid path prior to starting the conversion. If you receive this message, restore your full backup of program and data files, fix the archive path and run an Archive File Integrity Check before starting the process again. Call Technical Support to resolve any Archive File Integrity Check errors.


"GLS has already been converted to Version 11."
The GLS data has already been converted to a Version 11 format. If GLS has already been successfully converted, you can ignore this message. If you are receiving this message after restoring from the backup file created by the Conversion program, contact the Technical Support Department.
"No GLS data exists for GLS client <###>."
The conversion program couldn't find the G5LOG.DTA file in the client's data path.  If this client should have been converted to Version 11, you will need to call the Technical Support Department.  If this GLS client is an old client that you do not need to access information for, you can ignore this message.


"Could not find G5CONFIG.DTA. 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 present in 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 GLDATA10. Conversion will proceed."
The G5LOG.DTA file in the specified data path has something other than a GLDATA10 signature.  This would indicate that the GLS data is a version older than Version 10 or the G5LOG.DTA file is corrupted.  If you are converting from a GLS Version that is earlier than Version 10, you need to follow the conversion instructions provided to you to convert up to Version 10 first.  If you are converting from Version 10, you need to restore the FULL backup that was made before installing Version 10 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 11 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.


"GLS data for GLS client <###> is not version 10 data. Version ID <xxxxx> - Conversion will not start."
The G5LOG.DTA file in the specified data path has something other than a GLDATA10 signature.  This would indicate that the GLS data is a version older than Version 10 or the G5LOG.DTA file is corrupted.  If you are converting from a GLS Version that is earlier than Version 10, you need to follow the conversion instructions provided to you to convert up to Version 10 first.  If you are converting from Version 10, you need to restore the FULL backup that was made before installing Version 10 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 10 signature.  This would indicate that the PM data is a version older than Version 10 or the configuration file is corrupted.
Note: When converting from Case Master Version 2.x to Version 10, several files were renamed. So it is possible for PracticeMaster Version 10 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 was converted to Version 10 in the original directory, the old Version 2.x data files would have been deleted after they were converted.


"See PMConv11.log for detailed information on the PracticeMaster Conversion."
All information regarding the conversion of PracticeMaster data files is written to the PMCONV11.log instead of the STCONV11.LOG file. Most messages are routine in this file and can usually be ignored. However, this file should be reviewed for any issues.


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

REFERENCES

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 (The "Pinwheel" symbol is a Registered Trademark of Software Technology, Inc.) 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