Fatal Error: “We are sorry, we are not able to process the operation further…”- Don’t Panic! It’s not a bug.

If you see the message,

error-min

Please, don't panic! It is NOT A BUG!

This message appears during the login process - if user has different email addresses on Master (vBulletin acts as a Master) and Slave platforms (for example, WordPress or others).

Why does it happen?

Because one of the biggest SSO challenges is that data that identifies the user is not always consistent throughout the all platforms. For example, user John Smith might be identified as John Smith for one platform, but J. Smith for another and Smith, John for a third.

How to check this out?

A. First of all, you should check whether all the vBSSO hooks are enabled on the vBulletin side - it also may cause the fatal error messages. Log in your AdminCP and go to:
AdminCP -> vBulletin Options -> Plugin Options -> Plugin/Hook System.
Set it to Yes to enable. Also, it is also important to check this command in your code. If your code consists of:

define('DISABLE_HOOKS', true);

Either remove the line or simply comment that line out. add two forward slashes " / " so it will look like:

// define('DISABLE_HOOKS', true);

It will enable the plugin/hook system.

B. After that you can easily check for account duplicates by SQL requests.

Here is the list of SQL requests for supported platforms:
vBulletin 3.x, 4.x check for account duplicates (email and username)

SELECT email, COUNT(email) AS total FROM {TABLE_PREFIX_}user WHERE LENGTH(TRIM(email)) > 0 GROUP BY email HAVING total > 1 ORDER BY total DESC;
SELECT username, COUNT(username) AS total FROM {TABLE_PREFIX_}user WHERE LENGTH(TRIM(username)) > 0 GROUP BY username HAVING total > 1 ORDER BY total DESC;

WordPress 3.x, 4.x, check for account duplicates (email and username)

SELECT user_email, COUNT(user_email) AS total FROM {TABLE_PREFIX_}users WHERE LENGTH(TRIM(user_email)) > 0 GROUP BY user_email HAVING total > 1 ORDER BY total DESC;
SELECT user_login, COUNT(user_login) AS total FROM {TABLE_PREFIX_}users WHERE LENGTH(TRIM(user_login)) > 0 GROUP BY user_login HAVING total > 1 ORDER BY total DESC;

Prestashop 1.5.x, 1.6.x check for account duplicates (email)

SELECT email, COUNT(email) AS total FROM {TABLE_PREFIX_}customer WHERE LENGTH(TRIM(email)) > 0 GROUP BY email HAVING total > 1 ORDER BY total DESC;

Magento 1.7.x, 1.8.x, 1.9.x check for account duplicates (email)

SELECT email, COUNT(email) AS total FROM {TABLE_PREFIX_}customer_entity WHERE LENGTH(TRIM(email)) > 0 GROUP BY email HAVING total > 1 ORDER BY total DESC;

Drupal 6.x, 7.x check for account duplicates (email and username)

SELECT mail, COUNT(mail) AS total FROM {TABLE_PREFIX_}users WHERE LENGTH(TRIM(mail)) > 0 GROUP BY mail HAVING total > 1 ORDER BY total DESC;
SELECT name, COUNT(name) AS total FROM {TABLE_PREFIX_}users WHERE LENGTH(TRIM(name)) > 0 GROUP BY name HAVING total > 1 ORDER BY total DESC;

Joomla 1.5.x, 2.5.x, 3.x check for account duplicates (email and username)

SELECT email, COUNT(email) AS total FROM {TABLE_PREFIX_}users WHERE LENGTH(TRIM(email)) > 0 GROUP BY email HAVING total > 1 ORDER BY total DESC;
SELECT username, COUNT(username) AS total FROM {TABLE_PREFIX_}users WHERE LENGTH(TRIM(username)) > 0 GROUP BY username HAVING total > 1 ORDER BY total DESC;

Moodle 2.3.x check for account duplicates (email and username)

SELECT email, COUNT(email) AS total FROM {TABLE_PREFIX_}user WHERE LENGTH(TRIM(email)) > 0 GROUP BY email HAVING total > 1 ORDER BY total DESC;
SELECT username, COUNT(username) AS total FROM {TABLE_PREFIX_}user WHERE LENGTH(TRIM(username)) > 0 GROUP BY username HAVING total > 1 ORDER BY total DESC;

Mediawiki 2.3.x check for account duplicates (email and username)

SELECT user_email, COUNT(user_email) AS total FROM {TABLE_PREFIX_}user WHERE LENGTH(TRIM(user_email)) > 0 GROUP BY user_email HAVING total > 1 ORDER BY total DESC;
SELECT user_name, COUNT(user_name) AS total FROM {TABLE_PREFIX_}user WHERE LENGTH(TRIM(user_name)) > 0 GROUP BY user_name HAVING total > 1 ORDER BY total DESC;

* Do not forget to change the {TABLE_PREFIX_};

* The username or email may vary even if there are no duplicates.

If you discovered an account duplicates, you should just simply make the emails identical on both Master and Slave platforms.

The issue as described should not persist any longer.

2 Comments

  1. if the above doesnt work for you and you are using wordpress the next solution is to go to file manager for your wordpress install and rename the vbsso plugin fodler to something else.

    this will allow you to login to your WP admina nd work out the issues. im going for a reinstall of plugin both ends

    Siparker
    • vbsso

      We would like to thank you for your comment. Yes, you are right. However, your method allows only to login to WP admin panel. Then, you should check user’s email address identity for both Master and Slave platforms. Do not forget please to rename back the vBSSO plugin folder (otherwise it may cause fatal errors).

      You are always welcome to try it and leave your feedback assisting developers to do all their best!

      vbsso

Leave a reply


CAPTCHA Image
Reload Image