You searched for the word(s): userid:698469

More Search Options

RSS Available

• Re: Object Moved To <insert url here> In Report Builder (Forms Auth)

  For anybody interested. The problem here is that I had the Domain property set on the forms configuration element. Removing that completely solved the problem.

  Posted to SQL Server Reporting Services (Forum) by stimmell on 9/21/2009

• Re: "The request failed with an empty response." When connecting in mangement studio or report designer.

  For those getting errors like this one, try updating to the latest service pack. It worked for me.

  Posted to SQL Server Reporting Services (Forum) by stimmell on 9/11/2009

• Object Moved To <insert url here> In Report Builder (Forms Auth)

  First of all, I just want to get one little rant out of the way. I've been working professionally with .Net and SQL for some time now and have had to implement and configure a myriad of components for various projects, but getting SQL Reporting Services running with forms authentication is the single most aggrivating thing I've ever encountered. I have an existing web-app we are planning to extend with SRSS for ad-hoc reporting purposes. Said app uses forms authentication with a custom membership

  Posted to SQL Server Reporting Services (Forum) by stimmell on 9/11/2009

• "The request failed with an empty response." When connecting in mangement studio or report designer.

  The SRSS install in question has a custom forms auth provider. SRSS is set up as a virtual directory of an existing web-app. The goal is to have SRSS and the parent app share auth cookies and use one unified login page. That all seems to work fine, if browsing to the report server or report manager and not authenticated on the parent app, you are redirected to the login page of the parent app and redirected appropriately when authenticated. Conversely, when authenticated with the parent app and navagating

  Posted to SQL Server Reporting Services (Forum) by stimmell on 9/8/2009
  Filed under: forms authentication, The request failed with an empty response, custom authentication extension

• Re: Unrecognized element 'add' in upon reading ConfigurationElementCollection

  I feel silly. The problem is in the XML. I had given the error reporting section the name ErrorCodes. That section includes a collection named ErrorCodes. So I either had to wrap the ErrorCodes section in another node named ErrorCodes, or rename the error reporting to something different in the ConfigurationSections area and wrap ErrorCodes in that. Thanks for the replies, it was really aggravating me for a while.

  Posted to Configuration and Deployment (Forum) by stimmell on 9/4/2008

• Re: Unrecognized element 'add' in upon reading ConfigurationElementCollection

  AFAIK, the webserver is irrealivant as I'm just using the debugging environment. For reference, however, it is a .net 3.5 application. I tried using the xml format: < ErrorCode Group= "Foo" Code= "420" Message= "Bar" Source= "Blech" Severity= "Fatal" /> But all that did was change the error message from "Unrecognized element 'add'." to "Unrecognized element 'ErrorCode." There must be some obscure reason that

  Posted to Configuration and Deployment (Forum) by stimmell on 9/4/2008

• Unrecognized element 'add' in upon reading ConfigurationElementCollection

  I get an exception thrown with the message "Unrecognized element 'add'." when attempting to read a ConfigurationSection that contains a custom ConfigurationElementCollection. Thing is, I've been doing custom configurations in this way for years with no problem, I can't fathom what could be going on and have spent far too much time trying to figure things out. Any help would be greatly appreciated. All related code is posted below. Web.Config: < configuration > <

  Posted to Configuration and Deployment (Forum) by stimmell on 9/3/2008
  Filed under: web.config ConfigurationElementCollection ConfigurationElement ConfigurationSection

• Reading UsernameToken in web service

  Using WSE3, I have written a simple web-service and configured it to use only the most basic username/password authentication. The policies are all correctly configured on both ends, and the custom UsernameTokenManager I have implemented works as well. Consuming the web-service requires that a UsernameToken be added to the SOAP headers by using: wswProxy.SetClientCredential<UsernameToken>( new UsernameToken(...)); And that the proper policy be used with: wseProxy.SetPolicy(name); The authentication

  Posted to XML Web Services (Forum) by stimmell on 1/22/2008
  Filed under: webservice webmethod usernametoken

• Re: ViewState failed to load - FormView, DetailsView -- don't skip the "confirmation step"

  Sure, it seems that disabling the viewstate on the formview "fixes" this problem. But what is really going on here? It seems like disabling the viewstate is only fixing the symptoms and not the cause.

  Posted to Web Forms (Forum) by stimmell on 10/30/2007

• Re: ObjectDataSource and ViewState

  [quote user="anas"] hi how did you knew that ? [/quote] By running a trace. I suppose its possible that the trace is errantly reporting the viewstate size of the ODS controls.

  Posted to State Management (Forum) by stimmell on 10/25/2007