Crucible restore ERROR

Crucible 3.8.0 trail version.

When I want to restore data from a backup file. An error occurred. Below is information.

Is there any solution? Thank U.

 

F:\Atlassian\fecru-3.8.0\bin>fisheyectl.bat restore -f F:\fisheyeandcrucible_bac
kup_2016_08_25.zip --sql --no-batch-sql --force --dbtype built-in
WARN: your default encoding (GBK) does not support unicode.
This is likely to cause problems if any of the filenames, branch names or tag na
mes in one of your repositories contain unicode characters.
Update your locale settings or start with the -Dfile.encoding=UTF-8 option to av
oid these problems.
INFO - Using log4j configuration file: F:\Atlassian\fecru-3.8.0\log4j-client.xm
l
INFO - FishEye arguments: [-f, F:\fisheyeandcrucible_backup_2016_08_25.zip, --s
ql, --no-batch-sql, --force, --dbtype, built-in]
Starting Spring Context...
INFO - Refreshing com.cenqua.fisheye.ctl.Restore$RestoreApplicationContext@313f
cc: startup date [Fri Aug 26 08:43:41 CST 2016]; root of context hierarchy
INFO - Starting plugin system...
INFO - Plugin system started.
Spring Context started
Merged database configuration into F:\Atlassian\Data\fecru\config.xml
INFO - loading config from file: F:\Atlassian\Data\fecru\config.xml
Extracting fisheyedb/var/data/avatars/37/37c298a61085a5a94755d4c9999add02.image
(1M)...
Restoring to: jdbc:hsqldb:file:F:\Atlassian\Data\fecru/var/data/crudb/crucible
Dropping existing tables...
Creating table definitions...
1 rows written, 0 tables completed.
131 rows written, 1 tables completed.
136 rows written, 2 tables completed.
138 rows written, 3 tables completed.
139 rows written, 4 tables completed.
245 rows written, 5 tables completed.
314 rows written, 6 tables completed.
315 rows written, 7 tables completed.
395 rows written, 9 tables completed.
395 rows written, 10 tables completed.
395 rows written, 11 tables completed.
396 rows written, 11 tables completed.
INFO - Closing com.cenqua.fisheye.ctl.Restore$RestoreApplicationContext@313fcc:
startup date [Fri Aug 26 08:43:41 CST 2016]; root of context hierarchy
INFO - *** application context closed ***
ERROR: problem running command
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at com.cenqua.fisheye.FishEyeCtl.mainImpl(FishEyeCtl.java:99)
at com.cenqua.fisheye.FishEyeCtl.main(FishEyeCtl.java:42)
Caused by: java.lang.StringIndexOutOfBoundsException: String index out of range:
15
at java.lang.String.charAt(Unknown Source)
at com.cenqua.fisheye.util.XmlUtils.unicodeDecode(XmlUtils.java:120)
at com.atlassian.crucible.migration.xml.StAXStreamReader$1.getContentAsS
tring(StAXStreamReader.java:135)
at com.atlassian.crucible.migration.item.DBImporter$BaseInserter.setValu
e(DBImporter.java:442)
at com.atlassian.crucible.migration.item.DBImporter.importTable(DBImport
er.java:180)
at com.atlassian.crucible.migration.item.DBImporter.importData(DBImporte
r.java:134)
at com.atlassian.crucible.migration.item.SQLBackup.restore(SQLBackup.jav
a:192)
at com.atlassian.crucible.migration.item.SQLBackup$1.restore(SQLBackup.j
ava:173)
at com.cenqua.fisheye.ctl.Restore.run(Restore.java:197)
at com.cenqua.fisheye.ctl.Restore.main(Restore.java:273)
... 6 more
Press any key to continue . . .
F:\Atlassian\fecru-3.8.0\bin>

1 answer

1 accepted

This widget could not be displayed.

The warning you see at the beginning may indicate the culprit:

WARN: your default encoding (GBK) does not support unicode.
This is likely to cause problems if any of the filenames, branch names or tag names in one of your repositories contain unicode characters.
Update your locale settings or start with the -Dfile.encoding=UTF-8 option to avoid these problems.

Create a environment variable called FISHEYE_OPTS with a value "-Dfile.encoding=UTF-8" without the quotes and try again, please.

Hi Piotr,

Thank U very much.

It works.

I saw the WARN, But did not know how to solve it.

BR

dxzhuzhu

Suggest an answer

Log in or Sign up to answer
Atlassian Summit 2018

Meet the community IRL

Atlassian Summit is an excellent opportunity for in-person support, training, and networking.

Learn more
Community showcase
Posted 7 hours ago in Statuspage

What are your best incident management tips and stories? #HugOps

 👋Community members! Downtime happens. And great incident response takes a village. Teams like Support, Dev, SRE, Ops, IT, and Marketing have to come together to resolve the problem while keep...

25 views 0 2
Join discussion

Atlassian User Groups

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

Find a group

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

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you