I am trying to use the IISLog report packs with SQL Server Express reporting services. The guidance in http://blogs.msdn.com/sqlexpress/ indicates that I need to change the target URL and the connection string so that the report packs work with SQL Express. I cannot see how to centrally change the connection string, so that it will affect all the Datasets in the report project. If I try and open a report page and click on the Data tab I get the following error.
A connection cannot be made to the database.
Set and test the connection string.
An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (Microsoft SQL Server, Error: 2)
I have seen this error before when I have mistakenly used "data source=(local); initial catalog=AdventureWorks" instead of "data source=.\SQLExpress; initial catalog=AdventureWorks" as a connection string when creating a new Dataset.
How can I get the IISLog report pack to work with SQL Express
Report Packs and SQL Server Express
GregR
The problem is how to configure the report server. seems the report designer will create a report and has ability to preview it, but cannot connect to server for deployment after the build.
Even though I can connect to the server after I go through the report server configuration tool setup.
==================================error
TITLE: Microsoft Report Designer
------------------------------
A connection could not be made to the report server http://localhost/ReportServer$SQLExpress.
------------------------------
ADDITIONAL INFORMATION:
Client found response content type of '', but expected 'text/xml'.
The request failed with an empty response. (Microsoft.ReportingServices.Designer)
------------------------------
================================error
Your above guidelines are not specifically applicable to IIs 5.1, as there is no " IISDatabase.rds Data Source listed under the Shared Data Sources folder"
Bill Payne
shree123
The Readme.doc file provided with the samples provide two options for deploying the reports. Option 2, using the Report Manager actually gives instructions on how to correctly create a new datasource and then point the uploaded reports to that datasource. I'll leave you to review the readme if you're using this method.
Option 1, describing using Business Intellegence Development Studio (BIDS) doesn't actually address modifying the datasource, so I'll cover that here. If you're using an all Express system, you'll need to have the following installed to do this:
These products are currently in CTP, so you should not be installing them on your production computers...
I tried this and it worked for me. I did find a problem with the Bowser Statistics report generating an error about a parameter not being passed correctly. That is a problem with the report, not with SQL Express. If you're interested in troubleshooting that specific report, I would recoment the SQL Reporting Services forum.
Regards,
Mike Wachal
SQL Express team
----
Please mark your thread as Answered when you get your solution.