Same here. A repair/scan on battle.net did not fix the issue and did not change the error message. Seems like a server issue.
Same here. A repair/scan on battle.net did not fix the issue and did not change the error message. Seems like a server issue.