Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Get Fabric Certified for FREE during Fabric Data Days. Don't miss your chance! Request now

Issue With OData.Feed: 'System.String[]' of the OData-Version HTTP header is invalid. Only '4.0' ...

I have recently had an issue with an OData.Feed to https://api.securitycenter.microsoft.com/api/machines which was working fine until earlier this week. Other than general patches to my machine there haven't been any changes I am aware of. I have also tried it on more than one machine and in a new power BI document to make sure there aren't any code issues. I also have other OData feeds to Microsoft and other websites that are working without any issues.

 

The code is very simple and is produced by power BI when selecting OData as the feed type, it hadn't been altered by me: 

 

Source = OData.Feed("https://api.securitycenter.microsoft.com/api/machines", null, [Implementation="2.0"])

 The error received is:

 

Error

The value 'System.String[]' of the OData-Version HTTP header is invalid. Only '4.0' is supported as values for the OData-Version header.

True

 

Details from the error are:

 

Feedback Type:
Frown (Error)

Release:
October 2022

Product Version:
2.110.805.0 (22.10) (x64)

Stack Trace:
Microsoft.Mashup.Client.UI.Shared.ExceptionResultException
at Microsoft.Mashup.Evaluator.EvaluationHost.OnException(IEngineHost engineHost, IMessageChannel channel, ExceptionMessage message)
at Microsoft.Mashup.Evaluator.MessageHandlers.TryDispatch(IMessageChannel channel, Message message)
at Microsoft.Mashup.Evaluator.MessageHandlers.Dispatch(IMessageChannel channel, Message message)
at Microsoft.Mashup.Evaluator.ChannelMessenger.ChannelMessageHandlers.TryDispatch(IMessageChannel channel, Message message)
at Microsoft.Mashup.Evaluator.MessageHandlers.Dispatch(IMessageChannel channel, Message message)
at Microsoft.Mashup.Evaluator.Interface.IMessageChannelExtensions.WaitFor[T](IMessageChannel channel)
at Microsoft.Mashup.Evaluator.RemotePreviewValueSource.PreviewValueSource.WaitFor(Func`1 condition, Boolean disposing)
at Microsoft.Mashup.Evaluator.RemotePreviewValueSource.PreviewValueSource.get_SmallValue()
at Microsoft.Mashup.Evaluator.Interface.TracingPreviewValueSource.get_SmallValue()
at Microsoft.Mashup.Host.Document.Analysis.PackageDocumentAnalysisInfo.PackagePartitionAnalysisInfo.SetPreviewValue(EvaluationResult2`1 result, Func`1 getStaleSince, Func`1 getSampled)

PowerBINonFatalError:
{"AppName":"PBIDesktop","AppVersion":"2.110.805.0","ModuleName":"","Component":"Microsoft.Mashup.Evaluator.EvaluationHost","Error":"Microsoft.Mashup.Client.UI.Shared.ExceptionResultException","MethodDef":"OnException","ErrorOffset":""}

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

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

Peak Virtual Memory:
70.1 GB

Private Memory:
558 MB

Peak Working Set:
827 MB

IE Version:
11.789.19041.0

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

Telemetry Enabled:
True

Model Default Mode:
Empty

Model Version:
PowerBI_V1

Enabled Preview Features:
PBI_enableWebView2
PBI_sparklines

Disabled Preview Features:
PBI_shapeMapVisualEnabled
PBI_SpanishLinguisticsEnabled
PBI_qnaLiveConnect
PBI_azureMapVisual
PBI_compositeModelsOverAS
PBI_b2bExternalDatasetSharing
PBI_enhancedTooltips
PQ_WebView2Connector
PBI_scorecardVisual
PBI_NlToDax
PBI_fieldParametersSuperSwitch
PBI_horizontalFusion
PBI_relationshipEditPane

Disabled DirectQuery Options:
TreatHanaAsRelationalSource

Cloud:
GlobalCloud

DPI Scale:
150%

Supported Services:
Power BI

 

Thanks in advance for any help offered.

Status: Investigating
Comments
red13x
Regular Visitor

I heard from MS again today, a resolution has been implemented so this should now be resolved. We are monitoring it in the meantime, however if you've been holding off testing or using your Power BI query then now is the time to test it again! 😎

zeroSPace33
Frequent Visitor

I heard the same thing from MS on our ticket. I've done some testing and it seems ok so far. We're trying a more extensive test to see what happens.

red13x
Regular Visitor

MS have closed the ticket my side, problem fixed their end and I've had no issues since then.

zeroSPace33
Frequent Visitor

We finally tested it on a larger scale and it seems to be working again for us as well. We'll close our ticket with MS soon too.  Thanks for your help!