The newest version is bombing out in Windows Vista. When I open it, it stays open for a few seconds, then I get a "WowAceUpdater as stopped working" error.
There is a long standing bug problem with the WowAceUpdater going to 100% CPU utlization (sometimes 50% on dual CPU/core machines) when it goes to download the index. Several people have attempted to post bug information on the sourceforge site, but no one seems to be working to resolve the issues: http://sourceforge.net/tracker/?group_id=178751&atid=886395
Please help get this annoying and long standing bug problem resolved.
Any thought as to an easy method for using an older (without a bug) version of a plugin? I was picturing an option when you right-click that allows you to step the installed version back a version, but would install a newer version when that becomes available. I'm not sure if you'd want the most recent version or the most recent major release...
- The updater is designed as a developer tool to grab and install the latest release from the SVN. It's not meant as an auto-installer or old version manager. Ghoste 19:33, 28 November 2007 (EST)
Has anyone tried running this app on Linux? Aigarius 16:46, 1 December 2007 (EST)
--DARKGuy 23:49, 12 April 2008 (EDT):
Hi! I've discovered that WoWAce Updater has two weird bugs:
1. On a Win XP Pro SP2 box with .NET 2.0 already installed from dotnetfx.exe and Windows Updates (essential ones, 96 of them) without restarting, throws an error about "Value does not fall within the expected range".
2. On a Win XP Pro SP2 laptop with .NET 2.0 already installed and NO updates, it displays the AddOn list for a few seconds before throwing out some memory read/write errors. When looking at the debug log it is related to displaying the ads on the bottom of the main window.
Solution: Install .NET 2.0 Service Pack 1 and/or .NET Framework 3.0. That solved the problems for me.
I have been wanting to run this program under Linux either with Mono or WINE, but I don't even know -how- to run it, since it isn't even a .exe app, it's a lot of .manifest and .application files I don't know how to execute them, at least they don't look "executable" to me.
I'd be glad if someone could update the main page and state that the user needs .NET 2.0 with SP1 or .NET 3.0 before running or they'll run into errors!!
--Holyfield 21:21, 5 June 2008 (EDT)
Same Problem on Windows Vista with the last version of AceUpdater, but updating .NET doesnt seem to have any effect (.NET 3.5 installed)
-> AceUpdater displays the AddOn list for a few seconds before throwing out some memory read/write errors and crashes. (Data Execution Prevention, DEP)
striked addon names
One thing I noticed in 1.9 is some addons ( I guess outdated ) are striked out
I think it should be noted in the well ,, err ,, notes :)
I received the message that the updater needed to be updated. Now none of my wau works says to contact the user. Here is a copy of the log
PLATFORM VERSION INFO Windows : 5.1.2600.131072 (Win32NT) Common Language Runtime : 2.0.50727.42 System.Deployment.dll : 2.0.50727.42 (RTM.050727-4200) mscorwks.dll : 2.0.50727.42 (RTM.050727-4200) dfdll.dll : 2.0.50727.42 (RTM.050727-4200) dfshim.dll : 2.0.50727.42 (RTM.050727-4200)
SOURCES Deployment url : file:///C:/DOCUME~1/Micki/LOCALS~1/Temp/Temporary%20Directory%201%20for%20Install_WAU.zip/WowAceUpdater.application
ERROR SUMMARY Below is a summary of the errors, details of these errors are listed later in the log. * Activation of C:\DOCUME~1\Micki\LOCALS~1\Temp\Temporary Directory 1 for Install_WAU.zip\WowAceUpdater.application resulted in exception. Following failure messages were detected: + The referenced assembly is not installed on your system. (Exception from HRESULT: 0x800736B3)
COMPONENT STORE TRANSACTION FAILURE SUMMARY No transaction error was detected.
WARNINGS There were no warnings during this operation.
OPERATION PROGRESS STATUS * [5/6/2008 9:07:27 AM] : Activation of C:\DOCUME~1\Micki\LOCALS~1\Temp\Temporary Directory 1 for Install_WAU.zip\WowAceUpdater.application has started.
ERROR DETAILS Following errors were detected during this operation. * [5/6/2008 9:07:27 AM] System.Runtime.InteropServices.COMException - The referenced assembly is not installed on your system. (Exception from HRESULT: 0x800736B3) - Source: System.Deployment - Stack trace: at System.Deployment.Internal.Isolation.IStore.GetAssemblyInformation(UInt32 Flags, IDefinitionIdentity DefinitionIdentity, Guid& riid) at System.Deployment.Internal.Isolation.Store.GetAssemblyManifest(UInt32 Flags, IDefinitionIdentity DefinitionIdentity) at System.Deployment.Application.ComponentStore.GetSubscriptionStateInternal(DefinitionIdentity subId) at System.Deployment.Application.SubscriptionStore.GetSubscriptionStateInternal(SubscriptionState subState) at System.Deployment.Application.SubscriptionStore.CheckAndReferenceApplication(SubscriptionState subState, DefinitionAppId appId, Int64 transactionId) at System.Deployment.Application.DownloadManager.DownloadDeploymentManifestDirectBypass(SubscriptionStore subStore, Uri& sourceUri, TempFile& tempFile, SubscriptionState& subState, IDownloadNotification notification, DownloadOptions options, ServerInformation& serverInformation) at System.Deployment.Application.DownloadManager.DownloadDeploymentManifestBypass(SubscriptionStore subStore, Uri& sourceUri, TempFile& tempFile, SubscriptionState& subState, IDownloadNotification notification, DownloadOptions options) at System.Deployment.Application.ApplicationActivator.PerformDeploymentActivation(Uri activationUri, Boolean isShortcut) at System.Deployment.Application.ApplicationActivator.ActivateDeploymentWorker(Object state)
COMPONENT STORE TRANSACTION DETAILS No transaction information is available.
If anyone can help please let me know
Installing WAU without IE
Firstly, the linked addon has not been updated for use with Firefox 3 (the current release.) Also, it obviously doesn't work with Opera, Safari, or other browsers.
The problem is that
.application files must be "run" from the server, not downloaded and run from disk (brilliant move there, Microsoft!)
It might be worth noting that WAU can be installed by selecting Start, Run and entering the following command:
rundll32.exe dfshim.dll,ShOpenVerbApplication http://www.wowace.com/wau/WowAceUpdater.application
How to arrive at this:
- Load up
HKEY_CLASSES_ROOT\.application- this is the file extension association for
- Note that the default key value is
Application.Manifest- this is the name of the file type key.
HKEY_CLASSES_ROOT\Application.Manifest\shell\open\command- this is the command executed when you "open" an
.applicationfile either by double-clicking it, or selecting "Run" from a browser.
- The value of the default key is the actual command. This is
rundll32.exe dfshim.dll,ShOpenVerbApplication %1where
%1is the URL of the
This was verified on a brand new XP SP2 machine by first downloading and running the
setup.exe program, and then executing the above command.
Itsnoteasy 01:14, 7 July 2008 (EDT)
Debugging WoWAceUpdater High CPU Usage Issue
If this issue has been resolved, please disregard this information and post a fix! :)
I've been noticing the same High CPU usage issue on my box for a while now, so I decided to see what it was doing it. Fired up WowAceUpdater, waited a minute for it to peg the cpu at 100%.
Then loaded up Process Explorer to find the runaway thread. It was 3784, converted to hex is EC8. Loaded up Windbg, loaded the correct version of SoS.dll for the version of .net we are using and switched to thread 3784, which happened to be Thread 7.
Here is a portion of the stack dump of that thread:
OS Thread Id: 0xec8 (7) Current frame: (MethodDesc 0x792577a0 +0 System.Char.ToLower(Char, System.Globalization.CultureInfo)) ChildEBP RetAddr Caller,Callee 06f8e90c 7a4c6566 (MethodDesc 0x7a820150 +0x56 System.Text.RegularExpressions.RegexInterpreter.Forwardcharnext()), calling (MethodDesc 0x792577a0 +0 System.Char.ToLower(Char, System.Globalization.CultureInfo)) 06f8e914 7a4c74f9 (MethodDesc 0x7a820180 +0xf49 System.Text.RegularExpressions.RegexInterpreter.Go()), calling (MethodDesc 0x7a820150 +0 System.Text.RegularExpressions.RegexInterpreter.Forwardcharnext()) 06f8ea10 7a4b1615 (MethodDesc 0x7a81ce90 +0xa5 System.Text.RegularExpressions.RegexRunner.Scan(System.Text.RegularExpressions.Regex, System.String, Int32, Int32, Int32, Int32, Boolean)) 06f8ea24 7a4b14f3 (MethodDesc 0x7a81fad0 +0x103 System.Text.RegularExpressions.Regex.Run(Boolean, Int32, System.String, Int32, Int32, Int32)), calling (MethodDesc 0x7a81ce90 +0 System.Text.RegularExpressions.RegexRunner.Scan(System.Text.RegularExpressions.Regex, System.String, Int32, Int32, Int32, Int32, Boolean)) 06f8ea58 7a4c628c (MethodDesc 0x7a81f9f8 +0x30 System.Text.RegularExpressions.Regex.Match(System.String)), calling (MethodDesc 0x7a81fad0 +0 System.Text.RegularExpressions.Regex.Run(Boolean, Int32, System.String, Int32, Int32, Int32)) 06f8ea78 7a4d1887 (MethodDesc 0x7a81f9f0 +0x2b System.Text.RegularExpressions.Regex.Match(System.String, System.String, System.Text.RegularExpressions.RegexOptions)), calling (MethodDesc 0x7a81f9f8 +0 System.Text.RegularExpressions.Regex.Match(System.String)) 06f8ea88 0496751d (MethodDesc 0x7284f8 +0x1c5 WowAceUpdater.WowEnvironment.GetWoWVersion()), calling (MethodDesc 0x7a81f9f0 +0 System.Text.RegularExpressions.Regex.Match(System.String, System.String, System.Text.RegularExpressions.RegexOptions)) 06f8eac0 049671df (MethodDesc 0x728500 +0x1f WowAceUpdater.WowEnvironment.GetWoWInterfaceVersion()), calling (MethodDesc 0x7284f8 +0 WowAceUpdater.WowEnvironment.GetWoWVersion()) 06f8ead4 049671a1 (MethodDesc 0x7278e0 +0x9 WowAceUpdater.MainForm.<MonkeySee>b__2(System.Object, System.ComponentModel.DoWorkEventArgs)), calling (MethodDesc 0x728500 +0 WowAceUpdater.WowEnvironment.GetWoWInterfaceVersion()) 06f8eaf4 049671a1 (MethodDesc 0x7278e0 +0x9 WowAceUpdater.MainForm.<MonkeySee>b__2(System.Object, System.ComponentModel.DoWorkEventArgs)), calling (MethodDesc 0x728500 +0 WowAceUpdater.WowEnvironment.GetWoWInterfaceVersion()) 06f8eafc 7a4e7436 (MethodDesc 0x7a82f6c0 +0x86 System.ComponentModel.BackgroundWorker.OnDoWork(System.ComponentModel.DoWorkEventArgs))
Its hard to read on here but it looks like its basically caught in a RegEx loop of some sort. If one of the authors could provide the Symbols(.pbd's) that were used in the current release, i can get the exact code and variable that are causing it, then you could repro' it on your box and fix it.
Hope this helps, --Rizard