Analysis Services REST API missing location header

Question

Analysis Services REST API missing location header

Ivan Johannessen 11

The REST API to refresh the tabular model (https://learn.microsoft.com/en-us/azure/analysis-services/analysis-services-async-refresh) is supposed to return a Location header that can be used to obtain progress information. This has now stopped working. The refresh starts but there is no way to monitor progress without the Location header. Anyone else experiencing this?

Bhargava-MSFT 31,261 Reputation points Microsoft Employee Moderator

2022-10-20T23:31:32.853+00:00

Hello @Ivan Johannessen ,

Welcome to the MS Q&A platform.

I see a similar issue discussed in this thread.

Did you check "Disable async pattern"

Disable async pattern
Option to disable invoking HTTP GET on location given in response header of a HTTP 202 Response. If set true, it stops invoking HTTP GET on http location given in response header.
If set false then continues to invoke HTTP GET call on location given in http response headers.
Bhargava-MSFT 31,261 Reputation points Microsoft Employee Moderator

2022-11-03T20:45:55.59+00:00

Hello @Ivan Johannessen ,

I see a similar thread here and here is the solution mentioned on the thread. I hope this helps.

1) let A be http POST /refreshes via ADF Web activity with "Disable async pattern" ENABLED[a], then you can retrive:
either only refresh id with A.output.operationId or the entire URL with A.output.ADFWebActivityResponseHeaders.Location.
(no header status is returned by http POST /refreshes: eventually you can use http GET /refreshes/refreshId to learn about the status);

2) http POST /refreshes via ADF Web activity with "Disable async pattern" DISABLED[b] returns headers status -with value 'notStarted'- and startTime.
(neither refresh id nor header Location is returned).

[a] JSON code representation -> "turnOffAsync": true
[b] JSON code representation -> "turnOffAsync": false
Ivan Johannessen 11 Reputation points

2022-11-09T08:00:00.88+00:00

There is nothing new in that other thread, just another user reporting the same ting as I did: The refresh API no longer returns the Location header if the refresh has status notStarted.

1 answer

Your answer

Bhargava-MSFT 31,261 Reputation points Microsoft Employee Moderator

2022-10-20T23:31:32.853+00:00

Hello @Ivan Johannessen ,

Welcome to the MS Q&A platform.

I see a similar issue discussed in this thread.

Did you check "Disable async pattern"

Disable async pattern
Option to disable invoking HTTP GET on location given in response header of a HTTP 202 Response. If set true, it stops invoking HTTP GET on http location given in response header.
If set false then continues to invoke HTTP GET call on location given in http response headers.
Bhargava-MSFT 31,261 Reputation points Microsoft Employee Moderator

2022-11-03T20:45:55.59+00:00

Hello @Ivan Johannessen ,

I see a similar thread here and here is the solution mentioned on the thread. I hope this helps.

1) let A be http POST /refreshes via ADF Web activity with "Disable async pattern" ENABLED[a], then you can retrive:
either only refresh id with A.output.operationId or the entire URL with A.output.ADFWebActivityResponseHeaders.Location.
(no header status is returned by http POST /refreshes: eventually you can use http GET /refreshes/refreshId to learn about the status);

2) http POST /refreshes via ADF Web activity with "Disable async pattern" DISABLED[b] returns headers status -with value 'notStarted'- and startTime.
(neither refresh id nor header Location is returned).

[a] JSON code representation -> "turnOffAsync": true
[b] JSON code representation -> "turnOffAsync": false
Ivan Johannessen 11 Reputation points

2022-11-09T08:00:00.88+00:00

There is nothing new in that other thread, just another user reporting the same ting as I did: The refresh API no longer returns the Location header if the refresh has status notStarted.

Answer 1

Hi BhargavaGunnam-MSFT,

Thank you for replying. Yes, the "Disable async pattern" checkbox is checked. Here is a sample response:
{
"startTime": "2022-10-21T01:17:37.9288788Z",
"type": "full",
"status": "notStarted",
"currentRefreshType": "full",
"objects": [],
"ADFWebActivityResponseHeaders": {
"Strict-Transport-Security": "max-age=31536000; includeSubDomains",
"x-ms-root-activity-id": "bad6cd20-9821-4a8a-911f-de3ee4fd7241",
"x-ms-current-utc-date": "10/21/2022 1:17:38 AM",
"X-Frame-Options": "deny",
"X-Content-Type-Options": "nosniff",
"X-XSS-Protection": "1; mode=block",
"Content-Security-Policy": "script-src 'self'",
"Date": "Fri, 21 Oct 2022 01:17:39 GMT",
"Server": "Microsoft-HTTPAPI/2.0",
"Content-Length": "148",
"Content-Type": "application/json"
},
"effectiveIntegrationRuntime": "AutoResolveIntegrationRuntime (West Europe)",
"executionDuration": 3,
"durationInQueue": {
"integrationRuntimeQueue": 1
},
"billingReference": {
"activityType": "ExternalActivity",
"billableDuration": [
{
"meterType": "AzureIR",
"duration": 0.016666666666666666,
"unit": "Hours"
}
]
}
}
As you can see the ADFWebActivityResponseHeaders is returned but is missing the Location header. Notice the status is "notStarted". I assume if the refresh is not started there is no refreshId and therefore no Location header. But why did this change? It used to work just a few days ago.
This MS documentation https://learn.microsoft.com/en-us/azure/analysis-services/analysis-services-async-refresh states the Location header should be returned.

However, I have found a workaround thanks to a post by Filippo Leporati (https://www.filepora.com/post/refresh-azure-analysis-service-model-with-azure-data-factory-v2-and-azure-key-vault). He shows how to GET the most recent refreshes and filter the list down to the most recent. From there I get the refreshId and use it to monitor the progress and get the final status.

Bhargava-MSFT 31,261 Reputation points Microsoft Employee Moderator

2022-10-21T19:47:56.47+00:00

Hello @Ivan Johannessen ,
Thank you so much for the details. I will need to check with my internal team and see if any recent changes are causing the issue.
I will reach out to the relevant teams and get back to you.
And thank you for sharing the workaround
Kazi Sabbir 1 Reputation point

2022-11-11T17:15:54.703+00:00

This issue is impacting us as well. @Bhargava-MSFT . Hope you have some solution soon.

Share via

Analysis Services REST API missing location header

1 answer

Your answer