-
Notifications
You must be signed in to change notification settings - Fork 12
Plug-In install fails Maya 2017 #22
Comments
Looks like you don't have PIP - do you have Python installed? Recent versions of Python include Pip. |
Having an installation of Python/Pip is not required - the plugin should add a copy of pip into a Maya scripts directory in order for it to install additional dependencies. Could you check what directories and files are present in: |
Hi There, I am having a similar issue with Maya2018 Mac: // Error: file: /Applications/Autodesk/maya2018/Maya.app/Contents/scripts/others/pluginWin.mel line 290: ImportError: file /Users/peter.day/Downloads/azure-batch-maya-master/azure_batch_maya/plug-in/AzureBatch.py line 477: Failed to install dependencies - please install manually // Any advice would be great? Many Thanks |
Hi @Petewday - we've resolved one of the causes of this issue and released v0.16.0 - give this a go and let us know if you're still having difficulties! |
Thanks for letting me not about the updated plugin. I have tested it on 2 machines this morning and get pretty much the same error: /Applications/Autodesk/maya2018/Maya.app/Contents/bin/../Frameworks/Python.framework/Versions/Current/Resources/Python.app/Contents/MacOS/Python: can't open file '/Users/richard.todd/Desktop/azure_batch_maya/scripts/tools/install_pip.py': [Errno 2] No such file or directory Failed to install Pip. Please install dependencies manually to continue. Is there anything I could be doing wrong? I have followed the steps from guide. Thanks Pete |
Thanks @Petewday - can you confirm whether the following file exists? If it does - could it possibly be some kind of permissions issue? Would seem unlikely if the files are on the User desktop.... Though maybe Maya does not have permission to execute scripts on the desktop. |
This was resolved by sbuckley010 deleting the folder "Users<username>\AppData\Local\Temp\azure-batch-maya". Have logged a separate issue into needing to version this file as that should prevent this situation. |
Hello @annatisch, a customer reports exactly the same issue than the one Petewday experiences... // Error: file: /Applications/Autodesk/maya2018/plug-ins/xgen/scripts/xgmToolRegistration.mel line 58: Cannot find procedure 'xgmToolManagerRegisterTool'. //
Applications/Autodesk/maya2018/Maya.app/Contents/bin/../Frameworks/Python.framework/Versions/Current/Resources/Python.app/Contents/MacOS/Python: can't open file '/Users/peter.day/Downloads/azure-batch-maya-master/azure_batch_maya/scripts/tools/install_pip.py': [Errno 2] No such file or directory Failed to install Pip. Please install dependencies manually to continue. ***// Error: file: /Applications/Autodesk/maya2018/Maya.app/Contents/scripts/others/pluginWin.mel line 905: RuntimeError: file /Users/peter.day/Downloads/azure_batch_maya 2/plug-in/AzureBatch.py line 457: Failed to install pip // ***
// Error: file: /Applications/Autodesk/maya2018/Maya.app/Contents/scripts/others/pluginWin.mel line 905: (AzureBatch) // file please could you advise on how deal with a potential permission issue? Thank you in advance, /*Karl |
Hi @karlti - I haven't been able to reproduce this particular error - however I encountered a variety of other errors on my Mac due to out-of-date SSL libraries. As a result I've been forced to refactor some of the installation script which I'm hoping might solve your issue as well. |
Thank you very much, dear @annatisch :) |
Hello Anna, |
Happy new Year! are there any news on this OSX Plug-In issue? Thank you. |
Happy new year @karlti! |
Yep, Happy New Year you too, @annatisch! Thanks & Enjoy! |
@karlti - The fixes are now released :) |
Hi @annatisch . I think, we forgot to clean the plugin stuff from 'azure-batch-libs', so i advised him to do so today. In the meantime, i checked a little bit around & sent him instructions how he can manually run "getpip.py" from his maya python env (hopefully i got it right...). I am awaiting his feedback... btw he has "Maya2018", does this matter? regards, |
Thanks @karlti - I do find it odd that the error would be exactly the same. Regarding Maya 2018 - this should have no impact on the install process (it's what I'm using on my mac), however the VM images are currently running Maya 2017. I believe the team that builds the rendering service is publishing a new image - @davidkydd should be able to give you a time frame. |
Hi @karlti we are aiming to have the new images out which include maya2018 in the next couple of weeks. |
Thanks @davidkydd |
I've been trying to install the plug in but keep getting this error:
updateRendererUI;
Initializing Azure Batch plug-in
Checking for dependencies...
Unable to load pathlib==1.0.1: No module named pathlib
Unable to load futures==3.1.1: No module named concurrent.futures
Unable to load msrestazure==0.4.11: No module named msrestazure
Unable to load azure-common==1.1.8: No module named azure.common
Unable to load azure-mgmt-storage==1.0.0: No module named azure.mgmt.storage
Unable to load azure-batch-extensions==0.2.0: No module named azure.batch_extensions
Unable to load azure-storage==0.32.0: No module named azure.storage
Unable to load azure-batch==3.0.0: No module named azure.batch
Unable to load azure-mgmt-batch==4.0.0: No module named azure.mgmt.batch
Attempting to install dependencies via Pip.
Traceback (most recent call last):
File "Z:\Treanor_Paul\scripts\AzureBatch_Maya_Plugin-v0.14.0\azure_batch_maya\scripts\tools\install_pip.py", line 30, in
import pip
ImportError: No module named pip
Failed to install Pip. Please install dependencies manually to continue.
// Error: file: C:/Program Files/Autodesk/Maya2016/scripts/others/pluginWin.mel line 781: RuntimeError: file C:/Users/treanop/Documents/maya/scripts/AzureBatch_Maya_Plugin-v0.14.0/azure_batch_maya/plug-in/AzureBatch.py line 461: Failed to install pip //
// Warning: file: C:/Program Files/Autodesk/Maya2016/scripts/others/pluginWin.mel line 781: Failed to call script initialize function //
// Error: file: C:/Program Files/Autodesk/Maya2016/scripts/others/pluginWin.mel line 781: (AzureBatch) //
The text was updated successfully, but these errors were encountered: