One of our nodes is failing to start Render Manager with this error. It started spontaneously a few weeks ago and so far the rest of our farm is unaffected. The node is definitely connected to the network, it’s able to ping other machines just fine and I am currently connected to it myself. I tried resetting the network adapters and updating Pulze but so far we’re not having any luck.
Any ideas? I can send logs to the developers in a DM or email.
-Josh
Hi, we have had the same problem with one of our farms, we have tried different things to fix it and in the end the only one that solved the problem was to format the machine and reinstall windows again.
Things we have tried without solving the problem:
Change the ip from dynamic to fixed.
Change the user by creating a new one.
Resetting the network adapter.
Buy a new network card with a different chip (the one on the motherboard was realtek and we bought a PCI-E with Intel chip.
Update the driver version of the integrated network card and the one purchased afterwards.
Repairing windows installation.
Install and uninstall pulze and its plugin ( scene manager in our case ).
In the end the only solution we found was to format the machine.
As additional information, say that if the machine has installed Windows 11 Home edition, gives many synchronization problems, we changed to Windows 11 Pro and disappeared (at least for now) desynchronization problems almost entirely (I know it is information regarding another problem but maybe it will help you).
Good luck in your attempt to fix it!
Yikes, thank you for the insight @licencias. I’ll update this thread if we get any results here.
Unfortunately, we also had to reformat this node and re-install all applications. But it seems to be working after that.
We did the same as I told you in my previous post to solve it, the problem is that now sometimes 3ds max crashes and pulze doesn’t recognise it, in that case you have to restart the program in the affected node (farm).
Any ability to troubleshoot here? I had a user on our team that encountered this once they had installed Render Manager last week. We saw the comments above that only a reformat of the device fixed it, so we built and assigned him a new machine - same error immediately appears when installing Pulze on the new laptop.
I’ve got at least 2 users with this issue on a 10-person team & they are both dead in the water.
Help!
Did anyody ever get to the bottom of this issue? We have just run into it today for the first time. The machine in question was happily running Pulze for many months before suddenly exhibiting this behavior. So far we’ve tried the uninstall/reinstall with no joy, but I REALLY don’t want to have to reformat the machine.
Thanks in advance
No luck here just yet.
One of the people I mentioned above moved to a brand new laptop and the issue persists, which is troubling.
@bnuttall The only way we could solve it was a reformat and re-install of Windows. No clue what caused the issue in the first place but it is clearly something deep-rooted. Wouldn’t surprise me if it’s in the registry, we tried VERY hard to track down any pulze directories on disk and manually delete them afte uninstalling.
I too ended up going down the format and reinstall route. Extremely annoying!
Unfortunately in our case, even supplying a brand new laptop to a user didn’t work.
When you uninstall the Pulze application, files containing settings still remain in the folder %Appdata%\Pulze Service.
If you initially entered incorrect network settings (like gateway), or settings were somehow corrupted, they are saved in one of these files.
Usually, there’s no need to reinstall Windows; cleaning out %Appdata%\Pulze Service folder, relaunching Pulze, and entering the correct settings again will suffice.
Sometimes, when you have multiple network adapters, Pulze loses the correct network adapter, or it might initially fail to register the proper network adapter in the settings.
In a similar situation, аfter the initial setup of the farm, I just copied the files myDevice.json and another one (can’t remember which exactly), from a properly working node to the problematic ones, manually edited them by replacing the IP addresses, macs, network adapter names, prefered interface, etc… and then made those files read-only.