After updating to the 1.5 patch, I tried getting my mod with some imported files published onto battle.net. However, while I was trying to publish I found the error:
"Document information could not be retrieved. Internal Battle.net error."
Has anyone else encountered this??
EDIT: This also happens when I get onto the last stage of publishing, as it also says it recieved an Internal Battle.net error.
I am having the same problem :( any idea how to fix this?? I've been counting down the days till this release for this exact reason, and now I can't even publish this map...
How? All of us seem to have the same problem going.
Ever since then, I was never able to publish. I guess Blizzard didn't take their time to "maintain" after all. Got a really bad glitch going in my game and can't even update.
If I could tell you, I would. Seems everybody has this problem. My map is the only one up to date in the first 50 maps.
I pressed dependencies, modified the bnet side of my mod. Had bnet mod removed (while editing/preparing it with the beta editor), because the version was different in beta.
Then I pressed publish, next, next, next. Ding. Done.
Edit: Tried to upload an almost empty map: Internal Error
So I guess, I just got lucky
If I could tell you, I would. Seems everybody has this problem. My map is the only one up to date in the first 50 maps.
I pressed dependencies, modified the bnet side of my mod. Had bnet mod removed (while editing/preparing it with the beta editor), because the version was different in beta.
Then I pressed publish, next, next, next. Ding. Done.
Edit: Tried to upload an almost empty map: Internal Error
So I guess, I just got lucky
Your publishing broke it. :D
edit:
How about creating a thread in Blizzard's forums that their publishing service is broken?
I didn't see one in their forums, yet.
I don't mind being the OP I can post for this issue, just give me a little bit of time. First, to get our story straight, we can't publish maps that were on the old server / the 1.5 beta server due to an error that reads "Documentation information could not be retrieved: Internal Battle.net error" If there is anything I am missing please let me know, I'll link you to the post once I've composed it.
UNRELATED: In the mean time, please rant on my older post about the game lobbies. I've spent quite a bit of time writing this list and unfortunately it has not gotten enough attention. http://us.battle.net/sc2/en/forum/topic/5978368328?page=1
@DaBernMon: Go To me its not only previously published files. I ran into error messages while trying to publish new files too. I can make a detailed list of errors in the thread later.
I looked into it on the battle net forums and found this:
"
Hey Folks,
As many of you may be aware, today was the launch of patch 1.5.0 for StarCraft II. We would like to summarize some of the current issues we have identified with the patch and keep you up to date on our progress finding appropriate solutions.
1.) Viewing certain players’ profiles was causing the client to crash. We have released a temporary fix that allows these profiles to load without crashing, but some ladder related data may not appear. The ladder data is not lost; it is just not being displayed while we work on a long term fix for the issue.
2.) Searching for maps in the Arcade can sometimes not return any results.
3.) Attempting to open version 1.4.4 of StarCraft II, pinned to the task bar, will cause the launcher to go into an infinite loop. Please try launching the game from the installation directory to get around this. We are working on a solution to address this.
4.) Some games appearing in the “Join Game” list of the “Custom Games” menu on the StarCraft II side of the client will cause that game to be played using an older balance. As a temporary work around please start lobbies from the “Create Game” page.
5.) We are getting some early reports that a few people cannot publish their games.
We are rapidly working to solve the issues listed above. Please don’t hesitate to let us know if you experience any other problems with the patch over in the Technical Support and Bug Report forums.
We look forward to seeing you in-game!
"
Look at number 5, they have observed that the problem is occurring, I doubt at this point a new thread will change anything, they're already working on it.
If you guys still feel compelled to rant about it I don't mind making a thread, but I just thought that as they've already observed it there's no sense beating a dead horse over it.
You can publish files, if they got a new name.
It's currently impossible to update files on battle.net.
So you can publish a temporary version of your maps on battle.net.
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
After updating to the 1.5 patch, I tried getting my mod with some imported files published onto battle.net. However, while I was trying to publish I found the error:
"Document information could not be retrieved. Internal Battle.net error."
Has anyone else encountered this??
EDIT: This also happens when I get onto the last stage of publishing, as it also says it recieved an Internal Battle.net error.
I've the same problem.
Everyone has this. Battle.net is shot to hell right now and you'll just have to wait until it's fixed.
I managed to publish 1 mod and 2 maps before it started, nut it seems we will have to wait.
I am having the same problem :( any idea how to fix this?? I've been counting down the days till this release for this exact reason, and now I can't even publish this map...
had no problem at all, immediately after the server went up
i used my old, already online mod and just a new version of the map
@b0ne123: Go
How? All of us seem to have the same problem going.
Ever since then, I was never able to publish. I guess Blizzard didn't take their time to "maintain" after all. Got a really bad glitch going in my game and can't even update.
If I could tell you, I would. Seems everybody has this problem. My map is the only one up to date in the first 50 maps.
I pressed dependencies, modified the bnet side of my mod. Had bnet mod removed (while editing/preparing it with the beta editor), because the version was different in beta.
Then I pressed publish, next, next, next. Ding. Done.
Edit: Tried to upload an almost empty map: Internal Error
So I guess, I just got lucky
Your publishing broke it. :D
edit:
How about creating a thread in Blizzard's forums that their publishing service is broken?
I didn't see one in their forums, yet.
@Ahli634: Go Yeah, would you get it started? I'll show up there to complain too.
I've just published a map. :D
@Ahli634: Go I've already published 4 mods and 3 maps so I'm not the one starting the thread ;-)
im lazy and better at ranting then being the OP that is supposed to make sense.
This is fucking annoying. Way to fail Blizzard!
@Taintedwisp: Go
I don't mind being the OP I can post for this issue, just give me a little bit of time. First, to get our story straight, we can't publish maps that were on the old server / the 1.5 beta server due to an error that reads "Documentation information could not be retrieved: Internal Battle.net error" If there is anything I am missing please let me know, I'll link you to the post once I've composed it.
UNRELATED: In the mean time, please rant on my older post about the game lobbies. I've spent quite a bit of time writing this list and unfortunately it has not gotten enough attention. http://us.battle.net/sc2/en/forum/topic/5978368328?page=1
@DaBernMon: Go To me its not only previously published files. I ran into error messages while trying to publish new files too. I can make a detailed list of errors in the thread later.
I looked into it on the battle net forums and found this: " Hey Folks,
As many of you may be aware, today was the launch of patch 1.5.0 for StarCraft II. We would like to summarize some of the current issues we have identified with the patch and keep you up to date on our progress finding appropriate solutions.
1.) Viewing certain players’ profiles was causing the client to crash. We have released a temporary fix that allows these profiles to load without crashing, but some ladder related data may not appear. The ladder data is not lost; it is just not being displayed while we work on a long term fix for the issue.
2.) Searching for maps in the Arcade can sometimes not return any results.
3.) Attempting to open version 1.4.4 of StarCraft II, pinned to the task bar, will cause the launcher to go into an infinite loop. Please try launching the game from the installation directory to get around this. We are working on a solution to address this.
4.) Some games appearing in the “Join Game” list of the “Custom Games” menu on the StarCraft II side of the client will cause that game to be played using an older balance. As a temporary work around please start lobbies from the “Create Game” page.
5.) We are getting some early reports that a few people cannot publish their games.
We are rapidly working to solve the issues listed above. Please don’t hesitate to let us know if you experience any other problems with the patch over in the Technical Support and Bug Report forums.
We look forward to seeing you in-game! "
Look at number 5, they have observed that the problem is occurring, I doubt at this point a new thread will change anything, they're already working on it.
If you guys still feel compelled to rant about it I don't mind making a thread, but I just thought that as they've already observed it there's no sense beating a dead horse over it.
@SoulFilcher: Go
Yeah I didn't look into new mods, I was just summarizing the issues I personally observed. If I do end up posting something I will include that.
Bnet forums topic
This forum topic is about the publishing error. So annoying.
You can publish files, if they got a new name.
It's currently impossible to update files on battle.net.
So you can publish a temporary version of your maps on battle.net.