LabPython migration issues from windows 10 to windows server 2019

[viSci]

Greetings, a long running LV 2018/2020 app was recently migrated to run on windows server 2019 and am finding that I can no longer initialize the python script server. 

I have verified that my python 2.7.6 (32 bit) is installed correctly (BTW, it coexists with python 3.1 which needs to be on the machine for another non LV app).

I have tried the usual things like running as admin, checking folder permissions, etc to no avail.

Any ideas?

Edited June 9, 2023 by viSci

[LogMAN]

Your image is broken for me because it resides in your gmail account. Can you attach it directly to your post?

Did you add Python 2.7 to the PATH environment variable? Also make sure only one version is added to PATH, otherwise it may lookup the wrong version. This was the reason for me in the past.

[viSci]

 

[Rolf Kalbermatter]

Well so long ago. I would have to look into the code to see if it could actually even cause this error from not being able to locate the Python kernel. I kind of doubt it.

What might be more likely the problem is the lack of the correct MSC C Runtime library. Although a quick check seems to indicate that it was compiled with MSVC 6.0 which did not have this cumbersome C compiler version specific runtime support library issues. Not having a Windows Server 2019 installation available it is also a bit of a trouble to try to debug this.

[viSci]

Later this afternoon I plan on remoting into the server.  Could you suggest a specific MSC runtime to try?

[Rolf Kalbermatter]

16 minutes ago, viSci said:

Later this afternoon I plan on remoting into the server.  Could you suggest a specific MSC runtime to try?

No, Microsoft Visual C 6.0 still used the standard Windows C Runtime MSVCRT.DLL which should be available in every Windows version since 3.0. Or maybe it is not anymore in Windows Server 2019??

Try to see if you can find MSVCRT.DLL in SysWow64.

Edited June 9, 2023 by Rolf Kalbermatter

[LogMAN]

Not sure if this is relevant but there appears to be an issue with the file paths when loading the script node. The debugging window is displayed when placing the node on the block diagram (notice the unreadable characters in the file extension):

It often results in a crash but when it doesn't you get another debugging window when executing the VI:

It also reports the same error code as the one mentioned above:

This is running on Windows 11 using LabVIEW 2013 (32-bit) and Python 2.7 (registered in PATH) with the latest version of LabPython from VIPM. msvcrt.dll is available in SysWOW64 and System32 (part of Windows).

Not sure what causes the issue but at the very least it doesn't appear to be isolated to Windows Server 2019 🤷‍♂️

Edited June 9, 2023 by LogMAN