topbanner_forum
  *

avatar image

Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length
  • Wednesday April 24, 2024, 8:16 pm
  • Proudly celebrating 15+ years online.
  • Donate now to become a lifetime supporting member of the site and get a non-expiring license key for all of our programs.
  • donate

Author Topic: EInvalidOp exception  (Read 3937 times)

rgkh

  • Participant
  • Joined in 2010
  • *
  • default avatar
  • Posts: 2
    • View Profile
    • Donate to Member
EInvalidOp exception
« on: June 20, 2011, 02:10 AM »
Dear developer,

I have downloaded the latest version of FARR from donationcoder.com. When I wanted to launch the application and search for files, it crashed and threw the EInvalidOp exception.

I'm running Windows 7 Home Premium SP1 with 64-bit OS.

farrerror1.PNG

Please advise if you need more information on the error for your debugging.

Thank you!

Regards,
rgkh

mouser

  • First Author
  • Administrator
  • Joined in 2005
  • *****
  • Posts: 40,901
    • View Profile
    • Mouser's Software Zone on DonationCoder.com
    • Read more about this member.
    • Donate to Member
Re: EInvalidOp exception
« Reply #1 on: June 20, 2011, 02:53 AM »
Did it happen after you pressed your first key to search for files?

It's possible this is happening because a file on your search path (in start menu for example) has an insane date.  If you know how to search and find such a file it would be helpful if you could confirm.

I think someone else had this problem as well and I never got around to fixing it. I will.

rgkh

  • Participant
  • Joined in 2010
  • *
  • default avatar
  • Posts: 2
    • View Profile
    • Donate to Member
Re: EInvalidOp exception
« Reply #2 on: June 20, 2011, 03:02 AM »
Dear mouser,

I managed to launch and search successfully after editing the search folder entries, although I'm using the same directory path, after I re-added the entry it worked. Sorry that I don't know how it happened and I'm unable to provide further details for you to debug.

Did it happen after you pressed your first key to search for files?

It's possible this is happening because a file on your search path (in start menu for example) has an insane date.  If you know how to search and find such a file it would be helpful if you could confirm.

I think someone else had this problem as well and I never got around to fixing it. I will.