You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Trying to set the Python path to a virtual environment results in an exception when using the Load Script activity: "There was no endpoint listening at net.pipe://localhost/UiPath.Service/Host_IPythonService_13976 that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details. ----> System.IO.PipeException: The pipe endpoint 'net.pipe://localhost/UiPath.Service/Host_IPythonService_13976' could not be found on your local machine."
To Reproduce
Steps to reproduce the behavior:
Add a Python Scope activity
Set the path to a virtual environment
Use the Load Script activity
See error
Expected behavior
Should work just like when providing the system Python path
The text was updated successfully, but these errors were encountered:
andumorie
changed the title
Python activities do not work with virtual environments
Python: Python activities do not work with virtual environments
Jan 21, 2019
Describe the bug
Trying to set the Python path to a virtual environment results in an exception when using the Load Script activity: "There was no endpoint listening at net.pipe://localhost/UiPath.Service/Host_IPythonService_13976 that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details. ----> System.IO.PipeException: The pipe endpoint 'net.pipe://localhost/UiPath.Service/Host_IPythonService_13976' could not be found on your local machine."
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Should work just like when providing the system Python path
Screenshots
http://prntscr.com/ma29e6
Additional context
Example workflow to reproduce: https://drive.google.com/open?id=1S-RYuGmxN6vWDlWANnVEJcSzF7oaclI_
The text was updated successfully, but these errors were encountered: