LFS.exe using port 80 all to itself instead of sharing with IIS

asked on February 16, 2016

Ran into a unique problem this morning. IIS pages were displaying 404 error anytime port 80 specifically was used.

Checked to make sure no other services were using port 80 other than Laserfiche and IIS as threads through the SYSTEM process via the HTTP Protocol stack.

IIS thinks it can successfully bind to port 80 but LFS is hogging the entire protocol and you get a 404 error when trying to display web pages. When LFS is stopped IIS is able to display web pages on port 80 again. Starting LFS causes the 404 error again.

Was unable to reach out to support because it is an unsupported server version, though a very stable one (9.1.1). What causes LFS to hog the entire protocol?

0 0

SELECTED ANSWER

replied on February 16, 2016

Did you set up LFS for WebDAV?

0 0

View 2 previous replies

replied on February 16, 2016

Yes, someone did. I see the registry entry. Does that require full use of port 80?

0 0

replied on February 16, 2016

Yes.

0 0

replied on February 16, 2016

I think I just found the answer. Looks like it does use max out HTTP.

https://support.laserfiche.com/KB/1013185

0 0

replied on February 16, 2016

Thanks!

0 0

replied on February 16, 2016

Yes, both WebDav and SharePoint like to take over port 80. You could switch Web Access to a different port.

0 0

Question

Question

LFS.exe using port 80 all to itself instead of sharing with IIS

Answer

Replies

Sign in to reply to this post.