Unable to connect to Parallels Service.

I'm getting the following error:
Unable to connect to Parallels Service.
Make sure that prl_disp_service is running check your
firewall settings. If the problem persists, contact the
Parallels support team for assistance.

I tried uninstalling and reinstalling PDFM 4 from the latest
.dmg (ParallelsDesktop-parallels-en_US-4.0.3844.408728.dmg)
without success.

I also checked the firewall settings - Allow all incoming
connections is selected.

Thanks,
Charles

 

Charles,

Have you tried rebooting your Mac? If not, please try, this might help.

If it still doesn't help, please provide us with the following information:
1. When finished installing, do you see "Installation Succeeded" message from installer?
2. Do you start Parallels Desktop from shortcut in Dock, or from shortcut on your Desktop, or from Applications->Parallels?
3. If you had Parallels Desktop installed before 3844, what was the build number?

Thank you

 

Unable to connect to Parallels Service

I have the same problem in that I cannot auto-start a Parallels virtual machine at login time by making it (the .pvm file) a login item. This is on a clean instalation of Mac OS 10.5 with all OS patches and Parallels build 3844. It persists across a reboot and does not change with the firewall switched off.

Launching the virtual machine from its pvm file a few seconds later works fine, so I suspect there is something that needs to be waited for before allowing a pvm to start up in a login item.

 

prl_dsp_service not started

Hi,

I'm experiencing the same problem. I've installed Prallels and it worked fine (allthough starting my Boot Camp partition took ages). I tried to make a clean install by uninstalling both Parallels and VMware Fusion. Rebooted a few times, checked permissions a few times and made sure, that nothing of my older Parallels installations were left on my system. After that I installed Parallels again (latest version from the website). The installation was successful according to the installer.

When I start Parallels now, I always get the message the original poster gets too. I checked for loaded kernel modules:

sudo kextstat | grep -i prl_ -> no result

I checked for running processes:

ps -efa | grep -i par -> no result (except the Parallels.app, throwing the alert)
ps -efa | grep -i prl -> no result

So it seems to me, that Parallels isn't started correctly, especially not the prl_disp_service. If I start the service and load the kernel modules manually, Parallels starts.

Any clues?

Best regards,
m.h.

 

Have you checked this KB?

 

Kb 5791

Doesn't help, as I assumed. The problem seems to be, that the service isn't started. The error in system.log is:

com.apple.launchd[165] ([0x0-0x1e01e].com.parallels.desktop.console[237]): Exited with exit code: 5

The Installer logs this to system.log:

[0x0-0x44044].com.apple.installer[9406]: Parallels CPU Check Tool
[0x0-0x44044].com.apple.installer[9406]: CPU Vendor: Intel
[0x0-0x44044].com.apple.installer[9406]: Hardware Virtualization: PRESENTED (VT-x)
[0x0-0x44044].com.apple.installer[9406]: Summary: Your CPU can run Virtual Machines
Installer[9406]: P CFR: Direction: 0
Installer[9406]: P CFRv: Go to next
Installer[9406]: P CFR: Direction: 0
Installer[9406]: P CFR: Go to next
Installer[9406]: P CFR: Direction: 1
Installer[9406]: P CFR: Go to prev
Installer[9406]: P CFR: Direction: 1
Installer[9406]: P CFRv: Go to prev
Installer[9406]: P CFR: Direction: 0
Installer[9406]: P CFRv: Go to next
Installer[9406]: P CFR: Direction: 0
Installer[9406]: P CFR: Go to next
Installer[9406]: Could not find image named 'reboot-icon'.
Installer[9406]: P IRR: Direction: 0
Installer[9406]: drvcheck.py: Missing kernel extensions are: ['com.parallels.kext.prl_vnic', 'com.parallels.kext.prl_netbridge']\nTest test_driver_set failed

Installer[9406]: P IRR: Required, block all buttons

No errors in install.log or any other log.

Bye,
m.h.

 

Problem resolved (at least on my system)

Hi,

shame on me. It was all my fault. I've set

PARALLELS = -NO-

under /etc/hostconfig, therefore the service wasn't started at boot.
After reactivating the service, everything is OK. I shouldn't fiddle with my system, while having a glass of wine .

Bye,
m.h.