I hate being a dope, but clearly I need to alter my expectations of myself!
One machine in our office, our test machine: Can't publish on Port 80
In the past (last week), works no problemo.
Works fine on other machines.
Testing today... no go.
Works fine on other ports (81, 8080, 8081, etc)
Windows Server 2012 r2
4D - Windows 16r6
NOTHING (Really!) else running on port 80. (That I can see)
Checked
Resource Monitor - Nada
NetStat - Nope!
No Skype Running
IIS not running
Apache not running
Firewall completely turned off
Looked for any suspicious services or tasks
Restarted machine
Chanted Krishna, threw I Ching, smudged room with burning sage, etc.
Get error message: "Failed to Create a listening socket"
Database cannot be published.
"Only one usage of each socket address is normally permitted"
So.... this tells me that something "else" is hogging port 80
What other sneaky service/app could this possible be?
How else to find out what is using Port 80?
I'm starting the web server using "WEB START SERVER"
Tried the structure checkbox: "Launch Web Server at Startup"
Same results
Also, Same results for Single-User System (Local Mode)
OK... I give up, I'm on Candid Camera, right?
Randy Engle, Director
XC2 Software LLC – XC2LIVE!
**********************************************************************
4D Internet Users Group (4D iNUG)
Archive: http://lists.4d.com/archives.html
Options: https://lists.4d.com/mailman/options/4d_tech
Unsub: mailto:4d_tech-unsubscr...@lists.4d.com
**********************************************************************
