Mysterious trouble with PD12 on macOS Sierra

Hi. I have a problem with Parallels Desktop 12 on macOS Sierra.
After successful installation of PD on a clean-installed macOS I launch PD and it gets stuck on a loading circle for about 30 seconds, then quits without any error messages. I tried deleting it, reinstalling it, re-downloading it, deleting all the files i found with

Code:

sudo find / -name *parallels*

and reinstalling again. Sadly, nothing helped.

Parallels.log file is attached. I think, that the most interesting part of that file are the 4 following lines (guess it is quite obvious):

Code:

11-06 23:12:50.945 F /IOCommunication:4434:65827/ IO client ctx [read thr] (sender 3): Can't connect to socket:
11-06 23:12:50.945 F /IOCommunication:4434:65827/ IO client ctx [read thr] (sender 3): ERRORS BEGIN
11-06 23:12:50.945 F /IOCommunication:4434:65827/ IO client ctx [read thr] (sender 3): Error for socket ai_family = 1, ai_socktype = 1, ai_protocol = 0 in code line #2194, native error: No such file or directory [errno: 2]
11-06 23:12:50.945 F /IOCommunication:4434:65827/ IO client ctx [read thr] (sender 3): ERRORS END

Really hope for help here, can't live without Parallels Desktop

 

UPD:
I've tried reopening PD for like 30 times consequently and it randomly opened once, and was fully functional. However, after 5 seconds since its launch I got something like a critical error message and was offered to send a report (i zipped that report, but it is 2.2MB in size and i can't attach it). Nevertheless, this error did not affect the app operability in ANY way.

 

Hey @Aleksej1,
In order to resolve the issue, please follow the steps.

 

I'm afraid that is absolutely impossible for me to do, due to the fact that i don't have any virtual machines installed yet. Also, I don't have prl_vm_app process running.

I would be grateful for any further responses considering my issue, though.

 

Please open Activity Monitor from your Mac then quit Parallels Desktop and any "prl_" services.

 

I have the same problem
https://forum.parallels.com/threads/cant-open-parallels-desktop.338800/

 

Hey, we've replied you on the thread above, please check and reply.

 

Hey, did you perform the suggested steps?

 

I have tried to, but there are no prl_ services.

When I type ps aux | grep prl in terminal I get the following

Code:

mrkn             3829   0,0  0,0  2433664   1164 s001  S+    2:59     0:00.00 grep prl

I tried to reinstall PD again. I used PDremove.app and then entered sudo find / -name parallels in terminal and deleted every found item with sudo rm -rf. Than I rebooted my Mac, installed PD, rebooted again, wiped Parallels.log and opened the app. After all that my Parallels.log file consists mostly of this repeating lines:

Code:

01-07 02:47:44.089 F /sdk:3252:31711/ Can't connect to dispatcher!
01-07 02:47:46.071 F /IOCommunication:3252:31603/ IO client ctx [read thr] (sender 3): Can't connect to socket:
01-07 02:47:46.071 F /IOCommunication:3252:31603/ IO client ctx [read thr] (sender 3): ERRORS BEGIN
01-07 02:47:46.071 F /IOCommunication:3252:31603/ IO client ctx [read thr] (sender 3): Error for socket ai_family = 1, ai_socktype = 1, ai_protocol = 0 in code line #2194, native error: No such file or directory [errno: 2]
01-07 02:47:46.071 F /IOCommunication:3252:31603/ IO client ctx [read thr] (sender 3): ERRORS END

I am REALLY looking forward to solving this problem.

 

Hi, please follow the steps as suggested in the article and keep us updated on your progress.

 

It helped, thank you a lot!
Was it a macOS Sierra bug or a PD problem?

 

Glad to know that your Parallels Desktop issue has been resolved. The main reason behind this issue was wrong permissions to the necessary folder on the Mac side.

 

I have the same problem after upgrading to sierra 10.12.5. I've checked all the links and solutions proposed.
Could anyone help me?

 

It's solved. I've uninstalled again parallels, and this time I've deleted the folder Parallels inside /Libraries/Preferences/.
I don't know why, but it works!

 

Glad to know that you were able to resolve the issue. But in case it re-occurs, please get back to us.