As we getting below mentioned error when the pipeline component (i.e Gnu PGP Decoder)is dragged and dropped to Decode stage of Pipeline Editor .

we have added the corresponding to cache by using GAC command but still we facing the issue , we have spent around one week to resolve it but not able,  looking for quick help

Regards,

Nagaraja Karur

Hi,

can you paste the Load method of the Pipeline component? Maybe you are not loading the Piepline component properties correctly.

Also check that the pipeline component is allowed to be used as a Decoder. Verify that the Category Id is the following: [ComponentCategory(CategoryTypes.CATID_Decoder]

Re

You might receive the "pipeline component load() method failed on IPersisPropertyBag implementation" error message when you try to drag and drop a custom pipeline component into a pipeline stage. The root cause of this issue can be various, but the most common reason for this kind of failure is because ArgumentException is not caught when you develop the Load method of IPersistPropertyBag interface in your custom pipeline component class. A common way to catch exceptions in Load method is similar to the following:

            catch(ArgumentException)
            {
                return val;
            }
            catch(Exception ex)
            {
                throw new ApplicationException(ex.Message);
            }

If the first catch is missed, you will receive error when Load method runs for first time.

Refer: Error "pipeline component load() method failed on IPersisPropertyBag implementation"

Alternatively, you can refer to an old thread wherein this issue has been discussed in length: Pipeline component Load() method failed on IPersistPropertyBag implementati

Try the following:

1. Add the catch block "catch (System.ArgumentException)"
2. Unregister your pipeline component from Visual Studio tools.
3. Ungac your pipeline component assembly.
4. Delete the file from the <BizTalk Install Folder>\Pipeline Components directory.
5. Close all instances of Visual Studio.
6. Open your Custom Pipeline Component solution and rebuild.
7. Copy your Custom Pipeline Component assembly to <BizTalk Install Folder>\Pipeline Components.
8. Gac your custom pipeline component assembly.
9. Register your custom pipeline component in Visual Studio.
10. Try to drag your pipeline component to the pipeline.

I would suggest to use Pipeline component Wizard avail be over codeplex to create custom Pipeline component skeleton

Pipeline ReadPropertyBag and WritePropertyBag methods you're catching the ArgumentException and re-throwing it. You only need to CATCH IT.

catch (System.ArgumentException)
{
    return val;
}

You need to change this to ONLY the CATCH Block.

catch (System.ArgumentException)
{
}

Thanks

Abhishek

• Edited by Abhishek0127[Abhishek kumar]MVP 21 hours 28 minutes ago

Try the following:

1. Add the catch block "catch (System.ArgumentException)"
2. Unregister your pipeline component from Visual Studio tools.
3. Ungac your pipeline component assembly.
4. Delete the file from the <BizTalk Install Folder>\Pipeline Components directory.
5. Close all instances of Visual Studio.
6. Open your Custom Pipeline Component solution and rebuild.
7. Copy your Custom Pipeline Component assembly to <BizTalk Install Folder>\Pipeline Components.
8. Gac your custom pipeline component assembly.
9. Register your custom pipeline component in Visual Studio.
10. Try to drag your pipeline component to the pipeline.

I would suggest to use Pipeline component Wizard avail be over codeplex to create custom Pipeline component skeleton

Pipeline ReadPropertyBag and WritePropertyBag methods you're catching the ArgumentException and re-throwing it. You only need to CATCH IT.

catch (System.ArgumentException)
{
    return val;
}

You need to change this to ONLY the CATCH Block.

catch (System.ArgumentException)
{
}

Thanks

Abhishek

• Edited by Abhishek0127[Abhishek kumar]MVP Friday, August 07, 2015 9:38 AM

Try the following:

1. Add the catch block "catch (System.ArgumentException)"
2. Unregister your pipeline component from Visual Studio tools.
3. Ungac your pipeline component assembly.
4. Delete the file from the <BizTalk Install Folder>\Pipeline Components directory.
5. Close all instances of Visual Studio.
6. Open your Custom Pipeline Component solution and rebuild.
7. Copy your Custom Pipeline Component assembly to <BizTalk Install Folder>\Pipeline Components.
8. Gac your custom pipeline component assembly.
9. Register your custom pipeline component in Visual Studio.
10. Try to drag your pipeline component to the pipeline.

I would suggest to use Pipeline component Wizard avail be over codeplex to create custom Pipeline component skeleton

Pipeline ReadPropertyBag and WritePropertyBag methods you're catching the ArgumentException and re-throwing it. You only need to CATCH IT.

catch (System.ArgumentException)
{
    return val;
}

You need to change this to ONLY the CATCH Block.

catch (System.ArgumentException)
{
}

Thanks

Abhishek

• Edited by Abhishek0127[Abhishek kumar]MVP Friday, August 07, 2015 9:38 AM

Hi Abhishek,

I tired with all the steps but one of the step as Ungac , i am not able to Ungac the dll, throwing error as we please check with File Name specified. Thanks for response.

Regards,

Nagaraja karur

• Edited by Nagaraja Karur 19 hours 29 minutes ago

Hi Abhishek,

I tired with all the steps but one of the step as Ungac , i am not able to Ungac the dll, throwing error as we please check with File Name specified. Thanks for response.

Regards,

Nagaraja karur

• Edited by Nagaraja Karur Monday, August 10, 2015 11:34 AM

Hi Abhishek,

I tired with all the steps but one of the step as Ungac , i am not able to Ungac the dll, throwing error as we please check with File Name specified. Thanks for response.

Regards,

Nagaraja karur

• Edited by Nagaraja Karur Monday, August 10, 2015 11:34 AM

Ok, let's try to get this straightened out.

1. Gnu PGP Decoder - I'm not familiar with this component.  Can you provide a link?

2. Do not put any custom Pipeline Components in the %BizTalk%\Pipeline Components folder.  See here: BizTalk: Deploying Custom Pipeline Components in BizTalk Server 2006 and Higher

3. If you have the source Code, you can debug this pretty easily by attaching a second instance of Visual Studio to the one where you're adding the component to the Pipeline.  It will break on the error.

4. Our good friend and contributor Leonid Ganeline has a very excellent PGP Pipeline Component in the MSDN Code Gallery that I would recommend using instead: BizTalk: Sample: PGP Encryption/Decryption Pipeline Components

Hi Abhishek,

I tired with all the steps but one of the step as Ungac , i am not able to Ungac the dll, throwing error as we please check with File Name specified. Thanks for response.

You need to provide assembly version as well while you do undeploy activity .

Thank

Abhishek

Ok, let's try to get this straightened out.

1. Gnu PGP Decoder - I'm not familiar with this component.  Can you provide a link?

2. Do not put any custom Pipeline Components in the %BizTalk%\Pipeline Components folder.  See here: BizTalk: Deploying Custom Pipeline Components in BizTalk Server 2006 and Higher

3. If you have the source Code, you can debug this pretty easily by attaching a second instance of Visual Studio to the one where you're adding the component to the Pipeline.  It will break on the error.

4. Our good friend and contributor Leonid Ganeline has a very excellent PGP Pipeline Component in the MSDN Code Gallery that I would recommend using instead: BizTalk: Sample: PGP Encryption/Decryption Pipeline Components

• Proposed as answer by Angie xuMicrosoft contingent staff, Moderator 5 hours 5 minutes ago

Ok, let's try to get this straightened out.

1. Gnu PGP Decoder - I'm not familiar with this component.  Can you provide a link?

2. Do not put any custom Pipeline Components in the %BizTalk%\Pipeline Components folder.  See here: BizTalk: Deploying Custom Pipeline Components in BizTalk Server 2006 and Higher

3. If you have the source Code, you can debug this pretty easily by attaching a second instance of Visual Studio to the one where you're adding the component to the Pipeline.  It will break on the error.

4. Our good friend and contributor Leonid Ganeline has a very excellent PGP Pipeline Component in the MSDN Code Gallery that I would recommend using instead: BizTalk: Sample: PGP Encryption/Decryption Pipeline Components

• Proposed as answer by Angie xuMicrosoft contingent staff, Moderator Monday, August 17, 2015 2:00 AM

Ok, let's try to get this straightened out.

1. Gnu PGP Decoder - I'm not familiar with this component.  Can you provide a link?

2. Do not put any custom Pipeline Components in the %BizTalk%\Pipeline Components folder.  See here: BizTalk: Deploying Custom Pipeline Components in BizTalk Server 2006 and Higher

3. If you have the source Code, you can debug this pretty easily by attaching a second instance of Visual Studio to the one where you're adding the component to the Pipeline.  It will break on the error.

4. Our good friend and contributor Leonid Ganeline has a very excellent PGP Pipeline Component in the MSDN Code Gallery that I would recommend using instead: BizTalk: Sample: PGP Encryption/Decryption Pipeline Components

• Proposed as answer by Angie xuMicrosoft contingent staff, Moderator Monday, August 17, 2015 2:00 AM