Network Render - Error Starting Service

ricklaut wrote on 4/21/2004, 6:03 PM

I'm getting errors when I double click on the VegSrv50.exe file to start the network rendering service. Here's the background:

V5 is installed on the laptop and the desktop; I will use them independently to edit but together to render. Switched 10/100 ethernet network; no connectivity problems between the machines on the network.

When I double click the file (VegSrv50.exe) on either machine, I get "Failed to Initialize Network Render Service. The requested name was valid and found in the database, but it does not have the correct associated data being resolved for The application must exit".

The actual Vegas application is not running when I do this. The funny thing is last night, when I had the laptop off the network and was reading through the help files, I started the render service on the laptop. No error messages then....

Anybody have clues / advice / guidance?

Rick

Comments

SonyPJM wrote on 4/21/2004, 6:49 PM

Take a look at the Network Rendering section of Vegas' help... the troubleshooting section describes a way to fix this.

ricklaut wrote on 4/21/2004, 7:08 PM

Thanks - Never would have thought of that! The first one is working; now for the 2nd!

Rick

ricklaut wrote on 4/21/2004, 9:31 PM

Ok - I've made progress, but can only get it to network render when I'm not using distributed rendering. For some reason, I'm getting a status "failed" message and this error message:

Error: render job 'xxxxxx1.cox.net:53704/1' failed: EULA was violated by tcp://xxxxxxx2.lv.cox.net:53704/NetRenderService.rem (I x'd out my computer names...).

I'm using the NTSC DV template, but get the same message when I try to render as WM9. I've tried using both machines as the stitch host; I get the error either way. I'm scratching my head at the EULA reference... I read that you can't render MPEG-2, MP3 and AC-3 across the network, but DV?

Fortunately, I"m just trying to familiarize myself with things.... there are no real projects on the line.

Rick

SonyPJM wrote on 4/22/2004, 7:19 AM

The EULA violation is a result of your attempt to use two "full" Vegas
installations with the same license. You need to choose the
render-only option when installing Vegas on extra machines for network
rendering purposes.

The render-only option does not allow you to use Vegas for editing.
The fix would probably be to buy another copy of Vegas for your laptop
or continue to edit on both your laptop and desktop (but not at the
same time) and use a third computer with a render-only install for
distributed network rendering.

ricklaut wrote on 4/22/2004, 7:20 PM

Ahh.... makes a little more sense now. So even though I'm not actually "using" the second full copy of Vegas to render, it thinks that I am because it sees the full version installed.

Thanks for the clarification.

Rick

DataMeister wrote on 4/22/2004, 7:25 PM

Can I jump on to the end of this thread. I'm having the same problems basicly.

However. When I installed the Vegas 5.0 trial, it asks for a Serial number to install just the render client so I had to install the full program.

Are we not allowed to experiment with the network rendering in the trial version?

JBJones

hugoharris wrote on 4/22/2004, 7:58 PM

SonyPJM, I have a request for future versions:

I have not upgraded to 5.0 yet, but it sounds like you must choose between a "render" or "full" install. This is a significant limitation, IMO. For example, I have Vegas on my desktop and laptop (my only two computers), and edit both on the road and at home. Is there a way to make any networked systems "recognize" that they are "render computers" for EULA purposes? Otherwise, someone who owns only two computers, who wants to use each for editing in different environments (at different times), cannot use network rendering. Perhaps there is a technical reason I'm missing.

Kevin.

MadMikey wrote on 4/22/2004, 8:07 PM

Kevin,

The Network Rendering Service is installed when you do the full install of Vegas. So if you installed the full version on both your computers you can still use them for network rendering.

The Network Rending only install would be for those who did not want to install the full version of Vegas on another computer.

This is my understaning based on the install I did, so unless they deliberately disable NetRendering on a full install it should work.

MadMikey

DataMeister wrote on 4/22/2004, 8:49 PM

MadMikey,

Did you read the upper portion of this thread?

JBJones

ricklaut wrote on 4/22/2004, 9:24 PM

MadMikey -

Even though the network rendering piece is installed with the full versions, it doesn't work (give the EULA error that I described).

Sony PJM: Please don't get me wrong - I'm very grateful that Sony allows us to install full versions on more than one computer so long as they aren't used at the same time. That makes my laptop / desktop situation work well. However, I must agree that it doesn't seem to make sense to limit the network render in that situation. Perhaps there is a reason for it; if so it would be great if you can share it.

Rick

MadMikey wrote on 4/22/2004, 9:38 PM

Yes I did read the above. As I said unless Sony deliberately disables this it should work. Evidently they are.

MadMikey

MadMikey wrote on 4/22/2004, 9:50 PM

Rick,

Not sure if this would work but it might be worth a try. IF you are running Windows XP Pro try installing the full Vegas version under one account, allowing only that account to access it. Then create a second account, say Video, log into that account and install the Render Only version to this account. When you want to rendor just log in as the Render Only account, it should not see the full version.
Again, I have not tried this but in theory it should work.

MadMikey

ricklaut wrote on 4/22/2004, 10:04 PM

I thought about that but I'm running XP Home. Is there any hope of accomplishing the same thing with the home version?

Rick

MadMikey wrote on 4/22/2004, 10:19 PM

I run Pro, so not as familiar with Home, but you can set-up multiple accounts with home also, so it might work. Try right-clicking on your Icon to Vegas full install, go to properties and see if there is a Security Tab. What you want to do is specify what user has access to Vegas.

Again, I have never owned Home, only Pro, this may be one of the advantages of Pro, not sure.

MadMikey

ricklaut wrote on 4/23/2004, 4:57 AM

Doesn't look like it's going to work....

Rick

SonyPJM wrote on 4/23/2004, 6:46 AM

I understand your point and it is a scenario we'll reconsider for the
next release. But obviously for now I'm afraid you'll need to choose
between editing and network rendering on extra machines.

ricklaut wrote on 4/23/2004, 6:58 AM

Thanks for your help! The rendering is a "nice to have"; the ability for me to work off of either machine depending upon need is more important.

All is not lost - I can still render projects from my laptop (less powerful) to the desktop so long as it is not a distributed render (i.e. the desktop works on the whole job).

Rick

bruceo2 wrote on 4/27/2004, 4:12 PM

I have a full installation on one system and render only on another system. I am a licensed user with 5a installed. when I launch the network renderer on either system or from the render dialog I get the same "failed to init.... name is valid and found.....does not have the correct.... etc etc"
I dont see a troubleshooting for Network rendering in the vegas 5 help.

SonyPJM wrote on 4/27/2004, 4:23 PM

(Pasted from Network Rendering section of Vegas help)

If you receive an error message that indicates the Network Render Service cannot start when you start the application, you may need to resolve DNS suffixes on your computer.

Open a DOS window:

a. From the Start menu, choose Run to display the Run dialog.

b. In the Open box, type CMD.

c. Click OK. A DOS window is displayed.

Type ipconfig at the command prompt.

Your Windows IP Configuration information is displayed. Note the Connection-specific DNS suffix setting.

Update your computer's DNS suffix:

a. Right-click My Computer on your desktop and choose Properties from the shortcut menu (or press the Windows key + Pause) to open the System Properties dialog.

b. Select the Computer Name tab.

c. Click the Change button to display the Computer Name Changes dialog.

d. Click the More button to display the DNS Suffix and NetBIOS Computer Name dialog.

e. In the Primary DNS suffix of this computer box, type the DNS suffix you recorded in step 2.

Click OK to close all dialogs and restart your computer.

bruceo2 wrote on 4/27/2004, 7:27 PM

No the exact same one ststed a the beginning of this thread:

Failed to Initialize Network Render Service. The requested name was valid and found in the database, but it does not have the correct associated data being resolved for The application must exit".