Patcher crashes with 'There was an unhandled exception'

[zespri]

Dear patcher author, could you please have a look at this screenshots
http://brutsoft.com/wow/Tmp/patcher_bug.zip that I've taken and tell me what may be the problem. I guess the problem is pretty rare, because otherwise this forums would be swarmed with "the patcher doesn't work" messages, still I can't make it start on my machine, it crahes immideately. If you can't read my screenshots, let me know your e-mail please, so I could send them to you in a more acceptable format. Thank you in advance!

[Chukers]

I am also having the same trouble... I am not sure what the problems is, but here is what I tried... I took a working copy of the \world of warcraft folder with cosmos installed off another computer and copied it to this computer and it does the same thing... so its somethign with the computer settings? maybe video or directx... I dunno at this point. I am going to go try to re-install my video now.


Chukers

[Chukers]

Also thius happened after I upgraded Hard drives. I used Norton Ghost ot copy my data.

P.S. re installing video drivers didn't help

Chukers

[yoshimo]

I tried to use the new Cosmos-Patcher
At the beginning it seems to run fine, but it crashed ,as it tried to install Cosmos*****
<unhandled exception>

[Chukers]

I went back to 2.20 and its working fine.


Chukers

[taltamir]

for me it happened when I upgraded the patcher to a newer subversion... Now it always says there is an unhandled exception (or simply freezes) whenever I try to manipulate the settings:

Restore defaults = unhandled exception
Change settings and click ok = freeze, has to be manually terminated.

[Epomyx]

Just want to point out that i have got this same problem as described above whit the 3.0.3 version of the patcher on a PC as i did se the issue aparently was experienced on Mac's earlier.

First I get an message saying: there was an unhandled exception.
Then Cosmos Patcher tells me: an exception of class NiObjectException was not handeled. The application must shut down.
Then I get: there was an unhandled exception.
If I continu to klick OK I continu to get: there was an unhandled exception error messages and i have to close the aplication using task manager.

I havn't seen any solution or fix to this, so unless I am blind I would be quite happy if that issue could be fixed.

[dormlock]

V3.5 should fix this problem but you guys will probably end up seeing like 3.5.1 or 3.6 just as soon as I go through Karl's list of things.

[Farmbuyer]

I ran the new Cosmos***** from the WoWTest folder while trying things on the PTR, and all was well. When I moved the patcher into the real WoW installation and deleted WoWTest, it crashed with this error.

I made an empty WoWTest folder, and then the patcher started fine. I changed the config to point to the real WoW folder (which was my goal in the first place), and after that I deleted the WoWTest folder again. No problems since.

So it looks like a problem where the patcher's configuration (presumably in the windows registy) points to folders or files which no longer exist, and the patcher does no error checking before trying to use them.

[dormlock]

Yes that would be the case somewhere I forgot to check for something along the way. Hopefully with 3.5 that won't happen but I can think of one spot where I might want to add something so that you can reselect the folder.

[jgleigh]

Unhandled exception error is also happening on the 3.5 Mac version.

Deleteing the prefs fixed the error, but now it gets stuck in the initial setup screen. None of the buttons work. Have to force-quit to get out of it.

[rhonin922]

I'm also getting the same error. After the patcher comes up, it has Error underneath the links and "hit k to cancel autorun" in red to the right. I don't even have autorun on. I hit k, it says "WoW Autorun canceled" but it still comes back every time.

[zackary]

Reinstalled game recently after fresh windows install (what fun =) ) and I get same error (unhandled exception) as everyone else. Never had problem before outside of updating issues but im sure thats probably unrelated.

[GreyWolfdog]

i too am getting (unhandled exception) error. :?:

Using win98se for operating system.

Gone back to 2.20 wich works fine.

[Benabik]

(Using Mac Patcher v3.5)

Manually editing the Preferences file (setting "RunSetup" to 0) and restarting the Patcher allows me to select my WoW folder. However, it asks me to select it twice and then quits with "Unhandled Exception". I'm out of ideas.

Too bad I over-wrote my old patcher...

[Quishy]

Unhandled Exception Error

Deleted the pref and plist from preference(s) path... no more error but unusable screen / window point (must force quit - no interaction with anything)

Have a Nice Day :lol:

[zespri]

I'd like to take time to report that patcher 3.5 has fixed the original problem for me. Thank you.

[Rosshambo]

The previous patcher did not give me any problems. However, 3.5 is giving me the unhandled exception error. It then loads the cosmos patcher just fine, but will not do a file check on startup (nor does it upload). Just thought i'd give you a warning.

[Legorol]

I can confirm that unhandled exception error occurs for me reproducibly, 100% of the time, when I launch the patcher. Version 3.5.

[dormlock]

Please post some details as to what steps to take to cause it to reproduce if it's just opening then tell me what the status text says.

[Legorol]

This is what I found so far, running v3.5 on Windows XP.

Symptom: when I launch the patcher, first a single standard small message dialog box pops up. The dialog box has no title, and has the message "There was an unhandled exception". There is a single OK button. Clicking OK makes the dialog box go away, and the main patcher window appears.

Way to reproduce: the error occurs 100% of the time if I have "Auto Update Cosmos on Opening" checked. If I uncheck it, the error doesn't occur.

Seems like the exception is occuring during the auto-update. If you want me to post the contents of my "Cosmos Prefs" file let me know.

[dormlock]

Won't be a need when you guys get 3.7 you'll be able to post a log file that logs the exception. Heres a sample for something that got me when I was making sure 3.7 ran.

Cosmos Starting up at 10:44 PM on 3/28/06
An excpetion occured.

ErrNum: 0

Message:

Stack trace:

ComosFunctions.GetWoWFolder%o<FolderItem>%

CosmosMain.CosmosMain.SetupGlobalState%%o<CosmosMain>

CosmosMain.CosmosMain.#Open%%o<CosmosMain>

CosmosMain.CosmosMain%o<CosmosMain>%

_MakeDefaultView

_Main

% main

[Rosshambo]

My problem goes exactly as described before. only happens on auto-update running winXP (pro corp)

[smccormack]

I've deleted preferences and the lot and all I can get is two chances to pick my WoW folder and then an unhandled exception. Here's the log

Cosmos Starting up at 10:12 AM on 3/29/06
An excpetion occured.

ErrNum: 0

Message:

Stack trace:

CosmosPreferences.IsCosmosAddon%b%o<CosmosPreferences>s

ComosFunctions.DetermineInstallationStatus

CosmosMain.CosmosMain.#Open%%o<CosmosMain>

CosmosMain.CosmosMain%o<CosmosMain>%

_MakeDefaultView

_Main

% main

[Greysyn]

Cosmos Starting up at 1:02 PM on 3/29/2006
An excpetion occured.

ErrNum: 0

Message:

Stack trace:

CosmosPreferences.IsCosmosAddon%b%o<CosmosPreferences>s

ComosFunctions.DetermineInstallationStatus

CosmosMain.CosmosMain.#Open%%o<CosmosMain>

Window.Window%%o<Window>

CosmosMain.CosmosMain%o<CosmosMain>%

_MakeDefaultView

_Main

% main

[buddakist]

I am running the Cosmos_Mac Patcher (current version) and i to overwrote my previous patcher. I am also getting this error. Can you please make the older patcher available to download while this problem gets addressed? Thanks guys.

[Log]

running v3.7 Win same problem as the others here's my log hoping for a quick fix to be able to stay on top of 1.10 hotfixes as they drop. No way to rollback since v2.20 Win of Cosmos Patcher is no longer included in any of the downloadable versions.

Cosmos Starting up at 2:58 PM on 3/29/2006
An excpetion occured.

ErrNum: 0

Message:

Stack trace:

CosmosPreferences.IsCosmosAddon%b%o<CosmosPreferences>s

ComosFunctions.DetermineInstallationStatus

CosmosMain.CosmosMain.#Open%%o<CosmosMain>

Window.Window%%o<Window>

CosmosMain.CosmosMain%o<CosmosMain>%

_MakeDefaultView

_Main

% main

[Grisu]

Now version 3.7 seems to be downloadable, but still got that "unhandled exception" error message when starting the updater. When turning "autoupdate at startup" of, than its fine, no error message. But the updater seem to work correct anyway when updating manually, but error messsage is not really nice for loved COSMOS... :(

Grisu

[heschlie]

Same here, had it last night, decided to wait for a fix today, got 3.7 still have the unhandled exception, exact same log as the one above.

[Legorol]

Version 3.7, Windows XP.

The unhandled exception error message still pops up on patcher startup, if auto-update is enabled. Unfortunately it's the exact same dialog box as before, it is not providing any additional info about the exception for me to paste here.

[dormlock]

Thanks for the log that will help me track down the error and get it fixed. Expect a new version thursday evening.

[pandamad]

I have the same problem. I am receiving the unhandled exception error on cosmos***** startup version 3.7

I still get some program functionality. If I go into “configure” and click restore default settings I also get the unhandled exception error.

The first time I ran cosmos I was asked to locate my WoW folder 3 times which seemed a bit odd.

When I edited the "Cosmos Prefs" this line seems a bit odd :)

<WoWPath>APHRcwEAAgAAAAARV29ybGQgb2YgV2FyY3JhZnQBAAAAABpDOl xHYW1lc1xXb3JsZCBvZiBXYXJj
cmFmdAMAAAAAAQAEAAAAAAEAAAAAAAAA</WoWPath>

Hope that helps. I may have a different problem to some people.

[dormlock]

Wow path is as it should be. Heres the reason:

FolderItem.GetSaveInfo Method

Allow saving FolderItem references without relying on the absolute path. Returns a String.

Syntax
FolderItem.GetSaveInfo RelativeTo, Mode


Parameters
RelativeTo
FolderItem
Mode
Integer

The returned string indicates a relative path with is relative to the folder passed in RelativeTo.

The Class Constants and values (in parentheses) for Mode are:

SaveInfoDefaultMode (0): The FolderItem should be open in any way REALbasic can possibly create it. This is the Default value.

SaveInfoRelativeMode (1): The FolderItem should only be opened using relative path information.

SaveInfoAbsoluteMode (2): The FolderItem should only be opened using absolute path information.

Note: The returned string is not intended to be human-readable and any modifications may render it useless.

[dormlock]

Since People keep looking at the wowpath and thinking it's goofed up the pref file now has an attribute stored with the path with a message about it.

Current IsAddon bug squashed and looking at other trace reports working them out.

Hehe when i added some support to tag prefs with a message I introduced a few new bugs myself got them fixed and discovered another one where the Select wow folder came up twice and also a problem when you would cancel and it would try to quit.

[Braydin]

Heres my log file from the exception error. Good luck on the fix. I look forward to using the new patcher, it has many features I have been wanting since beta!


Cosmos Starting up at 10:27 AM on 3/31/2006
An excpetion occured.

ErrNum: 0

Message:

Stack trace:

CosmosRetrieveData.StartSession%%o<CosmosRetrieveData>

CosmosRetrieveData.FetchFileList%%o<CosmosRetrieveData>

CosmosMain.CosmosMain.#Open%%o<CosmosMain>

Window.Window%%o<Window>

CosmosMain.CosmosMain%o<CosmosMain>%

_MakeDefaultView

_Main

% main

[Legorol]

Braydin, could you please specify which version of the patcher are you using? There were a number of new versions released in the past few days, so if you are not using the latest (version 3.8 at time of this post), please try with that.

[dormlock]

From the looks of the trace It's the wrong version of 3.7 since that Open should read Activate now. That would be my fault since I apparently sent the wrong version of 3.7.

Yes 3.8 was released early this morning and should resolve hopefully all known bugs.