Hello there,
our system was rendering fine over the weekend…and suddenly stopped. The workers won’t launch, monitor won’t launch, nothing. Tried reinstall - getting an “deadlinecommand.exe -py -ver 2 PopulatePythonSync” error. On all machine, tried a laptop with a fresh OS and no connection to our repository, same error.
Something happend or what is going on here?
reverted back to 21.4 , installed an all machines…and everything works as before. Anyone knows whats different in 22.4 for all the sudden errors and being unable to install?
same here…need to roll back to 10.1.21.4
I just open a thinkbox support ticket, i invite you to do the same…
I got the same here as well when doing update as well.
To give some news here, since i open a ticket about this…
thinkbox team is on it…
Same here, Deadline won’t start on ANY machine we have… not the worker, not the monitor, not the launcher.
[10.1.22.4]
Same issue here! running on popos 22.04
multiple locations reporting this issue, including my local (upgrade) install.
had tested this stuff was all working fine, now can’t launch. Checked on a client and closed Deadline but couldn’t re-open, same error.
is this a certificate or similar date related error?
=======================================================
Log
=======================================================
2022-07-11 01:23:53: 0: Loading Job's Plugin timeout is Disabled
2022-07-11 01:23:53: 0: SandboxedPlugin: Render Job As User disabled, running as current user 'render'
2022-07-11 01:23:54: 0: Unhandled exception. System.Exception: Exception of type 'System.Exception' was thrown.
2022-07-11 01:23:54: 0: at DeadlinePython.DeadlineSandboxAppStartup.Main(String[]
args)
I thought my PC was wrong 
Same here with multiple locations. It is something related with date/certificate. I’ve changed the date on the Client without changing anything on the Repository and Deadline is running again.
Interesting, yes it felt something like the effect year 2.000 haha
Hopefully we can get a patch soon some how, we need it for max 2023 and the previous version wasn’t working for us
replacing all the dll files in c:\Program Files\Thinkbox\Deadline10\bin\
from deadline.dll to deadlineworker.dll and franticx.dll with 10.1.21 versions on workers allows them to pick-up again (still need to kill those processes on workers to do that).
What did you change the date to?
Same for us, we’re reverting back to the last working version for us (10.1.16.9)
Ok here some news (non offical) => thinkbox is aware of the issue with dEadline 10.1.22.4
"
the Deadline 10.1.22.4 is broken and this is reported as a high severity issue to our devs. They are working on this but we won’t be able to give an ETA as of now.
The workaround we have figured yet here is to downgrade Deadline to 10.1.21.4, here is a documentation for downgrading: (Upgrading or Downgrading Deadline — Deadline 10.1.22.4 documentation)
Look forward to Deadline release notes for future bug fixtures and feature releases: (Release History — Deadline 10.1.22.4 documentation)
"
We did find this morning that the Deadline 10.1.22.4 is broken and reported this issue as a high severity to our devs. They are working on this but we won’t be able to give an ETA as of now.
The workaround we have figured yet here is to downgrade Deadline to 10.1.21.4, here is a documentation for downgrading: (Upgrading or Downgrading Deadline — Deadline 10.1.22.4 documentation)
Look forward to Deadline release notes for future bug fixtures and feature releases: (Release History — Deadline 10.1.22.4 documentation)
Is there a way we could receive an email when the new version is released instead of having to check the Release History every day to see if/when the fix is released? I’ve signed up for a number of email lists through the Thinkbox website but none of them have worked, and this is exactly the sort of time when such a feature is needed.
The beginning of the month worked. However this is not great method since it can break access to Windows shares if the difference in time is too big between server and client.
Agreed; plus it changes the write date/times for render files which makes file sorting/organization extremely confusing.
Hey all, the problem is root cased and we’re actively working on a new build. We have a bit of testing to do before releasing it so bear with us but you shouldn’t have to wait long (days, not weeks). Noted on the mailing list, and Canada’s anti-spam legislation is a pain. I’ll have the team respond to tickets when we’ve got the build out and we’ll post again here. @karpreet is owning the bulk of them.
For some background, a component was incorrectly included in the build which time limited the software to expire on July 9th. The issue prevents any further execution of the software after July 9th and requires a roll back to a previous version to address.