Backburner Error - Job Not Found

[Anonymous]

It seems random, but at times when I submit to Backburner I get an error that says Job Not Found during the submission phase. When I go to submit, it will connect as normal and save the file. Right when it gets to the submitting file part, that is when the error shows up.

However, a job ends up existing in the render monitor. But that job will not activate or run, so I don't think it's a real job.

When this happens on a particular file, it seems like no matter what I can't get past this error.

[jon.bell · Accepted solution]

Hi WTRanger,

Thanks for your question. 

It sounds as if the jobs aren't getting saved properly, so I would suggest deleting them entirely from your Manager, resetting Backburner on all your nodes, and them resubmitting them from your Manager machine.

Can you please try these steps and let us know if they help?

In addition, for future reference, here's a quick checklist of problems/solutions if you want to continue using Backburner:

Backburner requires numerous factors to be in alignment to function properly. Check the Backburner logs and try any of the following that apply:

• Reset preferences by using Reset Backburner user settings to default.

• Refusing its own connection:

• Temporarily disable the firewall to see if it is causing conflicts.
• If yes, then please allow firewall exceptions - 3ds Max: Firewall and Antivirus configuration for Backburner

• The pipe has been ended: 109

Plug-in check

•  An existing connection was forcibly closed by the remote host (0x2746).

Permissions and Firewalls

• Servers aren't connecting to Manager.

Identical versions and Workgroups

• Backburner Error Code (0x2741).

Change the server name

• An address incompatible with the requested protocol was used. (0x273f)

Prefer IPv4 over IPv6

• Adapter returned unexpected code -2 pipe has ended

Perform a Clean Uninstall - Download & Install

• An operation was attempted on something that is not a socket. (0x2736)

Guidance for configuring IPv6 in Windows for advanced users -- download and run the Prefer IPv4 over IPv6 in Prefix Policies fix

Finally, if you want to investigate 3rd-party replacements for Backburner, please see this list.

Take care, and we hope to hear from you soon!

[Anonymous]

Thanks for the response. I think we figured out the error, though it never popped up until Max 2020.

The machine had 2 names on our network, the manager saw it as one name and we submitted it to another name. The machine also, for one reason or another, wasn't on our update cycle so it still had Backburner 2017 on it.

We ended up just using a whole new machine as our manager with a proper setup and the problem has gone away