Data File Integrity Check Errors (Ver. 15)

Last reviewed: 09/11/2009
Article ID: R11245

The information in this article applies to:

Note:  If you attempt to manually correct the errors found by the Data File Integrity Check, run the Data File Integrity Check again after your corrections. If you restore from a backup due to corrupted data files, run the Data File Integrity Check program after you have restored to verify that the restored data is not also corrupt.

Note:  If restoring data files, be sure to consider the status of other Tabs3 and PracticeMaster programs that integrate with the program you are restoring and also restore those systems if necessary.

Tabs3 Error Numbers

Note: The following errors are not reported when running the DFIC with the Read Only check box selected: 23 (when occurring in a file other than the Client file), 26, 27, 66 and 69.

  4 - Inactivity Warning
10 - Invalid Character
11 - Invalid Category
21 - Invalid Value for Boolean Field
22 - Integer Out of Range
23 - Reference Number is Negative
24 - Statement Number is Negative
26 - Reference Number is Too Large
27 - Reference Number is Zero
51 - Invalid Client ID
52 - Invalid Date
54 - Client ID Not Defined
55 - Keys Out of Sequence
56 - Invalid Sequence Number
57 - Invalid Link
59 - Invalid Client ID in Shared Client Rate Table
60 - Split Fee Client IDs Not Equal
66 - Duplicate Mirror Sequence Number
69 - Duplicate Keys
71 - Duplicate Task Code
72 - File Structure is Corrupt (Bad DODA)
73 - File Structure is Corrupt (Bad IFIL)
74 - Missing File
80 - Invalid Transaction Code
81 - Invalid Task Based Billing Code
94 - Invalid Percentage in Split Fee File
95 - Invalid Timekeeper
96 - Empty Field
97 - Colon Not Allowed
98 - Invalid Hours Worked
99 - Invalid Units
145 - User ID Not Defined
180 - Task Based Billing Switch Conflict
500 - PracticeMaster and Tabs3 / TAS Files Are Not Synchronized
501 - PracticeMaster and Tabs3 / TAS Files Are in Pending Sync Mode
600-699 - Ledger Validation Errors
If you encounter a ledger validation error, please contact Technical Support for additional information.
page top

Tabs3 Remote Error Numbers

Note: The following error is not reported when running the DFIC with the Read Only check box selected: 69.

10 - Invalid Character
11 - Invalid Category
21 - Invalid Value for Boolean Field
22 - Integer Out of Range
23 - Reference Number is Negative
26 - Reference Number is Too Large
51 - Invalid Client ID
52 - Invalid Date
55 - Keys Out of Sequence
56 - Invalid Sequence Number
69 - Duplicate Keys
72 - File Structure is Corrupt (Bad DODA)
73 - File Structure is Corrupt (Bad IFIL)
80 - Invalid Transaction Code
81 - Invalid Task Based Billing Code
95 - Invalid Timekeeper
98 - Invalid Hours Worked
99 - Invalid Units

page top

General Ledger Error Numbers

Note: The following error is not reported when running the DFIC with the Read Only check box selected: 69.

  8 - Path Not Relative
10 - Invalid Character
18 - Bad Sort Sequence Number
21 - Invalid Value for Boolean Field
25 - Invalid GLS Path
28 - Path Not Relative: Manual Change Required
50 - Invalid Key Value
51 - Invalid Account Number
52 - Invalid Date
54 - Account Not Defined
55 - Keys Out of Sequence
56 - Invalid Sequence Number
58 - Account is Heading/Total/Comment
65 - Invalid Department
66 - Invalid Journal
69 - Duplicate Key
72 - File Structure is Corrupt (Bad DODA)
73 - File Structure is Corrupt (Bad IFIL)
76 - Retained Earnings Mismatch
page top

Accounts Payable Error Numbers

Note: The following error is not reported when running the DFIC with the Read Only check box selected: 69.

  5 - Missing Federal ID Number in Vendor File
10 - Invalid Character
21 - Invalid Value for Boolean Field
23 - Reference Number is Negative
26 - Reference Number is Too Large
27 - Reference Number is Zero
50 - Invalid Key Value
51 - Invalid Vendor Number
52 - Invalid Date
54 - Vendor Not Defined
55 - Keys Out of Sequence
56 - Invalid Sequence Number
65 - Invalid Bank
69 - Duplicate Key
72 - File Structure is Corrupt (Bad DODA)
73 - File Structure is Corrupt (Bad IFIL)

page top

Trust Accounting Error Numbers

Note: The following error is not reported when running the DFIC with the Read Only check box selected: 69.

  4 - Inactivity Warning
  5 - Missing Federal ID Number in Payee File
  6 - Federal ID Numbers Do Not Match
10 - Invalid Character
11 - Invalid Category
21 - Invalid Value for Boolean Field
23 - Reference Number is Negative
26 - Reference Number is Too Large
27 - Reference Number is Zero
51 - Invalid Trust ID
52 - Invalid Date
54 - Trust ID Not Defined
55 - Keys Out of Sequence
56 - Invalid Sequence Number
65 - Invalid Bank
69 - Duplicate Keys
72 - File Structure is Corrupt (Bad DODA)
73 - File Structure is Corrupt (Bad IFIL)
74 - Missing File
77 - T3/GL Integration Pending
78 - Invalid Reconciliation State
95 - Invalid Timekeeper
page top

PracticeMaster Error Numbers

Note: The following errors are not reported when running the DFIC with the Read Only check box selected: 69, 170, and 301.

    7 - Data File Not Found - Will Be Created
  10 - Invalid Character
  21 - Invalid Value for Boolean Field
  51 - Invalid Client ID
  52 - Invalid Date
  53 - Invalid Time
  54 - Client ID Not Defined
  56 - Invalid Sequence Number
  66 - Duplicate Mirror Sequence Number
  69 - Duplicate Keys
  80 - Invalid Transaction Code
  82 - Invalid Category
  90 - Invalid Area of Practice in Client File
  91 - Mismatched Area of Practice Information in File
  95 - Invalid Timekeeper
110 - Error in Key #0 Sequence
111 - Error in Key Sequence
140 - Timekeeper Not Defined
141 - Transaction Code Not Defined
142 - Category Not Defined
143 - Task Code Not Defined
144 - User Defined Lookup Record Not Defined
145 - User ID Not Defined
146 - Calendar Code Not Defined
147 - Location Not Defined
148 - Related Party Category Not Defined
150 - Related Party Not Defined
151 - Cross Reference Record Not Found for Related Party Field
152 - Mismatched Related Party Field Record Number in Cross Reference File
153 - Mismatched Area of Practice Information in Cross Reference Record
154 - Mismatched File Name in Cross Reference Record
155 - Mismatched Area of Practice Record Number in Cross Reference File
156 - Mismatched Client ID in Cross Reference File
157 - Mismatched Area of Practice Field Number in Cross Reference File
158 - Related Party Lookup Field Does Not Point to a Cross Reference Record
170 - User Updating is Not Empty in Timer Record
171 - Invalid Task Based Billing Code
172 - Value of Numeric Field Outside of Configured Minimum and Maximum Range
174 - Invalid Syntax in Field
175 - A Required Field is Empty
176 - A Field is Longer than the Defined Length
177 - Validate Record Failed
178 - Value Not in List of Valid Options
179 - User/Group Field Has Lowercase Letters
210 - Invalid Field Count
220 - Invalid Record Length
252 - Invalid Segment Length
260 - Invalid Field Length
264 - Invalid Field Type
266 - Invalid Field Decimal Length
268 - Invalid Field Name
291 - Index File not found
295 - Data File Has Incorrect Permissions (not read/write)
296 - Index File Has Incorrect Permissions (not read/write)
301 - Incorrect Ctree Header Length
400-430 - Journal Attachment Errors
420 - Data appears to be corrupt
500 - PracticeMaster and Tabs3 / TAS Files Are Not Synchronized
501 - PracticeMaster and Tabs3 / TAS Files Are in Pending Sync Mode
page top

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