I'm having an annoying issue with my AppInstaller file giving an error when trying to install an MSIXBundle file from a HTTPS URI:
App installation failed with error message: error 0x8007000D: Opening the package from location {package_name}.dev.msixbundle failed. (0x8007000d)
MSIXBundle Install Failure
The AppInstaller file looks like this:
<?xml version="1.0" encoding="utf-8"?>
<AppInstaller Uri="https://{domain}/{package_name}.dev.appinstaller" Version="1.0.0.0" xmlns="http://schemas.microsoft.com/appx/appinstaller/2018">
<MainBundle Name="{package_name}" Version="0.6.220.0" Publisher="CN={publisher}" Uri="https://{domain}/{package_name}.dev.msixbundle" />
<UpdateSettings>
<OnLaunch HoursBetweenUpdateChecks="0" ShowPrompt="true" />
</UpdateSettings>
</AppInstaller>
If I download the AppInstaller and MSIXBundle files locally and change the HTTPS protocol to be FILE:/// within the AppInstaller file, then it works fine. I can keep the AppInstaller Uri in the file to FILE:/// and set the MainBundle Uri to HTTPS and then it fails as well.
I've noticed that this only started happening on the latest 2 version of Windows 10 (i.e 2004 and 20H2). If I restart my PC, then the HTTPS protocol works fine and I can install the package by referencing the hosted AppInstaller file. But when I update the AppInstaller to indicate a new version of the Package has been released, I get the above mentioned error again during the update process. I've I uninstall the package completely and try to install it again, I get the error as well.
I've been unable to find a reliable solution for this issue, so I was hoping some clever people out there might be able to help or at least point me in an alternative route if the AppInstaller is too buggy on the latest versions of Windows 10.
Although the post is a bit older, I'd like to share my experience with a similar behavior.
I got the error code when hosting the installer files using a self signed certificate (SSL not code sign) for the server.
After installing the root certificate to 'Trusted Root Certificates' of the local computer (installing for current user did not fixed the error), the installer worked as expected.
I'm not sure if this was your problem, since the installation worked after restarting the computer. For me the appinstaller never worked as long as I had the certificate not installed.
Related
I installed Phalcon PHP as described in https://docs.phalcon.io/3.4/en/webserver-wamp.
In this case the URL reads 3.4 because it applies alike for versions 4 and 5.
The WAMP server version is 3.2.6 configured with PHP 8.0.13
Everything was fine so far, so I continued installing the developer tools using composer as described in https://docs.phalcon.io/5.0/en/devtools.
Composer was installed globally and so were the developer tools, but when I type "phalcon" in the command window, the following error is shown:
C:\>phalcon
Fatal error: Uncaught Error: Class "Phalcon\Script" not found in C:\Users\Joachim\AppData\Roaming\Composer\vendor\phalcon\devtools\phalcon.php:38
Stack trace:
#0 {main}
thrown in C:\Users\Joachim\AppData\Roaming\Composer\vendor\phalcon\devtools\phalcon.php on line 38
C:\>
PSR and Phalcon extensions were successfully installed and I can see them in the WAMP Localhost page.
The Path environment variable contains the path to phalcon, composer, wamp, etc, nothing is missing as far as I can see.
Have anyone dealt with this error?
What could be the problem?
I'm a bit late answering this, but in case anyone else stumbles across it via Google the problem is that some namespaces have been altered between Phalcon4 and Phalcon5. I believe Phalcon\Config is one of those classes.
Until the devtools have been updated for Phalcon5, you'll either need to build the scaffolding manually, or copy an old Phalcon 3 or 4 project and update the namespaces.
The perils of using alpha/beta releases, unfortunately.
you didn't mention which phalcon version but since you are using php 8 the only version supporting php 8 is phalcon 5
your issue is most likely in your php.ini for the cli since wamp uses different files for apache and cli.
to fix the issue first remove the devtools package you installed globally then edit the cli php.ini in [wampDir]\bin\php\php8.0.13\php.ini and include psr and phalcon and install the devtools again using composer
you can also download the phar file here and test it in the cli
php phalcon.phar
After last attacks, I upgraded MODX to 2.6.5 version. And now there is a problem with uploading files via Modx File Manager. There are no errors during uploading. Message in File Manager after all is "File successfully uploaded" but file isn't uploaded.
In logs there are several errors but nothing about file transfer. A lot of error in /core/xpdo/xpdo.class.php:
Could not load class: fastFieldParser from fastfieldparser.
Problem getting service parser, instance of class fastFieldParser, from path /core/components/fastfield/model/fastfield/
Where can i find solution if there are no errors about file transfer problem?
I'd recommend re-running the upgrade. I've found that Susan's install script works very well for quick reinstallations. If that doesn't work I'd recommend reviewing the server's PHP logs to see if there's anything useful in there.
Install script: MODX Install Script
I tried to install Neos CMS local under Windows 10 with a Wamp Apache Server. After creating the project with a composer and registering the Vhosts, I tried to run neos.demo/setup. Then I get an 500 internal server error with the message "Specified path not found”, for more information, take a look at the screenshot.
I checked the solutions for the exception code 1355480641, but nothing can solve my problem.
Thanks for your recommendations!
do you have set Neos.Flow.core.phpBinaryPathAndFilename in Configuration/Settings.yaml to the correct php.exe binary path?
This is not an actual solution, this is more of an alternative.
I was having troubles installing neos on windows 10 as well (not the same as you though), a really nice solution that I would recommend as alternative to wamp is bitnami-neos.
I got the same error in the current version of Neos CMS (v4.1). The solution to the problem was for me:
Adjust Configuration/Settings.yaml with the php.exe path (which you already did)
Launch an administrator cmd
Go to the Neos CMS directory
Run flow flow:core:compile
Run flow flow:cache:warmup
Now I could access Neos with XAMPP.
All credit for this answer goes to the following post: https://discuss.neos.io/t/running-neos-flow-on-windows-10-success/2752
I just installed Dart Editor on Ubuntu 14.04, opened the Sunflower demo, right clicked on sunflower.html, chose Run in Dartium, and was faced with "Could not start pub serve or connect to pub." So I went to Google and found the following reasons why this happens:
"Run in Dartium" doesn't invoke "pub serve" correctly for Dart files that aren't in web/ or test/ (But the Sunflower demo files are all in web/)
https://code.google.com/p/dart/issues/detail?id=18990
Project files must be inside "C:\Users[username]\dart" instead of "C:\progs\Dart\projects" (Doesn't help; I'm not on Windows, but would demos that come with Dart Editor be in the wrong place?)
https://code.google.com/p/dart/issues/detail?id=19659
Same problem in recent release shows up on Mac OSX, bug fix promised in that next release (Doesn't help; I'm not on Mac OSX and that next release already came)
https://code.google.com/p/dart/issues/detail?id=19143
Another service is listening on port 8080 (Nope, I checked the ports and also made sure nothing with dart pub serve was already running, plus rebooted a couple of times)
dart error - could not start pub serve or connect to pub
So I found more information that gave me the idea to try pub serve from the command line. So I went to the directory where the sunflower project was placed by the Dart Editor (where the pubspec.yaml is found) and in the command line I typed:
sudo /opt/dart/dart-sdk/bin/pub serve
Which resulted in:
You don't have a lockfile, so we need to generate that:
Resolving dependencies... (1.1s)
Downloading browser 0.9.1...
Got dependencies!
Loading source assets...
Serving sunflower web on http:// localhost:8080
Build completed successfully
Great, I thought, so I opened Chrome and visited http:// localhost:8080 and saw this:
404 Not Found
Could not find asset web in package sunflower.
And in my command line console I saw this:
[web] GET / → Could not find asset sunflower|web.
[web] GET /favicon.ico → Could not find asset sunflower|web/favicon.ico.
I am about to get more aggressive with my Google search and investigation, but I thought I would have this question out here just in case I cannot find the answer. Even though I encounter many obstacles before running my first Dart demo, which makes for a poor introduction (I know, Dart is new), I keep liking what people say about it and I am compelled to get this working. Please help me like Dart. :)
Much appreciated!
I came across similar error and this solved it for me:
1) Move all html/css/dart files to /web directory.
2) Than create a pubspec.yaml with your projects dependences (usually it's "browser" only).
You may try like this, [run]-->[Manage Launches], then unmarked "Use pub serve to serve the application", good luck!
I'm new to Umbraco and I'm try to install some packages from the Umbraco package Repository. I'm getting a 500 - Internal server error in the Umbraco CMS when trying to browse the packages. First I thought I did something wrong in my installation of Umbraco but when I look at the source code it looks like packages.umbraco.org are having problems. Can anyone confirm if they having the same problem?
Thanks
Download the packages from our.umbraco.org and install as a local package. If that doesn't work then it may be permissions. If you aren't able to download packages on our.umbraco.org, then the package server may be down.
First of all either check the logs or change the customErrors section of your web.config so that you can see more details on the error.
<customErrors mode="Off" />
I have on a few rare occasions installed a version of Umbraco where I think the installedPackages.config file was empty and without at least an empty <packages /> node it generates an error. Check the file looks like this as a minimum:
<?xml version="1.0" encoding="utf-8"?>
<packages />
You will usually find the file located in App_Data\packages\installed\installedPackages.config however I think this may have changed in more recent versions of Umbraco.
Some good tips already, so I'll add a less likely one!
I have seen this error when I've first installed and for some reason the .net worker process has crashed so the internal error is simply that the site can't find cassini (or IIS depending on your settings).
Or perhaps there is nothing wrong and it is in fact related to the current issue with the Umbraco servers:
ICYMI: Our ISP have issues with their virtualisation platform and it affects > http://umbraco.com , umbraco.tv, Our Umbraco and package repo.
https://twitter.com/umbraco/statuses/293297374271533056