Thanks. so for every 2 hours we need to reinitialize right?
I am one more error.
when I click on Tag Geneneration->Create Tags
Global folder is not creating.
when I installed first time the kepware , I was able to get tag values in Kepware and Ignition also.
next time I am trying the same but values is not getting and other above errors are coming.
now tags are coming values are not coming
Kavya, were you ever able to figure out the issue here? Having the same issue myself.
Hi,
Kepware need License, if not we need to restart the Kepware.
Go to Services, search for the Kepware and restart its files. Then we can see the live tag values.
this is how I tried.
That was the fix! Thank you Kavya!
Facing Same problem 
what is this where I check this problem ..plc ... ignition software or designer software. Please tell me .....
You should start a new topic and explain what you've set up, and share screen shots of your results. All of the above is Kepware related--if you are asking about PLC and designer and Ignition itself, you may have a totally different problem.
Facing this problem 
from 24 hrs
Start a new topic. Provide complete details about YOUR system. You haven't provided anything useful for helping you.
Can we are use any dask you will easily find the problem
So this started happening to me as of this morning but in a different way then everyone else. I have a script that has been working for about two years not that can update the OPC Item path using a CSV file.
Sometime when we bring data from cygnet to ignition, there are some case sensitive issue for example instead of Lenable should be LEnable. Where it would say Error_configuration as the value in ignition.
Normally we just update our CSV then run the script to replace the old values. But as of this morning all those now has a status of "Bad" and when we try to update it the output error we get is what this post is talking about.
I was up at 6 am, central time, doing my own site changes worked fine. About an hour or two ago this started happening.
Has something change on Ignition's side by chance as of this morning?
Here is the image form above how the errors used to look like
here what it looks like as of now:
Ignition isn't hosted software-as-a-service that we can update underneath you.
It doesn't change unless you or somebody else at your org changes it.
Oh ok cool. That narrows it down. Is there some kind of gateway change that will change the error status? Sorry I added the two pictures after you commented
Right click the error tag and "restart" it. If that doesn't work you should probably call support and let them take a look at what might be wrong - it's hard to tell from just these screenshots.
