Omnis.cfg – Corrupted

Michael Mantkowski, November 08 2017 06:43:57

Omnis.cfg – Corrupted

Hi Bas,

Yes, been an issue for many years but seems to have gotten worse recently.
One customer is linking it to getting Windows 10 updates. I don’t know if
that is correct or not but I suppose that certain updates if occurring while
running Omnis could cause the issue.

I sent a message to Omnis Support to see if there was something that we
could check for in a good Omnis.cfg to tell us the file was ok so that we
would know that there was no need to replace it. I could always check to
see if the first few bytes were Hex 0, but I am not positive that this is
the only symptom of a corrupted file.

My other idea is to simply delete it after quitting Omnis or before starting
it every time. As it seems to have no ill effect on our runtime application
this could be a viable workaround. Not that I like it. But having 5 or 6
customer calls a week for this one issue gets old. And it makes them thing
there is something wrong with our program.

*********************************************************************
Michael Mantkowski
ClienTrax Software
1-614-875-2245
*********************************************************************

—–Original Message—–
From: omnisdev-en [mailto:omnisdev-en-bounces@lists.omnis-dev.com] On Behalf
Of Bastiaan Olij
Sent: Tuesday, November 7, 2017 8:33 PM
To: omnisdev-en@lists.omnis-dev.com
Subject: Re: Omnis.cfg – Corrupted

Hi Michael,

This has plagued us for years as well. The best understanding I have of the
problem is that the omnis.cfg file is opened when Omnis starts for reading
and writing. Certain actions such as changing preferences or changing data
file end up writing settings into this file.

There are (rare) situations where Omnis does not properly close this file
and when restarting Omnis the file is kept in some sort of locked state.
Often we find that a user will do a particular thing habitually that
contributes like leaving Omnis running overnight and returning in the
morning finding that the computer going to sleep and not coming back up
properly. But we’ve never been able to pin down what exactly causes it to go
wrong.

Tech support is evaluating a suggestion I made to them for changing the
logic, I don’t know where that stands right now and whether it will make the
problem go away but it may end up in a Studio 8 version at some point in
time.

Cheers,

Bas

On 8/11/17 2:18 am, Michael Mantkowski wrote:
> I have a client who is having frequent issues with the Omnis.cfg file
being corrupted. This is happening every few days.
>
> I have had him send me a copy and it is a 6k file filled with Hex 0 and
nothing else.
>
> So, when they try to start Omnis they get the Error message that it cannot
initialize the Omnis.cfg file and Omnis quits.
>
> All they customer has to do at this point is delete the current Omnis.cfg
and restart Omnis and it will create a new one and be fine. But obviously
this is not a great solution for them.
>
> Has anyone seen this before where someone gets this over and over? We see
it every so often with various clients but not where it keeps happening. I
wish that Omnis would just replace the file on its own if it cannot read the
current one. It does not save anything that we care about in the Runtime
anyway.
>
> I would like to come up with a method to automatically deal with this.
>
> *********************************************************************
> Michael Mantkowski
> ClienTrax Software
> 1-614-875-2245
> *********************************************************************
>
>
> _____________________________________________________________
> Manage your list subscriptions at lists.omnis-dev.com
>
>

—
Kindest Regards,

Bastiaan Olij
e-mail: bastiaan@basenlily.me
web: www.basenlily.me
Skype: Mux213
www.linkedin.com/in/bastiaanolij

_____________________________________________________________
Manage your list subscriptions at lists.omnis-dev.com

Omnis.cfg – Corrupted