[ISS Support Case] Launching InTouch Results In ALARMS.CFG corrupted error

Last updated: October 17th, 2025

Description

Unable to start Intouch windowviewer. When attempting to launch I get a ALARMS.CFG corrupted error. Reseploying the view engine and view app did not resolve this. The computer that has this issue hosts objects that are in active production so I cannot attempt to redeploy the platform while they are actively running. Would like some guidance on how to resolve this.

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:	04/08/2022
Case:	81331

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!