Sage 100

Client is on Sage100 standard, version 2017.  Very active - lots of posting - 150 invoices per day etc.  Every few days they get an error 105 in Cash receipts update, line 2027 which is the AR_TransactionPaymentHistory .  We rebuild it and complete the posting.  they post SO invoices (which never give this error), and cash receipts batches, and after a few days .... the error pops again.  No other functions (PO receipts, IM transactions, GL journal entries) ever get errors in any file other than the above.

Not the same user, not the same computer doing the Cash Receipts posting when the error occurs...

Any ideas, even "wacky" ones are welcome - (day of the week, what the person doing the entry had for lunch, etc.)

Thanks in advance.

Jeff

------------------------------
Jeff Fiddelman
Exeplex, LLC
------------------------------

It might be helpful to determine the record or records that are corrupted and are getting repaired during the rebuild.  For example, if it is a certain field that always gets corrupted (a date, a customer number, etc), maybe the corruption is being propagated from the Customer, Tax schedule, or another table to Cash Receipts, then to AR_TransactionPaymentHistory.

------------------------------
Doug Higgs
Midwest Commerce Solutions, Inc
(312) 315-0960
Assistant to the Traveling Secretary
------------------------------

Another trick, going way back is to copy the file, rename the original so it stays where it is, then rename and rebuild the copy as the history file.  This eliminates a weak sector or track as the cause.  I don't personally think this is the case, but an error 105 is a hardware related error.

How is Sage 100 accessed?  Directly from the workstations or through a terminal server?  If directly, you may have a intermittent or bad network card or cable, or a weak port on the switch (or a weak or failing switch).  Have IT move the CR user to a different port on the switch, change out network cables (both at the user's workstation and the patch cable).  If problem continues, change the network card in the workstation (or simply get a new workstation).  As you can see, this can be quite the snark hunt.

My personal recommendation is that Sage 100 Standard should always be run through a terminal server, with the Sage 100 Standard installed on that server, so the data never leaves the server.  Bonus, it runs faster in multi user mode, and I personally have never had error 105s in this configuration.

------------------------------
Bob Sosbee
Senior Developer
Accounting Systems, Inc. (ASI)
Covina CA
803-252-6154 x245
------------------------------