Does your admin or whomever sets up machines have a list or template for what is added to each workstation on a fresh install?
As it isn’t related to environment variables, it must be elsewhere and I’m thinking it might be a Windows update of sorts.
If you could get a list of things added to your system, or screenshot your “Add and Remove Programs” dialog, we might get a clue as to which one is causing the issue.
One last thing, when you launch Nuke etc. from this clean environment, you were running nuke.exe directly, and not one of your wrappers? It’s important nothing else is added so we know where to look.
So the only problem really is getting .setup() to run when launching a host? That is odd. Since the port is being set, the function clearly runs, but must be killed shortly afterwards… Hmm.
To confirm, this works well for you, on the machine you’re having trouble with?
It’s using the Python shipping with the Pyblish installer, I think it’s pyblish-win\bin for you.
The second time, Pyblish QML is already running (in the background, from having been started during the first time) and a connection is made in an attempt to communicate with it.
It sounds like it’s this connection that causes the issue.
In this case, it does sound like it might be related to your domain login, as it’s a permission issue. We tried before to run things as admin, but that didn’t change anything?
Could you try running this again, but with administrator terminals? You can run the terminal as an administrator by right-clicking on c:\windows\cmd.exe and running it as an admin, amongst other ways.
It is… I can’t make heads or tails of it. Does it give you linear numbers? Like 6001, 6002. That is, it doesn’t skip numbers, like 6001, 6003, 6007 etc.
I’m thinking it must have something to do with permissions and that you are within a domain. That being “admin” isn’t truly admin, as your user might still be restricted to a certain set of rules.
I’m not familiar enough with domains to know for sure, but if you have anyone you could ask, ask if there are any port-restrictions. Especially at 6001 and above. And if you could try temporarily allowing those ports to see whether you still experience the problem.
The really good news is that we’ve narrowed it down into a reproducible problem. I think we’re close to solving it once and for all.
Looks like you’re got processes running that is using ports Pyblish is attempting to use. This would explain the permission errors.
There isn’t any way of altering these ports programatically, but there should be. I’ll have a look at implementing this, but in the meantime, could you try altering this line, to something different, like 7001?
Ports range from 0-49151, so there are plenty to choose from. A few are reserved and, as we’ve seen, used by other apps so it’s important to get this feature implemented QML-side.