Troubleshooting
Problem
Downloading clients from the IBM Rational Host On-Demand server installed on Microsoft Windows 2008 or 2012 with Microsoft IIS 7.0 or 7.5 results in an error indicating that files are not found. The client applet can appear to hang and the status bar indicates 'Loading Java Applet...'.
Symptom
When downloading clients from the server, you might see a "Java FileNotFoundException" message in the Java console or "Unable to display page, 404 error" in the browser window or unable to launch a Webstart client.
Cause
The mime types are not automatically defined in IIS Web Server during install of Host On-Demand.
Resolving The Problem
When you install Host On-Demand on Windows 2008 or 2012 with Microsoft IIS 7.0 or 7.5, additional mime types that Host On-Demand requires are not configured in Microsoft IIS and need to be manually added. The Host On-Demand installation continues and it appears that the Microsoft IIS configuration has been updated.
The Microsoft IIS Administrator must configure specific mime types in the Web Server. The default settings have minimal or no mime types.
You need to add the following mime types (file extensions) for Host On-Demand:
.style - application/octet-stream
.props - application/octet-stream
.properties - application/octet-stream
.cf - application/octet-stream
.obj - application/octet-stream
.df - application/octet-stream
.ndx - application/octet-stream
.hodpdt - application/octet-stream
.mac - application/octet-stream
.pfb - application/octet-stream
.ttf - application/octet-stream
.inx - application/octet-stream
.gtt - application/octet-stream
.p12 - application/octet-stream
.jks - application/octet-stream
.fnt - application/octet-stream
.jnlp - application/octet-stream
After adding the mime types, you must restart the Web server. For more information about Microsoft IIS 7.0 mimetypes, refer to the Microsoft support Web site. For instructions on adding the mime types, refer to the Microsoft IIS 7.0 or 7.5 documentation.
If you continue to have problems, review the Web server log to identify which file types lack MIME entries. For example, the log entry might appear as follows:
- GET /hod/ibmhod_en.props - 80 - x.xx.xx.xx Mozilla/4.0+(Windows+XP+5.1) 404 3 50
As an alternative, it is possible to add the *.* wildcard indicator to include all mime types; however, you may want to consider the security risks this can pose to your network before allowing all mime types to be processed by your Web server.
Was this topic helpful?
Document Information
Modified date:
02 August 2018
UID
swg21423830