WoWReader Issues & Help (v.4)Follow

The error was fixed for me as well by completely uninstalling my existing copy of WowReader, and downloading and installing the newest version. Thanks for the update, guys.

In reference to the UAC problem mentioned above -- I've found that installing things into the "C:\Program Files" folder (or "C:\Program Files (x86)" folder with Vista 64-bit) will cause those "Cancel or Allow" messages to pop up an inordinate number of times... I always create a folder on the C:\ drive for whatever program I'm installing, and install it there instead of the default Program Files location. Makes Vista much easier to live with.

For example, I have WoW installed in "C:\World of Warcraft\" instead of "C:\Program Files (x86)\Blizzard\World of Warcraft\" which is where it wanted to install itself. Similarly, I have WowReader installed in "C:\World of Warcraft\WowReader\". I have no problems with the UAC popping up in normal circumstances (only when updates are downloaded and installed.)

Hope that helps...

Edited, Nov 27th 2007 5:49am by lmacneill

whhy does online play freeze alot??? like it will play good for a while then just freeze and then start up again.

I've been having trouble manually uploading my information. I even un-installed and re-installed the most recent reader. Is anyone else having trouble with updating to the Alla's site? It's still showing my characters info from weeks ago and no matter what I upload, nothing changes. I'm not sure it's a site problem or if the reader is just no longer collecting data.

Please advise.

I was having that problem consistently and finally chose to upload my info manually. Now, it seems that's loused up as well. Hopefully it all gets fixed soon.

I get the same error. But if I tell the shortcut to run as administrator, I still get the WoW.exe location popup...but after I click OK the WoWReader opens normaly.

Edited, Jan 4th 2008 2:01pm by Fyredrake

I am going to go out on a limb here and opine that perhaps the fact that the inability to upload the information from the wr2.lua and Blizzard's Armory being down may be correlated.

I am getting the error:



Any suggestions on how to fix this?

Thanks.

I recently purchased a new computer which runs windows vista 32 bit (not ultimate)
I downloaded the wowreader application and as soon as I try to run it i see for a split second what looks to be the automatic update running but it goes by so fast I can not be sure. Once that happens it opens up a window and asks me where wow is installed. I then browse to the wow folder and click on the wow.exe inside it and as soon as I do wowreader just shuts itself down I watched it in task manager under the processes, it is there running until I tell it where wow is installed and as soon as I click open the process dies and wowreader will not run.
I have the latest version of .NET installed.
I have un-installed / re-installed and still the exact same thing happens each time.

Any assistance is appreciated.

( hope this gets posted to the proper place this time )

Well, WowReader has stopped working for me again...

Here's the Error Log this time:
Unhandled exception log - 1/23/2008 4:37:12 AM
An attempt was made to load a program with an incorrect format. (Exception from HRESULT: 0x8007000B)
at LuaInterface.LuaDLL.lua_open()
at LuaInterface.Lua..ctor()
at wowreader.LuaData..ctor(MainWindow mw, WDBReader creatures, WDBReader quests)
at wowreader.MainWindow.ReadCacheData()
at wowreader.MainWindow.DoInit()
at wowreader.MainWindow.Main(String[] args)
Microsoft Windows NT 6.0.6000.0
v2.0.50727
C:\Windows\Microsoft.NET\Framework64\v2.0.50727\


I have no idea what any of it means... It just started doing this... Won't run, won't do anything -- just immediately jumps to "Log saved to Error.txt" or whatever...

I deleted all the WowReader files (the installation folder, the Wr2.lua files, the WoW cache files, even all references to WowReader in the Registry) and downloaded a fresh copy and re-installed it. Same thing, only now it asks me where WoW.exe is, and THEN crashes.

Please help.

I did update it again, and yes it does work -- but ONLY if I run it as Administrator. (WinVista 64-bit).

If I don't run it as administrator, I get the following:

Unhandled exception log - 1/25/2008 8:07:27 PM
The process cannot access the file 'C:\World of Warcraft\WowReader\startup.log' because it is being used by another process.
at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy)
at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, FileOptions options)
at System.IO.StreamWriter.CreateFile(String path, Boolean append)
at System.IO.StreamWriter..ctor(String path, Boolean append, Encoding encoding, Int32 bufferSize)
at System.IO.StreamWriter..ctor(String path, Boolean append)
at System.IO.File.AppendText(String path)
at wowreader.MainWindow.Main(String[] args)
Microsoft Windows NT 6.0.6000.0
v2.0.50727
C:\Windows\Microsoft.NET\Framework\v2.0.50727\

So, yes it's working again... But I didn't have to run it as an Administrator before... No big deal for me, but I'm sure some ppl will complain about that, so you might want to look into it.

EDIT: I didn't notice this earlier, but now WowReader messes with TeamSpeak somehow... Maybe it's the fact that I'm running WowReader in Admin mode, and nothing else in Admin mode -- I don't know. But with WowReader running, TeamSpeak will not work unless it's in the foreground (i.e. not running in the background behind WoW). So I can't use T.S. in-game anymore, unless WowReader is not running. I can still run WowReader after I exit WoW, and have it read the cache files and automatically upload all the data -- but I have to remember to do this when I exit WoW. Kinda liked it the way it was before...

Edited, Jan 26th 2008 10:04pm by lmacneill

Why is it I have noticed many posts about the update delay in the quest log and bag contents and such. However I have not seen a single reply from any of the admins about their attempts to fix this? Is it that they don't care. I pay for this site and have a reasonable expectation of things to work properly. Making it so that I have to log in and out a few times to get it to update to be usable is not acceptable. I like Allakhazam and the features you all have but you are not the only game support site out there. Please give us a fix for this issue or at least acknowledge that it is a problem and let us know what you are doing to fix it.