July 30, 2009 at 10:08 am
My SSIS project was humming along just fine until I introduced a script component into the Data Flow. I have a file enumerator loop around the data flow - the error gets thrown in the script component after processing 4 or 5 files - it depending on how big the source files are, but I'd say in general it craps out after processing about 1000 rows combined - not much. I have 2 GB memory on the machine - this should not max it out! Here's the error:
Error: System.TypeInitializationException:
The type initializer for 'Gdip' threw an exception. --->
System.DllNotFoundException:
Unable to load DLL 'gdiplus.dll'
: Not enough storage is available to process this command.
And why is gdiplus even getting loaded??!! It's a graphics device interface and this same error gets thrown when I run from the command line.
Any help would be mucho appreciated. I'm about to give up.
July 30, 2009 at 11:13 am
jreece (7/30/2009)
And why is gdiplus even getting loaded??!! It's a graphics device interface and this same error gets thrown when I run from the command line.
You get the same error when you run what from the command-line? The script? DTExec? ...
[font="Times New Roman"]-- RBarryYoung[/font], [font="Times New Roman"] (302)375-0451[/font] blog: MovingSQL.com, Twitter: @RBarryYoung[font="Arial Black"]
Proactive Performance Solutions, Inc. [/font][font="Verdana"] "Performance is our middle name."[/font]
July 30, 2009 at 11:17 am
Are you calling any custom assemblies or are you using SQLCLR anywhere?
[font="Times New Roman"]-- RBarryYoung[/font], [font="Times New Roman"] (302)375-0451[/font] blog: MovingSQL.com, Twitter: @RBarryYoung[font="Arial Black"]
Proactive Performance Solutions, Inc. [/font][font="Verdana"] "Performance is our middle name."[/font]
July 30, 2009 at 11:35 am
when I run the package from the command line. (Actually, when I choose "start without debugging" in VS
July 30, 2009 at 11:36 am
No, not calling custom assemblies though I do have one loaded as a reference. I wrote a custom class as part of the script component. Thanks so much for replying.
July 30, 2009 at 2:07 pm
Some more info on my "out of memory" error thrown in my script component:
It is configured as an asynchronous transformation. In some cases , I add multiple rows to the output buffer for each input row, then flush the output buffer before processing the the next input row. But most (99%) input rows pass through with no output row added. I just can't understand how I could be running out of memory.
August 11, 2009 at 12:40 pm
I have no idea if this will help you 🙂
But I'm having the exact same issue with a site I'm working on and research has led me to this hotfix
which is a hotfix for that namespace
I'm really hoping this resolves my issue (I don't have control over where the sites hosted 🙁 )
But figured I'd post it in here if on the off chance it works for you
August 13, 2009 at 1:20 pm
No, but thanks for trying! I'm not doing anything webby right now at all - just trying to get a freakin SSIS package with a script component to run. I gave up, wrote the rows that the script component was supposed to process to an internal ADO recordset destination, then processed them with a script task in the control flow. It works but is very slow. 🙁
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply