none
SSRS 2012 custom email delivery extender RRS feed

  • Question

  • We have a custom email delivery extender developed for SSRS 2005. Now we want to upgrade it to SSRS 2012. For the custom assembly we have created new project in VS 2008 complied with framework 3.5 We also upgraded the version of “Microsoft.ReportingServices.Interfaces” from SSRS 2012 (v11.0.2100.60). Used the latest webservice "ReportService2010.asmx".

    We did deployment of DLL as per http://technet.microsoft.com/en-in/library/ms153647.aspx

    The custom email delivery localised name also appears in "Report Delivery Options Delivered by:"

    But when we select that we are not able to see the custom UI in report manager and error " System.Web.Services.Protocols.SoapException: System.Web.Services.Protocols.SoapException: The value of parameter 'Extension' is not valid. ---> Microsoft.ReportingServices.Diagnostics.Utilities.InvalidParameterException: The value of parameter 'Extension' is not valid. at Microsoft.ReportingServices.Library.ReportingService2005Impl.GetExtensionSettings(String Extension, ExtensionParameter[]& ExtensionParameters) at Microsoft.ReportingServices.WebServer.ReportingService2010.GetExtensionSettings(String Extension, ExtensionParameter[]& ExtensionParameters) ".

    Also the CreateDataDrivenSubscription() method from code behind throwing error " Unable to cast object of type 'SecureEmailDeliveryExtension.SecureEmailDeliveryUIProvider' to type 'Microsoft.ReportingServices.Interfaces.IDeliveryExtension' " Please help us out to resolve these errors ?

    Friday, April 5, 2013 5:56 AM

Answers

  • Hi,

    For the error: "System.Web.Services.Protocols.SoapException: System.Web.Services.Protocols.SoapException: The value of parameter 'Extension' is not valid"

    This issue may be caused by the settings of your delivery extension. And Reporting Services includes an e-mail delivery extension and a file share delivery extension. Both e-mail delivery extension and file share delivery extension have many settings, maybe one of them is incorrect. For more information about Reporting Services Delivery Extension Settings, please see:
    http://msdn.microsoft.com/en-us/library/ms154020.aspx

    If this issue persists, could you provide detail information about the setting of the delivery.


    Regards,
    Christian HL
    Microsoft Online Community Support


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

    Wednesday, April 10, 2013 9:28 AM

All replies

  • Hi Sandeepvk,

    Thank you for your question.

    I am trying to involve someone more familiar with this topic for a further look at this issue. Sometime delay might be expected from the job transferring. Your patience is greatly appreciated.

    Thank you for your understanding and support.

    Thanks,


    Mike Yin
    TechNet Community Support

    Wednesday, April 10, 2013 8:21 AM
    Moderator
  • Hi,

    For the error: "System.Web.Services.Protocols.SoapException: System.Web.Services.Protocols.SoapException: The value of parameter 'Extension' is not valid"

    This issue may be caused by the settings of your delivery extension. And Reporting Services includes an e-mail delivery extension and a file share delivery extension. Both e-mail delivery extension and file share delivery extension have many settings, maybe one of them is incorrect. For more information about Reporting Services Delivery Extension Settings, please see:
    http://msdn.microsoft.com/en-us/library/ms154020.aspx

    If this issue persists, could you provide detail information about the setting of the delivery.


    Regards,
    Christian HL
    Microsoft Online Community Support


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

    Wednesday, April 10, 2013 9:28 AM