b9 pre-MS error report

first I'll send logs from pre-error report.

- the software loaded slightly minimized and "blank" as planned - I quickly looked at "Help file" Had hardly started that when error message popped up.

These "immediate" error reports began in b7 - got worse in b8 - and now continue in b9

I did not have them in b1-b6 (which was quite stable compared to all the others).

Steve

Logos4.log

Find more posts tagged with

Performance

Comments

SteveF

Hopefully this is log after error report.

If I were to reply to each error report as soon as each one appears, then the software would be unusable. They result in it continually disappearing from the screen.

The Release notes for b9 mentioned fixing a bug that crashed etc the software shortly after it loads. This "fix" has apparently NOT worked for mine.

Steve

Logos4.log

Bradley Grainger (Logos)

https://community.logos.com/discussion/comment/21208#Comment_21208

Hopefully this is log after error report.

The error in your log indicates a bug in the server that I was told was going to be fixed last night (but I haven't received confirmation of that). Assuming it is fixed, deleting the following file should let you restart Logos 4 without crashing:

C:\Documents and Settings\Stephen\Local Settings\Application Data\Logos4\Data\x1dsklus.tt5\Updates\Metadata.db

SteveF

https://community.logos.com/discussion/comment/21284#Comment_21284

(Sorry to be so long getting back to you, I was off doing a wedding this afternoon.)

Deleted the "Metadata" file and attempted to start software (successfully loaded "blank" screen) at 5:28:43

5:31:13 So far so good - it has now been over 2.5 minutes without the "error report message."

Do you need another log report, now that it appears to have been fixed?

Thanks

Steve

ps. After the constant "messages" from these last 2-3 betas this is a GREAT relief!

5:35 After waiting 7 minutes with no "MS message" even the home page opened successfully

Again, many thanks, Bradley!!!

Bradley Grainger (Logos)

https://community.logos.com/discussion/comment/21330#Comment_21330

Do you need another log report, now that it appears to have been fixed?

No need to send in another log file if everything's working fine. (I did receive confirmation that the server problem causing your bug was fixed, so if you do crash again, it's probably a different problem. Please create a new topic with your new log file for any new crashes.)