Unable to Create site getting error notification
I followed the instructions given here : https://docs.craftercms.org/en/3.1/getting-started/quick-start-guide.html
Steps followed:
I cloned Crafter CMS Docker Compose repo from GitHub and then
I started the container from authoring directory using the docker-compose up command
And then I tried to Create a site in Crafter Studio but I got error notification which says "Unable to Create site: contact system administrator"
I am using Docker Desktop Community in my windows 10 64 bit
Docker - Version 2.0.0.3 (31259)
Crafter CMS - Version 3.1.0
OS - Windows 10 64 bit
Browser: Google Chrome
I expected site creation but I got error notification which says "Unable to Create site: contact system administrator"
Error Nofication :
The problem is RAM. You need to give it 8GB+ of RAM to be able to start all the services (including Elasticsearch).
More on this issue here: https://groups.google.com/forum/#!topic/craftercms/Ei7gJGTEE4I
Also more on the requirements for the authoring env: https://docs.craftercms.org/en/3.1/system-administrators/activities/authoring/authoring-env-performance-tuning.html
Related
I'm trying to install an Umbraco version 8.4.0 on Windows 2016 Standard Server.
The dev machine is Windows 10 Pro on which the installation works fine.
But when I deploy to the Windows 2016 Standard Server the pages loaded do not format well - the footer, header and other compositions setup in the back-end do render.
There are no 500 server errors or Javascript errors in console. I'm clueless about whats going wrong?
Has anyone installed Umbraco v8 on windows 2016 server, are there any special considerations for installing it?
Please could someone help me, I'm really stuck on it and not sure how to go and resolve it.
We gave "Network Service" permissions to modify the website folders. That fixed it, not sure though why because Umbraco was already running without the "Network services" in the permissions. It was only the new release of the website that got affected, the previous release had no issues without Network Services having these permissions.
If anyone get stuck with something like this should check the permissions for the website folders.
Error: Failed to deploy COMPUTER_NAME :The Bootstrap service is not found on remote machine
Hello Stack overflow users. Google yields no results...
I configured a Wonderware Intouch for System Platform Runtime Client remote computer according to best practices found in the README files and other documentation.
On the GR in the ArchestrA IDE I created a platform then a view-engine and then an instance of the Intouch app underneath that.
I successfully deployed the application to the remote computer and everything was working as expected.
Afterwards I had to change the remote computer name as per our policy because the computer would be used at another site.
First I undeployed everything including the platform from the remote runtime computer. Then I changed the remote runtime computer name. Then I renamed all the objects in the IDE on the GR accordingly and changed the computer host name in the platform object instance accordingly.
I then tried to deploy the platform again, no success, I only receive an error message:
"Error: Failed to deploy COMPUTER_NAME :The Bootstrap service is not found on remote machine"
I have tried:
- Restarting the computer.
- Changing the IP Address.
- Google and AVEVA Knowledge base.
- Platform removal tool (which cannot be accessed since the platform does not display in the SMC manager)
The version of System Platform is 2014 R2 SP1.
When I look in the SMC log file, the Bootstrap service is starting on the remote runtime client.
I am not to keen to format the computer and start over so I would like to know if there may be some files that I need to delete or something else I could do to fix this problem.
EDIT:
I have also as mentioned in the comments and additionally tried:
- Uninstall Wonderware completely followed by a new fresh Install.
I had this problem recently. The problem seems to be that when creating a platform in the IDE it associates an ID for it and if you change the name of the machine and change the name of the platform it can try to search for the old platform through the id. To solve this, create a new platform and try to deploy it, System Platform can associate an old ID with the new platform, then create platforms until you have a unique id not yet used and deploy it. The platform id can be verified in the SMC. When deploying, leave the SMC open next to the IDE and note the ID of the platform being deployed.
I have Mirth Connect Version 2.2.3.6825 installed on RHL I want to access my Mirth my Local Machine which have Java 1.8(Java 1.7 it Work fine), I am not able to launch the Administrator tool of Mirth. When I clicked on the administrator button, It opened the window saying starting application after giving User name and Password it give error 'There was an error connecting to the server at the specified address. Please verify that the server is up and running'
http://www.mirthcorp.com/community/wiki/display/mirth/System+Requirements
Java 8 should work with version 2.2.3, but you must be using the Oracle JRE. OpenJDK only recently became supported with version 3.7.
You may also want to try using the new Administrator Launcher available on the mirth downloads page. It comes bundled with a Java 8 JVM so that you don't need to install one separately. It works with all versions of mirth from 2.x and up. See announcement here: https://www.mirthcorp.com/community/forums/showthread.php?t=218662
I am trying to publish a non-modified ASP.NET 5 project to my freshly installed Ubuntu 15.04 server, but I receive the following message:
An error occurred during publish. AspnetPublishHandler with name
"Custom" was not found
I bound the server to the correct port with:
docker daemon -H 0.0.0.0:5555 &
The connection validation is successful. Anyone has an idea what could be wrong?
Have you tried after the latest release? For some configuration combination the publish profile was getting generated incorrectly.
I'm trying to get Jenkins (1.510) running on my MacMini with the latest Mountain-Lion Server OSX installed (10.8.3). On the MacMini-server I've two users: admin, ioscoder and as the ioscoder user I logged-in, opened the jenkins-1.510.pkg and after entering the admin password it installed without problems.
However when the Jenkins-home page should come up, using localhost:8080, I get the following error message in Safari:
Safari can't open the page "http://localhost:8080/" because Safari can't connect to the server "localhost".
After logging in as admin and checking the current running services, being DNS, Open Directory, Websites (PHP- and Python web applications disabled), I also get the same error from above when entering the Jenkins address localhost:8080.
When I switched to the admin-user I saw on the welcome screen a Jenkins-user account, which was created by the jenkins-installer package.
What really puzzles me is that on another iMac, running Mountain Lion (NOT the server version of Mountain Lion), I installed Jenkins in the same way and after the installation finished I immediately got a running Safari which resolved the localhost:8080 to the Jenkins home screen.
Anybody ideas or suggestions why Jenkins is not running on a Mountain Lion Server device?
Google-ing for this specific problem didn't give me any clues yet.
After reading the https://wiki.jenkins-ci.org/display/JENKINS/Meet+Jenkins page where an easy installation was mentioned (java -jar jenkins.war) I remembered that java may not have been installed by default on a clean Mountain-Lion Server.
After activating the terminal and typing:
server:~ ioscoder$ java -v
No Java runtime present, requesting install.
it asked me if I wanted to install java. After accepting this and performing an installation of java, I was happy to see the 'Dashboard [Jenkins]' page in Safari for the localhost:8080.