[ISS Support Case] Warning messages in logger from OMI App

Last updated: October 17th, 2025

Description

We are working on some new OMI applications. Yesterday and today I saw some warning messages in the Archestra logger pop up on two different servers. The problem is the warning kept showing up in the logger over and over. The warning is: Failed to connect to 'Galaxy'. Error description: Connect found no endpoints for contract IDataV3 with access name domainname/Galaxy/closest It is coming from View.exe. As of now, I can make this warning stop appearing by shutting down the application. Any idea what this warning means and what triggers it? Is there a way to stop this warning from appearing in the logger without having to shut down the application.

Author: Kevin Modlin
Published: October 17th, 2025

Details:

Product: InTouch OMI

Version: 2020 R2

Solution: [Solution is visible below when you're logged in and have a current subscription]

Date Created:	01/12/2022
Case:	80264

Give feedback about this article

Recommended articles

[ISS Support Case] Trend not showing correct data from the previous day

Production machine that's been in production for a while Noticed the issue on the 20th They are unaware of any changes that could have caused the issue

[ISS Support Case] OMI MapApp Configuration

Client reached out looking for guidance on configuring the MapApp.

[ISS Support Case] Trend SQL DB Connection Issue

Client reached out due to receiging the following error when trying to login/connect to SQL DB within OMI Trends: "System.Security.Cryptography.CryptographicException: Key not valid for use in specified state."

[ISS Support Case] OMI Alarm Client Not Re-Querying Properly

I am having a really hard time understanding why my alarm query is not updating according to the script I wrote up. I have a script that should change how the alarm client is queried based on the current navigation. It updates the query accordingly when I navigate from one layout to another. However, when I navigate from one screen to another (that uses the same layout), the alarm query refuses to update!