This article provides an overview of the most common errors that can arise when signing up or into Mentimeter via SSO (single sign-on), along with suggested actions to take to resolve the issue.
Error codes
| We couldn’t find an SSO configuration for the workspace you are trying to sign in to or the authentication response we got was issued by an unexpected EntityId. Contact your IT administrator for help resolving this issue. |
| Your workspace does not support single-sign-on (SSO). SSO is only available on our Enterprise plan, and the workspace you entered is on another plan type. Use another sign-in method to access Mentimeter, and ask your internal IT administrator to be invited to the workspace. |
| It seems like the link you used to confirm your email was not working. Please check you used the right link, and that it hasn’t expired. If the invite link has expired, contact the person inviting you for a new one. |
| There were problems with the SAML assertion we received from your identity provider and we are unable to sign you in. The problem is likely caused by a SAML misconfiguration. Please reach out to your internal IT administrator for help. If you can’t resolve this on your own, contact our customer support for help. |
| Your Identity Provider Certificate may have expired, or the certificate in IdP metadata and SAML response do not match. Contact your internal IT administrator to ensure the current certificate is properly listed in your metadata and that the latest metadata has been shared with Mentimeter. Alternatively, check with your IT administrator if the certificate in IdP metadata and SAML response match. If either of these is the case, the setup might need to be updated by your IT administrator before you proceed to log in. |
| The attempt to sign in to your account was stopped due to it taking a long time to verify the account. Please try to sign in again. If you keep getting this error, contact customer support for help. |
| You seem to be a member of another Mentimeter Workspace. To sign in to your account, enter the correct workspace name and try again. If you continue to have issues, contact our customer support for help. |
| This error occurs when information is missing in the response we get from your organization. We need this information to verify your account and to sign you in. To resolve this issue, changes need to be made in the SSO setup from your organization. Please reach out to your internal IT administrator for help. If you can’t resolve this on your own, contact our customer support for help. |
| The service is currently down for maintenance but should be up and running again soon. Please try again shortly. If you keep getting this error, contact our customer support for help. |
| Your account doesn’t seem to meet the tenant requirements needed to access the workspace as decided by the settings of the workspace. To resolve this issue, contact your internal IT administrator. |
| Your Mentimeter account has been deactivated by a workspace admin. To regain access to your account, contact your internal IT administrator or follow your internal process for IT access. |
| The workspace invitation does not exist or is no longer valid. Make sure to use the correct invite link. If it still doesn’t work, ask the person inviting you for a new invite, or reach out to your internal IT administrator for help. |
| All licenses in the workspace are occupied. To access Mentimeter, you will need to ask your internal IT administrator for a license. |
| This error occurs when there’s no workspace registered with the name you are using. For this to work, your company needs to have an Enterprise subscription with SSO implemented. If you have typed the name of your company and the workspace cannot be found, try different versions of the name:
-The Ugly Duck Inc. -Ugly Duck -TUD -Uglyduck
Don't worry, we will not block your account if you try several times! If this doesn’t work, reach out to your internal IT administrator for help. |
If the error you're getting is not listed above, please contact our customer support and provide a screenshot of the error so we can look into it further.