Avatar of vsuripeddi
vsuripeddi
 asked on

Script Component in SSIS giving error after writing code for JSON file parsing

I am new to SSIS
I am using a Script component in SSIS for parsing a JSON file.
I am getting errors after I add the C# code in the Script component for parsing of the JSON file.

I am attaching a file which describes the issue that I am facing.
Is this a bug in the Software of Visual Studio 2015 professional? Do I need to re-install Visual Studio 2015 professional?
issues-with-json-scripting.docx
C#JSONSSIS

Avatar of undefined
Last Comment
Kelvin McDaniel

8/22/2022 - Mon
ASKER CERTIFIED SOLUTION
Kelvin McDaniel

Log in or sign up to see answer
Become an EE member today7-DAY FREE TRIAL
Members can start a 7-Day Free trial then enjoy unlimited access to the platform
Sign up - Free for 7 days
or
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.
Not exactly the question you had in mind?
Sign up for an EE membership and get your own personalized solution. With an EE membership, you can ask unlimited troubleshooting, research, or opinion questions.
ask a question
vsuripeddi

ASKER
@Kelvin McDaniel,

Thanks for the update....
I am using SQL Server 2017 developer edition

I am not sure if 2017 developer version has any service packs...

The link you had provided suggests that I change the value to 1 in the Registry Editor

I tried to go into the path
"Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\FipsAlgorithmPolicy" and change the value to 1
However, it did not allow me to change to 1
Also, I could not locate service packs for SQL Server 2017 Developer edition
vsuripeddi

ASKER
@Kelvin McDaniel

I used SSDT tools for Visual Studio 2015 professional edition
Kelvin McDaniel

That's what I figured. That particular setting is not typical for non-corporate/consultant environments and -- more than likely -- it's controlled by policy.

At this point, I think your lowest common denominator option is to create a dll that handles ingesting the file into a collection, which SSIS can then use in its flows. Hopefully, that one layer of abstraction will keep you from getting hit with that exception. If not, then you'll probably have to completely externalize that step.

To be clear:
1. Create a DLL  that SSIS can reference.
2. Use something like FileHelpers to turn the text into a useable collection.
3. Update your to call a method in this DLL, which will return the collection made in #2 above.
All of life is about relationships, and EE has made a viirtual community a real community. It lifts everyone's boat
William Peck