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

[red13x]

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.

[mccormickco]

@Microsoft Support, any news on a resolution for this? This error is happening across mutiple tenants. 

[Anonymous]

Hi @red13x ,

No further conclusions can be drawn in my case.

Based on the above information, if you are a Power BI Pro licensee, you can create a support ticket for free and a dedicated Microsoft engineer will come to solve the problem for you.
It would be great if you continue to share in this issue to help others with similar problems after you know the root cause or solution.

The link of Power BI Support: Support | Microsoft Power BI

For how to create a support ticket, please refer to How to create a support ticket in Power BI - Microsoft Power BI Community

Best Regards,
Community Support Team _ Caitlyn

[paulthepwner]

Same issue here.

I'd also like to add that it is actually impossible to open a support ticket. I go through the process with the chat bot and it gives me a form to fill out to open a ticket. I've done this multiple times and every time one of the required fields doesn't populate. So I fill the whole thing out but I can't select 'severity' because there are no options, and when I submit it says it can't submit without the required severity field. This makes it impossible to open a ticket. @v-caitlyn-mstf I would hope you can escalate this since I can't open a ticket.

[aledeniz]

I found a workaround, it is still working when using the EU service: 

• api-eu.securitycenter.microsoft.com

I have tried both those, and it is currently not working:

• api.securitycenter.microsoft.com
• api-uk.securitycenter.microsoft.com

I haven't tried the US service:

• api-us.securitycenter.microsoft.com

@Anonymous if you work for Microsoft, you should really escalate this internally to the appropriate teams (the ones mainteining the 4 services listed above, plus the team developing Power BI desktop).

This is clearly a bug, which is being likely introduced after some change (upgrade?) is being propagated on across the servers providing the service. It is not affecting the EU service only because the change has not been propagated there (or, optimistically, because they started to fix the problem from there).

[red13x]

I've manged to raise a ticket with MS so I will feedback here with any support I receive...

[red13x]

I had a support call with Microsoft Power BI support yesterday and was able to replicate the issue with them. They have all log/trace files from the tests and are actively investigating it their side. I will report back when I hear/know more.

[paulthepwner]

Great news thank you! I've had intermittent success this week but still getting the failures as well.

[zeroSPace33]

I too have a ticket open with MS. We've gone back and forth about what the proper URLs are to use. No matter we try, we still either get the version error (4.0) or we get what looks like a successful pull of data only to reveal that we're missing data for some hosts when we compare back to the MDE portal.

The URLs we were told shouldn't work were ones that end in .windows.com

I have not been able to get api.securitycenter.microsoft.com to work. The URL that sometimes "works" for us is api-us.securitycenter.microsoft.com, but we sometimes are missing data that should be there.

We're likely to have a live session with someone from engineering soon too.

[red13x]

I heard from MS yesterday to let me know they're investigatng with their engineers still.

For ref, I haven't had the error today, not even once. Anyone else seeing this as possibly resolved? I am not holding my breath just yet though.

[JCESTRA]

No errors today after multiple syncs. Promising.