PE & JAVA Issue

[Justin Ferello]

All,

We upgraded to TMS 14.2 & PE1.1, after TMS successfuly upgraded we uninstalled JAVA v6 u33 and installed JAVA v7 u17 x64.  Then when we ran the PE1.1 installer it bombed and told us to install JAVA v6 u33.  So we uninstalled JAVA v7 u17 and installed JAVA v6 u33, then we were able to run the installer fine.  PE1.1 then came online perfectly fine.

As an experiment, we stopped the PE service, uninstalled JAVA v6 u33 and re-installed JAVA v7 u17 x64.  Then we started the PE service, it failed immedialty and told us that Windows was unable to start the service.  We then uninstalled JAVA v7 u17 x64 and installed JAVA v7 u17 x86, then tried to start the PE service.  This time we got a progress bar a for a few seconds then Windows told us it was unable to start the service.

Finally we uninstall JAVA v7 u17 x86 and re-installed JAVA v6 u33, started the PE service, waited a few moments and then TMS & PE were happy again.

Does PE1.1 really not support JAVA v7 yet?  Also we are running Windows 2008 R2 x64 with all updates installed.

Thank you,

Justin Ferello
Technical Support Specialist
KBZ, a Cisco Authorized Distributor
http://www.kbz.com
e/v: justin.ferello@kbz.com       

[Patrick Sparkman]

I'm running the same configuration you are, Windows 2008 R2 x64, with the most recent update of Java 7 without issue.  In my case, I updated our server from Java 6 to 7 prior to the TMSPE 1.1 install.

[Justin Ferello]

Patrick,

Interesting, wonder why mine won't work then.  I guess I will need to do my "experiment" again and gather the PE logs to find out what is going on.

Thank you,

Justin Ferello
Technical Support Specialist
KBZ, a Cisco Authorized Distributor
http://www.kbz.com
e/v: justin.ferello@kbz.com

[Patrick Sparkman]

The only issue I ran into was it didn't allow me to install directly onto TMSPE 1.0, as I had to uninstall it before installing 1.1.  Perhaps that had something to do with updating Java, I don't know, but even after doing that uninstall of 1.0 and install of 1.1, everything is working fine.

[mahkrish]

Hi Justin, Can you share the errors seen in PE installation from C:\Program Files\TANDBERG\TMS\TMSProvisioningExtension\app\logs when hit the error.

BR, Mahesh Adithiyha

[Justin Ferello]

Mahkrish,

I will pull the logs tonight after doing some testing.

Thank you,

Justin Ferello
Technical Support Specialist
KBZ, a Cisco Authorized Distributor
http://www.kbz.com
e/v: justin.ferello@kbz.com

[thobonho · Accepted solution]

Hi

Provisioning Extension actually uses a 3rd-party application that wraps the java application made by Cisco into a Windows service. That 3rd-party application launches java binaries by using the shortcut "java", which is only recognized by the system if the PATH variable is correctly configured.

To quickly check if it's the case, issue the command "java -version" in a command box. If the command is taken, it will display which version is currently in use on your machine. If not, you'll need to add the path to the java installation folder in your PATH variable as shown on the screenshot below :

Note that you need to reboot your system after editing the PATH to make it aware of the new configuration. It's probably what you haven't done when you tried several java versions and I presume that your PATH was still pointing to Java v6 in fact...

Hope that helps,

Thomas

recognised

[Justin Ferello]

Thomas,

I will doublecheck your concept this evening when I do some more testing.

Thank you,

Justin Ferello
Technical Support Specialist
KBZ, a Cisco Authorized Distributor
http://www.kbz.com
e/v: justin.ferello@kbz.com