HELP: Logos crashes due to faulty Lectionary

Hi,

I played around with a PB of type Lectionary.
Following the intuitive path I set the value for @YearMonthDay as YYYY-MM-DD
(as one expect from the name and is the correct international ISO format for dates, mind you).
Of course, PBB gave me 365 warnings, which I corrected,
but instead of recompiling I opened the resource and was eager to see at work on the home screen.

BIG MISTAKE:
The lectionary opens on date "January 1, 0001" and seconds later Logos 5 crashes on me.

Now, my question is:
How can I disable this faulty lectionary outside of Logos?
I have searched hi and lo for some file I could remove, but no luck so far...

That aside, I think Logos 5 needs to treat faulty dates a bit more gracefully...
and make @YearMonthDay a bit more international/flexible (or perhaps rename it).

Find more posts tagged with

Comments

NB.Mick

Thomas,

you may try to open to a blank layout (holding Ctrl key when starting L5, then checking the respective box on the sign-on screen), then go to the library, hide the lectionary resource, restart Logos.

Hope this helps!

Mick

Thomas B.

https://community.logos.com/discussion/comment/621158#Comment_621158

Hi Mick,

For a minute or so I was hopeful, but even the blank layout crashes on me... [:(]

NB.Mick

https://community.logos.com/discussion/comment/621163#Comment_621163

can you post logs?

Thomas Ball

https://community.logos.com/discussion/comment/621176#Comment_621176

can you post logs?

And the source file?

NB.Mick

https://community.logos.com/discussion/comment/621163#Comment_621163

If not, maybe someone from Logos or the veteran MVPs drops by - I don't know whether

deleting the PB document (the file with the name consisting of cryptical long numbers that appear also as 'x'es in your PB log as PBB_xxxxxxxxxxxxxxxxxxxx_2014-08-(rest of timestamp)Z.log ending with lbspbb
deleting the personal books index
or both

will help you or make your situation worse. Calling Logos Technical Support might be in order, if no one else gives a recommendation that helps.

I retract that, since Tommy answered while I was typing.

Thomas B.

https://community.logos.com/discussion/comment/621228#Comment_621228

Ah, I identified the resource and succussfully deleted it.
Now, Logos comes back as it should. Thanks a lot!!!

For those inclined to fix this issue, here is the LogosCrash.txt

Program Version: 5.2b SR-1 (5.2.2.1496)
Windows Version: 6.1.7601.65536
Time: 2014-08-25 19:56:03 +02:00 (2014-08-25T17:56:03Z)
Installed memory: 3,493 MB
Install path: C:\Users\xxxx\AppData\Local\Logos4\System\Logos.exe
Free install space: 15,967 MB
Data path: C:\Users\xxxx\AppData\Local\Logos4\Data\s5ohniil.1ya
Free disk space: 15,967 MB
Temp path: C:\Users\xxxx\AppData\Local\Temp\
Free temp space: 15,967 MB

Error ID: 6411
Error detail: WrongDataTypeException: seqReferences

Libronix.DataTypes.WrongDataTypeException: seqReferences
   at Libronix.DataTypes.StandardDataType`1.CastReference(DataTypeReference refIn, String strArgName)
   at Libronix.DataTypes.Bible.BibleDataTypeFormatInfo.RenderReferencesCore(IEnumerable`1 seqReferences, DataTypeRenderStyle style, Object context)
   at Libronix.DataTypes.DataTypeFormatInfo.RenderReferences(IEnumerable`1 seqReferences, DataTypeRenderStyle style, Object context)
   at Libronix.DataTypes.DataTypeFormatInfo.<RenderRichTextReferencesCore>d__a.MoveNext()
   at System.Linq.Enumerable.<SelectManyIterator>d__14`2.MoveNext()
   at System.Collections.Generic.List`1.InsertRange(Int32 index, IEnumerable`1 collection)
   at LDLS4.HomePage.Tools.LectionaryToolViewModel.CreateRichText(IEnumerable`1 readings, List`1 alternateLinks)
   at LDLS4.HomePage.Tools.LectionaryToolViewModel.<UpdateToolWork>d__1d.MoveNext()
   at Libronix.Utility.Threading.AsyncWorkerTask`1.EnumMoveNext()

Again, this is for invalid @YearMonthDay fields, like this:

YearMonthDay: 2014-01-04]] {{field-on:day}} Das Wort für Samstag, 4. Januar 2014 {{field-off:day}}
Erstspruch: Wenn ihr nun wirklich meiner Stimme Gehör schenken
und gehorchen werdet und meinen Bund bewahrt,
dann sollt ihr vor allen Völkern mein besonderes Eigentum sein;
denn die ganze Erde gehört mir.{{field-on:reading}} [[2. Mose 19,5 >> biblelutbib1984: 2. Mose 19,5]] {{field-off:reading}}
Zweitspruch: Wohl dem Volk, dessen Gott der Herr ist,
dem Volk, das er sich zum Erbe erwählt hat!{{field-on:reading}} [[Psalm 33,12 >> biblelutbib1984: Psalm 33,12]] {{field-off:reading}}

Dave Hooton

https://community.logos.com/discussion/comment/621306#Comment_621306

Again, this is for invalid @YearMonthDay fields, like this:

YearMonthDay: 2014-01-04]] {{field-on:day}} Das Wort für Samstag, 4. Januar 2014 {{field-off:day}}

When it should be [[@YearMonthDay:Jan 4, 2014]] {{field-on:day}} Das Wort für Samstag, 4. Januar 2014 {{field-off:day}}

NB.Mick

https://community.logos.com/discussion/comment/621315#Comment_621315

Based on my experience with the "Losungen" (Moravian Daily Texts / Watchwords) the alternative format [[@YearMonthDay:mm/dd/yyyy]] e.g. [[@YearMonthDay:01/17/2012]] works as well and as it is numerical may be better suited to be generated from string functions in Excel (for the syntax details of PB tagging see https://wiki.logos.com/Personal_Books )

MJ. Smith

https://community.logos.com/discussion/comment/621328#Comment_621328

From my experience, none of the formats resolve the basic problem of the lectionary combining the ordo and the lectionary into one and requiring multiple occurrences of the same entry (think index portion) if one wants it to work correctly. But one can work with what we have ...

Thomas B.

https://community.logos.com/discussion/comment/621328#Comment_621328

I (now) know what the correct format is.Given the name of the field (@YearMonthDay), however, it is rather counter-intuitive.

Mind you, most people in the world don't use MonthDayYear as their date format.
See here:

http://en.wikipedia.org/wiki/Date_format_by_country

Again, my main quarrel is with the lack of grace and the subsequent abort for not obeying the law (of US date formats, that is)

Thanks for all your quick help!!

NB.Mick

https://community.logos.com/discussion/comment/621306#Comment_621306

Ah, I identified the resource and succussfully deleted it.
Now, Logos comes back as it should. Thanks a lot!!!

I forgot above:

You're very welcome, glad to hear your Logos is working again and thanks for telling how it resolved (this may help others until the bug is fixed)!