Error computing in SCADAConnect Simulator: Object reference not set to an instance of an object

Product(s): WaterGEMS, SewerGEMS
Version(s): 10.00.xx.xx
Area: Modeling


When computing a simulation in SCADAConnect Simulator, the following error occurs: 

System.NullReferenceException: Object reference not set to an instance of an object.

at Haestad.SCADA.Forms.Library.SCADAFormsLibrary.FeatureTrackSCADADatasource(ILicensedFeatureSet licensedFeatureSet, IDomainDataSet domainDataSet)
at Haestad.Idaho.Library.IdahoFeatureTrackingLibrary.TrackSCADACalculationType(ILicensedFeatureSet licensedFeatureSet, IDomainDataSet domainDataSet, Object data)
at Haestad.Idaho.Application.IdahoParentFormUIModel.ExecuteCommand(CommandType type, Object data)
at Haestad.Water.Forms.Application.SCADA.SCADAWaterSimulatorFormModel.CalculateSelectedScenario()
at Haestad.Water.Forms.Forms.SCADA.SCADAWaterSimulatorForm.OnSimulateClick(Object sender, EventArgs e)
at Haestad.Water.Forms.Forms.SCADA.SCADAWaterSimulatorForm.ExtraEditButton_Click(Object sender, EventArgs e)
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

Reference: 717177.


This issue should be resolved as of the CONNECT Edition Update 1 (and later) release of the products. If you are able to upgrade, use the steps found here to download the latest version of the program: Download OpenFlows | Hydraulics and Hydrology Software.

If you can't upgrade, try the following steps as a workaround. The issue occurs because of invalid data in the SCADA Signals table. Opening this table will see some rows in the Historical Data column with a null or blank setting. The first thing to try is to clean up the source data to make sure that the data is accurate. If you do that and the issue still occurs, manually change the null or blank fields so they are set to "<none>" instead. You can try filtering the FlexTable and using the Global Edit function to do this more quickly. Once the null fields are set to "<none>" the issue will no longer occur.

See Also

SCADAConnect Simulator for WaterGEMS (V8i SELECTseries 6 and CONNECT edition)