none
SSIS OData Source: Cannot access a disposed object. Object name: 'System.Net.HttpWebResponse' RRS feed

  • Question

  • Hello everyone,

    I need advice. I am pulling data from an API service using SSIS ‘OData Source’ component. The background to this is, everything used to work well, but for some reason there are now failures on the job running this service. The error message is,

    Cannot access a disposed object. Object name: 'System.Net.HttpWebResponse'.

     My connection on OData component is as shown below. Up until now I used to get column list, and was able to pull data through the displayed configuration.

    Now, when I try to view the columns, this is what I get, as shown below.

    I’m not sure what exactly the issue might be. I have asked the data vendor if there is any change that they have made to their configuration on the tables or API settings from their side, and they insist that nothing has changed. One possible reason that I have come across in my long search of the internet is about the computed columns on the source, which may generate the same error message. The vendor insists that they haven’t changed anything on the source side. If they haven’t changed anything and we haven’t changed anything, what could the problem be? Any suggestions and ideas will be greatly welcome.

    Kind regards,


    Mpumelelo

    Monday, October 21, 2019 12:36 PM

Answers

  • Hi Mona,

    Thank you for all the replies. Yesterday I finally managed to get this issue resolved. You will not believe that after all, the problem lied with the vendor. They had a software upgrade a few weeks ago, which interfered with the access permission levels while all along they have been refusing responsibility. When they updated the access permission issues, all started working again on my side without need to amend anything.

    Kind regards,



    Mpumelelo

    Thursday, October 24, 2019 11:23 AM

All replies

  • Hi Mpumelelo,

    May I know if you can test the connection successfully?

    Please refer to Using the OData Source in SQL Server Integration Services .

    Best Regards,

    Mona


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com

    Tuesday, October 22, 2019 3:14 AM
  • Hi Mona,

    I can confirm that the connection works successfully, and has always done. The error only happens when I try to pull the data.

    Kind regards,



    Mpumelelo

    Tuesday, October 22, 2019 7:46 AM
  • Hi Mpumelelo S,

    Please try to recreate the Data Flow Task, the OData Source.

    Please try to use another link.

    Best Regards,

    Mona


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com

    Thursday, October 24, 2019 10:01 AM
  • Hi Mona,

    Thank you for all the replies. Yesterday I finally managed to get this issue resolved. You will not believe that after all, the problem lied with the vendor. They had a software upgrade a few weeks ago, which interfered with the access permission levels while all along they have been refusing responsibility. When they updated the access permission issues, all started working again on my side without need to amend anything.

    Kind regards,



    Mpumelelo

    Thursday, October 24, 2019 11:23 AM
  • Hi Mpumelelo S,

    I'm glad to see that your issue has been solved.

    Please remember to click "Mark as Answer" the responses that resolved your issue.

    This can be beneficial to other community members reading this thread. 

    Thank you.

    Best Regards,

    Mona


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com

    Friday, October 25, 2019 2:01 AM