IBM Support

Why am I receiving a 404 page error when I go to Web Reports?

Technote (troubleshooting)


Problem(Abstract)

If another service is running on the same port as Web Reports, it will block requests to Web Reports.

Diagnosing the problem

Web Reports Logging can be used to see the problem as the Web Reports service attempts to startup. The following set of error messages will appear in the logging output:

Can't listen on address [::]: Socket Error: Windows Error 0000271d: An attempt was made to access a socket in a way forbidden by its access permissions.
Unable to start http server: socket may already be in use on port 80, next retry in 30 seconds

Resolving the problem

During Web Reports installation, the installation wizard prompts for the port number (the default port is 80) for the Web Reports Server Service.

If another service is running on this port (for example IIS), it will block the requests to Web Reports because the port is being used by that other software service. To determine if the port is in use by another program and to determine what program that is:

1. Open up Windows Task Manager (Start > Run > taskmgr)
2. Go to the Processes tab.
3. On the main menu select View > Select Columns > check PID (Process Identifier) > OK

Stopping or uninstalling the blocking software service (such as IIS) may or may not free up the port and may require changing the port that Web Reports uses to a port that is not currently in use. This issue has been observed on Windows 2008 R2 64 bit machines when IIS is installed or has been installed and then removed. IIS will listen on and use port 80 by default. This issue may occur on other OS versions as well. The default port 80 tends to stay in use even though IIS has been uninstalled.

To check to see if the default port 80 is in use, or to check to see if the port you are trying to run Web Reports on is in use (either by IIS or another service) first stop the Web Reports Server Service and then run the following at the command line:

netstat -ao

Proto      Local Address    Foreign Address   State     PID

TCP        0.0.0.0:80         rhost:0        LISTENING  156
TCP        0.0.0.0:445        rhost:0        LISTENING    4
TCP        0.0.0.0:49152      rhost:0        LISTENING  664

If you see the port anywhere in the list of the output, then it is in use. You will also see what process (from the PID) is listening on this port. Cross referencing the PID of the listening process from the netstat output with the current running processes in Windows Task Manager, you will be able to identify what program is using port 80. In this example port 80 was in use by process 156. To change the port Web Reports lives on, edit the following registry key.

On 32 bit OS servers:
HKEY_LOCAL_MACHINE\SOFTWARE\BigFix\EnterpriseClient\Settings\Client\_WebReports_HTTPServer_PortNumber

On 64 bit OS servers:
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\BigFix\EnterpriseClient\Settings\Client\_WebReports_HTTPServer_PortNumber

Change the value of this key from its current port to a port that is free and restart the Web Reports Server Service.

The Tivoli Endpoint Manager team recommends running Web Reports on port 52312.

Access Web Reports by opening a browser and going to the following URL:
http://{NAMEOFYOURSERVER}:52312/webreports

Finally, update the Web Reports URL for accessing Web Reports from the Console menu:

1. Login to Web Reports (note the URL you are using to login with), go to Administration > Database Settings.
2. Edit your database connection.
3. Put the URL in the Web Reports URL text box and click Submit.

Validate by launching web reports from your console, from Tools > Launch Web Reports.

URL entries for Web Reports are stored in AGGREGATEDBY table in the BFEnterprise database. If there are old URL records in the database that are no longer needed they can be deleted.

Historical Number

1716

Document information

More support for: IBM BigFix family

Software version: Version Independent

Operating system(s): Platform Independent

Reference #: 1506234

Modified date: 09 February 2016


Translate this page: