HTTP Status 404 - /webacs/welcomeAction.do

[chicagotech]

We are running WCS V4 on Windows 2003. We can't access WCS website with this error: HTTP Status 404 - /webacs/welcomeAction.do. How do you troubleshoot it?

[Stephen Rodriguez]

Hit the WCS Status, and make sure that everything is started.

HTH,
Steve

-----------------------------------------
Please remember to rate useful posts, and mark questions as answered

[chicagotech]

Thank you for the tip. After I did more research, I found this error:

Event Type: Error Event Source: Service Control Manager Event Category: None Event ID: 7034 Date: 5/8/2012 Time: 5:00:41 PM User: N/A Computer: RUNIT Description: The Wireless Network Management Application service terminated unexpectedly.  It has done this 2 time(s). For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

I can't start it manually. What could be the problem.

[chicagotech]

Can someone help?

[maldehne]

have the logs in <WCS Installation Dir>\webnms\logs zipped and upload them to see what do you have inside.

[maldehne]

One more thing the HTTP status 404 status code means that the client managed to contact the web server but for some reason the web server is not able to find what is requested.

In the meantime what is the browser version you are using?

[chicagotech]

WCS shows

Database server is stopped

Apache server is stopped

WCS is stopped.

I have uploaded the logs.

[maldehne · Accepted solution]

In the logs I can see the following clearly

5/12/12 21:28:44.861 ERROR[general] [10] Port 162 is in use. DatagramSocket binding gave exception java.net.BindException: Address already in use: Cannot bind

5/12/12 21:28:44.861 ERROR[general] [10] Port 162 needed by the server is being used by some other application.

5/12/12 21:28:44.861 ERROR[general] [10] Please free the port and restart the Server.

You have to find the application on your server that is using the aforementiond UDP port and stop (disable that application)

After that try to stop WCS and start it again and let me know how it goes with you.

Mohammad

--------------------------------------------------------------

Please Don't forget to rate correct answers

[Amjad Abdullah · Accepted solution]

This usually happens when there are reserved ports that are needed by WCS but when WCS tries to use the ports it finds it reserved by some other application. I saw this earlier with FTP port when you have an FTP server installed in same WCS machine. if WCS machine was restarted and FTP server started before WCS service then it will reserve the port and when WCS tries to take the port it will find it already reserved so it halts.

maldehne above helped finding exact reserved port which is port 162 that is used for SNMP. Try to check and stop any service in same server that utilizes SNMP and then try to start WCS again.

The below quote mentions all ports that need to be available for WCS to work correctly.  You need to directly go to the last point in the quote which talks about port 162, there is a linke to WCS guide metnioning all ports needed.

Q. The WCS fails to start up. What can be the issue?
A. Assume that the installation went correctly.
If the WCS were installed as a service, make sure that you rebooted the machine.
Check if the scripts are manually run from the bin directory. You must not manually run scripts from the bin directory. You must use the links from the Windows WCS programs menu or the scripts from Linux <Install Dir> (that is, /usr/local/bin/WCS22/StartWCSServer).
When there is a conflicting port in use, WCS fails to get started with just the error message "Failed to start WCS Server." The WCS requires these ports to be available in the machine:
   *Checking for Port 1299 availability... OK
       *Checking for Port 80 availability... OK
       *Checking for Port 443 availability... OK
       *Checking for Port 8009 availability... OK
       *Checking for Port 8456 availability... OK
       *Checking for Port 8457 availability... OK
       *Checking for Port 8005 availability... OK
       *Checking for UDP Port 69 availability... OK
       *Checking for Port 21 availability... OK


Make sure that you do not run other applications on those ports, such as web server (80), TFTP Server (69), or FTP server (21). On a WCS installed on linux, go to WCS/webnms/logs/wcs-0-0.log and look for the conflicting ports. On Windows based WCS, you can run netstat -a from a DOS window to see the listening ports that are used. If this is the case, shut them down and try to restart WCS.
Note: In Linux, enter netstat -nlp. In the Task Manager, you can view the respective PID and stop the process using the port that WCS requires.

WCS does not start if the database is corrupt. If you reinitialize or restore the database, it fixes the issue. Navigate to the WCS installation directory and issue the dbadmin.bat reinitdb command from the command prompt to reinitialize the database.
Collect the log files from the <WCS Installation Dir>\webnms\logs. These log files can be used to identify the root cause of the issue.

Check if the Windows SNMP trap service is active on the server. Disable the service because it uses Port 162 that is required by WCS. For more information on list of ports used by WCS, refer to the Prerequisitessection of Cisco Wireless Control System Configuration Guide, Release 5.2.

Reference: http://tiny.cc/1ucaew

I hope this is useful.

Amjad

[chicagotech]

It works. thank you very much!

[maldehne]

Fantastic