# Duplicate Ignition Servers

**URL:** <https://forum.inductiveautomation.com/t/duplicate-ignition-servers/38900>\
**Category:** Ignition\
**Created:** [September 21, 2020, 6:53pm UTC](https://forum.inductiveautomation.com/t/duplicate-ignition-servers/38900 "2020-09-21T18:53:09Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![jimjohnson](https://avatars.discourse-cdn.com/v4/letter/j/898d66/32.png) [@jimjohnson](https://forum.inductiveautomation.com/u/jimjohnson)\
**Post date:** [September 21, 2020, 6:53pm UTC](https://forum.inductiveautomation.com/t/duplicate-ignition-servers/38900/1 "2020-09-21T18:53:09Z")

</div>

I have a customer in China that I setup 2 years ago with Ignition Vision and Bridge. All of a sudden now, transactions have started executing twice simultaneously which got me wondering:

1. What would happen if you brought up two machines running the exact same Ignition Project
2. Best way to check / troubleshoot this

Any thoughts on any of this are appreciated!  
Jim

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [September 21, 2020, 7:15pm UTC](https://forum.inductiveautomation.com/t/duplicate-ignition-servers/38900/2 "2020-09-21T19:15:16Z")

</div>

Another possibility: they duplicated the project that contains the transaction groups.

---

<div class="post-metadata">

**Author:** ![jimjohnson](https://avatars.discourse-cdn.com/v4/letter/j/898d66/32.png) [@jimjohnson](https://forum.inductiveautomation.com/u/jimjohnson)\
**Post date:** [September 22, 2020, 12:46pm UTC](https://forum.inductiveautomation.com/t/duplicate-ignition-servers/38900/3 "2020-09-22T12:46:42Z")

</div>

So, yes that is what the problem was. I had a copy from years ago that somehow got started so both projects were running on the same server. I am surprised this doesn’t happen more often.

---

<div class="post-metadata">

**Author:** ![Sanderd17](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/sanderd17/32/8735_2.png) [@Sanderd17](https://forum.inductiveautomation.com/u/Sanderd17)\
**Post date:** [September 22, 2020, 12:56pm UTC](https://forum.inductiveautomation.com/t/duplicate-ignition-servers/38900/4 "2020-09-22T12:56:23Z")

</div>

If you only use Ignition for SCADA, it doesn’t matter if you have two instances.

But if you use Ignition for other stuff (like with transaction groups), having two instances can be a big problem. Hard to detect and things may fail in odd ways.

We’ve also had issues with this in the past, and even not only with Ignition. But it’s very hard to program detection for it.

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [September 22, 2020, 2:45pm UTC](https://forum.inductiveautomation.com/t/duplicate-ignition-servers/38900/5 "2020-09-22T14:45:14Z")

</div>

I tend to put transaction groups (or their scripted equivalents) in projects of their own with no other resources. Reduces the temptation to treat the project as a template for something new.