IIRF2.1 failed to install

Thanx for following up this... could not use the forum, "message too
long" error didn`t what to remove from the logfile.

Below is the log. This time it says it cannot connect to IIS.

I have IIS7 installed and i am running the program while logged in as
administrator. You can view it at http://trackafrica.com

as for the other question,

Alright all i need for the start is to get the java application in
tomcat to run on any port 80, 9009, 8080 any port. coz i need to test
it. Its a tracking java application i need to test with some GPS
device, for now.

So i don`t mind where the application runs, but i used iis because i
thought i couldn`t run the java tomcat application minus IIS. If i can
run tomcat (and access my application from any PC on internet) minus
IIS then i would would love that better ( do you think i can ?)

I will be glad to receive a response on this and promise a small
donation for your work. You really are helpful.

Yes, you can run Tomcat, directly exposed to the internet. It is not typically done, but it is possible.

Port 80 is the usual, default port for HTTP requests. Both Tomcat and IIS can listen for HTTP requests, but it is not possible to have both IIS and Tomcat listening on the same port. If you would like to run both IIS and Tomcat, then you
have two options:

Configure IIS and Tomcat to listen on different ports. Either Tomcat or IIS can listen on port 80, and the other must listen on a different port. (If you are using a Windows client OS such as Vista, or XP, this is not possible - IIS on
Vista or XP must always listen on port 80. Therefore when using a Windows client OS with IIS and Tomcat, and you want them to listen on different ports, you must configure Tomcat to listen on a distinct port. ) For example, configure IIS
to listen on port 80, and configure Tomcat to listen on port 8080, or 6060, or some other non-standard port. In this case users will address IIS-based applications via urls like
http://server/these/requests/go/to/IIS , and
http://server:8080/these/requests/go/to/Tomcat .

use the JK connector. This part of Tomcat allows IIS to "hand off" some of the incoming requests, discriminated by URL path, to to Tomcat. Using this approach, all incoming requests are initially handled by IIS. Some
subset of requests can be handed off to Tomcat, by IIS, via the JK connector. The choice to hand-off requests is done based on the URL path. In this case, all requests look like this: http://server/these/requests/go/to/IIS
. In this case, Tomcat is still listening on a distinct port, but that port is not exposed publicly, to the internet. It is used only on the internal network.

The reason Tomcat is not typically exposed directly to the internet is for security reasons. IIS on Windows Server has additional security capabilities beyond Tomcat.

I looked at your MSI log file, and the problem is that the installer cannot connect to IIS. I don't know why this would be true, unless you don't have IIS enabled or running. If IIS is disabled in the control panel, then this may occur.

In any case, if your goal is to run Tomcat with IIS, you really do not need IIRF, and so I don't think we need to spend more effort on this problem.