Tom,

You have a database source somewhere which is importing a column containing binary data. Typically this is represented as a BLOB data type, but for the database you're using, Omniscope is receiving untyped binary data.

When this happens, the column will show up in Omniscope as something cryptic like "[B@405217f8".

Typically BLOBs and other binary data are used to store resources such as image files. Omniscope can't import these, since Omniscope is concerned with text, date and number values.

I would verify this is indeed correct by looking at the previews of your source blocks, and then safely ignore these, or omit those fields from your database queries.

In future, if you need to understand the context of scheduler errors, try temporarily enabling the logging options in the main scheduler configuration dialog. This will give you a clearer picture of what part of what task has caused it. Alternatively start the desktop app using the Omniscope_console.exe shortcut, refresh blocks in turn, and watch for the message.

But we'll look into introducing proper warnings rather than console messages, to avoid needing to do this.

Steve

The warnings have now been fixed for tonight's build, 2.7 b216, so you will see the warning in DataManager after refreshing blocks.