Messages During the Version 12 to Version 14 Conversion
Last reviewed: 02/04/2007
Article ID: R11085
The information in this article applies to:
SUMMARY
This article includes a list of all of the possible messages that may occur when running the STCONV14.EXE conversion program.
The STCONV14.EXE program is used to convert Version 12 systems (Tabs3, PracticeMaster, GLS, APS, TAS, and System Configuration)
to Version 14 systems.
These messages may appear during the conversion process. Some of the messages will cause the conversion process to abort and
must be resolved before you can successfully run the conversion program. Following each message is an explanation of the message
and information regarding how to resolve it. Information placed inside the following characters "<" and ">"
represents text that will vary. Call our Technical Support Department at (402) 419-2210 if additional assistance is needed.
MESSAGES
- "A backup of data to be converted has been found. Do you want to restore it?"
- When the Version 14 conversion is run, a backup of the Version 12 data must be created if one does not already exist.
This backup is named STCONV14.ARQ and is created in a subdirectory named BACKUP under the directory where your Version 14
program files were installed. If the conversion is run a subsequent time and the STCONV14.ARQ file is present, this
message appears. If you choose to restore this backup, all converted data will be overwritten with the data that is in
the backup.
- "Backup NOT successful. <filename> did not get backed
up."
- The Version 14 conversion program automatically makes a backup of all data
files for all systems. In the event the backup cannot be completed because the
data set exceeds the 2GB file size limitation, this message will be displayed.
KB Article R11134, Large File Size Limitations in Tabs3 & PracticeMaster Software,
contains additional information regarding file size limitations and conversion
program behavior when the files size limitation is reached.
- Note: It is absolutely critical that you have a full backup of
your program and data files made using another method. We recommend copying
the folder to another location on the hard drive. Do NOT proceed with the
following work-around if you do not have a backup.
The following work-around can be used to proceed with the conversion if the
back up cannot be completed due to the file size limitation. You must create a
file named STCONV14.ARQ in the BACKUP subdirectory. An easy way to do this is
to use Windows Explorer to copy any file (smaller is better) from anywhere on
your computer to the BACKUP folder and then rename it to STCONV14.ARQ. Restart
the conversion. The following message will be displayed: "A backup of data to
be converted has been found. Do you want to restore it?". Click No. The
conversion program will then continue.
It is possible that this error message may be displayed for
other reasons than the file size limitation. Complete troubleshooting
Information regarding this message can be found in R10278,
Troubleshooting the Built-In Back Up Data Files Program.
- "<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
- Note: If you are receiving this message for the GLS Program, click
here
to read the information in the GLS section of this article.
-
- "<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> 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 this topic in the PracticeMaster section of the article.
-
- "<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.
-
- "<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.
-
- "All other users must exit before this task can be run."
- There are users currently logged into the Version 12 software. Have these users exit the software. If no users are
currently logged into the software, reset their User ID(s). (Note: Do not
reset users if they are logged
into the software.)
If these users were accessing the software when the backup was made, the backup may be invalid and should be redone.
-
- "There is no data that requires conversion."
- No Version 12 program is available for conversion. If you go back to the first screen of the conversion program,
you will note that all systems will say, "<.....> will not be converted" or "<.....> has already
been converted". Access all Version 12 systems to verify the location of the programs and data. Make sure that you
installed the Version 14 software to the correct program directory. If this message continues to appear, contact our
Technical Support Department.
- "Would you like to back up your data before converting?"
- When the Version 14 conversion is run, a backup of the Version 12 data must be created if one does not already exist.
If no backup is found, the program will create a backup file named STCONV14.ARQ in a subdirectory named BACKUP under the
directory where your Version 14 program files were installed. If one is found, this message is displayed. If you answer
"Yes", the existing backup will be overwritten with the current data. This backup will contain a backup of your
current Version 12 data. If you answer "No", this file will not be created. If you select "Cancel",
the Version 14 conversion will be cancelled. This backup should not be your ONLY backup. Do not proceed further if you do not
have a backup of your data and program files for your Version 12 programs.
- "This backup file MUST be created before you can proceed with the conversion."
- When converting to Version 14, the conversion program requires that you answer Yes to the Backup prompt before converting.
Although we only check for the internal conversion backup, we strongly recommend that a full backup of the entire directory
also be made before continuing. This message indicates that the backup was cancelled. Once the backup is completed successfully,
the conversion will allow you to continue.
- "A backup must be created before converting. Conversion Aborted!."
- When converting to Version 14, the conversion program requires that you answer Yes to the Backup prompt before converting.
Although we only check for the internal conversion backup, we strongly recommend that a full backup of the entire directory
also be made before continuing.
- "Failed to open CVREORG.LOG <###>"
- The conversion program cannot open or create the CVREORG.LOG file needed. Make sure the user
running the conversion has full network access rights to the directory. Please contact our Technical
Support Department for information on the error number listed in the message.
-
- "Data conversion completed with <###> message(s)."
- The Version 14 data conversion completed with at least one message written to the STCONV14.LOG file.
Open the STCONV14.LOG file with a text editor to read the messages.
-
- There is also a PMCONV14.LOG file created during the conversion of PracticeMaster. The STCONV14.LOG file will
alert you if reviewing this file is necessary. If errors occurred during the conversion, the PMCONV14.LOG file will
contain the error messages. Otherwise, the PMCONV14.LOG file simply contains detailed information on what was converted
in the PracticeMaster file system and is not necessary to review.
Note: For more information regarding messages in the STCONV14.LOG file, refer to KB Article
R11086, "STCONV14.LOG Information".
- "A common file <filename> necessary for all Tabs3 and PracticeMaster programs is in use. To complete the
conversion, close all Tabs3 and PracticeMaster programs on all workstations."
- The Conversion program is attempting to convert the Version 12 DROPBOX.EXE or STUINFO.DLL files to the Version 14 files.
It cannot do this if any user is using any Tabs3 or PracticeMaster program. There have been several checks prior to this point
to make sure the programs are closed, so if this message is received, it is likely that a user has gone BACK into the program
after being out of it. Do not abort the conversion at this point. The file shown is in use at this point, and must not be in use
for the conversion to successfully continue. You will have to restore a full backup if you abort the conversion now.
- "Path: <path> does not exist or you have insufficient permissions."
- This is referring to a path for a General Ledger client that is defined in General Ledger but cannot be accessed by
the workstation or server where the conversion is being run. The conversion will not continue until this situation is
resolved. Start General Ledger and print a Client List (Reports | GLS Client List). Correct any paths, including the
one referenced in the error you received, so that all paths are available from this computer. Please contact our
Technical Support Department if you are not sure how to do this. Once the paths are corrected, run a Data File
Integrity Check in General Ledger (Utilities | Data File Integrity Check). If there are no errors, try the
conversion again.
-
- Note: 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. Therefore, if you are
in the process of converting to Version 15, refer to KB Article
R11191, "How to Move GLS Clients," to make sure the
GLS Data Path is valid for the Version 14 and Version 15 conversions.
- "Error opening stuser12.dat. The conversion can't proceed."
- The user file was renamed to stuser12.dat in order to convert it to a valid Version 14 file. During this process, something
has changed on the network to make it not possible for the conversion program to load this file to convert it. The conversion
will abort. A full backup will need to be restored and the stuser12.dat and idx files should be deleted from the directory after
the data is restored. Then run a Data File Integrity Check in all Tabs3 and PracticeMaster programs that you are converting,
resolve any errors and try the conversion again.
- "Failed to write the task record. Access Denied."
- The Conversion program is trying to write to the STTASK.DAT file to indicate that it is performing a "Super-Exclusive"
task and is unable to do so. It is recommended at this point that you restore a full backup and run Data File Integrity Checks
in all Tabs3 and PracticeMaster programs. If everything is successful, take precautions to make sure no one goes into the
program and try the conversion again.
- "The program file System Configuration is in use. To complete the conversion, close System Configuration on all
workstations."
- The Conversion program is trying to convert the STICONFG.EXE and SCMAIN.EXE files from Version 12 to Version 14, but one or
both of the files are in use on a workstation. Make sure that every user has closed out of System Configuration. There have been
several checks prior to this point to make sure the programs are closed, so if this message is received, it is likely that a user
has gone BACK into the program after being out of it. Do not abort the conversion at this point. The file shown is in use at
this point, and must not be in use for the conversion to successfully continue. You will have to restore a full backup if you
abort the conversion now.
- "Data conversion completed."
- This message is received if the conversion completed without any messages being written to STCONV14.LOG. This file may
still need to be reviewed for WIP Payment allocation information.
- "The information on the Receipt Allocation Report in Version 14 will be tracked differently than in prior
versions.
If the Receipt Allocation Report is used for business decisions in your firm, it is strongly recommended that a Transition
Date be established prior to converting to Version 14.
Step-by-step procedures for establishing a Transition Date along with additional guidelines that should be considered before
actually converting to Version 14 can be found in Knowledge Base Article R11125,
"Preparing for and Using Date-Based Receipt Allocation Reporting."
Would you like to view this article on the Internet now?"
- This message will always come up before the Pre-Conversion Analysis window is loaded. This is an informational message
to alert you that the Version 14 Receipt Allocation Report will be different and there are issues that must be considered.
We strongly recommend that KB Article R11125 be reviewed by your firm before converting to Version
14.
- "The Version 14 Pre-Conversion Analysis requires Tabs3 data to be Version 10 or later."
- The Pre-Conversion Analysis must be run before converting to Version 14. Normally, when converting to Version 14, your
data will be in Version 12 format. But we have allowed the Pre-Conversion Analysis to be run on Versions 11 and 10 data also,
in order to allow some firms to get a "head start" on the conversion process. This message indicates that the
data in the directory is either corrupted, or is a version that is prior to Version 10.
- "Tabs3 data has already been converted to Version 14."
- The Pre-Conversion Analysis must be run before converting to Version 14. Normally, when converting to Version 14, your
data will be in Version 12 format. But we have allowed the Pre-Conversion Analysis to be run on Versions 11 and 10 data also,
in order to allow some firms to get a "head start" on the conversion process. This message indicates that the
data in the directory has already been converted to Version 14. If this is not true, you will need to restore a full backup
and run a Data File Integrity Check.
- "You must run the Pre-Conversion Analysis before you can proceed."
- The Pre-Conversion Analysis must be run before converting to Version 14. This message indicates that the files that the
Pre-Conversion Analysis creates are not present in the directory. Once the Pre-Conversion Analysis has been run, the
conversion program will allow you to continue.
- "Unable to determine the status of the last Pre-Conversion."
- The Pre-Conversion Analysis must be run before converting to Version 14. This message indicates that the files that the
Pre-Conversion Analysis creates cannot be read by the conversion program. Once the Pre-Conversion Analysis has been run
again, the conversion program will allow you to continue.
- "The Pre-Conversion Analysis was last run on <Date>. The Pre-Conversion utility must be run again
before you can continue with the conversion."
- The Pre-Conversion Analysis must be run before converting to Version 14. This message indicates that the files that the
Pre-Conversion Analysis creates were created on a day other than the day you are trying to convert. The files must be
created on the same day. Once the Pre-Conversion Analysis has been run again, the conversion program will allow you to
continue.
- "Are you sure you want to cancel the Pre-Conversion Analysis?"
- The Pre-Conversion Analysis must be run before converting to Version 14. This message indicates that you have
attempted to cancel the Pre-Conversion Analysis. Unless this is the intended course of action, select No to this
message because the Pre-Conversion Analysis will have to be run again if you cancel it. Once the Pre-Conversion Analysis
completes, the conversion program will allow you to continue.
- "Tabs3 could not be run."
- When the Pre-Conversion Analysis is run, if warnings are found that could be corrected by the Rebuild Client Ledger
Detail Program in Tabs3, you will be prompted to start Tabs3 and run the Rebuild Client Ledger Detail. If you select Yes,
the conversion program will exit and try to start Tabs3. If Tabs3 cannot start, this is the message that will be displayed.
Restore a full backup and run the Data File Integrity Check in Tabs3 and try the Pre-Conversion Analysis again.
- "Warnings were encountered that the Rebuild Client Ledger Detail program in Tabs3 may be able to correct.
Run the Rebuild Client Ledger Detail program (Utilities | Rebuild Client Ledger Detail) prior to converting to Version 14.
Would you like to launch Tabs3 now?"
- When the Pre-Conversion Analysis is run, if warnings are found that could be corrected by the Rebuild Client Ledger
Detail Program in Tabs3, you will be prompted to start Tabs3 and run the Rebuild Client Ledger Detail. If you select Yes,
the conversion program will exit and try to start Tabs3. This message indicates that the version of Tabs3 installed is
a version that is current enough to attempt to correct the warnings you have received. You should select Yes and run the
Rebuild Client Ledger Detail program now.
- "Warnings were encountered that the Rebuild Client Ledger Detail program in Tabs3 may be able to correct.
However, your Version 12 Tabs3 program needs to be updated to the most current release. Prior to converting to Version
14, you will need to:
1. Download the most current version of Tabs3.
2. Run the Rebuild Client Ledger Detail program (Utilities | Rebuild Client Ledger
Detail).
Would you like to download the most current version of Tabs3 now?"
- When the Pre-Conversion Analysis is run, if warnings are found that could be corrected by the Rebuild Client Ledger
Detail Program in Tabs3, you will be prompted to start Tabs3 and run the Rebuild Client Ledger Detail. If you select Yes
to this message, the conversion program will exit and access the Version 12.2 Update Site on the Internet so you can install
the latest build of the Tabs3 and PracticeMaster software you currently have installed. This must be done before running the
Rebuild Client Ledger Detail program in Tabs3. You should download and install the updates for all products you have installed.
Everyone must be out of the software to install the updates. Once you have installed the newest Tabs3 program, you should run
the Rebuild Client Ledger Detail program.
- "Warnings were encountered that the Rebuild Client Ledger Detail program in Tabs3 may be able to correct.
However, you are using a version of Tabs3 prior to Version 12. In order to convert to Version 14, you will need to call
Tabs3 Technical Support at 402-423-1440."
- When the Pre-Conversion Analysis is run, if warnings are found that could be corrected by the Rebuild Client Ledger
Detail Program in Tabs3, then the conversion will check to make sure that your Tabs3 program that you have installed is
Version 12. The most current Version 12 program is required in order to successfully rebuild the ledger detail to correct
the greatest number of warnings possible. This message means Version 12 Tabs3 is not installed in this directory. If you
are converting from a Version prior to Version 12, then you will need to convert up to Version 12, following the instructions
you received. Once your data is converted to Version 12, run the Rebuild Client Ledger Detail program in Tabs3 Version 12.
If you do not have a Version 12 CD, call Tabs3 Technical Support for assistance. The conversion will exit if this message is
received.
- "Pre-Conversion Analysis complete. Would you like to view the Pre-Conversion Report before proceeding?"
- This message indicates that there are warnings received in the Pre-Conversion Report. These warnings should be reviewed
before continuing the conversion to Version 14. Please refer to KB Article R11093 for information
on the warnings that are shown on the report.
- "Warning: The Pre-Conversion Analysis encountered warnings for one or more clients. Are you sure you want
to continue with the conversion?"
- This message indicates that there are warnings received in the Pre-Conversion Report. These warnings should be reviewed
before continuing the conversion to Version 14. Please refer to KB Article R11093 for information
on the warnings that are shown on the report. If you have already reviewed the warnings and are planning to convert without
addressing them, then Select Yes to this message.
- "<###> Tabs3 client(s) have final statements that need to be updated or unbilled before the conversion
can be run."
- The conversion to Version 14 requires that no clients have final statements that have not been updated during the
conversion. Any statements that have been final billed before converting must either be updated or unbilled. This message
will abort the conversion. Start Tabs3 Version 12 and update or unbill all your final statements. Then start the conversion
again. You do not need to restore if you receive this message.
- "Tabs3 files were found in the folder, however, Tabs3 is not installed.
Please call Technical Support for assistance at (402) 423-1440.
Conversion aborted."
- There are Tabs3 data files in the directory that the conversion is being run from, but Tabs3 programs are not installed.
If you are no longer using Tabs3, you can use KB Article R11082 to remove the Tabs3 data. If you
are using Tabs3, it must be converted at the same time as the other programs. Install your Version 14 CD again and make sure
to select to install Tabs3. If you cannot resolve this message, please contact our Technical Support Department.
- "Adjustments were made during the conversion. Would you like to review the Post-Conversion Report at this
time?"
- The conversion made adjustments to the Tabs3 Receipt Allocation figures during the conversion. This Post-Conversion Report
should be reviewed if you rely on the numbers on the Receipt Allocation Report to make decisions in your firm.
- "The Post-Conversion Report viewer (stcnvrpt14.exe) could not be run."
- When trying to start the Report Viewer to view the Conversion Report, the stcnvrpt14.exe file was either not found or
could not be started. Check to be sure this file exists. If it does not exist, reinstall the Pre-Conversion Analysis
program on the Version 14 CD. If the file does exist, contact our Technical Support Department.
- "The program file Tabs3 is in use. To complete the conversion, close Tabs3 on all workstations ."
- The Conversion program is trying to convert the TABS.EXE and TBMAIN.EXE files from Version 12 to Version 14, but one or
both of the files are in use on a workstation. Make sure that every user has closed out of Tabs3. There have been several
checks prior to this point to make sure the programs are closed, so if this message is received, it is likely that a user has
gone BACK into the program after being out of it. Do not abort the conversion at this point. The file shown is in use at this
point, and must not be in use for the conversion to successfully continue. You will have to restore a full backup if you abort
the conversion now.
- "A Super-Exclusive task is active. Access Denied."
- This message may be received when trying to start Tabs3. This may
indicate that the conversion program did not complete. Check STCONV14.LOG
to verify that the conversion completed for each program. If any program
did not complete, it will be necessary to restore from a backup made prior
to the conversion being run and perform the conversion again.
- "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 a 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.
- "The PracticeMaster Outlook PM Link file (PMLINKOL.DLL) is in use. To complete the conversion, close Outlook on all
workstations that have PM Link installed."
- The Conversion program is attempting to convert the Version 12 PMLINKOL.DLL file to the Version 14 file. It cannot do this
if any user that has PM Link installed is running Outlook on their workstation. Make sure every user has shut down Outlook and
that Outlook.exe has successfully cleared from each workstation's Windows Task Manager. Do not abort the conversion at this
point. The PMLINKOL.DLL file is in use at this point, and must not be in use for the conversion to successfully continue.
You will have to restore a full backup if you abort the conversion now.
- "The PracticeMaster HotDocs Plug-In file (PMLINKHD.DLL) is in use. To complete the conversion, close PracticeMaster
on all workstations."
- The Conversion program is attempting to convert the Version 12 PMLINKHD.DLL file to the Version 14 file. It cannot do this
if any user that has the PM HotDocs Plus-In installed is running PracticeMaster on their workstation. There have been several
checks prior to this point to make sure PracticeMaster is closed, so if this message is received, it is likely that a user has
gone BACK into the program after being out of it. Do not abort the conversion at this point. The PMLINKHD.DLL file is in use
at this point, and must not be in use for the conversion to successfully continue. You will have to restore a full backup if
you abort the conversion now.
- "The PracticeMaster e-mail program (STMAPI.EXE) is in use. To complete the conversion, close PracticeMaster on all
workstations."
- The Conversion program is attempting to convert the Version 12 STMAPI.EXE file to the Version 14 file. It cannot do this
if any user with e-mail integration enabled has PracticeMaster open. There have been several checks prior to this point to make
sure PracticeMaster is closed, so if this message is received, it is likely that a user has gone BACK into the program after
being out of it. Do not abort the conversion at this point. The STMAPI.EXE file is in use at this point, and must not be in use
for the conversion to successfully continue. You will have to restore a full backup if you abort the conversion now.
- "The program file PracticeMaster is in use. To complete the conversion, close PracticeMaster on all workstations.
"
- The Conversion program is trying to convert the CM.EXE and CMMAIN.EXE files from Version 12 to Version 14, but one or
both of the files are in use on a workstation. Make sure that every user has closed out of PracticeMaster. There have been
several checks prior to this point to make sure the programs are closed, so if this message is received, it is likely that a
user has gone BACK into the program after being out of it. Do not abort the conversion at this point. The file shown is in use
at this point, and must not be in use for the conversion to successfully continue. You will have to restore a full backup if
you abort the conversion now.
It is important to note that PracticeMaster contains a "minimize to tray" feature. If a user
has selected this option, the PraticeMaster icon could be showing in their System tray instead of on their Taskbar. Also,
depending on their System Tray settings, it could be hidden. It may be beneficial to check the Windows Task Manager for any
instances of CMMAIN.EXE under processes if you are having a difficult time making sure all users are out of the program.
-
- "GLS data not found for GLS Client <###> in path <path> - Conversion will not start."
- One of the GLS clients specified in the GLS client file either has an invalid path, or the path has no data in it.
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 has already been converted to Version 14."
- The GLS data has already been converted to a Version 14 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 our Technical Support Department.
-
- "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).
- "No GLS data exists for GLS client <###>."
- The conversion program could not find the G5LOG.DAT file in the GLS client's data path. If this client should have been
converted to Version 14, call our Technical Support Department. If this GLS client is an old client for which you do not need
to access 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 <###> 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.
-
- "The program file GLS is in use. To complete the conversion, close GLS on all workstations ."
- The Conversion program is trying to convert the GLS.EXE and GLMAIN.EXE files from Version 12 to Version 14, but one or
both of the files are in use on a workstation. Make sure that every user has closed out of GLS. There have been several checks
prior to this point to make sure the programs are closed, so if this message is received, it is likely that a user has gone
BACK into the program after being out of it. Do not abort the conversion at this point. The file shown is in use at this point,
and must not be in use for the conversion to successfully continue. You will have to restore a full backup if you abort the
conversion now.
-
- "The program file APS is in use. To complete the conversion, close APS on all workstations ."
- The Conversion program is trying to convert the APS.EXE and APMAIN.EXE files from Version 12 to Version 14, but one or
both of the files are in use on a workstation. Make sure that every user has closed out of GLS. There have been several checks
prior to this point to make sure the programs are closed, so if this message is received, it is likely that a user has gone
BACK into the program after being out of it. Do not abort the conversion at this point. The file shown is in use at this point,
and must not be in use for the conversion to successfully continue. You will have to restore a full backup if you abort the
conversion now.
-
- "The program file TAS is in use. To complete the conversion, close TAS on all workstations ."
- The Conversion program is trying to convert the TAS.EXE and TRMAIN.EXE files from Version 12 to Version 14, but one or
both of the files are in use on a workstation. Make sure that every user has closed out of GLS. There have been several checks
prior to this point to make sure the programs are closed, so if this message is received, it is likely that a user has gone
BACK into the program after being out of it. Do not abort the conversion at this point. The file shown is in use at this point,
and must not be in use for the conversion to successfully continue. You will have to restore a full backup if you abort the
conversion now.
-
REFERENCES
- KB Article R11086 - STCONV14.LOG Information
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