Mtmfs: mount failed for /Volumes/MobileBackups 9

Hello, I looked over the net and couldn't find an answer my problem.
The new MobileBackup feature in Lion doesn't work, error [1] keeps popping every 5 seconds. Looking over the System Diagnostic Reports I see that mtmfs keeps crashing regularly with the same errror [2].
It seems to me that mtmfs is looking for some executable that it can't find, but it's not clear from the log which one is that. Also I wonder why just MobileBackup 9?
Please I'm thinking about reinstalling Lion just so I can get ride of this annoying error.
Let me know if you require more information.
[1]:
11/10/11 12:47:33.988 PM mtmfs: mount failed for /Volumes/MobileBackups 9
11/10/11 12:47:33.990 PM com.apple.launchd: (com.apple.mtmfs[3993]) Exited with code: 22
11/10/11 12:47:33.990 PM com.apple.launchd: (com.apple.mtmfs) Throttling respawn: Will start in 5 seconds
[2]:
Process:         mtmfs [256]
Path:            /System/Library/CoreServices/backupd.bundle/Contents/Resources/mtmfs
Identifier:      mtmfs
Version:         ??? (???)
Code Type:       X86-64 (Native)
Parent Process: launchd [1]
Date/Time:       2011-10-08 10:55:45.497 +0300
OS Version:      Mac OS X 10.7.1 (11B26)
Report Version: 9
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Application Specific Information:
objc[256]: garbage collection is OFF
*** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: 'launch path not accessible'
*** First throw call stack:
    0   CoreFoundation                      0x00007fff88c44986 __exceptionPreprocess + 198
    1   libobjc.A.dylib                     0x00007fff8d504d5e objc_exception_throw + 43
    2   CoreFoundation                      0x00007fff88c447ba +[NSException raise:format:arguments:] + 106
    3   CoreFoundation                      0x00007fff88c44744 +[NSException raise:format:] + 116
    4   Foundation                          0x00007fff903ddcb4 -[NSConcreteTask launchWithDictionary:] + 470
    5   Foundation                          0x00007fff904f25f4 +[NSTask launchedTaskWithLaunchPath:arguments:] + 203
    6   mtmfs                               0x000000010ec72a18 mtmfs + 31256
    7   mtmfs                               0x000000010ec7af63 mtmfs + 65379
    8   mtmfs                               0x000000010ec80214 mtmfs + 86548
    9   Foundation                          0x00007fff9040d804 __NSFirePerformWithOrder + 382
    10 CoreFoundation                      0x00007fff88c04647 __CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION__ + 23
    11 CoreFoundation                      0x00007fff88c045a6 __CFRunLoopDoObservers + 374
    12 CoreFoundation                      0x00007fff88bd9889 __CFRunLoopRun + 825
    13 CoreFoundation                      0x00007fff88bd9216 CFRunLoopRunSpecific + 230
    14 Foundation                          0x00007fff90398983 -[NSRunLoop(NSRunLoop) runMode:beforeDate:] + 267
    15 Foundation                          0x00007fff9039886f -[NSRunLoop(NSRunLoop) run] + 62
    16 mtmfs                               0x000000010ec7fa0c mtmfs + 84492
    17 mtmfs                               0x000000010ec6ca4c mtmfs + 6732
    18 ???                                 0x0000000000000008 0x0 + 8
terminate called throwing an exception
abort() called
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   libsystem_kernel.dylib            0x00007fff8a792ce2 __pthread_kill + 10
1   libsystem_c.dylib                 0x00007fff8edc17d2 pthread_kill + 95
2   libsystem_c.dylib                 0x00007fff8edb2a7a abort + 143
3   libc++abi.dylib                   0x00007fff913597bc abort_message + 214
4   libc++abi.dylib                   0x00007fff91356fcf default_terminate() + 28
5   libobjc.A.dylib                   0x00007fff8d5051b9 _objc_terminate + 94
6   libc++abi.dylib                   0x00007fff91357001 safe_handler_caller(void (*)()) + 11
7   libc++abi.dylib                   0x00007fff9135705c std::terminate() + 16
8   libc++abi.dylib                   0x00007fff91358152 __cxa_throw + 114
9   libobjc.A.dylib                   0x00007fff8d504e7a objc_exception_throw + 327
10 com.apple.CoreFoundation          0x00007fff88c447ba +[NSException raise:format:arguments:] + 106
11 com.apple.CoreFoundation          0x00007fff88c44744 +[NSException raise:format:] + 116
12 com.apple.Foundation              0x00007fff903ddcb4 -[NSConcreteTask launchWithDictionary:] + 470
13 com.apple.Foundation              0x00007fff904f25f4 +[NSTask launchedTaskWithLaunchPath:arguments:] + 203
14 mtmfs                             0x000000010ec72a18 0x10ec6b000 + 31256
15 mtmfs                             0x000000010ec7af63 0x10ec6b000 + 65379
16 mtmfs                             0x000000010ec80214 0x10ec6b000 + 86548
17 com.apple.Foundation              0x00007fff9040d804 __NSFirePerformWithOrder + 382
18 com.apple.CoreFoundation          0x00007fff88c04647 __CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION__ + 23
19 com.apple.CoreFoundation          0x00007fff88c045a6 __CFRunLoopDoObservers + 374
20 com.apple.CoreFoundation          0x00007fff88bd9889 __CFRunLoopRun + 825
21 com.apple.CoreFoundation          0x00007fff88bd9216 CFRunLoopRunSpecific + 230
22 com.apple.Foundation              0x00007fff90398983 -[NSRunLoop(NSRunLoop) runMode:beforeDate:] + 267
23 com.apple.Foundation              0x00007fff9039886f -[NSRunLoop(NSRunLoop) run] + 62
24 mtmfs                             0x000000010ec7fa0c 0x10ec6b000 + 84492
25 mtmfs                             0x000000010ec6ca4c 0x10ec6b000 + 6732
Thread 1:: Dispatch queue: com.apple.libdispatch-manager
0   libsystem_kernel.dylib            0x00007fff8a7937e6 kevent + 10
1   libdispatch.dylib                 0x00007fff9140260e _dispatch_mgr_invoke + 923
2   libdispatch.dylib                 0x00007fff9140119e _dispatch_mgr_thread + 54
Thread 2:
0   libsystem_kernel.dylib            0x00007fff8a793192 __workq_kernreturn + 10
1   libsystem_c.dylib                 0x00007fff8edc1594 _pthread_wqthread + 758
2   libsystem_c.dylib                 0x00007fff8edc2b85 start_wqthread + 13
Thread 3:
0   libsystem_kernel.dylib            0x00007fff8a793192 __workq_kernreturn + 10
1   libsystem_c.dylib                 0x00007fff8edc1594 _pthread_wqthread + 758
2   libsystem_c.dylib                 0x00007fff8edc2b85 start_wqthread + 13
Thread 4:
0   libsystem_kernel.dylib            0x00007fff8a793192 __workq_kernreturn + 10
1   libsystem_c.dylib                 0x00007fff8edc1594 _pthread_wqthread + 758
2   libsystem_c.dylib                 0x00007fff8edc2b85 start_wqthread + 13
Thread 5:
0   libsystem_kernel.dylib            0x00007fff8a792e06 __select_nocancel + 10
1   libsystem_info.dylib              0x00007fff8fab33a5 svc_run + 80
2   mtmfs                             0x000000010ec770ae 0x10ec6b000 + 49326
3   mtmfs                             0x000000010ec7a9d5 0x10ec6b000 + 63957
4   mtmfs                             0x000000010ec7a6aa 0x10ec6b000 + 63146
5   mtmfs                             0x000000010ec7b476 0x10ec6b000 + 66678
6   com.apple.Foundation              0x00007fff903e71ea -[NSThread main] + 68
7   com.apple.Foundation              0x00007fff903e7162 __NSThread__main__ + 1575
8   libsystem_c.dylib                 0x00007fff8edbf8bf _pthread_start + 335
9   libsystem_c.dylib                 0x00007fff8edc2b75 thread_start + 13
Thread 0 crashed with X86 Thread State (64-bit):
rax: 0x0000000000000000 rbx: 0x0000000000000006 rcx: 0x00007fff6e868858 rdx: 0x0000000000000000
rdi: 0x0000000000000707 rsi: 0x0000000000000006 rbp: 0x00007fff6e868880 rsp: 0x00007fff6e868858
   r8: 0x00007fff7627dfb8   r9: 0x00007fff6e8682e8 r10: 0x00007fff8a792d0a r11: 0xffffff80002d8240
r12: 0x00007fdb83d5cf20 r13: 0x00007fdb83d409d0 r14: 0x00007fff76280960 r15: 0x00007fff6e8689d0
rip: 0x00007fff8a792ce2 rfl: 0x0000000000000246 cr2: 0x000000010fdfc000
Logical CPU: 0
Binary Images:
       0x10ec6b000 -        0x10ecc2fff mtmfs (??? - ???) <3770CF18-35EF-3251-B5DA-6F71C4E06586> /System/Library/CoreServices/backupd.bundle/Contents/Resources/mtmfs
    0x7fff6e86b000 -     0x7fff6e89fac7 dyld (195.5 - ???) <4A6E2B28-C7A2-3528-ADB7-4076B9836041> /usr/lib/dyld
    0x7fff84d47000 -     0x7fff84dccff7 com.apple.Heimdal (2.1 - 2.0) <E4CD970F-8DE8-31E4-9FC0-BDC97EB924D5> /System/Library/PrivateFrameworks/Heimdal.framework/Versions/A/Heimdal
    0x7fff84dcd000 -     0x7fff84dcefff libunc.dylib (24.0.0 - compatibility 1.0.0) <C67B3B14-866C-314F-87FF-8025BEC2CAAC> /usr/lib/system/libunc.dylib
    0x7fff84e76000 -     0x7fff84e76fff com.apple.vecLib (3.7 - vecLib 3.7) <29927F20-262F-379C-9108-68A6C69A03D0> /System/Library/Frameworks/vecLib.framework/Versions/A/vecLib
    0x7fff855d2000 -     0x7fff8566cff7 com.apple.SearchKit (1.4.0 - 1.4.0) <B7573888-BAF6-333D-AB00-C0D2BF88DF0F> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/SearchKit.framework/Versions/A/SearchKit
    0x7fff8566d000 -     0x7fff85674fff com.apple.NetFS (4.0 - 4.0) <B9F41443-679A-31AD-B0EB-36557DAF782B> /System/Library/Frameworks/NetFS.framework/Versions/A/NetFS
    0x7fff85675000 -     0x7fff85877fff libicucore.A.dylib (46.1.0 - compatibility 1.0.0) <82DCB94B-3819-3CC3-BC16-2AACA7F64F8A> /usr/lib/libicucore.A.dylib
    0x7fff8590c000 -     0x7fff85910fff libmathCommon.A.dylib (2026.0.0 - compatibility 1.0.0) <FF83AFF7-42B2-306E-90AF-D539C51A4542> /usr/lib/system/libmathCommon.A.dylib
    0x7fff85912000 -     0x7fff85d3ffff libLAPACK.dylib (??? - ???) <4F2E1055-2207-340B-BB45-E4F16171EE0D> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libLAPACK.dylib
    0x7fff85d40000 -     0x7fff85d8bfff com.apple.SystemConfiguration (1.11 - 1.11) <0B02FEC4-C36E-32CB-8004-2214B6793AE8> /System/Library/Frameworks/SystemConfiguration.framework/Versions/A/SystemConfiguration
    0x7fff86a01000 -     0x7fff86a0fff7 libkxld.dylib (??? - ???) <65BE345D-6618-3D1A-9E2B-255E629646AA> /usr/lib/system/libkxld.dylib
    0x7fff86a10000 -     0x7fff86af0fff com.apple.CoreServices.OSServices (478.25.1 - 478.25.1) <E7FD4DB7-7844-355A-83D0-C1F24BE71019> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/OSServices.framework/Versions/A/OSServices
    0x7fff86bdc000 -     0x7fff86ce8fef libcrypto.0.9.8.dylib (0.9.8 - compatibility 0.9.8) <3AD29F8D-E3BC-3F49-A438-2C8AAB71DC99> /usr/lib/libcrypto.0.9.8.dylib
    0x7fff86cfc000 -     0x7fff86d66fff com.apple.framework.IOKit (2.0 - ???) <F79E7690-EF97-3D04-BA22-177E256803AF> /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit
    0x7fff86df1000 -     0x7fff86dfdfff com.apple.DirectoryService.Framework (10.7 - 144) <067ACB41-E9B7-3177-9EDE-C188D9B352DC> /System/Library/Frameworks/DirectoryService.framework/Versions/A/DirectoryService
    0x7fff86dfe000 -     0x7fff86e06fff libsystem_dnssd.dylib (??? - ???) <7749128E-D0C5-3832-861C-BC9913F774FA> /usr/lib/system/libsystem_dnssd.dylib
    0x7fff86e0c000 -     0x7fff86e12fff com.apple.DiskArbitration (2.4 - 2.4) <5185FEA6-92CA-3CAA-8442-BD71DBC64AFD> /System/Library/Frameworks/DiskArbitration.framework/Versions/A/DiskArbitration
    0x7fff88097000 -     0x7fff880aaff7 libCRFSuite.dylib (??? - ???) <034D4DAA-63F0-35E4-BCEF-338DD7A453DD> /usr/lib/libCRFSuite.dylib
    0x7fff880ab000 -     0x7fff883c4fff com.apple.CoreServices.CarbonCore (960.13 - 960.13) <398ABDD7-BB95-3C05-96D2-B54243FC4745> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonCore.framework/Versions/A/CarbonCore
    0x7fff883c5000 -     0x7fff883e2ff7 libxpc.dylib (77.16.0 - compatibility 1.0.0) <0A4B4775-29A9-30D6-956B-3BE1DBF98090> /usr/lib/system/libxpc.dylib
    0x7fff883e3000 -     0x7fff8840eff7 libxslt.1.dylib (3.24.0 - compatibility 3.0.0) <8051A3FC-7385-3EA9-9634-78FC616C3E94> /usr/lib/libxslt.1.dylib
    0x7fff8840f000 -     0x7fff88413fff libdyld.dylib (195.5.0 - compatibility 1.0.0) <F1903B7A-D3FF-3390-909A-B24E09BAD1A5> /usr/lib/system/libdyld.dylib
    0x7fff88ba1000 -     0x7fff88d74ff7 com.apple.CoreFoundation (6.7 - 635) <57446B22-0778-3E07-9690-96AC705D57E8> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
    0x7fff88e69000 -     0x7fff88e70fff libcopyfile.dylib (85.1.0 - compatibility 1.0.0) <172B1985-F24A-34E9-8D8B-A2403C9A0399> /usr/lib/system/libcopyfile.dylib
    0x7fff88f6a000 -     0x7fff88f6bfff libdnsinfo.dylib (395.6.0 - compatibility 1.0.0) <718A135F-6349-354A-85D5-430B128EFD57> /usr/lib/system/libdnsinfo.dylib
    0x7fff8964f000 -     0x7fff8964ffff libkeymgr.dylib (23.0.0 - compatibility 1.0.0) <61EFED6A-A407-301E-B454-CD18314F0075> /usr/lib/system/libkeymgr.dylib
    0x7fff89669000 -     0x7fff89696fe7 libSystem.B.dylib (159.0.0 - compatibility 1.0.0) <7B4D685D-939C-3ABE-8780-77A1889E0DE9> /usr/lib/libSystem.B.dylib
    0x7fff896c5000 -     0x7fff89828fff com.apple.CFNetwork (520.0.13 - 520.0.13) <67E3BB43-2A22-3F5A-964E-391375B24CE0> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CFNetwork.framework/Versions/A/CFNetwork
    0x7fff89b63000 -     0x7fff89ba9ff7 libcurl.4.dylib (7.0.0 - compatibility 7.0.0) <EAF61ADC-DC00-34CE-B23E-7238ED54E31D> /usr/lib/libcurl.4.dylib
    0x7fff8a14e000 -     0x7fff8a159ff7 com.apple.bsd.ServiceManagement (2.0 - 2.0) <5209B4F1-D6D6-337B-B3C8-E168931C778C> /System/Library/Frameworks/ServiceManagement.framework/Versions/A/ServiceManagement
    0x7fff8a2e6000 -     0x7fff8a334ff7 libauto.dylib (??? - ???) <F0004B88-CA01-37D0-A77F-6651C4EC7D8E> /usr/lib/libauto.dylib
    0x7fff8a335000 -     0x7fff8a368fff com.apple.GSS (2.1 - 2.0) <A150154E-40D3-345B-A92D-3A023A55AC52> /System/Library/Frameworks/GSS.framework/Versions/A/GSS
    0x7fff8a625000 -     0x7fff8a6bbff7 libvMisc.dylib (325.3.0 - compatibility 1.0.0) <AC5A384A-FA5A-3307-9CED-BD69E6F12A09> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libvMisc.dylib
    0x7fff8a6fe000 -     0x7fff8a715fff com.apple.CFOpenDirectory (10.7 - 144) <9709423E-8484-3B26-AAE8-EF58D1B8FB3F> /System/Library/Frameworks/OpenDirectory.framework/Versions/A/Frameworks/CFOpenDirectory.framework/Versions/A/CFOpenDirectory
    0x7fff8a77c000 -     0x7fff8a79cfff libsystem_kernel.dylib (1699.22.73 - compatibility 1.0.0) <69F2F501-72D8-3B3B-8357-F4418B3E1348> /usr/lib/system/libsystem_kernel.dylib
    0x7fff8a949000 -     0x7fff8aa27ff7 com.apple.DiscRecording (6.0 - 6000.4.1) <DB0D0211-953B-3261-A4FD-74D2AC671DA6> /System/Library/Frameworks/DiscRecording.framework/Versions/A/DiscRecording
    0x7fff8aa28000 -     0x7fff8aa3aff7 libsasl2.2.dylib (3.15.0 - compatibility 3.0.0) <6245B497-784B-355C-98EF-2DC6B45BF05C> /usr/lib/libsasl2.2.dylib
    0x7fff8aa3b000 -     0x7fff8aa74fe7 libssl.0.9.8.dylib (0.9.8 - compatibility 0.9.8) <D634E4B6-672F-3F68-8B6F-C5028151A5B4> /usr/lib/libssl.0.9.8.dylib
    0x7fff8be7c000 -     0x7fff8be8eff7 libbsm.0.dylib (??? - ???) <349BB16F-75FA-363F-8D98-7A9C3FA90A0D> /usr/lib/libbsm.0.dylib
    0x7fff8beb8000 -     0x7fff8bf2dff7 libc++.1.dylib (19.0.0 - compatibility 1.0.0) <C0EFFF1B-0FEB-3F99-BE54-506B35B555A9> /usr/lib/libc++.1.dylib
    0x7fff8bfc9000 -     0x7fff8bfcaff7 libremovefile.dylib (21.0.0 - compatibility 1.0.0) <C6C49FB7-1892-32E4-86B5-25AD165131AA> /usr/lib/system/libremovefile.dylib
    0x7fff8cbb3000 -     0x7fff8ccb6fff libsqlite3.dylib (9.6.0 - compatibility 9.0.0) <ED5E84C6-646D-3B70-81D6-7AF957BEB217> /usr/lib/libsqlite3.dylib
    0x7fff8d1ce000 -     0x7fff8d270ff7 com.apple.securityfoundation (5.0 - 55005) <0D59908C-A61B-389E-AF37-741ACBBA6A94> /System/Library/Frameworks/SecurityFoundation.framework/Versions/A/SecurityFoundation
    0x7fff8d4ee000 -     0x7fff8d5d2def libobjc.A.dylib (228.0.0 - compatibility 1.0.0) <C5F2392D-B481-3A9D-91BE-3D039FFF4DEC> /usr/lib/libobjc.A.dylib
    0x7fff8d5d3000 -     0x7fff8d72cff7 com.apple.audio.toolbox.AudioToolbox (1.7 - 1.7) <296F10D0-A871-39C1-B8B2-9200AB12B5AF> /System/Library/Frameworks/AudioToolbox.framework/Versions/A/AudioToolbox
    0x7fff8d83d000 -     0x7fff8d83eff7 libsystem_blocks.dylib (53.0.0 - compatibility 1.0.0) <8BCA214A-8992-34B2-A8B9-B74DEACA1869> /usr/lib/system/libsystem_blocks.dylib
    0x7fff8d893000 -     0x7fff8d8d5ff7 libcommonCrypto.dylib (55010.0.0 - compatibility 1.0.0) <A5B9778E-11C3-3F61-B740-1F2114E967FB> /usr/lib/system/libcommonCrypto.dylib
    0x7fff8d9be000 -     0x7fff8d9bffff libsystem_sandbox.dylib (??? - ???) <8D14139B-B671-35F4-9E5A-023B4C523C38> /usr/lib/system/libsystem_sandbox.dylib
    0x7fff8d9ea000 -     0x7fff8da09fff libresolv.9.dylib (46.0.0 - compatibility 1.0.0) <33263568-E6F3-359C-A4FA-66AD1300F7D4> /usr/lib/libresolv.9.dylib
    0x7fff8e182000 -     0x7fff8e194ff7 libz.1.dylib (1.2.5 - compatibility 1.0.0) <30CBEF15-4978-3DED-8629-7109880A19D4> /usr/lib/libz.1.dylib
    0x7fff8e1a8000 -     0x7fff8e21bfff libstdc++.6.dylib (52.0.0 - compatibility 7.0.0) <6BDD43E4-A4B1-379E-9ED5-8C713653DFF2> /usr/lib/libstdc++.6.dylib
    0x7fff8e292000 -     0x7fff8e569fff com.apple.security (7.0 - 55010) <2418B583-D3BD-3BC5-8B07-8289C8A5B43B> /System/Library/Frameworks/Security.framework/Versions/A/Security
    0x7fff8e68e000 -     0x7fff8e6cdfff com.apple.AE (527.6 - 527.6) <6F8DF9EF-3250-3B7F-8841-FCAD8E323954> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/AE.framework/Versions/A/AE
    0x7fff8e7ae000 -     0x7fff8e84dfff com.apple.LaunchServices (480.19 - 480.19) <41ED4C8B-C74B-34EA-A9BF-34DBA5F52307> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchServices.framework/Versions/A/LaunchServices
    0x7fff8ea40000 -     0x7fff8ea45ff7 libsystem_network.dylib (??? - ???) <4ABCEEF3-A3F9-3E06-9682-CE00F17138B7> /usr/lib/system/libsystem_network.dylib
    0x7fff8eb55000 -     0x7fff8ebbcff7 com.apple.audio.CoreAudio (4.0.0 - 4.0.0) <0B715012-C8E8-386D-9C6C-90F72AE62A2F> /System/Library/Frameworks/CoreAudio.framework/Versions/A/CoreAudio
    0x7fff8ed65000 -     0x7fff8ed70fff com.apple.CommonAuth (2.1 - 2.0) <49949286-61FB-3A7F-BF49-0EBA45E2664E> /System/Library/PrivateFrameworks/CommonAuth.framework/Versions/A/CommonAuth
    0x7fff8ed71000 -     0x7fff8ee4efef libsystem_c.dylib (763.11.0 - compatibility 1.0.0) <1D61CA57-3C6D-30F7-89CB-CC6F0787B1DC> /usr/lib/system/libsystem_c.dylib
    0x7fff8ee6b000 -     0x7fff8ef65ff7 com.apple.DiskImagesFramework (10.7.1 - 330.1) <83086D90-A613-30CC-95A7-ABF8B85BFDBF> /System/Library/PrivateFrameworks/DiskImages.framework/Versions/A/DiskImages
    0x7fff8f036000 -     0x7fff8f096fff libvDSP.dylib (325.3.0 - compatibility 1.0.0) <74B62E70-4189-3022-8FC9-1182EA7C6E34> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libvDSP.dylib
    0x7fff8f097000 -     0x7fff8f67bfaf libBLAS.dylib (??? - ???) <D62D6A48-5C7A-3ED6-875D-AA3C2C5BF791> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libBLAS.dylib
    0x7fff8f796000 -     0x7fff8f7a0ff7 liblaunch.dylib (392.18.0 - compatibility 1.0.0) <39EF04F2-7F0C-3435-B785-BF283727FFBD> /usr/lib/system/liblaunch.dylib
    0x7fff8f85e000 -     0x7fff8f863fff libpam.2.dylib (3.0.0 - compatibility 3.0.0) <D952F17B-200A-3A23-B9B2-7C1F7AC19189> /usr/lib/libpam.2.dylib
    0x7fff8f864000 -     0x7fff8f869fff libcache.dylib (47.0.0 - compatibility 1.0.0) <B7757E2E-5A7D-362E-AB71-785FE79E1527> /usr/lib/system/libcache.dylib
    0x7fff8f929000 -     0x7fff8f92efff com.apple.OpenDirectory (10.7 - 144) <E8AACF47-C423-3DCE-98F6-A811612B1B46> /System/Library/Frameworks/OpenDirectory.framework/Versions/A/OpenDirectory
    0x7fff8f92f000 -     0x7fff8f95efff com.apple.DictionaryServices (1.2 - 158) <2CE51CD1-EE3D-3618-9507-E39A09C9BB8D> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/DictionaryServices.framework/Versions/A/DictionaryServices
    0x7fff8f9a6000 -     0x7fff8fa16fff com.apple.datadetectorscore (3.0 - 179.3) <AFFBD606-91DE-3F91-8E38-C037D9FBFA8B> /System/Library/PrivateFrameworks/DataDetectorsCore.framework/Versions/A/DataDetectorsCore
    0x7fff8fa28000 -     0x7fff8fa51fff com.apple.CoreServicesInternal (113.7 - 113.7) <ACAC98CD-5941-39DB-951A-2509DCCD22FD> /System/Library/PrivateFrameworks/CoreServicesInternal.framework/Versions/A/CoreServicesInternal
    0x7fff8fa8d000 -     0x7fff8fac9fff libsystem_info.dylib (??? - ???) <BC49C624-1DAB-3A37-890F-6EFD46538424> /usr/lib/system/libsystem_info.dylib
    0x7fff8fe2a000 -     0x7fff8fe2afff com.apple.CoreServices (53 - 53) <5946A0A6-393D-3087-86A0-4FFF6A305CC0> /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices
    0x7fff8fe2b000 -     0x7fff8fe66fff com.apple.LDAPFramework (3.0 - 120.1) <0C23534F-A8E7-3144-B2B2-50F9875101E2> /System/Library/Frameworks/LDAP.framework/Versions/A/LDAP
    0x7fff8fe67000 -     0x7fff8fe68fff liblangid.dylib (??? - ???) <CACBE3C3-2F7B-3EED-B50E-EDB73F473B77> /usr/lib/liblangid.dylib
    0x7fff8fee6000 -     0x7fff8feecfff libmacho.dylib (800.0.0 - compatibility 1.0.0) <D86F63EC-D2BD-32E0-8955-08B5EAFAD2CC> /usr/lib/system/libmacho.dylib
    0x7fff902c2000 -     0x7fff902c4fff com.apple.TrustEvaluationAgent (2.0 - 1) <80AFB5D8-5CC4-3A38-83B9-A7DF5820031A> /System/Library/PrivateFrameworks/TrustEvaluationAgent.framework/Versions/A/TrustEvaluationAgent
    0x7fff90327000 -     0x7fff90343ff7 com.apple.GenerationalStorage (1.0 - 124) <C0290CA0-A2A0-3280-9442-9D783883D638> /System/Library/PrivateFrameworks/GenerationalStorage.framework/Versions/A/GenerationalStorage
    0x7fff9038d000 -     0x7fff9069ffff com.apple.Foundation (6.7 - 833.1) <618D7923-3519-3C53-9CBD-CF3C7130CB32> /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation
    0x7fff906ab000 -     0x7fff906b0fff libcompiler_rt.dylib (6.0.0 - compatibility 1.0.0) <98ECD5F6-E85C-32A5-98CD-8911230CB66A> /usr/lib/system/libcompiler_rt.dylib
    0x7fff90717000 -     0x7fff90819ff7 libxml2.2.dylib (10.3.0 - compatibility 10.0.0) <D46F371D-6422-31B7-BCE0-D80713069E0E> /usr/lib/libxml2.2.dylib
    0x7fff9081a000 -     0x7fff9083eff7 com.apple.Kerberos (1.0 - 1) <2FF2569B-F59A-371E-AF33-66297F512CB3> /System/Library/Frameworks/Kerberos.framework/Versions/A/Kerberos
    0x7fff9083f000 -     0x7fff9084dfff com.apple.NetAuth (1.0 - 3.0) <F384FFFD-70F6-3B1C-A886-F5B446E456E7> /System/Library/PrivateFrameworks/NetAuth.framework/Versions/A/NetAuth
    0x7fff9085e000 -     0x7fff908a2ff7 com.apple.MediaKit (11.0 - 585) <8F2DF50A-03D2-3551-AD92-74A9262D6B0F> /System/Library/PrivateFrameworks/MediaKit.framework/Versions/A/MediaKit
    0x7fff908a3000 -     0x7fff908a5fff libquarantine.dylib (36.0.0 - compatibility 1.0.0) <4C3BFBC7-E592-3939-B376-1C2E2D7C5389> /usr/lib/system/libquarantine.dylib
    0x7fff908a6000 -     0x7fff908a7fff libDiagnosticMessagesClient.dylib (??? - ???) <3DCF577B-F126-302B-BCE2-4DB9A95B8598> /usr/lib/libDiagnosticMessagesClient.dylib
    0x7fff90c64000 -     0x7fff90c71ff7 libbz2.1.0.dylib (1.0.5 - compatibility 1.0.0) <8EDE3492-D916-37B2-A066-3E0F054411FD> /usr/lib/libbz2.1.0.dylib
    0x7fff90d3a000 -     0x7fff90d40ff7 libunwind.dylib (30.0.0 - compatibility 1.0.0) <1E9C6C8C-CBE8-3F4B-A5B5-E03E3AB53231> /usr/lib/system/libunwind.dylib
    0x7fff91351000 -     0x7fff9135cff7 libc++abi.dylib (14.0.0 - compatibility 1.0.0) <8FF3D766-D678-36F6-84AC-423C878E6D14> /usr/lib/libc++abi.dylib
    0x7fff9135d000 -     0x7fff91366fff libnotify.dylib (80.0.0 - compatibility 1.0.0) <BD08553D-8088-38A8-8007-CF5C0B8F0404> /usr/lib/system/libnotify.dylib
    0x7fff9137c000 -     0x7fff913fefff com.apple.Metadata (10.7.0 - 627.9) <F293A9A7-9790-3629-BE81-D19C158C5EA4> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Metadata.framework/Versions/A/Metadata
    0x7fff913ff000 -     0x7fff9140dfff libdispatch.dylib (187.5.0 - compatibility 1.0.0) <698F8EFB-7075-3111-94E3-891156C88172> /usr/lib/system/libdispatch.dylib
External Modification Summary:
Calls made by other processes targeting this process:
    task_for_pid: 5
    thread_create: 0
    thread_set_state: 0
Calls made by this process:
    task_for_pid: 0
    thread_create: 0
    thread_set_state: 0
Calls made by all processes on this machine:
    task_for_pid: 843
    thread_create: 0
    thread_set_state: 0
VM Region Summary:
ReadOnly portion of Libraries: Total=92.2M resident=42.3M(46%) swapped_out_or_unallocated=49.9M(54%)
Writable regions: Total=47.4M written=652K(1%) resident=2084K(4%) swapped_out=0K(0%) unallocated=45.3M(96%)
REGION TYPE                      VIRTUAL
===========                      =======
MALLOC                             20.5M
MALLOC guard page                    32K
STACK GUARD                        56.0M
Stack                              10.5M
VM_ALLOCATE                          36K
__DATA                             19.7M
__LINKEDIT                         47.1M
__TEXT                             45.1M
__UNICODE                           544K
mapped file                        15.5M
shared memory                       312K
===========                      =======
TOTAL                             215.3M

nuts

Similar Messages

Mount failed for usb3.0 pen drive on MBP Retina

I have 32GB pen drive, trying to connect it to MBP Retina.
OS version is the newest one.
Pendrive works great with Windows 7 and WD HD Live.
Tried to format pendrive with all available file systems (from Fat32, exFat, MacOS Extended) - and format works OK.
DiskUtility see the pendrive without any issues, but can not mount.
Following error appears:
- the disk could not be mounted. Try running First Aid on the disk and the retry mounting.
Verify Disk and Repair Disk completes without issues, but pendrive is still can not be mount.

I was having this problem with the exact same USB drive (Lexar USB 3.0 32GB) and an early 2011 Macbook pro. I tried EVERYTHING to make it work: most of the things you did including resetting the PRAM and the SMC and tried every kind of formatting (Mac Journaled, exFat, Fat32....), I tried every port on my laptop, I cleaned the contacts.... nothing worked. It was working on a friend's newer Macbook, and on my roommate's brand new windows desktop. However, on my computer It wasn't showing up in Finder or in Disk Utility no matter what I did.
I then read this comment on another forum: "Likely the problem is the USB 3.0 plug going into a USB 2.0 socket. Move it back and forth a bit and it should connect. For me this works every time."
And it works. I just have to move the USB drive slightly away from my screen and presto. I am not sure how great this is for the USB port itself but I have decided to sacrifice one USB port to using my thumb drive because I need it every day.
I too spent hours trying to resolve this and this was the solution, and it's been working for months.

Solaris 10 upgrade fails with "mount failed"

I'm trying to upgrade an aged Ultra 80 to Solaris 10u9 (from Solaris 10u2 or so), so that it can be used for our product testing purposes. After several unsuccessful attempts, I finally freed up enough space on the / filesystem (5.2GB free) by moving /opt to a newly installed second drive.
However, the upgrade now fails with
"Mount failed for either root, swap, or other file system.
Pfinstall failed. Exit stat= java.lang.UNIXProcess@e2892b 2"
At the end of the log file it says
"Checking c0t0d0s0 for an upgradeable Solaris image.
ERROR: Mount failed for either root, swap, or other file system."
I'm stumped. It doesn't say which file system it's having problems with.
Any ideas as to how to troubleshoot this problem, or what the cause might be? At 30 minutes per upgrade attempt, I'd like to know what the cause is rather than pursuing trial and error.
Thanks.

Look at your "vfstab" and see if there are any mounts that need a specific driver like a SAN-provided LUN. Comment them out during the upgrade for the upgrade tries to mount everything in your /etc/vfstab and if it doesn't have the driver/software to do it, it will fail...

"Mounting Failed" - downloaded driver for HP deskjet 6980

I downloaded the printer driver for my HP deskjet 6980 and when it finished downloading it said that mounting failed. Why would this be?

Hi Kat,
Either a RAM/Hardware issue, Disk needs Repair, or some glith in downloading.
Safe Boot , (holding Shift key down at bootup), off the HD & use Disk Utility from there to Repair Permissions, reboot once more.

BizTalk Powershell Provider Mount remote BizTalk drive: Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'

I've been dabbling in the Powershell BizTalk Provider Extensions for some automation of deployment and such. So far it's pretty cool on a local machine, but the real benefits to me would be to do it remotely. Does anyone have any experience in the with the
following issue?
My BizTalk Server and SQL Servers are on separate machines which I think is the issue, but I don't know how to resolve. I've tried to provided credentials to the New-PSDrive command, but get the following errors:
The provider does not support the use of credentials. Perform the operation again without specifying credentials.
I'm trying to manage a remote BizTalk instance. The machine running the script has biztalk fully configured and can connect
to the Target Server just fine. The issue comes when I try to mount the "BizTalk:" drive
Enter-pssession -computername myServer -configurationname microsoft.powershell32
$InitializeDefaultBTSDrive = $false;
Remove-PSSnapin -Name BizTalkfactory.PowerShell.Extensions;
Add-PSSnapin -Name BizTalkfactory.PowerShell.Extensions;
New-PSDrive -Name BizTalk -PSProvider BizTalk -Root "BizTalk:\" -Instance mySqlServer -Database BizTalkMgmtDb -Scope Global
When it get to the New-PSDrive I get the following error:
New-PSDrive : Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.
+ CategoryInfo : InvalidArgument: (BizTalk:PSDriveInfo) [New-PSDrive], BtsException
+ FullyQualifiedErrorId : 0,Microsoft.PowerShell.Commands.NewPSDriveCommand
Has anyone experienced this and solved? The same error occurs when use Invoke-Command as well.

It seems that the PowerShell provider is not Microsoft Support, it is community supported through the CodePlex site -
http://psbiztalk.codeplex.com
Right, I posted there as well, but there is not much movement on the site. I was hoping to find if this larger community may have had some experience with the provider.

VolumeMediaFormat upgrade for volume failed. Status 20888

Hello All;
I have 2 x OES 11 SP2 with NCS servers with the latest updates. These servers are virtuialized on a SLES 11 SP3 with KVM
Following the Docs on putting DHCP on a NCS with NSS volumes
https://www.novell.com/documentation...a/bbe81cc.html
Installing and Configuring a Cluster 8.3.3
Step 9
9. To hardlink, enable the shared volume on which the dhcpd.conf and dhcpd.leases files are hosted eg.DHCPVOL.
Invoke nsscon in the linux terminal and execute the following commands:
/ZLSSUpgradeCurrentVolumeMediaFormat=VolName
/hardlinks=VolName
in doing the first command, I receive
nss /ZLSSUpgradeCurrentVolumeMediaFormat=VOL1
VolumeMediaFormat upgrade for volume "VOL1" failed. Status = 20888.
The second command states the first command must be done.
nss /hardlinks=Vol1
Hardlinks may not be created on volume "vol1" until it is upgraded using the "ZLSSUpgradeCurrentVolumeMediaFormat" command...
I can offline, online, migrate the pool (with a single volume) between the 2 servers with no issues.
I have checked the nss and ncs modules on the 2 SLES 11 SP3 servers and they are exactly the same.
using nsscon, I can see the _ADMIN and VOL1 volumes. The _ADMIN has the hardlink attribute. So why does VOl1 not upgrade the media format? And what must be done to make this command work?
I cannot continue until this step is fully completed.
Thank you.

>>> So why does VOl1 not upgrade the media format?
Because we believe there is still a node is not fully upgraded to OES11 SP2. Volume upgrade cannot proceed until all nodes are capable of understanding the new media format.
>>> And what must be done to make this command work?
1. Run "sbdutil -v" on one node to check SBD signatures of all nodes.
The signature for all slots should be
"SBD*"
If some of them have "SBD+" (or other signatures), that's the cause of the problem.
2. Make sure those nodes are really on OES11 SP2, or no longer a participant of the cluster.
3. Run command "sbdutil -i" on one of the nodes to update all signatures.
You can do all of the above while NCS is running. You can now try to upgrade the volume without restarting anything.
Best regards,
Changju

Can't get around "mount failed" - "on error" won't do it - help appreciated

Hi
I'm using this syntax to mount a volume, and it works well if the volume can in fact be mounted:
try
mount volume "afp://username:[email protected]/MyDir"
on error
display dialog "blah blah"
end try
BUT, if the volume can't be mounted because the directory specified is incorrect, I a dialog saying "Mount Failed" opens with the only option being 'OK'. Under some other mount failure circumstances this dialog doesn't appear, and the script does eventually time out and disappear all by itself. But if this dialog appears, I have no option other than to manually press OK. It stays open forever. This dialog appears before the script passes the error to the display dialog part, so it prevents the "on error" part of the script from running. This is the only example I know of where 'on error' fails to let the scripter move on and manage the error.
What I would really like to do is to get the 'on error' functionality to actually work properly, because I can determine the PID of the process using Terminal and could then kill it using a shell script if , BUT none of this is possible because the script never gets to the 'on error' state because a real human must press the dialog's OK. I can't seem to use system events to send anything to it because the whole applescript just hangs at this point until the OK is checked.
Does anyone know a workaround? I've tried using a with timeout step around the whole thing but also won't work.
Thanks for any advice you could give me.
Chris.

I'm having the same trouble, but for different reasons. I was trying to determine a method for examining all the mounted volumes on my desktop and then detecting which mounted volume came from which network server. There doesn't seem to be any way to determine this via any filesystem metadata or anything. The only solution that I could think of was to build an afp url for each server/volume combination for any given mounted volume I wanted to test and then try mount volume on each url (thinking that the on error handler would trap the errors and then I could branch accordingly). Doesn't work. It's interesting that if you try mount volume afp://validerserver/badvolume, you get the mount failed error before your on error handler kicks in. If you try mount volume afp://badserver/validvolume, the on error handler fields the resulting -35 error. If you try mount volume afp://emptystring, you get a connection failed dialog before the on error handler again. Really annoying.
I filed a bug on this.

Problem: Mount Failed

Whenever I launch iPhoto 7.0.1 I get the following message:
Mount Failed.
Could not mount volume "My Book".
If I click "OK" The message pops up again over and over untill I quit iPhoto
My Book is å WD My Book Pro connected via Airport Extreme.... or it WAS connected... it no longer works. No pictures from the library were stored on the disc. I tried deleting iPhoto and airport disk util's plist files. I also moved the library, so iPhoto would not find it. After doing all these things, and rebooting, I still have the problem (with a new library w/o any photos!)
The problem is user spesific; other users are not affected.
Any help would be appreciated

Thanks for the tip. I had the same problem and indeed it was fixed by removing aliases to disk images from my User >Movies folder. However, I need those aliases there in order to access different disk images for viewing movies using the menu system in Front Row with the remote control on my iMac. Hopefully Apple will release a fix for this. Can anyone think of a workaround in the meantime?

Backup too large for volume

I have 2 macbook pro's (120GB & 160GB) backing up to a 500GB TM.
both were backing up just fine, however in the past month the 160GB
macbook pro keeps getting this message.....
"backup too large for volume?"
and subsequently the backup fails?
the size of the backup is less than the free space on the TM drive...
any help?

dave,
*_Incremental Backups Seem Too Large!_*
Open the Time Machine Prefs on the Mac in question. How much space does it report you have "Available"? When a backup is initiated how much space does it report you need?
Now, consider the following, it might give you some ideas:
Time Machine performs backups at the file level. If a single bit in a large file is changed, the WHOLE file is backed up again. This is a problem for programs that save data to monolithic virtual disk files that are modified frequently. These include Parallels, VMware Fusion, Aperture vaults, or the databases that Entourage and Thunderbird create. These should be excluded from backup using the Time Machine Preference Exclusion list. You will, however, need to backup these files manually to another external disk.
One poster observed regarding Photoshop: “If you find yourself working with large files, you may discover that TM is suddenly backing up your scratch disk's temp files. This is useless, find out how to exclude these (I'm not actually sure here). Alternatively, turn off TM whilst you work in Photoshop.” [http://discussions.apple.com/thread.jspa?threadID=1209412]
If you do a lot of movie editing, unless these files are excluded, expect Time Machine to treat revised versions of a single movie as entirely new files.
If you frequently download software or video files that you only expect to keep for a short time, consider excluding the folder these are stored in from Time Machine backups.
If you have recently created a new disk image or burned a DVD, Time Machine will target these files for backup unless they are deleted or excluded from backup.
*Events-Based Backups*
Time Machine does not compare file for file to see if changes have been made. If it had to rescan every file on your drive before each backup, it would not be able to perform backups as often as it does. Rather, it looks for EVENTS (fseventsd) that take place involving your files and folders. Moving/copying/deleting/saving files and folders creates events that Time Machine looks for. [http://arstechnica.com/reviews/os/mac-os-x-10-5.ars/14]
Installing new software, upgrading existing software, or updating Mac OS X system software can create major changes in the structure of your directories. Every one of these changes is recorded by the OS as an event. Time Machine will backup every file that has an event associated with it since the installation.
Files or folders that are simply moved or renamed are counted as NEW files or folders. If you rename any file or folder, Time Machine will back up the ENTIRE file or folder again no matter how big or small it is.
George Schreyer describes this behavior: “If you should want to do some massive rearrangement of your disk, Time Machine will interpret the rearranged files as new files and back them up again in their new locations. Just renaming a folder will cause this to happen. This is OK if you've got lots of room on your backup disk. Eventually, Time Machine will thin those backups and the space consumed will be recovered. However, if you really want recover the space in the backup volume immediately, you can. To do this, bring a Finder window to the front and then click the Time Machine icon on the dock. This will activate the Time Machine user interface. Navigate back in time to where the old stuff exists and select it. Then pull down the "action" menu (the gear thing) and select "delete all backups" and the older stuff vanishes.” (http://www.girr.org/mac_stuff/backups.html)
*TechTool Pro Directory Protection*
This disk utility feature creates backup copies of your system directories. Obviously these directories are changing all the time. So, depending on how it is configured, these backup files will be changing as well which is interpreted by Time Machine as new data to backup. Excluding the folder these backups are stored in will eliminate this effect.
*Backups WAY Too Large*
If an initial full backup or subsequent incremental backup is tens or hundreds of Gigs larger than expected, check to see that all unwanted external hard disks are still excluded from Time Machine backups.
This includes the Time Machine backup drive ITSELF. Normally, Time Machine is set to exclude itself by default. But on rare occasions it can forget. When your backup begins, Time Machine mounts the backup on your desktop. (For Time Capsule users it appears as a white drive icon labeled something like “Backup of (your computer)”.) If, while it is mounted, it does not show up in the Time Machine Prefs “Do not back up” list, then Time Machine will attempt to back ITSELF up. If it is not listed while the drive is mounted, then you need to add it to the list.
*FileVault / Boot Camp / iDisk Syncing*
Note: Leopard has changed the way it deals with FileVault disk images, so it is not necessary to exclude your Home folder if you have FileVault activated. Additionally, Time Machine ignores Boot Camp partitions as the manner in which they are formatted is incompatible. Finally, if you have your iDisk Synced to your desktop, it is not necessary to exclude the disk image file it creates as that has been changed to a sparsebundle as well in Leopard.
If none of the above seem to apply to your case, then you may need to attempt to compress the disk image in question. We'll consider that if the above fails to explain your circumstance.
Cheers!

Mounting remote AFP volumes on Panther Server from Tiger client.

Has anyone else had this problem....
When connecting to a remote AFP share hosted on a Mac OS X 10.3.9 server I receive a message "Mount Failed, Could not mount volume “sharename.”. This happens when I enter the FQDN followed by the share name, for example "afp://servername.domain.co.uk/sharepoint". The client is part of an Open Directory domain and automounts work fine during boot as the home directory sharepoint works with local and remote homes. I have setup many 10.3.9 servers and have never encountered this issue on a Panther client.
Any help would be much appreciated and its driving me to distraction!
Regards
James.

We are not using the server for users' home directories, but thanks for that tip.
Today we have also started having issues at another site with a 10.3.8 server and Tiger clients. The behavior is a little different: when connecting to the Pather server with Tiger clients using a keychain-saved password, the client machine will freeze and must be rebooted. The server is showing no process crashes. Deleting the keychain and entering the password each time fixes the problem.
At the other site, the server is 10.3.9 and when Tiger clients tried to connect using a keychain password, their machine would get a spinning beach ball, but they could get out of it.

Unable to reconnect afp share - "sosend failed for request" error

I use rsync to synchronize an Xserve G5 (2 x2 Ghz - Mac OS X 10.3.9) from a Windows 2000 Server.
I use a script to reconnect a network share hosted by the w2k server. today system.log indicates the following lines :
Jan 11 11:53:19 XserveStudio kernel: AFP_VFS afpfs UserCommand: sosend failed for request 32
Jan 11 11:53:19 XserveStudio kernel: AFP_VFS afpfs_Reconnect started /Volumes/Studio
Jan 11 11:53:19 XserveStudio kernel: AFP_VFS afpfs_Reconnect: Wrong version 4 or no more attempts 0
I am unable to remount the share with the Finder but I can mount another share of the same server
Any idea ?
Xserve G5 2 x 2Ghz Mac OS X (10.3.9)

i had a similar problem the other day at a client's office. the solution seemed to be to remove a faulty switch between the workstation and the server.
connecting the cat5 directly to an available wall jack allowed the user to reconnect right away. before that, she was unable to reconnect after getting disconnected, and the Finder would hang, rendering the Mac useless.
how does your script connect to the server? do you explicitly use afp://... or some other syntax?

How do I connect to a Windows Workgroup and mount a shared volume?

I have set up a network at home with my Mac G5 and my PC. I have a workgroup called "HOME". The PC can see my mac drive as a network place and I can access and browse it perfectly fine.
However I have a drive on my PC which I have set up as a shared volume on the PC. I want to mount that shared volume on my Mac. When I set up the share on the PC, I am not prompted to enter a password, and the only password I am aware of is the one I use to log on.
According to the instructions I am supposed to enter the IP address and a "sharename", but I have no idea what the sharename is. If I enter the share name of the volume I want to mount, I get a dialog box which requires a password. It sees the "HOME" workgroup and that is already filled out in the Workgroup window.
It has entered my Mac administrator account name in the Name box. I don't know if this is what name it needs, but what ever combination of names and passwords I use, including my PC logon name and password, I always get the error message "cannot connect because the name or password is not correct".
I have tried using different formats for the smb://Servername/sharename address, but everything I have tried gives the same result.
I have seen many other postings on this subject, all with similar problems, but so far I've yet to see an answer. A disscussion from 2004 said this was a known issue, but surely there must have been a fix by now?
I have read many of the mac documents on this subject but none specifically tells you what the sharename is and how you set a password for it.
Thanks in advance
David

OK - I have answered my own question, so if anyone else has this problem, you may like to know!
I needed to know what sharename to use to log on. On the Windows PC I was under the imprression that the windows log on was my user name. But if you right click on the My Computer and go to manage, you will see Local Users and Groups. Under Users, you will see all the user accounts on the PC. Even though I only ever set up one and it was called "David" that doesn't actually count as the user name.
If you look at the headings at the top, you will see that whatever account you think you are in, the chances are it actually has the name "User". It is what ever is in the Name column that the Mac needs, not what is in the Full Name column which is what you log on as. You can't change this, but when you connect to server, you can enter the SMB script smb://USER@(name of PC or IP address)/share name.
If you wish to mount a volume rather than a shared folder, simply type in the windows drive letter followed by the "$" - ie D$. The password is your log on password on the PC. Otherwise you can set up a folder share on the PC in the usual way, and give it a name. This will be the share name you enter in your smb script.
NONE of this is very clear in any of the Mac Networking Help guides that I have trawled through, so if they were to add it, you might help some more people...
Thanks,
David
G5 Mac OS X (10.4.6)

An error has occurred during report processing. (rsProcessingAborted). Query execution failed for dataset 'DimUserWorkCentre'. (rsErrorExecutingCommand). The Cube either does not exists or has not been processed

Hi,
I'm having issues with the report created using SSAS cube.
An error has occurred during report processing. (rsProcessingAborted)
Query execution failed for dataset 'DimUserWorkCentre'. (rsErrorExecutingCommand)
The Operator_Performance cube either does not exist or has not been processed.
I have searched through internet and tried all the solutions, but didn't worked for me.
SSRS services running as NETEWORK SERVICE user.
SSRS Execution running as a Different user, which is the login is used to logon ot that server. I have also verified this user has access to database. I'm using Shared DataSource(SSAS Source) for this report.
Can any one please help me.
Thank You,
Praveen.
Praveen

Hello,
Have you tried it to execute on report manager , Is your data source properly configured in Report Manager and your report is mapped with Datset correctly?
Have you executed the Dataset query MDX editor now?
What is the volume of data you are fetching in the report. Try it to execute in other than IE , I don't know the exact reason but some of our report with large volume of data are failing on IE , on the other hand these reports are running fine Google
Chrome
blog:My Blog/
Hope this will help you !!!
Sanjeewan

Finding rack mount kit for Cisco SF300-48P

I have a 10/100 POE managed switch laying around that I wanted to rack up to use for my VoIP phones. I however, had since lost the mounts (or never had them to begin with).
I've been looking all darn day for mounts just for this. It doesn't seem to fit any other of the 10,000 or so rack kits I have in house.
So far google and Ebay have been failing me. Everyone wants to sell me a darn switch, and I have that. I just want the bloody ears gosh darnit.
Can someone please, send me a model number I can search for on Amazon or Ebay to grab them?
Cheers,
Mike

If you are in the UK you could try ringing hardware.com.
They have supplied me with 'cisco-compatable' rackmount kits in the past at a fraction of the price of the genuine article.
Worth a shot.

Leopard (10.5) error: " EXCEPTION: Reverification failed for..."

I went on the road for a week (while I'm on the road PHDs don't sync) and when I returned and tried to sync my changes I'm getting all sorts of errors. Some errors seem to have cleared themselves up after several sync (which is bothering in and of itself) however I'm getting persistent errors that are called "reverification" errors (see below). Does anyone have any idea what these errors mean???? By the way these files are not getting sync'ed, yet I'm not getting any messages popping up to the user, the only way I even noticed is because after the first sync some files where still the old copies on the server, I had to go to the logs to try to find the errors.
Here's an example of just one:
0:: [2007/11/13 11:25:24.102] EXCEPTION: Reverification failed for "/Users/ramos-m/Documents/NoteTaker-NoteShare/Backup/Backup of people.ntx/Book.plist" on store HomeSync_Mirror-L-yvUOtsqmAt7-ramos-m (Object modified) <-[SStoreFileOperator_FS reverify] (StoreFileOperator-FS.m:654): "THROW(Reverification failed for "/Users/ramos-m/Documents/NoteTaker-NoteShare/Backup/Backup of people.ntx/Book.plist" on store HomeSync_Mirror-L-yvUOtsqmAt7-ramos-m (Object modified))">
0:: [2007/11/13 11:25:24.102] BACKTRACE: {
0:: [2007/11/13 11:25:24.102] ? | 0x4f0af
0:: [2007/11/13 11:25:24.102] ? | 0x4999b
0:: [2007/11/13 11:25:24.102] ? | 0x6893a
0:: [2007/11/13 11:25:24.102] ? | 0x53d76
0:: [2007/11/13 11:25:24.102] ? | 0x4804f
0:: [2007/11/13 11:25:24.102] ? | 0x47ace
0:: [2007/11/13 11:25:24.102] ? | 0x53929
0:: [2007/11/13 11:25:24.102] ? | 0x3132e
0:: [2007/11/13 11:25:24.102] ? | 0x30c65
0:: [2007/11/13 11:25:24.102] ? | 0x47a6a
0:: [2007/11/13 11:25:24.102] ? | 0x478d6
0:: [2007/11/13 11:25:24.102] ? | 0x158be
0:: [2007/11/13 11:25:24.102] ? | 0x9201b04d
0:: [2007/11/13 11:25:24.102] ? | 0x9201abf4
0:: [2007/11/13 11:25:24.102] ? | 0x96191075
0:: [2007/11/13 11:25:24.102] }
0:: [2007/11/13 11:25:24.102] <ERROR> network: MODIFY ./Book.plist (-[SStoreFileOperator_FS reverify] (StoreFileOperator-FS.m:654): "THROW(Reverification failed for "/Users/ramos-m/Documents/NoteTaker-NoteShare/Backup/Backup of people.ntx/Book.plist" on store HomeSync_Mirror-L-yvUOtsqmAt7-ramos-m (Object modified))")
0:: [2007/11/13 11:25:24.134] <ERROR> network: PACKAGE MODIFY "Documents/NoteTaker-NoteShare/Backup/Backup of people.ntx" {(Priority=1, EXECUTING)} (-[SStoreFileOperator_FS reverify] (StoreFileOperator-FS.m:654): "THROW(Reverification failed for "/Users/ramos-m/Documents/NoteTaker-NoteShare/Backup/Backup of people.ntx/Book.plist" on store HomeSync_Mirror-L-yvUOtsqmAt7-ramos-m (Object modified))")

Thanks for the input, this was helpful, however problem still not solved. This is very ugly if you ask me and very disappointing as PHDs have seem to have been nothing but problematic forever.
Yesterday I took a different approach to try to clear this particular problem. I manually mounted the AFP share and then one by one for each of the files that I was getting errors on, I copied the newer file over the older file.
To make matters worse, when I was comparing the files I noticed other files in the same directory that were out of sync and had NOT been generating errors. In other words these files had been silently not updating!!!! So I copied these files as well, but some had to go up to the server and some ad to go down.
Then a ran a manual sync. Interestingly I got conflicts that I had to resolve on the files that had been getting the errors, even though they were now the exact same file. The info for the file, displayed in the conflict resolution window, was the old file info even though that info was no longer correct since the two files now matched.
So I just tried your advice and took one folder that had in it both files that some were updating and that some were not updating and renamed the folder. I then ran a manual resync. At the end of the sync, basically all FileSyncAgent had done was copy the older named folder from the server to the local copy and the local newer named folder up to the server. So I now have TWO copies of ALL the data in BOTH places. However, that doesn't help much as I'm still going to have to go through and find the latest copies of all the files and over write the older copies, basically the same thing I did yesterday.
To further complicate things, as I've been typing this, another sync kicked off and during that sync it tried to move files from the older folder to the newer named folder, but gave me "Directory Not Empty" errors.
This is so frustrating. At this point I have no idea how many files are out of sync or what the best way to fix this is.

Mtmfs: mount failed for /Volumes/MobileBackups 9

Similar Messages

Maybe you are looking for