4.1 Beta 2 Error during install

Beta 2 installed and wanted a reboot. After the reboot, an error occurred but I was not able to capture it before it disappeared into the ether.

Are there log files somewhere I should look for? Logos 4 booted OK and the help about shows beta 2.

Regards,

Clinton

Find more posts tagged with

Comments

Rosie Perera

When you say it wanted a reboot do you mean it wanted to reboot your computer or just to restart Logos?

Logos does leave log files around (Logos4.log and others) if you enable Diagnostic Logging. If it crashes (which it doesn't seem to have done in your case), it will leave a file called Logos4Crash.txt even if you don't have diagnostic logging enabled. You'll find these files in the folder Logos Log Files inside your Documents folder.

Now that Beta 2 is booted and running fine, have you had any other problems?

If it was some Windows error that flashed by quickly, you can see it by running Event Viewer. Poke around through the different categories of logs and see if you find anything looking like an Error.

Clinton Thomas

https://community.logos.com/discussion/comment/151548#Comment_151548

1) Reboot.

2) Running fine, no other problems

3) Poked around in the event viewer, found the reboot and looked at what was going on, but there were no obvious errors or anything that seemed odd. I did notice the indexer start up. Maybe it was the indexer failing during the cleanup after the reboot due to a locked file or something.

Dave Hooton

https://community.logos.com/discussion/comment/151750#Comment_151750

I did notice the indexer start up. Maybe it was the indexer failing during the cleanup after the reboot due to a locked file or something.

Have you checked your temp folder for Logos Log Files?

Clinton Thomas

https://community.logos.com/discussion/comment/151960#Comment_151960

Have you checked your temp folder for Logos Log Files?

I have now [:)] The install went fine and the system wanted the reboot. After the reboot, the setuplog shows that the error was when the program attempted to launch logos4 and that requires admin level so it failed. It seems that the error was that the program just couldn't autostart logos 4.

I have attached the logs if you or someone from logos wants to take a look. This error is the last line of the logos4setup.log.

Thanks,

Clinton

7510.logos4setup.log

6433.DigitalLibraryInstall.log

Melissa Snyder

https://community.logos.com/discussion/comment/152013#Comment_152013

I have now The install went fine and the system wanted the reboot. After the reboot, the setuplog shows that the error was when the program attempted to launch logos4 and that requires admin level so it failed. It seems that the error was that the program just couldn't autostart logos 4.

I have attached the logs if you or someone from logos wants to take a look. This error is the last line of the logos4setup.log.

We'll review the logs. Thanks.

Bryan Albert

https://community.logos.com/discussion/comment/152013#Comment_152013

Have you checked your temp folder for Logos Log Files?

I have now The install went fine and the system wanted the reboot. After the reboot, the setuplog shows that the error was when the program attempted to launch logos4 and that requires admin level so it failed. It seems that the error was that the program just couldn't autostart logos 4.

7510.logos4setup.log

6433.DigitalLibraryInstall.log

Clinton,

Thanks for the log files. For a simple upgrade like this one, Windows Installer generally does not have reason to need a reboot. (When it does, it's generally only when installing Windows system files. We haven't updated the prerequisites installer file in a while, so your system shouldn't have needed to update any system files, unless maybe you were upgrading from a pretty old version, 4.0c Beta 5 or older. It doesn't look like this was the case.)

It looks like there's something fishy going on that left one of the Logos 4 files locked when we tried to update it. I'm assuming that when you ran Logos 4, it told you that updates were available, and when you chose to install them, it shut down Logos 4 automatically--though it looks like one file was somehow left locked. During the update, did you happen to see a dialog that would have said something like, "The file C:\Users\Clinton\AppData\Local\Logos4\System\LDLS3.dll is being held in use. Close that application and retry."? It's quite likely that that dialog would not have been displayed.

In any case, it's also quite odd that Logos4Setup.exe, which ran after the reboot with the sole purpose of launching Logos 4 for you, could not launch Logos 4. Do you have your Logos 4 shortcut configured to Run as administrator? When you launch Logos 4 manually (which works, right--beta 2?), do you see a UAC dialog (requesting elevation)?

Let's see what happens with the Beta 3 update next week.

Bryan

Clinton Thomas

https://community.logos.com/discussion/comment/152225#Comment_152225

Hi Bryan,

Thanks for the feedback. I too was surprised to see that it wanted a reboot of the system. Here are the answers to your questions.... No, Yes, Yes, and Yes.

details below.

During the update, did you happen to see a dialog that would have said something like, "The file C:\Users\Clinton\AppData\Local\Logos4\System\LDLS3.dll is being held in use. Close that application and retry."? It's quite likely that that dialog would not have been displayed.

No, there was nothing displayed during the update that I saw. It was a longer update than some of the others and I might have lost interest. However for logos, I tend to shut other programs down before I run the upgrade. I can't remember if I was as diligent this time.

Do you have your Logos 4 shortcut configured to Run as administrator?

Yes I do, I read on one of the threads that this might help a little with performance.

When you launch Logos 4 manually (which works, right--beta 2?), do you see a UAC dialog (requesting elevation)?

Yes it works, and Yes I do get the UAC dialog.

Regards,

Clinton

Bryan Albert

https://community.logos.com/discussion/comment/152305#Comment_152305

Do you have your Logos 4 shortcut configured to Run as administrator?

Yes I do, I read on one of the threads that this might help a little with performance.

Well... that explains part of the problem at least. Running Logos 4 as administrator is certainly not a supported scenario and is discouraged, maybe even highly discouraged. For one thing, Logos components are designed to restart themselves as necessary after a reboot, and when they do that, they aren't started elevated. This can make them incompatible with the data they were working with before the restart, which could lead to a number of different errors. You ran into one instance of that problem. I'm not aware of any reasons that running as administrator might improve performance.

As for the initial problem of the locked file, I'm not sure if that's related to running the install elevated or not...

When you upgrade to Beta 3, if Logos4Setup again asks you to reboot, please postpone the reboot and find the two log files again and post them here. They may have more information, and one of them is overwritten the second time Logos4Setup.exe runs.

Thanks,

Bryan

Clinton Thomas

https://community.logos.com/discussion/comment/152329#Comment_152329

Hi Bryan,

Will do.

I have also turned off the UAC thing based on your reply and the posting on the wiki saying the same thing.

Regards,

Clinton