Crash after updating Beta 2 to Beta 3

As described, Logos 4 crashed shortly after starting and is repeatable. Message is "The key 'SecureHiddenResourceSyncBaseUri' does not exist in the appSettings configuration section."

5635.Beta3Crash.log

When started Offline L4 came up OK and began to index TLOT which had been downloaded "Today"; which is the first time I used L4 in a number of days (update download was 59.4 MB). However, L4 still crashes when started normally.

Find more posts tagged with

Comments

Bradley Grainger (Logos)

It sounds like appSettings.config didn't get updated during the install. Try deleting \Beta\Logos4\System\Logos4\appSettings.config, then finding Logos4.msi, right-clicking it, and choosing Repair.

(Logos4.msi may be in \Beta\Logos4\Install\Installers\Logos4.msi, or it may (incorrectly) have ignored the custom install path and have been saved in C:\Users\<you>\AppData\Local\Logos4\Install\Installers\Logos4.msi.)

Dave Hooton

https://community.logos.com/discussion/comment/374405#Comment_374405

It sounds like appSettings.config didn't get updated during the install. Try deleting \Beta\Logos4\System\Logos4\appSettings.config, then finding Logos4.msi, right-clicking it, and choosing Repair.

That fixed it, thanks.

The original file was 7 KB, dated 28/5/2012 and it was replaced by a file 8 KB, dated 23/5/2012. The installer might have expected the original file to be dated earlier than the 23rd but the msi is dated 31/5/2012 so it should have been replaced anyway?

(Logos4.msi may be in \Beta\Logos4\Install\Installers\Logos4.msi, or it may (incorrectly) have ignored the custom install path and have been saved in C:\Users\<you>\AppData\Local\Logos4\Install\Installers\Logos4.msi.)

The web link puts it in the standard path and it was in the same path after this "normal update" method. Prerequisites msi goes to the standard path of the user account with Admin rights! So why not recommend repairing the installation from Programs and Features?

Bradley Grainger (Logos)

https://community.logos.com/discussion/comment/374531#Comment_374531

So why not recommend repairing the installation from Programs and Features?

That would have been a good idea. [:$]

I guess I just like to solve problems the hard way?

Dave Hooton

https://community.logos.com/discussion/comment/374531#Comment_374531

It sounds like appSettings.config didn't get updated during the install. Try deleting \Beta\Logos4\System\Logos4\appSettings.config, then finding Logos4.msi, right-clicking it, and choosing Repair.

That fixed it, thanks.

The original file was 7 KB, dated 28/5/2012 and it was replaced by a file 8 KB, dated 23/5/2012. The installer might have expected the original file to be dated earlier than the 23rd but the msi is dated 31/5/2012 so it should have been replaced anyway?

(Logos4.msi may be in \Beta\Logos4\Install\Installers\Logos4.msi, or it may (incorrectly) have ignored the custom install path and have been saved in C:\Users\<you>\AppData\Local\Logos4\Install\Installers\Logos4.msi.)

The web link puts it in the standard path and it was in the same path after this "normal update" method. Prerequisites msi goes to the standard path of the user account with Admin rights! So why not recommend repairing the installation from Programs and Features?

This problem occurred when updating to 4.5c SR-3 from 4.5b SR-3 (different system). Whilst the original file was 28/5/2012 the repair replaced it with a file dated 1/6/2012 (dll's were dated 13 July).

Dave Hooton

https://community.logos.com/discussion/comment/382863#Comment_382863

This problem occurred when updating to 4.5c SR-3 from 4.5b SR-3 (different system).

To clarify:

This problem re-occurred when updating to 4.5c SR-3 from 4.5b SR-3 on a different system.