Hello, I created a report connecting to XML query. It all works well without any errors when I preview the report using VS. However, after I deployed the report on to Report Manager it doesn't work with the following error.  The data source uses Windows integrated security and I use the same account to run the report through VS and Report Manager. Can anyone please help me what's wrong? Thanks Bo

Hi There Thanks for your posting. Can you please give some more details what method you are using for XML data source. Is XML Embedded Within the Query? Or XML Using URL or XML Using Web Services. Please also see this thread that might resolve your problem http://social.msdn.microsoft.com/Forums/is/sqlreportingservices/thread/75b9092a-e92a-4aca-a45b-96476fa3b496 Many thanks Syed

Hi Syed, Thanks for your reply. The report connects to XML using web services with the following setting. Datasource in the report project: - Name: WebServices2 - Type: XML - Connection string: http://webservices/NRA.Servicesv1/extranetwebservice.asmx Dataset: - Name: Extranet - Data source: WebServices2 - Query string: <Query> <Method Namespace="http://localhost/webservices/" Name="GetSSRSUserData" /> <SoapAction>http://localhost/webservices/GetSSRSUserData</SoapAction> <ElementPath IgnoreNamespaces="True">GetSSRSUserDataResponse{}/GetSSRSUserDataResult{}/SSRSExtranetUser{UserName,GivenName,Surname,Enabled,Expired,LogCount}</ElementPath> </Query> The report runs fine in the preview using VS2005, but doesn't work on Report Manager. Data Source on Report Manager is the same as the above data source with Windows integrated security. I've also had a look at the link you posted, but it didn't solve my problem. Please let me know if you need further details and hope you can point me in the right direction. Thanks Bo

Hi There Thanks for your posting again. Can you please use default name space http://tempuri.org/ instead of localhost both in soap action as well as Method Namespace and see if it make any difference Please have a look on this thread for more details http://stackoverflow.com/questions/4017642/ssrs-xml-data-source-using-web-service-and-parameters http://blog.infotoad.com/?tag=/Namespace I hope this will help Many thanks Syed Qazafi Anjum Please click "Mark as Answer" if this resolves your problem or "Vote as Helpful" if you find it helpful

Thanks for your reply, Syed. However, it didn't fix my problem and I actually have our domain URL address instead of localhost in the both URL which I deliberately replaced it with 'localhost' for security reason when I posted the code. Anything else you can think of? Thanks again

Hi There Thanks for your posting again. Can you please go to report server log and see what the exact error you are getting there. It will help to identify the issue Many thanks Syed Qazafi Anjum Please click "Mark as Answer" if this resolves your problem or "Vote as Helpful" if you find it helpful

Thanks Syde, I had a look at the log file but nothing about this report. It really makes insane because the report runs all fine with design preview, but not working after deployed on the report server. Can anyone please help me!!??

Hi Bobo224, Thanks for your posting. Based on the current information, the issue may be caused by the Kerberos double-hop issue. Kerberos is an authentication protocol that allows clients that create authentication tokens to associate a specific destination to that token. In the failure case there is a mismatch between the destination specified in the token and the report server process configuration. Due to this mismatch, the underlying Kerberos authentication scheme supported by Windows prevents report server from authenticating the user. For more information about double-hop, please see: http://blogs.msdn.com/b/knowledgecast/archive/2007/01/31/the-double-hop-problem.aspx To resolve the issue, you can simply configure the data source to use stored credentials. Additionally, if Kerberos is enabled, you can also address the issue by registering SPN for the report server service. For the detailed information, please see: How to: Configure Windows Authentication in Reporting ServicesRegister a Service Principal Name (SPN) for a Report Server If you have any more questions, please feel free to ask. Regards, Mike Yin

Thanks Mike. I connect data source using credentials stored securely in the report server and it worked! Thanks a lot for your help!