You are viewing limited content. For full access, please sign in.

Question

Question

Unable to use Port 80 for forms and App Server after upgrading to 10.2

asked on February 16, 2017

Greetings,

We have a Windows Server 2008 R2 server and just recently upgraded from 9.1 to 10.2. Unfortunately our vendor who did the upgrade, installed Forms 10.1 instead of upgrading to 10.2 like all other components installed (Server, Client etc). He also did not upgrade the App server, still on 9.1.

I tested that both Forms 10.1 and the App server where working fine and they were. I could go into configuration etc.

I then upgraded both components to 10.2. After which I am unable to start the default web site under port 80, If I do it says Port 80 is in use. I used a netstat -abno command to trace it to PID 4 (the system service). Changing http to another port like 8080 results in everything working fine.

My question is what is using Port 80? As I mentioned everything worked fine before the 10.2 install for forms and App server.

 

Thx.

0 0

Replies

replied on February 17, 2017 Show version history

If you run netstat -ab only, what does it show?

Are you running Apache server perchance?  If so, do you need it?  If you don't need it, uninstall it then try again.

0 0
replied on February 17, 2017

There is only IIS installed and no other applications on this server other than laserfiche.

Netstat -ab displays 'cannot obtain ownership information' for port 80. That is why I used the 'no' options to determine the PID in use.

I did a compare to my Empower virtual machine running 10.2 and noticed bindings only have http & https for IIS. I have attached my bindings and there are bindings for 'net.tcp', 'net.pipe','net.msmq' & 'msmq.formatname'. Is this normal? Can they be safely removed?

bindings.JPG
bindings.JPG (20.99 KB)
0 0
replied on February 20, 2017

Those are the bindings for Windows Message Queuing. They're not using port 80.

What exactly do you mean by "the system service"? I'm not seeing a service by that name. What's the executable running for PID 4?

0 0
replied on February 20, 2017

Service is http.sys or considered 'system'.

Worked more with our vendor and found a workaround for the problem. Changed bindings as follows:

where crd-rm is our server name. Removed the original blank host name for port 80 and added to specific bindings for host 'crd-rm' and 'localhost' for port 80. This works and resolves properly. Still not sure why the blank host for port 80 would not work but everything seems to be working fine now.

0 0
replied on March 21, 2017

I was just notified by one of our customers that they had the same issue. They resolved it by changing the startup of  the Laserfiche services to Automatic (Delayed Start).

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.