I am in the Language Studio > Custom question answering portal (https://language.cognitive.azure.com/questionAnswering/projects), trying to add a source to my existing Knowledge Base, but continuously get the error, "BadArgument Invalid input. See details." I've received this same error trying to add pdfs, word docs and csv files.
There is no link to see more details, just the text box that later disappears. I've been able to add documents this way when I had the free trial of azure, but since updating to a paid account 1/13/22 have had this error. Has anyone else received this error before?
I am seeing the same issue. I tried with multiple data sources and different files, and it seems to break after adding 3 sources and trying to add a fourth. I am following up with Microsoft and will share what I learn.
Related
I have an existing Knowledge Base in the QnA Maker that I am trying to update, however I am getting the following error: "You currently have no "knowledge bases", build one using the Create a knowledge base menu item. Learn more"
When I try to Create a Knowledge Base, my existing Azure subscription cannot be found.
I unable to create the new one as-well. It's been so buggy.
I am unable to create new knowledge base as-well.
I had a similar issue last week. Refreshing the page did not help. Meanwhile, I opened the KB using the link https://www.qnamaker.ai/Edit/KnowledgeBase?kbId=<knowledge-base-id> and that opened my Knowledge Base.
If this solution does not work, you can raise an issue by visiting the following page and click on GitHub as showed in the picture:
https://learn.microsoft.com/en-us/azure/cognitive-services/qnamaker/troubleshooting
I'm developing an Office.js based TaskPane Add-in. Recently I see frequently following error message which appears randomly:
Sorry, there was a problem saving your document.
Tell us about this problem to help us fix it. Give feedback to
Microsoft
Session ID: 1334d772-005e-4fcf-9ef0-6d5e19b56865 Please tell Microsoft
about this problem. We have created an error report that you can send
to help us improve Word Online. This report will include a copy of
your document which we will only use to investigate the error.
How can I get insight into this "Report" which is being sent to Microsoft?
The console.log itself doesn't show anything. Is there a way to figure out what might have caused this message?
Even playing around with the Script Lab I receive the same popup error message.
The issue can be more or less reliably reproduced by
Openin
opening a new word document in Microsoft Online
Opening Script Lab Code
Opening Script Lab Run
Selecting the Code example for 'Content control basics'
Running the example
interact with the example to insert and modify content controls
After a random period of time, the message pops up
Update: Issue was addressed and fixed by the Microsoft Office Team:
https://github.com/OfficeDev/office-js/issues/54#issuecomment-364346330
I created some reports in Report Builder for SQL 2012, before I realized that managing multiple reports is substantially easier in VS 2012. I created a reporting project in VS2012 and added the existing reports by right-clicking on the Reports icon in the solution tree, selecting Add ==> Existing Item and then navigating to and selecting the reports. I also added or recreated the data sources and data sets as needed.
Most of my reports "migrated" with no problems, and I was able to deploy them to a new dashboard and get a more unified experience for the users. However, a couple of the reports give the following error when I try to preview them:
The given path's format is not supported
Some of these reports deploy successfully and run in the SharePoint site, others do not. But my ask at this point is, can someone give me any tips on where to look for the cause of these errors? The Error and Output windows in VS2012 don't give file, line, or column info, so I just have no idea where to look. I have searched for as many URL or path references as I can in the query results, action targets, etc., and removed them when I found them, but the problem persists. If someone has any thoughts, or can tell me some settings to turn on in VS that might give me more information, that would be appreciated.
I have deployed an SSRS 2008 R2 project into our SharePoint Integration. This worked no problem. I then wanted to add report parts. I converted the DataSource and DataSets to Shared Components and re-deployed. No problem. I then selected the parts that I wanted to publish. Now when I deploy the project I get the error message:
Warning : Referenced item ReportsTo doesn't exist at http://dev-sp01/sites/CompanyName/Shared Documents/Reporting/Datasets/ReportsTo.rsds.
The item ReportsTo is a part that is trying to get published. This has me a little confused. I was under the impression that the rsds file type is soley for DataSources. Given that the path that is in the error is Datasets should it not be looking for a DataSet file?
Any help in resolving this to get the parts published would be greatly appreciated.
I am working in BIDS 2008 R2 not Report Builder
UPDATE:.. After Reviewing the Logs on the Reporting Server I noticed this.
GetPropertiesAction(http://dev-sp01/sites/ThriveReporting/http://dev-sp01/sites/CompanyName/Shared Documents/Reporting/Report Parts/TeamUtilizationOverWeeks_Chart.rsc, PathBased).
It looks like it is trying to merge the Site name with the Fully Qualified Path to the Reports Parts. In BIDS I've tried to change the Report Parts path in the deployment properties to the relative path to the Site Name provided, but it errors out and requests the Fully Qualified path. It would seem that this might be a bug.
So to Recap
When trying to Publish Report Parts
1) Bids Gives me the Warning:
Warning : Referenced item ReportsTo doesn't exist at 'http://dev-sp01/sites/CompanyName/Shared Documents/Reporting/Datasets/ReportsTo.rsds.'
Where ReportsTo is a Shared Dataset, so I beleive this should be looking for an rsd extention. In the Log there is a corresponding action for this but not error
Warning : Referenced item ReportsTo doesn't exist at 'http://dev-sp01/sites/CompanyName/Shared Documents/Reporting/Datasets/ReportsTo.rsds.'
GetItemTypeAction(http://dev-sp01/sites/CompanyName/Shared Documents/Reporting/Datasets/ReportsTo.rsds).
2) Reporting Services does not appear to be creating a path correctly to access a Report Part during deployment.
GetPropertiesAction(http://dev-sp01/sites/CompanyName/http://dev-sp01/sites/CompanyName/Shared Documents/Reporting/Report Parts/TeamUtilizationOverWeeks_Chart.rsc, PathBased).
From Microsoft, I am submitting Feedback now.
Hi Matt,
I can reproduce the issue. It seems to be a known issue.
I would suggest you submitting a feedback at https://connect.microsoft.com/sqlserver.
Your feedback enables Microsoft to make software and services the best that they can be, and you can learn about and contribute to exciting projects.
Thanks,
Jin Chen
Jin Chen - MSFT
UPDATE:
Please go to this link and vote this issue as important so that it will get looked at sooner.
I have a customer using the Access 97 runtime to support part of their product. Ideally, given the budget to do so, I would have replaced that dinosaur by this point, but that isn't an option today. I am not the system's original author, but am attempting to provide ongoing support.
To distribute this to their customers, they bought the Office 97 Developer Edition Tools, and once every few years they go through its Setup Wizard to package a new distribution.
This time, the Setup Wizard appears to reach a point where it wants to do something with AXDIST.EXE, and instead puts up a dialog box saying only "Path not found". The only reference I've located on the web is a tantalizing glimpse of a page from a domain that no longer exists, where Google has purged the cache retaining only the sentence that appears with the search result. It isn't enough of a hint to help me...
(Edit: Aside from lots of reported issues caused by AXDIST.EXE itself, or installations that are trying to use AXDIST.EXE in some way, that is. Our issue is a problem during the creation of a setup package using the ODE setup wizard. Its own documentation only references AXDIST in one place, and does not contain the text "path not found" at all.)
(Edit 2: Further investigation reveals that AXDIST.EXE itself is not the culprit. Removing that file from the setup wizard's list caused the wizard to stop on the next file in the list. There does not appear to be any significant differences between the description of the file on which it stopped, and the dozen or so files listed above it that were successfully processed. I'm guessing at this point that the resolution is going to be manually recreating the template from scratch, which would be a lot easier if it weren't trapped inside a horrible UI and stored in the form of an Access database containing a bunch of undocumented tables.)
My question is this: What mistake did we make this time with the setup wizard, and how can we fix it?
The issue turned out to be related to a feature of the Access run time that was explicitly listed in the setup wizard, but should have been left for the wizard to infer.
My general advice to anyone also stuck with dealing with the wizard would be to go back to the start and review all the settings carefully and methodically.