Render Client Hangs with Job "Queued"

2G wrote on 7/3/2004, 9:15 AM
I have one network render client working fine. I decided to set up a second one. Communications to the client works. I submit a job to it. The job shows up in the render client, status "Queued". In the lower right corner of the client, it says "Status: Starting". Hangs forever.

I can submit the same job to the other client, and it renders fine.

Suggestions? It appears to be waiting on something. Any ideas? Did I forget to enable some sort of connectivity? (I can access all the "file mapping" folders just fine using "My Network Places").

Thanks.

2G

Comments

SonyPJM wrote on 7/6/2004, 9:10 AM
Are you running Vegas 5.0b on all machines?
2G wrote on 7/7/2004, 11:54 AM
Well, yes and no... I downloaded build 5.0b build 154 to verify a different problem right before 5.0b released. The failing machine has build 160. I had just (incorrectly) assumed that they were the same builds. I'll refresh my editing machine up to 160 and try it again.
2G wrote on 7/7/2004, 9:23 PM
I upgraded the edit machine to 5.0b build 160. (the failing render client is also at 160). No change. It still hangs just as before.

I can do packet tracing, etc. if it will be useful. Just tell me what I can look at to see why it is hanging. You can contact me offline if you want to get specific info.

Thanks.

2G
2G wrote on 7/7/2004, 9:29 PM
One more thing... I cannot close the renderer when it gets into the hung state. When I click on close, it says something like, "you have jobs queued, do you really want to quit?". I click yes and the window freezes. It won't repaint. Finally have to get the "this program is not responding" popup and kill it that way.

2G
bensonw wrote on 7/13/2004, 10:54 PM
I'm having the same problem. I have the shares set up as needed. I have 5b on all machines. I've uninstalled and reinstalled the software several times and I've cleaned up all Vegas registry entries between installs. The client and the host see one another with no trouble. The render client that is working is running Server 2003 and, suprisingly enough, it's runing the network render service with no trouble.

The only thing I haven't tried so far as I can tell is logging the failing rendering client onto the domain. I'm going to try setting up the client on a different machine to see if I can get it wroking. Any suggestions would be greatly appreciated. Thanks!

(It's times like these that I REALLY wish someone would bring Batch Converter back.... What a great program!!! If only Vegas 5.0 didn't corrupt the old Sonic Foundry shared plugins which makes it impossible to render practically anything video with Batch Converter.... Frankly, I'm seriously contemplating wiping Vegas 5 from my system all together just to get Batch Converter back!!! What a shame...).
SonyPJM wrote on 7/14/2004, 8:14 AM

A couple of suggestions:

1) If you're using a wireless network, net rendering may not work.

2) Make sure you can ping each of the rendering hosts from each other.
For example, if the host name that appears in the status bar of the
render service is "mymachine.mydomain.net", go to the other machine
and type the following in a cmd window:


ping mymachine.mydomain.net


Make sure you get a response. If not, you may need to change
something in your network/DNS setup.

Recently, I helped someone who had his router configured in a way that
caused the ping command to fail. He had his ISP's domain entered in
his router's DNS configuration. The fix was to clear out that
setting. After doing so, the host name in the status bar of the
network render service dropped the domain part and everything started
to work.