Unable to connect Diagnostics Console to remote server

[Dillon_Miller]

Background: We just upgraded to OnBase Foundation v19 EP2, and are looking to have our development team connect the Diagnostics Console installed on their workstations to a remote application server. Read through the Diagnostics Console MRG extensively, but am unable to get our team to connect.

So far, I have: 

1. Ensured that the 'Hyland Diagnostics Service' Windows service is running on the application server
   1. This service is ran by a domain account with permissions to everything OnBase-related on the server
2. Verified that I can access the Diagnostics Console locally from the application server
3. Used every variant of the application server's URL, with and without the 8989 port (not sure if that's necessary):
   1. https://hostname/AppServer/Service.asmx 
   2. http://hostname:8989
   3. http://hostname:8989/AppServer/Service.asmx
   4. etc, about fifteen different variations
4. Verified that from the developer workstation, they can successfully access the application server URL via web browser
5. Checked to make sure port 8989 was not blocked

I have never configured the Diagnostic Console for remote access. Not sure what else I can try here, and help would be greatly appreciated!

[Kirk_Sumpter]

Hi Dillon,

I ran into this when I upgraded to v18 so it might still be the same; look for the following key in the diagnostics service (make sure it's the service, not diagnostic console) config file, and make sure it's set to true:

<RemoteClientRelayMessageAction AllMessageTypes="true"/>

Apparently they made the default to false in v18 as a security control.

As far as how to select remote in the console when launching, you should just need the machine name and port 8989 to connect (assuming this is the same issue I experienced).

[Dillon_Miller]

Hi Kirk,

Really appreciate you taking the time to review this. I was unable to find anything like an 'exe.config' file for the Diagnostics Service specifically (like I'm used to working in with the Unity Scheduler, Unity Client, etc).

I am not sure if I'm just missing where the file is, but for v19 EP2 I did not need to worry about correcting that key at all. The fix I used is listed in my response to Jim in this thread.

Thanks again for your help!

[Chris_Opper]

Hey Dillon,

I know this thread is a few months old so I'm not sure if you found a resolution to the error from Diagnostics Console where it throws the error "diagnostics NT service is not configured for remote access". 

Big thanks to Kirk, I was able to fix the issue with the recommendation of updating  <RemoteClientRelayMessageAction AllMessageTypes="true"/>. I initially had issues finding the line in the config file until I took a look at the DiagnosticServices Help file. In looking through help, I found there is actually another config file called "Hyland.Diagnostics.NTService.exe", which for me was located at the 64-Bit location (below). 

·       On 32-bit systems, this file typically resides in C:\Program Files\Hyland\Services\Diagnostics.

·       On 64-bit systems, this file typically resides in C:\Program Files (x86)\Hyland\Services\Diagnostics.

Once I updated the Remote Client line and set to True, Diagnostic Console opened up without an issue. 

[James_Perry · Accepted solution]

For OnBase Foundation EP1 this is what I had to do to get remote Diagnostics working.

On my production application and web servers I opened “C:\Program Files (x86)\Hyland\Services\Diagnostics\appsettings.json” in Notepad
Changed the BindIP from "http://localhost" to "http://0.0.0.0"
Saved the appsettings.json file
and finally, restarted the “Hyland Diagnostics Service” service

This is per the "Configuring the Diagnostics Service for Remote Access" section in the Diagnostics Service MRG (DiagnosticsService_FoEP1.pdf)

RESULTING JSON FILE
{
"Port": 8989,
"BindIP": "http://0.0.0.0"
}