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]
Related
Recently iam trying to update my angular project from 8 to 9. While updating i also updated wijmo from wijmo/wijmo to #grapecity/wijmo package as it supports IVY.
But after the completing the upgradation, i can able to compile the application but i am getting the following error at run time
global-error-handler.service.ts:43 Error: Uncaught (in promise): TypeError: (0 , t[n]) is not a function
TypeError: (0 , t[n]) is not a function
at backend.js:61
at Reflect.<anonymous> (backend.js:61)
at push../node_modules/#grapecity/wijmo.angular2.grid.detail/__ivy_ngcc__/index.js.__decorate (index.js:28)
at index.js:53
at Object../node_modules/#grapecity/wijmo.angular2.grid.detail/__ivy_ngcc__/index.js (index.js:53)
at __webpack_require__ (bootstrap:84)
I'd like to get some more info about this error. The quick thing to check is property initialization order. In Ivy, the properties are interpreted as they are specified in markup (previously wijmo controlled how they were interpreted). So you can break components by setting certain properties before others.
For example, if I tried to set the selectedIndex on a combobox BEFORE I set the data source, then the app would break at runtime because there are no items in the list to select yet.
More info here: https://www.grapecity.com/wijmo/docs/GettingStarted/Angular-Components#property-initialization-order-in-angular-9-ivy-and-higher
The next thing to check is component decorators (if you are inheriting our components). There are some breaking changes in decorators in Ivy.
For example, you might need to add {descendants: true} to ContentChildren queries.
Or you might need to add an #Injectable decorator to your class.
You can read more about breaking changes in Ivy and how to fix them here: https://angular.io/guide/ivy-compatibility-examples
But please feel free to contact us to work directly: wijmoexperts#grapecity.com
I'm trying to run a simple data flow task in SSIS pulling data from Snowflake to SQL Server using a component from CDATA called Snowflake Source.
Connection works and I can also see a preview of the data but when actually running the package I get the following error message:
[CData Snowflake Source [2]] Error: System.Exception: Get data error: Received metadata with an incompatible version number
at CData.SSIS.Snowflake.SSISSourceComponent.PrimeOutput(Int32 outputs, Int32[] outputIDs, PipelineBuffer[] buffers)
at Microsoft.SqlServer.Dts.Pipeline.ManagedComponentHost.HostPrimeOutput(IDTSManagedComponentWrapper100 wrapper, Int32 outputs, Int32[] outputIDs, IDTSBuffer100[] buffers, IntPtr ppBufferWirePacket)
Has anyone experienced this before or know what to do in order to fix it?
Hi I faced this error many time , when i use some custom script component or third party component.
Issue : We do remove or delete some component but some of the reference is not removed from package (it is very tough to debug )
Create fresh package it will work .
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.
Been dealing with a casting exception during design time only that getting me nuts.
I'm trying to create a custom control for winRT (a week view control just like windows phone 8.1). The control works fine during run time but in design time it gives me COMException. During my investigation of the cause of this COMException, I found out that there is a casting exception inside one of the component of my control. This component is a custom listview that implement ContainerContentChanging event. Inside this event there is a casting which raises this exception.
Here is a the custom list view class:-
The code is removed coz the source code is shared below.
The TemplatedListViewEntry cctor look like this one:-
The code is removed coz the source code is shared below.
And the AppointmentModel:-
The code is removed coz the source code is shared below.
OBS!!! while debugging using 2 instance of VS or VS+Blend and put a breakpoint before this line I can see that args.Item is of type ContentControl while during run time it is AppointmentModel.
Could it be a problem with the ItemsSource which is null at design time?
If yes how should I preceed and assign this_ If No, anyone here that can help me figure out what is the problem?
OBS!!! I anyone needs more info please ask and I would gladly share the entire code with you.
Edit 1
Even if i initiate my viewmodel in the cctor of the custom Control, it raises casting exception in Designtime and not in Run tim
Edit 2
After i wrote Edit 1 above i noticed that now i have to Cast exception in two different Styles (CustomWeekView style and TemplatedListView Style) this is if you open Generic.xaml inside Blend. It is really getting annoying and i'm out of thoughts now. That is why i decided to share the source code of this Project, hopfully someone will be able to help looking at it. Below you will see the source code.
CustomWeekView
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.