Interestingly, similar errors, known as Error 37 and Error 3006, were abundant on the launch of Diablo 3 back in 2012. Server issues rampant during the launch of Diablo 2: Resurrected were promptly fixed by Blizzard, hopefully meaning the ‘character already on server’ error will be fixed sooner, rather than later. If the above methods have not worked, the only option is to play offline until Blizzard implement an official fix. Close the application, re-launch Diablo 2: Resurrected and attempt to load into the character you wish to play as.
Open Task Manager (Ctrl + Shift + Esc) and find the ‘ App’ in the list of currently running programs.
0 kommentar(er)
