cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

upgraded from Integrity 10.6 to Integrity 10.7 and the "Integrity Server 10" service fails to remain in "Started" status. My logs show the following: ATAL [mksis.IntegrityServer] Service AppConfig not started due to errors: Service mks:name=IM not started

SOLVED
Highlighted
Newbie

upgraded from Integrity 10.6 to Integrity 10.7 and the "Integrity Server 10" service fails to remain in "Started" status. My logs show the following: ATAL [mksis.IntegrityServer] Service AppConfig not started due to errors: Service mks:name=IM not started

I upgraded from Integrity 10.6 to Integrity 10.7. The issues I'm having is the "Integrity Server 10" service fails to remain in "Started" status. My logs show the following:

FATAL [mksis.IntegrityServer] Service AppConfig not started due to errors: Service mks:name=IM not started due to errors: Unable to start IM service: Incorrect syntax near '.'.

I had to roll back to Integrity 10.6.

The steps I took for upgrade:

1. Stop the Integrity Server 10 service via cmd line within the 10.6 bin folder "mksis stop"

2. Remove the service "mksis remove"

3. Installed Integrity server 10.7 using 'Upgrade of an existing server"

4. Ran "isutil -c migrateserverconfig'

5. Started the Integrity Server 10 service via cmd line within the 10.7 bin folder "mksis start"

It proceeds to start then stops on it's own with the error below.

FATAL [mksis.IntegrityServer] Service AppConfig not started due to errors: Service mks:name=IM not started due to errors: Unable to start IM service: Incorrect syntax near '.'.

Tags (1)
1 ACCEPTED SOLUTION

Accepted Solutions
Highlighted

Re: upgraded from Integrity 10.6 to Integrity 10.7 and the "Integrity Server 10" service fails to remain in "Started" status. My logs show the following: ATAL [mksis.IntegrityServer] Service AppConfig not started due to errors: Service mks:name=IM not sta

Debbie,

I would recommend opening a new case with PTC Technical Support to take a closer look at the problem. Please provide them a copy of the log files in C:/Program Files/Integrity/IntegrityServer10_7/log

View solution in original post

7 REPLIES 7
Highlighted

Re: upgraded from Integrity 10.6 to Integrity 10.7 and the "Integrity Server 10" service fails to remain in "Started" status. My logs show the following: ATAL [mksis.IntegrityServer] Service AppConfig not started due to errors: Service mks:name=IM not sta

Debbie,

could you please attach the configuration files from the directory .../config/properites and the file .../config/mksservice.conf ?

Thanks,

Peter

Highlighted

Re: upgraded from Integrity 10.6 to Integrity 10.7 and the "Integrity Server 10" service fails to remain in "Started" status. My logs show the following: ATAL [mksis.IntegrityServer] Service AppConfig not started due to errors: Service mks:name=IM not sta

Debbie,

did you choose the option "Upgrade an exisitng server" and then install the 10.7 server within a new directory?

I do not think that this works.

Regards,

Peter

Highlighted

Re: upgraded from Integrity 10.6 to Integrity 10.7 and the "Integrity Server 10" service fails to remain in "Started" status. My logs show the following: ATAL [mksis.IntegrityServer] Service AppConfig not started due to errors: Service mks:name=IM not sta

Yes, I installed Integrity server 10.7 using 'Upgrade of an existing server". I used a new directory C:\Profram Files\Integrity\IntegrityServer10_7 where as my old one sites at C:\Profram Files\Integrity\IntegrityServer10_6

Highlighted

Re: upgraded from Integrity 10.6 to Integrity 10.7 and the "Integrity Server 10" service fails to remain in "Started" status. My logs show the following: ATAL [mksis.IntegrityServer] Service AppConfig not started due to errors: Service mks:name=IM not sta

Debbie,

could you please attach the configuration files from the directory .../config/properites and the file .../config/mksservice.conf ?

Thanks,

Peter

Highlighted

Re: upgraded from Integrity 10.6 to Integrity 10.7 and the "Integrity Server 10" service fails to remain in "Started" status. My logs show the following: ATAL [mksis.IntegrityServer] Service AppConfig not started due to errors: Service mks:name=IM not sta

#*********************************************************************
# Integrity Server Properties
#*********************************************************************

#*********************************************************************
# Title to use when running as a console. It is also used in some messages.
# The default is set to "Integrity Server <version>".
#*********************************************************************
mks.console.title=Integrity Server 10

#*********************************************************************
# Log file to use for output logging; default is startup.log.ROLLNUM.
#
# The name may contain ROLLNUM or YYYYMMDD as place holder tokens.
# ROLLNUM is used in combination with log file rolling and represents
# the log file number. YYYYMMDD is required when the log file rolling
# is date based (mks.logfile.rollmode=DATE) and represents the date
# the log file is for.
#
# By default log rolling based on file size is performed.
#*********************************************************************
mks.logfile=C:/Program Files/Integrity/IntegrityServer10_7/log/startup.ROLLNUM.log

# The name of the Java Native Library (JNI)
mks.native_library=mksservice

#*********************************************************************
# mks.java.additonal.<n>
# Additional Java parameters to pass to Java when it is launched.
# These are the parameters for the Java Virtual Machine.
# Each element has a property name which starts with mks.java.additional.
# and ends with a unique number between 1 and 60. The numbering
# and ordering in the file need not be continuous, but avoid duplicates.
#*********************************************************************
mks.java.additional.1=-Xms1024m
mks.java.additional.2=-Xmx1024m
mks.java.additional.3=-Xss512k
mks.java.additional.4=-Dprogram.name=run.bat
mks.java.additional.5=-Djboss.identity.domain=MKS
mks.java.additional.6=-Dmks.safemode=false
mks.java.additional.7=-Dmks.safemode.password=<secret>
mks.java.additional.8=-Dmks.unattended.startup=true
mks.java.additional.9=-Dmks.master.key=fake_master_key
mks.java.additional.10=-Dxmbean.metadata.xml.validate=true
mks.java.additional.11=-Djboss.server.base.dir="C:/Program Files/Integrity/IntegrityServer10_7/server"
mks.java.additional.12=-Djboss.server.base.url="file:/C:/Program Files/Integrity/IntegrityServer10_7/server"
mks.java.additional.13=-Djboss.server.log.dir="C:/Program Files/Integrity/IntegrityServer10_7/log"
mks.java.additional.14=-Djboss.server.temp.dir="C:/Program Files/Integrity/IntegrityServer10_7/server/mks/tmp"
mks.java.additional.15=-Djava.endorsed.dirs="C:/Program

Files/Integrity/IntegrityServer10_7/server/lib/endorsed"
mks.java.additional.16=-Djava.awt.headless=true
mks.java.additional.17=-Dmks.installDir="C:/Program Files/Integrity/IntegrityServer10_7"
mks.java.additional.18=-Dmks.install=server
mks.java.additional.19=-Duser.language=en
mks.java.additional.20=-server
# Used to define partition name for clustering
mks.java.additional.21=-Djboss.partition.name=MKS
mks.java.additional.22=-Djboss.partition.member.name=%MEMBER_NAME%
mks.java.additional.23=-Dorg.apache.catalina.connector.RECYCLE_FACADES=true
mks.java.additional.24=-

XX:CompileCommand=exclude,com/ibm/as400/access/AS400JDBCPreparedStatement,commonExecuteBefor

e
mks.java.additional.25=-XX:+UseCompressedOops
mks.java.additional.26=-XX:+HeapDumpOnOutOfMemoryError
mks.java.additional.27=-Djava.util.Arrays.useLegacyMergeSort=true
mks.java.additional.28=-Djdk.lang.Process.allowAmbiguousCommands=true
mks.java.additional.29=-XX:+UseConcMarkSweepGC
mks.java.additional.30=-XX:+UseParNewGC
mks.java.additional.31=-XX:CompileCommand=exclude,ca/odell/glazedlists/FilterList,constrained
mks.java.additional.32=-XX:CompileCommand=exclude,ca/odell/glazedlists/impl/filter/TextMatchers,matches
mks.java.additional.33=-Dhttps.protocols="TLSv1,TLSv1.1,TLSv1.2"
mks.java.additional.34=-Djdk.tls.client.protocols="TLSv1,TLSv1.1,TLSv1.2"

# User country in case of chinese traditional or simplified. For pseudo server this property is required.
#mks.java.additional.35=-Duser.country=

# Used to change the default location of temporary files created by the server. See also
# jboss.server.temp.dir above and mks.user.temp.dir defined in is.properties.
#mks.java.additional.36=-Djava.io.tmpdir=

# If verbose gc logging is turned on, the filename to log to
# An existing file is automatically renamed with .# on the end
mks.java.gcfile="C:/Program Files/Integrity/IntegrityServer10_7/log/gc.out"

# The command to use when launching a JVM.
mks.java.command=..\jre\bin\java.exe

#*********************************************************************
# Other Properties - modify these only under advice of PTC services team
#*********************************************************************

#*********************************************************************
# mks.java.classpath.<n> --- Java Classpath to use.
# Each element has a property name which starts with mks.java.classpath.
# and ends with a unique number between 1 and 40. The numbering
# and ordering in the file need not be continuous, but avoid duplicates.
#*********************************************************************
mks.java.classpath.1=C:/Program Files/Integrity/IntegrityServer10_7/server/lib/mksservice.jar
mks.java.classpath.2=C:/Program Files/Integrity/IntegrityServer10_7/server/bin/run.jar

# Class to execute when the service starts the application.
mks.java.mainclass=org.tanukisoftware.wrapper.WrapperSimpleApp

#*********************************************************************
# mks.app.parameter.<n>
# Application parameters to pass to the application when it is launched.
# Each element has a property name which starts with mks.java.parameter.
# and ends with a unique number between 1 and 40. The numbering
# and ordering in the file need not be continuous, but avoid duplicates.
#*********************************************************************
mks.app.parameter.1=org.jboss.Main
mks.app.parameter.2=-c
mks.app.parameter.3=mks

#*********************************************************************
# Format of output for console. The format consists of the tokens
# 'L' for log level,
# 'D' for thread,
# 'T' for time, and
# 'M' for message.
# If the property is missing or commented out, then the default value 'M'
# will be used. Setting the property to blank will disable console output.
# E.g. mks.console.format=LTM
# STATUS | 2005/11/16 11:00:25 | --> MKS Started as Console
# STATUS | 2005/11/16 11:00:25 | Launching a JVM...
#*********************************************************************
mks.console.format=M

#*********************************************************************
# Log level for console output. Valid log levels include:
# NONE for no output,
# FATAL to only show fatal error messages,
# ERROR to show all error messages,
# STATUS to show all state changes (the default),
# INFO to show all JVM output and informative messages, and
# DEBUG to show detailed debug information.
# Default is STATUS. Note that at STATUS level, hitting CTRL-BREAK does
# not produce a stack trace when running in console mode.
#*********************************************************************
mks.console.loglevel=STATUS

#*********************************************************************
# Control log file rolling for the startup.log file. The valid values
# are:
# NONE disable log rolling
# SIZE roll when the size specified by mks.logfile.maxsize
# is exceeded
# WRAPPER roll on launch of the service
# JVM roll on startup of the JVM
# SIZE_OR_WRAPPER combination of SIZE or WRAPPER rolling
# SIZE_OR_JVM combination of SIZE or JVM rolling
# DATE roll based on log message timestamp and a format token
# of the form YYYYMMDD in the log file name property
# mks.logfile
#
#*********************************************************************
mks.logfile.rollmode=SIZE

#*********************************************************************
# Format of output for log file. The format consists of the tokens
# 'L' for log level,
# 'D' for thread,
# 'T' for time, and
# 'M' for message.
# If the property is missing or commented out, then the default value 'LTM'
# will be used. Setting the property to blank will disable file logging.
# E.g. mks.logfile.format=LTM
# STATUS | 2005/11/16 11:00:25 | --> MKS Started as Console
# STATUS | 2005/11/16 11:00:25 | Launching a JVM...
#*********************************************************************
mks.logfile.format=LTM

#*********************************************************************
# Log level for console output. Valid log levels include:
# NONE for no output,
# FATAL to only show fatal error messages,
# ERROR to show all error messages,
# STATUS to show all state changes (the default),
# INFO to show all JVM output and informative messages, and
# DEBUG to show detailed debug information.
#*********************************************************************
mks.logfile.loglevel=STATUS

#*********************************************************************
# Maximum size that the log file will be allowed to grow to before the log
# is rolled. Size is specified in bytes may be abbreviated with the 'k' (kb)
# or 'm' (mb) suffix. The default value of 0 disables log rolling.
#*********************************************************************
mks.logfile.maxsize=10m

#*********************************************************************
# Maximum number of rolled log files which will be allowed before old files
# are deleted. The default value of 0 implies no limit.
#*********************************************************************
mks.logfile.maxfiles=50

#*********************************************************************
# Log Level for sys/event log output; default is NONE.
# Valid loglevels are the same as the other loglevel related properties.
#*********************************************************************
mks.syslog.loglevel=NONE

#*********************************************************************
# mks.java.library.path.<n> --- Java library path to use.
# Each element has a property name which starts with mks.java.library.path.
# and ends with a unique number between 1 and 40. The numbering
# and ordering in the file need not be continuous, but avoid duplicates.
#*********************************************************************
mks.java.library.path.1=C:/Program Files/Integrity/IntegrityServer10_7/server/lib
mks.java.library.path.2=C:/Program Files/Integrity/IntegrityServer10_7/server/mks/bin

#*********************************************************************
# Disable the service restart mechanism completely. Valid values are:
# TRUE disable the service restart mechanism
# FALSE enable the service restart mechanism
#*********************************************************************
mks.disable_restarts=FALSE

#*********************************************************************
# Number of seconds to allow between pinging the JVM and obtaining the
# response. 0 means never time out.
#*********************************************************************
mks.ping.timeout=300

#*********************************************************************
# Number of seconds to wait between startup attempts.
#*********************************************************************
mks.restart.delay=60

#*********************************************************************
# Number of startup attempts to try before giving up.
#*********************************************************************
mks.max_failed_invocations=20


#*********************************************************************
# Windows NT/2000/XP/2003 Service Properties
#*********************************************************************
# WARNING - Do not modify any of these properties when an application
# using this configuration file has been installed as a service.
# Please uninstall the service before modifying this section. The
# service can then be reinstalled.
#*********************************************************************
mks.ntservice.name=Integrity Server 10
mks.ntservice.displayname=Integrity Server 10
mks.ntservice.description=Integrity Enterprise Application Lifecycle Management Service

#*********************************************************************
# mks.ntservice.dependency.<n>
# Names of any other Services or groups which must be running before
# this service can be started.
# Each element has a property name which starts with mks.ntservice.dependency.
# and ends with an integer number counting up from 1. There can be no
# missing numbers.
#*********************************************************************
mks.ntservice.dependency.1=

# Mode in which the service is installed. AUTO_START or DEMAND_START
mks.ntservice.starttype=AUTO_START

# Allow the service to interact with the desktop.
mks.ntservice.interactive=false


Highlighted

Re: upgraded from Integrity 10.6 to Integrity 10.7 and the "Integrity Server 10" service fails to remain in "Started" status. My logs show the following: ATAL [mksis.IntegrityServer] Service AppConfig not started due to errors: Service mks:name=IM not sta

The property file looks OK.

Whenever I did such a Server Upgrade I installed the new Server version using the option "Install new server", not as "Upgrade exisitng server".

I am not sure if this is the cause of your problem ...

Highlighted

Re: upgraded from Integrity 10.6 to Integrity 10.7 and the "Integrity Server 10" service fails to remain in "Started" status. My logs show the following: ATAL [mksis.IntegrityServer] Service AppConfig not started due to errors: Service mks:name=IM not sta

Debbie,

I would recommend opening a new case with PTC Technical Support to take a closer look at the problem. Please provide them a copy of the log files in C:/Program Files/Integrity/IntegrityServer10_7/log

View solution in original post

Announcements