Yesterday I tried to install a Windows App via its built in App Store. Usually this works like a charm. This time the download seemed to succees (judged by the progress bar) but the installation failed with error 0x80070002;
Googling (and Bing’ing) found various issues with kind of the same description, ranging from “download failed” to “broken registry” (including repair guides). Yet none of the proposed solutions worked for me.
Hoping it would just be a temporary failure on the store side, I hit “retry” again and again while I was searching for other solutions (interrupted by a reboot – well you never know, sometimes it just helps). And suddenly a message appeared saying that a Microsoft account was required to install the app. That was strange as I had just switched to a MS account this day – and this message appeared just once! When I wanted to reproduce it it just failed with 0x80070002 again.
So I disconnected my account from MS again, reconnected afterwards and suddenly: The installation succeeded!
To make a long story short
If you experience an error 0x80070002 when installing an App from the store in Windows 8.1: Try to disconnect and reconnect your account from and to a Microsoft account:
- Win-C (open charms bar)
- Go down to settings
- Go down to PC settings
- Go to Accounts >> your account
- Disconnect your account
- Repeat the above to reconnect to your MS account
- Try to install the App
Java 8 is a bit more strict in JavaDoc parsing. This can lead to build failures in Maven when building the repo with warnings like:
Failed to execute goal org.apache.maven.plugins:maven-javadoc-plugin:2.7:jar (attach-javadocs) on project [projectname]: MavenReportException: Error while creating archive:
Exit code: 1 - [path-to-file]:[linenumber]: warning: no description for @param
Sure, the good solution would be to fix the JavaDocs. But in cases where you just clone a foreign repo, you probably just want to get it run and not start fixing it.
To ignore the erros, just turn off doclint by adding the following
<configuration> tag to your
<configuration> <!-- add this to disable checking -->
Some more solutions can be found in this StackOverflow thread.
Recently we migrated a Drupal managed website to a new server. – Everything was fine, just on some pages, some php-warnings showed up that did not show up on the original site.
After some investigation I checked php’s error_reporting setting and realized that the settings of the new new server were more sensitive than the old one.
The solution was pretty simple. As I definately didn’t want to start hacking around in Drupal, I just turned off showing the errors to the user:
Administer > Site configuration > Error reporting
(or in german:) Verwalten > Einstellungen > Error reporting
Error Reporting: Write errors to the log (instead: Write errors to the log and to the screen).
If Java comes up with the error message like “no main class found” you might have a problem like many many others before (as a google query reveals). Usually, the problem comes from one of the following issues:
Continue reading No Main Class Found