Internal Users Are Not Migrated During Upgrade to Confluence 3.5.x or Later

Still need help?

The Atlassian Community is here for you.

Ask the community

This KB only applies to instances that have been upgraded from Confluence 3.4 or below, to 3.5 or above. Do not use this article if you are not troubleshooting a failed upgrade attempt.


  1. The internal users were not migrated to table cwd_user, Crowd embedded, during upgrade to Confluence 3.5.x.
  2. The internal users remain at the old table users.

The following appears in the atlassian-confluence.log:

2011-05-26 14:40:29,437 WARN [http-8080-3] [atlassian.seraph.auth.DefaultAuthenticator] login login : 'admin' tried to login but they do not have USE permission or weren't found. Deleting remember me cookie.

NB: This error will also occur each time a user is denied access to the system based on permissions. If you see this error but did not just upgrade from Confluence 3.4 or below, this is likely not the cause of your problem. If you did not upgrade from 3.4 or below, contact Support for assistance.


  1. After the upgrade run these queries to check if there are internal users into the new cwd_user table:

    select * from cwd_user where directory_id = (select id from cwd_directory where directory_type='INTERNAL');
  2. If it's confirmed that there are no users from the internal directory into the cwd_user table after the upgrade, proceed with the next step.

  3. Run this query against your database pre-upgrade:
    (info) Note: Where ? is the BUILDNUMBER of your current version of Confluence. You can check witch buildnumber belongs to each version of Confluence by accessing this page.

  4. If it returns any result, proceed the resolution steps.


The restore of the database after an upgrade attempt was not correctly done, and some information from this upgrade attempt are still at the database.


  1. Rollback your database to a point pre-upgrade.
  2. Run this query to remove the rows of the extra buildnumbers:
    Note: Where ? is the CONFVERSIONID of all extra buildnumbers.

  3. Be sure that the correct buildnumber of your current Confluence version is set into your confluence.cfg.xml file, which is located at Confluence home.

  4. Try to proceed the upgrade again.
Last modified on Mar 30, 2016

Was this helpful?

Provide feedback about this article
Powered by Confluence and Scroll Viewport.