| Applies To: |
|
| Summary: |
| When the [CTEDIT]Run and [CTEDIT]Backup paths are used for redundancy, Citect may still shutdown if an included directory (such as System or Include projects) fails. This happens because the [CTEDIT]RunSubst parameter defaults to 1, which will substitute paths for the included files to the current run path. When this is turned on, the paths do not substitute the paths again when the Run path fails to point to the Backup path. |
| Solution: |
| If the included Projects are local, and
the Run and Backup paths are pointing to a network server, the
[CTEDIT]RunSubst parameter should be set to zero. This means that
no matter which path is active currently, the Include projects will
always be loaded from the local drive.
If the Run and Backup paths are used, and all projects are on these paths, Citect will now use the backup path as a basis for it's substitutions. This previously did not happen. e.g. Run path = p:\Citect\User\MyProj If RunSubst is set (the default) at startup the Include projects will point to p:\Citect\User\<project>. If the run path fails and switches to the backup path, Citect will try to find the Include projects at s:\Citect\User\<project>. This allows for full redundancy on file servers. CIT has confirmed this to be a problem in Citect for Windows versions 5.00 to 5.10. This problem has been fixed in version 5.10 Spk A. |
| Keywords: |
Related Links
Attachments