[SOLVED] When I invite a user, or Resend Invitation, dispaly "An error has occurred. An unhandled server error has occurred."

wcjxixi · July 7, 2021, 11:35am

My new free 7 day trial Enterprise Organization，When I invite a user, it dispaly “An error has occurred. An unhandled server error has occurred.” or Resend Invitation, the same error.

Is it a Bitwarden cloud server failure?

rabkevich_lesha · July 7, 2021, 2:17pm

у меня такая же ошибка

Peter_H · July 7, 2021, 2:57pm

Google translate: “I have the same error”

tgreer · July 7, 2021, 3:22pm

Hmmm - you may have a character in the Organization name that is causing the issue.

github.com/bitwarden/server

Fix queue message encoding for Azure (UTF-16 in XML)

bitwarden:master ← bitwarden:azure-queue-illegal-char-fix

opened 03:01PM - 06 Jul 21 UTC

cscharf

+76 -74

Fixes https://app.asana.com/0/1169444489336079/1200549509965487/f. Reverts #1…425 Based on discussions with @MGibson1 last week and needing to get something put together this week, taking a more simplistic approach that can be re-visited next week if necessary. This is _similar_ in approach to #1435 except that it moves the logic more lower-level in the queue service and alters all queue consumers with an extension method. ## Files * **CoreHelpers.cs**: Adds `DecodeMessageText()` extension method to `QueueMessage` which does a test for Base64 and falls back to the raw message text. This was Matt's original idea before we started overcomplicating things. * **AzureQueueService.cs**: 2 primary changes here, 1st is to always base64 encode the JSON message, the 2nd is to update the algorithm that determines and breaks up bulk enqueue requests by byte size to only serialize messages to JSON once, and to use the string byte-length overall to determine and calculate base64 size before creating finalized arrays in the message to return, and use string concatenation for the final JSON array (faster) vs. re-serializing to JSON (slower). * **everywhere else**: Use the new `DecodeMessageText()` extension method instead of getting `QueueMessage.MessageText` directly. ## Testing Notes * Noted in Asana and Slack ## Deployment Notes **MUST deploy FIRST:** 1. Event Processing Service 2. Notification Service 3. Admin Service **THEN:** 1. Identity 2. API 2. Anything else

Try removing any special characters from the Org name, removing the users whose invites failed (if they are listed) and invite them again.

wcjxixi · July 7, 2021, 4:04pm

No special characters, but all Chinese characters.

And I did the same operation in the previous version, everything is OK.

I will test it tomorrow, ths!

rabkevich_lesha · July 7, 2021, 5:18pm

Спасибо. Ввел название английскими буквами и все заработало

Peter_H · July 7, 2021, 11:29pm

Google translate: “Thank you. I entered the name in English letters and it worked”

tgreer · July 8, 2021, 12:36pm

Thanks @Peter_H

@rabkevich_lesha @wcjxixi I believe this fix was released last night, too. So, feel free to give it a shot again

wcjxixi · July 8, 2021, 1:52pm

Tested, all is OK now!

tgreer · July 8, 2021, 2:03pm

That’s great news!

Excellent

beatljuice · May 3, 2022, 9:56pm

I had the same warning.

Turns out I had already invited a second person to the organization. It was my wife, and I had used a different email to invite her from the one she signed up with. But I hadn’t deleted the invite, and it was still pending so it looked like I was trying to add a third person to the organization when we were using the free version.

FRG-Tech · December 13, 2022, 2:46pm

Hi,
I’m having the same problem with slightly different circumstances. I’m trying to add another user (myself), to the vault I set up at work.

I’ve already made a successful invite about a week or so ago without issue. Now that I’ve moved my personal KeepassXC vault over to Bitwarden, I wanted to add myself to my work vault.

So I saw the suggestion about removing special characters from the organization name. Our org name does have an “&” in the name, but it already worked without a hitch for one user invite, so I don’t think this would be the issue.

Is there anything else I can do to get this working? This really threw me for a loop. I already upgraded my personal account to premium and have gone all in with Bitwarden, but this has me dead in the water.

Thanks!

c-epitath · February 15, 2023, 3:00am

i am getting this error with the online bitwarden using the enterprise version. i invite a new user which is me with a different email address. i am on the same computer and my management account logs in and out fine but this new account gets this error. i have sent invites to users on other computers and they all work fine.
when i first tried to setup this new user of me with a different email address i forgot to save the password so i deleted the entry. then recreated it. i am suspicious that deleting a new user before it is first logged into has created a partial record in the data store so i cannot use the same email address again.