Network rendering

gjesion wrote on 7/31/2004, 2:13 PM
I have set up network rendering and am having a curious problem. Everything seems ok, each computer can see the other, no firewall, file sharing working, etc. I start the network render and if I try 'distribute rendering' the job runs on the host only. (Note: both machines show up in the 'stitch host' drop down). I have not let it complete, but it seems to run just fine. If I try to render on the other machine, I get an error:

'Error: Render job 'abs:53704/1' failed: Server encountered an internal error. For more information, turn on customErrors in the server's .config file.'

The render machine sees the host, and reports that it is ready. The host also shows the render machine in the 'renderers' tab.

After this I realized that I have 5.0b on the host machine and 5.0 on the render machine. I then proceeded to update the render machine. This promptly installed the full version on the render machine. After the update the job starts on the render computer, but I get this error message from the host:

Error: Render job 'abs:53704/1' failed: EULA was violated by tcp://dell:53704/NetRenderService.rem.

Apparently the end user license agreement is being violated. So, my question is this: How can I upgrade the network render software with out installing the full program?

Thanks in advance,

Jerry Jesion

Comments

cbrillow wrote on 8/2/2004, 10:48 AM
Some clarification on the upgrade process might be helpful. Based upon what I've read in this forum and in the "What's New in 5.0b" section of the update document, I'm fairly certain of only the following with reference to setting up network rendering:

-- The main editing computer and the render clients must be running the same Vegas version

-- Unlike the original Vegas CD, the update doesn't offer the choice of installing a render-only version of Vegas on your 2nd and 3rd computers.

-- The serial number and registration information must be the same for all 3 computers


This brings up several questions...

1) Is there a preferred path for upgrading an original 5.0 installation to subsequent versions? Must all of the subsequent versions be loaded, or is it permissible to skip from 5.0 to 5.0b, completely bypassing 5.0a? From what I've seen, it appears that updates are, in effect, time-limited full installation versions rather than patches and repairs, which would seem to obviate the need for following a strict upgrade path from original CD to latest version.

2) Can 5.0b, which installs the full-blown Vegas package, be installed onto a machine specified as a "render-only" client previously setup in 5.0?

3) Doesn't a Vegas installation performed via 5.0b update function as Vegas, rather than a render-only, restricted version? If so, isn't this a violation of the EULA?