After we updated to Deadline 6.1 we got problems with the deadline monitor on some of our workstations. It either shows no blades, or it shows just parts of the information about the blades.
If we try to look at the tasks on a job in progress it just says “Loading tasks…”
After the render is done everything lists fine… Since this only happens on a couple of our workstations I am guessing it is not server side, but it started happening after the update from 6.0 to 6.1…
My own workstation is one of the computers having trouble. I let the monitor stay open over night and everything was listed as normal this morning. After I submitted a new job all the blades disappeared and now after a couple of hours the information in the attached screenshot shows.
Here’s the screen shot of the issue. We do have 47 blades + our workstations when the full list is shown.
i.imgur.com/hCRapn7.png
Hello,
Can I have you open the console(View, new panel, console) and see if there is anything in there? Thanks.
Cheers,
Hi, sure. Here it is.
[code]2014-02-26 07:08:53: Deadline Monitor 6.1 [v6.1.0.54665 R]
2014-02-26 07:08:53: Time to initialize: 920.000 ms
2014-02-26 07:08:53: Time to connect to Repository: 3.151 s
2014-02-26 07:08:53: Time to check user account: 31.000 ms
2014-02-26 07:08:53: Time to purge old logs: 16.000 ms
2014-02-26 07:08:53: Time to synchronize plugin icons: 202.000 ms
2014-02-26 07:08:53: Time to initialize main window: 484.000 ms
2014-02-26 07:08:53: Main Window shown
2014-02-26 07:08:53: Time to show main window: 125.000 ms
2014-02-26 07:08:53: Error occurred while updating slave cache: Input string was not in a correct format. (System.FormatException)
2014-02-26 07:08:53: Error occurred while updating slave ping cache: Input string was not in a correct format. (System.FormatException)
2014-02-26 07:08:53: WARNING: disabling profiling because of error begin profiling section twice without ending the first one (Slave Importer).
2014-02-26 07:08:53: Error occurred while updating task cache: Input string was not in a correct format. (System.FormatException)
2014-02-26 07:08:53: WARNING: disabling profiling because of error begin profiling section twice without ending the first one (Task Importer).
2014-02-26 07:08:53: Traceback (most recent call last):
2014-02-26 07:08:53: File “DeadlineUI\UI\Models\SlaveListProxyModel.py”, line 77, in onRowsInserted
2014-02-26 07:08:53: KeyError: u’’
2014-02-26 07:08:53: Traceback (most recent call last):
2014-02-26 07:08:53: File “DeadlineUI\UI\Models\SlaveListProxyModel.py”, line 77, in onRowsInserted
2014-02-26 07:08:53: KeyError: u’’
2014-02-26 07:08:53: Traceback (most recent call last):
2014-02-26 07:08:53: File “DeadlineUI\UI\Models\SlaveListProxyModel.py”, line 77, in onRowsInserted
2014-02-26 07:08:53: KeyError: u’’
2014-02-26 07:08:53: Error occurred while updating slave cache: Input string was not in a correct format. (System.FormatException)
2014-02-26 07:08:53: Error occurred while updating task cache: Input string was not in a correct format. (System.FormatException)
[/code]
Hi,
Could you check what your “decimal symbol” is set to in your OS Region/Language? Please see attached image. If it’s not set to “.”, then please try changing it to “.”, rebooting your machine and see if that helps?
Mike
It already actually was set to “.”… But your suggestion made me check the settings on repository server too. It was set to Regional Format: English (United States), while my workstation was set to Norwegian. I also earlier manually changed my workstation decimal to be “.” (for being able to use the numpad decimal symbol in 3dsMax).
When I put my workstation to Format: English (United States) the Monitor started working!
So thanks for providing a solution! 
On the other hand is there a way around this? Now I’m back to not being able to use the numpad decimal button in 3dsMax again. Also since we are an international company I know there’s a lot of different regional settings on different computers that I guess then can end up causing problems…
Hi,
I’m glad to hear it’s all sorted for you now. This bug was discovered soon after we shipped v6.1; has been fixed internally and will now ship with v6.2, which will start going into beta soon. We will make an announcement when the beta is available if you would like to join and get this issue ‘solved’ properly instead of the temp work-around for the time being.
We will make the announcement here: thinkboxsoftware.com/news/
Cheers,
Mike
Oh, damn, months of beta testing, thousands hours spent. Still simple bugs. Keep up good work.
Deadline v6.2 beta is now available via a signed NDA. Request via beta@thinkboxsoftware.com
There is also a v6.1 webinar this week coming covering the major new features: thinkboxsoftware.com/news/20 … binar.html
