I am trying to install a package (oForms) with a new Orchard 1.8 installation, but receiving the following error:
"Package installation failed: There was an error installing the requested package. This can happen if the server does not have write access to the '~/Modules' or '~/Themes' folder of the web site. If the site is running in shared hosted environement, adding write access to these folders sometimes needs to be done manually through the Hoster control panel. Once Themes and Modules have been installed, it is recommended to remove write access to these folders."
This seemed rather straightforward, however my host has confirmed permissions are fine (and even added Everyone/Full Control to the folder), so I'm lost and appears to be happening with all modules from the Gallery, not just oForms. I changed the Config/log4net.config file to log everything, and I don't see anything specific in there except where it logs the same message above. Nothing outside of that stands out at all.
Is there a way to see why this is failing? Or, if not, is there a way to get the module and install it manually? I tried to download from the gallery, but it's just a NuGet package so I'm not sure how to take that and grab the raw module files.
You can use a program like 7zip to unzip the nuget package, then copy in the module manually yourself.
As for the permissions, when adding a new permission to the folder use:
IIS AppPool\name of your application pool
I also had this exact error message when installing modules from the gallery, and it took me a while to figure out what was happening. I made new installations, copying over files one-by-one, and eventually found the culprit. For my case anyways...
For me, it was all due to a bad formatting in my custom Theme. Specifically the Theme.txt file. The line where is says Version:, I had it formatted without any "."
Good:
Version: 1.0
BAD:
Version: 1
Yes, doing this simple mistake prevented me from installing Modules.
Related
I have an application, which is getting installed C:\ProgramFiles\RootFolder\InstallDir.
I have another application which is also getting installed in same root folder , eg:
C:\ProgramFiles\RootFolder\InstallDirofAnotherApp.
Here when I am trying to reinstall my application, it is deleting the entire Root Folder, It doesn't mind about the another installation of the other one.
So, it is deleting C:\ProgramFiles\RootFolder
Is there any setting to do like that? This is a legacy project and I am new to this. Unable to fine the cause
Thanks,
Nanda
What type of projects are these applications (basic MSI, or InstallScript)? Check [INSTALLDIR] (General Information -> INSTALLDIR) in both packages; if these properties are different, see if there is any custom action that perhaps delete some files/directories.
I am in the process of migrating to the latest version of ProGet. I'm currently using version 3.8.6, so am quite far behind the stable release.
I decided to start fresh, moving to a brand new Windows Server 2016 box in AWS, and using RDS for the SQL database.
The new setup is working perfectly, I have imported our NuGet packages by creating a feed, entering a Drop Path and dropping all of the packages there. ProGet picked up on this and moved them all to the Feed.
However, I am now trying to import our npm packages. I've created the feed, added a drop location and moved all the npm packges over. On the old server, they're all already in subfolders. ProGet seems to refuse to add them unless they're in the root folder specified as the Drop Path. So I've moved some packages there (inconveniently they're all called package.tgz...) and it picks them up, moves them to /ProgramData/ProGet/Packages/.npm/F5/ puts them in folder too but then does not become visble in the feed on the web interface.
The package number increases, and if I click packages I can see them all, then click into them and download the package, but it doesn't show up on the main Feed 'Page'.
On the other hand, if I manually upload a package via the web interface, it doesn't put the packages in the same location as above, but it is visible on the main feed page... Is this a bug or am I doing something wrong? The NuGet packages work perfectly using the same method, so I'm confused as to why npm isn't working.
I noticed this same behavior when using the bulk upload utilizing the drop path. From what I can tell, you must have at least one version with the "latest" tag on the details for it to show anything in the Feeds view.
High level overivew of the steps involved:
Use MSDeploy to create a deployment package
Edit the contents of the zip package and then repackage it
Deploy to a remote server fails as the values in the systeminfo.xml are different to what it expects i.e. the list of <installedComponentInfo> must be different from the source to the destination server. If I manually edit the xml and remove all the <installedComponentInfo> re-zip the package and try again it works fine.
So can I tell MSDeploy to ignore the systeminfo.xml file when it does the deploy step above or any other suggestions around the <installedComponentInfo>?
The error is:
Warning: Skipping source dirPath (c:\blah\blah\Package) because of rule SkipInvalidSource.
The Zip package 'c:\blah\blah\Package\MyPackage.zip' could not be loaded.
And nothing gets deployed to the remote IIS server.
I have done several searches on this so any answers on why the systeminfo.xml is causing an issue or more importantly a workaround to ignore it please?
Thanks in advance.
Try disabling the SkipInvalidSource rule.
msdeploy -verb:sync -source:webServer -dest:webServer,computerName=Server2 -disableRule:SkipInvalidSource
I am curious why you are manually editing the package. You can use MSBuild to customize the package or create a custom package yourself using MSDeploy.exe directly.
http://www.dotnetcatch.com/2016/05/19/extending-the-webdeploy-manifest/
https://technet.microsoft.com/en-us/library/dd569019(v=ws.10).aspx
I've created a custom module for Orchard and packaged it up as a .nupkg; and now I am testing deployment but I have hit a snag.
If I create a new Orchard site using the Web Platform Installer and install my module (by uploading the nupkg file), everything works fine - the module's single feature is enabled and its entry in the Admin menu appears.
If I build Orchard from source and install my module (again by uploading the nupkg file), everything works fine again.
If I create a site manually from Orchard.Web.1.9.1.zip the site works just fine, but when I install my module by uploading the nupkg, the installation goes through without an error; the module appears in the Modules list and its feature can be enabled/disabled without reporting an error; but the module's Admin menu entry does not appear, nor does the widget it provides and the module's assemblies do not get added into dependencies.xml.
NOTE: my module is precompiled (this is the way we want to ship it) so it contains a bin folder with its assembly and some dependencies contained in it but the module folder does not contain a csproj file. Therefore it should be loaded by the PrecompiledExtensionLoader (at least as I understand http://docs.orchardproject.net/Documentation/Orchard-module-loader-and-dynamic-compilation that should be the case).
Things I have already checked:
Comparing the directories for the installation from Web Platform Installer and the installation created manually from Orchard.Web.1.9.1.zip with WinMerge, there do not appear to be any significant differences. Except that all of the modules listed in dependencies.xml in the WPI site are loaded using the PrecompiledExtensionLoader whereas the modules loaded on the manually created site are all loaded using the DynamicExtensionLoader - and as noted, my module is not listed in the dependencies.xml on the manually created site.
There is nothing logged in the Orchard error log and even when I turn up logging to INFO level and try uninstalling and reinstalling the module I see no messages that indicate an error.
Other modules can be loaded from the Gallery on the manually created site; although these are also loaded by the DynamicModuleLoader.
So does anyone have an idea why this module will load in the case of a site created by WPI and a site created by compiling the source and not load on a site created from the Orchard.Web.1.9.1.zip file.
Failing that, can anyone tell me how to get some more detailed logging out of the module loader?
When I experience things such as this, it often has to do with caching. I'd get the site running without your custom module, add your module, and restart the site.
I installed Joomla on a website on Windows Azure. After trying to update the Joomla version or uploading a new template I get the following error
JFolder::create: Could not create directory
Warning: Failed to move file!
For me it's clear that the problem is regarding permissions, so the question is, how can it be solved?
Since the Azure architecture (basically the replication) makes you difficult to just change the permissions of the folders, and it is not possible to modify the folder permissions on a Windows server using FTP, I feel like I'm on a dead end.
It should definitely be possible. When installing a component JFolder::create is called several times.
I think that you are passing a wrong path or something to the actual call. Have you tried a simple test using the native mkdir()?