Jupyter server fails to start pycharm

I have installed PyCharm Professional and I want to run Jupyter notebook in it, but whenever I try to run a cell, a message appears saying Jupyter server stopped with this message error:

Jupyter server process finishedTraceback (most recent call last):
File "C:\ProgramData\Miniconda3\envs\untitled\Scripts\jupyter-notebook-script.py", line 6, in
from notebook.notebookapp import main
File "C:\ProgramData\Miniconda3\envs\untitled\lib\site-packages\notebook\notebookapp.py", line 49, in
from zmq.eventloop import ioloop
File "C:\ProgramData\Miniconda3\envs\untitled\lib\site-packages\zmq\__init__.py", line 47, in
from zmq import backend
File "C:\ProgramData\Miniconda3\envs\untitled\lib\site-packages\zmq\backend\__init__.py", line 40, in
reraise(*exc_info)
File "C:\ProgramData\Miniconda3\envs\untitled\lib\site-packages\zmq\utils\sixcerpt.py", line 34, in reraise
raise value
File "C:\ProgramData\Miniconda3\envs\untitled\lib\site-packages\zmq\backend\__init__.py", line 27, in
_ns = select_backend(first)
File "C:\ProgramData\Miniconda3\envs\untitled\lib\site-packages\zmq\backend\select.py", line 35, in select_backend
reraise(ImportError, ImportError("Importing %s failed with %s" % (name, e)), exc_info[2])
File "C:\ProgramData\Miniconda3\envs\untitled\lib\site-packages\zmq\utils\sixcerpt.py", line 33, in reraise
raise value.with_traceback(tb)
File "C:\ProgramData\Miniconda3\envs\untitled\lib\site-packages\zmq\backend\select.py", line 28, in select_backend
mod = __import__(name, fromlist=public_api)
ImportError: Importing zmq.backend.cython failed with invalid syntax (__init__.py, line 5)

I can run jupyter in the command prompt, and even in the pycharm terminal, but when i try to run in in pycharm, with the 2 "managed jupyter server:autostart" it just doesn´t work

Reproduce the managed Jupyter server launch in PyCharm with the reported Miniconda environment, then start with notebook/notebookapp.py and zmq/backend/select.py from the traceback. Compare that launch with the working command-prompt and terminal launches; done means the environment-specific startup failure is explained and the issue has a verified resolution or clear documentation.

Written by the indexing model from the issue text.