Openedge Explorer Tool The Remote Device Or Resource Won't Accept The Connection

[gerie]

I did a clean install of Progress 10.2B SP8 on a W2012R2 server.
When I try to open the Explorer tool I get the message: This page can't be displayed. Make sure the web address http://localhost:9090 is correct.
The event says: The remote device or resource won't accept the connection

Compatibility mode enabled for this site.
Changed the port in the fathom.properties file.
Set autostart=true in the fathom.properties file.
Controled the lockfiles.
C:\windows\system32\drivers\etc\hosts adjusted with 127.0.0.1 localhost.

Part of the adminserv.log:

[20-12-15 14:46:38] [3] [Database] All secondary brokers for configuration edis.defaultconfiguration are accounted for (ADMMsg001)
[20-12-15 14:46:38] [3] [Database] All auxiliary processes for configuration edis.defaultconfiguration are accounted for (ADMMsg016)
[20-12-15 14:46:39] [3] [Database] All secondary brokers for configuration exactcs.defaultconfiguration are accounted for (ADMMsg001)
[20-12-15 14:46:41] [3] [Fathom] All databases were successfully autostarted.
[20-12-15 14:46:41] [2] [Fathom] Starting Fathom probe. Version: 10.2A0000 (10142)
[20-12-15 14:46:41] [2] [Fathom] Fathom Build Date: Mon Feb 16 04:11:51 EST 2009 (10247)
[20-12-15 14:46:41] [2] [Fathom] Progress Version: 10.2B08 (10248)
[20-12-15 14:46:41] [2] [Fathom] Progress Build Date: Tue Nov 12 19:06:41 EST 2013 (10249)
[20-12-15 14:46:41] [3] [Fathom] Loading catalog file from:fathom.jar
[20-12-15 14:46:41] [3] [Database] All auxiliary processes for configuration exactcs.defaultconfiguration are accounted for (ADMMsg016)
[20-12-15 14:46:42] [3] [Fathom] Catalog file loaded.
[20-12-15 14:46:42] [3] [Fathom] Opening Fathom configuration database: C:\Progress\OEManage\config\fathom.odb (11027)
[20-12-15 14:46:43] [0] [Fathom] * Error opening Fathom configuration database: C:\Progress\OEManage\config\fathom.odb (11030)
[20-12-15 14:46:43] [0] [Fathom] * Fathom configuration database is already locked. Verify that Fathom is not already running. If it is not running and the Fathom configuration database lock file exists delete the lock file and restart Fathom. Lock file: C:\Progress\OEManage\config\fathom.odx (11031)
[20-12-15 14:46:43] [0] [Fathom] * Error starting Fathom probe: "Error loading Fathom configuration database." (10148)
[20-12-15 14:46:43] [3] [Fathom] Stopping Fathom probe. (10149)
[20-12-15 14:46:43] [3] [Fathom] Stopping Fathom project. (10152)
[20-12-15 14:46:43] [3] [Fathom] Fathom project stopped. (10153)
[20-12-15 14:46:43] [3] [Fathom] Stopping Fathom WebServer. (10154)
[20-12-15 14:46:43] [3] [Fathom] Fathom WebServer stopped. (10155)
[20-12-15 14:46:43] [3] [Fathom] Fathom probe stopped. (10156)


I renamed the Phatom.odf and Phatom.odb

Adminserver restarted.

All my actions made no difference. I think I followed all the options I could find in the knowledge base and I'm out of ideas. I configures 5 servers in the same way. 4 of them work just fine. Only one server has this problem and I don't know why.

Can anyone help me in the right direction?

 

[mollyfud]

Silly question, did you try deleting/renaming the file mentioned as the lock file and retrying?

 

[gerie]

Not so silly. I forgot to mention that there was no lock file.

 

[Stefan]

You seem to have a 10.2A / 10.2B mixed installation, on a machine here with 10.2B08 the startup is:

[9/22/15 4:47:28 PM] [2] [Fathom]                Starting Fathom probe. Version: 10.2B0800 (10142)
[9/22/15 4:47:28 PM] [2] [Fathom]                Fathom Build Date: Nov 13, 2013 1:06:41 AM (10247)
[9/22/15 4:47:28 PM] [2] [Fathom]                Progress Version: 10.2B08 (10248)
[9/22/15 4:47:28 PM] [2] [Fathom]                Progress Build Date: Nov 13, 2013 1:06:41 AM (10249)

You have:

[20-12-15 14:46:41] [2] [Fathom] Starting Fathom probe. Version: 10.2A0000 (10142)
[20-12-15 14:46:41] [2] [Fathom] Fathom Build Date: Mon Feb 16 04:11:51 EST 2009 (10247)
[20-12-15 14:46:41] [2] [Fathom] Progress Version: 10.2B08 (10248)
[20-12-15 14:46:41] [2] [Fathom] Progress Build Date: Tue Nov 12 19:06:41 EST 2013 (10249)

 

[gerie]

Hm I see what you mean. No idea how that happened. I have no knowledge of installing 10.2A. Weird......

 

[gerie]

Any suggestions how to alter this situation without haveing to reinstall everything are most welcome. ;-)

 

[Chris Hughes]

Hmm this is a pain I (too) often come up against.

The 10.2A and 10.2B installations will be cross linked now, you may find the OE Explorer on 10.2A doesn't work either.

The steps are to de-link the two installations, and then update 10.2B to run on different ports.

One of those things I've been meaning to properly document for a while, these KB's may help

Progress KB - Unable to connect to the AdminServer with OpenEdge Explorer after a new installation of OpenEdge on Windows.
Progress KB - How To Configure Multiple Versions of AdminServer To Be Run Concurrently since OpenEdge 10.1B