Omnis.cfg – Corrupted
Hi Derek,
The “serial.txt” will assist in the creation of a new “omnis.cfg” as you
will not have to manually enter the serialization information. But you
still need to delete to corrupt “omnis.cfg” and restart omnis to get that
done.
Just had another customer report the issue this afternoon. Same exact issue
the “omnis.cfg” is a 6k file but it is full of “Hex 0” instead of any
meaningful data.
*********************************************************************
Michael Mantkowski
ClienTrax Software
1-614-875-2245
*********************************************************************
—–Original Message—–
From: omnisdev-en [mailto:omnisdev-en-bounces@lists.omnis-dev.com] On Behalf
Of Derek Delpero
Sent: Tuesday, November 7, 2017 3:45 PM
To: OmnisDev List – English <omnisdev-en@lists.omnis-dev.com>
Subject: Re: Omnis.cfg – Corrupted
Hi Michael,
It’s my understanding that if you have a serial.txt file that it will also
automatically re-create the omnis.cfg if it’s corrupt. When Jock’s
application was having a lot of omnis.cfg errors, I added a method to the
startup library to generate a serial.txt file. Once that was released, the
issue with a corrupt omnis.cfg has almost gone away entirely.
Derek
On Tue, Nov 7, 2017 at 12:30 PM, Michael Mantkowski <michaelj@clientrax.com>
wrote:
> I figured as much. I know this issue has come up from time to time
> over the years. Never understood why it was saved this way and that
> there is no way to automatically overcome an issue with it.
>
> *********************************************************************
> Michael Mantkowski
> ClienTrax Software
> 1-614-875-2245
> *********************************************************************
>
>
> —–Original Message—–
> From: omnisdev-en [mailto:omnisdev-en-bounces@lists.omnis-dev.com] On
> Behalf Of Alex Clay
> Sent: Tuesday, November 7, 2017 1:24 PM
> To: OmnisDev List – English <omnisdev-en@lists.omnis-dev.com>
> Subject: Re: Omnis.cfg – Corrupted
>
> Hi Michael,
>
> It was in an email exchange with the UK support team for Omnis
> software in reference to another issue.
>
> I believe that file is a proprietary binary format and there’s not a
> way for us to read it out. FWIW, it seems that Omnis is migrating away
> from using this file. New options in Studio 8.x are going into the
> config.json file which is nice, readable JSON.
>
> Alex
>
>
> > On Nov 7, 2017, at 13:19, Michael Mantkowski
> > <michaelj@clientrax.com>
> wrote:
> >
> > It’s possible Alex. I will check into it.
> >
> > Where did you see that?
> >
> > BTW, does anyone know how this file is formatted? Is there any way
> > for
> “Us”
> > to read it?
> >
> > ********************************************************************
> > *
> > Michael Mantkowski
> > ClienTrax Software
> > 1-614-875-2245
> > ********************************************************************
> > *
> >
> >
> > —–Original Message—–
> > From: omnisdev-en [mailto:omnisdev-en-bounces@lists.omnis-dev.com]
> > On Behalf Of Alex Clay
> > Sent: Tuesday, November 7, 2017 1:16 PM
> > To: OmnisDev List – English <omnisdev-en@lists.omnis-dev.com>
> > Subject: Re: Omnis.cfg – Corrupted
> >
> > Hi Michael,
> >
> > I haven’t seen much of this personally, but Omnis support recently
> > mentioned that shutting off a PC with Omnis still running is known
> > to corrupt the omnis.cfg file. Perhaps this is what your clients are
doing?
> >
> > Alex
> >
> >> On Nov 7, 2017, at 13:08, Michael Mantkowski
> >> <michaelj@clientrax.com>
> > wrote:
> >>
> >> Hi Dan,
> >>
> >> I was thinking something similar. But hate resorting to a Batch file.
> >> Just seems so “stone age”. lol
> >>
> >> It would be really nice to know how this happens. It’s as if
> >> everything in the file is overwritten with Hex 0.
> >>
> >> *******************************************************************
> >> **
> >> Michael Mantkowski
> >> ClienTrax Software
> >> 1-614-875-2245
> >> *******************************************************************
> >> **
> >>
> >>
> >> —–Original Message—–
> >> From: omnisdev-en [mailto:omnisdev-en-bounces@lists.omnis-dev.com]
> >> On Behalf Of Dan Ridinger
> >> Sent: Tuesday, November 7, 2017 12:59 PM
> >> To: OmnisDev List – English <omnisdev-en@lists.omnis-dev.com>
> >> Subject: Re: Omnis.cfg – Corrupted
> >>
> >> Hello Michael,
> >>
> >> I had this happen on one client (windows machine) I got frustrated
> >> as you have. All I did i wrote a batch job that started on startup
> >> of Omnis app and copied a good copy of omnis.cfg file to the
> >> correct location and that took care of the problem. Not elegant but
> >> has worked
> > perfectly for 10 years.
> >>
> >> Dan Ridinger
> >> Managing Director
> >>
> >>
> >>
> >>
> >> FutureChalk Software Inc.
> >> 20521 92A Avenue
> >> Langley, BC V1M 1B7
> >>
> >> Phone No: 604.723.6837
> >> EMail: dlr@futurechalk.com
> >> www: www.futurechalk.com
> >>
> >>> On Nov 7, 2017, at 7:18 AM, Michael Mantkowski
> >>> <michaelj@clientrax.com>
> >> 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
> >>
> >> _____________________________________________________________
> >> Manage your list subscriptions at lists.omnis-dev.com
> >>
> >> _____________________________________________________________
> >> Manage your list subscriptions at lists.omnis-dev.com
> >
> > _____________________________________________________________
> > Manage your list subscriptions at lists.omnis-dev.com
> >
> > _____________________________________________________________
> > Manage your list subscriptions at lists.omnis-dev.com
>
> _____________________________________________________________
> Manage your list subscriptions at lists.omnis-dev.com
>
> _____________________________________________________________
> Manage your list subscriptions at lists.omnis-dev.com
>
_____________________________________________________________
Manage your list subscriptions at lists.omnis-dev.com
_____________________________________________________________
Manage your list subscriptions at lists.omnis-dev.com
