question

LukasAnderson-4988 avatar image
0 Votes"
LukasAnderson-4988 asked LukasAnderson-4988 commented

Provenance None is not supported for conversion to ContentSource - System.NotSupportedException - POST to graph.microsoft.com/v1.0/search/query

I'm using graph API v1.0 to query our Sharepoint site
This worked back in December of 2020

The only mention of ContentSource/Provenance in the MS Docs mentions that ContentSource is only relevant when we're searching for externalItems (which we're not).

I'm sending this as my POST body (with <host> and <site-name> replaced with our info)
I've tried with and without the path value in the queryString (tried with just "a"), same results

 {
     "requests": [
         {
             "entityTypes": [
                 "listItem"
             ],
             "query": {
                 "queryString": "a path:\"https://<host>/sites/<site-name>\""
             },
             "fields": [
                 "Title",
                 "Description",
                 "Answer",
                 "listId",
                 "listItemId"
             ]
         }
     ]
 }

Response: 500

 {
     "error": {
         "code": "System.NotSupportedException",
         "message": "\r\n Provenance None is not supported for conversion to ContentSource",
         "innerError": {
             "date": "2021-03-15T18:21:00",
             "request-id": "22f77433-3f9e-441f-bccb-d362c7540f76",
             "client-request-id": "22f77433-3f9e-441f-bccb-d362c7540f76"
         }
     }
 }



sharepoint-devmicrosoft-graph-sites-listsmicrosoft-graph-search
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Jerryzy avatar image
0 Votes"
Jerryzy answered Jerryzy edited

Hi @LukasAnderson-4988 ,

I tested /search/query in Graph Explorer and it's working as expected per the test result:

78201-77978-snipaste-2021-03-16-14-48-47.png

Can you please try again later to see if it works ? Feel free to post update.

If the issue still exists in your side, then the issue is possibly related to the Service Incident in Microsoft 365: https://status.office365.com/
You may check the service health status of your tenant via: https://portal.office.com/adminportal/home#/servicehealth

Microsoft is working on this issue actively, and we will be getting back to you as soon as the issue is resolved.

Thanks
Best Regards


If an Answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.



5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

LukasAnderson-4988 avatar image
0 Votes"
LukasAnderson-4988 answered Jerryzy commented

Unfortunately it's still happening after that incident
I've added more context (perhaps we're missing some header?) & the request IDs
I get the same behavior with and without the path value in the queryString

78363-image.png


78324-image.png


78317-image.png



image.png (314.7 KiB)
image.png (472.9 KiB)
image.png (119.4 KiB)
· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Suggest to test the same request in Graph Explorer and use Developer Tool Network tab to trace the detailed request header to see if there is some difference with your local side:

78434-snipaste-2021-03-17-08-43-28.png


0 Votes 0 ·
LukasAnderson-4988 avatar image
0 Votes"
LukasAnderson-4988 answered LukasAnderson-4988 commented

I get the same response in Graph Explorer
78796-image.png



image.png (69.9 KiB)
· 5
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

As the response is returning 500 internal server error and actually I can't reproduce the issue in my Tenant.

Suggest to submit a Azure Support Ticket for this issue for a deep troubleshooting for Azure Tenant.



0 Votes 0 ·

Ok, will do. Thanks anyway

0 Votes 0 ·
Jerryzy avatar image Jerryzy LukasAnderson-4988 ·

You are welcome :)

0 Votes 0 ·
Jerryzy avatar image Jerryzy LukasAnderson-4988 ·

Hi @LukasAnderson-4988 ,

I checked the backend request log, it seems there is something wrong with the service.

Can you try again now to see if it's fixed ?

Thanks

Best Regards

0 Votes 0 ·
Show more comments