I have some code within a .Net 3.5 library which call a web service.
The web proxy class was created using WSDL command line tool.
Also the library is wrapped within .Net console, for testing the library works, and SQL Server Integration Services custom task, which is intended to use so that it will be part of the ETL process.
If I run the SSIS custom task and console application on a Windows XP everything works as expected.
However I am currently facing a problem where the response from the web service is not being interpreted correctly when running
within the SSIS custom task on windows server 2008 R2, whereas the response from the web service is correctly understood when running the library within console application on the same server.
Has anyone come across this problem before or know any issues with SSIS and .Net libraries which call web services?
View Complete Post