Update Error

My first surprise is that LOGOS4 did not install the program in my "Program Files" directory, but instead in my "Users" directory as listed above. Is this an error regard installations? Is this where the program is suppose to install?

Yes, Logos4 installs to the User directory.

Full access to that directory may require administrator privileges, which may explain your other error.

https://community.logos.com/discussion/comment/50056#Comment_50056

You should make sure you run Logos with the same priveleges you had when you installed it. If you install as admin, then run as a user you can get problems.

Windell Gann

Thank you. Making sure I was running the program as Administrator solved the problem.

- Windell Gann

https://community.logos.com/discussion/comment/50093#Comment_50093

I'm seeing this same error on my system in the same scenario. However, I *am* a system administrator when I encounter this problem. Also, the path all the way to the Logos4.resources.dll file is writable from what I can see. In fact, if I remove the file (which I can do fine as an admin), and tell the install to "retry", it recreates the file in the target destination just fine--but it has a file size of 0--and the warning dialog reappears.

So it appears to be creating the file, but then fails when trying to write its contents for some unknown reason. Quite frustrating.

https://community.logos.com/discussion/comment/55538#Comment_55538

I'm seeing this same error on my system in the same scenario. However, I *am* a system administrator when I encounter this problem. Also, the path all the way to the Logos4.resources.dll file is writable from what I can see. In fact, if I remove the file (which I can do fine as an admin), and tell the install to "retry", it recreates the file in the target destination just fine--but it has a file size of 0--and the warning dialog reappears.

So it appears to be creating the file, but then fails when trying to write its contents for some unknown reason. Quite frustrating.

If your are unable to use Logos4, please contact tech support:

Email Support:
support@logos.com

Telephone Support:
(800) 875-6467

There may be multiple issue here that are beyond the scope of a forum to resolve.

https://community.logos.com/discussion/comment/55538#Comment_55538

I'm seeing this same error on my system in the same scenario. However, I *am* a system administrator when I encounter this problem.

It doesn't matter that you are an Administrator or Standard User, the issue arises if you invoke "run as administrator" when you install because this level of access will then be required when you perform an Update.

https://community.logos.com/discussion/comment/55788#Comment_55788

Hi Dave,

Thanks for your response.

Can you clarify a bit more what you mean? I performed a "standard" install of the original product while logged in as myself (and I have Administrator rights under XP). The original install went fine and the product works as advertized.

I'm only seeing this problem after closing the program and relaunching it--when it has detected an update and suggests installing it. I simply click "yes" and then it starts into the update, but then encounters this error.

I don't recall on the original installation whether there was a "run as administrator" option and, if there was, why would that prevent someone with an Administrator privilege from having the automatic update succeed?

https://community.logos.com/discussion/comment/55791#Comment_55791

Forgot to mention that this particular machine is running XP home -- so as far as I know I can't login directly as the "Administrator" account [unless there is a way to do that--I'm not very familiar with XP home since I spend most of my time under XP pro].

I thought about trying to log off as myself and then back in as "Administrator" and launch Logos4 under that account to see if the update would run successfully. But XP Home doesn't list an "Administrator" account. And I figured since I had Amin privileges that would be equivalent--especially since I installed the product logged in as myself.

https://community.logos.com/discussion/comment/55796#Comment_55796

If you installed Logos by right-clicking and choosing "Run as administrator", then you'll have to do the same everytime you run an update. On the other hand if you just installed it normally, then it should update normally.

https://community.logos.com/discussion/comment/56138#Comment_56138

I assume this means I have to select "Run as Administrator" when I launch Logos4--which subsequently detects and initiates the update?

So back to my other question: I'm using XP Home and when I "Run as ..." and look at the list of accounts, there is no plain "Administrator" account listed. All I can do is choose a non-Adminstrator account which has been given Admin privileges.

How can I "Run as Administrator" from within XP home? (Or is there a different way I'm supposed to be finding and launching the update?)

Thanks for your patience.

https://community.logos.com/discussion/comment/56345#Comment_56345

I assume this means I have to select "Run as Administrator" when I launch Logos4--which subsequently detects and initiates the update?

So back to my other question: I'm using XP Home and when I "Run as ..." and look at the list of accounts, there is no plain "Administrator" account listed. All I can do is choose a non-Adminstrator account which has been given Admin privileges.

How can I "Run as Administrator" from within XP home? (Or is there a different way I'm supposed to be finding and launching the update?)

Thanks for your patience.

If you did not explicitly choose to install "As Administrator", but simply clicked on the installation file/shortcut and let it run, this should not be the issue.

A denial of access to those folders may be caused by an overzealous anti-virus or anti-spyware program, by setting those folders to 'read only' or by some other process that I'm not thinking about at the moment.

If you haven't yet done so, enable logging (see this page for details on how to do that: http://wiki.logos.com/Diagnostic_Logging)

Run Logos and let it fail again. Before restarting Logos4 locate your logs (in My Documents\Logos Log Files\) and post the log here (use the paper clip on the reply screen to do that).

One of us or a Logos tech can look at the logs and possibly figure out whats going on.

If you're getting impatient with this process contact tech support directly at the email address or phone number I posted earlier.

https://community.logos.com/discussion/comment/56379#Comment_56379

Hi Richard,

Thanks for the additional suggestions. I did contact tech support as you suggested (thanks), but they appear to be pretty snowed under so I haven't heard anything yet.

As you surmised, I did not do the original install with "Run as...". I simply installed it while logged in as myself (with Admin permission)--as I've always done with Logos 3 and other applications in the past.

I'm in the process of reinstalling from scratch to see if that fixes the problem. If it doesn't, then I'll try your suggestion about capturing the log to see what it might indicate. I'm virtually certain the problem is not related to my antivirus software (Norton) or read-only. Prior to uninstalling, I verified that I can create, copy, rename, edit the very file in the very location it complains about (before it fails and restores the previous version in the same location).

If I still have problems I'll try to capture the log information next.

Thanks for help out on the forum.

- Tony

https://community.logos.com/discussion/comment/56460#Comment_56460

If I still have problems I'll try to capture the log information next.

Thanks for help out on the forum.

You're welcome.

Even if you don't have a problem, report back with success. It's always nice to hear when things go well too.

But if you do have a problem, by all means report back and include a log file, if you can.

https://community.logos.com/discussion/comment/56701#Comment_56701

I reinstalled the cross-grade from scratch and, so far, things are working--but I haven't seen it detect and attempt to initiate and update yet. Until that happens, I guess the jury is still out. Not sure how or when it decides to initiate an update after the initial install. I had assumed this would occur when it detects from the Logos website that an update is available. Maybe it hasn't checked yet.

In any case, I'll be more confident when I see it eventually detect and initiate an update--if that succeeds.

https://community.logos.com/discussion/comment/56716#Comment_56716

Whenever you install you always get the latest version, because most of files are downloaded by the installer. You'll have to wait until 4.0a, I'm afraid!

https://community.logos.com/discussion/comment/56345#Comment_56345

I assume this means I have to select "Run as Administrator" when I launch Logos4--which subsequently detects and initiates the update?

So back to my other question: I'm using XP Home and when I "Run as ..." and look at the list of accounts, there is no plain "Administrator" account listed. All I can do is choose a non-Adminstrator account which has been given Admin privileges.

How can I "Run as Administrator" from within XP home?

Anthony, I mislead you with advice that applies to Vista/Win7 only!

On XP, if you normally run as an Admin then run Logos4 setup, Sign in and complete downloading and indexing.

If you normally run as a Standard user, you still need to login to an Admin account and run Logos4 setup (to install the
system components). Do not Sign In but close the Sign In dialog, login as your regular
standard user, run Logos4 Setup again, Sign In, and complete the
installation (by downloading and indexing).

I haven't tried the latter method but I'm advised that's the way to do it by a Logos Tech.

EDIT: May not be needed now, but could be useful!

https://community.logos.com/discussion/comment/56736#Comment_56736

Hi Dave,

On XP, if you normally run as an Admin then run Logos4 setup, Sign in and complete downloading and indexing.

OK - that's the way I originally did the install (I'm always logged in as Admin and just did the install as myself). Thanks for the additional information about the steps required when you don't have Admin rights for your standard login (1-become admin, 2-setup up to the point of sign-in, 3-close, 4-login as non-Admin self, 5-run setup again). I've made a note of that for the future.

After I see an automatic update get initiated sometime down the line, I'll have some idea whether my reinstall somehow rectified the problem I was seeing. Until then, I'll just continue using the product.

Thanks again for the information - Tony

https://community.logos.com/discussion/comment/56743#Comment_56743

OK - so Logos 4 attempted to install an update and I see the failure as before. I've attached the log file.

DigitalLibraryInstall.log

https://community.logos.com/discussion/comment/62102#Comment_62102

OK - so Logos 4 attempted to install an update and I see the failure as before. I've attached the log file.

Hi we got your log, thanks. I will let you know once we narrow down why it's acting this way.

https://community.logos.com/discussion/comment/62102#Comment_62102

The problem is that some of the existing files can't be overwritten. This one, for example: \read\Logos4\System\es-MX\Logos4.resources.dll

You need to make sure you have r/w access to all the files in \read\Logos4\ before attempting the install.

https://community.logos.com/discussion/comment/62102#Comment_62102

Mark is right, right-click on the Logos4 folder and hit properties and ensure that you have all permissions set on this folder and the sub files and folders. It might be the case that you don't have the read and write but not modify property set

Albert Esselbrugge

https://community.logos.com/discussion/comment/62251#Comment_62251

Thanks for the responses, but checking the properties of the "es-MX" folder shows the "Read-only" box coloured in, and clearing it makes no difference. I can delete the file "Logos4.resources.dll", and paste it back without any issues. The file is not "read-only", but the installation of the update refuses to go any further.

https://community.logos.com/discussion/comment/62309#Comment_62309

Then can you delete the file and re-run the installation? Make sure logging remains turned on so we can diagnose further problems. Also, make sure you read my comments at the beginning of this thread which said "You should make sure you run Logos with the same privileges you had
when you installed it. If you install as admin, then run as a user you
can get problems."

Albert Esselbrugge

https://community.logos.com/discussion/comment/62314#Comment_62314

Hi Mark, I had already tried deleting the file, but no joy. Your last remark however did the trick. Running L4 as Administrator seems to have resolved the issue. I normally run my system as admin., but for some reason explicitly choosing run as admin resolved the update problem.

Thanks

https://community.logos.com/discussion/comment/62131#Comment_62131

The problem is that some of the existing files can't be overwritten. This one, for example: \read\Logos4\System\es-MX\Logos4.resources.dll

You need to make sure you have r/w access to all the files in \read\Logos4\ before attempting the install.

To summarize about this permission failure:

The directory is writable by me. I can create, edit, and delete files in \read\Logos4\System\es-MX without any problems.
The file is writable by me. When the update fails with this error, the original Logos4.resources.dll (from the previous version) has been successfully removed and a new copy of the file (with size zero) has been created. As a test, I opened the dll file in an editor and was able to inject ascii text (although I'm aware a DLL would typically be a binary file) into it and save it. So even the exact file it is complaining about is being created, although with size zero--and it is writable by me.
All this is as I would expect since I have Admin rights on the machine and originally installed Logos 4 "as me" without taking any special action other than inserting the CD and letting it run the install.

If I attempt to launch Logos 4 (the previous version before the update) as some other user, then it doesn't trigger the update and the previous version runs fine. If I launch Logos 4 as myself (without using "run as...") then it triggers the update and fails.

I am a software engineer by profession and generally familiar with file permissions and I don't think that has anything to do with it. It says "Error writing to file" and creates a DLL file with size zero. But the file and directory have complete write permission to me.

So I'm still at a loss to explain what's wrong with the update. If I uninstall Logos 4 and then reinstall it (so that it gets the latest version during the install), that works fine. Its only at the point of the subsequent automatic update where trouble begins.

https://community.logos.com/discussion/comment/62382#Comment_62382

I should also clarify that I'm running XP home edition on this particular machine, and as far as I can tell, there is no way to "run as... Administrator" since there is no "Administrator" account listed within XP home. (There are three accounts on the machine, all which have Administrator privileges, but none of which are the Administrator. I'm less familiar with XP home--usually using XP professional--so I'm not sure how or even if I can try to "Run as..." Administrator since there is no apparent Administrator account on the machine.)

https://community.logos.com/discussion/comment/62384#Comment_62384

I found out that Windows XP home edition disables the ability to login as
"Administrator" except when running in Safe Mode. (The idea is that
you only login as Administrator in Safe Mode to fix one of the other
accounts--which can have Administrator privileges--and then boot back to normal
mode.)

http://windowsxp.mvps.org/admins.htm

So I tried a couple of additional experiments:

Booted into safe mode, logged in as myself, and
launched Logos4.exe with "Run As... Administrator". This
doesn't work because of the following error:
"D:\read\Logos4\Logos4.exe The service cannot be started in
Safe Mode."
Booted into safe mode with networking, logged in as
Administrator, and launched Logos4.exe. After registering over the internet, it spends quite a while "downloading" but eventually fails with: "Logos 4 Bible Software encountered a problem and needs to close."

All this to say that my few attempts to try to run Logos4 (and especially the update) as Administrator under XP home have been futile. Then again, I have no real indication that this would fix the problem I'm seeing in the first place since I have Administrative rights and Logos4 was initially installed under my account directly from the crossgrade CD.

To summarize: the update always fails with a zero-sized DLL which is successfully created in the correct directory--both the directory and the file itself are writable by me. So the error writing the file must be due to something else. Since I'm unable to run Logos4 as Administrator under Safe Mode in XP home (and Administrator is unavailable outside of Safe Mode), I can't investigate whether running as the one-and-only Administrator would cause different behavior.

The question remains why the update reports an error writing the updated DLL, but successfully created the file itself (although empty) and is also successful at backing out the changes (deleting the zero-size DLL and restoring the original DLL) after reporting the error and I cancel the update.

https://community.logos.com/discussion/comment/62396#Comment_62396

All this to say that my few attempts to try to run Logos4 (and especially the update) as Administrator under XP home have been futile.

Is \ a fixed partition or a removable HDD? How did you create the \read folder (from your Admin account?)

The only way might be to re-install from your Admin account - but we can avoid downloading if you study Method 3 at http://wiki.logos.com/Quick_Installation_onto_multiple_computers (the "working installation" is your current installation!).

https://community.logos.com/discussion/comment/62435#Comment_62435

Anthony,

Sorry you're still having trouble with this. A couple of points:

Like you, I don't understand why Logos can write a zero-byte file, but then not add data to it.
However, Logos is designed to run on a per-user basis. It's designed to normally install without needing Administrator privileges (though the pre-requisites like .NET need those privileges, as do some fonts).
Logos therefore runs in a limited user mode, even if the user has administrative privileges (this is because the file is running from inside the user data folder, and Windows prevents files in there from having administrative privileges, unless you explicitly give it to them by choosing "Run as administrator".
Therefore, it's best to always install/run Logos using the same user account, avoiding "Run as" if at all possible. Logos can't overwrite files owned by other users.
If the permissions may have been compromised by doing this in the past, the best solution is to reclaim ownership of all the files in the Logos4 folder.

I hope this makes sense, and helps you solve the problem. Do let us know.

https://community.logos.com/discussion/comment/62467#Comment_62467

Thanks for the various suggestions.

\ is a fixed partition on a non-removable HDD. My machine initially came with both a C: and partition as purchased. I have several other bible study packages, including Logos 3, on the same partition under the same \read path (e.g., \read\libronix, \read\Logos4, \read\eSword, \read\SwordSearcher, \read\TheWord). None of the other programs have ever had problems creating files--nor do I when I manually do so.
My initial installation on this particular machine (and the reinstallation I did a while back) was simply done logged in as myself. As I've mentioned several times, on windows XP home you can't even login as Administrator except in safe mode which I haven't been using.
I've always run the program without using "Run as...", simply logged in as myself.
I've manually set "writable" permission on \read\Logos4 (and all subfiles and subfolders) which does not rectify the problem.
I've manually set the owner to myself (recursively) down this path.
Prior to the failed install, the original DLL which can't be successfully written is
\read\Logos4\System\es-MX\Logos4.resources.dll and it shows me as the owner and has a size of 9K. At the point of failure, it has been deleted and then recreated with size 0K, but the ownership still shows me as the owner. Plus, it does not have the "read-only" attribute set and is fully writable by me.

Henry Finkle

https://community.logos.com/discussion/comment/62740#Comment_62740

Anthony, how did you set the permissions for users in XP Home? The way I remembered it on my notebook is that I never saw any security settings on my version of xp home edition. To be able to make that tab visible, I had to download a utility from Microsoft.

If there is a "user group" with deny permissions, that will deny the administrators also. And maybe you might also need the "SYSTEM" account with all permissions set to allow also. A lot of times I saw installers fail if the "SYSTEM" account wasn't set on the folder or files that needed to be replaced.

https://community.logos.com/discussion/comment/63047#Comment_63047

Anthony,

I'm at a bit of a loss, I'm afraid. I'm going to take a wild guess, and if this doesn't work, suggest you contact support.

The wild guess is the the installation file doesn't like the folder called READ. Googling suggests that the first error that is being returned by the installer (2318) can sometimes occur when a reserved word is used in the pathname. I don't have any more details than that, and I'm not an MSI expert, I'm afraid. But it may be worth a try.

Mark

https://community.logos.com/discussion/comment/63652#Comment_63652

Problem solved!

I restarted in safe mode and logged in as Administrator and double-checked the permissions one more time. As I saw before, my normal login identity "tony", which has Admin rights had both ownership and full control permissions on every directory from all the way down to \read\Logos4\System\es-MX.

I repeated what I had done previously: set both Administrator and SYSTEM permission at \read and told it to propagate the permissions to child folders and files (and then watched as it took several minutes to visit all the folders and files setting the permissions). What was strange, though, was that when I browsed below \read again looking at security, neither Administrator nor SYSTEM appeared in the list of users. For some reason, these permissions were not propagated down as one would have expected.

I double-checked d:\read\Logos4 and saw something odd there that I hadn't noticed earlier:

There were two users listed in the security settings which did not make sense given the accounts on the machine: "SID 0" and "unknown user".
As with \read, neither SYSTEM nor Administrator permission had propagated to this folder.

I began to wonder whether these odd users were somehow interfering with the propagation of access permissions I had attempted earlier. So I deleted both of them from the list of users, went back to \read and then gave recursive permission for Administrator (user), SYSTEM (user) and Administrators (group) down the entire \read tree once again. This time, the permissions propagated all the way down \read\Logos4\System\es-MX and this fixed the problem.

So even though "tony" had the necessary permissions as an Admin, the other bogus users were somehow preventing Administrator, SYSTEM, and Administrators from being granted access each time I set these at a higher level and attempted to propagate the security settings downward.

And even though the update was running as "tony" with Admin permissions and complete control over the entire path down to \read\Logos4\System\es-MX\Logos4.resources.dll, something more was needed. I'm not sure if granting SYSTEM, Administrator, or Administrators permission was the key as I didn't do them one-at-a-time. But the main thing is it is fixed now.

I'm grateful for the patience and suggestions made by those who attempted to point me in the right direction to correct this glitch.

- Tony

https://community.logos.com/discussion/comment/63674#Comment_63674

I'm grateful for the patience and suggestions made by those who attempted to point me in the right direction to correct this glitch.

Glad it is fixed, Tony.

Enjoy the coming New Year!

https://community.logos.com/discussion/comment/63674#Comment_63674

Thanks for reporting on this issue Tony I'm sure other users may find it helpful, glad you got it working!

Stephen Miller

https://community.logos.com/discussion/comment/64678#Comment_64678

George and Tony,

I am one of the "other users". I have gone round and round with security access / user rights / adminstrator ..... I still can't get the update to get past the same hurdle as Tony.

Stephen Miller

Sydney, Australia

Stephen Miller

https://community.logos.com/discussion/comment/68972#Comment_68972

I now remember a change I made recently .... When I installed Windows 7 .... when windows started my User Icon popped up on the screen. This meant that Windows wouldn't start until I had clicked the icon.

Somehow I changed this so that Windows starts directly I switch on the computer.

I guess this has affected the user rights in my Logos 4 folder.

Stephen Miller

Sydney, Australia.

Stephen Miller

https://community.logos.com/discussion/comment/68992#Comment_68992

I switched off UAC, restarted Windows 7 and the update ran through.

Stephen Miller

Sydney, Australia