I am dead in the water - both systems I have crash immmediately on startup every time. Attached are logs from one of the systems. HELP!!
8407.Logos4.log
4452.Logos4Crash.txt
1134.Logos4Error.log
WARNING: BEWARE WITH BETA 3!!!!
I tried signing on with a Blank layout (I normally start with Home Page), and it came up fine. I brought up the Library, I clicked Resources because I have resource to download, and it crashed again.
I started in Offline mode, I was able to bring up library, go to Collections and bring up a collection definition, bring up a Bible, click on about 3 resource from library to open them, all fine. I was beginning to think it was connected to the network/servers. Then I clicked and opened a layout, CRASH.
Apologies: my initial launch of Logos 4.5b Beta 3 is OK (Home Page appeared); currently waiting for indexing to complete.
Noticed my Logos4error.log on Mac and PC has messages for http://internal.services.logos.com
Keep Smiling [:)]
Do you happen to use OpenDNS.com's DNS servers?
If so, try switching back to your ISP's servers, or Google's public DNS (8.8.8.8) and see if that works around the problem.
Do you happen to use OpenDNS.com's DNS servers? If so, try switching back to your ISP's servers, or Google's public DNS (8.8.8.8) and see if that works around the problem.
Bradley, I'm a college student that uses campus internet. I don't know what they use. But check this out. Beta 2 ran smooth all day. Beta 3 is crashing over and over right after I updated to it. Doesn't matter now, I' already deleted and in the process of reinstalling a stable version. I'm busy with homework tonight and Beta 3 put a stop to it.
Doesn't matter now, I' already deleted and in the process of reinstalling a stable version.
As per the beta testing information page, beta releases can't be downgraded to a stable release. (It may work, or it may crash at startup.)
If it doesn't work, and you have to re-upgrade to Beta 3, try following these instructions to configure your computer to use Google's DNS servers: http://code.google.com/speed/public-dns/docs/using.html, or these instructions with pictures: http://techie-buzz.com/how-to/google-public-dns-on-win7-and-winxp.html
(Since I'm not on your campus network, I can't say for sure that it'll fix the problem, but I think that it may work around it until Beta 4 is released.)
A final alternative is to hold down CTRL at startup and click the Work Offline button. This should stop the crash, even if changing DNS servers doesn't.
I happen to use OpenDNS and do not want to repeat the crashes of others. I have not installed Beta 3 although it downloaded automatically. Is there any way to delete the downloaded upgrade, and just stay with Beta 2 until beta 4 comes around.
Switching to 8.8.8.8 for DNS would not solve name resolution messages:
C:\>nslookup internal.services.logos.com 8.8.8.8
Server: google-public-dns-a.google.com
Address: 8.8.8.8
*** google-public-dns-a.google.com can't find internal.server.logos.com: Non-existent domain
Note: can resolve address for services.logos.com
Thanks for the thread.I am not somewhere that I can afford a full download or to wait for a Beta to be patched. I'll hold off till I know the risk. I was downloading it but cancelled before it was complete.
Here also beta3 crashes. It isn't a nameserver problem. I have tried the nameservers of my internetprovider AND the OpenDNS nameservers, and in each case Beta3 crashes.
I was using OpenDNS and Beta3 did crash. After changing the nameservers to my internetproviders default nameservers AND restarting Windows, Beta3 works just fine.
Thanks for the warning, Dominick! I'm holding off on downloading Beta 3 until this problem is fixed and another beta comes out without any crashing disasters reported in the first day of use.
I too am holding off. Thanks for taking one for the team Dominick
Thanks for taking one for the team Dominick
Yep. He's a real team player. [;)]
Sorry for your trouble. [:S]
Wish I would have read this before I installed the update.
Crashing here too. It crashes consistently on trying to save or load a layout. (sorry didn't save any logs)
It just crashed on cycling through some study Bibles. Here are all the recent logs for that crash (including setup logs, in case they give any help - sure would be nice if the forum software allowed for more than one file to be selected at a time).
3051.Logos4Indexer.log
5611.Logos4.log
228717.Logos4Crash.txt
5611.Logos4Error.log
4555.DigitalLibraryInstall.log
4064.logos4setup.log
EDIT: I did not do anything to alter the DNS (never heard of "Open DNS" before this thread) and have no idea what DNS server my ISP uses.
This crash appears to be unrelated to OpenDNS; can you please start a new thread and post the crash log there? (That will make it easier for Testing to respond to your issue individually.)
Crashing here too. It crashes consistently on trying to save or load a layout. (sorry didn't save any logs) This crash appears to be unrelated to OpenDNS; can you please start a new thread and post the crash log there? (That will make it easier for Testing to respond to your issue individually.)
Done.
I'm having the exact same problem. I've attached my log files. This is a real bummer...today is my message prep day. Note to self: always read the Beta Forum first. [:@]
8883.Logos4.log
663254.Logos4Crash.txt
1588.Logos4Error.log
today is my message prep day. Note to self: always read the Beta Forum first.
The same situation, plus I go to the Bible School to teach from Monday[:(] on... I hope we will see a new Beta till then.
I'm having the exact same problem.
Try following these instructions to configure your computer to use Google's DNS servers: http://code.google.com/speed/public-dns/docs/using.html, or these instructions with pictures: http://techie-buzz.com/how-to/google-public-dns-on-win7-and-winxp.html
Or, if you select Obtain DNS server address automatically in those dialogs, you should use your ISP's default servers, which should also avoid the crash.
Another alternative is to hold down CTRL at startup and click the Work Offline button. This should stop the crash, even if changing DNS servers doesn't.
