On all of our old windows xp pro 64bit slaves I get the following error:
But all of our windows 7 pro 64 bit slaves there is no errors
The repository is running on a Windows Server 2008 R2 Enterprise (64 bit)
I haven’t been able to find difference is the server/network setup that should make a difference between xp vs. 7, so could it be deadline?
Do you get this error a lot (to the point where the slaves appear as Stalled in the Monitor), or are they more of a random occurrence? If it’s the latter, then it’s safe to ignore these errors.
All Deadline is doing is writing to a temp slave info file in the repository, in the same folder as the original. When it finishes writing the file, it copies it over the original. Nothing fancy, and this process is exactly the same on all versions of Windows, so that’s really odd that you would only see this on your XP machines.
Cheers,
The slaves don’t appear as stalled, but I don’t think it is random, or?
Wow! It’s definitely happening more times than not. Pick one of your XP machines and close the Slave running on it. Then go to \your\repository\slaves[SLAVENAME] and delete all files except for [SLAVENAME].slaveSettings. Then restart the Slave application on that machine. It should recreate its slaveInfo file, but I’m curious to see if it starts printing out that error immediately afterwards.
Stopped the slave, then delete the “Slavename.slaveInfo” file, and started the slave again.
I could see that there is created a file in the folder, but the .info file is not updated/overwritten regular.
The file was updated at time 09.16 and again at 9.21, which fits with the info from the slave.
All the security settings and sharing options should be ok, any more good ideas?
That’s good that at least a few get through, and as long as your slaves aren’t showing up as stalled, it’s nothing major to worry about.
However, it would be nice to figure out why the slaves are having this problem. Which version of Deadline are you using?
We are running
It turned out that it was the antivirus program “CA Total Defense” on the server that was the problem, strange
We have now turned it off, and everything is good, no more errors
We’re getting this exact same issue, although I’m not sure if it’s on all our XP Slaves. The ones that error aren’t stalling but we’re not getting any Task/render/startup times for completed tasks which is a bit frustrating. Any suggestions on what might cause this? This has only been an issue since we upgraded to 5.1
Nick
Hey Nick,
Do you have any antivirus software running on your repository server? Just wondering if you’re hitting the same issue that cadpeople did.
Cheers,
Hi Ryan,
We don’t have virus software installed on the repository server. But I am looking into a separate issue with the server not releasing file handles so I don’t know if that’s going to be causing the problem.
Nick
That could definitely be the cause of the problem. The “The process cannot access the file because it is being used by another process.” error would be caused if the file is locked because the handle isn’t released.
Cheers,