@partofthething, based on your comment, I'm not sure how extensive your xcopy , but it is possible that you are missing some Python libraries.
For example, if you used the standard Python installer and Python C:\Python27 was installed, you should also have C:\Windows\System32\python27.dll or C:\Windows\SysWOW64\python27.dll . You can copy them to the root directory of your python installation and then run from a network drive without any problems, but otherwise they will be available for discovery in C:\Windows\* .
The above should work no matter what, but I have some theories of what could happen:
You may have chosen a custom installation directory - . It doesnβt make much sense, but you can somehow imagine it in Python, which you copy to the network (i.e. you installed in C:\Python27-64 , and this does not exist on the HPC server).
DLLs were completely absent - I doubt they were missing, because then you should get a message that says:
The program failed to start because python27.dll was missing on your computer. Try reinstalling the program to fix this problem.
Dlls were the wrong architecture . I failed (lacked patience) to install Python 2.7.2, but I was able to get python 2.7. 8 with a more reasonable error 0xc000007b ( STATUS_INVALID_IMAGE_FORMAT ), forcing it to use 32-bit DLLs with 64-bit Python.
source share