TMSPE service fail to start

[andrea.zandarin]

Hi, we have a problem with TMSPE service, it's not working anymore. The service wont start and it gives error code "1067 the process terminated unexpectedly"

TMS version is 13.2

TMS and SQLDB are on different server, and same domain

Provisioning Extension Diagnostic is not working .. " ... not running or still initializing"

At the moment we cannot provision new movi user, but the main problem is with the phonebook.

when i try to save a new phone book source, i receive an error and the log file says "unable to contact remote server" (log in attach)

I also have an error on the VCS cluster  " the VCS is unable to communicate with the TMS Provisioning Extension Services..."

The service has been running fine since we installed it, since two week ago. i checked other discussion in the forum, about basic and windows authentication on the IIS server but with no result.

any idea will be of great help

Thanks

Andrea

[thobonho]

You probably have to re-install Java 6 32-bit

[andrea.zandarin]

i have already reinstalled java, currently i have version 6 update 39.

but i feel it's something related to java.

from TMS , i can reach the SQLDB on the other server, using a normal ODBC connection, so it's not a problem of TCP and 1433 sql port.

by the way in the windows service i noticed that the service start reading a configuration file, wrapper.conf

and that file is related to some java configuration.

anyway thank for your help

Andrea

[thobonho]

Could you check your environment variables and that java is in your path? Open a command box, and type "java -version".

[aborodai · Accepted solution]

Hi,

it looks like Java issue. Could you please copy to the post last entry from tmspe wrapper log?

You can find it in TMSProvisioningExtension\app\logs folder.

It will be good to completely uninstall all Java versions and install latest Java 6

Best Regards,

Artem Borodai

[andrea.zandarin]

This is the java version:

C:\Users\z1_srv_tms>java -version
java version "1.6.0_39"
Java(TM) SE Runtime Environment (build 1.6.0_39-b04)
Java HotSpot(TM) 64-Bit Server VM (build 20.14-b01, mixed mode)

And this is the last part of the wrapper log

STATUS | wrapper  | 2013/03/04 11:15:25 | Launching a JVM...
FATAL  | wrapper  | 2013/03/04 11:15:25 | Unable to execute Java command.  The system cannot find the file specified. (0x2)
FATAL  | wrapper  | 2013/03/04 11:15:25 |     "java" -Dfile.encoding=UTF-8 -Duser.timezone=UTC -DLOG_HOME=logs -Dapp.pid="logs/tmsprovisioningextension.pid" -Ddatabase.name=mssql -Duser.language=en -Duser.country=US -XX:PermSize=128M -XX:MaxPermSize=384M -Xms256m -Xmx1024m -Djava.library.path="lib" -classpath "lib/wrapper.jar;etc/;../repo/appassembler-1.0.159.jar;../repo/security-1.0.159.jar;../repo/bouncycastle-jce-jdk13-112.jar;../repo/logging-common-1.0.159.jar;../repo/logback-classic-0.9.30.jar;../repo/logback-core-0.9.30.jar;../repo/jetty-server-7.2.2.v20101205.jar;../repo/servlet-api-2.5.jar;../repo/jetty-continuation-7.2.2.v20101205.jar;../repo/jetty-http-7.2.2.v20101205.jar;../repo/jetty-io-7.2.2.v20101205.jar;../repo/jetty-webapp-7.2.2.v20101205.jar;../repo/jetty-servlet-7.2.2.v20101205.jar;../repo/jetty-security-7.2.2.v20101205.jar;../repo/jetty-jmx-7.2.2.v20101205.jar;../repo/jetty-xml-7.2.2.v20101205.jar;../repo/jetty-util-7.2.2.v20101205.jar;../repo/jsp-2.1-glassfish-9.1.1.B60.25.p2.jar;../repo/core-3.1.1.jar;../repo/jsp-api-2.1-glassfish-9.1.1.B60.25.p2.jar;../repo/ant-1.6.5.jar;../repo/servlet-api-2.5-6.1.14.jar;../repo/commons-beanutils-1.7.0.jar;../repo/commons-codec-20041127.091804.jar;../repo/commons-collections-3.1.jar;../repo/collections-generic-4.01.jar;../repo/commons-dbcp-1.4.jar;../repo/commons-digester-1.6.jar;../repo/xml-apis-1.0.b2.jar;../repo/commons-el-1.0.jar;../repo/commons-email-1.2.jar;../repo/mail-1.4.1.jar;../repo/activation-1.1.jar;../repo/commons-io-1.4.jar;../repo/commons-lang-2.5.jar;../repo/commons-logging-1.1.1.jar;../repo/commons-management-1.0.jar;../repo/commons-net-2.0.jar;../repo/commons-pool-1.5.4.jar;../repo/ehcache-1.6.2.jar;../repo/commons-validator-1.3.1.jar;../repo/dom4j-1.6.1.jar;../repo/log4j-over-slf4j-1.6.1.jar;../repo/slf4j-api-1.6.1.jar;../repo/jcl-over-slf4j-1.6.1.jar;../repo/jul-to-slf4j-1.6.1.jar;../repo/oro-2.0.8.jar" -Dwrapper.key="IY381vF-rJOd9pN-5ux1gbMTmLIx9HSz" -Dwrapper.port=32000 -Dwrapper.jvm.port.min=31000 -Dwrapper.jvm.port.max=31999 -Dwrapper.pid=6732 -Dwrapper.version="3.5.13-st" -Dwrapper.native_library="wrapper" -Dwrapper.service="TRUE" -Dwrapper.cpu.timeout="10" -Dwrapper.jvmid=1 -Dwrapper.lang.domain=wrapper -Dwrapper.lang.folder=../lang org.tanukisoftware.wrapper.WrapperSimpleApp com.cisco.ts.mgmt.app.JettyLauncher
ADVICE | wrapper  | 2013/03/04 11:15:25 |
ADVICE | wrapper  | 2013/03/04 11:15:25 | --------------------------------------------------------------------
ADVICE | wrapper  | 2013/03/04 11:15:25 | Advice:
ADVICE | wrapper  | 2013/03/04 11:15:25 | Usually when the Wrapper fails to start the JVM process, it is
ADVICE | wrapper  | 2013/03/04 11:15:25 | because of a problem with the value of the configured Java command.
ADVICE | wrapper  | 2013/03/04 11:15:25 | Currently:
ADVICE | wrapper  | 2013/03/04 11:15:25 | wrapper.java.command=java
ADVICE | wrapper  | 2013/03/04 11:15:25 | Please make sure that the PATH or any other referenced environment
ADVICE | wrapper  | 2013/03/04 11:15:25 | variables are correctly defined for the current environment.
ADVICE | wrapper  | 2013/03/04 11:15:25 | --------------------------------------------------------------------
ADVICE | wrapper  | 2013/03/04 11:15:25 |
FATAL  | wrapper  | 2013/03/04 11:15:25 | Critical error: wait for JVM process failed

[andrea.zandarin]

thank you, re-installing java to the latest version solved the problem

even if i tried to reinstall java a couple of times!!

thank you and all you guys.

Andrea

[Magnus Ohm]

Sounds like a java issue indeed.

Completely re-install it but the wrapper log will tell you if this is the case.

/Magnus

Sent from Cisco Technical Support iPhone App

[rasimyigit]

Andrea,

i thought that the Java must have the Version 6 with 32bit and Update 33. You installed the update 39.

I think , that could be the problem

[rasimyigit]

Hi Artem,

you wrote to install the latest Java 6 32 bit. Cisco recommends the Java update 33. Now you write the latest update like 39.

What is now correct?

THX

[aborodai]

Hi Rasim,

TMSPE was tested with Java 6 update 33, but due to the secity issues we recommend to install latest update for Java 6.

Best Regards,

Artem Borodai

[andrea.zandarin]

hi, I installed latest version from www.java.com and now all works fine.

currently i have java 1.7.0_15.

regards

Andrea

[rasimyigit]

Hi,

the latest Java 6 32bit is with update 43. That is OK? That works?

THX

Sorry for my questions :-)

[aborodai]

Yes, you can use latest update. I tested with 41

Best Regards,

Artem Borodai

[rasimyigit]

Thank You Artem