Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Error when launching login page after xml migration

We completed the migration of our Confluence instance to a new server. We exported the confluence xml and successfully loaded it onto the new instance (on CentOS and MySQL).

After completing the import process through the Setup Wizard, when trying to launch and go to the Login page, we get the following error:

 

org.apache.velocity.exception.MethodInvocationException: Invocation of method 'isShowSignUp' in class com.atlassian.confluence.user.actions.LoginAction threw exception java.lang.NullPointerException: Application cannot be null at /login.vm[line 6, column 28]
    at org.apache.velocity.runtime.parser.node.ASTMethod.handleInvocationException(ASTMethod.java:337)

caused by: java.lang.NullPointerException: Application cannot be null
    at com.google.common.base.Preconditions.checkNotNull(Preconditions.java:204)

 

As a note, it is worth to mention that the original instance was integrated with Crowd, but the new instance/server will not. I am not sure if that may be related to this error, but it is another variable to consider

I am new to the administration aspect of Confluence, so I will appreciate if someone could please steer me in the right direction to find the cause of the problem.

Thanking you for your help.

-Idelso

3 answers

0 votes
Guilherme V. Atlassian Team Dec 08, 2015

Hey there,

It looks like you have some Null value or a misleading information in your cwd_app_dir_mapping table. Check this documentation of how to fix that.

Hope this will help you smile.

Cheers, 

Had the same Issue but the Resolution didn't work.

Like Evgeniy_Russkikh likes this

We even tried adding in the data (it exists in our production database) into the new PostgreSQL database (where it was missing) but it still fails with the same error.

0 votes
Bruno Atlassian Team Dec 08, 2015

Hi Idelso,

It could be the case that, since you used Crowd before, the internal directory is not working after the upgrade. You could try the following article:

Unable to log in due to disabled Internal Directory (Confluence 3.5 and later)

Regards,

Bruno

Yea, that didn't work either in our case. 

Did you ever resolve this issue?  Getting the same error Moving from a vanilla confluence server on VMware to a new vanilla server on Nutanix VM.  It is the exact same error and the recommended fixes above did not work for me either.

Our Confluence database was PostgreSQL 9.2 and when we migrated the data, it was to PostgreSQL 11.2. As I mentioned before, I tried to input the missing data but that failed. We were considering installing the older PostgreSQL version (you can run multiple instances, just need to configure ports for them) to continue with our upgrading but I decided perhaps there was an issue with the backup. So, I created another backup (leaving the defaults and not touching anything else in the PostgreSQL Admin console when it came to the backup creation), installed it in the new PostgreSQL and it worked. There were some depreciation (mainly not being UTF-8) errors but Confluence allowed start-up to continue.

Thanks!  I will give that a try, I was doing the backup from confluence itself.

Yea, we didn't use the XML backup of Confluence. Since the majority of the data resided in the PostgreSQL database, that is what we backed up and then we "robocopied" (i.e. manually transferred) other parts of Confluence into the new installation (such as the add-on folder, attachments, images, etc.).

Like ICT Team likes this
0 votes

Got the same error when upgrading to Confluence 7.4.6 => backup was incomplete compared to previous ones:

Following block was missing in XML file:

<collection name="directoryMappings" ...

With a new backup, XML import action was still blocked at 90% (due to ERROR [Long running task: Importing data]), but looking at logs, import was successful.

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Confluence

🥓🙅🏻‍♀️ Meet-less May Badge!

Hello Confluence Community!  What if i told you that you could have a healthier life and be 100% meet-less? This month, we're promoting a healthy, balanced work diet with Confluence. We la...

223 views 2 14
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you