Error: mdworker lsboxd deny mach-lookup

Getting the following, every 5 min, in Console.
9/25/12 10:35:21.415 AM mdworker[503]: Unable to talk to lsboxd
9/25/12 10:35:21.419 AM mdworker[504]: Unable to talk to lsboxd
9/25/12 10:35:21.474 AM sandboxd[505]: ([503]) mdworker(503) deny mach-lookup com.apple.ls.boxd
9/25/12 10:35:21.480 AM sandboxd[505]: ([504]) mdworker(504) deny mach-lookup com.apple.ls.boxd

I'm seeing the same issue and I think it started after the 10.8.2 update on my 2012 MBP (not retina). I usually do a command-option-eject to put the machine to sleep when I leave work at night but the last three mornings when I get back to work the MBP will not wake up and I have to hold the power button to force it off. The console is full of the following messages, even during the time when it should have been sleeping:
Sep 25 00:18:55 kernel[0]: Sandbox: sandboxd(3819) deny mach-lookup com.apple.coresymbolicationd
Sep 25 00:20:56 mdworker[3822]: Unable to talk to lsboxd
Sep 25 00:20:56 mdworker[3823]: Unable to talk to lsboxd
Sep 25 00:20:56 kernel[0]: Sandbox: sandboxd(3824) deny mach-lookup com.apple.coresymbolicationd
Sep 25 00:20:56 sandboxd[3824] ([3822]): mdworker(3822) deny mach-lookup com.apple.ls.boxd
Sep 25 00:20:56 sandboxd[3824] ([3823]): mdworker(3823) deny mach-lookup com.apple.ls.boxd
Also, when re-start it indexes my external Time Machine hard drive for what seems like hours - never used to do that.

Similar Messages

  • Problem: mdworker(20190) deny mach-lookup com.apple.ls.boxd

    Hey guys,
    since a while now, the macbook pro freeze and the mouse switch to this cycle (using firefox)...
    Here are the entries of the console after the freeze.
    08.12.12 12:40:16,467 sandboxd[20205]: ([20190]) mdworker(20190) deny mach-lookup com.apple.ls.boxd
    mdworker(20190) deny mach-lookup com.apple.ls.boxd
    Process:         mdworker [20190]
    Path:            /System/Library/Frameworks/CoreServices.framework/Frameworks/Metadata.framework /Versions/A/Support/mdworker
    Load Address:    0x10399d000
    Identifier:      mdworker
    Version:         ??? (???)
    Code Type:       x86_64 (Native)
    Parent Process:  launchd [447]
    Date/Time:       2012-12-08 12:40:16.346 +0100
    OS Version:      Mac OS X 10.8.2 (12C60)
    Report Version:  8
    Thread 0:
    0   libsystem_kernel.dylib            0x00007fff84270686 mach_msg_trap + 10
    1   CoreFoundation                    0x00007fff8ec8d803 __CFRunLoopServiceMachPort + 195
    2   CoreFoundation                    0x00007fff8ec92ee6 __CFRunLoopRun + 1078
    3   CoreFoundation                    0x00007fff8ec926b2 CFRunLoopRunSpecific + 290
    4   CoreFoundation                    0x00007fff8eca1371 CFRunLoopRun + 97
    5   mdworker                          0x00000001039a5ba9
    6   libdyld.dylib                     0x00007fff852b97e1 start + 0
    Thread 1:
    0   libsystem_c.dylib                 0x00007fff85220eeb tiny_free_list_add_ptr + 378
    1   libsystem_c.dylib                 0x00007fff85219f12 szone_free + 2094
    2   libdispatch.dylib                 0x00007fff8da48695 _dispatch_cache_cleanup + 30
    3   libdispatch.dylib                 0x00007fff8da4a0ba _dispatch_mgr_thread2 + 61
    4   libdispatch.dylib                 0x00007fff8da49afd _dispatch_mgr_invoke + 134
    5   libdispatch.dylib                 0x00007fff8da499ee _dispatch_mgr_thread + 54
    Thread 2:
    0   libsystem_kernel.dylib            0x00007fff842706c2 semaphore_wait_trap + 10
    1   libxpc.dylib                      0x00007fff82ff5e1f xpc_connection_send_message_with_reply_sync + 127
    2   LaunchServices                    0x00007fff8db033ce send(LSBoxMessage&, LSBoxMessage&) + 28
    3   LaunchServices                    0x00007fff8db83d4b lsbox_preflightAppLaunch + 84
    4   LaunchServices                    0x00007fff8db0e341 _LSFindOrRegisterBundleNode + 857
    5   LaunchServices                    0x00007fff8db6ab02 _LSRegisterNode + 75
    6   LaunchServices                    0x00007fff8db16a0f _LSBundleCopyOrCheckNode + 1047
    7   LaunchServices                    0x00007fff8dafe5b6 _LSCopyLibraryItemURLs + 486
    8   mdworker                          0x00000001039cd014
    9   libdispatch.dylib                 0x00007fff8da4af01 _dispatch_call_block_and_release + 15
    10  libdispatch.dylib                 0x00007fff8da470b6 _dispatch_client_callout + 8
    11  libdispatch.dylib                 0x00007fff8da4847f _dispatch_queue_drain + 235
    12  libdispatch.dylib                 0x00007fff8da482f1 _dispatch_queue_invoke + 52
    13  libdispatch.dylib                 0x00007fff8da481c3 _dispatch_worker_thread2 + 249
    14  libsystem_c.dylib                 0x00007fff85200cab _pthread_wqthread + 404
    15  libsystem_c.dylib                 0x00007fff851eb171 start_wqthread + 13
    Thread 3:
    0   libsystem_kernel.dylib            0x00007fff84270686 mach_msg_trap + 10
    1   liblaunch.dylib                   0x00007fff848e37c4
    2   liblaunch.dylib                   0x00007fff848e24d9 bootstrap_look_up3 + 69
    3   libxpc.dylib                      0x00007fff82ff3c21 _xpc_connection_bootstrap_look_up_slow + 371
    4   libxpc.dylib                      0x00007fff82ff2c82 _xpc_connection_init + 1062
    5   libdispatch.dylib                 0x00007fff8da470b6 _dispatch_client_callout + 8
    6   libdispatch.dylib                 0x00007fff8da4847f _dispatch_queue_drain + 235
    7   libdispatch.dylib                 0x00007fff8da482f1 _dispatch_queue_invoke + 52
    8   libdispatch.dylib                 0x00007fff8da48448 _dispatch_queue_drain + 180
    9   libdispatch.dylib                 0x00007fff8da482f1 _dispatch_queue_invoke + 52
    10  libdispatch.dylib                 0x00007fff8da481c3 _dispatch_worker_thread2 + 249
    11  libsystem_c.dylib                 0x00007fff85200cab _pthread_wqthread + 404
    12  libsystem_c.dylib                 0x00007fff851eb171 start_wqthread + 13
    Thread 4:
    0   libsystem_kernel.dylib            0x00007fff842726d6 __workq_kernreturn + 10
    1   libsystem_c.dylib                 0x00007fff85200cb3 _pthread_wqthread + 412
    2   libsystem_c.dylib                 0x00007fff851eb171 start_wqthread + 13
    Thread 5:
    0   libsystem_kernel.dylib            0x00007fff842726d6 __workq_kernreturn + 10
    1   libsystem_c.dylib                 0x00007fff85200cb3 _pthread_wqthread + 412
    2   libsystem_c.dylib                 0x00007fff851eb171 start_wqthread + 13
    Binary Images:
           0x10399d000 -        0x1039f6ff7  mdworker (707.3) <105316D8-F5DF-3079-96EF-0EF0986EB053> /System/Library/Frameworks/CoreServices.framework/Frameworks/Metadata.framework /Versions/A/Support/mdworker
        0x7fff82fea000 -     0x7fff8300cff7  libxpc.dylib (140.41) <FAC04D8B-680E-325F-8F0C-DD69859D0E01> /usr/lib/system/libxpc.dylib
        0x7fff84260000 -     0x7fff8427bff7  libsystem_kernel.dylib (2050.18.24) <C0535565-35D1-31A7-A744-63D9F10F12A4> /usr/lib/system/libsystem_kernel.dylib
        0x7fff848e0000 -     0x7fff848e8fff  liblaunch.dylib (442.26.2) <2F71CAF8-6524-329E-AC56-C506658B4C0C> /usr/lib/system/liblaunch.dylib
        0x7fff851ea000 -     0x7fff852b6fe7  libsystem_c.dylib (825.25) <8CBCF9B9-EBB7-365E-A3FF-2F3850763C6B> /usr/lib/system/libsystem_c.dylib
        0x7fff852b7000 -     0x7fff852baff7  libdyld.dylib (210.2.3) <F59367C9-C110-382B-A695-9035A6DD387E> /usr/lib/system/libdyld.dylib
        0x7fff8da45000 -     0x7fff8da5aff7  libdispatch.dylib (228.23) <D26996BF-FC57-39EB-8829-F63585561E09> /usr/lib/system/libdispatch.dylib
        0x7fff8dafa000 -     0x7fff8dbabfff  com.apple.LaunchServices (539.7 - 539.7) <DA7C602E-5E01-31B8-925D-B45360CA089F> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchS ervices.framework/Versions/A/LaunchServices
        0x7fff8ec5e000 -     0x7fff8ee47fff  com.apple.CoreFoundation (6.8 - 744.12) <EF002794-DAEF-31C6-866C-E3E3AC387A9F> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
    ================================================================================ ================================
    08.12.12 12:40:16,529 sandboxd[20205]: ([20189]) mdworker(20189) deny mach-lookup com.apple.ls.boxd
    mdworker(20189) deny mach-lookup com.apple.ls.boxd
    Process:         mdworker [20189]
    Path:            /System/Library/Frameworks/CoreServices.framework/Frameworks/Metadata.framework /Versions/A/Support/mdworker
    Load Address:    0x106809000
    Identifier:      mdworker
    Version:         ??? (???)
    Code Type:       x86_64 (Native)
    Parent Process:  launchd [113]
    Date/Time:       2012-12-08 12:40:16.468 +0100
    OS Version:      Mac OS X 10.8.2 (12C60)
    Report Version:  8
    Thread 0:
    0   libsystem_kernel.dylib            0x00007fff84270686 mach_msg_trap + 10
    1   CoreFoundation                    0x00007fff8ec8d803 __CFRunLoopServiceMachPort + 195
    2   CoreFoundation                    0x00007fff8ec92ee6 __CFRunLoopRun + 1078
    3   CoreFoundation                    0x00007fff8ec926b2 CFRunLoopRunSpecific + 290
    4   CoreFoundation                    0x00007fff8eca1371 CFRunLoopRun + 97
    5   mdworker                          0x0000000106811ba9
    6   libdyld.dylib                     0x00007fff852b97e1 start + 0
    Thread 1:
    0   libsystem_kernel.dylib            0x00007fff84272d16 kevent + 10
    1   libdispatch.dylib                 0x00007fff8da499ee _dispatch_mgr_thread + 54
    Thread 2:
    0   libsystem_kernel.dylib            0x00007fff84272d16 kevent + 10
    1   libdispatch.dylib                 0x00007fff8da489ee _dispatch_mgr_wakeup + 16
    2   libdispatch.dylib                 0x00007fff8da47e65 _dispatch_wakeup + 28
    3   libdispatch.dylib                 0x00007fff8da47e10 _dispatch_queue_push_list_slow2 + 33
    4   libdispatch.dylib                 0x00007fff8da47ecd _dispatch_wakeup + 132
    5   libdispatch.dylib                 0x00007fff8da48027 _dispatch_resume_slow + 17
    6   libxpc.dylib                      0x00007fff82ff5ff2 _xpc_connection_listen_for_reply + 198
    7   libxpc.dylib                      0x00007fff82ff5eff _xpc_connection_send_message_with_reply_f + 136
    8   libxpc.dylib                      0x00007fff82ff5e10 xpc_connection_send_message_with_reply_sync + 112
    9   LaunchServices                    0x00007fff8db033ce send(LSBoxMessage&, LSBoxMessage&) + 28
    10  LaunchServices                    0x00007fff8db83d4b lsbox_preflightAppLaunch + 84
    11  LaunchServices                    0x00007fff8db0e341 _LSFindOrRegisterBundleNode + 857
    12  LaunchServices                    0x00007fff8db6ab02 _LSRegisterNode + 75
    13  LaunchServices                    0x00007fff8db16a0f _LSBundleCopyOrCheckNode + 1047
    14  LaunchServices                    0x00007fff8dafe5b6 _LSCopyLibraryItemURLs + 486
    15  mdworker                          0x0000000106839014
    16  libdispatch.dylib                 0x00007fff8da4af01 _dispatch_call_block_and_release + 15
    17  libdispatch.dylib                 0x00007fff8da470b6 _dispatch_client_callout + 8
    18  libdispatch.dylib                 0x00007fff8da4847f _dispatch_queue_drain + 235
    19  libdispatch.dylib                 0x00007fff8da482f1 _dispatch_queue_invoke + 52
    20  libdispatch.dylib                 0x00007fff8da481c3 _dispatch_worker_thread2 + 249
    21  libsystem_c.dylib                 0x00007fff85200cab _pthread_wqthread + 404
    22  libsystem_c.dylib                 0x00007fff851eb171 start_wqthread + 13
    Thread 3:
    0   libsystem_kernel.dylib            0x00007fff84270686 mach_msg_trap + 10
    1   liblaunch.dylib                   0x00007fff848e37c4
    2   liblaunch.dylib                   0x00007fff848e24d9 bootstrap_look_up3 + 69
    3   libxpc.dylib                      0x00007fff82ff3c21 _xpc_connection_bootstrap_look_up_slow + 371
    4   libxpc.dylib                      0x00007fff82ff2c82 _xpc_connection_init + 1062
    5   libdispatch.dylib                 0x00007fff8da470b6 _dispatch_client_callout + 8
    6   libdispatch.dylib                 0x00007fff8da4847f _dispatch_queue_drain + 235
    7   libdispatch.dylib                 0x00007fff8da482f1 _dispatch_queue_invoke + 52
    8   libdispatch.dylib                 0x00007fff8da48448 _dispatch_queue_drain + 180
    9   libdispatch.dylib                 0x00007fff8da482f1 _dispatch_queue_invoke + 52
    10  libdispatch.dylib                 0x00007fff8da481c3 _dispatch_worker_thread2 + 249
    11  libsystem_c.dylib                 0x00007fff85200cab _pthread_wqthread + 404
    12  libsystem_c.dylib                 0x00007fff851eb171 start_wqthread + 13
    Thread 4:
    0   libsystem_kernel.dylib            0x00007fff842726d6 __workq_kernreturn + 10
    1   libsystem_c.dylib                 0x00007fff85200cb3 _pthread_wqthread + 412
    2   libsystem_c.dylib                 0x00007fff851eb171 start_wqthread + 13
    Thread 5:
    0   libsystem_kernel.dylib            0x00007fff842726d6 __workq_kernreturn + 10
    1   libsystem_c.dylib                 0x00007fff85200cb3 _pthread_wqthread + 412
    2   libsystem_c.dylib                 0x00007fff851eb171 start_wqthread + 13
    Binary Images:
           0x106809000 -        0x106862ff7  mdworker (707.3) <105316D8-F5DF-3079-96EF-0EF0986EB053> /System/Library/Frameworks/CoreServices.framework/Frameworks/Metadata.framework /Versions/A/Support/mdworker
        0x7fff82fea000 -     0x7fff8300cff7  libxpc.dylib (140.41) <FAC04D8B-680E-325F-8F0C-DD69859D0E01> /usr/lib/system/libxpc.dylib
        0x7fff84260000 -     0x7fff8427bff7  libsystem_kernel.dylib (2050.18.24) <C0535565-35D1-31A7-A744-63D9F10F12A4> /usr/lib/system/libsystem_kernel.dylib
        0x7fff848e0000 -     0x7fff848e8fff  liblaunch.dylib (442.26.2) <2F71CAF8-6524-329E-AC56-C506658B4C0C> /usr/lib/system/liblaunch.dylib
        0x7fff851ea000 -     0x7fff852b6fe7  libsystem_c.dylib (825.25) <8CBCF9B9-EBB7-365E-A3FF-2F3850763C6B> /usr/lib/system/libsystem_c.dylib
        0x7fff852b7000 -     0x7fff852baff7  libdyld.dylib (210.2.3) <F59367C9-C110-382B-A695-9035A6DD387E> /usr/lib/system/libdyld.dylib
        0x7fff8da45000 -     0x7fff8da5aff7  libdispatch.dylib (228.23) <D26996BF-FC57-39EB-8829-F63585561E09> /usr/lib/system/libdispatch.dylib
        0x7fff8dafa000 -     0x7fff8dbabfff  com.apple.LaunchServices (539.7 - 539.7) <DA7C602E-5E01-31B8-925D-B45360CA089F> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchS ervices.framework/Versions/A/LaunchServices
        0x7fff8ec5e000 -     0x7fff8ee47fff  com.apple.CoreFoundation (6.8 - 744.12) <EF002794-DAEF-31C6-866C-E3E3AC387A9F> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
    ================================================================================ ================================
    08.12.12 12:40:16,000 kernel[0]: Sandbox: sandboxd(20205) deny mach-lookup com.apple.coresymbolicationd
    Maybe some of you might know an answer for this problem.
    Thanks a lot.

    baltwo wrote:
    Those are Spotlight indexing crashes, not freezes. AFAICT, theyre due to crappy sandboxing in ML. File a bug report with Apple. For more on crashes, see TN 2123 CrashReport Decipherer.
    Actually, if you look closely, you'll see that they're neither crashes (.crash) nor hangs (.hang).
    Here's what's reported in Console.app:
    1/3/2013 11:01:30.601 AM mdworker[12719]: Unable to talk to lsboxd
    1/3/2013 11:01:30.946 AM sandboxd[12721]: ([12719]) mdworker(12719) deny mach-lookup com.apple.ls.boxd
    The second line has an "attachment" icon which you can click to get the full report, which is saved in an auxiliary document at:
    /private/var/log/asl/AUX.2013.01.03/796282
    Here's the contents (minus the backtrace information) of that asl (Apple System Log) auxiliary document:
    mdworker(12719) deny mach-lookup com.apple.ls.boxd
    Process:         mdworker [12719]
    Path:        /System/Library/Frameworks/CoreServices.framework/Frameworks/Metadata.framework /Versions/A/Support/mdworker
    Load Address:    0x10817a000
    Identifier:      mdworker
    Version:         ??? (???)
    Code Type:       x86_64 (Native)
    Parent Process:  launchd [340]
    Date/Time:       2013-01-03 11:01:30.905 -0500
    OS Version:      Mac OS X 10.8.2 (12C60)
    Report Version:  8
    Compare that with a crash log (.crash) which specifies a Crashed Thread number as well as the Exception Type and Exception Codes:
    Process:         AppleScript Editor [88791]
    Path:            /Applications/Utilities/AppleScript Editor.app/Contents/MacOS/AppleScript Editor
    Identifier:      com.apple.ScriptEditor2
    Version:         2.5 (138)
    Build Info:      ScriptEditorX-138000000000000~5
    Code Type:       X86-64 (Native)
    Parent Process:  launchd [344]
    User ID:         501
    Date/Time:       2013-01-01 06:05:30.986 -0500
    OS Version:      Mac OS X 10.8.2 (12C60)
    Report Version:  10
    Crashed Thread:  8
    Exception Type:  EXC_BAD_ACCESS (SIGSEGV)
    Exception Codes: KERN_INVALID_ADDRESS at 0xfffffffffffffff8
    So, it's not a crash, but just a report of a sandboxing violation. It is likely the backtrace information that makes it look so similar to a crash, but the backtrace information serves the same purpose in both cases: to provide the contextual information about what lead up to the event being reported. (In the case of a crash log, there will be one Thread that is listed as Crashed).
    Anyway, if it isn't already obvious, I'm experiencing the same logging to Console about this issue, and a Google search led me here.
    From what I've gathered, you can apparently fix the issue by restarting in Safe Mode, then restarting normally. That appears to delete some cache files inside the "secure" temporary items and caches folders, which are located in /private/var/folders/, that are somehow responsible for this issue.
    Unfortuanately, I don't think I can start up in Safe Mode, since I don't have a recovery partion, because my Mountain Lion installation is spread across 2 volumes in a RAID 0 setup.
    I'm still in the process of researching this, and need to reboot now to try creating an external flash drive with a ML installation + Recovery Partition.

  • What's this sandboxd mdworker deny mach-lookup thing about?

    My newer iMac keeps locking up over many months. It seems to be getting more frequent. All updated are made and I'm running OS10.8.2.
    Each time I've looked at the console log one of the last entries has been related to mdworker and sandboxd.
    This is the console immediatly surrounding the latest lockup and restart (having to use the powerbutton.)
    3/10/13 7:48:27.128 PM com.apple.backupd[20992]: Backup completed successfully.
    3/10/13 7:48:27.000 PM kernel[0]: Sandbox: sandboxd(21005) deny mach-lookup com.apple.coresymbolicationd
    3/10/13 7:50:27.573 PM mdworker[21015]: Unable to talk to lsboxd
    3/10/13 7:50:27.577 PM mdworker[21014]: Unable to talk to lsboxd
    3/10/13 7:50:27.622 PM sandboxd[21016]: ([21015]) mdworker(21015) deny mach-lookup com.apple.ls.boxd
    3/10/13 7:50:27.626 PM sandboxd[21016]: ([21014]) mdworker(21014) deny mach-lookup com.apple.ls.boxd
    3/10/13 7:50:27.000 PM kernel[0]: Sandbox: sandboxd(21016) deny mach-lookup com.apple.coresymbolicationd
    3/10/13 7:52:28.404 PM mdworker[21026]: Unable to talk to lsboxd
    3/10/13 7:52:28.408 PM mdworker[21027]: Unable to talk to lsboxd
    3/10/13 7:52:28.457 PM sandboxd[21028]: ([21026]) mdworker(21026) deny mach-lookup com.apple.ls.boxd
    3/10/13 7:52:28.461 PM sandboxd[21028]: ([21027]) mdworker(21027) deny mach-lookup com.apple.ls.boxd
    3/10/13 7:52:28.000 PM kernel[0]: Sandbox: sandboxd(21028) deny mach-lookup com.apple.coresymbolicationd
    3/10/13 10:04:58.000 PM bootlog[0]: BOOT_TIME 1362978298 0
    3/10/13 10:05:24.000 PM kernel[0]: Darwin Kernel Version 12.2.0: Sat Aug 25 00:48:52 PDT 2012; root:xnu-2050.18.24~1/RELEASE_X86_64
    3/10/13 10:05:24.000 PM kernel[0]: vm_page_bootstrap: 3994120 free pages and 167416 wired pages
    3/10/13 10:05:24.000 PM kernel[0]: kext submap [0xffffff7f80741000 - 0xffffff8000000000], kernel text [0xffffff8000200000 - 0xffffff8000741000]
    3/10/13 10:05:24.000 PM kernel[0]: zone leak detection enabled
    3/10/13 10:05:24.000 PM kernel[0]: standard timeslicing quantum is 10000 us
    3/10/13 10:05:24.000 PM kernel[0]: standard background quantum is 2500 us
    3/10/13 10:05:24.000 PM kernel[0]: mig_table_max_displ = 74
    3/10/13 10:05:24.000 PM kernel[0]: corecrypto kext started!
    3/10/13 10:05:24.000 PM kernel[0]: Running kernel space in FIPS MODE
    Below is the full report from the line in red above --
    mdworker(21027) deny mach-lookup com.apple.ls.boxd
    Process:         mdworker [21027]
    Path:            /System/Library/Frameworks/CoreServices.framework/Frameworks/Metadata.framework /Versions/A/Support/mdworker
    Load Address:    0x107e3e000
    Identifier:      mdworker
    Version:         ??? (???)
    Code Type:       x86_64 (Native)
    Parent Process:  launchd [285]
    Date/Time:       2013-03-10 19:52:28.457 -0700
    OS Version:      Mac OS X 10.8.2 (12C60)
    Report Version:  8
    Thread 0:
    0   libsystem_kernel.dylib                  0x00007fff8ca62686 mach_msg_trap + 10
    1   CoreFoundation                          0x00007fff93f47803 __CFRunLoopServiceMachPort + 195
    2   CoreFoundation                          0x00007fff93f4cee6 __CFRunLoopRun + 1078
    3   CoreFoundation                          0x00007fff93f4c6b2 CFRunLoopRunSpecific + 290
    4   CoreFoundation                          0x00007fff93f5b371 CFRunLoopRun + 97
    5   mdworker                                0x0000000107e46ba9
    6   libdyld.dylib                           0x00007fff94edb7e1 start + 0
    Thread 1:
    0   libsystem_kernel.dylib                  0x00007fff8ca64d16 kevent + 10
    1   libdispatch.dylib                       0x00007fff94d8c9ee _dispatch_mgr_thread + 54
    Thread 2:
    0   libsystem_kernel.dylib                  0x00007fff8ca626c2 semaphore_wait_trap + 10
    1   libxpc.dylib                            0x00007fff94f48e1f xpc_connection_send_message_with_reply_sync + 127
    2   LaunchServices                          0x00007fff8e8ec3ce send(LSBoxMessage&, LSBoxMessage&) + 28
    3   LaunchServices                          0x00007fff8e96cd4b lsbox_preflightAppLaunch + 84
    4   LaunchServices                          0x00007fff8e8f7341 _LSFindOrRegisterBundleNode + 857
    5   LaunchServices                          0x00007fff8e953b02 _LSRegisterNode + 75
    6   LaunchServices                          0x00007fff8e8ffa0f _LSBundleCopyOrCheckNode + 1047
    7   LaunchServices                          0x00007fff8e8e75b6 _LSCopyLibraryItemURLs + 486
    8   mdworker                                0x0000000107e6e014
    9   libdispatch.dylib                       0x00007fff94d8df01 _dispatch_call_block_and_release + 15
    10  libdispatch.dylib                       0x00007fff94d8a0b6 _dispatch_client_callout + 8
    11  libdispatch.dylib                       0x00007fff94d8b47f _dispatch_queue_drain + 235
    12  libdispatch.dylib                       0x00007fff94d8b2f1 _dispatch_queue_invoke + 52
    13  libdispatch.dylib                       0x00007fff94d8b1c3 _dispatch_worker_thread2 + 249
    14  libsystem_c.dylib                       0x00007fff89e9ccab _pthread_wqthread + 404
    15  libsystem_c.dylib                       0x00007fff89e87171 start_wqthread + 13
    Thread 3:
    0   libsystem_kernel.dylib                  0x00007fff8ca646d6 __workq_kernreturn + 10
    1   libsystem_c.dylib                       0x00007fff89e9ccb3 _pthread_wqthread + 412
    2   libsystem_c.dylib                       0x00007fff89e87171 start_wqthread + 13
    Thread 4:
    0   libsystem_kernel.dylib                  0x00007fff8ca646d6 __workq_kernreturn + 10
    1   libsystem_c.dylib                       0x00007fff89e9ccb3 _pthread_wqthread + 412
    2   libsystem_c.dylib                       0x00007fff89e87171 start_wqthread + 13
    Thread 5:
    0   libsystem_kernel.dylib                  0x00007fff8ca62686 mach_msg_trap + 10
    1   liblaunch.dylib                         0x00007fff918217c4
    2   liblaunch.dylib                         0x00007fff918204d9 bootstrap_look_up3 + 69
    3   libxpc.dylib                            0x00007fff94f46c21 _xpc_connection_bootstrap_look_up_slow + 371
    4   libxpc.dylib                            0x00007fff94f45c82 _xpc_connection_init + 1062
    5   libdispatch.dylib                       0x00007fff94d8a0b6 _dispatch_client_callout + 8
    6   libdispatch.dylib                       0x00007fff94d8b47f _dispatch_queue_drain + 235
    7   libdispatch.dylib                       0x00007fff94d8b2f1 _dispatch_queue_invoke + 52
    8   libdispatch.dylib                       0x00007fff94d8b448 _dispatch_queue_drain + 180
    9   libdispatch.dylib                       0x00007fff94d8b2f1 _dispatch_queue_invoke + 52
    10  libdispatch.dylib                       0x00007fff94d8b1c3 _dispatch_worker_thread2 + 249
    11  libsystem_c.dylib                       0x00007fff89e9ccab _pthread_wqthread + 404
    12  libsystem_c.dylib                       0x00007fff89e87171 start_wqthread + 13
    Binary Images:
           0x107e3e000 -        0x107e97ff7  mdworker (707.3) <105316D8-F5DF-3079-96EF-0EF0986EB053> /System/Library/Frameworks/CoreServices.framework/Frameworks/Metadata.framework /Versions/A/Support/mdworker
        0x7fff89e86000 -     0x7fff89f52fe7  libsystem_c.dylib (825.25) <8CBCF9B9-EBB7-365E-A3FF-2F3850763C6B> /usr/lib/system/libsystem_c.dylib
        0x7fff8ca52000 -     0x7fff8ca6dff7  libsystem_kernel.dylib (2050.18.24) <C0535565-35D1-31A7-A744-63D9F10F12A4> /usr/lib/system/libsystem_kernel.dylib
        0x7fff8e8e3000 -     0x7fff8e994fff  com.apple.LaunchServices (539.7 - 539.7) <DA7C602E-5E01-31B8-925D-B45360CA089F> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchS ervices.framework/Versions/A/LaunchServices
        0x7fff9181e000 -     0x7fff91826fff  liblaunch.dylib (442.26.2) <2F71CAF8-6524-329E-AC56-C506658B4C0C> /usr/lib/system/liblaunch.dylib
        0x7fff93f18000 -     0x7fff94101fff  com.apple.CoreFoundation (6.8 - 744.12) <EF002794-DAEF-31C6-866C-E3E3AC387A9F> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
        0x7fff94d88000 -     0x7fff94d9dff7  libdispatch.dylib (228.23) <D26996BF-FC57-39EB-8829-F63585561E09> /usr/lib/system/libdispatch.dylib
        0x7fff94ed9000 -     0x7fff94edcff7  libdyld.dylib (210.2.3) <F59367C9-C110-382B-A695-9035A6DD387E> /usr/lib/system/libdyld.dylib
        0x7fff94f3d000 -     0x7fff94f5fff7  libxpc.dylib (140.41) <FAC04D8B-680E-325F-8F0C-DD69859D0E01> /usr/lib/system/libxpc.dylib
    Any suggestions and help apprecieated.
    --Dan

    Dan Bratten wrote:
    3/10/13 7:48:27.128 PM com.apple.backupd[20992]: Backup completed successfully.
    3/10/13 7:48:27.000 PM kernel[0]: Sandbox: sandboxd(21005) deny mach-lookup com.apple.coresymbolicationd
    3/10/13 7:50:27.573 PM mdworker[21015]: Unable to talk to lsboxd
    3/10/13 7:50:27.577 PM mdworker[21014]: Unable to talk to lsboxd
    3/10/13 7:50:27.622 PM sandboxd[21016]: ([21015]) mdworker(21015) deny mach-lookup com.apple.ls.boxd
    3/10/13 7:50:27.626 PM sandboxd[21016]: ([21014]) mdworker(21014) deny mach-lookup com.apple.ls.boxd
    3/10/13 7:50:27.000 PM kernel[0]: Sandbox: sandboxd(21016) deny mach-lookup com.apple.coresymbolicationd
    3/10/13 7:52:28.404 PM mdworker[21026]: Unable to talk to lsboxd
    3/10/13 7:52:28.408 PM mdworker[21027]: Unable to talk to lsboxd
    3/10/13 7:52:28.457 PM sandboxd[21028]: ([21026]) mdworker(21026) deny mach-lookup com.apple.ls.boxd
    3/10/13 7:52:28.461 PM sandboxd[21028]: ([21027]) mdworker(21027) deny mach-lookup com.apple.ls.boxd
    3/10/13 7:52:28.000 PM kernel[0]: Sandbox: sandboxd(21028) deny mach-lookup com.apple.coresymbolicationd
    3/10/13 10:04:58.000 PM bootlog[0]: BOOT_TIME 1362978298 0
    3/10/13 10:05:24.000 PM kernel[0]: Darwin Kernel Version 12.2.0: Sat Aug 25 00:48:52 PDT 2012; root:xnu-2050.18.24~1/RELEASE_X86_64
    3/10/13 10:05:24.000 PM kernel[0]: vm_page_bootstrap: 3994120 free pages and 167416 wired pages
    3/10/13 10:05:24.000 PM kernel[0]: kext submap [0xffffff7f80741000 - 0xffffff8000000000], kernel text [0xffffff8000200000 - 0xffffff8000741000]
    3/10/13 10:05:24.000 PM kernel[0]: zone leak detection enabled
    3/10/13 10:05:24.000 PM kernel[0]: standard timeslicing quantum is 10000 us
    3/10/13 10:05:24.000 PM kernel[0]: standard background quantum is 2500 us
    3/10/13 10:05:24.000 PM kernel[0]: mig_table_max_displ = 74
    3/10/13 10:05:24.000 PM kernel[0]: corecrypto kext started!
    3/10/13 10:05:24.000 PM kernel[0]: Running kernel space in FIPS MODE
    You have a common problem with OS X 10.8.2, the "unable to talk to lsboxd" message. First of all, try to fix this. It's fixed just starting your Mac in safe mode, holding the Shift key while your computer is starting. Then, just after starting in safe mode, restart, and that message will disappear. Finally, see if your red message appears

  • Mdworker deny mach-lookup. But macbook won't boot in safe mode

    I have a common problem, I get theese messages every now and then in console:
    2/8/13 6:38:24.000 PM kernel[0]: Sandbox: sandboxd(793) deny mach-lookup com.apple.coresymbolicationd
    2/8/13 6:38:24.534 PM sandboxd[793]: ([791]) mdworker(791) deny mach-lookup com.apple.ls.boxd
    2/8/13 6:38:24.556 PM sandboxd[793]: ([792]) mdworker(792) deny mach-lookup com.apple.ls.boxd
    There is a solution, which should resolve it, like here https://discussions.apple.com/message/19750564?searchText=mach-lookup%20com.appl e.ls.boxd#19750564
    I have just boot in safe mode. (holding Shift during boot)
    but my macbook won't boot in Safe mode. It just freeses with a grey screen for hours and wont boot.
    I tried to leave it overnight to boot, but it didn't.
    Please help me make my macbook to boot in SafeMode.
    my configuration is the following:
    MacBookPro8,1
    OSX 10.8.2

    There is a bug in fsck_hfs that is affecting a bunch of people.  Basically as your comptuer starts in safe mode, it runs a file system check (fsck) against your hard drive, it gets to a certain point and... just sits there.  No one knows why outside of apple.
    Lots of info here, including a way to get around it by tricking the system to think fsck had been run, though the fsck will not be complete so it is not a good solution.
    https://discussions.apple.com/message/21389737?ac_cid=tw123456#21389737

  • Mdworker deny mach-lookup com.intego.mig_hook (pre-ls-info fstype:hfs

    I made a clean insatlle of Mouatin Lion and my HD is  is filled with many files every day.
    I looked in the console, I get this message that reproduces to infinity
    Here you have an example :
    mdworker(2557) deny mach-lookup com.intego.mig_hook (pre-plugin fstype:hfs fsflag:480D000 flags:240000004C diag:0 uti:com.apple.property-list plugin:internalPlainTextImporter - find suspect file using: sudo mdutil -t 1387774)
    Process:         mdworker [2557]
    Path:            /System/Library/Frameworks/CoreServices.framework/Frameworks/Metadata.framework /Versions/A/Support/mdworker
    Load Address:    0x10e999000
    Identifier:      mdworker
    Version:         ??? (???)
    Code Type:       x86_64 (Native)
    Parent Process:  launchd [305]
    Date/Time:       2012-10-06 13:27:46.816 +0200
    OS Version:      Mac OS X 10.8.2 (12C60)
    Report Version:  8
    Thread 0:
    0   libsystem_kernel.dylib                  0x00007fff82cec686 mach_msg_trap + 10
    1   CoreFoundation                          0x00007fff8bb05803 __CFRunLoopServiceMachPort + 195
    2   CoreFoundation                          0x00007fff8bb0aee6 __CFRunLoopRun + 1078
    3   CoreFoundation                          0x00007fff8bb0a6b2 CFRunLoopRunSpecific + 290
    4   CoreFoundation                          0x00007fff8bb19371 CFRunLoopRun + 97
    5   mdworker                                0x000000010e9a1ba9
    6   libdyld.dylib                           0x00007fff889777e1 start + 0
    Thread 1:
    0   libsystem_kernel.dylib                  0x00007fff82ceed16 kevent + 10
    1   libdispatch.dylib                       0x00007fff8ac139ee _dispatch_mgr_thread + 54
    Thread 2:
    0   libsystem_kernel.dylib                  0x00007fff82cec686 mach_msg_trap + 10
    1   liblaunch.dylib                         0x00007fff861ac7c4
    2   liblaunch.dylib                         0x00007fff861ab4d9 bootstrap_look_up3 + 69
    3   liblaunch.dylib                         0x00007fff861ab591 bootstrap_look_up + 37
    4                                           0x000000010ea1eb40
    5                                           0x000000010ea1f098
    6   mdworker                                0x000000010e9a6282
    7   mdworker                                0x000000010e9a6027
    8   mdworker                                0x000000010e9a34f2
    9   libsystem_c.dylib                       0x00007fff828b8742 _pthread_start + 327
    10  libsystem_c.dylib                       0x00007fff828a5181 thread_start + 13
    Thread 3:
    0   libsystem_kernel.dylib                  0x00007fff82cec686 mach_msg_trap + 10
    1   mdworker                                0x000000010e9b5df9
    2   libsystem_c.dylib                       0x00007fff828b8742 _pthread_start + 327
    3   libsystem_c.dylib                       0x00007fff828a5181 thread_start + 13
    Thread 4:
    0   libsystem_kernel.dylib                  0x00007fff82cee6d6 __workq_kernreturn + 10
    1   libsystem_c.dylib                       0x00007fff828bacb3 _pthread_wqthread + 412
    2   libsystem_c.dylib                       0x00007fff828a5171 start_wqthread + 13
    Binary Images:
           0x10e999000 -        0x10e9f2ff7  mdworker (707.3) <105316D8-F5DF-3079-96EF-0EF0986EB053> /System/Library/Frameworks/CoreServices.framework/Frameworks/Metadata.framework /Versions/A/Support/mdworker
        0x7fff828a4000 -     0x7fff82970fe7  libsystem_c.dylib (825.25) <8CBCF9B9-EBB7-365E-A3FF-2F3850763C6B> /usr/lib/system/libsystem_c.dylib
        0x7fff82cdc000 -     0x7fff82cf7ff7  libsystem_kernel.dylib (2050.18.24) <C0535565-35D1-31A7-A744-63D9F10F12A4> /usr/lib/system/libsystem_kernel.dylib
        0x7fff861a9000 -     0x7fff861b1fff  liblaunch.dylib (442.26.2) <2F71CAF8-6524-329E-AC56-C506658B4C0C> /usr/lib/system/liblaunch.dylib
        0x7fff88975000 -     0x7fff88978ff7  libdyld.dylib (210.2.3) <F59367C9-C110-382B-A695-9035A6DD387E> /usr/lib/system/libdyld.dylib
        0x7fff8ac0f000 -     0x7fff8ac24ff7  libdispatch.dylib (228.23) <D26996BF-FC57-39EB-8829-F63585561E09> /usr/lib/system/libdispatch.dylib
        0x7fff8bad6000 -     0x7fff8bcbffff  com.apple.CoreFoundation (6.8 - 744.12) <EF002794-DAEF-31C6-866C-E3E3AC387A9F> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
    I contacted intego France, who told me that they were not aware of this

    I contacted Intego opened a ticket (no response), but I think Version 6 must have a big bug  with ML
    you can see this url :
    https://www.facebook.com/Intego/posts/311468278907535
    dam Wallace I am getting exactly the same thing in Mountain Lion. My System Log is full of hundreds of messages repeating exactly the same thing, around 20 times per second. Macintosh.local sandboxd[7781] ([7307]): mdworker(7307) deny mach-lookup com.intego.mig_hook (pre-plugin fstype:hfs fsflag:480D000 flags:250000005E diag:0 uti:com.apple.application-bundle plugin:/Library/Spotlight/Application.mdimporter - find suspect file using: sudo mdutil -t 1029605)
    I think this might explain why I have been getting system freezes & kernel panics. A fix for this would be much appreciated.
    Mike Dever mdworker(2315) deny mach-lookup com.intego.mig_hook (pre-plugin fstype:hfs fsflag:480D000 flags:240000004C diag:0 uti:com.apple.property-list plugin:internalPlainTextImporter - find suspect file using: sudo mdutil -t 64324970)

  • Deny mach-lookup com.apple.PowerManagement.control

    I keep seeing this message in the Console log. In searching other discussions, I find it listed in the logs, but I don't see any explanation of whether this repesents a problem and if so how it can be fixed.
    I have already gotten rid of some of the lookup error by restarting into Safe Boot and then restarting normally.

    There is nothing wrong in terms of functionality. I did experience an intermittent loss of power on battery over the last week. I didn't make note of the exact time. I shouldn't say loss of power, but the machine would just go to sleep during use. I would click a key 10 seconds later and it would wake from sleep. Not sure if this would be related, but given: deny mach-lookup com.apple.PowerManagement.controle. it may be possible. Not sure. Besides that, no performance issues.

  • Sandboxd WebProcess deny mach-lookup ATS Query

    Hi
    I keep getting a lot of these lines on the system log messages (Lion 10.7.3)
    Anyone has an idea what doest it mean?
    Thanks
    13/03/12 13:50:58,285 sandboxd: ([5444]) WebProcess(5444) deny mach-lookup ATS Query Port 975
    13/03/12 13:50:58,285 sandboxd: ([5444]) WebProcess(5444) deny mach-lookup ATS Query Port 4033
    13/03/12 13:50:58,286 sandboxd: ([5444]) WebProcess(5444) deny mach-lookup ATS Query Port 4125
    13/03/12 13:50:58,286 sandboxd: ([5444]) WebProcess(5444) deny mach-lookup ATS Query Port 4202
    13/03/12 13:50:58,286 sandboxd: ([5444]) WebProcess(5444) deny mach-lookup ATS Query Port 4477
    13/03/12 13:50:58,287 sandboxd: ([5444]) WebProcess(5444) deny mach-lookup ATS Query Port 4767
    13/03/12 13:50:58,321 sandboxd: ([5444]) WebProcess(5444) deny mach-lookup ATS Query Port 975
    13/03/12 13:50:58,321 sandboxd: ([5444]) WebProcess(5444) deny mach-lookup ATS Query Port 4033
    13/03/12 13:50:58,321 sandboxd: ([5444]) WebProcess(5444) deny mach-lookup ATS Query Port 4125
    13/03/12 13:50:58,322 sandboxd: ([5444]) WebProcess(5444) deny mach-lookup ATS Query Port 4202
    13/03/12 13:50:58,323 sandboxd: ([5444]) WebProcess(5444) deny mach-lookup ATS Query Port 4477
    13/03/12 13:50:58,356 sandboxd: ([5444]) WebProcess(5444) deny mach-lookup ATS Query Port 4767
    13/03/12 13:50:58,381 sandboxd: ([5444]) WebProcess(5444) deny mach-lookup ATS Query Port 975
    13/03/12 13:50:58,382 sandboxd: ([5444]) WebProcess(5444) deny mach-lookup ATS Query Port 4033
    13/03/12 13:50:58,382 sandboxd: ([5444]) WebProcess(5444) deny mach-lookup ATS Query Port 4125
    13/03/12 13:50:58,383 sandboxd: ([5444]) WebProcess(5444) deny mach-lookup ATS Query Port 4202
    13/03/12 13:50:58,383 sandboxd: ([5444]) WebProcess(5444) deny mach-lookup ATS Query Port 4477
    13/03/12 13:50:58,384 sandboxd: ([5444]) WebProcess(5444) deny mach-lookup ATS Query Port 4767

    Although I'm not a software engineer, I've done some research on this...
    This is a common entry type
    WebProcess is trying to accerss a mach service, a component of the oepertaing system
    Sandbox(ing) is a design concept for software, which should help apps be more stable & make it harder for malware ( viruses, et al ) to hijack an app for potentially nefarious purposes
    So the operating system is informing the software developers, in this case @ Apple, that WebProcess is attempting to access something that it either shouldn't or needs to be given the correct permissions to access
    There is nothing wrong with your computer.  This is a tool to help developers find where holes exist in their sandboxed apps.  There is nothing that you can do to fix this & it shouldn't cause any performance issues
    WebProcess is a separate process from Safari.  Basically, Safari is the user interface to the browser & WebProcess is the web page.  Because it is usually the web page that causes crashes, Safari & WebProcess run independently of each other.  This way, when WebProcess crashes, it won't take down Safari.  Rather than rebooting the whole app, WebProcess needs only refresh the open tabs

  • Kernel: Sandbox: xpchelper(265) deny mach-lookup com.intego.mig_hook ?

    Can someone provide a short explanation on what this means, and what can be the consequences ? I have 1 Kernel Panic a day, and those kind of crashes are very unpleasant. I would like to find the source of my problem. I know that installing Virus Barrier X6 on a Lion Server is not supported. Thing is I managed to get it to work and it appears to work very fine ... or not.

    Apparently, something from Intego's not compatible. Contact them.

  • Com.apple.WebKit deny mach-per-user-lookup

    Hi all
    My console log is full of these:
    PM kernel: Sandbox: com.apple.WebKit (####) deny mach-per-user-lookup
    Anyone have any idea what this means and should something be done about it?
    Thanks

    As do I.  I can see that there is the usual overwhelming response to a problem.

  • What is "deny mach-per-user-lookup"

    I went to console to investigate system crashes (i believe to be an openGL issue unrelated to this) and i saw a number of these:
    5/26/10 1:22:42 AM sandboxd[330] sshd(1056) deny mach-per-user-lookup
    There were 883 messages over 8.5 hours, mixed in with occasional:
    Allow sshd-keygen-wrapper connecting from 217.27.150.178:55936 to port 22 proto=6
    I traced the IP back to Kiev… in Russia. That's odd. I did a search around and found mention of people with snow leopard, 10.6.2 or 3 (which i have) reporting this but the conversations were varied…
    could someone explain 'deny mach-per-user-lookup' for me, and elaborate on the sshd attempts? I don't know if i should be concerned. I do have an RSA key-only tunnel set up with my work computer, but i had believed this was to be the most secure set up possible and these seem to be on port 22 which is common FTP anyway. OS firewall is up otherwise allowing the common connections like fire sharing and SHH, my router is set for 'inbound and outbound accept' as its security policy, but regardless, all but a couple dozen specific ports are blocked.
    Thanks for any input—

    Nmap scan report for 217.27.150.178.sitel.com.ua (217.27.150.178)
    Host is up (0.24s latency).
    Not shown: 89 closed ports
    PORT STATE SERVICE
    21/tcp open ftp
    22/tcp open ssh
    25/tcp open smtp
    80/tcp open http
    110/tcp open pop3
    135/tcp filtered msrpc
    139/tcp filtered netbios-ssn
    445/tcp filtered microsoft-ds
    1720/tcp filtered H.323/Q.931
    3128/tcp open squid-http
    3306/tcp filtered mysql
    From the scan, it appears to be some sort of server, possibly a private proxy server.
    Perhaps someone is using it to anonymously attempt connecting to your machine.
    Unless you are running a server, I say you need to beef up your security a bit. Close up
    some of those ports you have opened up to the Internet.

  • Error encountered while signing: The Windows Cryptographic Service Provider reported an error: Access was denied because of a security violation. Error Code: 2148532330

    Last night when i tried to sign a document i received the mesage below and after that it says this document can't be signed what can i do to fix this problem.
    Error encountered while signing:
    The Windows Cryptographic Service Provider reported an error:
    Access was denied because of a security violation.
    Error Code: 2148532330

    I assume you are implying "biztax" application here, right?
    I have contacted their program lead, with no result at all.
    Past days I have been searching for a solution - reinstalls / new systems - no solution.
    This issue appeared a week or two ago only.
    I found http://forums.adobe.com/message/5338853 useful - but no positive results either.
    http://test.eid.belgium.be/faq/faq_nl.htm obviously didnt help either.
    If anyone finds a solution to this issue, please do let me know - any help is appreciated.
    Biztax tells to use the "signature", not the "authentication"  - but it is only Auth. that is showing up as option to sign (that works)
    ps, did you fiddle with the Adobe Reader XI security settings and import that PKI etc as well? I hoped that would be the breaktrough. Sadly i'm still crying in my chair.
    Oh, and dont forget: they claim nobody else got this issue. Maybe one or two people. (We got about 8 customers experiencing exactly the same symptoms at the same time )
    >  I noticed that when I try to open the pdf  document that is 'signed' by the government it is not showing the filename in the title bar, but only " - Adobe Reader".    every piece of info helps I guess.
    Obviously last version of Reader   11.0.03

  • Getting error-"Process Access denied" while invoking Process as web service

    Hi,
    I have a very simple Business Process, just to take some input & give some String as output. I published this BP as web service on Oracle BPM - Process Administrator. I got its WSDL also. I can invoke startSession operation. But when I invoke the operation that is exposed by BP as web service, I am getting an error - "Process Access denied".
    Please help to solve the issue, as I need it urgently.
    Thanks,
    Sujata

    Hi Ariel,
    Thanks for reply and sorry for delay on updating status. Actually our process server was having a problem, so I could not check the same in last 4 days. Now coming to the point....
    I changed Process web service by changing authentication type as "Usernname token profile". I have not checked "Required HTTP Basic Authentication". As you said, WSDL got changed, it has removed startSession(). But when I invoke my actual operation, I am supposed to send authentication data (user name & password) in header.
    I tried to send correct authentication info in header. But still I am getting an exception.
    soapenv:Server.generalException - WSDoAllReceiver: Request does not contain required Security header
    I feel header might be going wrong. I have taken header format from web service guide. I am attaching the entire request message taht I am sending, please tell me where I am going wrong...
    <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:sim="http://bea.com/albpm/Sample/SimpProc">
    <soapenv:Header>
    <wsse:Security soapenv:mustUnderstand="1" xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wsswssecurity-secext-1.0.xsd">
    <wsu:Timestamp xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
    <wsu:Created> 2010-06-01T19:23:29.774Z </wsu:Created>
    <wsu:Expires> 2010-07-02T15:02:29.774Z </wsu:Expires>
    </wsu:Timestamp>
    <wsse:UsernameToken>
    <wsse:Username>bpr_user</wsse:Username>
    <wsse:Password Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wssusername-token-profile-1.0#PasswordText">bpruser12</wsse:Password>
    </wsse:UsernameToken>
    </wsse:Security>
    </soapenv:Header>
    <soapenv:Body>
    <sim:sayHello>
    <argInput>ss</argInput>
    </sim:sayHello>
    </soapenv:Body>
    </soapenv:Envelope>
    I cehcked with & without wsu:Timestamp. But same.....
    Please give your suggestion.
    Thanks
    Sujata

  • Error while trying to backup - Microsoft.SqlServer.SmoExtended, Error 5 (access denied)

    Hey guy,
    I have a problem with my SQL Express Server.
    If I try to backup a database I'm getting the following error:
    (Microsoft.SqlServer.SmoExtended)
    System.Data.SqlClient.SqlError: Das Sicherungsmedium 'D:\my-database.bak' kann nicht geöffnet werden. Betriebssystemfehler 5(Access denied). (Microsoft.SqlServer.Smo)
    I have done this a month ago and it worked.
    Can someone help me please?
    I am logged in as sa, the OS is Windows Server 2012 Essentials.
    Thanks
    Regards,
    Alex

    'D:\my-database.bak' kann nicht geöffnet werden. Betriebssystemfehler 5(Access denied). (Microsoft.SqlServer.Smo)
    Hi,
    Since error is access denied it means SQL server service account ,the account with which SQL Server service is running, does not have read/write privilege on folder where you are taking backup. It does not matters whether you login with SA.
    Now I see you are backing database to root(D:) drive. This should not be practiced its a bad practice and has lots of drawbacks. Instead create a folder BACKUP in D rive and give SQL Server service account read write privileges on that folder and start backup
    Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it
    My Technet Articles

  • OS command error=13, Permission denied in File Adapter

    Hi All,
    I am trying to call the OS commands in File adaper, when i check the Audit log i am getting Error exectuting the command. the same command when i check in OS its working fine.
    i have collected the debug log and i can see the message saying
    Catching #1#java.io.IOException: java.io.IOException: error=13, Permission denied
         at java.lang.UNIXProcess.<init>(UNIXProcess.java:148)
         at java.lang.ProcessImpl.start(ProcessImpl.java:65)
         at java.lang.ProcessBuilder.start(ProcessBuilder.java:451)
         at java.lang.Runtime.exec(Runtime.java:591)
         at java.lang.Runtime.exec(Runtime.java:429)
         at java.lang.Runtime.exec(Runtime.java:326)
         at com.sap.aii.af.lib.util.system.CommandLauncher.exec(CommandLauncher.java:64)
         at com.sap.aii.adapter.file.util.OSCommand.exec(OSCommand.java:58)
         at com.sap.aii.adapter.file.util.OSCommand.exec(OSCommand.java:33)
         at com.sap.aii.adapter.file.File2XI.processFileList(File2XI.java:991)
         at com.sap.aii.adapter.file.File2XI.invoke(File2XI.java:622)
         at com.sap.aii.af.lib.scheduler.JobBroker$Worker.run(JobBroker.java:500)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:169)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:266)
    I hope the problem with problem XI communication with OS level, Could you pls suggest me the problem?
    Thanks,
    Venkat

    Hello!
    You can see more information about os command using the file adapter in SAP note:
    #841704 - XI File & JDBC Adapter: Operating system command
    o  The command line of an operating system command run through the
       File and JDBC Adapter is interpreted slightly different compared
       to common operating system shells. E.g. quotes and apostrophes
       are handled differently. If in doubt, check if the command can be
       successfully run through the Java Runtime.exec(...) API. Also
       note that the command is run as user "<sid>adm" (Unix) /
       "SAPService<SID>" (Windows).
       Under Windows, this especially means that you cannot use any
       shell commands interpreted by teh command processor (such as
       "copy", "ren" or "del") using the operating system command.
    Best regards,
    Franklin

  • Linux error :13 permission denied.

    Hi ,
    When I am trying to create a database I am getting the following errors.
    ORA - 01501 Create database failed.
    ORA-00200 Control file couldn't be created.
    ORA -00202 Control file :'/disk1/oradata/DEMO/CONTROL1.ctl'
    ORA-27040 skgfrcre: create error, unable to create file.
    Linux error 13: Permission denied.
    Here I could see the directory exists.
    I have changed the permissions to chmod 6751 $ORACLE_HOME/bin/oracle.
    What else could be the possible error am I making?
    Thanks,
    Radhika.

    Hi ,
    When I am trying to create a database (change default password), using sapinst, I am getting the following errors.
    27-OCT-2006 16:16:50 * (CONNECT_DATA=(SID=SSM)(GLOBAL_NAME=SSM.WORLD)(CID=(PROGRAM=sqlplus@spank)(HOST=spank)(USER=ssmadm))) * (ADDRESS=(PROTOCOL=tcp)(HOST=192.168.23.9)(PORT=12960)) * establish * SSM * 12518
    TNS-12518: TNS:listener could not hand off client connection
    TNS-12546: TNS:permission denied
    TNS-12560: TNS:protocol adapter error
    TNS-00516: Permission denied
    Linux Error: 13: Permission denied
    What else could be the possible error am I making?
    Thanks,
    Edoardo Carletti

Maybe you are looking for

  • App store won't start

    My app store tells me I have two updates, but when I open it, it just freezes. Once I got as far as clicking on the update icon, but then the wheel in the top left just kept turning for an hour. Now all I get when I open the App Store is a big blank

  • Creating our own Thread Pool

    We have an application running on WLS6.1 with WLI2.1. We're using WLI2.1 to define workflows; we interface to the workflow definitions with custom EJB/JSP code. Without getting too detailed, we would like to spawn a thread when a user submits some of

  • Status on a PO

    Hello All - I know this seems like a simple question but does anyone have a list of the possible statuses when processing a shopping cart all the way through to invoice?  I have a purchase order that has been received and invoiced but the statuses th

  • Lightroom CC freezes on splash screen

    I've seen lots of posts about Lightroom CC crashing, but my problem seems to be different. I installed Lightroom CC through the CC app.  When I launch the app, it asks me to update my catalog.  After the "Updating Catalog" dialog finishes, it launche

  • With Computer info 11.6 r602 has stopped-- error message

    Message says Adobe FLash Player 11.6 r602 has stopped working. A probelm caused the program to stop working correctly.  Windows will close the program and notify you if a solution is available. This message has interferred with just about all web sit