Forum Discussion
Solved
Connector Rule - Object reference not set to an instance of an object
Hi I always seem to get an "Object reference not set to an instance of an object" in the error log when I execute data loads that use connector rules. The full error message is: -------------...
Hey Rob
FYI, I reached out to support and they confirmed that it is a bug in the current version of OneStream that we are using (we're on 7.0.1).
"Hi Mark,
I believe this is a bug that has been fixed in version 7.4. It is caused by the Telemetry Service which provides us with logs. This error does not mean anything is breaking, it is just a false flag. Upgrading is the only way to get rid of this error but if possible, would come with extra benefits like access to Smart Integration Connector (SIC), our new connector service. OneStream is moving to Smart Integration Connector (SIC) for all future integrations and will be a requirement for 8.0 so would be good to have the option of slowly migrating.
Thanks, Max"
Subscript, "Array Index, all the same thing.
At this point, I would experiment with writing the values of the variables to the log in your Catch block.
This will require you to declare your variables before the try (you should do this anyway).
I would also chain your exception throwing and only write to the log from Main. This will give you more of a stacktrace to work with.
When you say chain your exception throwing, is that not what I'm doing here?
Catch ex As Exception
Throw ErrorHandler.LogWrite(si, New XFException(si, ex))
End Try
I tried a log write in the catch of my Main function and it didn't write anything, so I'll raise a support ticket.
Appreciate your efforts in trying to help me find the issue though!
Mark
Hey Rob
FYI, I reached out to support and they confirmed that it is a bug in the current version of OneStream that we are using (we're on 7.0.1).
"Hi Mark,
I believe this is a bug that has been fixed in version 7.4. It is caused by the Telemetry Service which provides us with logs. This error does not mean anything is breaking, it is just a false flag. Upgrading is the only way to get rid of this error but if possible, would come with extra benefits like access to Smart Integration Connector (SIC), our new connector service. OneStream is moving to Smart Integration Connector (SIC) for all future integrations and will be a requirement for 8.0 so would be good to have the option of slowly migrating.
Thanks, Max"