Reporting Services 2005 xml datasource

Hi, i'm having problems with last version of reporting services. i've been trying to create a new datasource whose type was XML, this is posible in this version, but i can't create a report using this datasource, the following message appears :
"A connection cannot be made to the database. Set and check the connection string." .I don't know how to do it, i don't know if i have to set a special connection string or any special condition.
So if someone could know how i can create this type of datasource, please send me a reply.

thanksThe connection string is the URL to the XML document (or SOAP endpoint). Which are you trying to use?|||I am receiving the same error myself, except I'm using a SQL server data source.

When I create the SQL Server Data Source, I put in the credentials, etc. and do a "Test" and receive a successful test message. When I then try and use the shared data source in a report, I receive the above error.

I ran a sniffer on my machine, and found that it was making no attempt to contact the SQL server (no network traffic) when it gave this error.|||Can you post your connection string and query?|||This happens with multiple Datasources (I've tried Native SQL, OLEDB, and ODBC so far).

I've never been able to actually get to the point of entering a query.

<?xml version="1.0" encoding="utf-8"?>
<RptDataSource xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<Name>AltirisCentral</Name>
<DataSourceID>b777bfc6-cb4a-4d4b-8d07-47714739abfe</DataSourceID>
<ConnectionProperties>
<Extension>SQL</Extension>
<ConnectString>Data Source=oakdbs03;Initial Catalog=AltirisCentralNew</ConnectString>
</ConnectionProperties>
</RptDataSource>|||Alright this has been out there for a long time, and no responses...anyone been able to fix this?

Reporting Services 2005 xml datasource

Hi, i'm having problems with last version of reporting services. i've been trying to create a new datasource whose type was XML, this is posible in this version, but i can't create a report using this datasource, the following message appears :
"A connection cannot be made to the database. Set and check the connection string." .I don't know how to do it, i don't know if i have to set a special connection string or any special condition.
So if someone could know how i can create this type of datasource, please send me a reply.

thanksThe connection string is the URL to the XML document (or SOAP endpoint). Which are you trying to use?|||I am receiving the same error myself, except I'm using a SQL server data source.

When I create the SQL Server Data Source, I put in the credentials, etc. and do a "Test" and receive a successful test message. When I then try and use the shared data source in a report, I receive the above error.

I ran a sniffer on my machine, and found that it was making no attempt to contact the SQL server (no network traffic) when it gave this error.|||Can you post your connection string and query?|||This happens with multiple Datasources (I've tried Native SQL, OLEDB, and ODBC so far).

I've never been able to actually get to the point of entering a query.

<?xml version="1.0" encoding="utf-8"?>
<RptDataSource xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<Name>AltirisCentral</Name>
<DataSourceID>b777bfc6-cb4a-4d4b-8d07-47714739abfe</DataSourceID>
<ConnectionProperties>
<Extension>SQL</Extension>
<ConnectString>Data Source=oakdbs03;Initial Catalog=AltirisCentralNew</ConnectString>
</ConnectionProperties>
</RptDataSource>|||Alright this has been out there for a long time, and no responses...anyone been able to fix this?

Reporting Services 2005 xml datasource

Hi, i'm having problems with last version of reporting services. i've been trying to create a new datasource whose type was XML, this is posible in this version, but i can't create a report using this datasource, the following message appears :
"A connection cannot be made to the database. Set and check the connection string." .I don't know how to do it, i don't know if i have to set a special connection string or any special condition.
So if someone could know how i can create this type of datasource, please send me a reply.

thanksThe connection string is the URL to the XML document (or SOAP endpoint). Which are you trying to use?|||I am receiving the same error myself, except I'm using a SQL server data source.

When I create the SQL Server Data Source, I put in the credentials, etc. and do a "Test" and receive a successful test message. When I then try and use the shared data source in a report, I receive the above error.

I ran a sniffer on my machine, and found that it was making no attempt to contact the SQL server (no network traffic) when it gave this error.|||Can you post your connection string and query?|||This happens with multiple Datasources (I've tried Native SQL, OLEDB, and ODBC so far).

I've never been able to actually get to the point of entering a query.

<?xml version="1.0" encoding="utf-8"?>
<RptDataSource xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<Name>AltirisCentral</Name>
<DataSourceID>b777bfc6-cb4a-4d4b-8d07-47714739abfe</DataSourceID>
<ConnectionProperties>
<Extension>SQL</Extension>
<ConnectString>Data Source=oakdbs03;Initial Catalog=AltirisCentralNew</ConnectString>
</ConnectionProperties>
</RptDataSource>|||Alright this has been out there for a long time, and no responses...anyone been able to fix this?sql

Reporting Services 2005 and XML DataSource (as WebService)

I'm trying to build WebService to use result as DataSource for RS 2005 (XML DataSource).

But I have a strange problem.

I have WebMethod with parameters.

When I'm testing my WS in browser then everything works just fine.

But... When I'm trying to call this web-service from VS2005 environment then something strange happens.

Looks like VS passing parameters incorrectly to my WS (not passing at all!)

I've created very simplyfied version just to check parameters:

using System.Xml;
using System.Xml.Serialization;
using System.Messaging;
using System.Text;
using System;
using System.Web.Services;
[WebService(Namespace = "http://company.org/")]
[WebServiceBinding(ConformsTo = WsiProfiles.BasicProfile1_1)]
public class GetRemoteData : System.Web.Services.WebService
{
[WebMethod]
public XmlElement GetData(string CompanyName, string FunctionName, string ParameterList)
{
XmlDocument xmlDocument = new XmlDocument();
XmlElement xmlElement1;
xmlElement1 = xmlDocument.CreateElement("parameters", "values", "urn:errors");
xmlElement1.InnerText = String.Format("{0}, {1}, {2}", CompanyName, FunctionName, ParameterList);
return xmlElement1;
}
}

In the browser WS returns all passed parameters back correctly. VS - not.

What's wrong with my code? Why MSDN example works fine?
Do I need to specify some undocumented (soap specific) attributes?

Where I can find full tutorials how to create RS-compatible web-service?

(Sorry for cross-posting but I have no single reply...)

Hmmm...

I don't understand... Is it so hard? Nobody is using WebService as datasource for RS?

May be I've found some "global unfixable" issue is RS?

I'm checked "address" in my browser server times, but "microsoft" and "MSDN" still are here...

|||

So...?

I've tested different scenarious, but result always is same. RS (only RS!) doesn't passes parameters to my webservice or passing them incorrectly.

How to build RS2005-compatible WebService? I Have non-standard data source and need to show results as RS report.

Very funny result I've got then tried to create WebMethod which returns DataSet! In RS I've got scructure without data instead of data.

Why standard methods from ReportingService2005.asmx (ListChildren, for instance) returns values as "out" parameters?

|||

Dude,
Did you find a solution to this problem?

I fell into this issue for a project I'm developping... but what's weirdest is that I have another project which I developped last year, where I'm using web services with parameters and it works fine.... and I try to find the difference between the 2 of them but I just cannot find it ....

By now, I just know that it the one is working I'm using Kerberos delgation.... besides that, I think everything is the same...

Bye

Reporting Services 2005 and XML DataSource (as WebService)

I'm trying to build WebService to use result as DataSource for RS 2005 (XML DataSource).

But I have a strange problem.

I have WebMethod with parameters.

When I'm testing my WS in browser then everything works just fine.

But... When I'm trying to call this web-service from VS2005 environment then something strange happens.

Looks like VS passing parameters incorrectly to my WS (not passing at all!)

I've created very simplyfied version just to check parameters:

using System.Xml;
using System.Xml.Serialization;
using System.Messaging;
using System.Text;
using System;
using System.Web.Services;
[WebService(Namespace = "http://company.org/")]
[WebServiceBinding(ConformsTo = WsiProfiles.BasicProfile1_1)]
public class GetRemoteData : System.Web.Services.WebService
{
[WebMethod]
public XmlElement GetData(string CompanyName, string FunctionName, string ParameterList)
{
XmlDocument xmlDocument = new XmlDocument();
XmlElement xmlElement1;
xmlElement1 = xmlDocument.CreateElement("parameters", "values", "urn:errors");
xmlElement1.InnerText = String.Format("{0}, {1}, {2}", CompanyName, FunctionName, ParameterList);
return xmlElement1;
}
}

In the browser WS returns all passed parameters back correctly. VS - not.

What's wrong with my code? Why MSDN example works fine?
Do I need to specify some undocumented (soap specific) attributes?

Where I can find full tutorials how to create RS-compatible web-service?

(Sorry for cross-posting but I have no single reply...)

Hmmm...

I don't understand... Is it so hard? Nobody is using WebService as datasource for RS?

May be I've found some "global unfixable" issue is RS?

I'm checked "address" in my browser server times, but "microsoft" and "MSDN" still are here...

|||

So...?

I've tested different scenarious, but result always is same. RS (only RS!) doesn't passes parameters to my webservice or passing them incorrectly.

How to build RS2005-compatible WebService? I Have non-standard data source and need to show results as RS report.

Very funny result I've got then tried to create WebMethod which returns DataSet! In RS I've got scructure without data instead of data.

Why standard methods from ReportingService2005.asmx (ListChildren, for instance) returns values as "out" parameters?

|||

Dude,
Did you find a solution to this problem?

I fell into this issue for a project I'm developping... but what's weirdest is that I have another project which I developped last year, where I'm using web services with parameters and it works fine.... and I try to find the difference between the 2 of them but I just cannot find it ....

By now, I just know that it the one is working I'm using Kerberos delgation.... besides that, I think everything is the same...

Bye

sql

Reporting Server Project 2005 - xml datasource - Querying the data

The way I create the report is I use VS2005 to create the RDL programmatically on the fly. The problem is querying the data when I use XML as a data source (changing the data source is not an option).

I can connect to the XML data source, I enter a basic query in the data tab in VS 2005 and what happens is for some reason or another the above element in XML gets concatenated onto the column name in the result set.

So what I have to do is manually modify the RDL file to accept the new names and then the report works. There has to be a way to not have this happens. Any advice on where I can find information on how to do this would be greatly appreciated. Examples are always welcome.

See below for an example of what I did and an example of the XML data.

XML File Example:
<data>
<Table>
<iss_id>Test Data1</issu_id>
<issue_nm>Test Data1</issue_nm>
</Table>
<Table>
<iss_id>Test Data2</issu_id>
<issue_nm>Test Data2</issue_nm>
</Table>
<data>

XML Query: (I enter this in the data tab in VS 2005)
data/Table

Result:

Table_iss_id Table_issue_nm <--Column Headers
Test Data1 Test Data1
Test Data2 Test Data2

I think it has to do with the webservice web method, and how it needs to be set-up for serializing the parameters correctly to work with the XML data Source. I am having a similar problem which I am documenting here

http://forums.microsoft.com/MSDN/User/MyForums.aspx?SiteID=1

J. C.

Reporting on SharePoint list data?

Hi,
Can anyone direct me to a step by step tutorial on how to create a Reporting
Service's XML Dataset that queries a SharePoint list? I have found bits and
pieces in the SQL Books on line but I have not been able to put it all
together.
Thanks
Jeff.Hello again,
I was able to setup a dataset that queries a SharePoint list so I don't need
help on that any more :-).
The new problem: The report run fine in my development environment but when
I deploy my report and I try to run the report from the RS server I get an
"Query execution failed for data set 'DataSet1'" error. Since the
SharePoint server is running on a different machine I suspect that RS is
running the web service call under the identity of the ASP.NET thread which
does not have rights on the SharePoint server. I tried modifying the thread
pool that IIS is running RS but after I did that Report Manager would not
run any more :-(
What is the correct procedure to get RS to run under a domain account?
Thanks
Jeff.
"Jeff Richardson" <BobcatRidge@.newsgroups.nospam> wrote in message
news:uTVyJEaiGHA.2208@.TK2MSFTNGP05.phx.gbl...
> Hi,
> Can anyone direct me to a step by step tutorial on how to create a
> Reporting Service's XML Dataset that queries a SharePoint list? I have
> found bits and pieces in the SQL Books on line but I have not been able to
> put it all together.
> Thanks
> Jeff.
>|||Hello Jeff,
Thank you for posting in the MSDN newsgroup.
As for the reporting service accessing SPS list data issue, I think your
thought on the security permission is reasonable. At development time in VS
IDE, it use the logon user as the security context to access any remote
datasource (if require authentcated) user. However, after you deployed it
to reportServer, if you haven't explicitly set any credential for the
datasource(used in the report), it'll still use the authenticated user(if
you choose integrated windows credential) or the report server's service
account(if you do not specify any credentials).
Anyway, changing the report server's service identity is certainly not
recommended. I suggest you consider choose a certain credential supply mode
for your SPS datasource. We can configure credentials for report datasource
through two means:
1. In the DataSource's "Credentials" properties at design-time in VS IDE.
2. Use the report manager to configure credentials info for datasource
after deploying to report server.
Here is the BOL reference about how to specify credentials for datasource
connection:
#Specifying Credential and Connection Information
http://msdn2.microsoft.com/en-us/library/ms160330.aspx
Hope this helps.
Regards,
Steven Cheng
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)|||Hi Jeff,
Have got any further progress on this issue or does my last reply helps you
a little? If there is anything else we can help, please feel free to post
here.
Regards,
Steven Cheng
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)