In one of my self-asserted technical profiles, I use a validation technical profile which calls a REST service. That service returns a 200 or 409 if all goes well, but it can also return a 500.
If that happens, the following message is shown:
I'm looking for a way to translate that message.
It's not using DefaultUserMessageIfRequestFailed and I can't seem to find it in the default page level resources file either.
The docs also don't seem to specify anything concrete enough.
I'm assuming it's some kind of default message for when an orchestration step fails, or when any claims exchange fails, but I can't seem to find any details.
Any pointers?
Microsoft is fixing the behavior for error code handling from rest apis. the recent changes you see here are a result of that.
The bug fix for issue you are seeing will be rolled out in next 2-3 weeks. And then you should be able to use DefaultUserMessageIfRequestFailed or potentially some other metadata element to control this error message.
Related
I'm integrating Microsoft Teams into my app using microsoft graph API.
But with the API to get list message, I used parameter $top={pageSize} for pagination, then I got surprised that in the first call, the response returned "pageSize - 1" records, not exactly the number of pageSize.
In contrary, the API to get list replies, it returned exactly "pageSize" records in the first call.
I don't understand why is there a difference like this between message and relpy. Can anyone help me?
This is the pattern of the API that I used:
https://graph.microsoft.com/beta/teams/{teamId}/channels/{channelId}/messages?$top={pageSize}
https://graph.microsoft.com/beta/teams/{teamId}/channels/{channelId}/messages/{messageId}/replies?$top={pageSize}
We could able to reproduce the issue on our side raised a bug.
I have a problem with querying the Facebook Graph API and reading with extended permissions. I want to query a page's latest posts with additional data for a reporting dashboard (show the number of likes, reactions and post impressions) I have an express app with passport-facebook running in order for the user to authenticate and provide the permissions in question. This setup used to work before, but now I am experiencing a strange problem.
This is what I am requesting: created_time,link,full_picture,message_tags,with_tags{link},message,reactions.summary(true),insights.metric(post_impressions)
I had my app in Facebook's review process and they granted me the read_insights permission for querying insights.metric(post_impressions). After the review I was able to pull all the data I needed from the API. That was 2 weeks ago. Today I experienced the problem that I can only pull very limited data out of the API. The response keeps giving me Permission error (OAuthException), stating "User doesn't have enough permissions to load insights", "You do not have enough permission to view the metric."
However, when I add the limit and/or the after params to the query I do get data back, but only with very low values for limit (that is <= 5, but after 2 paginated requests, no subsequent requests are allowed) or a value for after, which I don't have for an inital request.
Has there been a change to the API (couldn't find anything in the changelog)? Maybe I'm just overlooking something trivial?
Thanks!
Since nobody else (not here or anywhere else I asked for help) seemed to have experienced the issue I filed a bug at Facebook and it turned out to be an individual problem with some item(s) on my page's feed. Here's their response:
This is a particular issue with one or more specific posts from that page feed, that is causing the entire call to fail when trying to include it.
This issue might be addressed in a future version of Graph API. There are two workarounds for now: either use a page access token or if sticking with a user access token, giving it granular permissions to the pages.
I've tried option 1 and a page access token seems to fix the issue.
I'm trying to follow along with this tutorial https://azure.microsoft.com/en-us/documentation/articles/service-bus-dotnet-multi-tier-app-using-service-bus-queues/ on azure queues but I opted for using an MVC app instead of the web role. I have everything working up to step 9 of the create a web role where it says you should now be able to hit submit and watch the message count increase of your queue on page.
Instead I get An exception of type 'Microsoft.ServiceBus.Messaging.MessagingEntityNotFoundException' occurred in Microsoft.ServiceBus.dll but was not handled in user code
Additional information: 40400: Endpoint not found.
on the step 8 line when it send the message to the queue. It detects the queue as being there or it wouldn't skip over the check for is it created so I have to think it's some kind of access issue.
Can someone please assist me?
So funny enough I had all the code correct as per the tutorial but after checking the error definition metadata it says that entity not found usually means it can't find the queue. So as a shot in the dark I looked at this line
OrdersQueueClient = messagingFactory.CreateQueueClient(
"OrdersQueue");
and guessed that maybe the OrdersQueue was actually supposed to match the name of my queue which I overlooked during my first go through. So if you get entity not found make sure you check your connection string and queue name in the azure portal. Hope this is helpful.
I have a premium Spotify account and I am trying to generate an application key to use with libspotify. I am doing this using the form here: https://developer.spotify.com/technologies/libspotify/request-key/, but the generation of the key always fails with a message "There was an error generating your application key".
I tried formatting my application name differently (e.g., spaces, no spaces, no dashes, etc), but the outcome is still the same.
Not sure if it's of any relevance, but I am logged in through facebook and my user name on the application form is shown as a number.
Is it possible that there is something wrong with my account ?
Thanks in advance,
-Kal.
I suspect that something is up with the API key registration page. I've filed an internal bug report with the team that maintains that (I work at Spotify), and hopefully it'll be up and running soon! I'll update this answer if it turns out to be something other than that.
Edit: The error was on Spotify's website, everything seems to be working again.
I'm getting the following error when uploading a file to a Sharepoint 2010 list, using a WebRequest with the PUT verb.
X-MSDAVEXT_Error: 327704; Unable%20to%20complete%20this%20operation%2e%20%20Please%20contact%20your%20administrator%2e
There is pretty much no information about that specific error code (327704). I came up with the following page by Microsoft, which says that due to the existing HTTP errors not being enough to handle all file operation scenarios, they created that MSDAVEXT error.
http://msdn.microsoft.com/en-us/library/cc250064(v=prot.10).aspx
However, after googling for two hours, I cannot find a description of that error, or ANY of the extended errors they supposedly handle.
Here's a link to the MS WebDav implementation index, and of course, the "Errors" link under the E letter is not a link.
http://msdn.microsoft.com/en-us/library/cc250260(v=PROT.10).aspx
Does anyone know about these extended errors, or know where I can find more information about this? Thanks .
I don't link answering my own questions, but just in case it helps anyone else, I was able to find a couple of pages that detail just the general cause of groups/ranges of Extended WebDAV errors, here they are:
The link originally included in my question:
MS-WDV - Extended Error Handling
MS-WEBDAVE - Currently defined WebDAV Extended Errors
WEBDAV Protocol Status Codes
WHY the "Currently defined WebDAV extended errors is not linked from the Extended Error Handling is beyond me. It does not even detail each error code, but a "range of them". I still don't have access to the Sharepoint logs as to see if the logged error does indeed give more information about the actual server problem, but I hope this helps someone.