Network Rendering problem: Failed to Open Project using 5.0b

mowtoe wrote on 6/26/2004, 1:01 PM
I have yet to successfully complete one network render using 5.0a or 5.0b. The errors that I was getting in 5.0a were "some files may not be shared" after starting the render for a minute or so. Now that I've updated to 5.0b I keep getting "Failed to open project: \\COMPUTERNAME\Shareddirectory\projectname_1.veg. I have actually mapped network drives and even placed those mappings manually in the network rendering service mappings. This "bug" of saving the temporary .veg file has not been fixed. My network render test is as simple as you can get it. I have 1 .avi file on a timeline and I am doing a Non-distributed render on to a notebook over a wireless network. I've attempted to save the output file locally on the host machine (in a fully shared folder) as well as to the rendering machine (in a fully shared folder). I've done the same with the .veg file and the temporary folder, and continue to get the message "Failed to open project: \\COMPUTERNAME\Shareddirectory\projectname_1.veg. I feel like calling support, but don't feel it right to start the clock on my free support for buggy software. Any thoughts or success stories would be appreciated as I'm finally giving up after hours of troubleshooting and forum searching.

I'm using XP Pro on my host machine and XP home on my render client, both using Net Framework 1.1 and both using Vegas 5.0b.

Comments

mowtoe wrote on 6/27/2004, 2:55 PM
I checked and rechecked everything. In all of the past tests I auto-filled drive maps, I checked that the renderers said "ready" in both the host and renderer machines, checked all of the file sharing permissions, DNS names etc.

I've finally gotten it to work. I'm not sure 100% which piece fixed it.
Here's what I did:

1. I removed, cleaned all references to Vegas from the registry and reloaded both the .NET framework, the full Vegas 5.0 load and the Vegas 5.0b update. Things still didn't seem to work, so:

2. I renamed the renderer machine. (One thought I had was that the machine had an all UPPERCASE name before) but was seen in the renderers list under NRS in lowercase. I don't think this should matter, as I could access all files and the NRS renderers list showed "ready" each time....The job would even show up remotely and start the status bar on the renderer (remote) machine.

3. I hooked directly to the LAN with a cable, and successfully ran.

4. I then unhooked the wired LAN and am now rendering a job at 60% complete via the wireless network.

I even tried port forwarding in my router before all of the above for port 53704 on both machines and that didn't seem to help.

I'm wondering if it was a bad software load, or the name on the machine?
The reason I say bad software load is that I originally had a demo version of 5.0 on the notebook, but since had deleted and installed new. However, I remember on a couple of the times I tried to reinstall the setup script ended right before "finished" All of the software seemed functional, but I wonder if a piece was missed.

So, for others with this problem, I'm not sure I can tell you which piece fixed it, but I'm leaning toward a "confused" install or the uppercase name of the machine. I haven't ruled out the port forwarding piece in my Linksys Router however.

Any thoughts?

MR