httpd WebServer not starting

[pedrammobedi]

I have renewed my SAS license and have taken all the steps in the email and the document. The deployments is successfully complete.

In the very last step I am asked to start all the servers. 

I used the start order in this page. My machine does not have all the servers mentioned there.

The other servers are started and running but httpd WebServer cannot be started and therefore my WebApp is not up.

This is the error message I am getting:

Has anyone faced the same problem?

[Kalind_Patel]

Hi @pedrammobedi,

Have you checked log for webserver?

what it is showing?

[pedrammobedi]

I have checked Windows Event Viewer and it seems to be a problem with Apache trying to reach its point 80 which is apparently being used by TCP. Are you asking for a specific log file? I see many of them? Do you I think I should change the Apache port from 80 to something else?

[Thu May 12 16:31:54 2016] [error] (OS 10061)No connection could be made because the target machine actively refused it.  : proxy: HTTP: attempt to connect to 192.168.27.158:8080 (kssas.alotteri.se) failed
[Thu May 12 16:31:54 2016] [error] ap_proxy_connect_backend disabling worker for (kssas.alotteri.se)

[Kalind_Patel]

It looks like that other process is running on the same port, thats why Web server can not start, can you free that port and try again? generally 80 port is used by SAS Web Server.

[pedrammobedi]

That's true. But that port I is now taken by TCP. I don't know how it happened.

But instead of that, is it possible that we change 80 to something else?

In Apache's case, I know we can change the port in the file httpd.conf in the folder:

E:\sas\config\Lev1\Web\WebServer\conf\httpd.conf

But I am a bit scared of making such changes.

Is there a secure way of changing the port? Mind that, there is also the WebAppServer in addition to WebServer.

[JuanS_OCS]

Hi,

I don't think the license has anything to do with this issue, but a current change/issue on the configuration files of the httpd, or the fact that the port number might be in use by a different service (as the Windows http service, a really common issue), or an orphaned instance of the same process (check with "netstat -nao|find ":[yourport]", and it only took efect when you restarted the SAS services.

I would suggest you to check in the log files of the httpd server, it usually gives all the information you might require.

[pedrammobedi]

It's TCP on port 80 that is blocking Apache I think. I need to kill that. But I am not sure if that's straightforward or a good idea.

[Kalind_Patel]

What is pid of that port 80 ?

Have you installed Apache on that server ?

If not than SAS' Apache service is running on that.

[pedrammobedi]

PID is 4 which is taken by TCP.

[JuanS_OCS · Accepted solution]

Most probably your WIndows http process is running. You can disable as described on':

http://superuser.com/questions/352017/pid4-using-port-80

[pedrammobedi]

I'm following your link. It's a system process with PID 4.

So I open the device manager and view hidden devices but I find no item called Non-Plug and Play Driver”/HTTP.

Any idea why?

[JuanS_OCS]

Since I am not a full windows administrator, I have no much idea of that, sorry.

But I would try the option to modify the regedit and reboot the computer. There are other options too, just give it a chance and google it 🙂

[pedrammobedi]

We solved the problem finally. Apparently IIS had taken port 80. So we just disabled it and then tried to restart the service and it started working.