Customer Support

What can we help you with?

Find the Help You Need

Have a question? Find the answers you need by searching our knowledge base, visiting our community forum or watching our helpful online training videos.

Contact Us

Our support team is available to help you Monday - Friday 6am - 5pm PST.

Inductive Automation Corporate
+1 (800) 266-7798 Toll Free (USA) Support
+1 (916) 456-1045 International Support
+1 (800) 207-5506 MES Module Support
+1 (844) 924-7787 MQTT Module Support

Other Ways to Get Help

Latest Updates
Updated 7.9.8 Version Now Available
Posted by Peggie Wong on 06/08/2018 02:23 PM
Recently we made an announcement regarding 7.9.8 and a bug with resource locks that could affect users who use multiple designers concurrently for project design. This bug has been fixed and a new version of 7.9.8 that includes this fix is available from the main downloads page. The version number is still the same however there is a different build number associated with the release so users can identify which version of 7.9.8 they are running and determine whether or not the fix is included. The whole version including the build number is as follows: 7.9.8 (b20180607). Users can check which version they have installed from the Ignition Gateway Status page. We apologize for any inconvenience this may have caused.

Download 7.9.8 here
Read more »

Multi-Designer Saving Issue in 7.9.8
Posted by Dave Fogle on 06/01/2018 03:09 PM
UPDATE: The issue has been fixed in a new version of 7.9.8 (b20180607) which can be downloaded here.

There is a bug that has been discovered recently after the release of Ignition 7.9.8 that affects users who routinely use multiple designers at the same time for project design. It has the potential to be quite negatively impactful so we want to publicly address the details of this bug in order to help users avoid any problems or confusion it may cause. 

The issue revolves around how locks on project resources are obtained and released in an Ignition designer session. When a resource is opened in one designer a lock for that resource is correctly obtained and any other open designers will not be able to obtain that lock for editing. This is the expected normal behavior. Where the problem arises is when the designer currently holding the lock for the open resource saves the project. At this time the lock is released and it is possible for a second designer to obtain that lock for the same resource and begin to make changes. The initial designer is unaware that it no longer has a lock for the current project resource which creates a situation where both designers can makes edits and saves to the same resource, essentially overwriting each other's changes. This can lead to lost work and confusion on the part of the Ignition user. 

It is possible to work around this bug by ensuring that all project resources (windows, templates, etc.) for which a user has made edits to are first closed and the changes committed to those resources before commencing with a project save. By doing this the designer will have to try and re-obtain the resource lock after the save upon opening that resource for further editing. 

Due to the workaround being less than ideal for most users, Inductive Automation is quickly working to fix this bug and making a release with the fix publicly available as soon as possible. Until that time it is officially recommended that users working in environments where multiple designers are used concurrently to edit the same project avoid upgrading to Ignition 7.9.8. Another news article will be posted once a new release that includes a fix is available for download. We apologize for any inconvenience this may cause.
Read more »

Ignition 7.9.8 Now Available
Posted by Janice Chan on 05/31/2018 04:28 PM

The 7.9.8 official release is now available for download on the Ignition downloads page. It contains minor features and bug fixes. You can view a complete list of this in the change log here

7.9.8 is now the recommended download for new installations and upgrades.

Read more »

Known Issue with Windows 10 Feature update 1803
Posted by James Hunt on 05/18/2018 12:42 PM
After Windows Feature update Windows 10 version 1803 has been installed. Ignition service will no longer start automatically on OS startup. In windows event viewer log you will see the following error:

" The Ignition Gateway service failed to start due to the following error:  Ignition Gateway is not a valid Win32 application."

This issue will be fixed in Ignition 7.9.8

In the meantime, there is a hotfix that you can apply to work around this issue. You can replace the 'IgnitionGateway.exe' located here 'C:\Program Files\Inductive Automation\Ignition' with a new .exe file found here:

Windows 32-bit

Windows 64-bit

In addition to the hotfix the service can also be started by running the following command via a command prompt: "c:\Program Files\Inductive Automation\Ignition\IgnitionGateway.exe" "c:\Program Files\Inductive Automation\Ignition\data\ignition.conf"

This will resolve the startup issues until the fix is released in Ignition update 7.9.8
Read more »

Java and Ignition
Posted by Janice Chan on 04/20/2018 04:29 PM

At Inductive Automation, we are constantly improving Ignition to best serve our customers. As part of this effort, we work closely with our technology partners to ensure the stability of the Ignition platform. Java has long been a strong part of the Ignition platform and we have exciting news about our plans to make the experience of using Java with Ignition easier and more seamless in the future.

Recently, Oracle put out a white paper focusing on their roadmap for Java, which announces that they plan on ending commercial support of Java 8 effective January 2019. While this may seem like a cause for concern, we think this is a great opportunity to inform you about how we are improving Ignition. In talks with Oracle, we were made aware of their roadmap prior to their recent announcement and have been working on our own development plan to continue to make sure that using Java with Ignition is a good experience for our users.

We are planning to embed the open-source version of Java, which is available through OpenJDK, into Ignition v8.0, which is currently in development for release later this year. In v8.0, there will be no need to install Java to launch clients. This change will make Ignition simpler to manage and easier to maintain.

In the meantime, the current version of Ignition, v7.9, will continue to support Java versions 6, 7, 8, and 9, and LTS v7.7 supports Java version 6, 7, and 8. Ignition v7.9 does not currently support Java 10; for more information, please refer to our Knowledge Base article on that subject. No immediate action is needed at this time but we encourage you to consider other available Java distributions such as the OpenJDK, which can be downloaded here. You also have the option to obtain a commercially supported version of Java from Azul Systems. These solutions will not degrade or otherwise affect the performance of your Ignition installation.

If you have any questions or encounter any Java-related issues with your Ignition system, our support staff is available to assist you. Want to know more about the future of Java and Ignition? Please check out our blog post on the subject.

Read more »