RequestSoapContext.Current is always null
Hi, All, I developed a customized delivery extension (SSRS) and deployed it in GAC (global assembly cache) on our report server. I also modified 4 config files (RSReportServer.config, RSWebApplicaiton.config etc) to make the extension work (thanks for Jin’s help). Now when I tried to use this customized delivery extension to schedule a report, I got an error which caused by RequestSoapContext.Current is always null. The version of Microsoft.Web.Services2.dll is 2.0.2.0 in RSReportServer.config which is the same with the version in GAC. And we have .NET SDK (2.0) and WSE 2.0/3.0 installed on the report server. What could be the cause and how to fix it? Thanks. RapidWave
September 30th, 2010 9:10pm

When running subscriptions, there is no web request. So any code that you have in your delivery extension which relies on the HTTP or SOAP context is bound to run into trouble at subscription execution time. It might work when creating the subscription, but I don't think you can reliably know that there is a HTTP or SOAP request for the Delivery Extension. If you are writing a Report Manager Delivery UI extension, then you might get away with it, but it still wouldn't recommend it. What are you try to accomplish by reading the SOAP context? Hope this helps, -LukaszGot a bug or feature request? Tell me about it at http://connect.microsoft.com. This posting is provided "AS IS" with no warranties, and confers no rights.
Free Windows Admin Tool Kit Click here and download it now
October 6th, 2010 5:09am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics