Unable to print checks

From the clerk's office computer, I loaded up LCR, had a payment in the "Print Check" queue, entered the queue, selected the check, and clicked "Print Checks". I received the following error message:

"Uh oh! We're Sorry ...
It looks like something went wrong which prevented the page you requested from displaying. Sorry for any inconvenience that this may have caused!"

I'm going to call it a night and head home, but hopefully whomever supports that function gets word of it and can get it fixed or let me know what I need to do.

Thanks.

siredge wrote:I'm going to call it a night and head home, but hopefully whomever supports that function gets word of it and can get it fixed or let me know what I need to do.

This is a user-to-user forum. It is unlikely than anyone here will see your request or get word of your problem, let alone fix it.

You will need to call the Global Services Department, which was still open for another two hours when you posted, but is closing as I send this message.

Perhaps try the usual troubleshooting steps: incognito mode, clear cache and cookies, try a different browser, etc.

That error is also often just due to temporary server issues so just trying again later often works.

I am encountering the same issue constantly over the last 48 hours. I attempted to print the check from MLS, too, but because the expense hasn't been finalized by LCR (through the print check process) the expense hasn't been synced to MLS (so it isn't available to print in MLS either).

I am having the same issue.

Send feedback. Stake Clerk. Global Services Department.

Same issue at a Stake level.

Same issue as everyone else since Thursday 12/17/2020.

anyone been able to print checks?

Also having the same problem.

Same issue here. Can't print since 12/17/2020
Things we tried that didn't work: Different browsers, different network connection, clearing cache and cookies and history, restarting the computer, different account authorization (my sign in and bishops). Can't get it to work yet.

still unable.

We are encountering this problem as well. Of course church telephone number isn't taking calls on Sunday.

Same issue. In clerk's office, same printer and computer as before, same network. Using Chrome browser and on the LCR page. Expense has been approved and says it is ready to have the check printed. Sunday, Dec. 20. I'm not aware of any difference that would be a problem.

We are having the same error and cannot print checks

Also having issues printing Checks. Receiveing the following error when attempting to print checks.

"
Uh oh! We're Sorry ...
It looks like something went wrong which prevented the page you requested from displaying. Sorry for any inconvenience that this may have caused!
"

still not working.

same issue same equipment same everything. no success as of 4pm on sunday

Once again, send feedback. That is how they will know there is a problem.

At the risk of repeating other reports, I am seeing the same error. I have attempted to force a complete reload on the page in case there was a code caching error all to no avail. I am seeing the following error trace in the console of the developer tools:

vendor.ea96ab4c897f5279b393.js:21 ReferenceError: i is not defined
at Scope.scope.getNextCheckToPrint (https://lcrf.churchofjesuschrist.org/fi ... :21:133048)
at Scope.scope.printChecks (https://lcrf.churchofjesuschrist.org/fi ... :21:128316)
at fn (eval at compile (https://lcrf.churchofjesuschrist.org/fi ... :21:221621), <anonymous>:4:329)
at expensiveCheckFn (https://lcrf.churchofjesuschrist.org/fi ... :21:123215)
at callback (https://lcrf.churchofjesuschrist.org/fi ... :21:252516)
at Scope.$eval (https://lcrf.churchofjesuschrist.org/fi ... :21:142173)
at Scope.$apply (https://lcrf.churchofjesuschrist.org/fi ... :21:142512)
at HTMLButtonElement.<anonymous> (https://lcrf.churchofjesuschrist.org/fi ... :21:252623)
at defaultHandlerWrapper (https://lcrf.churchofjesuschrist.org/fi ... s:21:25434)
at HTMLButtonElement.eventHandler (https://lcrf.churchofjesuschrist.org/fi ... s:21:25282) undefined
(anonymous) @ vendor.ea96ab4c897f5279b393.js:21
(anonymous) @ vendor.ea96ab4c897f5279b393.js:21
(anonymous) @ app.83842bd2e9d08fc35fdd.js:1
$apply @ vendor.ea96ab4c897f5279b393.js:21
(anonymous) @ vendor.ea96ab4c897f5279b393.js:21
defaultHandlerWrapper @ vendor.ea96ab4c897f5279b393.js:21
eventHandler @ vendor.ea96ab4c897f5279b393.js:21

Having the same issue. Been happening for several weeks. Seems to be server issue and when we try again later, sometimes it will work.

Been unable to print checks all day. Tried Chrome, Edge, Firefox, cleared cache, cookies, etc... Incognito mode as another thread suggested.
Opened a ticket.... Just letting others know issue is still there.

I have had the same issue yesterday (Sunday) and expect that it was a server problem. I expect the church IT department will be on it right away today. At least I hope so. I'll give them a call when they open in a few hours.

They are aware of it and working on a fix.

Anyone find a fix?

There isn't a fix that you can make. I talked to the developer working on the issue yesterday and he said that they are aware of it and working on a fix.

May have been fixed. -- I was just able to print some today after being unable to print on Sunday. I also heard from our stake clerk that two other wards were also able to print checks today. No idea what the issue was or what changed, other than maybe less connections to the server today.