Authentication Extension: SoapException: Null Reference

Okay, I thought I almost had this security extension licked, but now I've run
into this and I don't know where to begin looking.
When I call LogonUser() from my UILogon.aspx, I'm getting this:
System.Web.Services.Protocols.SoapException: Server was unable to process
request. --> Object reference not set to an instance of an object. at
System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage
message, WebResponse response, Stream responseStream, Boolean asyncCall) at
System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String
methodName, Object[] parameters) at
Microsoft.SqlServer.ReportingServices.ReportingService.LogonUser(String
userName, String password, String authority) in
c:\dotnet\UserDirectoryWeb\RSSecurityExtension\ReportingService.cs:line 2301
at TBI.UserDirectory.RSSecurityExtension.UILogon.BtnLogon_Click(Object
sender, EventArgs e) in
c:\dotnet\userdirectoryweb\rssecurityextension\uilogon.aspx.cs:line 96
Some descriptions:
ReportingServices.cs is the same one provided with the FormsAuth example.
I checked out the properties unique to SoapException while debugging; there
is nothing of note there (e.g., Actor == "").
My "variation" on the FormsAuth also has ReportManager using Forms
authentication, because it makes managing my single logon mechanism easier.
Could this difference be causing the error?
Finally, I'm quite sure it isn't my custom LogonUser() that's throwing the
error; even a trivial version ("return true;") has this issue. In fact,
since in debug it never breaks at the breakpoint I set, I'm not entirely sure
that it is even being called (it would be underneath the ASP.NET worker
process, would it not?)
This is especially frustrating, since I'm not even sure where to begin
debugging this one. Any suggestions of how I might even begin tracking the
error down would be appreciated.
Thanks,
-MarcWhen debugging, you have to do two things:
1) Copy the Custom Security dll's into the Report Manager\Bin folder and
Report Server\bin folder.
2) Attach to the process aspnet_wp.exe using Debug > Processes...
Cheers,
--
'(' Jeff A. Stucker
\
Business Intelligence
www.criadvantage.com
---
"Marc Lewandowski" <MarcLewandowski@.discussions.microsoft.com> wrote in
message news:0376DE5D-EA59-48EF-B2C0-655AEBA9EFF4@.microsoft.com...
> Okay, I thought I almost had this security extension licked, but now I've
> run
> into this and I don't know where to begin looking.
> When I call LogonUser() from my UILogon.aspx, I'm getting this:
> System.Web.Services.Protocols.SoapException: Server was unable to process
> request. --> Object reference not set to an instance of an object. at
> System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage
> message, WebResponse response, Stream responseStream, Boolean asyncCall)
> at
> System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String
> methodName, Object[] parameters) at
> Microsoft.SqlServer.ReportingServices.ReportingService.LogonUser(String
> userName, String password, String authority) in
> c:\dotnet\UserDirectoryWeb\RSSecurityExtension\ReportingService.cs:line
> 2301
> at TBI.UserDirectory.RSSecurityExtension.UILogon.BtnLogon_Click(Object
> sender, EventArgs e) in
> c:\dotnet\userdirectoryweb\rssecurityextension\uilogon.aspx.cs:line 96
> Some descriptions:
> ReportingServices.cs is the same one provided with the FormsAuth example.
> I checked out the properties unique to SoapException while debugging;
> there
> is nothing of note there (e.g., Actor == "").
> My "variation" on the FormsAuth also has ReportManager using Forms
> authentication, because it makes managing my single logon mechanism
> easier.
> Could this difference be causing the error?
> Finally, I'm quite sure it isn't my custom LogonUser() that's throwing the
> error; even a trivial version ("return true;") has this issue. In fact,
> since in debug it never breaks at the breakpoint I set, I'm not entirely
> sure
> that it is even being called (it would be underneath the ASP.NET worker
> process, would it not?)
> This is especially frustrating, since I'm not even sure where to begin
> debugging this one. Any suggestions of how I might even begin tracking
> the
> error down would be appreciated.
> Thanks,
> -Marc