The crash was very annoying... I lived with it until today when I finally checked the forums and found this thread. Please find a way to always auto-update in the future.
The crash was very annoying... I lived with it until today when I finally checked the forums and found this thread. Please find a way to always auto-update in the future.
I know I'm sorry about that. This was a one time thing.
Ever since WoWAce got its new file manager, I've been having problems with WoWAceUpdater on my desktop running Vista 32bit with UAC turned off.
Immediately after start, it sucks up 40% CPU and takes about 2 minutes to parse the list.
Updating also takes about 10 minutes, and it hangs for another 15 minutes after update.
The popup box to ask to confirm before updating, also takes around 15 seconds to appear.
The first time this happened, there was a stack trace in the Output log where one addon's download seemed to get a timeout error.
This hasn't happened since, but the extreme slowdowns still occur.
What's strange is that it works absolutely perfect on my laptop, running Vista 32bit with UAC turned ON.
I tried doing a Control Panel uninstall following the deletion of the 2.0 folder in the AppData folder, but this had no effect.
I update WITH externals and have Automatic Dependency checked, however the problem still occurred even with that unchecked. Other than that, all settings are as default.
I really like the changelog-summary at the end of an update.
1) Sometimes only the Addon-Name appears but no changes, although there were more changes then included libs
2) if you run libs embedded, it'd nice to see the changes for the updated libs as well, if you want to . I currently have libthreat installed twice to see the updatechangelog ;)
Integrated in Omen , and as seperate external addon Libthreat-1.0 .
A friend of mine is having the following error when booting up WAU, now I've read the common problems and to me it seems like a winsock problem, but the error is slightly different.
"Bypassing Cache, Reloading index from http://files.wowace.com/
Error loading addon list Object reference not set to an instance of an object.
Complete
Error During Download: System.Net.WebExcept ion: Unable to connect to the remote server ---> System.Net.Sockets.S ocketException: An invalid argument was supplied
at System.Net.Sockets.S ocket.get_ConnectEx( )
at System.Net.Sockets.S ocket.BeginConnectEx (EndPoint remoteEP, Boolean flowContext, AsyncCallback callback, Object state)
at System.Net.Sockets.S ocket.UnsafeBeginCon nect(EndPoint remoteEP, AsyncCallback callback, Object state)
at System.Net.ServicePo int.ConnectSocketInt ernal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Int32 timeout, Exception& exception)
--- End of inner exception stack trace ---
at System.Net.HttpWebRe quest.EndGetResponse (IAsyncResult asyncResult)
at System.Net.WebClient .GetWebResponse(WebR equest request, IAsyncResult result)
at System.Net.WebClient .DownloadBitsRespons eCallback(IAsyncResu lt result)"
Notice the yellow, is it still a winsock problem? :)
Hello, I'm pretty new to using WoW Ace Updater, Ive had the last version and its always worked fine for me, but ever since I updated it I've had an issue that seems to not want to update my mods. I get a message saying "Error During Update" for all mods. Is there a fix for this?
I cant get WAU to work at all I did what i checked the dependicies and then hit f4 and ran the updated all installed addons I get update errors and then when i start the game i get a bunch of errors. Why isnt this working right.
I have the exact same problem as scibat in Reply #46. I run Vista Ultimate 64-bit and I've tried updating all the way up til .Net Framework 3.5 beta and I get the "Cannot continue. The application is improperly formatted. Contact the application vendor for assistance." -message. And when I click details, I get this:
**********************
PLATFORM VERSION INFO
Windows : 6.0.6000.0 (Win32NT)
Common Language Runtime : 2.0.50727.1378
System.Deployment.dll : 2.0.50727.1378 (REDBITSB2.050727-1300)
mscorwks.dll : 2.0.50727.1378 (REDBITSB2.050727-1300)
dfdll.dll : 2.0.50727.1378 (REDBITSB2.050727-1300)
dfshim.dll : 2.0.50727.1378 (REDBITSB2.050727-1300)
ERROR SUMMARY
Below is a summary of the errors, details of these errors are listed later in the log.
* Activation of http://www.wowace.com/wau/WowAceUpdater.application resulted in exception. Following failure messages were detected:
+ Exception reading manifest from http://www.wowace.com/wau/WowAceUpdater.application: the manifest may not be valid or the file could not be opened.
+ Manifest XML signature is not valid.
+ Access is denied.
COMPONENT STORE TRANSACTION FAILURE SUMMARY
No transaction error was detected.
WARNINGS
There were no warnings during this operation.
ERROR DETAILS
Following errors were detected during this operation.
* [25-09-2007 10:12:40] System.Deployment.Application.InvalidDeploymentException (ManifestParse)
- Exception reading manifest from http://www.wowace.com/wau/WowAceUpdater.application: the manifest may not be valid or the file could not be opened.
- Source: System.Deployment
- Stack trace:
at System.Deployment.Application.ManifestReader.FromDocument(String localPath, ManifestType manifestType, Uri sourceUri)
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)
--- Inner Exception ---
System.Deployment.Application.InvalidDeploymentException (SignatureValidation)
- Manifest XML signature is not valid.
- Source: System.Deployment
- Stack trace:
at System.Deployment.Application.Manifest.AssemblyManifest.ValidateSignature(Stream s)
at System.Deployment.Application.ManifestReader.FromDocument(String localPath, ManifestType manifestType, Uri sourceUri)
--- Inner Exception ---
System.Security.Cryptography.CryptographicException
- Access is denied.
- Source: System.Deployment
- Stack trace:
at System.Deployment.Internal.CodeSigning.SignedCmiManifest.VerifyPublicKeyToken()
at System.Deployment.Internal.CodeSigning.SignedCmiManifest.Verify(CmiManifestVerifyFlags verifyFlags)
at System.Deployment.Application.Manifest.AssemblyManifest.ValidateSignature(Stream s)
COMPONENT STORE TRANSACTION DETAILS
No transaction information is available.
***********************
Searched, and also read tons of threads, looking for the answer to this issue.
I have used the updater for several months, but with the new version that installs to the program menu I have not had any luck. I went back to using an old version to update, but want to stop that.
I have the most recent WUA installed this morning again. I have removed all previous updater instances before doing so. Windows XP fully updated, IE7, but use FF as primary browser.
When I select the updater it starts, I see the window open, and then it is closed again in a flash.
I am sure I am making a simple error, but I am not seeing it.
Just wanted to mention on start up today it seems to have 'forgotten' mods that I had set to ignore. NO a big deal and resetting them to ignore works. More an fyi then anything.
Just wanted to mention on start up today it seems to have 'forgotten' mods that I had set to ignore. NO a big deal and resetting them to ignore works. More an fyi then anything.
It does that every time you update, I put .svn folders in the addons I don't want updated because of that.
Is an option to ignore SVN folders in the addon libraries present in WAU? What I'd like for WAU to do is to update from zips and leave SVN folders alone. I've checked 'Skip SVN Working Copies' but the addons are listed under SVN and not 'installed' still.
I keep getting an "Cannot Start Application" error, whenever I try to download & install WAU. I've tried searching for a solution, but haven't found anything. Any help would be appriciated.
Searched, and also read tons of threads, looking for the answer to this issue.
I have used the updater for several months, but with the new version that installs to the program menu I have not had any luck. I went back to using an old version to update, but want to stop that.
I have the most recent WUA installed this morning again. I have removed all previous updater instances before doing so. Windows XP fully updated, IE7, but use FF as primary browser.
When I select the updater it starts, I see the window open, and then it is closed again in a flash.
I am sure I am making a simple error, but I am not seeing it.
Thank you.
Not sure why this was moved, and with no help or comments included.
That said, this issue I stated above is not linked to the particular version this current thread is specifically about. My solution may be solved in general by diagnosing what occured with the last 3 versions that all behaved the same on my system.
Luckily I found a 1.9.10-Version in my Download-directory on my Harddrive, everything works fine now again. A little executable in a directory of my choice, thats the way it should be.
Where can I find the old working version? Today I installed, reinstalled, installed and reinstalled over and over again but only get errors, the older versions worked fine. I rather go with a working non-supported one than a new shiny supported broken one.
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
I know I'm sorry about that. This was a one time thing.
Unbelievable it may be but many people I know are very resistant to crashs:
"Hmm, let's try this - Uuh, it crashed - Let's just try again - Ooh, there it goes again - Oh, well I'll just try again in 20 seconds..."
If you know what I mean...;)
Immediately after start, it sucks up 40% CPU and takes about 2 minutes to parse the list.
Updating also takes about 10 minutes, and it hangs for another 15 minutes after update.
The popup box to ask to confirm before updating, also takes around 15 seconds to appear.
The first time this happened, there was a stack trace in the Output log where one addon's download seemed to get a timeout error.
This hasn't happened since, but the extreme slowdowns still occur.
What's strange is that it works absolutely perfect on my laptop, running Vista 32bit with UAC turned ON.
I tried doing a Control Panel uninstall following the deletion of the 2.0 folder in the AppData folder, but this had no effect.
I update WITH externals and have Automatic Dependency checked, however the problem still occurred even with that unchecked. Other than that, all settings are as default.
What gives?
1) Sometimes only the Addon-Name appears but no changes, although there were more changes then included libs
2) if you run libs embedded, it'd nice to see the changes for the updated libs as well, if you want to . I currently have libthreat installed twice to see the updatechangelog ;)
Integrated in Omen , and as seperate external addon Libthreat-1.0 .
Notice the yellow, is it still a winsock problem? :)
Thanks in advance.
**********************
PLATFORM VERSION INFO
Windows : 6.0.6000.0 (Win32NT)
Common Language Runtime : 2.0.50727.1378
System.Deployment.dll : 2.0.50727.1378 (REDBITSB2.050727-1300)
mscorwks.dll : 2.0.50727.1378 (REDBITSB2.050727-1300)
dfdll.dll : 2.0.50727.1378 (REDBITSB2.050727-1300)
dfshim.dll : 2.0.50727.1378 (REDBITSB2.050727-1300)
SOURCES
Deployment url : http://www.wowace.com/wau/WowAceUpdater.application
ERROR SUMMARY
Below is a summary of the errors, details of these errors are listed later in the log.
* Activation of http://www.wowace.com/wau/WowAceUpdater.application resulted in exception. Following failure messages were detected:
+ Exception reading manifest from http://www.wowace.com/wau/WowAceUpdater.application: the manifest may not be valid or the file could not be opened.
+ Manifest XML signature is not valid.
+ Access is denied.
COMPONENT STORE TRANSACTION FAILURE SUMMARY
No transaction error was detected.
WARNINGS
There were no warnings during this operation.
OPERATION PROGRESS STATUS
* [25-09-2007 10:12:39] : Activation of http://www.wowace.com/wau/WowAceUpdater.application has started.
ERROR DETAILS
Following errors were detected during this operation.
* [25-09-2007 10:12:40] System.Deployment.Application.InvalidDeploymentException (ManifestParse)
- Exception reading manifest from http://www.wowace.com/wau/WowAceUpdater.application: the manifest may not be valid or the file could not be opened.
- Source: System.Deployment
- Stack trace:
at System.Deployment.Application.ManifestReader.FromDocument(String localPath, ManifestType manifestType, Uri sourceUri)
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)
--- Inner Exception ---
System.Deployment.Application.InvalidDeploymentException (SignatureValidation)
- Manifest XML signature is not valid.
- Source: System.Deployment
- Stack trace:
at System.Deployment.Application.Manifest.AssemblyManifest.ValidateSignature(Stream s)
at System.Deployment.Application.ManifestReader.FromDocument(String localPath, ManifestType manifestType, Uri sourceUri)
--- Inner Exception ---
System.Security.Cryptography.CryptographicException
- Access is denied.
- Source: System.Deployment
- Stack trace:
at System.Deployment.Internal.CodeSigning.SignedCmiManifest.VerifyPublicKeyToken()
at System.Deployment.Internal.CodeSigning.SignedCmiManifest.Verify(CmiManifestVerifyFlags verifyFlags)
at System.Deployment.Application.Manifest.AssemblyManifest.ValidateSignature(Stream s)
COMPONENT STORE TRANSACTION DETAILS
No transaction information is available.
***********************
Any solution for this problem?
Thx :)
/nk
Searched, and also read tons of threads, looking for the answer to this issue.
I have used the updater for several months, but with the new version that installs to the program menu I have not had any luck. I went back to using an old version to update, but want to stop that.
I have the most recent WUA installed this morning again. I have removed all previous updater instances before doing so. Windows XP fully updated, IE7, but use FF as primary browser.
When I select the updater it starts, I see the window open, and then it is closed again in a flash.
I am sure I am making a simple error, but I am not seeing it.
Thank you.
Just wanted to mention on start up today it seems to have 'forgotten' mods that I had set to ignore. NO a big deal and resetting them to ignore works. More an fyi then anything.
It does that every time you update, I put .svn folders in the addons I don't want updated because of that.
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=128818&SiteID=1
Not sure why this was moved, and with no help or comments included.
That said, this issue I stated above is not linked to the particular version this current thread is specifically about. My solution may be solved in general by diagnosing what occured with the last 3 versions that all behaved the same on my system.
Where can I find the old working version? Today I installed, reinstalled, installed and reinstalled over and over again but only get errors, the older versions worked fine. I rather go with a working non-supported one than a new shiny supported broken one.