Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal

Recognition

  • Give kudos
  • Received
  • Given

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

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

Problem importing Crowd xml backup file on migration Edited

In case others run into this problem - I could not find a solution on the web:

I migrated from an older Crowd version (2.7.2) using  JDK 1.7.x (that matters - also for older versions) )  to the actual version  (3.1.2) with JDK 1.8.x (that matters) and ran into the symptoms described under  Importing Crowd XML Backup Fails due to Different Locale.

ERROR [atlassian.crowd.migration.DirectoryMapper] Failed to parse date: Wed May 14 18:03:35 +0200 2008
java.text.ParseException: Unparseable date: "Wed May 14 18:03:35 +0200 2008"
  at java.text.DateFormat.parse(DateFormat.java:335)
  at com.atlassian.crowd.migration.GenericMapper.getDateFromFormattedString(GenericMapper.java:99)

The problem in this constellation is that java changed it's german date interpretion of the month march, which was "Mrz" until JDK 1.7.x and is "Mär" ( the german umlaut for ae in the middle ) from JDK 1.8.x on.

So what you have to do is to find "Mrz" and replace it with "Mär" in the Crowd xml export.

Cheers,
Christian

1 answer

1 accepted

0 votes
Answer accepted
Lauretha R Atlassian Team Mar 26, 2018

Hey @Christian Bär - seems like you're hitting intosimilar  issue as the one described in this KB article - Importing Crowd XML Backup Fails Due To Different Locale.

Could you please follow the workarounds mentioned in that KB article and see if that works?

 

Hope this helps :) 

Hello Lauretha,

thanks, I fixed my problem and gave a solution for others, because this cause/solution is missing in your kb article. ;-)

The articel ( I already mentioned in my post) has the same symptom, but a different cause !

This affects only customers using  de_DE locale when exporting and importing.

Sorry that I posted that under "questons" - as I had no question but an answer for others -  but I didn't see a better place.

And as you are an Atlassian I suggest to update the referenced kb article.

Cheers,
Christian

Suggest an answer

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

Share your Confluence Cloud experience for a chance to win $500!

Take our 5-minute survey to win a $500 Visa gift card! Are you currently using Confluence Cloud? We want to hear from you! Fill out this quick survey about your Confluence Cloud experience so we ...

293 views 5 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