EW does not stay logged in with CCLI, messes up reporting

Pretty much every time I start Easy Worship and need to access Song Select, I see the Login screen. Although when I hit the login button it pops up the login window, logs me in and closes it without requiring me to enter my credentials.


This isn't really a problem, except for Sunday mornings when I'm doing 50 things getting ready for service and generally forget to go log into CCLI. What this does is cause EW to fail to auto-report the songs that day. Because Sunday is the only day I'm actually "live", CCLI is rarely receiving reports.


I know it would seem the easiest solution would be to just remember to make sure I'm logged in on Sunday mornings, but like I said, I'm pretty busy trying to get all of the audio, video and live streaming stuff going... etc. If EW is supposed to remain logged in to CCLI, it would be nice if it did so.


Thank you,



Additional info...


EW 7.4.1.9 running on Windows 11 22H2 build 22621.1992

David. EasyWorship should keep you signed in to SongSelect if you have the box checked to stay signed in. However, any time you sign in to SongSelect in EW, it will check for any unreported songs for the last 45 days and will report them. So you don't need to be signed in every week.
If you still have an issue with SongSelect staying signed in, please contact support directly and they can troubleshoot that with you.

I will contact support some time here in the future when I have a few minutes to stop and breath. And I appreciate the response.


But, for the sake of posterity and for other people who might be having problems and  come across this thread, this is what I'm seeing. Bear in mind that I can log into CCLI (https://reporting.ccli.com/search) and see what's been reported and when.


EW is supposed to keep me logged in... but it doesn't. I suspect this is a bug and it really isn't causing me problems beyond being a bit frustrating.


Apparently (I didn't know this), EW will report previously used songs when I do log in, up to 45 days post use... but it doesn't. For example, EW didn't report any songs I used Sunday, Monday (we're doing VBS right now and using EW for songs) or Tuesday. I know I've been logged in since yesterday (Tuesday) and I can see that none of the songs we've used have been reported.


And... EW is only supposed to report songs when it's "live"... But is doesn't... When I look at songs I first used live last Sunday, I can see where they were reported a few weeks ago, when I was creating the schedule we used Sunday.


That last one is actually kind of interesting, because it tells me that I'm likely reporting every song that gets used, just not when I'm actually using them. I assume they only get reported once, and not every time I use them. Or at least the list I see on the reporting search page only shows the first time I used them.


Anyway, I'm just rambling because none of this is a really serious problem, other than my reporting isn't very accurate. I just wanted to put it all out there for the next guy who comes along looking for an answer.


Thank you for your reply.


David Chamberlain

Experiencing exactly the same as David.

EasyWorship does not stay logged in to CCLI/SongSelect - it logs out and needs to be logged in every time.

And, yes, I did check the box to stay logged in.

The computer is hard-wired to the Broadband Modem so is connected as soon as it it switched on.

NB: It might be worth mentioning that EW Auto-reports ONLY Digital and LiveStreaming.
People still need to add Printed Copies of Lyrics, Backing Track info and ALL copies of Musical Scores (both printed and emailed) on CCLI to report.

We're having the same problem. Every time we go to SongSelect in EasyWorship it prompts us to login again, even though we always check "Keep me signed in". We can log in to both SongSelect and the CCLI reporting site using a browser and it always keeps us logged in, but doing it via EasyWorship we keep getting logged out. Meanwhile nothing has been reported to CCLI for the past 3 weeks. We are running the latest EW version 7.4.1.9. 

We also have EW installed on a few other computers in the church (for building schedules etc). Because they are not used in our services, auto-reporting is not enabled on these machines but they still have the problem of EW constantly logging out of SongSelect. 

KVFC Calcot
Dan's reply on the following thread might be relevant...

https://support.easyworship.com/support/discussions/topics/24000022059

Re. Background Helper. I suspect therefore there might be an issue with the Background Helper not 'helping'.

Yes, you are correct EW doesn't stay logged in to CCLi Reporting despite having clicked 'Stay Logged' in.

I'm wondering whether it has anything to do with connection to default browser, or the Browser platform used for Livestreaming?

Lindsey

Thanks for your comments, Lindsey. 

The problem of SongSelect logging out seems to affect all our computers that are using EW7, not just the church laptop. 

Some are on Windows 10, some on Windows 11, some use Edge, some use Chrome etc. 

We can all login and stay logged in to CCLI and SongSelect if we use a browser, but doing it via EasyWorship we are constantly logged out. 

Regarding the Background Helper, I can't easily check the church laptop until next Sunday as the laptop is kept locked away. 

Perhaps I will be able to get a log report from the church laptop to send to EW Support.

Out of interest I checked the Windows Task Manager on my own computer, and the EasyWorship Helper is running in the background even when EasyWorship itself is closed. However that doesn't solve the login issue, and it doesn't prove anything about auto-reporting because that is disabled on my machine. I'll let you know if I find out more.

John

We’re still having the same problem. We keep logging SongSelect back in and checking that auto reporting is still enabled but nothing is being reported to CCLI. I did try stopping and starting the EW Helper as Dan suggested but reporting is still not working. I have sent the auto-reporting log report to EW Support and raised a ticket, but no response yet. 
John

Login to post a comment