Backburner server well known bug in 2016, too: Incompatible Adapter

[jens.diemer]

I get the well known bug Incompatible Adapter again with 2016:

2015/06/10 10:54:11 INF Adapter returned unexpected code 1 for "C:\Program Files\Autodesk\3ds Max 2016\maxadapter.adp.exe" "-o" "GetInfo" "-l" "Info" 
2015/06/10 10:54:11 ERR Incompatible Adapter: C:\Program Files\Autodesk\3ds Max 2016\maxadapter.adp.exe
2015/06/10 10:54:11 INF <AdapterInfo>
2015/06/10 10:54:11 INF 	<Name>Autodesk 3ds Max 2015 (64-bit)</Name>
2015/06/10 10:54:11 INF 	<Version>300</Version>
2015/06/10 10:54:11 INF 	<Description>Autodesk 3ds Max 2015 (64-bit) Renderer Adapter</Description>
2015/06/10 10:54:11 INF </AdapterInfo>
2015/06/10 10:54:12 INF <AdapterInfo>
2015/06/10 10:54:12 INF 	<Name>Command Line Tool</Name>
2015/06/10 10:54:12 INF 	<Version>300</Version>
2015/06/10 10:54:12 INF 	<Description>Command Job Adapter v2016</Description>
2015/06/10 10:54:12 INF </AdapterInfo>
2015/06/10 10:54:12 INF Starting backburner Server
2015/06/10 10:54:12 INF Loading plugin: Autodesk 3ds Max 2015 (64-bit) Renderer Adapter from Backburner Adapter Plugin
2015/06/10 10:54:12 INF Loading plugin: Command Job Adapter v2016 from Backburner Adapter Plugin
2015/06/10 10:54:17 INF Looking for a manager using 224.0.0.1:3234
2015/06/10 10:54:17 INF Registration to 192.168.1.1 accepted
2015/06/10 12:01:01 ERR Error accepting connection: Ein Vorgang bezog sich auf ein Objekt, das kein Socket ist. (0x2736).
2015/06/10 12:02:18 INF Adapter returned unexpected code 1 for "C:\Program Files\Autodesk\3ds Max 2016\maxadapter.adp.exe" "-o" "GetInfo" "-l" "Info" 
2015/06/10 12:02:18 ERR Incompatible Adapter: C:\Program Files\Autodesk\3ds Max 2016\maxadapter.adp.exe
2015/06/10 12:02:18 INF Adapter returned unexpected code 1 for "C:\Program Files\Autodesk\3ds Max 2015\maxadapter.adp.exe" "-o" "GetInfo" "-l" "Info" 
2015/06/10 12:02:18 ERR Incompatible Adapter: C:\Program Files\Autodesk\3ds Max 2015\maxadapter.adp.exe
2015/06/10 12:02:18 INF Adapter returned unexpected code 1 for "C:\Program Files (x86)\Autodesk\Backburner\Adapters\CmdjobAdapter.exe" "-o" "GetInfo" "-l" "Info" 
2015/06/10 12:02:18 ERR Incompatible Adapter: C:\Program Files (x86)\Autodesk\Backburner\Adapters\CmdjobAdapter.exe
2015/06/10 12:02:18 INF Starting backburner Server

Will there ever land a bugfix for this?!? IMHO this bug exist since 2012, see: http://forums.autodesk.com/t5/3ds-max-3ds-max-design-general/backburner-is-not-working-for-me/m-p/42...

[jens.diemer]

Really strange...

I have run "repair" from "\Autodesk_3ds_Max_2016_EFGJKS_Win_64bit_dlm\x64\max\3dsMax.msi"

Now the server output is this:

2015/06/11 10:27:44 INF Adapter returned unexpected code 1 for "C:\Program Files\Autodesk\3ds Max 2016\maxadapter.adp.exe" "-o" "GetInfo" "-l" "Info" 
2015/06/11 10:27:44 ERR Incompatible Adapter: C:\Program Files\Autodesk\3ds Max 2016\maxadapter.adp.exe
2015/06/11 10:27:44 INF <AdapterInfo>
2015/06/11 10:27:44 INF 	<Name>Autodesk 3ds Max 2015 (64-bit)</Name>
2015/06/11 10:27:44 INF 	<Version>300</Version>
2015/06/11 10:27:44 INF 	<Description>Autodesk 3ds Max 2015 (64-bit) Renderer Adapter</Description>
2015/06/11 10:27:44 INF </AdapterInfo>
2015/06/11 10:27:44 INF <AdapterInfo>
2015/06/11 10:27:44 INF 	<Name>Command Line Tool</Name>
2015/06/11 10:27:44 INF 	<Version>300</Version>
2015/06/11 10:27:44 INF 	<Description>Command Job Adapter v2016</Description>
2015/06/11 10:27:44 INF </AdapterInfo>
2015/06/11 10:27:44 INF Starting backburner Server
2015/06/11 10:27:44 INF Loading plugin: Autodesk 3ds Max 2015 (64-bit) Renderer Adapter from Backburner Adapter Plugin
2015/06/11 10:27:44 INF Loading plugin: Command Job Adapter v2016 from Backburner Adapter Plugin
2015/06/11 10:27:49 INF Looking for a manager using 224.0.0.1:3234
2015/06/11 10:27:50 INF Registration to 192.168.1.1 accepted
2015/06/11 10:28:07 INF Receiving new job from 192.168.1.1
2015/06/11 10:28:08 ERR No plugin to handle job: Autodesk 3ds Max 2016 (64-bit)

2016 3dsMax.msi repair fixed the 2015 adapter is fixes, but 2016 is still broken?!?

[jens.diemer]

Seems that deleting %LOCALAPPDATA%\backburner will fix the problem.

[jens.diemer]

No, deleting %LOCALAPPDATA%\backburner doesn't fix the problem in any case...

Don't know but this happens often on different machines 😞

Can anyone confirm? Is there any work-a-round?

[jens.diemer]

Wow, i made some tests!

If i start server.exe first and then manager.exe on the same machine -> i get the Incompatible Adapter error

If i start first manager and then server it works fine!

WTF? 

[Laurent.Pallares]

Hi Jens,

The manager need to be started previously and the server for render later one.

Depending the number of server and the OS release could also have an impact.

Are you using a render engine like Vray or Arnold.

Thanks for the feedback.

Best regards,

[jens.diemer]

No Vray, no Arnold.

IMHO: the starting order should be totally no matter.

This is a very strange behaviour.

[jens.diemer]

This happen to me again.

The Fix is: Disable "VitualBox" Ethernet Adapter... Then restart backburner...

Think backburner has try to use the Virtual Adapter than the real network adapter... Strange!

[jens.diemer]

Ah... No, the "Disable "VitualBox" Ethernet Adapter" is to fix connection problems... Not the "Incompatible Adapter" problem...

This just happens, sometimes:

[jens.diemer]

Still exist in 2017:

Maybe deleting backburner data directory will fix this... But hey: It should not happen, isn't it?!?

[jens.diemer]

no fix with 2017 SP2 😞

Backburner still v2017.0

[Alfred.DeFlaminis]

Hello @jens.diemer,

Thanks for the detailed info here.  I feel like maybe those error messages are leaving out some information.  Are you by any chance running IPv6?  My first move would be to disable it, as it is not supported under backburner.  (Also, tunneling or IPv6 to IPv4 adapters not supported.)

Can you check those for me to make sure that you aren't using IPv6?  Thank you for doing so.

Best Regards,

[Alfred.DeFlaminis]

Hello @jens.diemer,

I just wanted to follow up here, any progress on your issue?

Best Regards,

[mickatt1]

Hello I have the same problem as JENS in 3dsmax 2017 
I'm not in IPv6 but in IPv4.

Could you help me please?

Thanks

Michael Attia

Backup postprod

[Alfred.DeFlaminis]

Hello @mickatt1,

Can you please describe the issue in a bit more detail for me?  Typically a new thread per user issue is warranted because we can't be sure that it's the same problem.  For example, Jens reported above that starting the manager first and then the server solved his issue.  Does that work for you?  If not, I'll move this post and replies to a new thread.

Best Regards,

[mickatt1]

Hello Alfred,

I have the same problem when I start my manager first and my server after.

I have 4 rendernode with 3dsmax 2017/vray running and I have this problem only with one rendernode the 3 others work like a charm.

It's very strange because the 4 rendernodes are the same.

It worked very well when I was 3dsmax 2016 installed.

thanks in advance

Ps: sorry for my poor english I hope you understand my problem.

Regards

Michael Attia

Backup postprod

[Alfred.DeFlaminis]

Hello @mickatt1,

Is there anything different about the machine that is having this issue compared to other machines?  Would you mind posting the text for the error you are getting?  (Whole screen text is fine, and thank you.)

Best Regards,

[mickatt1]

Server 3dsmax 2017 OK

The 2 servers are identical same processor same OS same plugins (Vray 3.40.03)

I have 5 servers only one has this problem and just with 3dsmax 2017 

it has never happened with 3dsmax 2015 or 2016

Thanks for your help

Michael Attia

Backup postprod

[Alfred.DeFlaminis]

Hello @mickatt1, @jens.diemer,

I've installed and reinstalled Backburner about 15 times over the past few days trying to reproduce this error but I am unable to do so.  I've talked to the KDE and looked in developer notes and all of us are unable to reproduce this issue.  So, I have to go to the old fallback of uninstall it and reinstall it.  But, make sure you remove all the leftover config and cache files as well.  

First, uninstall backburner.  Then we need to delete the following folders:

C:\Windows\SysWOW64\config\systemprofile\AppData\Local\backburner

C:\Users\%username%\AppData\Local\backburner

Reboot

Then, Reinstall BB with administrative rights.  Once you install backburner... please open the programs in this order (I'm just being extra careful): 

1) Start manager on local machine.  

2) Start monitor, connect to local manager.  Close monitor, close manager.  

3) Start network manager (not local)

3) Start server.  

If this fails, then the problem must be something to do with network connections or permissions on the OS level.  I would check the TCP/IP settings for the offending machines and see if there is any differences at all between the working ones and the error machines.  I would log this as a bug but it's already logged and closed as 'unable to reproduce'.  

If there is anything at all that you can tell me about the machines having issues, ways to reproduce this, or anything at all... please do.  I very much want to help you both.

Best Regards,

[jens.diemer]

---

Alfred.DeFlaminis schrieb:

I've installed and reinstalled Backburner about 15 times over the past few days trying to reproduce this error but I am unable to do so.

---

That's it! Some bugs are hard to reproduce. You can't find them just by testing... but you will find them, if you use 3dsmax in production! And if you use max in production, then you will find many bugs!

But there is no bug bounty program. So every user of max must work with 3dsmax to earn money. Finding Bugs, help to find bugs or report bugs just cost time and brings no money.