Logos 4 won't log into Logos anymore!

2»

Comments

  • Cindy said:

    OK, I did what you said, here's the ones from today.

    Logos4.log file shows 4.6c SR-7 experiencing login error with server certificate mentioned in message:

    2017-03-03 10:54:19.0582 4 Error WebServiceClient CommunicationException for Boolean: System.ServiceModel.CommunicationException: An error occurred while making the HTTP request to https://services.logos.com/v1/AuthenticationService.svc. This could be due to the fact that the server certificate is not configured properly with HTTP.SYS in the HTTPS case. This could also be caused by a mismatch of the security binding between the client and the server. ---> System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a send. ---> System.IO.IOException: Received an unexpected EOF or 0 bytes from the transport stream. ~ at System.Net.TlsStream.EndWrite(IAsyncResult asyncResult) ~ at System.Net.PooledStream.EndWrite(IAsyncResult asyncResult) ~ at System.Net.ConnectStream.WriteHeadersCallback(IAsyncResult ar) ~ --- End of inner exception stack trace --- ~ at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult) ~ at System.ServiceModel.Channels.HttpChannelFactory.HttpRequestChannel.HttpChannelAsyncRequest.CompleteGetResponse(IAsyncResult result) ~ --- End of inner exception stack trace --- ~ ~Server stack trace: ~ at System.ServiceModel.AsyncResult.End[TAsyncResult](IAsyncResult result) ~ at System.ServiceModel.Channels.ServiceChannel.SendAsyncResult.End(SendAsyncResult result) ~ at System.ServiceModel.Channels.ServiceChannel.EndCall(String action, Object[] outs, IAsyncResult result) ~ at System.ServiceModel.Channels.ServiceChannelProxy.InvokeEndService(IMethodCallMessage methodCall, ProxyOperationRuntime operation) ~ at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message) ~ ~Exception rethrown at [0]: ~ at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg) ~ at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) ~ at LDLS4.WebServices.AuthenticationServices.AuthenticationService.EndIsLoggedIn(IAsyncResult result) ~ at LDLS4.WebServices.AuthenticationServices.AuthenticationServiceClient.EndIsLoggedIn(IAsyncResult result) ~ at Libronix.Utility.Threading.AsyncMethodAsyncAction`1.Callback(IAsyncResult ar) ~ at Libronix.Utility.Threading.AsyncMethodAsyncAction`1.get_Result() ~ at LDLS4.WebServiceClient.GetResult[T](AsyncMethodAsyncAction`1 action)

    Keep Smiling [:)]

  • Jose said:

    yes I heard recently Logos provides free version of Logos 6 and Logos 7. Does it have all the features as logos 4?

    All Logos 4 features work in Logos 6 and Logos 7. Thankful for many more new features/datasets. Thankful for Logos Now and Verbum Now.

    Thankful for $ 0.00 packages => Basic and => Verbum Basic that include Logos 7 and Verbum 7 software engine update for use with newer Windows (and Mac's running OS X 10 or newer). Basic packages also include "access-only" resources that enable many Bible study features, However, Basic packages have no effect on dynamic pricing for future upgrades since "access-only" resources are not owned (so they appear in library with temporary license).

    Microsoft no longer supports XP for consumers and also choose to not support .NET Framework 4.5 on XP plus did not implement security protocol updates on XP. Hence, newer Logos 7 and Verbum 7 need newer Windows (or macOS / OS X).

    Jose said:

    My biggest complain is why the software even if is a logos 4 version cannot be fully installed OFFLINE,

    For Logos 4 and newer (e.g. Verbum), Faithlife developers choose to implement online server connection being needed for resource licensing (seem to remember Logos 4 having offline option with customer service involvement for awhile). Since implementing online connection for resource licenses, worldwide trend has been more online connectivity, especially with smart phones (so Logos 4 offline installation product was discontinued years ago).

    Due to security certificate issues, appears online login using XP is no longer feasible.

    FYI: Microcenter has refurbished deals so could upgrade to refurbished computer with newer operating system (Windows or OS X) for under $ 200.

    Keep Smiling [:)]

  • Dave Hooton
    Dave Hooton MVP Posts: 35,917

    Cindy said:

     It serves no purpose. Instead, since many of us are having this problem, I'll pray that the Lord will help us to help each other fix it and that He will soften hearts at logos so that they also might help us.  

    I hope others will join me in prayer.  I know the Lord will hear and act on our behalf.

    I think it is time to move on, allowing that God knows your needs and is big enough to act on them in other ways. Practically, what you want is a Windows 7 computer with Service Pack 1, or even the current Windows 10 because your Logos account will allow you to restore your library on these systems. This is my prayer, because whilst I might be able to get you working offline in XP I need to have access to your computer and your Logos account!

    Dave
    ===

    Windows 11 & Android 13

  • Jose
    Jose Member Posts: 16

    thanks brother (smiling for Jesus), I already have plenty of computers with all kinds of OSs I happen to use XP because I am transitioning slowly, moving all the applications I can and trying to make work in what will become my main computer with windows 7, however what will happen when Windows 7 is not longer supported? I just find it crazy I can't have at least an offline choice. but is fine. thanks for all your help and patience. Smiling for Jesus, you've been very kind and helpful. God bless you. Cindy my prayer will be for you also. I thank God I have Logos 6 on WIndows 7 in another computer and I am currently have to switch to that other computer and keep transitioning until it becomes my main computer. I am sorry that no one could really help you. 

  • Jose said:

    ... however what will happen when Windows 7 is not longer supported?

    Current minimum Windows version for .NET Framework 4.6.2 is Windows 7 SP1, which is the same as Logos 7 and Verbum 7. Noticed .NET Framework 4.6.2 is not installable on Windows 8 => https://msdn.microsoft.com/en-us/library/bb822049.aspx

    Microsoft end of extended support for Windows 7 is 14 Jan 2020 => https://support.microsoft.com/en-us/help/13853/windows-lifecycle-fact-sheet Windows 8 needs free Windows 8.1 Update for extended support until 10 Jan 2023. After 11 Apr 2017 end of extended support for Vista, Microsoft will be supporting three operating systems: Windows 7 SP1 , Windows 8.1 Update , and Windows 10 until 14 Jan 2020.

    Lifecycle Policy FAQ - Microsoft .NET Framework => https://support.microsoft.com/en-us/help/17455 includes

    .NET Framework 4.6.2">

    Support for .NET 4.6.2 follows the Lifecycle Policy of the parent operating system. It is supported as a Windows component on the latest required operating system update for Windows 7 SP1, Windows Server 2008 R2 SP1, Windows 8.1 Update, Windows Server 2012, and Windows Server 2012 R2. .NET 4.6.2 is also supported on Windows 10 Anniversary Update (Version 1607) and Windows Server 2016 operating systems. We recommend customers upgrade to .NET Framework 4.6.2 to receive the highest level of performance, reliability, and security.

    Logos Wiki => Mac Release Notes and History shows Logos 7 release on Mon 22 Aug 2016, which was preceded by Logos 6 on Mon 27 Oct 2014 and Logos 5 on Thu 1 Nov 2012. Uninformed speculation for Logos 8 and Verbum 8 would be near Labor Day in 2018 for Back to School plus Fall introductory promotion, which should have the same Windows system requirements as Logos 7 while may need newer macOS. If Microsoft releases a newer .NET Framework in 2020 after Windows 7 end of support plus Faithlife code migration, then can speculate Logos 9 and Verbum 9 release near Labor Day in 2020 needing newer Windows 8.1 Update or Windows 10 along with needing newer macOS (otherwise Windows 7 SP 1 could be viable even though no longer supported).

    Note: Microsoft ended all XP support on 8 Apr 2014 => https://www.microsoft.com/en-us/WindowsForBusiness/end-of-xp-support

    FYI: Visual Studio 2017 launch date is Tue 7 Mar 2017 => https://launch.visualstudio.com/

    Keep Smiling [:)]

  • Cindy
    Cindy Member Posts: 138

    Yes, that's what I said it was doing. I said it can't log onto Logos.  So what can be done?

  • Cindy said:

    Yes, that's what I said it was doing. I said it can't log onto Logos.  So what can be done?

    Recommend replacing dying computer with one that has a minimum of Windows 7 SP1 or OS X 10.10 so can use Logos 7 or Verbum 7.

    Microcenter has a number of refurbished computers under $ 200 that would be usable. Recommend replacing hard drive with SSD for noticeably faster responsiveness. For 64 bit operating systems, also suggest 8 GB of more RAM.

    Logos 7 thread => Can't Log onto Logos After downloading Logos 7 includes replies by Mark Barnes.

    Thread => Important Announcement for Windows XP, Vista, OS X 10.5, 10.6, 10.7 users included notice:

    There will be no further updates to Logos 4.6c on Windows XP/OS X 10.5 after that date.¹ Your copy of Logos will not be disabled. Your existing install will continue to run with the resources you already have. However, new resources purchased from logos.com may not be readable by Logos 4.6c. Your documents and settings may eventually stop syncing to newer versions of Logos. Web services that are only used by Logos 4.6c may be discontinued without notice. Eventually, you may have to permanently "Work Offline" to keep using the software.

    Thread => Logos 4/Windows XP remote certificate issue? has many replies by Bradley Grainger with last one being:

    Cross-referencing https://www.ssllabs.com/ssltest/analyze.html?d=services.logos.com with https://msdn.microsoft.com/en-us/library/windows/desktop/aa380512.aspx makes me think that there is no TLS 1.0 cipher suite that the server and Windows XP can agree on using. (And according to https://www.ssllabs.com/ssltest/viewClient.html?name=IE&version=8&platform=XP almost all the XP cipher suites are regarded as insecure; the two that aren't also aren't supported by our server.) This would mean that a secure connection can't be established, so logging in would fail.

     

    I'm not aware of any TLS cipher configuration changes that have happened recently on our end, so it's not immediately obvious to me what might have changed here. 

    Hence, time has arrived where existing Logos 4 installations only work offline. Windows XP cannot negotiate secure connection with Faithlife for login.

    Keep Smiling [:)]