The information in this article applies to:
Tabs3 Palm Application is a separate software module that allows integration with various handheld devices using Palm OS® software. This article includes troubleshooting information and a list of messages that may be encountered when HotSyncing from the handheld device to Tabs3. Each error message includes a cause and solution to assist in troubleshooting.
Messages that occur during HotSync will be saved in either the HotSync Log file or T3PALM.LOG file.
HotSync Log: If an error occurs during a HotSync, a window will be displayed asking if you want to view the HotSync Log file. If you choose to view the log file, a window will be displayed listing the error that occurred. The file name is HOTSYNCLOG.HTM or HOTSYNC.LOG (depending on which version of HotSync is being used). This file is located in the Palm user's directory where the Palm Desktop is installed (e.g., C:\PALM\ROBERT). The HotSync Log file is created by the Palm OS® HotSync software.
T3PALM.LOG: The T3PALM.LOG file is created if there is an error while merging data into Tabs3. This file resides in the directory where the Tabs3 software is installed (e.g., C:\STI). Each time a HotSync is performed, a new T3PALM.LOG file is created only if errors are encountered. If no errors are reported, the T3PALM.LOG file is deleted.
Note: All of the following situations will cause an entry to remain in the handheld without being merged.
Tabs3 Program and Palm Sync Program do not match.
Cause: The serial number of the Tabs3 Palm Sync program and Tabs3 do not match.
Solution: Contact your reseller or Technical Support.
Tabs3 data not found.
Cause: The t3custom.dat file is corrupt or missing from the Tabs3 directory.
Solution: Determine why the file is missing. To recreate it, you must restore from a backup.
User xxx not found in System Config. This user ID must be added before the data can be synchronized.
Cause: The handheld user you are syncing for does not exist in System Configuration.
Solution: Add the User ID to System Configuration. HotSync again.
Active user limit reached or user has no access rights. Sync Denied.
Cause: Too many users are logged into Tabs3.
Solution: Wait until a user logs out of Tabs3 and try the HotSync again. The Active User List in Tabs3 can be used to determine which users are using the software. DO NOT reset a user who is still in the software.
Tabs3 Palm Sync could not be started. Try again later.
Cause: An exclusive task is running in Tabs3. When an exclusive task is running in Tabs3, no other users can use Tabs3.
Solution: Wait until the exclusive task has been completed and try the HotSync again. The Active User List in Tabs3 can be used to determine which users are using the software. DO NOT reset a user who is still in the software.
Invalid client ID: <client ID> in record <record #>.
Cause: An invalid Client ID was assigned to an entry in the handheld.
Solution: Edit the entry in the handheld using a valid Client ID. HotSync again.
Client ID: <client ID> in record <record #> not found in Tabs3.
Cause: A Client ID that does not exist in Tabs3 was assigned to an entry in the handheld.
Solution: Either edit the entry in the handheld or add the Client ID in Tabs3. HotSync again. The entry will be retained in the handheld until: 1) it is deleted; or 2) the client has been added to Tabs3 and the entry is HotSynced to Tabs3.
Tcode: <tcode> in record <record #> not found in Tabs3.
Cause: A tcode that does not exist in Tabs3 was assigned to an entry in the handheld.
Solution: Either edit the entry in the handheld or add the tcode in Tabs3. HotSync again. The entry will be retained in the handheld until: 1) it is deleted; or 2) the tcode has been added to Tabs3 and the entry is HotSynced to Tabs3.
Tcode: <tcode> in cost record <record #> is a fee tcode.
Cause: Tabs3 does not allow fee tcodes to be used for cost transactions.
Solution: Either edit the cost transaction in the handheld to use a cost tcode, or delete the cost entry and reenter it as a fee entry if appropriate.
Timekeeper: <timekeeper> in record <record #> not found in Tabs3.
Cause: A timekeeper was assigned to an entry that has not been set up in Tabs3.
Solution: Either edit the entry in the handheld or add the timekeeper in Tabs3. HotSync again. The entry will be retained in the handheld until: 1) it is deleted; or 2) the timekeeper has been set up in Tabs3 and the entry is HotSynced to Tabs3.
Client <xxx.xxx> is Inactive in record <record #>.
Cause: A transaction (other than a credit) has been entered for a client with an inactive status.
Solution: Billable transactions cannot be entered for an inactive client. Change the transaction to a Non-Billable transaction in the handheld or change the client in Tabs3 to not have an inactive status.
These errors will appear in the T3PALM.LOG file.
If an error is encountered when Tabs3 attempts to create the GLS journal entries, the transaction will be merged into Tabs3 but the GLS journal entries will not be created. These entries should be entered manually in GLS. The GLS reject codes are listed below:
Code 10
GLS Account not found.
Code 30
Invalid GLS journal.
Code 40
Date for GLS journal entry out of valid range.
Warning
Entry was posted into prior year balances. (Note: The Warning indicates a GLS journal entry with a date for the prior fiscal year was posted. The Warning is generated to let you know that your previous year’s balances have changed.)
"xxx" is synchronizing Tabs3 data to the Palm. You may continue but errors may occur. Continue anyway?
Cause: This error occurs when trying to use the Tabs3 Handheld Integration program. It is caused by one of two situations:
- a user is currently synchronizing data with a handheld; or
- a user has created Tabs3 Palm App data files using the Handheld Integration program in Tabs3 but has not yet HotSynced the files to their handheld.
Solution: If a user is currently synchronizing data to the handheld, wait until the user is finished. If the latter situation is the cause of the error, determine whether the user specified in the message (i.e., "xxx") wants to HotSync their data before you create new data files. If the user wants to HotSync the files, wait until they have been HotSynced to that user's handheld prior to creating data files for your User ID. If you continue, the other user's data files will be overwritten. If the user is not available, you can continue and overwrite the user's files and the user can easily recreate them at a later time. However, you want to avoid a situation where another user creates the files, you create your files (effectively overwriting their files) and then the other user HotSyncs your files.
Additional troubleshooting assistance can be found using the following article in our Knowledge Base:
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