Log in

View Full Version : Unable to Validate Game Version.... Battle.net and Symlink on Mac


Guilo
03-30-2009, 07:43 PM
So it's been about a month since I've played... but during that month I merged my 3 accounts into a battle.net account.

Well I tried to login this weekend and got this message:

Unable to validate game version. This may be caused by file corruption or the interference of another program. Please visit http://us.blizzard.com/support/article.xml?articleId=21031 for more information and possible solutions to this issue.
So this is only on my symlinked accounts... I deleted all of the symlink directories and reran the script from wowwiki and I"m sill having the problem.

Has anyone else run into this and has a solution been found yet? I tried all of the blizzard solutions but they aren't really geared towards our situations.

Any help EXTREMELY appreciated.

Thanks
-G
homerjunior
03-30-2009, 08:07 PM
Update WoW
Guilo
03-30-2009, 09:48 PM
When I log in and play on my main account... there do not appear to be any updates...
Guilo
03-30-2009, 10:55 PM
If I copy my whole directory I can load up multiple characters... but I don't like the performance + harddrive hit... any help with symlinking with the new acct. changes?
robgfl23
03-31-2009, 01:58 AM
copy wow.exe and loader.exe from your main wow directory to your symlinked directories. I had this problem too right after the 3.0.9 patch and this fixed it.
Guilo
03-31-2009, 09:38 PM
I tried doing that with the world of warcraft.app (I'm on a mac there is no loader equivalent that I see) and still no dice. Thanks for the suggestion though.
Guilo
04-03-2009, 07:48 PM
Just to update... I went back and looked at the original wow directory today and found that there is a launcher app... (dunno why i didnt see it before) and copying both of them into the symlink directory worked like the above poster suggested.
Ferrea
04-03-2009, 10:57 PM
Although resolved, Id like to note...

Had this issue when they released the Battle.net account junk, I dont know if its related. However, repair.exe took care of it.
Moorea
04-06-2009, 02:30 AM
Thanks a lot ! I had the same problem and indeed *only* for my battle net logins I was getting that error and needed to copy the launcher to fix it (I guess the battle net login code got pushed through one of the recent launch updates - weird error though; you used to not need the launcher at all)