Parallels Workstation is unable to communicate...

D

dhjdhj

Hunter
Out of the blue....I just booted up my laptop, tried to run Parallels and it popped up the message



Parallels Workstation is unable to communicate with application drivers. Please shutdown all the application sessions and re-boot your computer. If rebooting does not help, re-install the application.


Nothing else was running - as I said, I just booted the machine and the first thing I did was to run PW. Obviously I will try the suggestion to reboot (there are no application sessions running) but it would be good to know what happened here and why.

David
 
Update: after clicking the ABORT button, just for grins I just tried running PW again and it started perfectly!!! I'm therefore now wondering whether this problem is really due to trying to run PW too quickly after booting up the Mac. Is it possible that some services are not yet initialized, etc? If this is the problem, then (a) the error message needs to be corrected to so inform the user and (b) how would one deal with the situation where PW is configured to start automatically after the Mac is booted (sleep for x seconds?)
D




dhjdhj said:
Out of the blue....I just booted up my laptop, tried to run Parallels and it popped up the message



Parallels Workstation is unable to communicate with application drivers. Please shutdown all the application sessions and re-boot your computer. If rebooting does not help, re-install the application.


Nothing else was running - as I said, I just booted the machine and the first thing I did was to run PW. Obviously I will try the suggestion to reboot (there are no application sessions running) but it would be good to know what happened here and why.

David
Click to expand...
 
Any update on why this error (which required restarting the VM, although not OS X) occurred?
dhjdhj said:
Parallels Workstation is unable to communicate with application drivers. Please shutdown all the application sessions and re-boot your computer. If rebooting does not help, re-install the application.
Click to expand...
 
Sometimes this happen, our drivers are started by non standard way because we need some "extra" initialization. And our drivers may start a little bit later after system startup.
 
Well, I'm not sure how to control "sometimes" but if it can't be fixed, then at least the error message should be changed so that it simply suggests starting the VM again rather than rebooting OS X.
D

ms @ parallels said:
Sometimes this happen, our drivers are started by non standard way because we need some "extra" initialization. And our drivers may start a little bit later after system startup.
Click to expand...
 
You must log in or register to reply here.
Back
Top