Simple question... Using Visual Studio 2013 to build and deploy A Windows Store App for Windows 8.1 with Javascript. Unfortunately, even basic sample apps will not deploy. The error that pops up everytime when attempting to deploy is RDSAppXNotifyRecoveryTrigger.
I cannot seem to find any information on this error which makes it very frustrating. There is no problem when building the solution, however then we get the message...
The app needs to be deployed. When you click deploy we get this annoying ERROR: Error 1 Error : DEP0700 : Registration of the app failed. error 0x80070003: AppX Deployment operation failed. The specific error text for this failure is: RDSAppXNotifyRecoveryTrigger (0x80073cf9)
So it would help if I could find anything on MSDN about this error unfortunately someone asked this same question and then the entire post was deleted from the forums. Please help, I have tried to repair my Visual Studio installation, since even when you open a brand new Template App and press F5 you get this error, so I am thinking something is wrong or corrupt in my environment that is preventing any type of Windows Store App deployments, I cannot even run the apps. Thank you for any suggestions.
The specific Error 0x80073cf9 is related to apps not being able to be installed with Windows Store.
Some users have been successful with any of these 2 solutions:
1: The problem is that the folder AUInstallAgent is missing from the Windows folder.
Press Win+R, in Run type %windir% and press Enter. Create new folder named AUInstallAgent if that is missing in the Windows directory. Reboot computer
2: Start Command Prompt with 'Run as Administrator' option.
run this command:
powershell -ExecutionPolicy Unrestricted Add-AppxPackage -DisableDevelopmentMode -Register $Env:SystemRoot\WinStore\AppxManifest.xml
Hope this helps.
I have the same problem and this did not work for me. Still found lots of comments that this worked for others.
Related
When I try to sideload my Outlook add-in, created based on the last Ignite session by Andrew Salamatov, I get following error when I add the add-in from a URL (https://bulkpermissiondemo.azurewebsites.net/manifest-bulkpermission.xml): "The app can't be installed. This app isn't supported by the version of Exchange Server that your account connects to."
any idea what I'm doing wrong?
Thanks :-)
We’ve tried installing the manifest provided in the link but were unable to reproduce the error listed in the original post on recent builds. Could you try installing the manifest again and see if the same error occurs? If so, would you be willing to provide the email address for the account you are trying to install the add-in to? Then we can take a look at the server logs to see what the issue might be.
I'm getting the following error when trying to upgrade an application I wrote:
Sorry an error occurred
The application cannot be installed due to a certificate problem. The
certificate does not match the installed application certificate, does
not support application upgrades, or is invalid. Please contact the
application author.
Here is a screenshot:
I'm the application author. I recently created a new project and copied the old project files to the new location.
Is this due to that or am I possibly using a different certificate somehow? In the drop down list I have multiple entries pointing to same cert. I will try going through them but I'm wondering too if it's possible if anyone else has run into this issue.
I was using the incorrect cert. When I created a new project, Flash Builder preloaded certs from somewhere. They looked correct, however, the cert I was using was not in that list. So I opened the previous project and found a cert from that the project was using. After recompiling and attempting to update, the install went correctly with no error.
we have a windows 8.1 app in the windows store that sometimes crashes or hangs and we are unable to receive reports about hangs and crashs reported by the user via the store.
Collecting of telemetriy data is enabled in the store like mentioned in this MSDN-Article(http://msdn.microsoft.com/en-us/library/windows/apps/hh967787.aspx).
So I did a crash of the app by myself, took a look in the WER-ReportArchive(%localappdata%\Microsoft\Windows\Windows Error Reporting) and found a .cab & .wer-file. So I think the report was sended to microsoft, but theres still no crash or hang documented in the Dashboard of the App Store.
I tried to get a crashdump via Windows Error Reporting - LocalDumps (msdn.microsoft.com/en-us/library/ bb787181%28VS.85%29.aspx), but this dump is only generated when an error occurs.
In my case mostly the app just hangs!
I also tried to configure Windows Error Report - Registry Entries (http://msdn.microsoft.com/en-us/library/bb513638%28VS.85%29.aspx), but it seems most of the entries are just ignored.
I noticed WER is creating a dump-file of AppHangs as well, before sending the data to Microsoft (memory.hdmp in ReportQueue). But this files are deleted immediately after sending.
Does somebody know a way to get memory dumps and further information for AppHangs as well?
Thanks in Advance.
I think you could use the posibility of Just-In-Time or postmortem debugging via setting registry key for AeDebug, if you can create the crash.
Have a look at:
Improving apps with Quality reports
https://blogs.msdn.microsoft.com/windowsstore/2012/06/27/improving-apps-with-quality-reports/
Debugging a Windows 8.1 Store App Crash Dump
https://blogs.msdn.microsoft.com/ntdebugging/2014/01/13/debugging-a-windows-8-1-store-app-crash-dump/
Configuring Automatic Debugging https://msdn.microsoft.com/en-us/library/bb204634(vs.85).aspx
Using WER: Collecting User-Mode Dumps https://msdn.microsoft.com/en-us/library/bb787181(v=vs.85).aspx
Enabling JIT-Attach Debugging https://msdn.microsoft.com/en-us/library/2ac5yxx6.aspx
Several weeks ago side loading was working on my windows phone 8 device. I had installed a valid enrollment token (.aetx file). I was able to successfully side load signed .xap files (either via downloading in IE or attaching to an e-mail). All was good.
Then I ran down the battery and left the device for dead for over a week. When I tried to run the old side loaded apps they worked. But when I tried to side load a new xap I got an error message that said something about it having been too long since the enrollment token was verified with Microsoft. I wish I'd written it down, because I can't get the error to show up again.
Now when I try to side load apps nothing happens at all. It pops up the familiar dialog that confirms I want to install the app ("Would you like to install [my app] from [company name]?"), then I click install and the dialog disappears and the app isn't installed.
When I try to install the .aetx again it pops up the dialog to install, I click install, and then nothing (same as the first time). Xap files still won't install.
Guessing that the phone needs to re-verify the enrollment token with Microsoft I tried waiting 24 hours, but that didn't help. I'm running out of ideas.
In lieu of a direct answer, could someone help me at least get an error message? Nothing shows up in the output window in Visual Studio when I try to side load while debugging an app and I'm not able to find any OS level error logs.
Did you try to install the aetx on another phone or did you try to reset your phone? You should also watch out for invalid date and time on the phone. I've run into similar problems with Lumias which keep on resetting to the 1.9.2012 7:00. The aetx was then declared invalid and was not installed.
Incidentally, it eventually started working for me again. I can't recall now how long it took, about a week I think, but I'm guessing eventually it called home and re-activated the enrollment token.
Tried to open an SSIS project I had been working on today and received this lovely error:
Unable to generate temporary class (result=1)
error CS0009: Metadata file 'c:\WINDOWS\assembly\GAC_MSIL\System.Xml\2.0.0.0_b77a5c561934e089\System.XML.dll' could not be opened -- 'No metadata was found.'
Anyone know why this happens and how to correct it, I've Googled and haven't found any valid solutions relating directly to SSIS. It is only happening with BIDS 2008 and SSIS project types and I tried the same packages (as well as creating a new one) on my other machine and it was fine.
Any ideas? Thank you.
Since you cannot actually browse to that directory I used Command Prompt on another machine to copy the System.Xml.dll and then transfered it over to the problem directory with Command Prompt on the machine I was getting this error on.
That simple.