SSIS- Cannot Create user component - Component Entry Point Attribute - ssis

I created a Data flow task, with a simple flow inside.
The script component type is destination.
First I look for some data from my database, then I transform it, and finally insert it to my CRM database.
I'am using Microsoft.Xrm sdks.
Here is the error I'm getting
Reading the error, it says that I have to make sure there is one class marked with SSISScriptComponentEntryPointAttribute
I confirm that the scriptMain class is already marked
For information, even is the script component is blank, I mean as is when created , without my code, it stills giving the same error.
And I don't have any build or analysis error

Related

Unmapped column in a dependence restriction in SSIS

I have an issue in SSIS in the dependence restriction. I am trying to import data from an excel file. I have used the EXCEL FILE, that it is connected to a derived column. After we have the UNION ALL component. Everytime I try to assign one column to the Account column it throws an error telling the metadata...
if I click in the restriction dependence between the UNION ALL component and the DERIVED COLUMN component IT shows that account is not mapped... but in the source (excel source component) it is mapped!!! it is driving me mad.
why i cannot add the account in this table?! to the source column? i HAVE TRIED to remove and recreating everything again... same problem again. I even opened a new package to test.. driving me mad.
does it make sense that the solution was to COPY one good excel source and then just change the new sheet? If I created from root with a new excel source it would throw always the previous errors. So it was just to copy the excel source that was working and then just changing to the desired (new) sheet. and it worked this way. Reset the metadata seems to be flick in SSIS. I would like if someone could share a secure way to do it!

TF293000: The data warehouse has detected data conflicts for the following work item fields

Hi I'm looking for help with the following issue:
In TFS on our SSRS report server whenever I run any of the out the box Sprint Burndown reports the report seems to run successfully but I get the following error in the bottom right hand corner:
Through some research I found that the issue was due to the field definitions in that particular Collection not matching the other collections that we have in TFS. Simple...
In order to determine which field definition in the collection was the issue I used the witadmin command listfields for all of my collections:
witadmin listfields /collection:Collection /n:Microsoft.VSTS.Common.ReviewedBy
This led me to find that the Synchronizes Identity Name Changes definition in the collection mentioned in the TF293000 error was set to a value of true, while it is false in all of my other collections. Issue Found! Should be easy from here...wrong.
The following command should solve my problem:
witadmin changefield /collection:Collection /n:Microsoft.VSTS.Common.ReviewedBy /syncnamechanges:false
*of course with the proper collection url subbed in for the word Collection
However when run and after I confirm that I want to make the change I get the following error:
TF401327: The operation is not supported. The feature is obselete.
I look the error up and it takes me to this page TFS Known Issue which tells me it's a known issue but was resolved in update 1 ... we have update 3.
I then attempted to simply edit the WIT .xml file and update the attribute for that WIT on that collection with false, but when I import the change to the server it tells me it has imported successfully however when I export it I see that the file has not changed.
I have also tried copying the the .xml file from the same WIT in another collection and uploading that to the offending collection and that will not work. I've never had an issue with uploading a WIT as we've made several changes to our TFS workflow before. I'm pretty stuck at this point and just wondering if anyone else has experienced this issue before, thanks!
According to the error info, seems there is a conflict in the TFS Data warehouse and this because 2 fields in different collection has different attributes in the data warehouse as it’s only one data warehouse. To avoid schema conflicts when you export and process data to the data warehouse databases, you must assign the same values to these attributes across all collections:
Field type (the value for this field cannot be changed for an
existing field).
Reporting type.
Reporting name.
What you have done is the correct operation, change/update the attribute for the field in one project collection to match the assignments that are made in other project collections.
You could try to narrow the issue, if this issue only happened on that specific field in the team project collection. All other work item filed working correctly? Also give a try with other collections, such as change the syncnamechanges=true, then set it back to syncnamechanges=false, to see if any issue occurs.
Run the command line on TFS sever machine instead of your develop machine. Clear TFS cahce. And if the filed is not use for reporting about those project collections, you could also try to mark it as non-reportable. More details please refer below links:
Resolve data warehouse schema conflicts
Change a reportable attribute for a work item field

Continue adding input file rows to table after an error using SSIS

I’m a newbie to SSIS, and have an issue with a package that has been puzzling me.
My company has SQL Server Business Intelligence Development Studio 2008 (also, SQL Server 2008 R2). On the Control Flow tab, I have two executables: an Execute SQL Task (Truncate_crm_account_Table) that truncates the SQL Server crm_account table, and a Data Flow Task.
On the Data Flow tab, I have a Flat File Source that opens and reads a pipe-delimited file, and an OLE DB Destination that moves the rows in the input file to the crm_account table.
Data Flow tab
On the Event Handlers tab I have created an OnError Event Handler for the Truncate_crm_account_Table, and an OnError Event Handler for the Data Flow Task. Both OnError Event Handlers are an Execute SQL Task object that writes the error encountered to a SQL Server error table.
This all works fine if there are no issues with the data. When there is an error with the data (for example, on row 10,000), the package writes the records that have passed through its butter to the crm_account table (say, 9,000 or so records). The package also writes the error to the error table, and then stops. What the Project Manager would like the package to do is to continue processing the remainder of the input file after encountering the error.
After reading through a number of forums and posts for SSIS issues that are somewhat related to mine, this is what I have done so far. On the Control Flow tab, for the Data Flow Task, I’ve set MaximumErrorCount = 0 and noted that FailPackageOnFailure = False (also, FailParentOnFailure = False). I’ve seen some posts that mention to set the System variable Propagate = False. Both of these I’ve done, yet the package stops after encountering the error on row 10,000.
System Variables
I don’t know how many records will be in the input file. So, I believe that using a For Loop Container would not be a good object to add to the project. As I’m very new to SSIS, I don’t know whether the ForEach Loop Container or some other object is the way to go. How can this package be minimally modified so that it continues processing the remainder of the input file after encountering an error with the data?
Any help you can provide would be greatly appreciated. Thank you in advance for your time.
Ed
In the data flow tab in the source node, find the error output section on the left side. Click it and change the applicable column in question to 'ignore failure' under the error column.

Error using Dynamic Data Filtering: missing datasource

I am trying to use the ASP.NET Dynamic Data Filtering project, but I'm running into a problem during the configuration.
I'm following the instructions on the author's blog, and everything works like described. Then it tells me to change the datasource using the designer view. I am told to select the "GridDataSource" in the "Configure data source" wizard. This option is not there though.
I get all of the classes in my project, including the DataContext that was generated by Linq. When I choose "Show only DataContext objects", the dropdown ("Choose your context object:") is completely empty.
When I turn of the checkbox and choose my DataContext class, I get asked which table I want and all that. But, as the whole purpose of a Dynamic Data site is NOT to use one single table, that's not much help.
So I've looked at the instructions again and copied the resulting datasource from the example:
<asp:DynamicLinqDataSource ID="GridDataSource" runat="server"
EnableDelete="True" EnableUpdate="True"></asp:DynamicLinqDataSource>
Which is exactly what I had, without the "WhereParameters" nodes in there.
Now, when I run the list page however, I get an exception about a missing datasource from the filtering component. Of course when I remove the DynamicFilterRepeater, it works again.
This is the meat of the exception:
[InvalidOperationException: Missing DataSource]
Catalyst.Web.DynamicData.DynamicFilterRepeater.GetTable() in D:\Catalyst\Projects\DynamicData\Project\Trunk\DynamicData\DynamicData\DynamicFilterRepeater.cs:74
Catalyst.Web.DynamicData.DynamicFilterRepeater.GetFilters() in D:\Catalyst\Projects\DynamicData\Project\Trunk\DynamicData\DynamicData\DynamicFilterRepeater.cs:81
Catalyst.Web.DynamicData.DynamicFilterRepeater.OnInit(EventArgs e) in D:\Catalyst\Projects\DynamicData\Project\Trunk\DynamicData\DynamicData\DynamicFilterRepeater.cs:106
How do I make the DynamicFilterRepeater recognize my datasource?
I'm using VS2010 Pro, on a Win7 machine.
have you looked at the sample project you get when you download the source code.
Have a look at my blog post here Dynamic Data Filtering – Installation

Invisible component in SSIS Dataflow package

Everytime I run my data flow component, it gives me a validation error on a component whose name I cannot find in the editor! I think it happpened when I did ctrl-c on an existing component, and did ctrl-v. and it was successfully pasted, but somehow I can't see it, and therefore can't remove it!. My package is damaged as a result. Any ideas?
Can you see it in the XML when you select View..Code in Visual Studio? Or can you select it from the object drop down list in the Properties window?