I've been searching for answers and support regarding deploying Azure Text Analytics through Power BI desktop. Essentially, I've followed the tutorial here for key phrase extraction:
https://learn.microsoft.com/en-us/azure/cognitive-services/language-service/key-phrase-extraction/tutorials/integrate-power-bi
After following the steps listed Power BI gives me a 404 error code "Resource not found". Others seem to think that the endpoint URL is incorrect, however I triple checked the endpoint URL from my Azure account which is:
https://alextextanalyzer.cognitiveservices.azure.com/
(I'm Alex). My location is set to Australia East. For further reference I've attached my m language edit as well as per the MS instructions. M editor code
Does anyone have any recommendations as to why this might be occurring? I've already changed the privacy settings as per the instructions, and still get an error. As far as I know I've done everything else correctly?
Error code is as follows:
An error occurred in the ‘’ query. DataSource.Error: Web.Contents failed to get contents from 'https://alextextanalyzer.cognitiveservices.azure.com/v3.0/keyPhrases' (404): Resource Not Found
Details:
DataSourceKind=Web
DataSourcePath=https://alextextanalyzer.cognitiveservices.azure.com/v3.0/keyPhrases
Url=https://alextextanalyzer.cognitiveservices.azure.com/v3.0/keyPhrases
You are missing a part of your endpoint.
The provided documentation says:
endpoint = "https://<your-custom-subdomain>.cognitiveservices.azure.com/text/analytics" & "/v3.0/keyPhrases"
Based on the capture you provided, you forgot the "text/analytics" part. It should be "https://alextextanalyzer.cognitiveservices.azure.com/text/analytics/v3.0/keyPhrases"
Can you check?
And please, rotate your API key as it is well visible in the capture ;)
Related
While creating knowledge base in dialog flow from URL, I am getting message "Error". However I am able to see FAQ which are on this URL when opening in browser. For reference please find below screenshot below, If feasible suggest how can I find exact reason for this error as dialog flow don't give any other relevant error for this.
URL which I am configuring knowledge base is :
https://www.owens.edu/faq/early-alert/
enter image description here
The full error message is the following:
"Failed to crawl https://www.owens.edu/faq/early-alert. Please verify that your URL is publicly accessible and is hosted on a site that can be indexed by Google Search."
I have tested the FAQ page you shared and by using the "Developer tools" of Chrome, I was able to see that error message. I suggest you to take a look at the "Supported content" documentation for knowledge bases in Dialogflow. In there, you can see the following statement:
Files from public URLs must have been crawled by the Google search indexer, so that they exist in the search index. You can check this with the Google Search Console. Note that the indexer does not keep your content fresh. You must explicitly update your knowledge document when the source content changes.
Therefore, make sure to meet all the requirements listed there.
https://atlas.microsoft.com/search/address/json?subscription-key=[subscription-key]&api-version=1.0&query=15127
NE 24th Street, Redmond, WA 98052
This link is not working. I added the subscription key but still getting this message 'Could not get any response'.
I am using this service from unsupported region. That is why azure map REST API link was not working.
I just tried the link and it worked for me. You sure you have the right subscription-key? (I don't see anything wrong the the url and the service is up as well)
https://atlas.microsoft.com/search/address/json?subscription-key={subscription_key}&api-version=1.0&query=15127%20NE%2024th%20Street,%20Redmond,%20WA%2098052
Also, What's the response status code that you get back?
I am getting error establishing a data connection in excel to import MS Dynamics report. Here what I have followed so far:
Went to Data tab >> New Query >> From Online services >> From Dynamics CRM online.
A pop up comes up saying Enter URL. Refer to Image below>
I put the URL I got from developer resource in MS CRM that exactly looks like this format
This is the url I am using (cannot reveal org name)-
https://orgname.api.crm.dynamics.com/XRMServices/2011/Organization.svc
When I click next, I get this error -
OData: The given URL neither points to an OData service or a feed: 'https://orgname.api.crm.dynamics.com/XRMServices/2011/Organization.svc'.
Why I am getting this error and what is the possible resolution?
You have to use OrganizationData.svc.
The URL will look like: https://orgname.crm.dynamics.com/XRMServices/2011/OrganizationData.svc/
Note the trailing slash / at the end of URL.
Refer this
Settings – Customizations – Developer Resources menu
I have deployed CRM and installed the reporting extensions component successfully on the SSRS server with rollup2 (server and router match this) - I have separate servers for CRM , SQL and SSRS. The out the box reports work ok but the custom reports present an error "rsProcessingAborted" which to me sounds like permissions. I have read a number of articles relating to pepople with the same issue and have tried all possible fixes but still no joy.
SSRS runs under a svc_sqlserver acccount and this account has permissions in the DB
the datasources have all been created successfully and the custom reports are using the MSCRM_FetchDataSource which is configured with type Dynamics CRM Fetch and credentials supplied by the user running the report. The connection string says CustomerServicesCE which is the correct OrgsanisationID (as found within developer resources) - i have tried clearing this connection string, adding the server url, all possible combinations with no joy.
Within SSRS i cannot view the report, it says "cannot access the CRM datasource" - i read somewhere you need to enter the GUIDs systemuserid and organisationid as username and pwd but still no joy.
I tried amending one report to use the samedatasource as the out the box reports that work but still no joy which is the MSCRM_DataSource...................am i missing something?
These reports have come from another supplier - i don't mind how they are displayed (Fetch or otherwise) i just need them working!
interestingly i do get them working on my Development environment (after getting the same error) and to my eyes the setup looks identical!
thanks for any help
richard
the answer was to create an spn as
setspn -a http/crmservername domain\accountCRMrunsunderrIIS
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.