• Listen to a special audio message from Bill Roper to the Hive Workshop community (Bill is a former Vice President of Blizzard Entertainment, Producer, Designer, Musician, Voice Actor) 🔗Click here to hear his message!
  • Read Evilhog's interview with Gregory Alper, the original composer of the music for WarCraft: Orcs & Humans 🔗Click here to read the full interview.
  • The Hive's 22nd Icon Contest: Creep Abilities is now concluded, time to vote for your favourite set of icons! Click here to vote!
  • ✅ The POLL for Hive's Texturing Contest #34 is OPEN! Vote for the TOP 3 SKINS! 🔗Click here to cast your vote!
  • ✅ The POLL for Hive's Techtree Contest #20 is OPEN! Vote for the TOP 3 FACTIONS! 🔗Click here to cast your vote!

Error when publishing "Unable to send event to b.net"

Status
Not open for further replies.

daath

D

daath

I've looked everywhere and it seems others are having this problem also, but there hasn't been any solutions given.

Does anyone have an idea how to fix this?
 
Did you try restarting your editor, or publishing from a different computer?

Yeah I restarted many times, and turned off my firewall, opened ports, ect.

And unfortunately this is the only computer I can publish from.
 
Is that all it says? Nothing in parentheses or anything at all? Its little to go on so as much info as possible would be nice, a screenshot of the error would probably help figure out the problem as well.
 
As soon as I press OK to publish, the editor freezes for about a minute, then a message says: Battle.net connection was interrupted, and the Publish Document window tells me: Unable to send event to Battle.net. I will also now be logged out of Battle.net.

Sometimes this will be all, other times I will get Document dependency header file is not available errors and I will have a file transfer open with my map uploading but stuck at 0%.
 
Sometimes this will be all, other times I will get Document dependency header file is not available errors and I will have a file transfer open with my map uploading but stuck at 0%.

This can be avoided by re-publishing the map. I get that error a lot.

If re-publishing doesn't work, delete then re-do your map variants and attributes.

Dunno about the first one.
 
Status
Not open for further replies.
Back
Top