Error writing to file during beta upgrade

I've been getting this the last few beta's and just took a screenshot.

"error writing to file: c:\....\Libronix.DigitalLibrary.Resources.dll verify that you have access to that directory."

Clicking Retry brings up:

"Error writing to file: c:\...\Libronix.Utility.dll"

Interestingly enough, Logos did not automatically restart on this install either.

Install Log is attached. http://community.logos.com/cfs-file.ashx/__key/CommunityServer.Discussions.Components.Files/76/3750.Logos-Log-Files.zip

Find more posts tagged with

Comments

Graham Criddle

Hi Thomas

It looks as though you might be running into the "previously installed as administrator" issue as discussed in http://community.logos.com/forums/p/3539/37919.aspx and elsewhere

I see from Logos4Setup (line 4) that "process is elevated" which seems to confirm that this may be related to what you are seeing

Hope this helps (at least a little!)

Graham

TCBlack

https://community.logos.com/discussion/comment/268548#Comment_268548

No it's a bit different Graham. I've installed it and use it in an admin account.

The interesting tidbit is that after hitting retry, it works fine. So even without Logos running (it shuts down during the upgrade process) there must still be a file handle open on the file that prevents writing.

I suspect Logos isn't letting something loose when it shuts down.

TCBlack

...and I just realized this is not in the PCBeta forum.

Sigh. I'm going back to the rest of my vacation.

Graham Criddle

https://community.logos.com/discussion/comment/268601#Comment_268601

Hi Thomas

No it's a bit different Graham. I've installed it and use it in an admin account.

Yes - I thought you were aware of this issue, so would have been surprised - but thought it worth trying!

Sigh. I'm going back to the rest of my vacation.

Now that sounds a good plan. Enjoy!

Graham

Dave Hooton

https://community.logos.com/discussion/comment/268601#Comment_268601

No it's a bit different Graham. I've installed it and use it in an admin account.

Logos4 (and other programs) is run as a Standard user even in an Admin account. When you right click and choose "Run as administrator" the process will be run as "elevated" and now have your Admin privilege to access files. In this case Setup may have started normally and then "elevated" itself.

I suspect Logos isn't letting something loose when it shuts down.

I think your problem was one of access or privilege and Setup had to run itself as "elevated" because of the Retry attempts. I'm not fully convinced because it looks like it took 2 retries, so I would welcome some input from Logos.

TCBlack

https://community.logos.com/discussion/comment/268775#Comment_268775

After not having this issue over several beta's it's baaaack!

I click resume and it does, but there is something wrong and something different between 4.5 RC2 and whatever I just installed. (4.5a Beta 1 (v4.51.0.1895) )

Update logs: http://community.logos.com/cfs-file.ashx/__key/CommunityServer.Discussions.Components.Files/76/5850.DigitalLibraryInstall.zip

Dave Hooton

https://community.logos.com/discussion/comment/330311#Comment_330311

After not having this issue over several beta's it's baaaack!

I click resume and it does, but there is something wrong and something different between 4.5 RC2 and whatever I just installed. (4.5a Beta 1 (v4.51.0.1895) )

Update logs: http://community.logos.com/cfs-file.ashx/__key/CommunityServer.Discussions.Components.Files/76/5850.DigitalLibraryInstall.zip

Have you tried http://wiki.logos.com/Fixing_Logos_4_folder_Ownership or "run as administrator"?

TCBlack

https://community.logos.com/discussion/comment/330707#Comment_330707

Have you tried http://wiki.logos.com/Fixing_Logos_4_folder_Ownership or "run as administrator"?

Yes I actually did that several installs ago right after you came up with the procedure. I haven't had a problem until just now. which tells me that something very specific happened to flip ownership either during THIS install (4.5aB1) or the LAST install (4.5RC2).

TCBlack

https://community.logos.com/discussion/comment/330958#Comment_330958

**sigh** just did it again with the Logos4.exe file. Curiously I am the full owner of both the directory, and the executable.

Clicking retry made it work just fine. I think this is related in some way to another problem where Logos' threads are not completely dead or cleaned up before the update happens.

In another thread I was having an issue caused by Word and it's tie in via comlauncher with the smarttags. Word was not running in this instance (hadn't been all night).