deploying reports from vs2005 issue

I'm trying to deploy reports to development server that is running
mssql 2000 and a named instance of mssql 2005 but when I deploy I'm
running into authentication issues. From some articles I'm finding
that this can occur when using SSRS in mssql2000. Do I need to modify
the deployment path in visual studio to some how point to the named
mssql 2005 database, if so how? Also where do I find the
configuration in vs2005 to not overwrite the datasources when a report
is deployed?
Thanks,
JeffWhen you setup for deployment you give it the web address. If your report
server is working that is all you should need to do. For instance it would
look like this for TargetServerURL: http://yourserver/ReportServer
Now, to be able to deploy you need to have the rights to do so. This is
Reporting Services rights. It has nothing to do with SQL Server DB rights.
Can you run reports? First make sure of that.
If your domain account is in the local administrators group on the server
then you will automatically have all the rights you need. Again, this is
around your windows account, not your SQL Server access rights.
Also, the default in vs2005 is to NOT overwrite a datasource. Right mouse
click on the project, properties. This is where you set the targetserverurl
and also the overwritedatasources (which you want to be false).
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Jeffa" <Jeff.Arlt@.gmail.com> wrote in message
news:1183479523.437839.111440@.j4g2000prf.googlegroups.com...
> I'm trying to deploy reports to development server that is running
> mssql 2000 and a named instance of mssql 2005 but when I deploy I'm
> running into authentication issues. From some articles I'm finding
> that this can occur when using SSRS in mssql2000. Do I need to modify
> the deployment path in visual studio to some how point to the named
> mssql 2005 database, if so how? Also where do I find the
> configuration in vs2005 to not overwrite the datasources when a report
> is deployed?
> Thanks,
> Jeff
>

deploying MSDE instance

Hi there,
I am having a hard time trying finding information on how to deploy my
instance along with my application. I found the following link to be useful
in attaching my database to the server
(http://support.microsoft.com/kb/q240293/) but how do I create that instance
for the attachment to occur. My application was coded using Visual C++ so
the deployment using the VB Package and Deployment Wizard does not apply. I
looked endless on the web on how to do this but to no avail.
I'm using Installshield X to package my install. I have it setup so that the
MSDE install folder is copied onto the c: drive. But I need to create the
instance in the command line using setup.exe. I don't know how to call the
command line within the Installshield script to create my instance. Am I
headed in the wrong direction or is there some easier way? Any help would be
much appreciated!
Hi
These may help!
http://msdn.microsoft.com/library/de...eddingmsde.asp
http://www.microsoft.com/sql/msde/te...ntegration.asp
John
"luv2travel" wrote:

> Hi there,
> I am having a hard time trying finding information on how to deploy my
> instance along with my application. I found the following link to be useful
> in attaching my database to the server
> (http://support.microsoft.com/kb/q240293/) but how do I create that instance
> for the attachment to occur. My application was coded using Visual C++ so
> the deployment using the VB Package and Deployment Wizard does not apply. I
> looked endless on the web on how to do this but to no avail.
> I'm using Installshield X to package my install. I have it setup so that the
> MSDE install folder is copied onto the c: drive. But I need to create the
> instance in the command line using setup.exe. I don't know how to call the
> command line within the Installshield script to create my instance. Am I
> headed in the wrong direction or is there some easier way? Any help would be
> much appreciated!
|||Thanks John!
"John Bell" wrote:
[vbcol=seagreen]
> Hi
> These may help!
> http://msdn.microsoft.com/library/de...eddingmsde.asp
> http://www.microsoft.com/sql/msde/te...ntegration.asp
> John
> "luv2travel" wrote:

deploying MSDE instance

Hi there,
I am having a hard time trying finding information on how to deploy my
instance along with my application. I found the following link to be useful
in attaching my database to the server
(http://support.microsoft.com/kb/q240293/) but how do I create that instance
for the attachment to occur. My application was coded using Visual C++ so
the deployment using the VB Package and Deployment Wizard does not apply. I
looked endless on the web on how to do this but to no avail.
I'm using Installshield X to package my install. I have it setup so that the
MSDE install folder is copied onto the c: drive. But I need to create the
instance in the command line using setup.exe. I don't know how to call the
command line within the Installshield script to create my instance. Am I
headed in the wrong direction or is there some easier way? Any help would be
much appreciated!Hi
These may help!
http://msdn.microsoft.com/library/d...beddingmsde.asp
http://www.microsoft.com/sql/msde/t...integration.asp
John
"luv2travel" wrote:

> Hi there,
> I am having a hard time trying finding information on how to deploy my
> instance along with my application. I found the following link to be usefu
l
> in attaching my database to the server
> (http://support.microsoft.com/kb/q240293/) but how do I create that instan
ce
> for the attachment to occur. My application was coded using Visual C++ so
> the deployment using the VB Package and Deployment Wizard does not apply.
I
> looked endless on the web on how to do this but to no avail.
> I'm using Installshield X to package my install. I have it setup so that t
he
> MSDE install folder is copied onto the c: drive. But I need to create the
> instance in the command line using setup.exe. I don't know how to call the
> command line within the Installshield script to create my instance. Am I
> headed in the wrong direction or is there some easier way? Any help would
be
> much appreciated!|||Thanks John!
"John Bell" wrote:
[vbcol=seagreen]
> Hi
> These may help!
> http://msdn.microsoft.com/library/d...beddingmsde.asp
> http://www.microsoft.com/sql/msde/t...integration.asp
> John
> "luv2travel" wrote:
>

deploying MSDE instance

Hi there,
I am having a hard time trying finding information on how to deploy my
instance along with my application. I found the following link to be useful
in attaching my database to the server
(http://support.microsoft.com/kb/q240293/) but how do I create that instance
for the attachment to occur. My application was coded using Visual C++ so
the deployment using the VB Package and Deployment Wizard does not apply. I
looked endless on the web on how to do this but to no avail.
I'm using Installshield X to package my install. I have it setup so that the
MSDE install folder is copied onto the c: drive. But I need to create the
instance in the command line using setup.exe. I don't know how to call the
command line within the Installshield script to create my instance. Am I
headed in the wrong direction or is there some easier way? Any help would be
much appreciated!Hi
These may help!
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnsql2k/html/sql_embeddingmsde.asp
http://www.microsoft.com/sql/msde/techinfo/MSDEintegration.asp
John
"luv2travel" wrote:
> Hi there,
> I am having a hard time trying finding information on how to deploy my
> instance along with my application. I found the following link to be useful
> in attaching my database to the server
> (http://support.microsoft.com/kb/q240293/) but how do I create that instance
> for the attachment to occur. My application was coded using Visual C++ so
> the deployment using the VB Package and Deployment Wizard does not apply. I
> looked endless on the web on how to do this but to no avail.
> I'm using Installshield X to package my install. I have it setup so that the
> MSDE install folder is copied onto the c: drive. But I need to create the
> instance in the command line using setup.exe. I don't know how to call the
> command line within the Installshield script to create my instance. Am I
> headed in the wrong direction or is there some easier way? Any help would be
> much appreciated!|||Thanks John!
"John Bell" wrote:
> Hi
> These may help!
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnsql2k/html/sql_embeddingmsde.asp
> http://www.microsoft.com/sql/msde/techinfo/MSDEintegration.asp
> John
> "luv2travel" wrote:
> > Hi there,
> >
> > I am having a hard time trying finding information on how to deploy my
> > instance along with my application. I found the following link to be useful
> > in attaching my database to the server
> > (http://support.microsoft.com/kb/q240293/) but how do I create that instance
> > for the attachment to occur. My application was coded using Visual C++ so
> > the deployment using the VB Package and Deployment Wizard does not apply. I
> > looked endless on the web on how to do this but to no avail.
> >
> > I'm using Installshield X to package my install. I have it setup so that the
> > MSDE install folder is copied onto the c: drive. But I need to create the
> > instance in the command line using setup.exe. I don't know how to call the
> > command line within the Installshield script to create my instance. Am I
> > headed in the wrong direction or is there some easier way? Any help would be
> > much appreciated!

Deployed Application isn't connecting to SQL Server

When deploying my application that uses sql server it doesn't connect to the server.

I checked the connection string & it's ok the server instance is the same.

The computer name isn't the same & i use the .\SQLExpress as the data source.

I get an error saying 'sqlserver does not allow remote connections error 26 locating server / instance specified'.

Since computer name is changed, can you try to recreate the data source again? When creating a datasource, you can verify that if the datasource is ok to connect to the server.|||Another thing to look at is that if computer name is changed, the servername might not be valid. Can you run select @.@.servername to verify?|||

This link can help you.

http://blogs.msdn.com/sql_protocols/archive/2006/03/23/558651.aspx

|||

The connection string from the dataset that visual studio generated was wrong

it needed to be .\SQLExpress thanks to all for the help

Deploy to named instance

Is it possible to deploy to a named instance from the default instance on the same machine? I keep gettin 'unable to connect' error.

Thanks.

SQL Server 2005 sp 2/Vista

> deploy to a named instance from the default instance on the same machine?

What does it mean "deploy from instance" ? Normally the project is deployed from BI Dev Studio. There in the Deployment Options, you specify the named instance as a server to deploy to, and it will work.

|||

I get the following error message: The project could not be deployed to the '...' server because of the following connectivity problems" '....' instance was not found on '..' server

I know the instance is there because I can open it in sql server mgmt studio. I can also use the named instance as a data source.

|||

Further information: Microsoft doesn't like instance names to include the '_' character, as in SQL_TWO.

Getting closer....just one Mdx script error

Deploy SRS created in 2005 to SQL 2000 SRS

I have SQL 2005 on my dev computer. Can I deploy reports from it to a SRS 2000 instance? If not, what do I have to install on my dev computer to generate SRS 2000 reports?

You would need to install VS.Net 2003 and the developer plug in that comes with Reporting Services 2000 install.

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