- Ran a build to assist with improvements to server security.
Update - Wednesday February 22, 2012
1 pages • Page 1
I'm getting two very different opinions based on that statement.
1) Anytime we've been told a maintenance would occur to close servers down for some time was a fraud and that closing servers was never a necessity.
2) The new security thing people have tested did more than it should had and less what it was intended for.
Let the speculation train commence!
1) Anytime we've been told a maintenance would occur to close servers down for some time was a fraud and that closing servers was never a necessity.
2) The new security thing people have tested did more than it should had and less what it was intended for.
Let the speculation train commence!
R
If either of you is running Windows 7, try the option of running the program As an Administrator since Windows 7 won't let the program change itself to try and protect you. I know this was an issue others faced in the past and this resolved it. If nothing else, a restart should also work. Hope this helps.
E
I have the same problem too. Tries to load the files then I get the "Serious Error/Send Report" message. :/
Edit:
thanks
this fixed it for me. didnt think to try this. ^_^
Edit:
Quote:
|
If either of you is running Windows 7, try the option of running the program As an Administrator since Windows 7 won't let the program change itself to try and protect you. I know this was an issue others faced in the past and this resolved it. If nothing else, a restart should also work. Hope this helps.
|
thanks
this fixed it for me. didnt think to try this. ^_^R
S
Quote:
|
1) Anytime we've been told a maintenance would occur to close servers down for some time was a fraud and that closing servers was never a necessity.
|
Compare this to other games especially Wow ( from being told by ex wow players ) which did server updates regular and closed servers to do it.
The security part anet wanted to test i doubt was the cause of problems - not everyone tested it - so in thoery only those testing would have been affected.Anet was meant to be viewing data to monitor it and im sure as hell if it was going to cause problems it would show in first few hrs rather than a few days later.
Hey,
Having same problem, that the gw.exe doesnt let the game run. I have windows xp. Reinstalled gw, also moved the gw.dat file from laptop, on which it works even after the update, but the desktop comp keeps getting the error. Contacted support too. I've checked firewall as well that it allows it.
Error log keeps logging this error:
App: Gw.exe
Fatal error (2): Exception
When: 2/23/2012 17:57:29
File: u:\code\arena\core\platform\windows\exe\error\exee rror.cpp(419)
Any other solutions?

Having same problem, that the gw.exe doesnt let the game run. I have windows xp. Reinstalled gw, also moved the gw.dat file from laptop, on which it works even after the update, but the desktop comp keeps getting the error. Contacted support too. I've checked firewall as well that it allows it.
Error log keeps logging this error:
App: Gw.exe
Fatal error (2): Exception
When: 2/23/2012 17:57:29
File: u:\code\arena\core\platform\windows\exe\error\exee rror.cpp(419)
Any other solutions?

f
Quote:
|
Hey,
Having same problem, that the gw.exe doesnt let the game run. I have windows xp. Reinstalled gw, also moved the gw.dat file from laptop, on which it works even after the update, but the desktop comp keeps getting the error. Contacted support too. I've checked firewall as well that it allows it. Error log keeps logging this error: App: Gw.exe Fatal error (2): Exception When: 2/23/2012 17:57:29 File: u:\code\arena\core\platform\windows\exe\error\exee rror.cpp(419) Any other solutions? ![]() |
but seriously, that's really weird. i'm interested to see what support says for that. i've never gotten this issue before, and i've had plenty of gw issues. gl friend!
F
Quote:
|
Hey,
Having same problem, that the gw.exe doesnt let the game run. I have windows xp. Reinstalled gw, also moved the gw.dat file from laptop, on which it works even after the update, but the desktop comp keeps getting the error. Contacted support too. I've checked firewall as well that it allows it. Error log keeps logging this error: App: Gw.exe Fatal error (2): Exception When: 2/23/2012 17:57:29 File: u:\code\arena\core\platform\windows\exe\error\exee rror.cpp(419) Any other solutions? ![]() |
Others suggest a runtime error.
or
infamous cpp.exe errors:
malicious threats
slow down your PC
Driver update failure
Application update failure
Browser crash
Blue Screen of Death errors
missing registry files
Obscure system errors
This one definately fall into the obscure system error
I would start with updating your drivers (video/sound/etc)
F
Freeze, could it be possible that ANET is looking for the product registration keys on Hennu's system and perhaps due to a registry error is not finding them?
F
Then they have worse programmers than I thought, if they can't catch a very expectable error... This is the program on their side erroring out I'd say, which means that Hennu has not done anything wrong, but just can't ID himself.
ps, if you can't ID, it should just say password not recognized, nothing else. I mean, even with a totally new computer, where I just installed Guild Wars, I can connect to the main server, and it simply serves me the login screen. Why doesn't it do that here? We know the only thing changed is their file.
They have 'tightened security', but that should mean security after logging in. I have no idea how the program does its handshake with the server (I'm not going to reverse-engineer that, I expect them to make it work
) but it should be foolproof and failsafe. This bit of programming is neither.
ps, if you can't ID, it should just say password not recognized, nothing else. I mean, even with a totally new computer, where I just installed Guild Wars, I can connect to the main server, and it simply serves me the login screen. Why doesn't it do that here? We know the only thing changed is their file.
They have 'tightened security', but that should mean security after logging in. I have no idea how the program does its handshake with the server (I'm not going to reverse-engineer that, I expect them to make it work
) but it should be foolproof and failsafe. This bit of programming is neither.
