Announcements
Attention for Customers without Multi-Factor Authentication or Single Sign-On - OTP Verification rolls out April 2025. Read all about it here.

Backburner .... ARGH!

kris
Collaborator

Backburner .... ARGH!

kris
Collaborator
Collaborator

I recently upgraded to W10 due to an HD failure. I don't think there's any going back.

 

I have max2016 and 2017 running.  I cannot get BB to work; to connect to the manager on the server, either as the server or max itself to submit a job.  Max says "timeout error" (using auto/name/IP for the address), and server gives me "Could not find a manager will keep trying."

 

I have;

 

1) Reinstalled BB

2) Deleted the BB xml files

3) Rebooted a half dozen times

4) Disabled all firewalls/AV

5) Disabled Windows Defender.

 

I can:

 

1) Remote desktop to the server

2) Ping the server

3) Connect to the server's manager with monitor

4) Connect to and operate my farm just fine from any machine other than my workstation.

 

Backburner probably wastes more time than ANYTHING I do.  I hate it, but I'm loathe to spend a fortune on a third party solution...

 

Kris.

0 Likes
Reply
Accepted solutions (1)
602 Views
5 Replies
Replies (5)

kris
Collaborator
Collaborator

On the plus side, I found my inability to connect with max was stupidity on my part - forgot to change the port on "advanced settings".  Still can't get server to connect, though.

 

Oh, and IPv6 is disabled on all machines.

0 Likes

markcalloway
Collaborator
Collaborator

Hi @kris

 

Which version of Backburner are you using.

 

As a qucik suggestion try reinstalling Microsoft .Net Framework. For Windows 10 the top of this webpage will show you where to go:

https://www.raymond.cc/blog/add-or-remove-windows-features-through-the-command-prompt/

 

Also I believe in Windows 10 that .Net Framwork 3.5 isnt installed to start with, for 2016 software you might want to make sure this is selected as well as .Net 4.5

 

Hope this helps. Let us know how you get on.


Regards,

________________________________________________________________________________
If you find this post helpful, please LIKE.
If you have solved you issue please mark as ACCEPTED SOLUTION so other forum users can see how to fix this issue.

Follow me on Twitter / Follow me on Linkedin / Blog
0 Likes

kris
Collaborator
Collaborator

@markcalloway No, that had no effect.  

 

I'm using 2017.0.  

 

Late last night, I remembered that I had a problem similar to this in W7, but I can't for the life of me remember how I fixed it.  This is the problem with intermittent problems whilst getting old.

 

When I put BB into "automatic search" it looks for a weird IP range, 224.0.0.1.  Last time, I discovered that was irrelevant; once I fixed whatever it was, it connected just fine.

 

When I put the server IP (192.168.0.25:3237), and I have debug on, it says its "attempting connection with 192(etc)..." then "could not find manager, will keep trying".  

 

I can ping both ways.

 

Kris.

0 Likes

kris
Collaborator
Collaborator
Accepted solution

Go it!  This wasn't the same cause as it was last time. 

 

When I installed W10, I hadn't changed the computer name, and windows had named it "Desktop-VKJSGS" or something like that.  When I changed it to something shorter and without the dash, it worked fine.  Bear in mind that in server settings, I had a short server name w/o special characters.

 

Yet another reason to scrap BB and get something not coded before the first Bush took office.

 

Thanks @markcalloway for the help.

 

Kris.

kris
Collaborator
Collaborator
0 Likes