Closed. This question needs debugging details. It is not currently accepting answers.
Edit the question to include desired behavior, a specific problem or error, and the shortest code necessary to reproduce the problem. This will help others answer the question.
Closed 5 years ago.
Improve this question
TFS2013
Edit: Additional info as per comment:
I'm trying to add a "blocked" swim lane to my task board.
So as per instructions I run:
witadmin.exe exportprocessconfig /collection:http://{my collection} /p:{my project} /f:config.xml
It generates the XML as expected
If I immediately run (without editing the xml):
witadmin.exe importprocessconfig /collection:http://{my collection} /p:{my project} /f:config.xml /v
I get:
Line: 3 Position: 4 - The required attribute `pluralName` is missing.
So basically the XML generated by witadmin exportprocessconfig is invalid?!
exportprocessconfig creates a BROKEN xml file (according to importprocessconfig /v)
I amended line 3 from:
<BugWorkItems category="Microsoft.BugCategory" singularName="Bug">
To:
<BugWorkItems category="Microsoft.BugCategory" singularName="Bug" pluralName="Bugs">
then carried out my own changes and it worked.
Kinda sucks that the export is not compatible with the import on the same tool.
Related
When highlighting a line and using the key combination 'Ctrl+K, Ctrl+C' to comment out code, I get the message:
The key combination (Ctrl+K, Ctrl+C) is bound to command (Comment
Selection) which is not currently available
I am using Visual Studio 2019.
I have tried: 'Tools | Options | Keyboard | Reset' but this has not resolved the issue.
I'm editing an HTML file and haven't got any plugins installed in Visual Studio.
Closed. This question is not reproducible or was caused by typos. It is not currently accepting answers.
This question was caused by a typo or a problem that can no longer be reproduced. While similar questions may be on-topic here, this one was resolved in a way less likely to help future readers.
Closed 2 years ago.
Improve this question
Windows 32, Delphi XE5. Database from Component ACE: Absolute database.
Form Create Procedure worked ok upto few hours ago. Suddenly resulted in error:
Cannot open File"Error Code 3" Error message: Can not find the path specified. Error 30364.
I have read many discussion with the same or similar problem but none gave me a good hint to solve.
The Procedure code is:
Procedure TForm1.FormCreate(Sender: TObject);
begin
ABSDatabase1.DatabaseFilename:= ExtractFilePath(Application.ExeName)+'LibCat.ABS';
ABSDatabase1.Open;
// showmessage(ABSDatabase1.Databasefilename);
ABSTable1.TableName:='Cat';
ABSTable1.Open; // gives error
ABSTable1.Last;
GetAppVersionStr;
Form1.Caption:=Form1.Caption +': Books Catalogue, ver. ' + Versione;
end;
The database file is in the same folder as the Project exe file. Any path of the option file point to the same folder.
I cannot imagine what modication I did to get this error.
On a step by step debugging the Database opens regularly, but the open Table gives the error.
On Object Inspector for Database the FileName is specified as .\LibCat.abs
Solved.
It was really a silly reason:
I examined carefully the .dfm file and I found that on "Object Inspector" providing data to ABSDatabase1 I have written the name and put at the end of the string a carriage return and a new line. Of course these characters where not visible on ID, only on .dfm file.
I do not know why this additional keys caused the error, but as I cleared them the Form was regularly generated and the program run perfectly.
Hope this can be useful to someone else.
I downloaded DBPedia turtle-files with their extraction framework (https://github.com/dbpedia/extraction-framework).
Then I used the docker image tenforce/virtuoso:1.3.2-virtuoso7.2.2 after extracting all ttl.bz2 to a toLoad folder.
After the full load, I checked isql with select * from DB.DBA.LOAD_LIST; and got an error from one of the files:
2 2019.2.2 11:31.43 69876000 2019.2.2 11:31.44 521623000 0 NULL 37000
[Vectorized Turtle loader] SP029: TURTLE RDF loader, line 172395:
syntax error
The virtuoso endpoint (http://localhost:8890/sparql) is online, but the queries don't return correct results.
Do you know what I can do to correct this error?
UPDATE: newer tenforce/virtuoso:1.3.2-virtuoso7.2.5.1 and openlink/virtuoso-opensource-7 were also tested giving the same result.
UPDATE 2: Line 172395 of that file seems ok: <http://pt.dbpedia.org/resource/Reino_de_Roma> <http://dbpedia.org/ontology/governmentType> <http://pt.dbpedia.org/resource/Monarquia> <http://pt.wikipedia.org/wiki/Reino_de_Roma?oldid=53119289&ns=0> .
As I said in your duplicate post on github --
I would start by using tenforce/virtuoso:latest or tenforce/virtuoso:virtuoso7.2.5 or tenforce/virtuoso:1.3.2-virtuoso7.2.5, all of which should be based on Virtuoso 7.2.5.1 (from August 2018), rather than the rather elderly tenforce/virtuoso:1.3.2-virtuoso7.2.2 which is based on the similarly elderly Virtuoso 7.2.2 (from December 2015).
I am trying out BDD with Specflow in Visual Studio 2017. Previously I had created a new project and added Specflow and Nunit using NuGet Package Manager. From the Solution Explorer, I right click and select Add New Item. From the Add New Item window, I could see SpecFlow feature File and Feature.cs file
But I open the Feature.cs it's showing empty with the message
<#error Generation error: The element may only appear once in this section.>
Then I try to build the solution then I'm getting error on Output
Error CS1029
error: 'Generation error: The element may only appear once in this section.'
The references I can see from Solution Explorer are: SpecRun.SpecFlowPlugin TechTalk.SpecFlow TechTalk.SpecRun NUnit.VisualStudio.TestAdapter
Am I missing something?
Thanks, Mohammed
If you have a scenario outline, but you for get to write the Examples-Keyword, you will get the following error during the build process:
CS1029 #error: 'Generation error: Sequence contains no elements' in Line 1 of MyFeature.feature
It took me some hours in my large created feature file to locate my error. I deleted the temp files, restarted visual studio several times, but it was difficult to figure out why it occurs.
Could you somehow improve the error messages e.g. with a better location, a simple syntax check before or something similar?
As far as I understand, the ScenarioOutline, followed by a will allways need at least an Examples keyword and a table with this varname, before an other Tag like Scenario, etc. is allowed again. I would appreciate to have such markup
?xml version="1.0" encoding="utf-8"?>
configuration>
<configSections>
<section name="specFlow" type="TechTalk.SpecFlow.Configuration.ConfigurationSectionHandler, TechTalk.SpecFlow" />
</configSections>
<specFlow>
<!-- For additional details on SpecFlow configuration options see http://go.specflow.org/doc-config -->
<!-- For additional details on SpecFlow configuration options see http://go.specflow.org/doc-config --><!-- use unit test provider SpecRun+NUnit or SpecRun+MsTest for being able to execute the tests with SpecRun and another provider --><unitTestProvider name="SpecRun" /><plugins>
<add name="SpecRun" />
</plugins></specFlow>
</configuration>
I have a macro that we were using for years and worked well in Excel 2010. However, now that we upgraded to Excel 2013, it gives a run time error 9.
The following code part is highlighted after debugging it:
Sheets(1).Copy after:=Workbooks(mfname).Sheets(3)
I know already that this error has to do something with the availability of the range. The question is if there is any easy fix to this? The relevant code-snippet:
Workbooks.Add
mfname= ActiveWorkbook.Name
Workbooks.Open template
template_name = ActiveWorkbook.Name
Sheets(1).Copy after:=Workbooks(mfname).Sheets(3)
Workbooks(mfname).Activate
Sheets(1).Delete
Sheets(1).Delete
Sheets(1).Delete
lapok = Sheets.Count
Thank you for the help!
I'm no expert in VBA, but little google searching says error 9 is subscript out of range error.
This likely is from Sheets(3). I also remember excel had 3 sheets open by default in those versions. Maybe that is not the case now, and causing the problem.