Error Code 3003 - Cannot delete this meeting

  • 0
  • 4
  • Question
  • Updated 5 months ago
  • Acknowledged
When a meeting is cancelled, I receive Error Code 3003 - Cannot delete this meeting.  I receive the pop up several times.  I can close out of the error code pop-ups and the meeting is still deleted, but I should not be receiving this message
Photo of Beth Jensen

Beth Jensen

  • 526 Points 500 badge 2x thumb

Posted 8 months ago

  • 0
  • 4
Photo of Brett Kitani

Brett Kitani

  • 62 Points
I'm having the same issue and I'm unable to cancel the meeting. Quite annoying. Only started a few weeks ago.
Photo of Saadet

Saadet, Employee

  • 68,092 Points 50k badge 2x thumb
Hey Beth and Brett,

Could you provide more details? When are you receiving this error message? Where are you trying to delete the Meeting from?
Photo of Beth Jensen

Beth Jensen

  • 526 Points 500 badge 2x thumb
I receive the message when I am cancelling (not deleting) a meeting from Outlook, but the error message is generated from RingCentral, not Outlook.  And I receive it multiple times - close one error message and another instance pops up - up to 4 times.  But the meeting does eventually cancel and I can "x" out of each instance of the error message.  
Photo of Saadet

Saadet, Employee

  • 67,790 Points 50k badge 2x thumb
So weird! I would suggest opening a case so that our Support Team can take a deep dive. Let us know what they come back with! That way, if anyone else has this issue, the resolution will be right here :)
Photo of Beth Jensen

Beth Jensen

  • 526 Points 500 badge 2x thumb
What is the process for opening a support case?  Is there a link I should use?
Photo of Becky - Community Support

Becky - Community Support, Official Rep

  • 1,188 Points 1k badge 2x thumb
Hi, Beth! Use this button to create your support case.

Open support case online
Photo of Fergus Graham

Fergus Graham

  • 72 Points
Hello,

Has there been a resolution on this? We recently started using RC (previously on Skype) and this issue has popped up a few times.
Photo of Saadet

Saadet, Employee

  • 67,790 Points 50k badge 2x thumb
Hey Fergus, please contact Support as we mentioned earlier. Feel free to keep us posted about a resolution! I'm not aware of one at this time.
Photo of Dean Rogers

Dean Rogers

  • 154 Points 100 badge 2x thumb
Usually this occurs when you are trying to cancel a meeting series made by someone else. To resolve, have the original meeting scheduler delete the meetings or grant you permission to do so.
Photo of Fergus Graham

Fergus Graham

  • 72 Points
Hi Dean, 

In the case I have been dealing with, it is the owner of the meeting who was having issues with deleting a meeting, I would completely understand that an error code would be thrown up if someone else who didn't own the meeting was trying to cancel it. 
Photo of Beth Jensen

Beth Jensen

  • 526 Points 500 badge 2x thumb
Same here ... I was the owner of the meeting, but still received the error.  It usually happens if I try to delete the meeting too close to the meeting start time.  But it's still before the meeting start, so it doesn't seem like I should receive any type of error.  The meeting does delete, but the error message shows multiple times and is very annoying.
Photo of Patrick

Patrick

  • 60 Points
Ours seems to be a bit more mysterious.  The meeting shows the correct organizer and when it is forwarded to someone or declined by someone it emails the organizer (him) but it is not his RC meeting ID.  As IT manager i had the organizer forward it to me.  I accepted it, he was notified i did then I logged in. It logged me into a users meeting not in our tenant or working for our organization. We've had the support ticket open with RC since 6/18/2019 with no results. The error now makes sense as RC does not see him as the organizer but he is listed as the organizer in the scheduling assistant and he is the one who gets notifications of acceptance, decline, and your attendees are waiting.  Some sort of cross tenant glitch i am assuming. I just escalated to my Rep but this seems like a security issue as well to me.  
(Edited)