Deadline 3.0 and network path errors

Deadline
1

i have a error when using network path:

Exception during render: An error occurred in RenderTasks(): Renderer reported an error with error code 121002: failed to open \292.268.50.55\MI-Files\tmp\MI\anga\var3\anga_3.2.mi for reading, The network path was not found.

but my host is 192.168.50.55
when i looking frames i see:

frame 1 - 192.168.50.55
frame 2 - 292.268.50.55
frame 3 - 392.368.50.55
and etc…

what hapeaned? why incrimenting IP in path?

2

I’m wondering if there is a problem with frame number search & replace code where it is replacing a number in the IP address instead of in the actual mi file. We can’t reproduce this with Deadline 4.0, so if this was a bug in 3.0, it looks like it’s been fixed.

If upgrading isn’t an option at the moment, is it possible to use the host name in the UNC path instead of the IP address? Another alternative would be to map that UNC path to a drive letter on your machines and use that instead.

Cheers,

  • Ryan
3

host name of my server “DC-01” fnd frame 2 search “DC-02” and frame 3 - “DC-03” and etc… i cant rename server and cant render…

its a bug and you must fix in current version, without trying sell me another version!

4

I wasn’t trying to sell you another version, I was only asking if it was an option for you to upgrade since it appears to be working fine in the latest version (clients with up-to-date support and upgrade contracts can upgrade at no additional cost).

Since upgrading is not an option, and using the host name in the UNC path won’t work, let’s see what else we can do. First, can you let us know if you are using Deadline 3.0.32934 or 3.0.33353 so we know which version to test against?

Thanks,

  • Ryan
5

Deadline 3.0.33353

6

After a bit of digging, it looks like the problem is occurring because of the padding in the mi file. For example, I can reproduce the problem using a file sequence like this:

inputMapped.1.mi
inputMapped.2.mi
inputMapped.3.mi

But the problem doesn’t occur if I use this sequence:

inputMapped.0001.mi
inputMapped.0002.mi
inputMapped.0003.mi

I’ve confirmed that this specific problem occurs in Deadline 4.0 as well. Is it possible to use a padding of 4 in your mi files instead of 1? That should workaround the problem for now.

Cheers,

  • Ryan