When you attempt to apply any hot fixes via the ColdFusion 10 Administrator you continuously get:
Error occurred while installing the update:
Failed Signature verification
You may have even validated the files and manually and placed them in the hf-updates directory at which point the CF10 admin page still shows the "Install" option, but again you receive the same error.
This error means you've forgotten to apply the ColdFusion 10 Mandatory Update which updates the certificate used to validate install packages.
From Adobe's website:
All ColdFusion updates are now signed with the new code signing
certificate because of a code signing certificate revocation. This
mandatory Update ensures that your current installation of ColdFusion
10 is updated with the new code signing certificate. This update is
also required for proper functioning of the auto update functionality
in ColdFusion 10. Adobe strongly recommends that you apply this
update.
Once the update has been installed (you can find the JAR install instructions here) the service will be restarted and you will be able to apply subsequent updates via the ColdFusion administrator.
Edit:
Run the command prompt as Administrator:
Navigate to your jar file, and run the following command to run jar file:
D:\>java -jar cf10_mdt_updt.jar
#UncleSol,
I also encountered the issue after having installed the mandatory update (cf10_mdt_updt.jar). After successfully applying the mandatory update, CF wanted to apply update 12 as the first update, which is where I encountered this issue, so I downloaded and manually installed Update 11 from this page:
https://helpx.adobe.com/coldfusion/kb/coldfusion-10-updates.html (installed in exactly the same manner as NotJustClarkKent's instructions)
After manually installing update 11, I was able to use the CF Updater to install the rest of my updates.
Hope that helps.
Related
When trying to create a custom ElasticBeanstalk platform that uses Python3.10.5, I keep running across this error:
[2022-07-01T05:50:06.466Z] INFO [5419] - [CMD-PackerBuild/PackerBuild/PackerBuildHook/build.rb] : Activity execution failed, because: Version 2 of the Ruby SDK will enter maintenance mode as of November 20, 2020. To continue receiving service updates and new features, please upgrade to Version 3. More information can be found here: https://aws.amazon.com/blogs/developer/deprecation-schedule-for-aws-sdk-for-ruby-v2/
'packer build' failed, the build log has been saved to '/var/log/packer-builder/Python3.10_Ubuntu:1.0.8-builder.log' (ElasticBeanstalk::ExternalInvocationError)
caused by: Version 2 of the Ruby SDK will enter maintenance mode as of November 20, 2020. To continue receiving service updates and new features, please upgrade to Version 3. More information can be found here: https://aws.amazon.com/blogs/developer/deprecation-schedule-for-aws-sdk-for-ruby-v2/
'packer build' failed, the build log has been saved to '/var/log/packer-builder/Python3.10_Ubuntu:1.0.8-builder.log' (Executor::NonZeroExitStatus)
I'm not sure how to get around it, as none of my actual code for this uses ruby at all.
I have tried to SSH into the packer build box and run gem install aws-sdk to get the latest version, however it eventually ends up hanging and never completes.
I'm really unsure of what to do at this point. Any advice?
Update: Was finally able to get a gem install aws-sdk -V to finish after changing the version to ruby2.4, however the problem above still persists.
We are trying to change how we manage our QA Enviroments.
Till now we have installed Coldfusion using the Adobe Installer that install a modified Tomcat.
We want to manage the QA server using CommandBox Tool that installs Coldfusion in JEE install mode using war file, but situation will be similar with any of the supported JEE Application Server. (EAP, Wildfly, Tomcat).
We have little experience in using Coldfusion in the JEE install mode then several questions arise regarding the JVM Settings.
Below the JVM Setting we got after install CF using the Adobe Standard installer, accessing the Coldfusion (CF) Administrator (here for a fresh installation of a CF2018):
--add-modules=java.xml.ws
--add-opens=java.base/java.lang=ALL-UNNAMED
--add-opens=java.base/java.nio=ALL-UNNAMED
--add-opens=java.base/sun.util.cldr=ALL-UNNAMED
--add-opens=java.base/sun.util.locale.provider=ALL-UNNAMED
--add-opens=java.rmi/sun.rmi.transport=ALL-UNNAMED
-Dcoldfusion.classPath={application.home}/lib/updates,{application.home}/lib,{application.home}/lib/axis2,{application.home}/gateway/lib/,{application.home}/wwwroot/WEB-INF/cfform/jars,{application.home}/wwwroot/WEB-INF/flex/jars,{application.home}/lib/oosdk/lib,{application.home}/lib/oosdk/classes
-Dcoldfusion.home={application.home}
-Dcoldfusion.jsafe.defaultalgo=FIPS186Random
-Dcoldfusion.libPath={application.home}/lib
-Dcoldfusion.rootDir={application.home}
-Dcom.sun.xml.bind.v2.bytecode.ClassTailor.noOptimize=true
-Djava.awt.headless=true
-Djava.locale.providers=COMPAT,SPI
-Djava.security.auth.policy={application.home}/lib/neo_jaas.policy
-Djava.security.policy={application.home}/lib/coldfusion.policy
-Djava.util.logging.config.file={application.home}/lib/logging.properties
-Djdk.attach.allowAttachSelf=true
-Dorg.apache.coyote.USE_CUSTOM_STATUS_MSG_IN_HEADER=true
-Dorg.eclipse.jetty.util.log.class=org.eclipse.jetty.util.log.JavaUtilLog
-Dsun.font.layoutengine=icu
-XX:+UseParallelGC
-XX:MaxMetaspaceSize=192m
-Xbatch
-Xdebug
-Xms256m
-Xmx1024m
-Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=6006
-server
Q1. the Coldfusion war have inside it the JVM settings (we have written above) and will apply it during deploy?
Q2. if answer to is no!, what are the settings that are applicable according the JEE Application Server used (i.e. some settings are ok for Tomcat but meaniless for wildfly).
We were able to find specific documentation from Adobe for Coldfusion 2018 (https://helpx.adobe.com/it/coldfusion/installing/coldfusion-2018-install-jee-configuration.html).
The number of settings is incredible low comparing with the standard one!:
-Djava.locale.providers=COMPAT,SPI
-Dcoldfusion.disablejsafe=true
-Djdk.attach.allowAttachSelf=true
-Djdk.serialFilter= !org.mozilla.**;!com.sun.syndication.**
We were not able to find similar documentationfor Coldfusion 2021 (latest release).
Till now trying to get help from Adobe has been produce not effective results.
Thanks in advance
Adobe isn't going to help you support an installation via CommandBox, you need to talk to Ortus Solutions about that. Every JVM setting available in CF Admin for Standard is not displayed in the UI for CF Enterprise. You're looking for the CF install folder for the instance you have (non-CB version), find a file called jvm.config.
https://www.cfguide.io/coldfusion-administrator/server-settings-java-jvm/
In ColdBox, you can set everything via the command line or use a server.json file to do that same configuration.
https://commandbox.ortusbooks.com/embedded-server/configuring-your-server/jvm-args
Here's an example from a CB install I have on a Mac where I'm running an older version of CF that requires an older JDK, but I've also set the heapSize.
{
"jvm": {
"javaHome": "/Library/Java/JavaVirtualMachines/jdk1.7.0_15.jdk/Contents/Home",
"heapSize": 1024
}
}
What I would suggest is
export your existing CF Admin settings to a .car file
log in to your ColdBox server's CF Admin
import the .car file
adjust all the settings (DSN, etc) for your QA server
go to the command line and install the CFConfig plugin
export all the CF Admin settings to a JSON file (instructions in their docs)
save that to a private repo or your secrets / passwords vault.
Join the BoxTeam Slack where you can find the CommandBox community and ask more questions.
We have a requirement to install Sitecore packages programmatically from a custom admin page. The package installation is working but once the package is installed I wanted to restart the Sitecore server from code.
Sitecore.Install.Installer installer = new Sitecore.Install.Installer();
I tried with installer.ExecutePostStep but not sure what action I need to provide to this function.
If anyone has done it before Please help .
Basically I wanted to execute the functionality from code what the two below check boxes are doing when we do manual installation.
The easiest thing will be to restart the Sitecore's application pool by a Restart-Application PowerShell command.
Find more details here.
I'm trying to download the facebook/php-sdk-v4 repository into my project, running the "php composer.phar update" command.
I recently added this to the require section of my composer.json file:
"facebook/php-sdk-v4": "4.0.*",
Upon running the update command, I am given the following error:
---> Your requirements could not be resolved to an installable set of packages.
Problem 1
- The requested package facebook/php-sdk-v4 1.0.0 could not be found.
It seems that I have set it up exactly according to the Facebook Graph API instructions as listed on this page:
https://developers.facebook.com/docs/php/gettingstarted/4.0.0
But... It's still unable to find the repository.
Does anybody know the name of the Facebook SDK 4.0 repository or see any reason why this process I am following isn't working?
Thanks for listening!
I install sitecore 6.4 but after login i take this error
The directory name c:\ınetpub\wwwroot\mysite\website\sitecore\shell\override is invalid.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
I uninstall sitecore and install again but result same. Someone can help me pls.
By default this folder is not created when you create a fresh install of Sitecore. Have had this many times, and essentially you must manually create the folder, and also ensure the app pool identity has write permissions to this folder. If you have your Visual Studio solution open, also close and reopen as the change will not be picked up if you are running webdev.
I ran into this problem as well. My problem was i had my project committed on Git and I was trying to pull files from GIT to my local to setup the project.
The problem with GIT is that it doesnt commit empty folders so \website\sitecore\shell\override was not committed to the repo, and when i pulled, the folder didnt existed on my local as well.
Creating the folder manually resolved the issue.
As mentioned by #pranav-shah, git doesn't support adding empty folders so if you are using git and you are doing clean builds it is likely you are running into this problem.
To get around it you can just create an empty file in the override folder. I recommend following the suggestion in this answer and call it .keep
Whenever I run into this, it's the app pool identity missing write permissions to the folder. Often applies to following folders too, under the sitecore directory:
* shell\controls\debug
* shell\applications\debug
(I think there's one more but too tired to remember right now).
If you run the installer it normally takes care of these issues. Also be sure to read the manual installation steps in the Sitecore documentation, available on the Sitecore Developer Network.