STCONV15.LOG Information

Last reviewed: 06/21/2011
Article ID: R11235

The information in this article applies to:

All Version 15 Products

SUMMARY

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

LOG FILE MESSAGES

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

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 15.

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 15.

"<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 15 program files for this program but it does not find Version 14 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 15 is not installed."

This message indicates the conversion program has found data for a program, but does not find the corresponding Version 15 program files. Reinstall the software from the Version 15 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 14. If you are converting from a version other than 14, follow the instructions you received for your version. If you are converting from Version 14, 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 15."
"System Configuration data is for a version other than Version 14 or 15."

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 14, 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 15."

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

"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 14 signature. This would indicate that the user data is a version older than Version 14 or the user file is corrupt.

If you are converting from a Tabs3 or PracticeMaster version that is earlier than Version 14, you need to follow the conversion instructions provided to you to convert up to Version 14 first.
If you are converting from Version 14, make sure that you installed the Version 15 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 14 and you did not run the Data File Integrity Check program in all the software packages prior to installing the Version 15 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 14 Data File Integrity Check(s) had no errors, and you are sure that the Version 15 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 15 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.

"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 15, 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 GLDATA14. Conversion will proceed.": The G5LOG.DAT file in the specified data path has something other than a GLDATA14 signature. This indicates that the GLS data is a version older than Version 14 or the G5LOG.DAT file is corrupt. If you are converting from a GLS Version that is earlier than Version 14, you need to follow the conversion instructions provided to you to convert up to Version 14 first. If you are converting from Version 14, you need to restore the FULL backup that was made before installing Version 15 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 because of 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 15 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 14 data. Version ID <xxxxx> - Conversion will not start.": The G5LOG.DAT file in the specified data path has something other than a GLDATA14 signature. This indicates that the GLS data is a version older than Version 14 or the G5LOG.DAT file is corrupt. If you are converting from a GLS Version that is earlier than Version 14, you need to follow the conversion instructions provided to you to convert up to Version 14 first. If you are converting from Version 14, you need to restore the FULL backup that was made before installing Version 15 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.

The Conversion program has encountered an invalid GLS Data Path for one or more GLS Clients. Please review the STCONV15.LOG file located in the program directory to determine which GLS Client(s) have an invalid GLS Data Path. Once you have fixed the invalid Path(s), you will need to run STCONV15.EXE again to convert your data. Detailed information regarding how to resolve the invalid GLS Data Paths can be found in Knowledge Base Article R11234 at www.support.Tabs3.com.

Click OK to clear the message. The STCONV15.EXE program will close without the conversion having been run. You will need to rerun STCONV15.EXE after fixing the invalid GLS Data Paths.

GLS Version 15 software requires the GLS Data Path for all defined GLS clients to be relative paths AND located in a folder under the current working directory. The path must also include a trailing backslash character. Previous versions of GLS did not have this requirement, excluding Version 14.3 CSV.

The conversion program detected that one or more of your GLS clients does not meet this criteria. The STCONV15.LOG file will indicate which GLS client(s) have an invalid GLS Data Path using the following format:

	Path Is Not Relative for GLS Client <X>
		Path=<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 Path(s) must be addressed before you will be able to use Version 15 of the software. Once you have addressed the invalid path(s), rerun STCONV15.EXE from the server (located in the Tabs3 program directory).

Note: Whenever possible, the STCONV15.EXE program will change the GLS Data Path to a relative path that matches the current working directory. If this change is made, it is done so silently and is noted in the STCONV15.LOG file. If it is not possible for STCONV15.EXE to resolve the discrepancy (e.g., the GLS Data Path is located on another drive), this message will be displayed.

Trailing backslash character is missing: If the STCONV15.LOG file states "GLS data not found for GLS client XXX in path: GLSdatapath" (where 'XXX' represents the GLS Client number and GLSdatapath is the directory that the GLS client's data is stored in), then the cause of the problem may be that the trailing backslash character is missing from the GLS client's data path. If this is the issue, there are some additional steps that need to be taken to ensure that the GLS Client's data gets converted. Please contact Technical Support if this issue is reported in the STCONV15.LOG file.

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

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

If you are converting from a PracticeMaster or Case Master version that is earlier than Version 14, you need to follow the conversion instructions provided to you for converting to Version 14 first.
If you are converting from Version 14, make sure that you installed the Version 15 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 14 and you did not run the Data File Integrity Check program in PracticeMaster prior to installing the Version 15 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 14 PracticeMaster Data File Integrity Check had no errors, and you are sure that the Version 15 programs were installed into the correct directory, perform the following steps.

From a Command prompt, change to your PracticeMaster program directory.
Type the following command and press Enter: REN CM3LST.DAT CM3LST.OLD
Type the following command and press Enter: REN CMCONFIG.DAT CMCONFIG.OLD
Type EXIT and then press Enter.
Start the Version 15 conversion again. If you are still receiving the message that PracticeMaster will not be converted, call our Technical Support Department.
After the conversion is completed, start the PracticeMaster program. Verify that your data is present. If your data is present, continue with the conversion instructions. If your data is not present, contact our Technical Support Department.

"See PMCONV15.LOG for detailed information on the PracticeMaster Conversion.": All information regarding the conversion of PracticeMaster data files is written to the PMCONV15.LOG instead of the STCONV15.LOG file. Most messages are routine in this file and can usually be ignored. However, this file should be reviewed for any issues.
"*** TP changed ***": This indicates that the file was changed to work with Transaction Processing. Additional information about Transaction Processing can be found in KB Article R11175, "Transaction Processing and Auto-Recovery".
"STCONV15 Reindex Files log begin...": The conversion program writes this message to the log file when the reindex of Version 15 files is started. The next line in the log file should be "STCONV15 Reindex Files log end". If there are additional messages between the beginning and ending messages, contact our Technical Support Department.

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

STCONV15.LOG Information

Last reviewed: 06/21/2011 Article ID: R11235

SUMMARY

LOG FILE MESSAGES

Last reviewed: 06/21/2011
Article ID: R11235