I've been testing the SETI Beta for a couple of days now and have not had any of the errors. I haven't seen them from the other two projects that I run either so I'm not quite sure what to make of it.

---

I suppose it really doesn't matter if you don't understand that each Project uses a different Science App, and that the App on SETI Main is different than the App at SETI Beta that isn't giving you any problems. What does matter is that you test the New App at Beta and report if it solves the problem with the App on Main. It's been almost 2 weeks since my last post and there isn't a single post at Beta stating that the App at Beta solves the problems some are having with the App on Main. Until there are a few posts there, I doubt this problem will ever be solved on SETI Main. If the App at Beta solves the problem, post about it here, https://setiweb.ssl.berkeley.edu/beta/forum_thread.php?id=2266

I have been running Beta since I posted below. I cannot say that it has solved any problem in any app. What I can say is that I have not experienced this particular problem since well before I started running Beta.

---

I've been running beta for a week without any errors. If you need any other information just let me know.

---

https://boincstats.com/signature/-1/user/40040505/sig.png

Did something change in the late afternoon on 3/13/2018? This error had not occurred since early February? It's back.

---

https://boincstats.com/signature/-1/user/40040505/sig.png

I've run the Beta 8.22 app for about a day and the problem doesn't occur.

---

Thanks ThrowerGB! So far, it has only happened that one time. If it pops up again I'll switch to Beta.

---

https://boincstats.com/signature/-1/user/40040505/sig.png