Gateway Service

Hi everyone !!! Installed the latest version of Java and my Ignition Gateway service now fails on error 1067. What registry fixes do I need to do to correct this ? I am using 7.3.

( Previous to this I was unable to launch an application due to error httpresponseexception: 505:http version not supported. Don’t see any references to this in the forum and it was originally what I was trying to fix. The program was running from designer )

Wrapper Log

STATUS | wrapper | 2011/12/17 22:54:04 | --> Wrapper Started as Service
STATUS | wrapper | 2011/12/17 22:54:04 | Java Service Wrapper Standard Edition 64-bit 3.5.4
STATUS | wrapper | 2011/12/17 22:54:04 | Copyright © 1999-2010 Tanuki Software, Ltd. All Rights Reserved.
STATUS | wrapper | 2011/12/17 22:54:04 |
STATUS | wrapper | 2011/12/17 22:54:05 | Licensed to Inductive Automation for Ignition Gateway
STATUS | wrapper | 2011/12/17 22:54:05 |
STATUS | wrapper | 2011/12/17 22:54:05 | Launching a JVM…
FATAL | wrapper | 2011/12/17 22:54:05 | Unable to execute Java command. The system cannot find the file specified. (0x2)
FATAL | wrapper | 2011/12/17 22:54:05 | “java” -XX:PermSize=64m -XX:MaxPermSize=128m -XX:+UseConcMarkSweepGC -XX:+CMSClassUnloadingEnabled -XX:+CMSPermGenSweepingEnabled -Ddata.dir=data -Dorg.apache.catalina.loader.WebappClassLoader.ENABLE_CLEAR_REFERENCES=false -Xms256m -Xmx1024m -Djava.library.path=“lib” -classpath “lib/wrapper.jar;lib/annotations-api.jar;lib/catalina.jar;lib/catapult.jar;lib/el-api.jar;lib/log4j-1.2.15-min.jar;lib/servlet-api.jar;lib/slf4j-api-1.5.3.jar;lib/slf4j-log4j12-1.5.3.jar;lib/tomcat-coyote.jar;lib/tomcat-juli.jar;lib/mail.jar” -Dwrapper.key=“C3NVJ7C-RcjcUsl1HhPJb5jAMC0DECff” -Dwrapper.port=32000 -Dwrapper.jvm.port.min=31000 -Dwrapper.jvm.port.max=31999 -Dwrapper.version=“3.5.4-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.inductiveautomation.catapult.Catapult
ADVICE | wrapper | 2011/12/17 22:54:05 |
ADVICE | wrapper | 2011/12/17 22:54:05 | --------------------------------------------------------------------
ADVICE | wrapper | 2011/12/17 22:54:05 | Advice:
ADVICE | wrapper | 2011/12/17 22:54:05 | Usually when the Wrapper fails to start the JVM process, it is
ADVICE | wrapper | 2011/12/17 22:54:05 | because of a problem with the value of the configured Java command.
ADVICE | wrapper | 2011/12/17 22:54:05 | Currently:
ADVICE | wrapper | 2011/12/17 22:54:05 |
ADVICE | wrapper | 2011/12/17 22:54:05 | Please make sure that the PATH or any other referenced environment
ADVICE | wrapper | 2011/12/17 22:54:05 | variables are correctly defined for the current environment.
ADVICE | wrapper | 2011/12/17 22:54:05 | --------------------------------------------------------------------
ADVICE | wrapper | 2011/12/17 22:54:05 |
FATAL | wrapper | 2011/12/17 22:54:05 | Critical error: wait for JVM process failed

Another wrapper log

WARN | wrapper | 2011/12/17 11:35:26 | An encoding declaration is missing from the top of configuration file:
WARN | wrapper | 2011/12/17 11:35:26 | C:\PROGRA~1\INDUCT~1\Ignition\wrapper-license.conf
WARN | wrapper | 2011/12/17 11:35:26 | trying the system encoding.
WARN | wrapper | 2011/12/17 12:20:14 | An encoding declaration is missing from the top of configuration file:
WARN | wrapper | 2011/12/17 12:20:14 | C:\PROGRA~1\INDUCT~1\Ignition\wrapper-license.conf
WARN | wrapper | 2011/12/17 12:20:14 | trying the system encoding.
WARN | wrapper | 2011/12/17 12:25:31 | An encoding declaration is missing from the top of configuration file:
WARN | wrapper | 2011/12/17 12:25:31 | C:\PROGRA~1\INDUCT~1\Ignition\wrapper-license.conf
WARN | wrapper | 2011/12/17 12:25:31 | trying the system encoding.
WARN | wrapper | 2011/12/17 12:35:04 | An encoding declaration is missing from the top of configuration file:
WARN | wrapper | 2011/12/17 12:35:04 | C:\PROGRA~1\INDUCT~1\Ignition\wrapper-license.conf
WARN | wrapper | 2011/12/17 12:35:04 | trying the system encoding.
WARN | wrapper | 2011/12/17 22:18:23 | An encoding declaration is missing from the top of configuration file:
WARN | wrapper | 2011/12/17 22:18:23 | C:\PROGRA~1\INDUCT~1\Ignition\wrapper-license.conf
WARN | wrapper | 2011/12/17 22:18:23 | trying the system encoding.
WARN | wrapper | 2011/12/17 22:23:17 | An encoding declaration is missing from the top of configuration file:
WARN | wrapper | 2011/12/17 22:23:17 | C:\PROGRA~1\INDUCT~1\Ignition\wrapper-license.conf
WARN | wrapper | 2011/12/17 22:23:17 | trying the system encoding.
WARN | wrapper | 2011/12/17 22:43:55 | An encoding declaration is missing from the top of configuration file:
WARN | wrapper | 2011/12/17 22:43:55 | C:\PROGRA~1\INDUCT~1\Ignition\wrapper-license.conf
WARN | wrapper | 2011/12/17 22:43:55 | trying the system encoding.
WARN | wrapper | 2011/12/17 22:47:51 | An encoding declaration is missing from the top of configuration file:
WARN | wrapper | 2011/12/17 22:47:51 | C:\PROGRA~1\INDUCT~1\Ignition\wrapper-license.conf
WARN | wrapper | 2011/12/17 22:47:51 | trying the system encoding.
WARN | wrapper | 2011/12/17 22:54:04 | An encoding declaration is missing from the top of configuration file:
WARN | wrapper | 2011/12/17 22:54:04 | C:\PROGRA~1\INDUCT~1\Ignition\wrapper-license.conf
WARN | wrapper | 2011/12/17 22:54:04 | trying the system encoding.

Ignition.conf file … so much for my weekend of working with ignition :wink:


Configuration files must begin with a line specifying the encoding

of the the file.


Wrapper License Properties (Ignored by Community Edition)


Professional and Standard Editions of the Wrapper require a valid

License Key to start. Licenses can be purchased or a trial license

requested on the following pages:

Include file problems can be debugged by removing the first ‘#’

from the following line:


The Wrapper will look for either of the following optional files for a

valid License Key. License Key properties can optionally be included

directly in this configuration file.

#include ./wrapper-license.conf

The following property will output information about which License Key(s)

are being found, and can aid in resolving any licensing problems.



Wrapper Localization


Specify the locale which the Wrapper should use. By default the system

locale is used.

#wrapper.lang=en_US # en_US or ja_JP

Specify the location of the Wrapper’s language resources. If these are

missing, the Wrapper will default to the en_US locale.



Wrapper Java Properties


Java Application

Locate the java binary on the system PATH:

Specify a specific java binary:


Tell the Wrapper to log the full generated Java command line.

Java Main class. This class must implement the WrapperListener interface

or guarantee that the WrapperManager class is initialized. Helper

classes are provided to do this for you. See the Integration section

of the documentation for details.

Java Classpath (include wrapper.jar) Add class path elements as

needed starting from 1

Java Library Path (location of Wrapper.DLL or

Java Bits. On applicable platforms, tells the JVM to run in 32 or 64-bit mode.

Java Additional Parameters,server=y,suspend=n,address=8000

Initial Java Heap Size (in MB)

Maximum Java Heap Size (in MB)

Application parameters. Add parameters as needed starting from 1



Wrapper Logging Properties


Enables Debug output from the Wrapper.


Format of output for the console. (See docs for formats)


Log Level for console output. (See docs for log levels)


Log file to use for wrapper output logging.


Format of output for the log file. (See docs for formats)


Log Level for log file output. (See docs for log levels)


Maximum size that the log file will be allowed to grow to before

the log is rolled. Size is specified in bytes. The default value

of 0, disables log rolling. May abbreviate with the ‘k’ (kb) or

‘m’ (mb) suffix. For example: 10m = 10 megabytes.


Maximum number of rolled log files which will be allowed before old

files are deleted. The default value of 0 implies no limit.


Log Level for sys/event log output. (See docs for log levels)



Wrapper General Properties


Allow for the use of non-contiguous numbered properties


Title to use when running as a console

wrapper.console.title=Ignition Gateway


Wrapper JVM Checks


Detect DeadLocked Threads in the JVM. (Requires Standard Edition)


Out Of Memory detection.

#wrapper.filter.message.1000=The JVM has run out of memory.



Wrapper Email Notifications. (Requires Professional Edition)


Common Event Email settings.<SMTP_Host>[%WRAPPER_HOSTNAME%:%WRAPPER_NAME%:%WRAPPER_EVENT_NAME%] Event Notification

Configure the log attached to event emails.

Enable specific event emails.

Specify custom mail content JVM was restarted.\n\nPlease check on its status.\n


Wrapper Windows NT/2000/XP 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.

Name of the service

Display name of the service

wrapper.displayname=Ignition Gateway

Description of the service

wrapper.description=Ignition Gateway

Service dependencies. Add dependencies as needed starting from 1


Mode in which the service is installed. AUTO_START, DELAY_START or DEMAND_START


Allow the service to interact with the desktop.



Hi folks ! Can’t seem to get to the bottom of my Gateway Service not starting ( Error 1067 ) so I am considering uninstalling and re installing Ignition. Problem is that I have a lot of work into a project with no backup and can’t backup now because gateway won’t run. Catch 22. Can anyone tell me how I can manually backup my project files so that I can re install ignition and maybe keep on going here on my development. I’ve been stuck for a day and a half. Thanks !

I’m not completely comfortable recommending how to wipe your gateway, but here goes:

I believe that the last 5 versions of your projects should be stored here {Install Dir}\data\db\autobackup based on Colby’s post.

If in doubt, I’d back up the whole folder. Do you have another computer that you could Install Ignition on and do the restore from the autobackup on as a (safe) test? I know there is a safe way of doing what you want, but I’m not comfortable stepping you through it.

Hey Nathan. I appreciate the reply… even though its the weekend before Christmas. Quick update here. I completely uninstalled Java and re installed version 29 ( also did 27 but I thought that 29 was the original version ). So the Ignition Gateway Service starts up now but the Ignition Gateway does not start from the Windows Program menu. I am deciphering the wrapper logs and gateway logs etc. Also the link to Designer is broken so it will not even try to start.

Now regarding your idea to use the auto backup files. I did see these. I was not clear on whether they contained the project files. I will attempt to install on my backup computer and see if I can move the latest version from this backup directory into the new install. Thanks !!

No problem. Try searching the forum. I believe Colby has explained the backup recovery process. To the best of my memory, it’s simply a matter of copying a file or folder to the right place. Everything is stored in the “internal database”, which is local instance of HSQL running on the gateway.

I’m browsing on (a renewable) 30 free minutes of Wifi at 30,000 feet compliments of Ebay and Delta. I’m also on my Macbook Air that doesn’t have Ignition installed.

update: Found it. Colby explains how you copy the backup over the db folder to “manually recover” your Ignition instance below.


This would be a good topic for a tutorial and/or training video.

Okay… some good news. I did a new install and was able to get at my projects by copying the autobackup files to the db directory.

Bad news… is that something is broken in my project. This was my original issue that made me install a new version of Java. On launching I am getting an exception “CouldNotLoad ArgumentException” wrapped exception HTTP response code 505. More details to come perhaps on a new thread. I will try to uninstall and recover my original computer 1st.

Okay. I would like to wrap up this post for future users by saying that uninstalling Ignition and re installing got me back to where I started.

To summarize… the original problem was I downloaded and installed Java Version 30 which stopped the Ignition Gateway Service from working on Error 1067. Going back to previous versions of Java 27 & 29 did not fix my issues as the service now started but Launching Gateway from the Windows Menu selection did not work ( Gateway launched with issues ) and the Designer link was also broken. (Thanks to Nathan for the assist on the manual restore from autobackup directory. I will start a new thread on my project launch issues and http error 505. )