RealTime startup validation
- Last UpdatedApr 08, 2026
- 2 minute read
When the RealTime service starts, pre-assertion scripts run to perform validation on Execution Pipeline configuration files. A separate pre-assertion script runs for each Execution Pipeline configuration file in the AVEVA Enterprise SCADA system. If the configuration file indicates that the pipeline is disabled—"UseLegacyExecution = true"—then the system stops validating the configuration for that pipeline.
For more information on the settings inside a configuration file, see Execution Pipeline configuration settings.
When "UseLegacyExecution" is false, the validation checks the following conditions. In the event of a failure on any of these, the system will:
- Generate a log message.
- Shut down the RealTime service.
| Cause | Log Message Example |
| The type name referred to in a step cannot be found | The type name referred to in a step cannot be found KrunchPipeline pre_assert failed. Failed to load assemblyName <assembly name> for step <step name>, reason: Could not load file or assembly <assembly name> or one of its dependencies. The system cannot find the file specified. RealTime service will be shutdown. |
| Dependent step disabled | KrunchPipeline pre_assert failed. Step: <step name> depends on step: <step name> but the dependent step is disabled. RealTime service will be shutdown. |
| Fail to load an assembly in a dependency step | KrunchPipeline pre_assert failed. Failed to load assemblyName <assembly name> for step <step name>, reason: Could not load file or assembly <assembly name> or one of its dependencies. The system cannot find the file specified. RealTime service will be shutdown. |
| Dependent step does not exist | KrunchPipeline pre_assert failed. Step: <step name> depends on step: step <step name>, but the dependent step does not exist. RealTime service will be shutdown. |
If the system logs any of these types of messages, review the applicable Execution Pipeline configuration file and correct the errors.