Error when logging-for all users

[dbaudio99]

All users are receiving this error message when they try to log in.  I can't log in to put in a ticket. Can someone help resolve this?

We encountered an error processing your request. If the issue persists, please contact your Company Administrator or Help Desk with correlation_id acf63e2bdbed-c2ed68fd8651faaaea2e-1-1 for additional help.

[chriscooke]

Also having this issue.

[SMyatt25]

Hello, 

Yes we are also facing the same issue, I have checked Concur Service status and its showing as all fine, so this issue has just happened. I can't log to create an support ticket either. @KevinD please can you help and possibly log a ticket for us? I am in the EMAE region

Many thanks 

Sam

[KevinD]

@SMyatt25 my Concur Open shows that the US data center is currently in a degradation. Did you check the US data center or the EU data center? Although you are located in EMEA, your company's site is running off the US data center. 

[SMyatt25]

Hi Kevin,

Yea i'm working on the US data server, but for the EMEA region. Glad to see that it's all back up and running this morning 🙂

[EGryczko]

I too am having this issue.  Is it a system issue?

[mbrown2626]

[karenp919]

I'm having the same issue.  Is there any updates from Concur?

[mmonacelli]

I am getting the same error but was able to login with the one-time email approach.  However, I am getting a new error trying to view my expense report.

analytics.js:61 Uncaught TypeError: Cannot read properties of null (reading 'toString') at useNavigation.ts:37:9 at onClick (ReportTile.tsx:55:7)

[ttmck]

Not able to open any expense reports

Sorry, but something went wrong with this task. Try refreshing the page, or sign out and sign in again. correlation_id: 1a56be6c-81d4-47e6-91cf-53de2d010ba5 TypeError: Cannot read properties of null (reading 'toString')

[Shannon1]

No one in my company can log in either - help!

[mbrown2626]

This is getting frustrating. 13,000 employees and nobody can sign in.

[KevinD]

Hello all...Concur Open is showing a degradation still. That is likely why you aren't able to sign in. I'm sure we are aware of it and working on getting it fixed.