Interlinear update problem

The recent 1gb update downloaded, but had trouble installing. It said something like "Make sure you have authority to access..." somethingrather (sorry I didn't memorize it, I would have had I known it would be a problem). So I had to cancel the install, which I didn't think would be a problem.

But now this is all I can see for my Bibles:

It's the same for NASB and I would assume all my Bibles that are reverse interlinear.

Is there a way to start the 1gb install again?

Find more posts tagged with

Comments

MJ. Smith

Update resources should restart a download that failed. But have you checked your visual filters?

Jeremy

https://community.logos.com/discussion/comment/124015#Comment_124015

You can't read that?

John Bowling

https://community.logos.com/discussion/comment/124015#Comment_124015

MJ:

Thanks, I haven't tried that yet because the download was successful. It was the install that got botched.

Jeremy:

Hardy har har har.

Dave Hooton

But now this is all I can see for my Bibles:

John

This is a beta problem so you should be posting to the PC Beta forum.

Check the settings of your Display menu in the header (ensure "Surface" is checked).

John Bowling

https://community.logos.com/discussion/comment/124020#Comment_124020

Dave, I did post this in beta forum. It says it's in beta forum, I think.

And thanks for the suggestion. However, it didn't work. And the menu to select "show surface text" has chinese characters as well as others.

Darren Paul Wright

https://community.logos.com/discussion/comment/124023#Comment_124023

I just moved it.

Dave Hooton

https://community.logos.com/discussion/comment/124018#Comment_124018

Thanks, I haven't tried that yet because the download was successful. It was the install that got botched.

In Vista/7 try running L4 with Admin Privilege (right click the L4 icon and "run as administrator").

In XP you may have to temporarily set the user account as an Administrator one.

John Bowling

https://community.logos.com/discussion/comment/124025#Comment_124025

In Vista/7 try running L4 with Admin Privilege (right click the L4 icon and "run as administrator").

Thanks. I wasn't running it as admin at the time I tried to download and install it. But right now it seems to be too late for that, I did the "Update now" command and it said nothing was available (I tried the "Update Resources" command too).

Dave Hooton

https://community.logos.com/discussion/comment/124028#Comment_124028

I wasn't running it as admin at the time I tried to download and install it.

That's not normally needed. Have you had problems with previous Beta updates or downloading previous beta resources?

For now, turn on permanent logging as per Diagnostic Logging, run L4 normally and upload all the logs (see Uploading Logs).

John Bowling

https://community.logos.com/discussion/comment/124034#Comment_124034

No. I've never had a problem with a previous Beta update.

Here is the only Log I have:

Program Version: 4.0c Beta 5 (4.03.3.8778)

Windows Version: 6.1.7600.0

Time: 2010-04-29 20:51:11

Installed memory: 2,815 MB

Install path: C:\Users\JonathanB\AppData\Local\Logos4\System\Logos4.exe

Data path: C:\Users\JonathanB\AppData\Local\Logos4\Data\obhvlxc3.pe0

Free disk space: 117,300 MB

Temp path: C:\Users\JonathanB\AppData\Local\Temp\

Free temp space: 117,300 MB

Error ID: 8947

Error detail: InvalidOperationException: The Writer is closed or in error state.

System.InvalidOperationException: The Writer is closed or in error state.

at System.Xml.XmlWellFormedWriter.AdvanceState(Token token)

at System.Xml.XmlWellFormedWriter.WriteEndElement()

at Libronix.Utility.Scope.Dispose()

at Libronix.DigitalLibrary.PreferencesManager.CommitPreferences[T](String strName, T preferences)

at Libronix.DigitalLibrary.PreferencesBase.Commit()

at LDLS4.PanelViewModel.SavePreferences()

at LDLS4.Panels.ResourcePanel.ResourceViewModelBase.DestroyDisplay(Boolean bDeferDisposal)

at LDLS4.Panels.ResourcePanel.ResourceViewModelBase.Dispose(Boolean disposing)

at LDLS4.Panels.ResourcePanel.ResourceViewModel.Dispose(Boolean disposing)

at Libronix.Utility.ViewModels.TiledFramePanelSource.DisposePanels(IEnumerable`1 seqPanels)

at LDLS4.AppModel.ProcessAppliedLayoutSnapshot(LayoutSnapshot snapshot)

at LDLS4.AppModel.PanelSource_LayoutManipulated(Object sender, EventArgs e)

at System.EventHandler.Invoke(Object sender, EventArgs e)

at Libronix.Utility.EventHandlerUtility.Raise(EventHandler fn, Object sender)

at Libronix.Utility.ViewModels.TiledFramePanelSource.<StartLayoutTransaction>b__2()

at Libronix.Utility.Scope.Dispose()

at LDLS4.MainWindow.MainWindow_CloseTiledFrameTileOrPanel(Object sender, ExecutedRoutedEventArgs e)

at System.Windows.Input.CommandBinding.OnExecuted(Object sender, ExecutedRoutedEventArgs e)

at System.Windows.Input.CommandManager.ExecuteCommandBinding(Object sender, ExecutedRoutedEventArgs e, CommandBinding commandBinding)

at System.Windows.Input.CommandManager.FindCommandBinding(CommandBindingCollection commandBindings, Object sender, RoutedEventArgs e, ICommand command, Boolean execute)

at System.Windows.Input.CommandManager.FindCommandBinding(Object sender, RoutedEventArgs e, ICommand command, Boolean execute)

at System.Windows.Input.CommandManager.OnExecuted(Object sender, ExecutedRoutedEventArgs e)

at System.Windows.UIElement.OnExecutedThunk(Object sender, ExecutedRoutedEventArgs e)

at System.Windows.Input.ExecutedRoutedEventArgs.InvokeEventHandler(Delegate genericHandler, Object target)

at System.Windows.RoutedEventArgs.InvokeHandler(Delegate handler, Object target)

at System.Windows.RoutedEventHandlerInfo.InvokeHandler(Object target, RoutedEventArgs routedEventArgs)

at System.Windows.EventRoute.InvokeHandlersImpl(Object source, RoutedEventArgs args, Boolean reRaised)

at System.Windows.UIElement.RaiseEventImpl(DependencyObject sender, RoutedEventArgs args)

at System.Windows.UIElement.RaiseEvent(RoutedEventArgs args, Boolean trusted)

at System.Windows.Input.RoutedCommand.ExecuteImpl(Object parameter, IInputElement target, Boolean userInitiated)

at System.Windows.Input.RoutedCommand.Execute(Object parameter, IInputElement target)

at Libronix.Utility.Windows.Controls.TiledFrameTabControl.TiledFrameTabControl_Executed(Object sender, ExecutedRoutedEventArgs e)

at System.Windows.Input.ExecutedRoutedEventArgs.InvokeEventHandler(Delegate genericHandler, Object target)

at System.Windows.RoutedEventArgs.InvokeHandler(Delegate handler, Object target)

at System.Windows.RoutedEventHandlerInfo.InvokeHandler(Object target, RoutedEventArgs routedEventArgs)

at System.Windows.EventRoute.InvokeHandlersImpl(Object source, RoutedEventArgs args, Boolean reRaised)

at System.Windows.UIElement.RaiseEventImpl(DependencyObject sender, RoutedEventArgs args)

at System.Windows.UIElement.RaiseEvent(RoutedEventArgs args, Boolean trusted)

at System.Windows.Input.RoutedCommand.ExecuteImpl(Object parameter, IInputElement target, Boolean userInitiated)

at System.Windows.Input.RoutedCommand.ExecuteCore(Object parameter, IInputElement target, Boolean userInitiated)

at MS.Internal.Commands.CommandHelpers.CriticalExecuteCommandSource(ICommandSource commandSource, Boolean userInitiated)

at System.Windows.Controls.Primitives.ButtonBase.OnClick()

at System.Windows.Controls.Button.OnClick()

at System.Windows.Controls.Primitives.ButtonBase.OnMouseLeftButtonUp(MouseButtonEventArgs e)

at System.Windows.UIElement.OnMouseLeftButtonUpThunk(Object sender, MouseButtonEventArgs e)

at System.Windows.Input.MouseButtonEventArgs.InvokeEventHandler(Delegate genericHandler, Object genericTarget)

at System.Windows.RoutedEventArgs.InvokeHandler(Delegate handler, Object target)

at System.Windows.RoutedEventHandlerInfo.InvokeHandler(Object target, RoutedEventArgs routedEventArgs)

at System.Windows.EventRoute.InvokeHandlersImpl(Object source, RoutedEventArgs args, Boolean reRaised)

at System.Windows.UIElement.ReRaiseEventAs(DependencyObject sender, RoutedEventArgs args, RoutedEvent newEvent)

at System.Windows.UIElement.CrackMouseButtonEventAndReRaiseEvent(DependencyObject sender, MouseButtonEventArgs e)

at System.Windows.UIElement.OnMouseUpThunk(Object sender, MouseButtonEventArgs e)

at System.Windows.Input.MouseButtonEventArgs.InvokeEventHandler(Delegate genericHandler, Object genericTarget)

at System.Windows.RoutedEventArgs.InvokeHandler(Delegate handler, Object target)

at System.Windows.RoutedEventHandlerInfo.InvokeHandler(Object target, RoutedEventArgs routedEventArgs)

at System.Windows.EventRoute.InvokeHandlersImpl(Object source, RoutedEventArgs args, Boolean reRaised)

at System.Windows.UIElement.RaiseEventImpl(DependencyObject sender, RoutedEventArgs args)

at System.Windows.UIElement.RaiseEvent(RoutedEventArgs args, Boolean trusted)

at System.Windows.Input.InputManager.ProcessStagingArea()

at System.Windows.Input.InputManager.ProcessInput(InputEventArgs input)

at System.Windows.Input.InputProviderSite.ReportInput(InputReport inputReport)

at System.Windows.Interop.HwndMouseInputProvider.ReportInput(IntPtr hwnd, InputMode mode, Int32 timestamp, RawMouseActions actions, Int32 x, Int32 y, Int32 wheel)

at System.Windows.Interop.HwndMouseInputProvider.FilterMessage(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)

at System.Windows.Interop.HwndSource.InputFilterMessage(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)

at MS.Win32.HwndWrapper.WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)

at MS.Win32.HwndSubclass.DispatcherCallbackOperation(Object o)

at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Boolean isSingleParameter)

at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Boolean isSingleParameter, Delegate catchHandler)

at System.Windows.Threading.Dispatcher.WrappedInvoke(Delegate callback, Object args, Boolean isSingleParameter, Delegate catchHandler)

at System.Windows.Threading.Dispatcher.InvokeImpl(DispatcherPriority priority, TimeSpan timeout, Delegate method, Object args, Boolean isSingleParameter)

at System.Windows.Threading.Dispatcher.Invoke(DispatcherPriority priority, Delegate method, Object arg)

at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam)

at MS.Win32.UnsafeNativeMethods.DispatchMessage(MSG& msg)

at System.Windows.Threading.Dispatcher.PushFrameImpl(DispatcherFrame frame)

at System.Windows.Threading.Dispatcher.PushFrame(DispatcherFrame frame)

at System.Windows.Threading.Dispatcher.Run()

at System.Windows.Application.RunDispatcher(Object ignore)

at System.Windows.Application.RunInternal(Window window)

at System.Windows.Application.Run(Window window)

at System.Windows.Application.Run()

at LDLS4.OurApp.InitializeAndRun(ReadOnlyCollection`1 listArgs, SingleInstanceManager sim)

at LDLS4.OurApp.Main(String[] astrArgs)

Bradley Grainger (Logos)

https://community.logos.com/discussion/comment/124023#Comment_124023

And thanks for the suggestion. However, it didn't work. And the menu to select "show surface text" has chinese characters as well as others.

Your menu should look like the picture I've attached to this message. Please attach a screenshot of your display so we can see where/how it is different.

Dave Hooton

https://community.logos.com/discussion/comment/124037#Comment_124037

Here is the only Log I have:

John we need current logs. As I indicated above, set up permanent logging and run L4.

Please don't paste them into your post.

John Bowling

https://community.logos.com/discussion/comment/124078#Comment_124078

Bradley:

Dave:

Sorry, I thought the log was current. I see that it says Beta 5, but the date is current (yesterday's date, when I had the problem). Looking at my "About Logos Software" right now, it does in fact say that I have Beta 5, even though I have the update channel set to Beta and it should have been updating automatically. I have logos installed on my other computer, with the same settings, and it reads Beta 7.

Should I open another post following the BUG: guidelines then?

(I ran the update on my other computer and it worked fine.)

Melissa Snyder

https://community.logos.com/discussion/comment/124144#Comment_124144

Sorry, I thought the log was current. I see that it says Beta 5, but the date is current (yesterday's date, when I had the problem). Looking at my "About Logos Software" right now, it does in fact say that I have Beta 5, even though I have the update channel set to Beta and it should have been updating automatically. I have logos installed on my other computer, with the same settings, and it reads Beta 7.

Should I open another post following the BUG: guidelines then?

Close Logos 4 and run the update script to update to Beta 7: http://downloads.logos.com/LBS4/InstallerBeta/Logos4Setup.exe. After the update has been installed and Logos restarted, open the interlinear Bibles again to check the display.

John Bowling

https://community.logos.com/discussion/comment/124192#Comment_124192

I'm receiving the same error message that I did when trying to install the 1gb resource update:

"Error writing to file:

c:\users\JonathanB\AppData\Local\Logos4\System\sv-SE\Libronix.DigitalLibrary.Controls.Resources.dll. Verify that you have access to that directory."

It then gives me the option to retry or cancel. Clicking retry brings up the same message. Clicking cancel is what caused the Bibles to get messed up last time.

Melissa Snyder

https://community.logos.com/discussion/comment/124206#Comment_124206

I've submitted this information to a developer.

Bryan Albert

https://community.logos.com/discussion/comment/124206#Comment_124206

I'm receiving the same error message that I did when trying to install the 1gb resource update:

"Error writing to file:

c:\users\JonathanB\AppData\Local\Logos4\System\sv-SE\Libronix.DigitalLibrary.Controls.Resources.dll. Verify that you have access to that directory."

It then gives me the option to retry or cancel. Clicking retry brings up the same message. Clicking cancel is what caused the Bibles to get messed up last time.

John,

The error you're describing is issued by Windows Installer when you try to install Beta 7. Here's what's going on: when you run Logos4Setup.exe from the link that Melissa provided, it downloads an installation file named Logos4.msi, which contains everything needed to install Beta 7, then launches Microsoft's Windows Installer program to install the file. Windows Installer is attempting to update a file on your system, but for some reason it can't write to the file when it should be able to. We've seen this problem before and have written code that should fix it, though it appears that, at least in your case, that code isn't working.

When Logos4Setup.exe runs, it writes log files to your hard disk which contain descriptive information about what's going on and what's going wrong. It would be really useful to see your log files. If you have enabled diagnostic logging already, Logos4Setup.exe will write log files to your Documents folder's "Logos Log Files" folder. If you don't have diagnostic logging enabled, Logos4Setup.exe will write log files to the "Logos Log Files" folder in your Temp folder. You should see this folder in C:\Users\JonathanB\AppData\Local\Temp.

Please run the Beta 7 setup from http://downloads.logos.com/LBS4/InstallerBeta/Logos4Setup.exe so that it gives the error. Click Cancel to cancel the setup and locate the "Logos Log Files" folder. Find the logos4setup.log and DigitalLibraryInstall.log files in the folder, attach them to a response on this forum thread and I'll check them out. (For instructions on uploading files to a forum post, see http://wiki.logos.com/Uploading_Logs.)

Thanks!

Bryan

John Bowling

https://community.logos.com/discussion/comment/124319#Comment_124319

Thanks.

6253.logos4setup (2).log

8625.DigitalLibraryInstall.log

Bryan Albert

https://community.logos.com/discussion/comment/124327#Comment_124327

John,

I've checked out your log files. Unfortunately, I'm afraid I'll need more information to figure out where the problem lies. Please save the attached file to your Logos 4 folder, which is C:\Users\JonathanB\AppData\Local\Logos4, and rename it to ReportFolderPermissions.bat. When you run the file, it will create a file named Logos4Permissions.txt in your Logos4 folder which will contain the file permissions of all the files and folders in the Logos 4 folder. Post that file back here and I'll look at it.

Thanks,

Bryan

8524.ReportFolderPermissions.bat.txt