Deploying Reports

Hi All,
I am having a strange problem. I have created a shared data source and
multiple datasets for my reports. The multiple datasets are created to get
data for the different parameters in the report. The report works fine in
Visual Studio. But I don't see the data source listed and when I try to
deploy the report and run it on my webserver. I get the following error
An error has occurred during report processing. (rsProcessingAborted)
Cannot create a connection to data source 'CWPresales'.
(rsErrorOpeningConnection)
For more information about this error navigate to the report server on the
local server machine, or enable remote errors
Can anyone help me with this. I am confused on why I cannot see the
datasource listed in the solution explorer.
Thanks
ShriI am not sure what you mean by solution explorer? I use Report Manager for
this sort of thing. When you deploy the data sources get created BUT they
get created without credentials. You need to use Report Manager to view the
properties of the data source and set the credentials.
Data sources in RS2005 can either be in the same folder as your reports or
in a special folder called Data Sources. Just in case they are hidden in
List View then click on the Show Details link in Report Manager.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"formcreator" <formcreator@.discussions.microsoft.com> wrote in message
news:44C8FFDC-B340-43E5-8244-9AAEA63902D1@.microsoft.com...
> Hi All,
> I am having a strange problem. I have created a shared data source and
> multiple datasets for my reports. The multiple datasets are created to get
> data for the different parameters in the report. The report works fine in
> Visual Studio. But I don't see the data source listed and when I try to
> deploy the report and run it on my webserver. I get the following error
>
> An error has occurred during report processing. (rsProcessingAborted)
> Cannot create a connection to data source 'CWPresales'.
> (rsErrorOpeningConnection)
> For more information about this error navigate to the report server on the
> local server machine, or enable remote errors
> Can anyone help me with this. I am confused on why I cannot see the
> datasource listed in the solution explorer.
> Thanks
> Shri

Deploying Report Server to a Shared Server

I wish to deploy reporting capability on a web page with a ReportViewer to a shared server environment. On my local server, all works fine when IU view the aspx page, I can see my report on my aspx page, images and all.

However, when I deploy to my shared server, I can not get the page to work. Googling, I heard that I needed to copy three files to the bin folder, which I did. I copied:

Microsoft.ReportViewer.Common.dll
Microsoft.ReportViewer.WinForms.dll
Microsoft.ReportViewer.ProcessingObjectModel.dll

But now I get the error when accessing everything but the default page:

"Exception Details: System.Security.Policy.PolicyException: Required permissions cannot be acquired."

Any help would be appreciated,

Thank you,

Paolo

I assume that your local server has Visual Studio installed but your shared server does not. In that case you need to install the Report Viewer Redistributable on your shared server. You can download the redistributable package from here: http://www.microsoft.com/downloads/details.aspx?FamilyID=8a166cac-758d-45c8-b637-dd7726e61367&DisplayLang=en

-Albert

|||

Thank you. Correct assumption.

I just learned that my hosting provider prohibits deploying "reporting software", so I will be looking at one that does. (what is different between a dataset needed to supply a webform and a reporting object ?) But will any shared provider allow installation of the redistributable?

Thanks again,

Paolo

Deploy to Production Server

Hi guys

I have some SSRS reports, shared data sources, data source views and a data model that I need to deploy into production. But I work in a very large firm and we cannot use the Visual Studio interface - I have to provide another team with the files and instructions for installation. Has anyone done this before or have any ideas?

Cheers

XOR

XOR

If you cant use VS.NET you can send them the rdls and ask them to navigate to the Report Maanger and upload the rdls into the directory, if it does not already exist, they will have to create the directory which they can do through the report manager interface also

HTH

|||Thanks HTH, do you know if this action can be scripted at all?|||

XOR

Check out this article, havent tried it myself but it may help you

http://msdn2.microsoft.com/en-us/library/ms159720.aspx

deploy shared datasources

Is there any way to deploy a report to the server and not have to reconfigure its reference to its shared data source?

For instance, if in the development environment my report is pointing to a data source called "MasterDB", and i deploy the RDL file to the server which has a data source called "MasterDB", it doesn't recognize the server-side data source. It informs me shockingly, inaccurately that

"The data source connection information has been deleted. (rsInvalidDataSourceReference)"

I have to go into the report properties and re-bind it manually.

Any thoughts on how to avoid this unnecessary step?

- Ian

If you deploy both the report and shared data source together and then modify the shared data source's properties in Report Manager (to point it to a production database rather than the development database), you can subsequently re-deploy the same report and/or additional reports without having to hook them up manually to the shared data source. (You can do this via VS.NET 2003 "Deploy" command or by uploading the RDL and RDS files from your dev machine to the Report Server.)

The <DataSourceReference/> in your RDL file can use a relative or absolute path to your RDS file. Typically they use relative paths. i.e. "Company Sales.rdl" has its <DataSourceReference/> set to AdventureWorks since AdventureWorks.rds is in the same folder as the RDL. Is this true for your RDS/RDL files? Are they in the same folder? If not, are their relative locations the same between your dev box and the deployment server?

N.B. In your Reporting Services project properties, you should leave the option "OverwriteDataSources" set to false (the default) to prevent subsequent project/solution deployments from overwriting changes to the shared data source.

|||

Thank you for your quick reply.

More specifically, this is the problem I'm having. Maybe there's a principle I haven't understood yet.

1. When I create the report in the IDE, I attach it to the data source called MasterDB, and code looks exactly like this :

<DataSources>
<DataSource Name="MasterDB">
<rd:DataSourceID>74b97554-7a77-4325-a8ad-4b7887aa7d54</rd:DataSourceID>
<DataSourceReference>MasterDB</DataSourceReference>
</DataSource>
</DataSources>

2. When I create the RDS file, The IDE seems to put this data source in a folder called \Shared Data Sources, but the relative path still seems to work despite the fact that the report is in a different folder.
3. In Report Manager, I use the New Data Source screen to create a matching datasource, but pointing to the server-side database.
a) as a variation, if I try to upload an RDS file using the "Upload File" screen, it does actually upload it, but doesn't recognize it as a Data Source. It just thinks it's some XML file.
4. If I have a valid data source on the server, say \MasterDB, and I upload my RDL file -- which still has a relative reference to MasterDB -- to the root, it still doesn't recognize the data source.
5. If i try to change the DataSourceReference to <DataSourceReference>\MasterDB</DataSourceReference>, my dev environment chokes.
6. If I upload the RDL file and go into the report's properties and specify it to point to the valid \MasterDB data source, the report works fine.

I think we're almost there. Any clarification?

|||

I believe you're right about RDS files displaying as XML if you go through Report Manager. I've always initially deployed them using VS.NET 2003. On the project properties, set your TargetServerURL to http://YourDeploymentServer/ReportServer. Set your TargetFolder to wherever you want your RDL and RDS files deployed to. (It will be created if it doesn't exist.) Now right-click your project or solution and select Deploy. Your RDL and RDS files are uploaded to the server. Usually, your Debug configuration should deploy to http://localhost/ReportServer and your Production (or Release) configuration should deploy to http://ProductionServer/ReportServer. Note that you can set up additional configurations that deploy to testing servers or elsewhere. I've used this technique numerous times and I never have to re-link my reports to my shared data sources. Hopefully you can get it working too.

When you're dealing with <DataSourceReference/>, the URL syntax uses "/". For instance, "/My Folder/MySharedDataSource". I suspect that this will still probably cause VS.NET to choke. The GUID in <rd:DataSourceID/> is only used by the Report Designer. So I don't think that's the source of your problem.

As for the RDL and RDS files being in different folders... This is only visual separation in the Solution Explorer. The files still exist in the same physical folder on your local hard drive, which is what's important. They should still upload to the same folder on the report server and their relative paths remain consistent.

|||Thanks, that got it.

- Ian

Deploy Shared Datasource error

Hello,
When I tried to deploy shared data sources, there is an error â'A connection
could not be made to report server to â?¦â' I donâ'tâ' what is wrongâ?¦. Could
anyone please help me to solve this problem?
Thanks in advance
ChiekoCheck the properties of the shared data source from the web folder where it
resides. I'm not sure if this is the norm, but I have to choose Connect
Using: Credentials stored securely in the report server and include a
username and password. For security purposes, use a username that has
read-only access to your database.
Hope that helps!
"chieko" wrote:
> Hello,
> When I tried to deploy shared data sources, there is an error â'A connection
> could not be made to report server to â?¦â' I donâ'tâ' what is wrongâ?¦. Could
> anyone please help me to solve this problem?
> Thanks in advance
> Chieko
>

deploy shared data source

I have modified a shared data source and when I deployed it, the data source
on the Report Manager page did not change. I then deleted the data source
from the Report Manager and redeployed the data source. Then the reports
errored with a data source not found error, so I redeployed the entire
project, but now, even thought the shared data source is in it's original
location all of my reports (50) say that The shared data source reference is
no longer valid. I have redeployed my project again with the same results.
Any help would be appreciatedAre you doing this with RS 2000 or RS 2005?
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Robert Willhite" <RobertWillhite@.discussions.microsoft.com> wrote in
message news:2D8DD698-0E6A-463F-92B2-86EF2BE3C2D0@.microsoft.com...
>I have modified a shared data source and when I deployed it, the data
>source
> on the Report Manager page did not change. I then deleted the data source
> from the Report Manager and redeployed the data source. Then the reports
> errored with a data source not found error, so I redeployed the entire
> project, but now, even thought the shared data source is in it's original
> location all of my reports (50) say that The shared data source reference
> is
> no longer valid. I have redeployed my project again with the same
> results.
> Any help would be appreciated
>|||I am doing this with RS 2000
"Bruce L-C [MVP]" wrote:
> Are you doing this with RS 2000 or RS 2005?
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Robert Willhite" <RobertWillhite@.discussions.microsoft.com> wrote in
> message news:2D8DD698-0E6A-463F-92B2-86EF2BE3C2D0@.microsoft.com...
> >I have modified a shared data source and when I deployed it, the data
> >source
> > on the Report Manager page did not change. I then deleted the data source
> > from the Report Manager and redeployed the data source. Then the reports
> > errored with a data source not found error, so I redeployed the entire
> > project, but now, even thought the shared data source is in it's original
> > location all of my reports (50) say that The shared data source reference
> > is
> > no longer valid. I have redeployed my project again with the same
> > results.
> >
> > Any help would be appreciated
> >
>
>|||First, so you can understand what happened along the way. When you deploy
the default is that the shared datasource does not overwrite. The reason is
so you can have a shared data source when developing that points to a
development database and then when deployed the datasource points to
production. So deleting and deploying again works (you can also force the
deploy to overwrite but I have never done that). Usually when re-deploying a
datasource the issue that comes up are the credentials. In report manager
open up the data source and make sure the credentials are correct.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Robert Willhite" <RobertWillhite@.discussions.microsoft.com> wrote in
message news:34B4224C-6043-4527-83B3-D216414B1A9B@.microsoft.com...
>I am doing this with RS 2000
> "Bruce L-C [MVP]" wrote:
>> Are you doing this with RS 2000 or RS 2005?
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>> "Robert Willhite" <RobertWillhite@.discussions.microsoft.com> wrote in
>> message news:2D8DD698-0E6A-463F-92B2-86EF2BE3C2D0@.microsoft.com...
>> >I have modified a shared data source and when I deployed it, the data
>> >source
>> > on the Report Manager page did not change. I then deleted the data
>> > source
>> > from the Report Manager and redeployed the data source. Then the
>> > reports
>> > errored with a data source not found error, so I redeployed the entire
>> > project, but now, even thought the shared data source is in it's
>> > original
>> > location all of my reports (50) say that The shared data source
>> > reference
>> > is
>> > no longer valid. I have redeployed my project again with the same
>> > results.
>> >
>> > Any help would be appreciated
>> >
>>

Deploy database develop from MSDE

Hi,
I have a small access database develop using msde as back end. I want to put
this backend database on shared drive so that other user can access to it.
My question is
1 - Does I need to setup MSDE on every workstation?
2 - Can other user connect to this database using ODBC?
SF
Thank you very much for this useful tip.
SF
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:4s0fftFsu16iU1@.mid.individual.net...
> hi,
> SF wrote:
> SQL Server/MSDE is not a file based database like Access is... so you only
> have to put the database on the machine hosting the MSDE instance (and not
> on a shared folder).. obviously every machine in the lan can then access
> the MSDE service...
> ODBC api? yes, if you like the hard way, but you probably shoud consider
> other data acces methods, like ADO, Ado.Net and the like...
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz http://italy.mvps.org
> DbaMgr2k ver 0.20.0 - DbaMgr ver 0.64.0 and further SQL Tools
> -- remove DMO to reply
>