15-01-17 DrServer closed loopback connection

[Christa Noel]

I just activate my DR Slave with new 15-01-17 Drserver. find it isn't working at all at the first try with note closed loopback connection. check the attachment
need your advise guys..

[Juraj]

I have the same issue with it. It seems random though.

[Christa Noel]

so it must be moved to bug report. I get this consistenly, can't use DR at all.
I have 2 network connection, the first connection is office network connection with hundreds of users, the second connection is DR use only with only 2 nodes (connection is generated with LANcard). it works correctly in 7.2 but cannot use search LAN feature.. I have to manually input the IP or PC name. i need 2 connection because it slow down the communication between the master and slave. I reported this about a month ago.
but if I disable or remove the first connection, it works normally.
Juraj, Do you have two network connection like I do?
and someone please move this thread to bug report board. but if I need to create new thread there, let me know.

[Juraj]

Ok, after some renderings, I came to this conclusion. It lets me do DR one or two times, and then every other attempt keeps closing.

[maru]

<just random guessing, I only ran DR on a single machine to check it>
Maybe some required process in the background doesn't closed or doesn't start for some reason?
I know that sometimes Backburner may do bad things to DR. Do you have the same version of Backburner as 3ds Max installed? (for example BB2014 and Max2014)? Any other versions installed at the same time?

[Juraj]

I don't see backburner in this equation but for sake of clarity, in my case, all slaves, and all workstation have equal 3dsMax installations, same goes for backburner, which is alligned.

In most cases, simply deleting the DrData folder inside solves this issues. But to do so after every few renderings ?
I previously didn't have this issue until the recent new DR (17th Jan).

The closing usually happens shortly before computing GI, so after the scene translation is finished. It's scene independent. It loops the issue afterwards. It's pretty new phenomenon, alone of user error issue.

[maru]

I don't see backburner in this equation but for sake of clarity, in my case, all slaves, and all workstation have equal 3dsMax installations, same goes for backburner, which is alligned.

Ok, then I suppose Keymaster will need to take a look at this.

About Backburner, you would be surprised. I couldn't get DR working and was getting a very informative "unknown error" from Autodesk all the time, so after a long chat with Keymaster we found out it was because Backburner 2012 and Max 2014 were installed. Uninstalling BB12 (also pretty hardcore) and installing 14 fixed the problem instantly. It's because BB needs to be installed to run 3dsmaxcmd, which is required to run with DR. :)

[Christa Noel]

I checked my backburner version, and it is 2014 as the same as the max version.
to use the dr correctly I have to disabled my first network connection (2nd connection is DR only) and follow the way juraj tricked this by deleting the files inside the drdata. is it known bug? or I missed some thread / info which explain this?
and guys, let me hear your opinion about the way I decide to accelerate dr networking with having 2 network connection in my master PC. because I have no any problem in vray with 2 connections. check the attachment. I hope there will be improvement to break this DR limitation.
are there anybody has the same case like me?

[xt13r]

i  have the same problem here.
One slave works fine, and on the other this problem appear. Every pc have the same max version with backburner and corona 1.00.01
I have no idea what's going wrong)

[blankvisual]

Guys I had the same problem with this new version, here is what i did.

Are you able to render corona on backburner on each render node? without errors?

In the render nodes (slaves) I installed corona and actually opened 3dsmax. The license message then popped up and I activated it on each slave.
Then, I made sure on the slave that I could do a local backburner render, 100% and complete without errors using backburner.

Just a little test scene with 5 sec time limit and finally when I got the render done in backburner, that meant max and backburner were talking to eatchother with this new version.

That proved key for my DR to work. So this does seem to be related to Backburner.
Before It was failing and I got "... closed loopback connection"

[micmac]

Same problem for me " closed loopback connection".
Everything was fine with 7.2 version but not with 1.0!

[Ondra]

this might be caused missing/incorrect version of backburner. See troubleshooting #6: https://coronarenderer.freshdesk.com/support/solutions/articles/5000501666

[micmac]

backburner are same on both machines (bb2014)...

[Juraj]

Backburner also worked fine in my case, and the loopback closure happened randomly on and off (the 3D scene would actually start, perhaps got to parsing, sometimes more, and then quit), even during same session. Will have to try 1.0 if that changed, but I abandoned DR in meantime and just use strongest machines to multitask.

[krimson]

i have the same problem here.