iFix 5.1, Windows 2003 Terminal Server
I created an remote station alarm notification picture that opens when any alarm in any remote station exists (I have an event scheduled that will launch the pic.)
My problem is that when this pic is open simultaneously multiple TSclient sessions, only ONE session successfully opens with the tag group file substitutions. ALL other nodes show the "Animation Data Error Defaults" for every object on the pic that has a tag group substitution. Its as if the tag substitution failed completely, no error appears, and the pic sits there with animation errors.
I did some testing with just two TSclient nodes and the pic opens fine in one of the sessions, but not the other...and its NOT consistent - one time session 1 will work fine, then randomly session 2 will work. So, it is definitely repeatable, but not consistent with the session that gets the good data.
I've never had this problem before but it definitely appears to be related to the taggroup file being accessed by multiple sessions at the exact same time. How do I get around this one?
I created an remote station alarm notification picture that opens when any alarm in any remote station exists (I have an event scheduled that will launch the pic.)
My problem is that when this pic is open simultaneously multiple TSclient sessions, only ONE session successfully opens with the tag group file substitutions. ALL other nodes show the "Animation Data Error Defaults" for every object on the pic that has a tag group substitution. Its as if the tag substitution failed completely, no error appears, and the pic sits there with animation errors.
I did some testing with just two TSclient nodes and the pic opens fine in one of the sessions, but not the other...and its NOT consistent - one time session 1 will work fine, then randomly session 2 will work. So, it is definitely repeatable, but not consistent with the session that gets the good data.
I've never had this problem before but it definitely appears to be related to the taggroup file being accessed by multiple sessions at the exact same time. How do I get around this one?