• Replies 8 replies
  • Subscribers 582 subscribers
  • Views 752 views
  • Users 0 members are here
Options
Related

Citect 2018 R2 - Unresponsive after a time

Peter

After a time Citect becomes unresponsive and won't accept any inputs. Values on the mimics are still updating.
The user restarts Citect and all runs fine again - for a while.

In Syslog.dat:

2020-02-07 04:27:27.387    +13:00    TranWrite(0, 23): Name=IOServer1, User has not been authorised
2020-02-07 04:27:27.387    +13:00    TranWrite(1, 23): Name=IOServer2, User has not been authorised
2020-02-07 04:27:27.387    +13:00    TranWrite(4, 23): Name=Alarm, User has not been authorised
2020-02-07 04:27:27.387    +13:00    TranWrite(5, 23): Name=Trend, User has not been authorised

The project has been upgraded from Citect 7.4.
There is a default user login with an on entry command: LogOutIdle(-1)
The individual operator logins have an on exit command that logs the default user in when they timeout or log off.

This was working fine in ver7.4. Perhaps LogOutIdle(-1) is not working in Citect 2018?

Parents
  • Thanks Patrick.
    Gave that a try. Still get the same problem.
    After a period the default login loses ability to write values. Buttons & cicode stop working.

    Syslog shows series of TranWrite User not authorised errors.
    Have replaced LogIn() calls with ini file setting AutoLoginMode - 6.
    Works great - but still has same timeout problem.

    On the background Cicode have added:
    IF UserInfo(0) <> "1" THEN
    Login("~~~");
    END
    But no joy. The default user is logged in - just can't write values.

    Restart Citect and default login works fine again. For a period.
    Which has made me suspicious of LogOutIdle(-1).

    Could it be a Win10 issue?
    The two redundant IO servers are just running on Win10 Pro with ~14 clients.
    Have looked in the windows event log on them - but nothing stands out.
Reply
  • Thanks Patrick.
    Gave that a try. Still get the same problem.
    After a period the default login loses ability to write values. Buttons & cicode stop working.

    Syslog shows series of TranWrite User not authorised errors.
    Have replaced LogIn() calls with ini file setting AutoLoginMode - 6.
    Works great - but still has same timeout problem.

    On the background Cicode have added:
    IF UserInfo(0) <> "1" THEN
    Login("~~~");
    END
    But no joy. The default user is logged in - just can't write values.

    Restart Citect and default login works fine again. For a period.
    Which has made me suspicious of LogOutIdle(-1).

    Could it be a Win10 issue?
    The two redundant IO servers are just running on Win10 Pro with ~14 clients.
    Have looked in the windows event log on them - but nothing stands out.
Children
No Data
© 2025 AVEVA Group Limited or its subsidiaries. All Rights Reserved.