Company File Check & Repair - Password?

SUGGESTED

I have an error message re. "Unhandled exception has occurred in a component in your application.......etc"

After checking through this forum, I believe I can at least attempt to fix this by running the Company File Check & Repair option. However, when I try to run this it requests a password. I do not have a password set up for my Simply Accounting files. I tried setting up same, which worked fine for accessing my data, but would not permit me to access the Company File Check & Repair program. If anyone has any ideas, I'd be happy to try them! Many thanks.

Parents Reply Children
  • 0 in reply to Old Salt

    We have Sage50 2013.Pro.  And so far so good.  Our issue was that we could not rollover into a new calendar year. Other threads on other forums suggest the fix is the run the Company File check tool - not from with the program, but standalone from the start menu.  Our sysadmin password is good, we have no problem accessing our data with it or even changing the password - but the File checker refuses the password and so does not run.  And Sage support needs $150CDN for a new support contract yet will not guarantee any repair.

    Arrghh!

    So far I have not found anyone online with a similar problem until this forum.

    -Brad

  • 0 in reply to bpears
    SUGGESTED

    Hi Brad,

    Would you consider Sage Partner for this service.

    Please drop a line.

    Thanks,

    Akhtar

  • 0 in reply to BIThelp.ca
    SUGGESTED

    Thank you Akhtar,

    Over this past weekend we were able to fix things.  We located a file of 0 size (tpjbfwdl.frm) that in previous versions is 8.61kb.  Copying this file into our current folder fixed our problem. That file was referenced in "errorlog.txt" under the backups folder and was easy enough to find after knowing where to look.

    Our original trouble was in changing to a new year, but this thread is about the File Checker failing due to an incorrect password.  We no longer are having that problem.  Correct the single bad file has fixed things for us.

    OldSalt... I hope this can drive you in the right direction.

  • 0 in reply to bpears

    So glad this worked for you bpears. I've checked my tpjbfwdl.frm file & it is 8.61kb, which seems right from the size you mention in your message. However, you did prompt me to check the error log, and the message:-

    Error in my_thread_global_end(): 2 threads didn't exit      

    appears numerous times. Does this mean anything to anyone out there? Many thanks, Oldsalt