Network render hangs 'queued'

Venom wrote on 6/3/2004, 5:45 PM

There's been a thread about a month ago, without solution, so I'm starting a new one: My network render projects just hang in status 'queued' on the client machine. If I render on the machine where the full Vegas is installed (the 'owner') it works. But neither on a client nor distributed.
I double checked the mappings (like John Meyer advised) and am quite certain they are okay (including project file and target directory). Besides, I also tried it with a project with only a generated media inside. Server and client report as 'ready'. Both are v5.0b. The client's log says 'process performance counter is disabled'. This is the full log:
Label: Beginning Render Job: \\Chris2\chris2_H_shared\generated_media_only.avi
Error: System.InvalidOperationException: Process performance counter is disabled, so the requested operation cannot be performed.
at System.Diagnostics.NtProcessManager.GetProcessInfos(PerformanceCounterLib library)
at System.Diagnostics.NtProcessManager.GetProcessInfos(String machineName, Boolean isRemoteMachine)
at System.Diagnostics.ProcessManager.GetProcessInfos(String machineName)
at System.Diagnostics.Process.EnsureState(State state)
at System.Diagnostics.Process.get_MainWindowHandle()
at Sony.Vegas.NetRender.NetRenderService.QueueVegasTask(String msgText)
at Sony.Vegas.NetRender.NetRenderService.DoRemoteJob(String jobID)
at Sony.Vegas.NetRender.NetRenderService.DoJob(Object sender, LocalTaskArgs args)
at Sony.Vegas.NetRender.LocalTask.DoTask()
at Sony.Vegas.NetRender.NetRenderService.RunRenderService()

Thanks for any help!

Comments

Spot|DSE wrote on 6/3/2004, 6:25 PM

I think this is a job for Sony PJM or John Meyer/BJ_M.
your description says everything is right...Vegas 5b? is the build you are using?
You are using IP address or machine name?

Venom wrote on 6/4/2004, 2:26 AM

5.0a, of course - my mistype! I use machine names, but since they report as ready, I think that's okay. Shared folder names are more than 12 characters, but both machines have WinXP SP1.

SonyPJM wrote on 6/4/2004, 12:55 PM

I just did a web search and it appears this problem has occasionally
come up with other .net apps. Apparently, Microsoft is addressing the
issue in a future release but I'll still need to try to find a
workaround.

Which version of Windows are you using?

There may be a possible fix which involves editing the registry. Do
you have a registry value named "Performance Counters Disabled" under
the following key?

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\PerfProc\Performance
You can look using regedit.exe.

Venom wrote on 6/5/2004, 1:30 AM

Thank you. Unfortunately I don't have any such key in the reg. I have found an older .NET version (1.0.3705) besides v1.1 (or at least a software entry). Have deinstalled both and re-installed v1.1, but that wouldn't help. I get the same log message.
I have another problem for which you might have a solution. My preferences changes don't get saved. I've found a solution (or rather workaround) by de-installing Vegas, creating a new user, installing it again for the new user and finding then, that I could save now prefs for the original user, too. Funny, but that's the way it was. But with all the de- and re-installing I did in the course of the above problem, my preferences don't store themselves again. Where are they stored? Is there a better solution for that?

SonyPJM wrote on 6/6/2004, 7:03 AM

Which version of Windows are you using?

Venom wrote on 6/7/2004, 10:06 AM

XP SP1.

Ruchir wrote on 6/9/2004, 1:57 AM

I've got exactly the same problem. i.e. 2nd machine hangs on queued when requesting a non-distributed render to the 2nd machine and a distributed render only uses the base machine with an endless loop on the 2nd machine.

But a couple of additional factors:
1. When installing the network render on the second machine, the final install screen said 'installation incomplete'
2. I had orginally installed the trial version of V5 on the second machine - license locking issue?

Venom wrote on 6/9/2004, 5:10 AM

wrt 1: my installation(s) were okay.
wrt 2: I had the trial installed before, too. At one stage I had an EULA problem reporting, but with the CD serial on both machines that does not seem to be a problem anymore.
Hope we get some help! For me the distributed rendering was one of the main reasons for the V5 upgrade.

Venom wrote on 6/10/2004, 6:59 AM

So is there any news wrt this matter? At least I'm not alone with it.

Ruchir wrote on 6/11/2004, 1:01 AM

I've checked using IP addresses instead of machine names - same problem.
I noticed something in this thread about Performance Counters disabled?
Any more on that?

SonyPJM wrote on 6/17/2004, 10:26 AM

We fixed a few problems with network render jobs becoming stuck in the
queued state in 5.0b. However, we've not fixed the performance counter problem.

Ruchir wrote on 6/23/2004, 9:40 AM

5.0b has fixed the distributed render problem, but it still hangs queued on the non-distributed render. Any thoughts?