I did a de-installation of Fabric Manager (also removing left over folder).
I re-installed FM 5.0(4d) = latest version
We use the Oracle database
I reloaded rrd files:(these were saved before the uninstall)
copy rrd files back to $INSTALLDIR/pm/db.
run "$INSTALLDIR/fm/bin/pm.bat s"
Restart FMServer, discover fabric. Add fabric to collection. Restart
FM and DM are working OK now!
Fabric Manager Web Client does not start (either with localhost or using ip address)
On or "good working" sa005265 Fabric Manager Server:
C:\Documents and Settings\jd04841.DOM001>netstat -a -n -o | findstr 0.0:80
TCP 0.0.0.0:80 0.0.0.0:0 LISTENING 5304
TCP 0.0.0.0:8009 0.0.0.0:0 LISTENING 5304
This server works OK wih FM Web Client using localhost, IP or sa005265, local on server or remote Internet Explorer.
On our "bad working" sa005266
C:\Documents and Settings\jd04841>netstat -a -n -o | findstr 0.0:80
TCP 0.0.0.0:80 0.0.0.0:0 LISTENING 4
We found a system service "4" taking port :80!
For some reason there were two web servers contending for the port MS IIS and Apache.
When MS IIS is de-installed everything works again for FM WEb Client on port :80 ;-))
Can it be that FM comes with MS IIS for version 4 and uses Apache for version 5?
We reinstalled from scratch FM version 5.
All is working now!