Your best friend for file transfer.

Fetch application logoFetch

Fetch 5.3 does not work. Mac OS Error? (13 posts)

  • Started 9 years ago by voyager360
  • Latest reply 9 years ago from Scott McGuire
  • voyager360 Member

    This just started. I cannot enter any shortcut now and I cannot CREATE new Fetch shortcuts. Oddly enough my passwords to servers did NOT change and only one shortcut link works. I am n Mac OS 10.5 and using Fetch 5.3 -- latest update and patch. I get a Mac OS error -2147415734

    IS anyone else getting this headache? I had to switch to another FTP client to get this to work, so this is Definitely a Fetch problem or a Mac OS 10.5 bug.

    Can anyone shine some light on this? I have Fetch 5.3 at home and is on a G4 with Mac os 10.5 and it runs just fine.

    Posted 9 years ago #

  • Scott McGuire Administrator

    Hi,

    This is a bug in the Mac OS X keychain that some users have experienced after upgrading to Mac OS X 10.5. While it is not a Fetch bug, it affects Fetch because Fetch uses the keychain to securely store the passwords for your shortcuts.

    Usually one of the two solutions below fixes the problem. Please try the following:

    First, choose Software Update from the Apple menu and check for updates. You should install both the "Login & Keychain Update for Leopard" and the "Mac OS X 10.5.1" update. These both include Keychain fixes. (You may have already installed the former, so don't worry if it's not listed.) Then restart your Mac, if you haven't been required to by the update process.

    Try Fetch again. If the updates haven't helped, or you've already installed both updates, next please do the following:

    * Quit Fetch, if it's running.
    * Open the Keychain Access application, which is in the Utilities folder inside your Applications folder.
    * Go to the Keychain Access menu, and choose Preferences.
    * Click on the "First Aid" tab.
    * Make sure both "Synchronize login keychain password" and "Set login keychain as default" are checked.
    * Then go to the Keychain Access menu, and choose Keychain First Aid.
    * In the password field of the Keychain First Aid window, enter your Mac OS X admin password (this should be the same as your Mac OS X login password).
    * Click the Repair radio button.
    * Click the Start button.
    * Once it's done, close the Keychain First Aid window.
    * Restart your Macintosh.

    Then try Fetch again.

    Let us know if either of these helps. If not, we will investigate further.

    Thanks,

    Scott McGuire
    Fetch Softworks

    Posted 9 years ago #

  • dspedersen Member

    I have the almost same problem, albeit I get the 'Mac OS error 10002'. Both of the suggestions posted were tried but in vain. It's odd because I've had no problems so far using Fetch (latest) under Leopard 10.5.2. It just came out of nowhere today.

    Any other suggestions, as to how to solve the problem?

    I tried downloading Fetch for a re-install but that didn't help either.

    Thanks in advance,
    Dan

    Posted 9 years ago #

  • Scott McGuire Administrator

    Hi Dan,

    Mac OS Error 10002 is an error from the Mac OS X's graphics system. So this is not related to the keychain.

    Mac OS X 10.5.2 has not been released yet; could you please double-check which version of the Mac OS you have and let us know?

    And let me make sure I understand you correctly: on the very same Macintosh, Fetch was working fine yesterday, and today it does not?

    Thanks,

    Scott McGuire
    Fetch Softworks

    [This message has been edited by ScottMcGuire (edited 01-17-2008).]

    Posted 9 years ago #

  • dspedersen Member

    Sorry, my mistake - we're talking 10.5.1, of course.

    Yes, pretty much that way, though I believe it was last week I used it, or so. But I haven't done anything radically to the OS X, installed other apps or something like that.

    Thanks,
    Dan

    Posted 9 years ago #

  • dspedersen Member

    Oh, another thing: The dialog window giving me the message is stock - It won't disappear, why I have to force quit Fetch.

    Thanks,
    Dan

    Posted 9 years ago #

  • Scott McGuire Administrator

    Hi Dan,

    We'd like some more information in order to investigate.

    Does this error happen when you open Fetch, or when you trying to do something in Fetch? And if so, what actions cause the error to appear

    And we'd like to see a copy of your system.log, which contains information about what caused that error.

    To find the system.log file, choose "Go to Folder..." from the Go menu in the Finder and enter "/var/log" (without the quotes).

    Then, please email the system.log file you'll find in that folder to:

    bugs at fetchsoftworks dot com

    Thanks,

    Scott McGuire
    Fetch Softworks

    Posted 9 years ago #

  • dspedersen Member

    Hi Scott

    It's when I start Fetch the problem arises. I have a server shortcut on my desktop and at first I thought that this one was causing the problem. I am, however, unable to start Fetch directly from the App folder.

    I've sendt my system.log file to the address you posted.

    Thanks for all your help,
    Dan

    Posted 9 years ago #

  • dspedersen Member

    Hi again

    Just to report back - I've solved the problem, or sort of...

    Two days ago my Macbook was unable to shut down properly, it just hanged without getting somewhere. The following day, all my iWork-apps started to malfunction, e.g. like non.operable ghost-like windows, and even my old Pages-files wouldn't open properly.

    So, after doing som research and writing on the Apple discussion pages, I came to the conclusion that a clean installation was the right, and only, choice as I've already archived and installed Leopard THREE (!) times before (excluding the first, faulty blue screen situation I got when I did the first update from Tiger to Leopard).

    So, I've been cursed by a long row of problems, of which can possibly be traced back to a curvy road of upgrade and A&I's of Leopard.

    However, now both Fetch and Pages functions and hope they'll keep on doing that, as well hope that a lot of irregularities (like prolonged shut downs, etc.) are off for good!

    Thanks for being so responsive - you (and Fetch) rock big time :-)

    Regards,
    Dan

    [This message has been edited by dspedersen (edited 01-22-2008).]

    Posted 9 years ago #

  • Scott McGuire Administrator

    Hi Dan,

    You're welcome, and thanks for the followup - we're glad to hear your problems are resolved!

    Best,

    Scott McGuire
    Fetch Softworks

    Posted 9 years ago #

  • ckilgore Member

    In case anyone else has this problem, I solved it using a method I saw posted in response to someone getting the same error message, but in their .mac settings.

    All I did was go into my keychain and delete all the fetch passwords (make sure you have these someplace else first or can remember them!), restart my computer and voila! Fetch works like it is supposed to again.

    Posted 9 years ago #

  • voyager360 Member

    I completely gave up on Fetch and whole stupid idea of the Macintosh Keychain piece of crap. I have Mac OS 10.5 on both computers one at off and one at home. AFter 30 days of corruption, calling Apple computer and not being to use Fetch, and wiping out the Keychain passwords I just gave up. I removed Fetch from both computers and I purchased Transmit. This sucks because I was a real Fetch fan for years, and I was an original Netscape employee and I am no dummy when it comes to using computers. But 30 days... come on. This is stupid and I blame Apple or Fetch because the product has flaws due to how Apple OS works or how Fetch insists on using the stupid keychain.

    Originally posted by ScottMcGuire:

    Hi,

    This is a bug in the Mac OS X keychain that some users have experienced after upgrading to Mac OS X 10.5. While it is not a Fetch bug, it affects Fetch because Fetch uses the keychain to securely store the passwords for your shortcuts.

    Usually one of the two solutions below fixes the problem. Please try the following:

    First, choose Software Update from the Apple menu and check for updates. You should install both the "Login & Keychain Update for Leopard" and the "Mac OS X 10.5.1" update. These both include Keychain fixes. (You may have already installed the former, so don't worry if it's not listed.) Then restart your Mac, if you haven't been required to by the update process.

    Try Fetch again. If the updates haven't helped, or you've already installed both updates, next please do the following:

    * Quit Fetch, if it's running.
    * Open the Keychain Access application, which is in the Utilities folder inside your Applications folder.
    * Go to the Keychain Access menu, and choose Preferences.
    * Click on the "First Aid" tab.
    * Make sure both "Synchronize login keychain password" and "Set login keychain as default" are checked.
    * Then go to the Keychain Access menu, and choose Keychain First Aid.
    * In the password field of the Keychain First Aid window, enter your Mac OS X admin password (this should be the same as your Mac OS X login password).
    * Click the Repair radio button.
    * Click the Start button.
    * Once it's done, close the Keychain First Aid window.
    * Restart your Macintosh.

    Then try Fetch again.

    Let us know if either of these helps. If not, we will investigate further.

    Thanks,

    Scott McGuire
    Fetch Softworks

    Posted 9 years ago #

  • Scott McGuire Administrator

    Originally posted by voyager360:

    I completely gave up on Fetch and whole stupid idea of the Macintosh Keychain piece of crap. I have Mac OS 10.5 on both computers one at off and one at home. AFter 30 days of corruption, calling Apple computer and not being to use Fetch, and wiping out the Keychain passwords I just gave up. I removed Fetch from both computers and I purchased Transmit. This sucks because I was a real Fetch fan for years, and I was an original Netscape employee and I am no dummy when it comes to using computers. But 30 days... come on. This is stupid and I blame Apple or Fetch because the product has flaws due to how Apple OS works or how Fetch insists on using the stupid keychain.

    Transmit also uses the Keychain to store passwords - in fact, nearly every password-using program on the Macintosh does - so you may eventually run into the same problem with it. So in this regard, Fetch and Transmit do nothing different.

    We're sorry about the problems you had and we are sorry to lose you as a customer, and had you contacted us again, we would would have been happy to try to help.

    As you can see from the discussion above, we do try to work with customers to resolve their problems.

    Thanks,

    Scott McGuire
    Fetch Softworks

    Posted 9 years ago #

Reply

  • Or nickname, if you prefer.
  • This will be kept confidential.
  • This is to ensure that you’re a person, not a spambot.