We’re getting a lot of errors reported on our slaves in 2.0. They appear to be benign and do not affect any of the frames being rendered. However, they are a bit annoying. The error is below. Any ideas how to get rid of it? I thought it was related to the new power management features, but I have all disabled and all paths deleted in the repository options and it still appears.
Exception Details
NotSupportedException – The given path’s format is not supported.
Exception.TargetSite: System.String CanonicalizePath(System.String, Boolean)
Exception.Source: mscorlib
Exception.StackTrace:
at System.Security.Util.StringExpressionSet.CanonicalizePath(String path, Boolean needFullPath)
at System.Security.Util.StringExpressionSet.AddExpressions(String[] str, Boolean checkForDuplicates, Boolean needFullPath)
at System.Security.Permissions.FileIOPermission.AddPathList(FileIOPermissionAccess access, String[] pathListOrig, Boolean checkForDuplicates, Boolean needFullPath, Boolean copyPathList)
at System.Security.Permissions.FileIOPermission…ctor(FileIOPermissionAccess access, String[] pathList, Boolean checkForDuplicates, Boolean needFullPath)
at System.IO.File.InternalCopy(String sourceFileName, String destFileName, Boolean overwrite)
at Deadline.PowerManagement.SlavePowerManager.UpdateLocalTemperatureSettings()
Thanks.
Todd
Sorry I didn’t get back to you yesterday (busy day) Anyway, permissions on the repository are set to everyone on both the file and share level, so it’s not a permissions problem. Cycling the PM controls did not help. I have a second repository on our network for test purposes (post scripts and what not) that does not do this, so I’m sure it is a setting someplace in our primary repository that is messed up.
I think I saw a message about the first installer posted being messed up? I ended up re-downloading the installer and re-installing. Before I did that, I could not remove the PM paths from the Monitor as it would remove it, but next launch they would be there again. That is not the case now, but I’m just wondering if I used the earlier installer and that is the root cause of something now?
Thanks.
Todd
Stephen,
I figured out what was causing my errors in my repository. It has to do with something I did a long time ago. We had one machine that we received from another branch office that was configured funny. It’s root drive was an H: drive instead of C:. Unfortunately it has some software on it that we can’t move so I can’t reformat it or change the drive letter. Anyway I tried to get deadline to install on it by setting hte install path to c:\deadline;h:\deadline. This ended up not working so as Deadline still kept trying to install into the C: drive. So I gave up on it and did not think about it again.
I was browsing through the settings folder and found the networkSettings.xml file and when I checked the setting in there I found that the LocalPowerSettingsPath had been set to c:\deadline;h:\deadline and since the H: does not exist on my slaves, the resulting error. So, if anyone else runs across this problem, checking this path may be a good place to start.
Thanks.
Todd