Cannot start service created with Apache Daemon on Windows Server - Amazon EC2 - amazon-ec2

I'm facing some trouble while trying to start a windows service that I've created with Apache Daemon on an Amazon EC2 Instance (Windows Server 2012 R2). The error I'm getting is "Windows could not start the service_name on local Computer. For more information, review the System Event Log. If this is a non-Microsoft service, contact the service vendor, and refer to service-specific error code 1."
I checked some other links and most of the similar problems are related to Apache servers issues, but I already have Apache Tomcat working perfectly here and the problem seems to be related to the windows service only.
Does anyone have any idea?

Related

Deploy Outlook Add-in on an AWS EC2 instance

We are trying to host a custom Outlook Add-in on an AWS EC2 instance. We are using a windows server in EC2 to host this. Currently we are using webpack dev server to host it locally and everything is working fine. Now we need to deploy and have this app run as a service in the Windows Server.
We have tried to deploy the build on an IIS server. But we were not able to proceed after logging in to the application. We are getting the error as a Bad request. We also have tried to deploy it on Apache server using XAMP. But the results were the same. It is getting deployed in the webservers, however when we are hitting the backend application it seems to be erroring out.
The error we are getting is Error: redirect_uri_mismatch, when we try to authenticate and redirect to the authenticated home page of the application.
When we deploy the same using webpack-dev-server in the instance, It is working as indented.
We are facing issue to identify the proper reason for this error and unable to deploy the service in EC2.
EDIT
Screenshoot-1
Screenshot-2

Started SQL Server Service on cluster remotely but cluster resource is offline

I have an issue while I start SQL Server service remotely using powershell. The Service is hosted on a cluster as a cluster instance. I start the service with service name, not cluster resource name. So, I am able to bring the service online and connect to the instance, however, the cluster administrator shows the resource is offline until I bring it online. Why is this problem. Why is cluster not able to detect service status.
I don't think starting the SQL Server service will bring the SQL Cluster Resource online. Because you are only attempting to start the SQL Svcs Locally. It is as good as starting the services using service control manager.
You should rather be using Start-ClusterResource -Name <SQLClusterResourceName>

Install Learning Locker on AWS EC2 and got error 404

I installed Learning Locker using Community AMI on AWS and the system said that it successfully build and running and I can connect to my server using ssh, but when I access public DNS of my instance I always get error 404 not found, and my server running nginx, ubuntu 10.4
I do not have a technical support while I use a free AWS account
So, what should I do?

web service address for Jenkins on AWS Windows installed as a Windows Service

I have just installed Jenkins (as a Windows Service) on AWS Windows (Win Server 2012R2) instance.
I'm able to launch it via browser using http://localhost:8080
What url should I use to access this server from other client? I have tried http://:8080 or without the port number but my client (over the net) is failing to connect. The Public DNS of the AWS is also not working.
I set up another Jekins on AWS Ubuntu server with apache tomcat and it's connecting just fine using the Public DNS of the AWS Ubuntu server.

Unable to connect to ec2 windows instance

I have installed mysql 5.5 and tomcat 6 on an amazon ec2 windows micro instance. I am unable to access the pages deployed in tomcat from my local browser.It says The server at ec2-50-19-6-147.compute-1.amazonaws.com is taking too long to respond.
When i pinged using my command prompt, it says request time out.
Can somebody please help me??
Thank you in advance.
You need to check your security settings and make sure that the ports are open for inbound requests.

Resources