com.atlassian.crowd.exception.DirectoryNotFoundException

There are no available Samebug tips for this exception. Do you have an idea how to solve this issue? A short tip would help users who saw this issue last week.

  • h3. Summary When migrating from Cloud to Server, the directory poller job is not removed for the previous Crowd User Directory (aka Horde). h3. Steps to Reproduce # Export from a JIRA Cloud instance. # Import it into JIRA Server. h3. Expected Results There are no noticeable errors. h3. Actual Results The following exception is thrown: {noformat} 2015-05-04 10:45:36,829 atlassian-scheduler-quartz1.clustered_Worker-1 ERROR [com.atlassian.scheduler.JobRunnerResponse] Unable to synchronise directory com.atlassian.crowd.exception.DirectoryNotFoundException: Directory <10000> does not exist at com.atlassian.jira.crowd.embedded.JiraDirectorySynchroniser.runJob(JiraDirectorySynchroniser.java:71) at com.atlassian.scheduler.core.JobLauncher.runJob(JobLauncher.java:136) at com.atlassian.scheduler.core.JobLauncher.launchAndBuildResponse(JobLauncher.java:101) at com.atlassian.scheduler.core.JobLauncher.launch(JobLauncher.java:80) at com.atlassian.scheduler.quartz1.Quartz1Job.execute(Quartz1Job.java:32) at org.quartz.core.JobRunShell.run(JobRunShell.java:223) at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:549) {noformat} Additionally viewing the Scheduler Administration page will present errors as per the attached screenshot. h3. Workaround You can remove the orphaned job directly from the database as per our [Directory Sync Throws Error "Directory <2> does not exist"|https://confluence.atlassian.com/display/JIRAKB/Directory+Sync+Throws+Error+Directory+%3C2%3E+does+not+exist] KB article. h3. Notes When this is fixed, please include an upgrade task to clean up existing records, or some provide some SQL as a workaround that can be used to fix the problem.
    via by David Currie [Atlassian],
  • h3. Summary When migrating from Cloud to Server, the directory poller job is not removed for the previous Crowd User Directory (aka Horde). h3. Steps to Reproduce # Export from a JIRA Cloud instance. # Import it into JIRA Server. h3. Expected Results There are no noticeable errors. h3. Actual Results The following exception is thrown: {noformat} 2015-05-04 10:45:36,829 atlassian-scheduler-quartz1.clustered_Worker-1 ERROR [com.atlassian.scheduler.JobRunnerResponse] Unable to synchronise directory com.atlassian.crowd.exception.DirectoryNotFoundException: Directory <10000> does not exist at com.atlassian.jira.crowd.embedded.JiraDirectorySynchroniser.runJob(JiraDirectorySynchroniser.java:71) at com.atlassian.scheduler.core.JobLauncher.runJob(JobLauncher.java:136) at com.atlassian.scheduler.core.JobLauncher.launchAndBuildResponse(JobLauncher.java:101) at com.atlassian.scheduler.core.JobLauncher.launch(JobLauncher.java:80) at com.atlassian.scheduler.quartz1.Quartz1Job.execute(Quartz1Job.java:32) at org.quartz.core.JobRunShell.run(JobRunShell.java:223) at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:549) {noformat} Additionally viewing the Scheduler Administration page will present errors as per the attached screenshot. h3. Workaround You can remove the orphaned job directly from the database as per our [Directory Sync Throws Error "Directory <2> does not exist"|https://confluence.atlassian.com/display/JIRAKB/Directory+Sync+Throws+Error+Directory+%3C2%3E+does+not+exist] KB article. h3. Notes When this is fixed, please include an upgrade task to clean up existing records, or some provide some SQL as a workaround that can be used to fix the problem.
    via by David Currie [Atlassian],
    • com.atlassian.crowd.exception.DirectoryNotFoundException: Directory <10000> does not exist at com.atlassian.jira.crowd.embedded.JiraDirectorySynchroniser.runJob(JiraDirectorySynchroniser.java:71) at com.atlassian.scheduler.core.JobLauncher.runJob(JobLauncher.java:136) at com.atlassian.scheduler.core.JobLauncher.launchAndBuildResponse(JobLauncher.java:101) at com.atlassian.scheduler.core.JobLauncher.launch(JobLauncher.java:80) at com.atlassian.scheduler.quartz1.Quartz1Job.execute(Quartz1Job.java:32) at org.quartz.core.JobRunShell.run(JobRunShell.java:223) at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:549)
    No Bugmate found.