• Replies 1 reply
  • Subscribers 587 subscribers
  • Views 102 views
  • Users 0 members are here
Options
Related

Citect Historian Fails to Read Cluster on Import Schema after successful test connection.

John

We're migrating from Citect 2016 ->2018 (Soon to go to 2023)

Anyway, our historian is Citect 4.6.  (Also about to be upgraded, but got to stay online until upgrade complete.)

We have changed our primary server to 2018 and get a successful connection notice.

But when we try to import the Schema we get the error on reading Cluster seen below.

the allowlegacyconnection ini parameter is set to 7400

Parents

  • Try to remove [LAN]EarliestLegacyVersion=7400 from the CtAPI servers. I believe that this parameter was left over once your system was upgraded to 2018 (v8.10). CtAPI components in Citect Historian v4.6 are, however, in v8.20 (2018 R2). Hope that removing this parameter would resolve your problem.

    Regards,

    Jacky

Reply

  • Try to remove [LAN]EarliestLegacyVersion=7400 from the CtAPI servers. I believe that this parameter was left over once your system was upgraded to 2018 (v8.10). CtAPI components in Citect Historian v4.6 are, however, in v8.20 (2018 R2). Hope that removing this parameter would resolve your problem.

    Regards,

    Jacky

Children
No Data
© 2024 AVEVA Group Limited or its subsidiaries. All Rights Reserved.