4532.Logos Log Files.zip
We had an issue with our servers that has since been resolved.
https://status.faithlife.com/incidents/n07vrvlsvwbr
My Logos has been trying to Sign In for the past 40 minutes - so I still cannot sign in. I have even re-installed the program.
Try restarting your computer, then pressing and holding the control key when restarting Logos. Enter your proper credentials.
When you say that you "re-installed the program," do you mean engine only? (That would not have fixed anything in any case, but the answer could help us figure out your issue).
I have restarted Windows a number of times. I have also tried the control key (I have been trying to fix this for awhile so I have been reading and trying different solutions, this is my last effort - thinking it may be a Windows problem).
I Uninstalled the engine and re-installed it - but it did not change a thing, did the same as before. I thought there might be a corrupted file that could be replaced.
Best contact Faithlife Tech Support for this.
Thank you
Tech Support seems to take awhile - been 3 days and no answer. I need this software to work.
Thats a long time to be hanging on the phone Trevor - did you ring the right number?
I am in Australia so I emailed the log files to tech support ....
Try Skype - it's cheaper; and the time difference puts them 5hrs ahead of Oz (one day behind)
Still no fix - It seems they do not have email support. Sent an email with the problem (a number of times now), logs etc, and just get an email back with support and contact details. I told them I was from Australia.
I'm sorry for any confusion. Looking at your account it looks like we did respond to your email, it may have been caught by your spam filter.
Based on the logs you emailed in, it looks like you may have an issue with the .Net Framework. Unfortunately this can't just be uninstalled and reinstalled on Windows 10. This tool may help repair Microsoft's .Net Framework https://www.microsoft.com/en-us/download/details.aspx?id=30135.
If you are still having the issue I would recommend contacting either the computer's manufacturer or Microsoft for assistance in fixing the .Net issue.
Thank You
