The application "xxxx" cannot be launched -10810

Discussion in 'Parallels Desktop for Mac' started by ordishs, Apr 18, 2006.

  1. ordishs

    ordishs

    Messages:
    1
    I am receiving the following message:

    The application "xxxx" cannot be launched -10810

    when I try to load any new application is OS X. This seems to have started since I installed Parallels Beta 3 version on my MacBook Pro (OS X 10.4.6).

    Looking at /var/log/system.log, I can see that after a variable amount of time since rebooting, I start to get multiple entries like:

    Apr 18 16:34:07 SAOMAC /usr/libexec/bootpd: bind call failed: Address already in use
    Apr 18 16:34:07 SAOMAC /usr/libexec/bootpd: bind call failed: Address already in use
    Apr 18 16:34:07 SAOMAC /usr/libexec/bootpd: bind call failed: Address already in use
    Apr 18 16:34:07 SAOMAC /usr/libexec/bootpd: bind call failed: Address already in use
    Apr 18 16:34:07 SAOMAC /usr/libexec/bootpd: bind call failed: Address already in use
    Apr 18 16:34:07 SAOMAC /usr/libexec/bootpd: bind call failed: Address already in use
    Apr 18 16:34:07 SAOMAC /usr/libexec/bootpd: bind call failed: Address already in use
    Apr 18 16:34:07 SAOMAC /usr/libexec/bootpd: bind call failed: Address already in use
    Apr 18 16:34:07 SAOMAC /usr/libexec/bootpd: bind call failed: Address already in use
    Apr 18 16:34:07 SAOMAC /usr/libexec/bootpd: bind call failed: Address already in use
    Apr 18 16:34:07 SAOMAC /usr/libexec/bootpd: bind call failed: Address already in use
    Apr 18 16:34:07 SAOMAC /usr/libexec/bootpd: bind call failed: Address already in use
    Apr 18 16:34:07 SAOMAC /usr/libexec/bootpd: bind call failed: Address already in use
    Apr 18 16:34:07 SAOMAC /usr/libexec/bootpd: bind call failed: Address already in use
    Apr 18 16:34:07 SAOMAC /usr/libexec/bootpd: bind call failed: Address already in use
    Apr 18 16:34:07 SAOMAC /usr/libexec/bootpd: bind call failed: Address already in use
    Apr 18 16:34:07 SAOMAC /usr/libexec/bootpd: bind call failed: Address already in use
    Apr 18 16:34:07 SAOMAC /usr/libexec/bootpd: bind call failed: Address already in use
    Apr 18 16:34:07 SAOMAC /usr/libexec/bootpd: bind call failed: Address already in use
    Apr 18 16:34:07 SAOMAC /usr/libexec/bootpd: bind call failed: Address already in use
    Apr 18 16:34:07 SAOMAC /usr/libexec/bootpd: bind call failed: Address already in use

    This is then followed by hundreds of entries:

    Apr 18 16:34:12 SAOMAC kernel[0]: proc: table is full
    Apr 18 16:34:12 SAOMAC kernel[0]: proc: table is full
    Apr 18 16:34:12 SAOMAC kernel[0]: proc: table is full
    Apr 18 16:34:12 SAOMAC kernel[0]: proc: table is full
    Apr 18 16:34:12 SAOMAC kernel[0]: proc: table is full
    Apr 18 16:34:12 SAOMAC kernel[0]: proc: table is full
    Apr 18 16:34:12 SAOMAC kernel[0]: proc: table is full
    Apr 18 16:34:12 SAOMAC kernel[0]: proc: table is full
    Apr 18 16:34:12 SAOMAC kernel[0]: proc: table is full
    Apr 18 16:34:12 SAOMAC kernel[0]: proc: table is full
    Apr 18 16:34:12 SAOMAC kernel[0]: proc: table is full
    Apr 18 16:34:12 SAOMAC kernel[0]: proc: table is full
    Apr 18 16:34:12 SAOMAC kernel[0]: proc: table is full
    Apr 18 16:34:12 SAOMAC kernel[0]: proc: table is full
    Apr 18 16:34:12 SAOMAC kernel[0]: proc: table is full
    Apr 18 16:34:12 SAOMAC kernel[0]: proc: table is full
    Apr 18 16:34:12 SAOMAC kernel[0]: proc: table is full
    Apr 18 16:34:12 SAOMAC kernel[0]: proc: table is full
    Apr 18 16:34:12 SAOMAC kernel[0]: proc: table is full
    Apr 18 16:34:12 SAOMAC kernel[0]: proc: table is full
    Apr 18 16:34:12 SAOMAC kernel[0]: proc: table is full
    Apr 18 16:34:12 SAOMAC kernel[0]: proc: table is full
    Apr 18 16:34:12 SAOMAC kernel[0]: proc: table is full
    Apr 18 16:34:12 SAOMAC kernel[0]: proc: table is full
    Apr 18 16:34:12 SAOMAC kernel[0]: proc: table is full
    Apr 18 16:34:12 SAOMAC kernel[0]: proc: table is full
    Apr 18 16:34:12 SAOMAC kernel[0]: proc: table is full
    Apr 18 16:34:12 SAOMAC kernel[0]: proc: table is full
    Apr 18 16:34:12 SAOMAC kernel[0]: proc: table is full

    The only solution is to hard reboot.

    This happens even if I do NOT run Parallels on my machine.

    Is it possible that there are some Extensions loaded by the Parallels installer that are causing this to happen?

    Has anyone else seen this problem?
     
  2. Andrew @ Parallels

    Andrew @ Parallels Parallels Developers

    Messages:
    1,507
    Thanks for reporting - we'll investigate this issue.
     
  3. bketelsen

    bketelsen Bit Poster

    Messages:
    9
    -10810 suddenly

    I've been using parallels for a week or so, but only in the last day or two quite heavily. Now I'm getting this -10810 error when I try to open any application. I can often close an app in order to open another, so it seems as if a maximim number of processes has been reached somehow.

    I have installed parallels and HP printer drivers since unpacking this mac from the factory, so it is a pretty fresh machine. Trying to launch Terminal simply brings up an empty window that says "Completed Command". Very frustrating. I think I'm going to have to try a fresh install of Tiger.

    Machine : Mac Mini 1.66 CDuo 1.25 GB RAM
     
  4. chrismasto

    chrismasto

    Messages:
    27
    If you can get a terminal open, try running "top -u". You'll probably quickly discover what's filling up your process table. In the past I've seen smbd (samba aka Windows file sharing) do it.
     
  5. neosublime

    neosublime

    Messages:
    62
    I had the same problems this morning on my 2GHz MacBook Pro. I have a 20" iMac as well, but have not had this problem. The MBP is using the virtual NIC, and the iMac is using bridged.

    The problem was so bad, I reinstalled my OS to fix the problem. I also reinstalled Parallels, and so far everything is fine.
     
  6. bketelsen

    bketelsen Bit Poster

    Messages:
    9
    Reinstall

    I couldn't even get a terminal window to open, nor could I view the console. I ended up reinstalling Tiger. I'll reinstall Parallels tonight and see if the issue returns. To keep it scientific, I'll do the Software Update on the mac so I'll have a fresh/virgin install of 10.4.6 and then I'll only install Parallels. I have other machines I can use for a while so I can isolate this problem.
     
  7. neosublime

    neosublime

    Messages:
    62
    Well after my Tiger reinstall, and reinstalling all updates, and software, I started to have more of the same problem. So I uninstalled the RC, Parallels tools, and all preferences. Installed Beta 6, and so far... thing are working much better. No broken networking, or strange app errors. I will continue to test it more.

    Testing on 2 machines. MBP 2.0GHz/iMac 2.0GHz.
     

Share This Page