ePortal upgraded on IIS 7, now can't access through port 80

[OverWorked]

Hello,

 

I've already logged this with Serco, but I'll see if I get an answer here first.

 

I run ePortal on IIS 7, and following an updgrade to v09.2, I can't access it through port 80 any more(it was on port 80 before the upgrade). It still works through port 8080.

 

What's gone wrong? Any ideas? I can't find the answer on the Serco KB.

 

Thanks.

[mbyrew]

I have the answer to this. Will need to look it out for you. DM me your details and I'll fwd to you.

[michael2k6]

Are you on 64bit OS? If so you will need the 64Bit ISAPI.

 

Mic @ Serco

[john]

have you checked the port setting in the eportal conf folder to ensure its set with port 80 as the port you want? I often have to remember to reset it as it does go astray at times.

[robk]

How many times has the server been rebooted after upgrade? Ours took two reboots before IIS would work correctly.

[Guest L3o]

Your Tomcat looks like it is working fine on Port 8080 (set in the server.xml) IIS would normally be setup to use port 80 by default. IIS needs to then communicate with Tomcat on other ports, if these are in use IIS tries loading index.jsp but can't (the redirect is failing because of a possible port issue).

 

Try commenting out the following in the server.xml located in \facility\ePortal\conf

 

protocol="org.apache.coyote.http11.Http11NioProtocol"

SSLEnabled="true" scheme="https" secure="true"

keystoreFile="/webapps/API/certs/ePortalKeyStore"

keystorePass="79WSax88" clientAuth="false" sslProtocol="TLS" />

 

place a at the end.

 

Restart ePortal services and run an IIS reset. If this fails you will need to run a port scan possibly to check the ports. This sometimes fixes the problem. Make sure you backup the file before editing it

 

Or make sure you have the 64bit filters, like Mic suggested, if you are using a 64bit server.

 

Leo

[OverWorked]

Thanks, everyone.

 

Serco fixed it the next morning in a 90-minute remote desktop session.

 

The solution was quite complex, I really can't remember it all, and involved some of what people have suggested here. It looks like (I could be wrong) that a patch has added another place where the ISAPI fiter has to be enabled.

 

Anyway, Serco know about it now so if anyone else has the same problem, please ask them!