24 - Error upon load/open
What steps will reproduce the problem?
1. Log in to WoW with Armory set to load (error #1)
2. Open Armory by clicking on icon (error #2)
3. Reloadui to repeat
What is the expected output? What do you see instead?
Appears to run normally, but UI throws up errors. Errors presented only on first load and first open. During session, errors do not seem to repeat. However, if you reloadui or log off and back in, the errors are presented again during the same actions.
What version and language of the product are you using?
v7.3.9 (english)
Do you have an error log of what happened?
Yes
Please provide any additional information below.
Error #1 (Upon load of Armory at char login):
===================================
Date: 2009-10-15 12:43:53
ID: 1
Error occured in: Global
Count: 1
Message: ...erface\AddOns\Armory\Frames\ArmoryPaperDollFrame.lua line 1751:
attempt to call method 'UpdateGearSets' (a nil value)
Debug:
(tail call): ?
[C]: UpdateGearSets()
...erface\AddOns\Armory\Frames\ArmoryPaperDollFrame.lua:1751 func()
...nterface\AddOns\Armory\Core\ArmoryCommandHandler.lua:176 Execute()
...nterface\AddOns\Armory\Core\ArmoryCommandHandler.lua:116 OnTimerUpdate()
...nterface\AddOns\Armory\Core\ArmoryCommandHandler.lua:47
...nterface\AddOns\Armory\Core\ArmoryCommandHandler.lua:47
Error #2 (Upon opening Armory GUI):
=============================
Date: 2009-10-15 12:47:53
ID: 2
Error occured in: Global
Count: 1
Message: ...erface\AddOns\Armory\Frames\ArmoryPaperDollFrame.lua line 1461:
attempt to call method 'GetNumEquipmentSets' (a nil value)
Debug:
(tail call): ?
[C]: GetNumEquipmentSets()
...erface\AddOns\Armory\Frames\ArmoryPaperDollFrame.lua:1461 ArmoryPaperDollFrame_OnShow()
[string "*:OnShow"]:1:
[string "*:OnShow"]:1
[C]: Show()
..\FrameXML\UIParent.lua:1937 ShowUIPanel()
Armory\Core\ArmoryBase.lua:1048 Toggle()
Armory\Core\ArmoryLDB.lua:43 OnClick()
Armory\Frames\ArmoryFrame.lua:579 ArmoryMiniMapButton_OnClick()
[string "*:OnClick"]:1:
[string "*:OnClick"]:1
| User | When | Change |
|---|---|---|
| Veyska | Fri, 30 Oct 2009 16:01:10 | Changed status from Waiting to Replied |
| Warmexx | Sun, 18 Oct 2009 10:29:14 | Changed status from Replied to Waiting |
| MhicAoidh | Thu, 15 Oct 2009 21:39:40 | Changed status from Waiting to Replied |
| Warmexx | Thu, 15 Oct 2009 19:26:25 | Changed status from New to Waiting |
| MhicAoidh | Thu, 15 Oct 2009 17:50:33 | Create |
- 10 comments
- 10 comments
- #10
Veyska Fri, 30 Oct 2009 16:01:08Never got around to trying 7.3.9 again and didn't set aside time between 7.3.10 and 7.4.1 to try the .10 release out, but figured you might be interested in knowing upgrading from 7.2.1 to 7.4.1 seems to have gone off for me without a hitch.
- #9
Warmexx Sun, 18 Oct 2009 10:28:54If you got a database conversion error you can expect things to go wrong. To be sure I just checked and I didn't notice any problems when mailing something to an alt.
I'm really interested in the backup Armory.lua data file that couldn't be converted. As you can see several people experienced conversion problems, but with that notice alone I can't take any action.
Since a lot has changed in 7.3.9 I suggest you start from scratch. I understand it's inconvenient but for now it's the only suggestion I have. If you want me to find another way I need to be able to reproduce the error you get, i.e. I need your 7.2.1 data file. And if I'm able to fix it I'll return the fixed file.
- #8
Veyska Fri, 16 Oct 2009 15:54:48I also got a similar error upon upgrading from 7.2.1 to 7.3.9, installed while WoW was not running. Rolled back to the previous version with a few-days-out-of-date back-up of the saved variables, but one thing I'd noted while checking mail with 7.3.9 running was that tooltips weren't updating their item counts after pulling/mailing things - one alt was my transmute alch, she made an epic gem and mailed it to another alt for storage and the tooltip count for the eternal/rare gem didn't go down by one and the epic gem's tooltip didn't show one in the mailed-to-alt's inbox.
- #7
Warmexx Fri, 16 Oct 2009 08:52:48The db update process is a bit radical: some combined storage containers are being split and then everything is converted to a binary format. Different people have tested this without any problems, so I'm curious why it fails in your case. Would you be so kind and mail your Armory.lua to warmexx at wow-neighbours dot com? I like to figure out what goes wrong.
- #6
MhicAoidh Fri, 16 Oct 2009 06:22:04Yes, I use armory just to keep track of my toons' inventory, gear, and professions. So, not too much trouble to log them all in and open the various windows. Posted the errors here so you'd be aware that the dB conversion may not be going as smoothly as anticipated.
- #5
Sinktinkler Fri, 16 Oct 2009 02:51:26After upgrading, I'm getting an error on login too, though mine's a little different (possibly due to having different modules enabled?): "Interface\AddOns\Armory\Core\ArmoryFriends.lua:40: attempt to index global 'dbEntry' (a nil value)"
Rather than blow away and redo all my Armory saved variables, I've reverted to the previous version for now. I can post the full lua error if it helps.
- #4
Warmexx Fri, 16 Oct 2009 00:07:03So you're fine now (except for the fact you'll have to re-login and rescan every character alas)?
- #3
MhicAoidh Thu, 15 Oct 2009 21:40:38No, I had WoW completely closed, downloaded the update via CurseClient, and then relaunched WoW. So, WoW was not running at time of update.
- #2
MhicAoidh Thu, 15 Oct 2009 21:39:39Suspecting it was an issue with dB conversion from the previous to new version, I renamed Armory.lua and Armory.lua.bak in my global saved variables folder. I then relaunched WoW, and no errors were presented and Armory appears to be functioning normally (sans having the information from the toons I have yet to log back in on, heh).
- #1
Warmexx Thu, 15 Oct 2009 19:26:17This looks like you did a hot update (without leaving WoW) and just reloaded the UI. If this is the case, always exit WoW completely when updating add-ons. Most of the time you get away with just a reload but if the number of source files have changed (or renamed) you get into trouble.
Since new source files have been added to this version, it would explain your error. Is my assumption correct?