"Tag Group Invalid" Error in Ignition tags

Ignition
1

I've exported and imported tags from one project to another and also added necessary tag groups in new project.
But getting "Tag Group Invalid" error even though the tag group is present.
May I know what should I check?

2

Hi Aman,

If you have not yet done so, I would recommend making a support ticket. You can find our contact information here: https://support.inductiveautomation.com/hc/en-us.

If you do make a support ticket, be sure to include a brief history of how the project and tags were moved. Additionally, a gateway backup would be helpful as it includes all of your tags and tag groups, which would make it easier for our support team to resolve your issue.

3

Hi Aman.
I'm having the same issue. Did you manage to solve it? And if so, how did you do it?
Thank you in advance.

4

It would be super helpful to get a resolution update on this. I am getting the exact same issue with a tag group I exported from a test install to a live server

5

I am having a similar issue, we have UDTs which inside have different elements, for some reason only some elements on some elements on some tag providers seem to be affected, and seems to be related to OPC types.

Running (Version: 8.1.31 (b2023081007))

I followed the steps as below.

  1. Deleted Tag Provider, to make sure I sure I start with no previous conflicts.
  2. Export TagGroups, and UDTs from other working TP
  3. Import Tag Groups
  4. Import UDTs
  5. Copy tag from working TP to new TP (usign json Copy, but same thing happens if I export/import tags)
  6. On first picture below you can see the error.
  7. If I override the type to Memory it works (second picture below)

image
image649×601 29.3 KB

image
image642×568 24.2 KB

6

+1 on this issue. I exported all tag groups to json from a working development gateway, and imported into another gateway. The identical UDT instances on the new gateway all report "Error Configuration" when assigned to one particular tag group. If I assign it to a different tag group that was created during that same import, the issue clears. When pointed back to the original tag group, the error returns. I renamed the tag group to something random, assigned the UDT instances, and that cleared the error as well. Inspecting the json between the working and non-working tag groups, they are identical.

7

I'd be interested to see the differences between them in the config.idb, and the related references. I'd expect to see some things missing when the name is the original, but I'm just speculating

8

I didnt see anything on the TagGroups nor on the TagConfig. I just submited a backup of the config.idb to Support to see if they can spot something.

1 Like
9

I just had this issue after importing a project and the tags for the project from another gateway. The issue ended up being that the Tag Groups for the tags in the project were not mapped to the "default" tag group, and the tag group configurations were not part of either export. To resolve this issue, I created Tag Groups with the same name and configuration as the original project and the error was resolved.