Apache Tomcat 9.0.40 server throws 404 error when ran on eclipse. otherwise it works fine - eclipse

I am trying to learn jsp-apache web server - oracle db interconnectivity.
I installed Apache and gave it 10407 port and when I run it in windows command line 'startup'
server starts and I can connect to localhost:10407 website successfully.
But, when I try to do the same thing in Eclipse, (only one apache is installed in my computer atm)
Console shows same messages and it connects to server. But when I try to access localhost:10407,
it throws this error.
HTTP Status 404 – Not Found
Type Status Report
Message The requested resource [/] is not available
Description The origin server did not find a current representation for the target resource or is not willing to disclose that one exists.
How can I fix this?

It was a mistake. I put index.html file in WEB-INF folder.

Related

Web Deploy not working. Timeout on client. Schannel 1203 on server

I'm trying to deploy an application via web deploy to a windows 2012 r2 server.
First tried installing iis, web deploy using the msi. After getting an unreachable error I saw somewhere that I needed wmsvc to be installed and installed it via powershell command Install-WindowsFeature Web-Mgmt-Service.
I stopped getting the unreachable error and started getting this error ->
Error: Could not complete the request to remote agent URL 'http://xx.x.xx.xx:8172/MSDEPLOYAGENTSERVICE'.
Error: The operation has timed out
On the server's event viewer under system I get the following error ->
A fatal alert was generated and sent to the remote endpoint. This may result in termination of the connection. The TLS protocol defined fatal error code is 10. The Windows SChannel error state is 1203.
Any idea of what could be going on? Did I miss something on the installation?
After this I also tried installing everything but without iis and I get the same error.
So, this is really not a PoSH issue.
Maybe you should consider movin gthis question to another forum.
Anyway, you have either real server config issues (this can sometimes mean wipe and rebuild - very ugly option - but if it's a virtual machine and you have a snapshot, just roll back), or an app causing this.
Typically for Schannel type of error, it has to do with application or service in machine not able to complete any SSL connection sort of connection.
The error state parameter of 1203 means client error connecting to server, ie invalid ClientHello from the client
See if you can collect more data by...
https://support.microsoft.com/en-us/help/260729/how-to-enable-schannel-event-logging-in-iis
I realized this is an old question, but in case somebody ran into the same issue, here are my solution.
I had to follow this guidelines : https://learn.microsoft.com/en-us/aspnet/web-forms/overview/deployment/configuring-server-environments-for-web-deployment/configuring-a-web-server-for-web-deploy-publishing-web-deploy-handler
Copy the resulting publishsetting file. In the Publish/Profile page import it.
In the Publish/Connection page, change the server to the server address with the 8172 port. Add the password. Change the Destination URL to the site to go to after the publish is completed.
Then after Validate connection was completed, go ahead and publish it!

AEM login screen is not apprearing in a linux machine AEM6.3

I have set up AEM 6.3 on remote Linux machine. But when I try to access the AEM from browser, it says "Connection has timed out".
I am not getting any error in the error.log file. Also, in stdout.log file, it says "Startup completed".
Also, I checked that port(4502) is not blocked on the server.
When I put command "curl http://localhost:4502/" on the server, I am not getting any error, which makes me assume that the connection is established.
Do I need to do any other configuration or something in order to access it from the browser? I am using http://ip:4502/ in the browser..
Almost certainly a firewall issue, check and check again :)
Look in the AEM Access log (same folder as the other logs you looked in) can you see any requests coming in from your browser? There is no other config required on AEM to access other than starting it up, assuming there is nothing network/firewall related blocking then you should be able to access it.

Zumero error 1992: http_404

I've successfully configured ZSS Server on my internal system (Win Server 2008R2 + IIS 7.5), and everything works fine.
Now I'm trying to install the same system on a customer machine; I've done this through the installer (latest version), he has applied the necessary security permissions, the home page of the site is visible, but syncing the db give the 1992 error.
Taking a look at IIS logs, I see that every call with GET /pull result in a 404 error code, subcode 0; there are several consecutive statements like this, all terminating wi9th 404.0 error code.
The web.config is the same as my system. What else can I check ?
You say you can reach the home page of the site - do you mean the "main" IIS home page, or the root of the ZSS site? That is, assuming Zumero is running on port 8080, what do you see when you point a browser at http://your.customer.site:8080?
I my case it was caused by the Application pool being configured for 32 bit (which it should not be). Version 1.4 has an improved installer, that should prevent this from happening

How do I get more details on my request error on IIS7

I have deployed a REST service on an external server (IIS7). When I start the service from VS on the Dev server it works fine. But on the server i get:
Request Error, The server encountered an error processing the request. Please see the service help page for constructing valid requests to the service.
How do I get more details on this error? I have looked in the log files directory that is configured under Logging feature for this web site in IIS Manager, but there are no files at all for this site it seems.
You should look in the Windows Event Log using the Event Viewer application (eventvwr.exe). Output to the IIS log files may be buffered so their contents may be updated after a restart, or when IIS is set to do it. Restarting IIS is a surefire way to force this.
Here is a blog post on how to do this.
I'm aware of 3 ways to get nicer errors:
Set UseVerboseErrors in InitializeService method. However, this won't give you anything if your error occurs before InitializeService is called (which happens).
Set IncludeExceptionDetailInFaults to true using an attribute before your service class.
Set IncludeExceptionDetailInFaults to true using web.config.

running a .net web service on iis6 deployed on windows 2003 server sp2

To whom it may respond to,
We have deployed a web service to Windows 2003 Server SP2 , .net framework 3.5 .
"The service is not running , we are getting the error :
The website declined to show this webpage
HTTP 403
Most likely causes:
•This website requires you to log in.
What you can try:
Go back to the previous page.
More information
This error (HTTP 403 Forbidden) means that Internet Explorer was able to connect to the website, but it does not have permission to view the webpage.
For more information about HTTP errors, see Help."
We have played around with the permissions but the situation didn't change a bit.
We would be very glad ideas on it,
Thank you for your concern,
Best Regards,
Kayhan YUKSEL
Make sure you have aspnet_isapi.dll as your wildcard handler in the Virtual Directory setup. Properties --> Virtual Directory --> Configuration --> Insert... --> aspnet_isapi.dll, make sure you uncheck Verify that file exists.