each time i try to add ssis custom component, this error pops up
note:- this component works fine on data tool 2010 and 2013 , this problem happens only on Data Tool 2015
is there any thing missing and how to fix it
my .net framework 4.0
the error as follows:
enter image description here
TITLE: Microsoft Visual Studio
The component could not be added to the Data Flow task.
Could not initialize the component. There is a potential problem in the ProvideComponentProperties method.
------------------------------
ADDITIONAL INFORMATION:
Error at Data Flow Task [DTS [7]]: System.MissingMethodException: Method not found: 'Microsoft.SqlServer.Dts.Pipeline.Wrapper.IDTSComponentMetaData100 Microsoft.SqlServer.Dts.Pipeline.PipelineComponent.get_ComponentMetaData()'.
at CustomProparties.Class1.ProvideComponentProperties()
at Microsoft.SqlServer.Dts.Pipeline.ManagedComponentHost.HostProvideComponentProperties(IDTSManagedComponentWrapper100 wrapper)
------------------------------
Method not found: 'Microsoft.SqlServer.Dts.Pipeline.Wrapper.IDTSComponentMetaData100 Microsoft.SqlServer.Dts.Pipeline.PipelineComponent.get_ComponentMetaData()'. (Microsoft.SqlServer.DTSPipelineWrap)
------------------------------
BUTTONS:
OK
------------------------------
I had the same problem and this worked for me:
"Please open your csproj file, and remove <EmbedInteropTypes>True</EmbedInteropTypes> element or set the value to False in the reference to Microsoft.SQLServer.DTSPipelineWrap.dll , then rebuild your project."
Although this is a solution for the component being targeted for SSIS 2012 instead of SSIS 2015 and this is not my situation, it worked.
Source:
Social MSDN
Related
I'm writing tests for a rest API. I'm using property and property transfer.
When I run my TestCase using SoapUI, everything goes fine. However, when I run it using maven and the com.smartbear.soapui:soapui-maven-plugin:4.6.1 I got this error:
Status: FAILED
Time Taken: 64
Size: 0
Timestamp: Fri Dec 21 14:15:12 GMT+01:00 2018
TestStep: Property Transfer 1
Error:com.eviware.soapui.impl.wsdl.teststeps.PropertyTransferException: error: Unexpected element: CDATA
----------------- Messages ------------------------------
Error performing transfer [city] - error: Unexpected element: CDATA
----------------------------------------------------
city transferred [[error: Unexpected element: CDATA]] from [Personal_data.city] to [eligibility.Request]
------------ target path -------------
$..city
I'm thinking of using a Groovy script to do my properties transfers but first, I would realy like to understand why I have this error and if there is a way to fix it who doesn't involve a Groovy script.
After looking and looking again, I finally manage to solve the issue:
The problem was that I was using SoapUI 5.4.0 with a (very) old version of soapui-maven-plugin. So, I just change the version of the soapUI plugin in maven to match the one of my SoapUI interfaces and it's now working fine.
I am using JSON Source component in a package, it is working fine on my local machine but when I deploy in server am receiving the following error.
System.ArgumentException: Value does not fall within the expected range.
at Microsoft.SqlServer.Dts.Pipeline.Wrapper.IDTSBufferManager100.FindColumnByLineageID(Int32 hBufferType, Int32 nLineageID)
at KingswaySoft.IntegrationToolkit.ProductivityPack.JsonSourceComponent.yhs.cgd(IDTSOutputColumn100 kbk, IDTSExternalMetadataColumn100 kbl)
at System.Linq.Enumerable.d__614.MoveNext()
at System.Linq.Buffer1..ctor(IEnumerable1 source)
at System.Linq.Enumerable.ToArray[TSource](IEnumerable1 source)
at KingswaySoft.IntegrationToolkit.ProductivityPack.JsonSourceComponent.bdc()
at KingswaySoft.IntegrationToolkit.ProductivityPack.JsonSourceComponent.PreExecute()
at Microsoft.SqlServer.Dts.Pipeline.ManagedComponentHost.HostPreExecute(IDTSManagedComponentWrapper100 wrapper)
For the error “Value does not fall within the expected range”, it seems to be an issue caused by the SSIS optimization design, it happens when you don’t have all the output attached to a destination component.
In this case, either of the following two options can solve the issue properly:
Set the RunInOptimizedMode property to False in the Properties window
at Data Flow Level (see figure 1). This setting can be found after
you click the blank area on your data flow designer.
Alternatively, you can try to direct other outputs of the JSON Source component to an SSIS Destination component which can take care of this situation as well.
Can you please give it a try and see if it helps?
[Figure 1]
When I set the TargetServerVersion = SqlServer2012 in my SSIS project, my script component throws a null object exception.
I am importing about 140,000 records from a CSV file. To confirm I do get records, I removed my script component step and ran the flow with no issues.
I then added back in the Script Component (which has worked fine with this very data file) and I get the null exception.
When I debug the script and check the value of the Row property it says the following:
?Row
{Input0Buffer}
Buffer: {Microsoft.SqlServer.Dts.Pipeline.PipelineBuffer}
BufferColumnIndexes: {int[2]}
MembershipPlanName: 'Row.MembershipPlanName' threw an exception of type 'System.NullReferenceException'
MembershipPlanName_IsNull: 'Row.MembershipPlanName_IsNull' threw an exception of type 'System.NullReferenceException'
The script then fails when the rest of the lines try to reference Row. When I change the TargetServerVersion back to 2016 or 2014, the package works fine.
During debegging I also looked at BufferWrapper.cs and there seems to be some data in there
?Buffer
{Microsoft.SqlServer.Dts.Pipeline.PipelineBuffer}
ColumnCount: 2
ColumnInfo: 0x0000000000000000
CurrentRow: 0
EndOfRowset: false
Mode: Input
RowCount: 9936
RowSize: 260145280
RowStarts: 0x000000000f82b700
Out of frustration I installed SSDT for VS2012. For some reason, that made everything work fine in VS2015. Not sure why it worked, but posting this if anyone has a similar issue.
I found that my Sonar instance 5.1 or 5.1.1 (with latest sonar-runner 2.x) stopped showing part of the Unit test info (Unit test widget) on the project's dashboard.
The properties I had were (in Gradle's sonarRunner > sonarProperties section):
property "sonar.junit.reportsPath", "build/test-results/UT"
property "sonar.surefire.reportsPath", "build/test-results/UT"
To fix it, I had to include the following properties as well:
property "sonar.java.junit.reportsPath", "build/test-results/UT"
property "sonar.java.surefire.reportsPath", "build/test-results/UT"
Just FYI: All my Unit tests reports go under build/test-results/UT folder, all Integration Tests result files go unedr build/test-results/IT folder and etc.
I'm wondering if this is due to Gradle version that I'm using (2.3) or is it due to a later version of SonarQube (4.5+) as I have both SQ 5.1 and 5.1.1 instance.
I know SonarQube team started Multi language support since SonarQube version 4.12
Since SonarQube 4.2, it is possible to run an analysis on a multi-language project.
Now, it raises a question. For Getting the same Unit test info for Groovy based projects, do I need to use:
property "sonar.groovy.junit.reportsPath", "build/test-results/UT"
property "sonar.groovy.surefire.reportsPath", "build/test-results/UT"
something like that if my project has Groovy code instead of java?
Searching "**sonar.java.junit.reportPath"** with using double quotes shows No results found in Google and it forces me to try and see google results if I can run the search again without using " double quotes (for this property).
Doing the same in SonarQube site "search box" shows:
No results found for sonar.java.junit.reportPath. Please try one of the following suggestions:
Though in Gradle, inside
sonarRunner task {
.. inside ..
sonarProperties {
... section ... where I define various sonar props..
}
...
}
I can define both sonar.junit.reportPath, sonar.java.junit.reportPath and similarly, sonar.surefire.reporPath and sonar.java.surefire.reportPath and while running sonarRunner task in Gradle, it doesn't error out. Thus it makes me believe that the property variables are valid.
There are also issues with running sonarRunner or stand alone sonar-runner command for a mixed Java and Groovy based project (i.e. source code in Java but tests in Groovy). Setting sonar.language=java,grvy didn't help. I posted this question on stackoverflow but so far I have no perfect result/answer on how to get a full fledged sonar dashboard up and running for a Groovy projects like I get for a Java project.
Groovy project - Sonar - Publish project and Unit + Integration Test code coverage data
PS: I have tried various values for setting sonar.. variables (as far a sonar source, tests, etc, etc properties are concerned, which they have mentioned on their site's docs section)
The only valid property to use as of now is sonar.junit.reportsPath which will tell the java sonarqube plugin where to import your result of unit tests.
For groovy, this is work in progress, see : http://jira.sonarsource.com/browse/SONARGROOV-2
All the other properties you mentioned do not exist and are not taken into account.
In my iPhone app I'm using Core Data and I've made changes to my data model that cannot be automatically migrated over (i.e. added new relationships). I added the data model version (Design -> Data Model -> Add Model Version) and applied my new data model changes to the new version 2. I then created a mapping object model and set the Source and Destination models to their correct data models (old and new respectively).
When I run the app and call the persistentStoreCoordinator, my app barfs with the following:
2010-02-27 02:40:30.922 XXXX[73578:20b] Unresolved error Error Domain=NSCocoaErrorDomain Code=134110 UserInfo=0xfc2240 "Operation could not be completed. (Cocoa error 134110.)", {
NSUnderlyingError = Error Domain=NSCocoaErrorDomain Code=134130 UserInfo=0xfbb3a0 "Operation could not be completed. (Cocoa error 134130.)";
reason = "Can't add source store";
}
FWIW (not much i think) I've also made the usual code changes in persistentStoreCoordinator to use the NSMigratePersistentStoresAutomaticallyOption and NSInferMappingModelAutomaticallyOption (for future data model changes that can be automatically migrated). More relevantly, my managedObjectModel is created by calling initWithContentsOfURL where the file/resource type is "momd".
I've tried updating both the source and destination model in the mapping model (Design -> Mapping Model -> Update XXX Model) as well as deleted the mapping model and recreated it. I've cleaned and re-built but all to no avail. I still get the above error message.
Any pointers/thoughts on how I can further debug or resolve this problem please? I haven't posted any code snippets because this feels much more like a build environment issue (and my code is very standard - just the usual core data code to handle migrations using a mapping model but I'm happy to show the code if it helps).
Appreciate any help.
Thanks
Ok, this is now fixed.
I (a) deleted and then recreated my managed object model classes, (b) deleted and then recreated the mapping model and then finally I (c) deleted the iphone project under the users/xxx/Library/Application Support/iPhone Simulator/User/Applications.
Given I previously tried and failed with doing just (a) and (b), I suspect it was (c) which fixed the problem.