Page 1 of 1

Clerk Resources - Unit Statistics

Posted: Mon Mar 11, 2013 7:18 am
by coconaut
I am trying to access reports from the Unit Statistics in Clerk Resources under Reports but am getting the following error message.

Clerk Resources - Sorry, an error occurred while processing this page.
Retry the web page by clicking the refresh/reload button or trying the URL from the address bar again. Even though the Server Error is reporting a general error on the web site's servers and not your computer, the server error may only be temporary. Trying the page again will often be successful.

Come back later. The Server Error message is often temporary and should be resolved fairly soon.

Use your browser’s back button to go back to the page you came from.

Has anyone (especially Bishops) had this problem before and if so, what was done to resolve the issue? Please assist.
Thank you.
Bishop

Re: Clerk Resources - Unit Statistics

Posted: Mon Mar 11, 2013 9:45 am
by lajackson
This error usually means the servers at Church headquarters are not keeping up with demand. Sunday afternoons and evenings seem to be the busiest, and the error seems to occur most often during those times.

Trying at a less busy time usually works.

Re: Clerk Resources - Unit Statistics

Posted: Mon Mar 11, 2013 10:21 am
by eblood66
coconaut wrote:Has anyone (especially Bishops) had this problem before and if so, what was done to resolve the issue? Please assist.
Thank you.
Bishop
This bug has been discussed in the Unit Statistics Error thread. It seems to be universal (at least, no one posted that it is working for them) and no one has found a work around. Further discussion should probably occur in that thread.

Re: Clerk Resources - Unit Statistics

Posted: Mon Mar 11, 2013 3:39 pm
by coconaut
It doesn't work at all. I've been trying at random times for the past month with no avail.

Re: Clerk Resources - Unit Statistics

Posted: Wed Mar 13, 2013 5:22 am
by dannykos
Works fine for me.

Re: Clerk Resources - Unit Statistics

Posted: Wed Mar 13, 2013 6:11 am
by coconaut
Seems to be working ok now. Whatever happened and when it happened, it's working now.
Thank you.