09-14-2012 07:26 AM - edited 03-17-2019 11:48 PM
We have installed TMS PE on the server and now we are trying to migrate from Open DS to TMS PE. When running the migration tool, we are running into Migration Failed.
Is there a guide that will walk me through ?
It is failing after : Migrating Phone books .....
Any thoughts ?
09-14-2012 07:31 AM
Hi
Yes I have seen this before and it fails when importing phonebooks. It might be a duplicate entry in the OpenDS database and in the logs will show some number i.e "49 is already on the map".
The issue that we saw on this was resolved by manually going in the opends database and removing the duplicates. Can you tell me if the log contains some similar message like the one above? Or what error are you seeing?
I think anyways that this one is leading towards a TAC case but it would be intresting to know what error is in the log just for reference.
/Magnus
09-14-2012 07:35 AM
Here is the log :
Found Java at: "C:\Program Files\Java\jre6\bin\java.exe"
14 sept. 2012 12:44:27 INFO - Migration started
14 sept. 2012 12:44:27 INFO - Exporting data from OpenDS
14 sept. 2012 12:44:33 ERROR - Export ldif error output: You have provided optio
ns for scheduling this operation as a task but options
provided for connecting to the server's tasks backend resulted in the
following error: 'Erreur de connexion'
14 sept. 2012 12:44:33 ERROR - Ldif export failed
java.util.concurrent.ExecutionException: com.cisco.ts.mgmt.migrationtool.excepti
on.LdifExportFailedException: Ldif export failed: You have provided options for
scheduling this operation as a task but options
provided for connecting to the server's tasks backend resulted in the
following error: 'Erreur de connexion'
at java.util.concurrent.FutureTask$Sync.innerGet(Unknown Source) [na:1.6
.0_35]
at java.util.concurrent.FutureTask.get(Unknown Source) [na:1.6.0_35]
at com.cisco.ts.mgmt.migrationtool.ldif.LdifExporterImpl.exportLdif(Ldif
ExporterImpl.java:143) ~[migration-tool-1.0.159.jar:na]
at com.cisco.ts.mgmt.migrationtool.ldif.LdifExporterImpl.exportLdifFromO
penDS(LdifExporterImpl.java:55) ~[migration-tool-1.0.159.jar:na]
at com.cisco.ts.mgmt.migrationtool.MigratorImpl.getLdifFileInputStream(M
igratorImpl.java:334) [migration-tool-1.0.159.jar:na]
at com.cisco.ts.mgmt.migrationtool.MigratorImpl.runMigration(MigratorImp
l.java:145) [migration-tool-1.0.159.jar:na]
at com.cisco.ts.mgmt.migrationtool.ui.MigrationToolUI$4.doInBackground(M
igrationToolUI.java:341) [migration-tool-1.0.159.jar:na]
at com.cisco.ts.mgmt.migrationtool.ui.MigrationToolUI$4.doInBackground(M
igrationToolUI.java:338) [migration-tool-1.0.159.jar:na]
at javax.swing.SwingWorker$1.call(Unknown Source) [na:1.6.0_35]
at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) [na:1.6
.0_35]
at java.util.concurrent.FutureTask.run(Unknown Source) [na:1.6.0_35]
at javax.swing.SwingWorker.run(Unknown Source) [na:1.6.0_35]
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source
) [na:1.6.0_35]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [n
a:1.6.0_35]
at java.lang.Thread.run(Unknown Source) [na:1.6.0_35]
Caused by: com.cisco.ts.mgmt.migrationtool.exception.LdifExportFailedException:
Ldif export failed: You have provided options for scheduling this operation as a
task but options
provided for connecting to the server's tasks backend resulted in the
following error: 'Erreur de connexion'
at com.cisco.ts.mgmt.migrationtool.ldif.LdifExporterImpl$1.call(LdifExpo
rterImpl.java:121) ~[migration-tool-1.0.159.jar:na]
at com.cisco.ts.mgmt.migrationtool.ldif.LdifExporterImpl$1.call(LdifExpo
rterImpl.java:93) ~[migration-tool-1.0.159.jar:na]
at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) [na:1.6
.0_35]
at java.util.concurrent.FutureTask.run(Unknown Source) [na:1.6.0_35]
... 3 common frames omitted
14 sept. 2012 12:44:33 ERROR - Migration failed
09-14-2012 07:42 AM
Ok
It seems more of a connection issue, and that its failing to export data from opends.
Are you sure the service is running? Can you access the provisioning directory in TMS or have you already switched over to provisioning extension?
Are you sure this log is the correct one?
How are you running the migration tool? Manually from the migration folder?
/Magnus
09-14-2012 07:57 AM
This is what i have done so far :
Upgraded to TMS 13.2
Downloaded TMS PE and installed it.
Enabled TMS PE from Configuration --> General Settings
Ran Migration Tool manually from Migration Folder
Last time before i ran migration tool, i went into services to see if OPEN DS was running. Found out it was not and started it. Also changed the setting to TMS PE from TMS Agent. And after making this changes the migration tool ran upto --> Migratng Phone Books;
Without making those changes it was not connecting to TMS Provisioning Extension at all. It would fail on the first step.
09-14-2012 07:40 AM
Magnus,
Do you have a link to Migration guide ? I think it might be helpful to verify if i have done the process right.
Thanks for your help !!!
09-14-2012 08:02 AM
If the settings are ok and the opends service is running you should only have to run the migration tool and it should do the migration.
The strange thing is that I see nothing about the phonebook import in the log snippet you sent which does not help me at all
/Magnus
09-14-2012 08:16 AM
Ok i will run the tool again and see if i can what i get ... Will let you know when i have some results...
Regards
09-16-2012 07:11 PM
Hi, Also check if you have jave version 6 only on the the TMSPE server. Java version 7 has some issues specifically to migration tool.
09-17-2012 05:34 AM
Hi
Where you able to get any results on this?
/Magnus
09-18-2012 08:19 AM
09-18-2012 08:22 AM
Hi, I would suggest to open a TAC case to get this resolved once for all so our Team can help to fix the problem through webex session.
BR,
Mahesh Adithiyha
09-18-2012 08:32 AM
09-18-2012 10:10 AM
Hey
Thanks, however this still does not help much as I need to see whats the actual error is and this is in the logs. You have just taken a screenshot of the failure not the actual error.
I recommend you to open a TAC case on this or just post us the error string in the log why the migration actually failed.
/Magnus
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide