Deployment Version Problem

We are trying to deploy a report server project from an XP Dev box to a
Server2003 production environment.
Both computers are running SQL Server 2005 with SP1 installed.
We have tried to deploy by (1) a deploy over the network and (2) a database
backup of the ReportServer database and then a restore to the Server 2003
system.
Both methods give us exactly the same error...
The version of the report server database is either in a format that is not
valid, or it cannot be read. The found version is 'Unknown'. The expected
version is 'C.0.8.43'. To continue, update the version of the report server
database and verify access rights.
Why are we getting this error?
Regards,
GaryHi Gary,
Thank you for your posting!
Based on my research and experience, I think you need to reinstall the SP1
on the Server 2003 box.
Please let me know if you get any error message when you reinstall the SP1.
You could send the setup error log to me if you get any error. By default,
the error log file folder is C:\WINDOWS\Hotfix
Please let me know the result. Thank you!
Sincerely,
Wei Lu
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.|||Hi Gary,
How is everything going? Please feel free to let me know if you need any
assistance.
Sincerely,
Wei Lu
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.|||Wei,
It turned out that [apparently] the person who installed sp1 was not a
"member of the SQL Server Administrators Group" and when we followed the
recommeded fix in configuration manager the problem went away.
A mystery that remains for me is that I can't find a "SQL Server
Administrators Group". Do you know exactly what that is? Is it a user with
sysadmin privlidges?
Gary
"Wei Lu [MSFT]" <weilu@.online.microsoft.com> wrote in message
news:t1rUdcOoGHA.2024@.TK2MSFTNGXA01.phx.gbl...
> Hi Gary,
> How is everything going? Please feel free to let me know if you need any
> assistance.
> Sincerely,
> Wei Lu
> 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.
>|||Hi Gary,
Thank you for the update and glad to hear the issue has been resolved.
I think the SQL Server Administrators Group means the SQL Server sysadmin
group. Members of the sysadmin fixed server role can perform any activity
in the server. By default, all members of the Windows
BUILTIN\Administrators group, the local administrator's group, are members
of the sysadmin fixed server role.
If you have any questions or concern, please feel free to let me know.
Sincerely,
Wei Lu
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.

Deployment to Production problems

Somewhat newbie here trying to deploy my first Report. Production machine is
on Windows 2003 - finally got around the reporting service prompting for
windows authentication and now I'm trying to deploy my report through VS
2003. Which reports successful deployment.
If I press the "Run" button in VS 2003 it displays a web page:
[To Parent Directory]
Tuesday, March 29, 2005... Name of my report
No fancy Reporting Service front end, just a hyperlink. If I click on the
link, it displays my report.
If I navigate to http://[servername]/Reports/Pages/Folder.aspx it displays
the web page of SQL Server Reporting Services Home (with the appropriate
GUI), but no folders are listed.
There's obviously some extra step I need to do with 2003 that I didn't need
to setup on my local XP system that I developed and debugged on.Sounds like you haven't given permissions for anyone to see the reports. By
default, only admins can see contents of the server.
--
Brian Welcker
Group Program Manager
Microsoft SQL Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"dtaylor" <dtaylor@.discussions.microsoft.com> wrote in message
news:F158F5D6-E52B-40F6-9F31-31C49358C33D@.microsoft.com...
> Somewhat newbie here trying to deploy my first Report. Production machine
> is
> on Windows 2003 - finally got around the reporting service prompting for
> windows authentication and now I'm trying to deploy my report through VS
> 2003. Which reports successful deployment.
> If I press the "Run" button in VS 2003 it displays a web page:
> [To Parent Directory]
> Tuesday, March 29, 2005... Name of my report
> No fancy Reporting Service front end, just a hyperlink. If I click on the
> link, it displays my report.
> If I navigate to http://[servername]/Reports/Pages/Folder.aspx it displays
> the web page of SQL Server Reporting Services Home (with the appropriate
> GUI), but no folders are listed.
> There's obviously some extra step I need to do with 2003 that I didn't
> need
> to setup on my local XP system that I developed and debugged on.sql

Deployment to one Database 'Clearing' Another...

Hi,

We have a setup whereby our production server builds to a build cube overnight, and if and when this completes successfully, and passes sanity checks, it automatically backs up and restores the cube over the top of a 'live cube'.

This seemed like a fair enough plan - it allows developers to deploy to the production server without breaking the production-live cube, however, we have noticed that deploying to the build cube database sometimes results in the clearing out of the production cube database (much to the users' dismay!).

Anyone else seen anything similar, or have any ideas as to what the problem could be?

Thanks,

Will.

First time I hear about something like that.

Try and see if you can use Synchronization functionality to deploy your changes from test to production. This is more straightforward then backup-copy-restore.

Edward Melomed.
--
This posting is provided "AS IS" with no warranties, and confers no rights.

|||

Hi Edward,

Thanks for your reply.

We currently build the cube on the production server (and 'deploy' the live cube to a databae on the same server) - we're of the view that synchronization is not possible with two databases on the same server. Is this correct?

Regards,

Will.

|||

You are right. You cannot synch from one database to another on the same server instance.

What I suggest in your case is to install another instance of Analysis Server on the same server machine. This case you achive better separation between test and production. If something wrong goes with the test instance, you can easily restart it or, it would be easier to monitor usage of the production server instance without developers interfere. Then, also you'd be able to use synch. Overall in your case second instance might be cleaner solution.

Edward Melomed.
--
This posting is provided "AS IS" with no warranties, and confers no rights.

Deployment to IIS and SQL

I've written a number of reports that now need to be deployed to a production
environment. The reports will be sitting on one IIS server that is
completely hidden from SQL Server. The reports data is retrieved via a web
service.
Can the reports be deployed to IIS and SQL server independantly? If so how?Deployment is easy, you just say where it resides (the IIS portion of RS)
and RS design client within VS does the rest. The real issue for you is
installing RS in this configuration. RS is an asp.net application. Your IIS
has to be configured appropriately for this. Read up on installing where the
SQL Server is not on the same box. This is totally supported. Note that you
will still need a license for the IIS box. You have to have a license on
every box that has RS server software installed.
Bruce L-C
"Buzz" <Buzz@.discussions.microsoft.com> wrote in message
news:90E11231-A3AE-42CC-9CD3-A0F469A00AD4@.microsoft.com...
> I've written a number of reports that now need to be deployed to a
production
> environment. The reports will be sitting on one IIS server that is
> completely hidden from SQL Server. The reports data is retrieved via a
web
> service.
> Can the reports be deployed to IIS and SQL server independantly? If so
how?|||VS does not have to be installed on the Server. Only on the development
machine.
Bruce L-C
"Buzz" <Buzz@.discussions.microsoft.com> wrote in message
news:76C3CEA2-DD41-4F26-A197-8C7FA36D1F41@.microsoft.com...
> We cannot use Visual Studio to deploy in a production environment, its
just
> not installed. I am looking into using the .NET ReportingService() class
to
> deploy via a windows application or script.
> "Bruce Loehle-Conger" wrote:
> > Deployment is easy, you just say where it resides (the IIS portion of
RS)
> > and RS design client within VS does the rest. The real issue for you is
> > installing RS in this configuration. RS is an asp.net application. Your
IIS
> > has to be configured appropriately for this. Read up on installing where
the
> > SQL Server is not on the same box. This is totally supported. Note that
you
> > will still need a license for the IIS box. You have to have a license on
> > every box that has RS server software installed.
> >
> > Bruce L-C
> >
> > "Buzz" <Buzz@.discussions.microsoft.com> wrote in message
> > news:90E11231-A3AE-42CC-9CD3-A0F469A00AD4@.microsoft.com...
> > > I've written a number of reports that now need to be deployed to a
> > production
> > > environment. The reports will be sitting on one IIS server that is
> > > completely hidden from SQL Server. The reports data is retrieved via
a
> > web
> > > service.
> > >
> > > Can the reports be deployed to IIS and SQL server independantly? If
so
> > how?
> >
> >
> >

Deployment problem to production server

I just started using reporting services and have a set of reports done that works on VS2005, however I am struggling with how to deploy this to a production server. The production server does not have a public presnet on the web. If I copy the directory to the production machine it does not work. I realzie that somehow I need to update the report database on the production machine but am lost about how to do that if I cannot connect to the machine from VS2005. I also tried the upload function in report manager.

How do I get my reports onto this box? Surely there is a way to do this without having to have a connection from VS2005. If you do applications that you want to ship to remote users there must be a way to do this.

Thanks

Chuck

In an effort to see how this works I took the reports database from my devleopment machine and installed it onto the server using SQL backup / restore. Does this break the reports database? Do I have to uninstall the reporting services using the SQL install tool or is there a way to recreate the database without doing the SQL uninstall reinstall?

Thanks

Chuck

Deployment of Reports and Data Sources

What is the best way to deploy reports to production considering the fact that different developers would be working on different reports and different data sources. Also consider that the data sources connect to local machines of the developers during report creation and a different database server on deployment.

One way is to use VS2005 to deploy it to production but I am not sure if that is the way to go?

Any ideas?

Thanks

I'd probably create an RSS script which will publish the report to the whatever server it needs to and then actually "fixes up" the report to point to a "production datasource" which already exists on the production box. This "production datasource" points to the correct database on the server.

Use the CreateReport() API to publish the report, and here's a quick sample on fixing up the datasource on a report:

DataSourceReference reference = new DataSourceReference();
DataSource[] dsarray = new DataSource[1];
DataSource ds = new DataSource();
reference.Reference = "/Data Sources/AdventureWorks";
ds.Item = (DataSourceReference)reference;
ds.Name = "AdventureWorks";
dsarray[0] = ds;
rs.SetItemDataSources("/AdventureWorks Sample Reports/Company Sales", dsarray)

It bascially sets the datasource of the Company Sales report to point to the AdventureWorks datasource int he /Data Sources folder.

The nice thing about this idea is that if you have only a few different databases to deal with, you could actually write the RSS script to that it acts on all reports in filesystem folder, and then does some thinking and points each report to the correct "production" data source during the "fix up" phase...

Deployment of Rdl files and datasource to Production Server

Hi All,
I have develoded the SRS report using vs.net , and deployed to my local
sever using vs.net all works fine.
No i need to deploy these reports to a production server where vs.net is
not present.
So can any one tell me how to automate this process of deployment to
production server insteed of mannualy uploading the rld files and creating
data source in report manager.
Can set up be made for this scenarion to my production server.
Please help me it's urgent,
Thanks in advanceYou can create a deployment script with the rss utility in RS. Please
refer to the two scripts that ship with the product and customize it to
deploy to your production server. Command line arguments can be
specified for the datasource, connection string , report server url
etc.|||You have here the code for deploy the report on any SQLRS server
http://www.rdlcomponents.com/ASPExamples/default.aspx
Jerry
"RN" wrote:
> You can create a deployment script with the rss utility in RS. Please
> refer to the two scripts that ship with the product and customize it to
> deploy to your production server. Command line arguments can be
> specified for the datasource, connection string , report server url
> etc.
>

Deployment issue SSRS 2000 reports on Production server

Hi All,
I am facing the issue while deploying Reporting Services 2000 Reports in
Production environment (Windows NT Server and SQL Server 2000) in our
application.
Background: I developed few reports using SQL Server Reporting Services 2000
and are able to deploy in Development environment and those reports are
working fine without any issues.
When we are trying to deploy the same in our Production environment, then we
are facing some issue during the deployment time and not able to deploy those
reports into it. We are followed 3 ways to deploy the same as mentioned below:
Method 1: From Application or report manager screen
(http://servername/reports or http://localhost/reports ) we are trying to
deploy / uploads all the reports one by one, then we are getting the error at
the time of upload as â'The underlying connection was closed: Could not
establish trust relationship with remote server.â'
Method 2: From Reports Designer window, we set build mode as â'Productionâ'
and set all the project environments as Production environment and made a
build and then made deploy. After that we are getting an error as "A
Connection could not be made to the report server
http://servername/reportserver". Later we manually copying all the reports
into Production environment and trying to open the reports, then we are not
able to open / call those reports from our application. Here we could not
able to connect or do not know what to do after copying of the reports into
physical environment of the application.
Method 3: We search thru google and few forums, and then we got to know that
we can deploy reports from the script also. So we tried to do the same as per
their instructions, then we got the error in command prompt as below:
E:\New Folder\Files\Dev2.0\ProfessionalServices\REPORTS>rs -i ps_reports.rss
â's http://servername/reportserver -v parentfolder="DBDReports"
The operation you are attempting requires a secure connection (HTTPS). -->
The operation you are attempting requires a secure connection (HTTPS).
The operation you are attempting requires a secure connection (HTTPS). -->
The operation you are attempting requires a secure connection (HTTPS).
The operation you are attempting requires a secure connection (HTTPS). -->
The operation you are attempting requires a secure connection (HTTPS).
The operation you are attempting requires a secure connection (HTTPS). -->
The operation you are attempting requires a secure connection (HTTPS).
The operation you are attempting requires a secure connection (HTTPS). -->
The operation you are attempting requires a secure connection (HTTPS).
The command completed successfully
Kindly help us to resolve this issue and thanks in advance for your help.
Regards,
nsbThe best way to work this out is from the development environment. You can
deploy a single report by doing a right mouse click on the report and
deploy. What error if any are you getting? Do you have the rights to
publish? One easy thing to try in that regard is to add your user to the
local adminstrators group on the server.
I am betting that you are not part of the administrators group and you were
on the development server. You need to have someone who is in that group to
add you to the appropriate roll in RS.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"nsb" <nsb@.discussions.microsoft.com> wrote in message
news:8327C9F9-4320-4D0B-84F2-B636A0CAC04C@.microsoft.com...
> Hi All,
> I am facing the issue while deploying Reporting Services 2000 Reports in
> Production environment (Windows NT Server and SQL Server 2000) in our
> application.
> Background: I developed few reports using SQL Server Reporting Services
> 2000
> and are able to deploy in Development environment and those reports are
> working fine without any issues.
> When we are trying to deploy the same in our Production environment, then
> we
> are facing some issue during the deployment time and not able to deploy
> those
> reports into it. We are followed 3 ways to deploy the same as mentioned
> below:
> Method 1: From Application or report manager screen
> (http://servername/reports or http://localhost/reports ) we are trying to
> deploy / uploads all the reports one by one, then we are getting the error
> at
> the time of upload as "The underlying connection was closed: Could not
> establish trust relationship with remote server."
> Method 2: From Reports Designer window, we set build mode as "Production"
> and set all the project environments as Production environment and made a
> build and then made deploy. After that we are getting an error as "A
> Connection could not be made to the report server
> http://servername/reportserver". Later we manually copying all the reports
> into Production environment and trying to open the reports, then we are
> not
> able to open / call those reports from our application. Here we could not
> able to connect or do not know what to do after copying of the reports
> into
> physical environment of the application.
> Method 3: We search thru google and few forums, and then we got to know
> that
> we can deploy reports from the script also. So we tried to do the same as
> per
> their instructions, then we got the error in command prompt as below:
> E:\New Folder\Files\Dev2.0\ProfessionalServices\REPORTS>rs -i
> ps_reports.rss
> -s http://servername/reportserver -v parentfolder="DBDReports"
> The operation you are attempting requires a secure connection (HTTPS). -->
> The operation you are attempting requires a secure connection (HTTPS).
> The operation you are attempting requires a secure connection (HTTPS). -->
> The operation you are attempting requires a secure connection (HTTPS).
> The operation you are attempting requires a secure connection (HTTPS). -->
> The operation you are attempting requires a secure connection (HTTPS).
> The operation you are attempting requires a secure connection (HTTPS). -->
> The operation you are attempting requires a secure connection (HTTPS).
> The operation you are attempting requires a secure connection (HTTPS). -->
> The operation you are attempting requires a secure connection (HTTPS).
> The command completed successfully
> Kindly help us to resolve this issue and thanks in advance for your help.
> Regards,
> nsb

Deployment error: Expected C.0.8.43

We are trying to deploy a report server project from an XP Dev box to a Server2003 production environment.

Both computers are running SQL Server 2005 with SP1 installed.

We have tried to deploy by (1) a deploy over the network and (2) a database backup of the ReportServer database and then a restore to the Server 2003 system.

Both methods give us exactly the same error...

The version of the report server database is either in a format that is not valid, or it cannot be read. The found version is 'Unknown'. The expected version is 'C.0.8.43'. To continue, update the version of the report server database and verify access rights.

Why are we getting this error?

Regards,

Gary

Reporting Services data is encrypted. Did you backup and restore the symetric key from the old to the new system ? Otherwiese the information from the report database like report definitions can′t be read.

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de

|||

Check out this link. It does not directly apply to your problem, but it may lead you in right direction for a fix. Using the Configuration tool may be helpfull.

http://blogs.msdn.com/lukaszp/archive/2006/05/18/601340.aspx

Deploying web app, which SQL files do I upload?..

I'm working on a web application that uses SQL Server 2000. Once I'm ready to upload my website to a production server, I need to know how to upload my SQL Server database files to the server. Are there actual files that can be uploaded? I've only deployed a website that works with MySQL to a production server, and there were no files to upload... the database had to be created on the server, and then the data itself had to be exported to text files (on my computer), then imported/uploaded to the production server using SQL statements...

How do I do this?

Thanks~::I need to know how to upload my SQL Server database files to the server.

Ask your provider, systemadministrator or whoever manages this.

Our hosting operation does NOT allow uploads of sql database fiules - you are supposed to create a new database and use the copy database wizard out of SQL Server's enterprise manager.|||hi
i saw http://europe.webmatrixhosting.net, do you know that all hosts provide like this host utilities to work with SQL Server? utilities like http://www.aspenterprisemanager.com??

i'm developing an asp.net storefront that uses SQL Server Database, but i'm worry about after developing that, i want to do what?!! how to manage my database?
tahnk

Deploying Reports to a different Environment

I am developing some reports and the only way I can deploy the reports to
the production server is via files on a CD.
The project manager would like to encapsulate everything into an .MSI file
for deployment.
Is there any documentation on whether this can be done? or how to go about
deploying reports when all I have is a bunch of files
Thanks
BobYou can deploy using RM from VS or through scripts. Best way for you is to
create scripts and put it in a batch file.
Amarnath,MCTS
"Bob" wrote:
> I am developing some reports and the only way I can deploy the reports to
> the production server is via files on a CD.
> The project manager would like to encapsulate everything into an .MSI file
> for deployment.
> Is there any documentation on whether this can be done? or how to go about
> deploying reports when all I have is a bunch of files
> Thanks
> Bob
>
>

Deploying reports on Production server

hello experts,

i need help with deployment of reports (SSRS 2005). we need to deploy many reports (more then 100) on the production everytime we make changes in them.

"the problem is we cannot install visual studio on the server to open the project and use the deploy option from it" i tried using the script - PublishSampleReports.rss

but everytime i run i need to go and manully configure the report to map the shared datasource to it. any way to pass the information in the script itself, or is there any smart way to deploy on production.

/chandresh soni

Hello Chandresh,

You can deploy to your production server from your local machine, or wherever you develop the reports.

Open your report project and go to Properties from the Project menu. From here, you can change your TargetServerURL to be your production server, then when you deploy the reports, they will go there.

Hope this helps.

Jarret

|||

Hi Jarret,

when i try to deploy on the remote server through my local report Solution then i get the below error.

===================================

A connection could not be made to the report server http://seldapp113.corpusers.net/ReportServer. (Microsoft Report Designer)

===================================

The request failed with HTTP status 407: Proxy Authentication Required. (System.Web.Services)

Program Location:

at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
at Microsoft.SqlServer.ReportingServices2006.ReportServiceAuthentication.GetAuthenticationMode()
at Microsoft.ReportDesigner.Project.ReportServiceClient2006.CheckAuthenticated()
at Microsoft.ReportDesigner.Project.ReportClientManager.DetectEndpointAndAuthenticate(String url, ICredentials credentials, String& authCookieName, Cookie& authCookie, EndpointType& endpointType)
at Microsoft.ReportDesigner.Project.ReportClientManager.GetCredentials(String url)
at Microsoft.ReportDesigner.Project.ReportProjectDeployer.PrepareDeploy()

any solution?

Deploying Reports from Development to (Remote) Production Machines

After intial development of some reports on my notebook I will need to deploy them to a production machine remote from my office. In other words I will will not be able to directly from the BI (aka VS) Studio on my notebook.

I had thought that I might be able to simply send the RDL files to the remote site and instruct them to create data sources with the same name (and in the same folders) on the local ReportServer (not the BI Studio) then use the "Upload File" option to upload the RDL files. I have tried this once so far, without success.

The next alternative that I can think of to copy the entire set BI Studio project files to the production server (which should have the BI Studio installed) and deploy normally from there, after changing the TargetServerURL naturally.

Can any one suggest any options?

Dick Campbell

I normally utilise option 2

I create several configurations (1 per environment) then when I need to, just change the configuration from the toolbar dropdown and deploy. No need to manually change the target server every time.

|||

Hi,

is the Webservice not accessible from your notebook ? If yes, you could deploy the reports with the right click on project -option Deploy, sending the RDL files via WebServervices to the Report Server. If this is not an option for you, I would suggest taking the RDL files and send them over to the guys who can install them by loading them up via the web console.

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.de

|||

Thanks Jens,

The second option sounds like the one I am looking for. Can you describe what you mean by "loading up via the web console".

I have tried using "Upload File" from the ReportServer web page but the report would not run even after i checked that tjhere was a working Data Source with the same name on the remote computer. Pehaps i just did something wrong.

Thanks for your reply.

Dick Campbell

|||You will have to reset the datasource to the actual data source in your report server. As the data source gets a GUID during the creation, the Guid of the report datasource and the actual existing might differ.

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.de|||

I have set up the data source with the same name and in the same folder (with localhost and the same databasename) but I didn't realise that it was identified by a GUID so I suspect that this is where the problem lies.

Thanks again for the help.

Best regards,

Dick Campbell

|||

With regard to the data source GUID, if you are refering to the GUID in the RDL file, my mistake may have been to create the data source on the production machine (thus generating a new GUID).

Perhaps I should also upload the data source file (I can't remember what the extension for that is) thereby keeping the same GUID.

So I am thinking that the steps could be:-

1. Create the same folder structure (the first time round) on the production machine using the ReportServer UI.

2. Copy the RDL and data source files onto the machine.

3. Upload each file into the appropriate folders, inlcuding the data source (XML) files, again using the Report Server UI.

4 Change data souces to the new environment if necessary. It they are ".\DatabaseName" this may not be necessary.

Any future upgrades can then just be a matter of sending the changed RDL file and uploading over the existing one. Actyally I suppose that they would just have to be copied over the original.

Why not just copy the entire BI Studio project onto the production machine and deploy it locally? I think that this exposes some customers to the BI Studio when they don't really want to know about it and also leads to the possibility of reports being modified in more than one place.

Deploying Reporting Servoces Reports to the Production Server

Hi,
I am new to Reporting Services. I have installed RS and SQL Server200 on my dev machine. I have created a few .rdl files and deployed them. The TargetServerURL property of my project is set tohttp://localhost/ReportServer. and TargetFolder is "ScoreCardReports".
I have used the reports in my Asp.net app by the RS Webservice (Web Reference URL is :http://localhost/ReportServer/ReportService.asmx.). I used the Render mehtod the get the images from the reports.
Now I will deploy my Asp.net app by creating the msi installer created by the setup & deployment project.
But how to package the .rdl and .rds files so that the app works on the production server ? That will be a windows2003 server.
Please help.The way we deploy to prod is to have the change control person log ontothe prod reporting services, and use the "upload file" option,selecting the .rdl file to import.
|||

I have solved the problem by executing the rs.exe in a bat file. I have created the .rss file containing all the commands to create the reports folder and deploying the reports to the target server. The path of the file has been passed as a parameter to the RS command.

The person to setup the whole application should now only run the .bat file and all the reports will be deployed to the server at one click.

|||

Hi Boss Th Question what u asked is little bit complex.

What u need to generate an .rss file by writing code in VB.Net

use this .rss file with a small command & create a batch file

So whenever u run that batch on a particular server the Reports what u have developed will be deployted on tto the Particular Production Server

Deploying development packages to production

We have a system here where we develop SSIS packages on a development server. I am trying to figure out the cleanest way to promote these changes to a production server where stored procedures/tables that are used in the package are not deployed yet.

When I switch the connection in the package to the production server there are alot of objects in the package that are "invalidated" because they are trying to verify existence of tables/columns. One example is outputing the results of a query to a text file. The text file destination gets a red X on it because it cant grab the columns from the source query (because that stored procedure doesnt exist yet)

Is there a best practices or something on how to deploy packages to a production system? I have tried turning off "ValidateExternalMetaData" with no success.

Thanks!

I think you need to read up on configurations. Configurations allow you to change all sorts of properties/variables external to the ssis package itself.

-Try searching 'configurations' on this forum

-Read books on-line

-Or check many articles on Jamie Thompson's website

http://blogs.conchango.com/jamiethomson/

Hope this helps.

|||

CraigL77 wrote:

We have a system here where we develop SSIS packages on a development server. I am trying to figure out the cleanest way to promote these changes to a production server where stored procedures/tables that are used in the package are not deployed yet.

When I switch the connection in the package to the production server there are alot of objects in the package that are "invalidated" because they are trying to verify existence of tables/columns. One example is outputing the results of a query to a text file. The text file destination gets a red X on it because it cant grab the columns from the source query (because that stored procedure doesnt exist yet)

Is there a best practices or something on how to deploy packages to a production system? I have tried turning off "ValidateExternalMetaData" with no success.

Thanks!

If you use configurations (as Anthony suggested), you can set different connection strings for different environments. However, for the packages to run (and validate) in the production environment, the stored procs will have to be present.

If you change the connection strings in the package, you can ignore the validation errors and copy the packages to the server. They should run successfully as soon as the procs are created.

Deploying Custom Task to Production Server

This seems like a rather simple questions that I've hesitated posting for a day now, but as of yet I can't really find an answer through my searches online.

My SSIS package is using a couple of the Konesans Transforms, this worked fine on my development box with my dev SQL server. The time has come now to deploy my package to my production SQL server. The instructions on installing the transforms on my dev box all uses Visual Studio to add the components.

Is there a way to deploy 3rd party (own my own) SSIS tasks with the package? Does it require a seperate install? How can I do it without Visual Studio?

Thanks for any help,

-Dan

You don't need Visual Studio to install the custom components. You need to add them to the toolbox in BIDS in order to use them, but that's not teh same as installing them.

All you need to do on your production server is make sure that the DLLs are in the GAC (c:\windows\assembly)

-Jamie

|||

Thanks Jamie. I can do that.

I'm hoping though the future might hold a little more functionality in the "Deployment Utility." I'm also using my own libraries for some script tasks and it'd be nice if the deployment utility recognized the dependancy in visual studio and provides a way for it to be installed into the GAC on deployment.

|||

Nice idea. Request it at the Feedback Centre: http://lab.msdn.microsoft.com/productfeedback/default.aspx

-Jamie

|||

Thanks for the link, it was handy for submitting a bug on my FTP issue.

|||I downloaded Visual Basic studio 2005 Trying to do a project for my class final and it has no toolbox? Please help|||

>I downloaded Visual Basic studio 2005 Trying to do a project for my class final and it has no toolbox? Please help

Sorry, we'll not be able to answe this here. Please repost this in the appropriate Visual Studio forum where I'm sure they will jump on it.

deploying CLR objects best practice

Hi,
When I want to deploy CLR assemblies on a SL Server Production Server. What
is the best pratice to define where to store theses assemblies?
In the case of deploying with VS 2005, where the tool put the assemblies on
the server?
Thanks in adavance,
LaurentAssemblies are stored in databases, no matter if you deploy them using
CREATE ASSEMBLY command of VS.NET IDE deployment. Therefore, store the
assembly in the database where you need your CLR objects.
Dejan Sarka, SQL Server MVP
Mentor
www.SolidQualityLearning.com
"laurent banon" <laurent.banon@.soorce.com> wrote in message
news:uNPGDOl%23FHA.2812@.TK2MSFTNGP09.phx.gbl...
> Hi,
> When I want to deploy CLR assemblies on a SL Server Production Server.
> What is the best pratice to define where to store theses assemblies?
> In the case of deploying with VS 2005, where the tool put the assemblies
> on the server?
> Thanks in adavance,
> Laurent
>

deploying changes to cub

Hi,

I have a cube in production server and i want to update that with my latest copy. Is the only way to update it is generate an .xmla again through the deployment wizard? what if i just added a new cube on top of my existing ones. do i need to replace all of them again?

cherriesh

From the underlying XMLA perspective this is definitely possible. The Deployment Wizard uses an Alter command with the AllowCreate option set to true, so aslong as you have not altered the structure of any of the existing cubes and have not chosen the option to do a process operation as part of the deploy, then you should be able to deploy using the Wizard without loosing any data. You would then only need to process the new cube.

It would also be an option to build a CREATE script for just the new cube, but I don't know of any tools that would build this for you. If you have a dev server you could deploy the database to it and connect to it using SSMS and then right click on the new cube and script out the CREATE command.

Note that a cube is dependant on other objects in the database like the dimensions and if any of these have been changed or added then the create script on its own might not work.

Deploying AS to Production

Hi,

Is this the right deployment procedure: I copied the whole project to production server and re-processes the cube. Does the OLAP database resides in \bin or is it the one in C:\Program Files\Microsoft SQL Server\MSSQL.2\OLAP\Data? What's the extension name?

Thanks alot!

cherriesh

Copy the whole project is not really required. The database in the \bin folder is the one that was last built from the BI Development Studio (BIDS), but you do not deploy this file by copying it. In your program files folder where you have installed BIDS you should have an Analysis Services folder with an Analysis Services deployment wizard. This wizard allows you to do a number of things that are useful when deploying to production such as changing or retaining data source connection strings and retaining roles and partitions which may be different between dev and prod.

Also from BIDS, you can setup different profiles and change the target server for the deploy operation from BIDS, but if you needed to change data source connections you would need to remember to do that yourself.

|||

Hi,

After deployment, does the AS database reside in the drive where Analysis Services resides? I'm afraid in the server it is installed in C:\ with only 10GB instead of in the D:\ which has much greater space capacity..

cherriesh

|||

Hi,

If you open up the management studio and right click on the server instance and look at the properties. The Property DataDir will tell you where it's storing the databases. You can change it if it is wrong from C: to D: and you might want to change the backup and log directories property too (BackupDir, LogDir).

Hope that helps

Matt

|||

Hi,

Done with LogDir, BackUpDir and DataDir. I also saw the AllowedBrowsingFolder that is set to :

C:\Program Files\Microsoft SQL Server\MSSQL.3\OLAP\Log|C:\Program Files\Microsoft SQL Server\MSSQL.3\OLAP\Backup

Do I have to change this also?

I've done the Deployment wizard and I have generated the .xmla script. How to proceed from there?

cherriesh

|||

Hi,

Probably worth doing the AllowedBrowsingFolder to, it populates the drop down when you are backup and restore, various things like that.

On the assumption your script looks something like:

<Alter AllowCreate="true" ObjectExpansion="ObjectProperties" xmlns="http://schemas.microsoft.com/analysisservices/2003/engine">

<Object />

<ObjectDefinition>

<Server xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlnsdl2="http://schemas.microsoft.com/analysisservices/2003/engine/2" xmlnsdl2_2="http://schemas.microsoft.com/analysisservices/2003/engine/2/2">

<ID>SERVER</ID>

<Name>SERVER</Name>

<ServerProperties>

<ServerProperty>

<Name>BackupDir</Name>

<Value>D:\Microsoft SQL Server\MSSQL.4\OLAP\Backup</Value>

</ServerProperty>

</ServerProperties>

</Server>

</ObjectDefinition>

</Alter>

Just open an xmla query, run it on the server and restart the service. It should in theory create the directories, pretty sure it did when i have done this before. If there is anything already on the AS Server, best to back that up first then restore it in the new location.

Any problems, just post again.

Matt

|||

hi,

sorry im really new to this. how do i run this .xmla in the server? what command?

thanks a lot!

cherriesh

|||

Hi,

Not to worry. If you open up management studio, click on File, then New, Analysis Services XMLA Query. Type in the server you are changing into "Server Name"

Or there is an icon on the query tool bar, has XMLA in green on it, if you hover over it it will say "Analysis Services XMLA Query".

An Alternative to not running XMLA:

If you are in management studio, connect to the server and right click the server in the object explorer. You can manually change the settings in the properties there.

If I didn't make any sense:

http://www.microsoft.com/technet/prodtechnol/sql/2005/ssasproperties.mspx

(Figures 1 and 2 are the wrong way around though)

remember to restart it the service

Hope that helps

Matt

|||

Thanks a lot! this really helps. is it the AS service that i need to restart? because, when i ran the .xmla, i could already see the AS database in the Management Studio. Does it really important to restart?

thanks!

cherriesh

|||

The changes you make won't actually take effect until you do, just the AS service.

No problem

Matt

Deploying AS to Production

Hi,

Is this the right deployment procedure: I copied the whole project to production server and re-processes the cube. Does the OLAP database resides in \bin or is it the one in C:\Program Files\Microsoft SQL Server\MSSQL.2\OLAP\Data? What's the extension name?

Thanks alot!

cherriesh

Copy the whole project is not really required. The database in the \bin folder is the one that was last built from the BI Development Studio (BIDS), but you do not deploy this file by copying it. In your program files folder where you have installed BIDS you should have an Analysis Services folder with an Analysis Services deployment wizard. This wizard allows you to do a number of things that are useful when deploying to production such as changing or retaining data source connection strings and retaining roles and partitions which may be different between dev and prod.

Also from BIDS, you can setup different profiles and change the target server for the deploy operation from BIDS, but if you needed to change data source connections you would need to remember to do that yourself.

|||

Hi,

After deployment, does the AS database reside in the drive where Analysis Services resides? I'm afraid in the server it is installed in C:\ with only 10GB instead of in the D:\ which has much greater space capacity..

cherriesh

|||

Hi,

If you open up the management studio and right click on the server instance and look at the properties. The Property DataDir will tell you where it's storing the databases. You can change it if it is wrong from C: to D: and you might want to change the backup and log directories property too (BackupDir, LogDir).

Hope that helps

Matt

|||

Hi,

Done with LogDir, BackUpDir and DataDir. I also saw the AllowedBrowsingFolder that is set to :

C:\Program Files\Microsoft SQL Server\MSSQL.3\OLAP\Log|C:\Program Files\Microsoft SQL Server\MSSQL.3\OLAP\Backup

Do I have to change this also?

I've done the Deployment wizard and I have generated the .xmla script. How to proceed from there?

cherriesh

|||

Hi,

Probably worth doing the AllowedBrowsingFolder to, it populates the drop down when you are backup and restore, various things like that.

On the assumption your script looks something like:

<Alter AllowCreate="true" ObjectExpansion="ObjectProperties" xmlns="http://schemas.microsoft.com/analysisservices/2003/engine">

<Object />

<ObjectDefinition>

<Server xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlnsdl2="http://schemas.microsoft.com/analysisservices/2003/engine/2" xmlnsdl2_2="http://schemas.microsoft.com/analysisservices/2003/engine/2/2">

<ID>SERVER</ID>

<Name>SERVER</Name>

<ServerProperties>

<ServerProperty>

<Name>BackupDir</Name>

<Value>D:\Microsoft SQL Server\MSSQL.4\OLAP\Backup</Value>

</ServerProperty>

</ServerProperties>

</Server>

</ObjectDefinition>

</Alter>

Just open an xmla query, run it on the server and restart the service. It should in theory create the directories, pretty sure it did when i have done this before. If there is anything already on the AS Server, best to back that up first then restore it in the new location.

Any problems, just post again.

Matt

|||

hi,

sorry im really new to this. how do i run this .xmla in the server? what command?

thanks a lot!

cherriesh

|||

Hi,

Not to worry. If you open up management studio, click on File, then New, Analysis Services XMLA Query. Type in the server you are changing into "Server Name"

Or there is an icon on the query tool bar, has XMLA in green on it, if you hover over it it will say "Analysis Services XMLA Query".

An Alternative to not running XMLA:

If you are in management studio, connect to the server and right click the server in the object explorer. You can manually change the settings in the properties there.

If I didn't make any sense:

http://www.microsoft.com/technet/prodtechnol/sql/2005/ssasproperties.mspx

(Figures 1 and 2 are the wrong way around though)

remember to restart it the service

Hope that helps

Matt

|||

Thanks a lot! this really helps. is it the AS service that i need to restart? because, when i ran the .xmla, i could already see the AS database in the Management Studio. Does it really important to restart?

thanks!

cherriesh

|||

The changes you make won't actually take effect until you do, just the AS service.

No problem

Matt