Missing Resources in Beta install in separate Windows account

I installed 4.0b Beta in a separate Windows account. Its a brand new install as I had deleted the 4.0a Beta.

I downloaded 8.04 Gb of data - that took nearly 24 hrs and I had three "moves" of the computer during it - put laptop into sleep mode and it resumed, plus several loss of internet connections, but resumed each time.

When done, the reading plan for one of my books showed no readings. I searched for it and found it isn't in my separate install directory.

I have it in my SR2 install in my main account and it is accessible, and downloaded, on my iPod Touch install.

I checked my Library and found only 1310 books. In my SR2 main account, I have 1331.

I tho't some might have been corrupted in all the interruptions in the download. So I compared my SR2 and 4.0b Beta directories - the files are missing. I ran "update resources" downloaded 260 Mbs and gained 4 resources. I tried "update resources" again and got "all resources are up to date."

I could copy the missing files, but don't want to mess up (in light of Bradley's warnings on the Beta forum) my installs.

Chris

Find more posts tagged with

Comments

Mark Smith

Chris,

How about copying the files to a new location, then using the scan command in the new installation to see if Logos will pick these up and transfer them to your resources directory?

Chris Elford

https://community.logos.com/discussion/comment/73137#Comment_73137

Chris,

How about copying the files to a new location, then using the scan command in the new installation to see if Logos will pick these up and transfer them to your resources directory?

Mark,

I realize I could do this, but wondered if that might "corrupt" the beta - in light of Bradley's stern warning in http://community.logos.com/forums/t/8883.aspx

Do not share resources or Data folders between the stable Logos 4 and the Logos 4 Beta release; the format of data files and (some) resources in Logos 4 Beta may have changed, making them unreadable by Logos 4.

And, I don't think it should miss a bunch of resources. It's the old "If it misses these this time, what might it miss another time" fear of the Cloud.

I guess I'd like to get a fix rather than a work around.

Chris

Mark Smith

https://community.logos.com/discussion/comment/73150#Comment_73150

I think Bradley's warning is about shared resources and folders. Copying then scanning would put those resources into your new folder. You wouldn't be sharing them.

Chris Elford

https://community.logos.com/discussion/comment/73156#Comment_73156

I think Bradley's warning is about shared resources and folders. Copying then scanning would put those resources into your new folder. You wouldn't be sharing them.

Oh, I thought he was warning that "some" resources have changed format and can't be shared (or exchanged). Because I don't know which I was unwilling to go ahead like a bull.

I also wondered how someone who hasn't messed around like we have in our files would be able to solve this issue.

Because it affected a resource I use for a reading plan it was obvious something was wrong - it was all over my banner - like a Banner in the Sky!

Chris

Mark Smith

https://community.logos.com/discussion/comment/73167#Comment_73167

I think the 4.0b resources cannot be read in 4.0a therefore the warning. I didn't get from what Bradley said that 4.0a resources wouldn't mix with 4.0b. I was imagining it like a 2007 Word file cannot be read by Word 2002 (or whatever earlier version) because the file format has changed. The earlier version files can be read in the newer version software, however. I could be the dummy here, though.

Chris Elford

https://community.logos.com/discussion/comment/73175#Comment_73175

Mark,

I tried moving one of the missing files and then ran scan. Closed L4 and re-opened. Waited. No resource. Closed again. Re-opened. No resource.

Still at 1314 resources.

I think my licence must be corrupted on the server. I suspect I'll have to call. I guess it will have to wait until Monday.

I might try a straight copy the file into the beta resource file - don't remember if some have found this works or not.

Chris

EDIT: Must have mistyped something. Tried again and now it's there.

Now for the other ones.

Rosie Perera

https://community.logos.com/discussion/comment/73185#Comment_73185

I think my licence must be corrupted on the server. I suspect I'll have to call. I guess it will have to wait until Monday.

Just FYI, if you suspect a corrupted license file, the corrupted one might be on your computer rather than on the server. It is safe to delete your copy of it and force it to be downloaded fresh from the server, as instructed by Bradley Grainger in this post.

Sounds like you're on the way to success though, so you probably don't need to try this.

Chris Elford

https://community.logos.com/discussion/comment/73191#Comment_73191

I think my licence must be corrupted on the server. I suspect I'll have to call. I guess it will have to wait until Monday.

Just FYI, if you suspect a corrupted license file, the corrupted one might be on your computer rather than on the server. It is safe to delete your copy of it and force it to be downloaded fresh from the server, as instructed by Bradley Grainger in this post.

Sounds like you're on the way to success though, so you probably don't need to try this.

Rosie,

Thanks for that. I remember seeing that post, but never put it together with my issue. I tried it, the license.dat file that was downloaded today is different from the one that was installed when I put the Beta on, but update resources still says there are no updates available.

Scan seems to be the only solution.

FWIW, here's are the files that were not installed:

Chris

SteveF

https://community.logos.com/discussion/comment/73441#Comment_73441

Chris be warned:

three of these files will cause problems. You do NOT want them on any system:

LEXHAMSGGNT.lbssyn

LEXHAMSGGNT.lbxclv

(and I think ) LEXglossary.logos 4 (not sure of it)

But the first two have been replaced by the newer CASCADIA files etc.

Dave Hooten has a thread on this somewhere in response to a problem I had with these. They were supposedly OFF of mine yet were still CRASHING everything (ie. M$ error report etc.)

Regards

Steve

Chris Elford

https://community.logos.com/discussion/comment/73653#Comment_73653

Chris be warned:

three of these files will cause problems. You do NOT want them on any system:

LEXHAMSGGNT.lbssyn

LEXHAMSGGNT.lbxclv

(and I think ) LEXglossary.logos 4 (not sure of it)

But the first two have been replaced by the newer CASCADIA files etc.

Dave Hooten has a thread on this somewhere in response to a problem I had with these. They were supposedly OFF of mine yet were still CRASHING everything (ie. M$ error report etc.)

Regards

Steve

Thanks, Steve. I haven't actually scanned them in yet -- just the 131 people book, because I wanted to give time for such a response as yours.

What's funny (not ha ha, but CURIOUS) is that those are in my SR2 data files and aren't causing any problem. I had problems during the private beta when they converted to Cascadia. I hadn't picked up on the fact they had not deleted those files.

Are you (along with Dave) recommending they be deleted from all files.

EDIT: Steve, the first two files are .lbssyn and .lbxclv, but the Glossary files is a .logos4 file, so I think it is probably safe.

Chris

SteveF

https://community.logos.com/discussion/comment/73676#Comment_73676

Are you (along with Dave) recommending they be deleted from all files.

EDIT: Steve, the first two files are .lbssyn and .lbxclv, but the Glossary files is a .logos4 file, so I think it is probably safe.

Chris

Dear Chris:

I accept Dave's advice even before my own! (so yes)

& thanks for the note that "glossary" is now a L4 file.

Dave Hooton

https://community.logos.com/discussion/comment/73676#Comment_73676

Thanks, Steve. I haven't actually scanned them in yet -- just the 131 people book, because I wanted to give time for such a response as yours.

What's funny (not ha ha, but CURIOUS) is that those are in my SR2 data files and aren't causing any problem. I had problems during the private beta when they converted to Cascadia. I hadn't picked up on the fact they had not deleted those files.

Are you (along with Dave) recommending they be deleted from all files.

EDIT: Steve, the first two files are .lbssyn and .lbxclv, but the Glossary files is a .logos4 file, so I think it is probably safe.

You should delete LexhamSGGNT.lbssyn and LexhamSGGNT.lbxclv together with LexSGGlossary.logos4 from the L4 resource folder! All have been replaced by Cascadia Syntax Graphs.

Chris Elford

https://community.logos.com/discussion/comment/73750#Comment_73750

You should delete LexhamSGGNT.lbssyn and LexhamSGGNT.lbxclv together with LexSGGlossary.logos4 from the L4 resource folder! All have been replaced by Cascadia Syntax Graphs.

Thanks, Dave.

Bradley Grainger (Logos)

https://community.logos.com/discussion/comment/73441#Comment_73441

FWIW, here's are the files that were not installed:

Thanks for posting this list; I'm going to look into the problem.

We have a couple of Chris Elford's in our system; can you confirm that you're logging in to Logos 4 with an email address containing "@rocky" ?

I've been able to reproduce this problem on my own account and have filed a bug with the server team.

Bradley Grainger (Logos)

https://community.logos.com/discussion/comment/74622#Comment_74622

The bug that prevented these 14 (non-Lexham SGGNT) resources from being downloaded has been fixed. Your system should automatically detect the missing files and start downloading the next time you run Logos 4 (or if you enter "update now" into the command box). (You can enter "update resources" to force a full check for missing resources, but I would be interested to know if the resources do get downloaded without forcing that full check.)