Excel Generator
This issue has been solved. See solution.
Steve Wayment
October 13th, 2009
I'm trying to use an Excel Generator in an Integration project. Everything seems to work properly (it shows the number of data rows and displays the column headers), but when I use the DynamicClassRead component for this library in a workflow, I get a Buffer error:
Error Message:
Buffer cannot be null. Parameter name: buffer
I cannot find any referece to "buffer" anywhere in the Workflow or in the Integration project. I have tried changing a few of the advanced settings, but nothing seems to work. Has anyone seen anything like this before?
Thanks.
Filed under: Workflow Solution, Endpoint Management and Virtualization
Update
I did find that I get a different error by unchecking the 'Use Syncfusion Libs' in the DynamicClassRead component. Instead of a 'buffer' error, I now get an error that says:
Value cannot be null. Parameter name: path2
Like the original error, I cannot find any reference to path2 in the Integration project or the Workflow.
I'm curious... what -bit OS
I'm curious... what -bit OS are you running? It might have to with some 3rd party libraries not playing well.
I can also look at this better if you send me the .package/.xls file used. You can email me at richard UNDERSCORE wright AT symantec DOT com.
32-bit OS -- Windows Server
32-bit OS -- Windows Server 2003 SP2
I sent you the Integration and Workflow test projects. Thanks for your help!
Found the problem... you're
Found the problem... you're using a global variable for your "File Data Type Variable Name" in your generated component, and it's empty.
To get around this, have a Read File component immediately before the generated component that reads your .xls into a new stream variable (you can reference it by path if you like, it's what I did). Then replace the globar var hookup in the generated component with the new file stream variable.
Optionally, you could read the file into your global variable, and not change anything with the generated comp. Either way, you'll get better, non-exception-throwing results.
Hope this helps.
Thank you
That works perfectly. I didn't realize the Read component was looking for an already existing file type.
Thanks for your help!
Would you like to reply?
Login or Register to post your comment.