Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Error while grinding AlohaQs trans.log

Status
Not open for further replies.

posknowitall

Technical User
Dec 2, 2005
252
US
insert entries: e is null is the error I am getting when grinding a trans.log in QS 5.2.8. Tried to run a fixlog and copied dbf files from the day before. I have seen this before but can't remember the fix to this very old problem. Anyone remember?? Thanks
 
I think "e" is referenced in the trans.log but no longer found in the database. If copying .dbf files and running a fixlog didn't work, I would remove the instances of "e" in the trans.log if you have the ability to do so.
 
My experience has been that when a trans.log is so corrupt that the fix log doesn't work, its usually history. I know it's technically fixable, but once you tell them that they'll have to pay Radiant to have it fixed, they usually just say forget it.

Usually the corruption is in the log itself, not the dbfs tho.
 
Yep, it was a goner. No hope for the trans.log. Thanks
 
Yeah, I kinda figured.

Clients who've had experience with older versions, 4.x and early 5.0, were WAY more susceptible to corrupt logs. However, they were generally fixable.

In more recent versions, they are FAR less common overall, but when they do happen, there seems to be a much greater chance that it will NOT be fixable.

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top