458162 Views 692 Replies Latest reply: Dec 9, 2013 10:22 PM by seasonsinthesky
Currently Being ModeratedNov 30, 2009 4:51 PM (in response to Moxley)I wonder if it in some way has to do with using Windows file systems via SMB.
I never do, and have never seen this problem regardless of whether I write to USB sticks or whatever - just a data point.Quad 2.5 GHz G5, 5 GB | 15" 2.6 GHz MBP Penryn, 4 GB | 1 TB Dual-Band TC, Mac OS X (10.6.2)
Currently Being ModeratedNov 30, 2009 11:57 PM (in response to William Kucharski)No, I don't think it is anything to do with shared environments. I have been getting these issues ever since moving to SL and at both our UK and French bases, we are now Windoze free zones. In France, we are actually 100% SL, so it is not a question of mixing 32 and 64 bit operating systems either. Disappointed to have received no response from Apple i.r.o. the Capture Data files I have been sending them.
WilsonMBP 13" 2.53 Ghz, MacAir 1.8 Ghz, PMac G5 dual 2.3, Core 2 Duo 2.16 Ghz 20" iMac, Mac OS X (10.6.1)
Currently Being ModeratedDec 1, 2009 12:12 AM (in response to Kel Solaar)i have a wireless network enabled external harddisk, configured to work as an AFP server with my macbook pro...
it worked fine, double-click on the AFP server name on the left pane of the Finder will list down all the shared folders, and i can double-click on any shared folder to open the contents inside.
but after about 1.5 mths of using the external network drive .. i cannot seemed to see the list of shared folders after double-clicking on the AFP server name in Finder..
i tried using "connect to server" option in Finder, and managed to see the list of shared folders. But when i double-click the usual shared folder where i saved all my work, it keeps showing "connecting" and takes forever..
and some times, Finder will hang, when i tried to relaunch it, Finder app cannot be opened anymore, with that error message and i had to force restart my mac
but the other shared folders connect well, and i can see all the contacts inside..
what puzzles me are:
this usual shared folder was working fine, and i did not re-configure anything, but after some time, it seemed to have stopped working.. (time out?)
when i tried to create a new shared folder, which is located inside the shared folder that is not working, it managed to connect without any issue...
anybody encountered such behavior with AFP servers? looks like some "time out" issue, as it was working fine until some time??
any help will be very very much appreciated.. as i had tried all ways and means .. thank
Message was edited by: dlckson
Message was edited by: dlckson
Message was edited by: dlcksonMacBook Pro, Mac OS X (10.6.2), Centrino Core 2 Duo, 2.53GHz with 4GB RAM
Currently Being ModeratedDec 1, 2009 10:51 AM (in response to Kel Solaar)I just got this error message too. It occurred when I had just clicked once (not double) on a TIF file. Finder did not show the preview as expected, and the spinning wheel showed up.
I hit Command-Option-Esc to open "Force Quit Applications", and tried to relaunch Finder, as it was "not responding". The relaunch failed, and Finder disappeared from the list of apps in the Force Quit Applications window.
Also, Finder was missing from the list of apps in the Command-Tab list. Clicking on Finder in the Dock produced the error:
"the application finder can't be opened -10810".
Going into Terminal, and executing the command "open ." produced the error:
LSOpenURLsWithRole() failed with error -10810 for the file /Users/myusername.
I have no choice but to restart, and hope that things will return to normality.13-inch MacBook Pro 2.26 GHz Intel Core 2 Duo, Mac OS X (10.6.2)
Currently Being ModeratedDec 1, 2009 12:07 PM (in response to abatko)A follow-up to my restart attempt.
First of all, as Finder was unavailable, I had to open Terminal and enter the command "reboot" to restart the computer. Restarting failed. I only got the blue screen with the black spinning wheel. And I let it sit like that for at least 10 minutes - at which point I was forced to hold down the power button for several seconds to do a hard shutdown. Once the computer had shut down, I pressed the power button to start it up again. Everything came back to normal, including good ol' Finder. I hope this error does not recur.12-inch PowerBook G4, Mac OS X (10.4.11)
Currently Being ModeratedDec 1, 2009 12:57 PM (in response to Kel Solaar)I was having this problem, getting "The application Finder.app can't be opened.-10810" error message and seeing lots of messages relating to coreservicesd crashing in Console ("coreservicesd is running an unsupported version, etc.").
After some testing, I found I could reliably reproduce the problem just by launching iCal (though I'm pretty sure that wasn't the only thing that could trigger it).
Tried various troubleshooting techniques, all to no avail until I used Onyx (http://www.titanium.free.fr/index_us.html) to rebuild LaunchServices, which seems to have fixed it right up (at least I can launch iCal without triggering it now).MacBook (Core Duo), Mac OS X (10.6.2)
Currently Being ModeratedDec 1, 2009 1:14 PM (in response to Kel Solaar)Unplugging the offending WD MyBook Drive fixed the issue for me. The finder popped back to life. Not sure if I should be mad at WD or Apple.
I just wanted to add this to the bottom as it surfaces here and again in the VERY long thread.MacBook Pro, Mac OS X (10.6.2)
Currently Being ModeratedDec 2, 2009 1:09 PM (in response to Two Weims)Yea I had the same thing. I was working with files on my Time Machine backup drive. So it looks like it has to do with external drives?
Message was edited by: cworsley4MacBook Pro, Mac OS X (10.6.2), 2.4 GHz 4GB ram
Currently Being ModeratedDec 2, 2009 7:30 PM (in response to cworsley4)second to that.... i also suspect... could it be some hidden issues with external hard drive.. when i work without any external hard disk, there is no problem with the Finder...
Yea I had the same thing. I was working with files on my Time Machine backup drive. So it looks like it has to do with external drives?
Message was edited by: cworsley4MacBook Pro, Mac OS X (10.6.2), Centrino Core 2 Duo, 2.53GHz with 4GB RAM
Currently Being ModeratedDec 2, 2009 11:45 PM (in response to dlckson)Have you tried this?
In Preferences Systeme, Energy Saver ( I don't know if then are the right translations in english)
Put OFF: "Stop as soon as possible HD activity".Mac Pro (early 09), Mac OS X (10.6.2)
Currently Being ModeratedDec 3, 2009 6:54 AM (in response to yoonka)Same problem here, attempting to connect to WD Sharespace leads to Finder not responding and not being able to restart. We are a PC Free environment with several other SL Macs accessing WD drive without issues ???? Prior to today, no problems with WD.Macbook Pro, Mac OS X (10.6.2)
Currently Being ModeratedDec 4, 2009 8:47 AM (in response to Publish007)i feedback to the network-enabled external hard disk company 2 months ago, and they replaced another unit of external hard disk for me... it worked fine for 2 months.. and then the same, yes, exactly the same behavior happened again : unable to connect to external hard disk and finder hangs..
hard disk was working fine for past 2 months => no problem with the hard disk and my network configurations.. if thats the case, what could have caused it to stop working?
i tried calling Apple Care twice. .. spoke to 2 different support officers .. tried every thing they said [delete preference files, terminal command, etc etc] .. and still the same problem
submitted a case via support web here, and waiting for them to call back [if ever?]
juz curious , is there any apple staff in this forum.... i need to know, what could have caused my connection to the network hard disk to stop work after some time..MacBook Pro, Mac OS X (10.6.2), Centrino Core 2 Duo, 2.53GHz with 4GB RAM
Currently Being ModeratedDec 4, 2009 3:50 PM (in response to Kel Solaar)I've had this problem too. I found that journaling had become disabled on my boot volume, causing 10.6 to cause directory corruption as it relies on the volume's journal to operate properly. After fixing the directory using DiskWarrior (DiskUtility would work as well), I re-enabled journaling in DiskUtility and restarted. The problem hasn't come back since.MacBook Pro, Mac OS X (10.6.2), 2.66, 4GB RAM, 500GB 7200rpm HD
Currently Being ModeratedDec 4, 2009 4:20 PM (in response to NURV2600)Man, would that be amazing... Everyone here experiencing this issue: go to Disk Utility, and make sure that journaling is enabled on your boot drive!
Either way, report back, just in case we've (NURV2600, actually) found the solution!!Quad core Mac Pro 2.66GHz, MacBook Pro 2.4GHz, Mac OS X (10.6.1), 12 GB RAM (Mac Pro), 4 GB RAM (MB Pro)
Currently Being ModeratedDec 4, 2009 4:49 PM (in response to John I. Clark)mine is still journaled so it's not the problem. My guess in NURV2600's case it was just coincidence.
The only common things I see are that we are all mounting some kind of file system whether it's on a USB external drive, a USB thumbdrive, CD/DVD or network. My hunch was that spotlight was somehow involved (trying to scan the newly mounted drive), but I'm not sure if that's been ruled out. In my case i disabled spotlight on the affected drives and so far haven't had a problem, but not sure if that's a coincidence.MacBook Pro 2.5GHz Core 2 Duo, Mac OS X (10.6.1), 4GB RAM (keys that don't work 100% of the time when hit in the corners)