Data pull through ODBC connection failures

[DSKinCO]

We have been using an ODBC connection from PowerBI to pull data from a FileMaker Server for months.  Now 2 out of 17 data table throw errors whenever updates/refreshes are requested of the data.  These are larger data files, one containing over 4.4 million records the other over 550 thousand records.  These 2 seem to use the Microsoft.Mashup.Container.NetFX45.exe during the connections, the other data pulls from other tables don't seem to activate this.  The largest one doesn't even seem to make it past the preview evaluation, while the second one seems to process the rows, but hten fails at the end, without the data making it into the PowerBI model.

Follwing is the information copied form the error report.  Any suggestions would be greatly appreciated. 

Feedback Type:
Frown (Error)

Timestamp:
2023-02-14T14:11:44.3287226Z

Local Time:
2023-02-14T07:11:44.3287226-07:00

Session ID:
8c6d9a07-39d8-4e61-b270-e69ebf328625

Release:
December 2022

Product Version:
2.112.1161.0 (22.12) (x64)

Stack Trace:
Microsoft.Mashup.Host.Document.SerializedException
at Microsoft.Mashup.Evaluator.ErrorTranslatingMessenger.MessageChannel.Read()
at Microsoft.Mashup.Evaluator.ChannelMessenger.Read(MessageChannel channel)
at Microsoft.Mashup.Evaluator.ChannelMessenger.MessageChannel.Read()
at Microsoft.Mashup.Evaluator.Interface.IMessageChannelExtensions.WaitFor[T](IMessageChannel channel)
at Microsoft.Mashup.Evaluator.MessageBasedInputStream.ReadNextChunkAndCheckIfClosed()
at Microsoft.Mashup.Evaluator.MessageBasedInputStream.ReadNextChunk()
at Microsoft.Mashup.Common.ChunkedInputStream.Read(Byte[] buffer, Int32 offset, Int32 count)
at Microsoft.OleDb.Serialization.PageReader.Read(Byte[] buffer, Int32 offset, Int32 count)
at Microsoft.OleDb.Serialization.PageReader.Read(Void* dst, Int32 length)
at Microsoft.OleDb.Serialization.PageReader.ReadArray(Char[] values, Int32 offset, Int32 count)
at Microsoft.OleDb.Serialization.PageReader.ReadChars(Int32 count)
at Microsoft.OleDb.Serialization.PageReader.ReadArray(String[] values, Int32 offset, Int32 count)
at Microsoft.OleDb.NullableColumn.Deserialize(PageReader reader)
at Microsoft.OleDb.Serialization.ColumnsPage.Deserialize(PageReader reader)
at Microsoft.OleDb.Serialization.OleDbPageReader.Read(ColumnsPage page)
at Microsoft.Mashup.Common.IPageReaderExtensions.NotifyingPageReader.Read(IPage page)
at Microsoft.Mashup.Engine.Interface.Tracing.TracingPageReader.Read(IPage page)
at Microsoft.Mashup.Evaluator.SoftCancellingDocumentEvaluator.DataReaderSourceEvaluation.SoftCancellingDataReaderSource.SoftCancellingPageReader.Read(IPage page)
at Microsoft.Mashup.OleDbProvider.DataHost.NonBufferingMashupEvaluator.MashupEvaluation.ExceptionResolverPageReader.Read(IPage page)
at Microsoft.Mashup.Common.IPageReaderExtensions.NotifyingEndOfAllResultsPageReader.Read(IPage page)
at Microsoft.Mashup.Engine.Interface.Tracing.TracingPageReader.Read(IPage page)
at Microsoft.Mashup.Common.IPageReaderExtensions.NotifyingEndOfAllResultsPageReader.Read(IPage page)
at Microsoft.OleDb.Serialization.PageReaderRowset.ReadNextPage()
at Microsoft.OleDb.Serialization.PageReaderRowset.Microsoft.OleDb.IRowset.GetNextRows(HCHAPTER hchapter, DBROWOFFSET lRowsOffset, DBROWCOUNT cRows, DBCOUNTITEM& countRowsObtained, HROW** pRows)
at Microsoft.OleDb.Rowset.Microsoft.OleDb.IRowset.GetNextRows(HCHAPTER hReserved, DBROWOFFSET lRowsOffset, DBROWCOUNT cRows, DBCOUNTITEM& countRowsObtained, HROW** pRows)
at Microsoft.Mashup.OleDbProvider.TracingRowset.Microsoft.OleDb.IRowset.GetNextRows(HCHAPTER hReserved, DBROWOFFSET lRowsOffset, DBROWCOUNT cRows, DBCOUNTITEM& countRowsObtained, HROW** pRows)

PowerBINonFatalError:
{"AppName":"PBIDesktop","AppVersion":"2.112.1161.0","ModuleName":"","Component":"Microsoft.Mashup.Evaluator.ErrorTranslatingMessenger.MessageChannel","Error":"Microsoft.Mashup.Host.Document.SerializedException - Microsoft.Mashup.Evaluator.Interface.ErrorException","MethodDef":"Read","ErrorOffset":""}

OS Version:
Microsoft Windows NT 10.0.19044.0 (x64 en-US)

CLR Version:
4.8 or later [Release Number = 528372]

Peak Virtual Memory:
71.9 GB

Private Memory:
1.07 GB

Peak Working Set:
1.52 GB

IE Version:
11.789.19041.0

User ID:
a862eab7-e455-4f6d-a998-2252617622b2

Workbook Package Info:
1* - en-US, Query Groups: 0, fastCombine: Disabled, runBackgroundAnalysis: False.

Telemetry Enabled:
True

Model Default Mode:
Import

Model Version:
PowerBI_V3

Enabled Preview Features:
PBI_enableWebView2
PBI_sparklines
PBI_scorecardVisual
PBI_fieldParametersSuperSwitch
PBI_horizontalFusion

Disabled Preview Features:
PBI_shapeMapVisualEnabled
PBI_SpanishLinguisticsEnabled
PBI_qnaLiveConnect
PBI_azureMapVisual
PBI_compositeModelsOverAS
PBI_b2bExternalDatasetSharing
PBI_enhancedTooltips
PQ_WebView2Connector
PBI_NlToDax
PBI_optimizeTabRibbon
PBI_relationshipEditPane

Disabled DirectQuery Options:
TreatHanaAsRelationalSource

Cloud:
GlobalCloud

DPI Scale:
125%

Supported Services:
Power BI

[Anonymous]

Hi @DSKinCO ,

Have you considered optimizing your data sources? We usually consider asking our clients to optimize reports and related data when there is some information such as inability to evaluate.
Does this problem still occur if you reduce the amount of data?

Best regards.
Community Support Team_ Caitlyn