Patcher throwing exceptions?
Since yesterday when I put the examine.xml file on ignore, I get exceptions thrown every time I run the patcher. I don't know if they're related, I just know it didn't happen in the morning, only started after the patch. I have reinstalled the patcher, and reinstalled Java, and still getting it.
|
Quote:
|
:confused: The answer to a bug report is "just ignore it"?!
|
Quote:
|
Quote:
|
Quote:
Quote:
|
I have gotten this exception twice recently. I'm using 32-bit Java 7 and I do not let it patch automatically. In both cases where the exception was thrown, I ignored it and the patch session seemed to complete as expected.
I personally think this is just Java being flaky. At least, I have not so far seen anything that looks like a bug in the patcher. The thread does raise an interesting question: if I did suspect a bug in the patcher, where would I report it? |
Either try Options -> Reset all settings, or Options -> Uninstall updater, an re-install.
One of those should fix the error. I believe it's from a java update and the updater not being completely compatible with all versions of java. |
Quote:
EDIT TO ADD: After resetting the settings again and rebooting before starting the updater, I was able to get it to work again, and no more throwing exceptions. I was about it to lose my mind there for a minute!! |
Oh another tip for this:
Sometimes the updater doesn't close properly, or sometimes it gets opened twice (we the user get impatient and click it twice). Having multiple javaw.exe's open make the patcher throw exceptions until you force the original one shut. A restart would mimic this since the exe would no longer be open after restart. |
I posted this about a month ago and got no response. I have 2 machines, 32-bit and 64-bit. Neither update java unless I okay it, the patcher works fine on both. But since coe came out the 64-bit pc throws that exception every time. I deleted java and reinstalled it twice, hasn't helped yet. I tried uninstalling the patcher but the instructions say to go to control panel and click the app, click uninstall. Except it doesn't show up in control panel. I will try the Options > Uninstall as listed above and see what happens.
But like mae said, when a program tells you there is a problem somewhere, it is a problem, not just some message you ignore. Otherwise, why even bother with giving you a warning? Edit to add: Tried all the above, still get the error each time I run the patcher. Since it is only happening on the 64-bit machine, I would guess it has something to do with the 64-bit OS. |
I am getting timed out exceptions...is the server this is hosted on down?
|
it worked
This is EXACTLY what the problem was. I did ctrl alt del; went to processes, ended the process ( I had already closed the updatedr, therefore this was a second one as mentioned) reran updater and it worked perfect. THANK YOU!!!! :nana::nana::nana::nana:
Quote:
|
Interesting. If this shows up again for me, I'm going to check the process list. The system where I tend to see this almost never gets restarted because it's my local file and print server.
|
All times are GMT -5. The time now is 07:48 PM. |
vBulletin® - Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
© MMOUI