cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1246
Views
0
Helpful
15
Replies

TMSPE Upgrade Fails

Linus98
Level 1
Level 1

Hi all,

 

argh. My TMSPE Migartion faild because TMS Agent Service was not running. (Unable to communicate with the TMS Agent service. Quitting the Migration.)

 

Can I restart the Migartion Wizard so that TMSPE migartion succseed and i can go further with my Migration. Goal is to migrate TMS 13.2.1 to newest TMS Version including a change of Server hardware.

 

Regards Timo

15 Replies 15

Patrick Sparkman
VIP Alumni
VIP Alumni

Verify that the TMS Agent is turned on and running on the TMS server.  Once you do that, simply re-run the migration tool.

Also, take a look at the TMSPE Deployment Guide 1.0, there are some troubleshooting steps starting on pg 69 that might help with common issues.

Found the Migration Tool and started it again, failed again.

20 Aug 2015 14:58:51 INFO  - Migration started
20 Aug 2015 14:58:51 INFO  - Exporting data from OpenDS
20 Aug 2015 14:59:41 INFO  - Export ldif command output: Exportieren Aufgabe 20150820165938376 wurde zum sofortigen Starten geplant
[20/Aug/2015:16:59:38 +0200] severity="NOTICE" msgCount=0 msgID=9896349 message="Exportieren-Aufgabe 20150820165938376 startete die Ausführung"
[20/Aug/2015:16:59:38 +0200] severity="INFORMATION" msgCount=1 msgID=10487422 message="Exportieren nach C:\Programme\TANDBERG\TMS\TMSProvisioningExtension\migration-tool\export\tmsagent-provisioning.ldif"
[20/Aug/2015:16:59:40 +0200] severity="NOTICE" msgCount=2 msgID=8847447 message="30 Einträge exportiert und 2520 übersprungen in 1 Sekunden (durchschnittliche Rate 18,5/Sek.)"
That lin tells that 30 Entries were exported and 2520 skipped.
[20/Aug/2015:16:59:40 +0200] severity="NOTICE" msgCount=3 msgID=9896350 message="Exportieren-Aufgabe 20150820165938376 beendete die Ausführung"
Exportieren Aufgabe 20150820165938376 erfolgreich abgeschlossen That lin tells that Export-Task succeed.

20 Aug 2015 14:59:41 INFO  - Deleting existing data
20 Aug 2015 14:59:42 ERROR - Encountered migration error.
20 Aug 2015 14:59:42 ERROR - Migration failed

Any Idea ?!

 

Regards Timo

 

What version of Java is installed on the TMS server?

1.7 (67) - Last available Version for W2K3.

Regards Timo

 

TMSPE 1.0 requires Java 6 Update 33. You can download Java 6 for W2K3 from www.oldapps.com/java.php. Because you're running such and old version, I'd suspect that is the issue you're facing with the migration. 

Hi Patrick,

 

thanks for the hint, but with 1.6.33 I'm runnig in a JAVA error:

 

24.08.2015 15:52:46 com.sun.jersey.api.client.ClientResponse getEntity
SCHWERWIEGEND: A message body reader for Java class com.cisco.ts.mgmt.lib.api.mo
del.ApiResponse, and Java type class com.cisco.ts.mgmt.lib.api.model.ApiResponse
, and MIME media type text/html; charset=ISO-8859-1 was not found
24.08.2015 15:52:46 com.sun.jersey.api.client.ClientResponse getEntity
SCHWERWIEGEND: The registered message body readers compatible with the MIME medi
a type are:
*/* ->
  com.sun.jersey.core.impl.provider.entity.FormProvider
  com.sun.jersey.core.impl.provider.entity.StringProvider
  com.sun.jersey.core.impl.provider.entity.ByteArrayProvider
  com.sun.jersey.core.impl.provider.entity.FileProvider
  com.sun.jersey.core.impl.provider.entity.InputStreamProvider
  com.sun.jersey.core.impl.provider.entity.DataSourceProvider
  com.sun.jersey.core.impl.provider.entity.XMLJAXBElementProvider$General
  com.sun.jersey.core.impl.provider.entity.ReaderProvider
  com.sun.jersey.core.impl.provider.entity.DocumentProvider
  com.sun.jersey.core.impl.provider.entity.SourceProvider$StreamSourceReader
  com.sun.jersey.core.impl.provider.entity.SourceProvider$SAXSourceReader
  com.sun.jersey.core.impl.provider.entity.SourceProvider$DOMSourceReader
  com.sun.jersey.core.impl.provider.entity.XMLRootElementProvider$General
  com.sun.jersey.core.impl.provider.entity.XMLListElementProvider$General
  com.sun.jersey.core.impl.provider.entity.XMLRootObjectProvider$General
  com.sun.jersey.core.impl.provider.entity.EntityHolderReader

24 Aug 2015 13:52:46 ERROR - Encountered migration error.
24 Aug 2015 13:52:46 ERROR - Migration failed

 

Regards Timo

You're getting errors because you're running an unsuported and way out of date version of Java that TMSPE doesn't support. You need to update Java on your TMS server to Java 6 Update 33. Also, don't install anything newer than what the TMSPE deployment guides state, as that will cause TMSPE to have unknown issues, you should be running exactly the version noted in the guides. 

Patrick,

6 Update 33 is installed which is aka 1.6.0.33 . See Screenshot.

Regards Timo

 

Ah, I didn't recognize or know 1.6.33 was just a different way of saying it. Knowing that, I take it you rolled back Java then from version 7 Update 67? You should reinstall TMSPE then, running a newer version of Java and then rolling back to a different version while TMSPE is already installed can cause some issues. 

Correct, I rolled back to 6 Update 33.

So you suggest to install TMSPE once again with Java 6 Update 33 installed now ?!

Just Need torerun Setup again ?

 

Regards Timo

 

 

Yes, just run the installer again, shouldn't need to uninstall.

Patrick,

 

Housten we have a problem:

 

a. A reinstall was not possible, so i need to deinstall an install again.

b. TMS Agent allways stops immediately after I started the service.

 

Any Idea....

 

Regards Timo

Check the TMS Agent logs located under:

C:\ProgramFiles\TANDBERG\TMS\wwwTMS\Data\Logs\tmsdebug\log-tmsagent.txt

Does it give you any idea why it might be stopping?

Hi Patrick,

 

sorry for the delay:

 

TMS Version 13.2.1
11:22:09,492 [TMSAgentWindowsService.TMSAgentWindowsService] WARN  TMSAgentWindowsService.TMSAgentWindowsService - Service startup...
11:22:09,507 [TMSAgentWindowsService.TMSAgentWindowsService] WARN  TMSAgentWindowsService.TMSAgentWindowsService - OpenDS service is not running, starting now...
11:22:20,494 [TMSAgentWindowsService.TMSAgentWindowsService] WARN  TMSAgentWindowsService.TMSAgentWindowsService - OpenDS service started
11:23:20,434 [TMSAgentWindowsService.TMSAgentWindowsService] WARN  TMSAgentWindowsService.TMSAgentWindowsService - Starting the TMS agent...
11:23:20,465 [TMSAgentWindowsService.TMSAgentWindowsService] WARN  TMSAgentWindowsService.TMSAgentWindowsService - Start script execution failed. Exit Code: 1 Output: Starting Argon
Expecting java located at: C:\Programme\TANDBERG\TMS\Provisioning\jre
Expecting opends located at: C:\Programme\TANDBERG\TMS\provisioning\opends-2.0
 Error: Der Prozess kann nicht auf die Datei zugreifen, da sie von einem anderen Prozess verwendet wird. (Translation: The process can not access the file because it is being used by another process)

 

Regards Timo