Besclientui not starting with besclient service

I have encountered a system that is not running BESClientUI. BESClient service is running but BESClientUI is not. Have attempted to stop and restart the service, reinstall with repair, uninstall and install, run the BESClientUI Enable Mode task all with no success. I have retrieved the BESClient.dmp file. Our version of the BESClient is 9.2.6.94

I’d suggest having a look within the Client’s log as it should provide indications of the successful launch of the ClientUI, and if there are failures, the errors referenced in the log will be useful for troubleshooting.

1 Like

I started a remote session with our Bomgar tool. The Endpoint Manager Support Center was not in the system tray and was not running. Went into services and stopped BESClient. Waited and after a period started the BESClient service. Quickly noticed the BESClientUI starting and was not in the system tray as expected. There is a message in the log that needs to be resolved. <RegisterOnce: GetURL failed - General transport failure. - BAD SERVERNAME (winsock error -6) - registration url . . . >

error message is “RegisterOnce: GetURL failed - General transport failure. - BAD SERVERNAME (winsock error -6) - registration url . . .”

That doesn’t have much to do with the ClientUI, but the client is not able to resolve the DNS name of its relay/server