Deployment with Hardware Load balancing.

I am currently planning the deployment of reporting services into a hardware
load balanced environment. The documentation from MS only covers MS's NLB
software. Has anyone had any experience deploying with a hardware load
balancer. Specifically F5 load balencing equipment.
Thanks,
Adrian.Hello Adrian,
A report server Web farm is a collection of report server instances that
share the same report server database. Reporting Services does not provide
Web farm deployment functionality. To deploy Reporting Services in a Web
farm, you can use network load balancing (NLB) functionality provided
through Windows servers, Microsoft Application Center, or third-party
software that supports Web farm deployment. The load balancer can be
software or hardware.
For the "Steps for Deploying a Report Server Web Farm", please refer to the
"Steps for Deploying a Report Server Web Farm" section in the following web
site:
Enterprise Deployment Model
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/rsadmin/htm
/drp_deploying_v1_0h9e.asp
More information for reference:
Installing a Report Server Web Farm
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/RSinstall/h
tm/gs_installingrs_v1_2ckm.asp
305064 How To Set Up an NLB Cluster for Application Center 2000
http://support.microsoft.com/?id=305064
Regarding the information of how to implement and maintain NLB clusters, if
you use a third-party hardware load balancer, please contact the hardware
vendor support to inquire about this issue. I believe that they will assist
you best since they will have the proper material resources to resolve this
problem.
I hope the information is helpful.
Sophie Guo
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
=====================================================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 Sophie,
To confirm that I understand what you are saying, here is my take on how you
would deploy a multi node reporting server with hardware load balancing.
Note: Database tier is being deployed as active/active SQL Cluster.
1. Deploy the initial reporting services server node as per a vanilla
install.
2. Deploy any subsequent nodes by joining the nodes to the initial reporting
services node by specifying the RSWEBFARMSERVER property in the installation
3. Overlay the web nodes with either a hardware or software load balancing
solution.
Thanks,
Adrian.
"Sophie Guo [MSFT]" <v-sguo@.online.microsoft.com> wrote in message
news:Tu9WDs$QFHA.3704@.TK2MSFTNGXA02.phx.gbl...
> Hello Adrian,
> A report server Web farm is a collection of report server instances that
> share the same report server database. Reporting Services does not provide
> Web farm deployment functionality. To deploy Reporting Services in a Web
> farm, you can use network load balancing (NLB) functionality provided
> through Windows servers, Microsoft Application Center, or third-party
> software that supports Web farm deployment. The load balancer can be
> software or hardware.
> For the "Steps for Deploying a Report Server Web Farm", please refer to
> the
> "Steps for Deploying a Report Server Web Farm" section in the following
> web
> site:
> Enterprise Deployment Model
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/rsadmin/htm
> /drp_deploying_v1_0h9e.asp
> More information for reference:
> Installing a Report Server Web Farm
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/RSinstall/h
> tm/gs_installingrs_v1_2ckm.asp
> 305064 How To Set Up an NLB Cluster for Application Center 2000
> http://support.microsoft.com/?id=305064
> Regarding the information of how to implement and maintain NLB clusters,
> if
> you use a third-party hardware load balancer, please contact the hardware
> vendor support to inquire about this issue. I believe that they will
> assist
> you best since they will have the proper material resources to resolve
> this
> problem.
> I hope the information is helpful.
>
> Sophie Guo
> Microsoft Online Partner Support
> Get Secure! - www.microsoft.com/security
> =====================================================> 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.
>|||One further point, this is an Enterprise only feature.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Adrian Russell" <adrianru@.avanade.com> wrote in message
news:ujF3s%23ARFHA.356@.TK2MSFTNGP14.phx.gbl...
> Hi Sophie,
> To confirm that I understand what you are saying, here is my take on how
you
> would deploy a multi node reporting server with hardware load balancing.
> Note: Database tier is being deployed as active/active SQL Cluster.
> 1. Deploy the initial reporting services server node as per a vanilla
> install.
> 2. Deploy any subsequent nodes by joining the nodes to the initial
reporting
> services node by specifying the RSWEBFARMSERVER property in the
installation
> 3. Overlay the web nodes with either a hardware or software load balancing
> solution.
> Thanks,
> Adrian.
> "Sophie Guo [MSFT]" <v-sguo@.online.microsoft.com> wrote in message
> news:Tu9WDs$QFHA.3704@.TK2MSFTNGXA02.phx.gbl...
> > Hello Adrian,
> >
> > A report server Web farm is a collection of report server instances that
> > share the same report server database. Reporting Services does not
provide
> > Web farm deployment functionality. To deploy Reporting Services in a Web
> > farm, you can use network load balancing (NLB) functionality provided
> > through Windows servers, Microsoft Application Center, or third-party
> > software that supports Web farm deployment. The load balancer can be
> > software or hardware.
> >
> > For the "Steps for Deploying a Report Server Web Farm", please refer to
> > the
> > "Steps for Deploying a Report Server Web Farm" section in the following
> > web
> > site:
> >
> > Enterprise Deployment Model
> >
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/rsadmin/htm
> > /drp_deploying_v1_0h9e.asp
> >
> > More information for reference:
> >
> > Installing a Report Server Web Farm
> >
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/RSinstall/h
> > tm/gs_installingrs_v1_2ckm.asp
> >
> > 305064 How To Set Up an NLB Cluster for Application Center 2000
> > http://support.microsoft.com/?id=305064
> >
> > Regarding the information of how to implement and maintain NLB clusters,
> > if
> > you use a third-party hardware load balancer, please contact the
hardware
> > vendor support to inquire about this issue. I believe that they will
> > assist
> > you best since they will have the proper material resources to resolve
> > this
> > problem.
> >
> > I hope the information is helpful.
> >
> >
> > Sophie Guo
> > Microsoft Online Partner Support
> >
> > Get Secure! - www.microsoft.com/security
> >
> > =====================================================> > 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.
> >
>|||By Enterprise only I mean both SQL Server db has to be enterprise and the
Reporting Services install has to be Enterprise. Plus, for each server in
the web farm with Reporting Services you need an SQL Server Enterprise
license.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Adrian Russell" <adrianru@.avanade.com> wrote in message
news:ujF3s%23ARFHA.356@.TK2MSFTNGP14.phx.gbl...
> Hi Sophie,
> To confirm that I understand what you are saying, here is my take on how
you
> would deploy a multi node reporting server with hardware load balancing.
> Note: Database tier is being deployed as active/active SQL Cluster.
> 1. Deploy the initial reporting services server node as per a vanilla
> install.
> 2. Deploy any subsequent nodes by joining the nodes to the initial
reporting
> services node by specifying the RSWEBFARMSERVER property in the
installation
> 3. Overlay the web nodes with either a hardware or software load balancing
> solution.
> Thanks,
> Adrian.
> "Sophie Guo [MSFT]" <v-sguo@.online.microsoft.com> wrote in message
> news:Tu9WDs$QFHA.3704@.TK2MSFTNGXA02.phx.gbl...
> > Hello Adrian,
> >
> > A report server Web farm is a collection of report server instances that
> > share the same report server database. Reporting Services does not
provide
> > Web farm deployment functionality. To deploy Reporting Services in a Web
> > farm, you can use network load balancing (NLB) functionality provided
> > through Windows servers, Microsoft Application Center, or third-party
> > software that supports Web farm deployment. The load balancer can be
> > software or hardware.
> >
> > For the "Steps for Deploying a Report Server Web Farm", please refer to
> > the
> > "Steps for Deploying a Report Server Web Farm" section in the following
> > web
> > site:
> >
> > Enterprise Deployment Model
> >
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/rsadmin/htm
> > /drp_deploying_v1_0h9e.asp
> >
> > More information for reference:
> >
> > Installing a Report Server Web Farm
> >
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/RSinstall/h
> > tm/gs_installingrs_v1_2ckm.asp
> >
> > 305064 How To Set Up an NLB Cluster for Application Center 2000
> > http://support.microsoft.com/?id=305064
> >
> > Regarding the information of how to implement and maintain NLB clusters,
> > if
> > you use a third-party hardware load balancer, please contact the
hardware
> > vendor support to inquire about this issue. I believe that they will
> > assist
> > you best since they will have the proper material resources to resolve
> > this
> > problem.
> >
> > I hope the information is helpful.
> >
> >
> > Sophie Guo
> > Microsoft Online Partner Support
> >
> > Get Secure! - www.microsoft.com/security
> >
> > =====================================================> > 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.
> >
>|||I'm operating in exactly this configuration. As mentioned by others,
its really straight forward to setup:
Prerequsites:
- A Sql Server 2000 Enterprise instance with SP3a
Installation:
1) Install Sql Reporting 2000 Enterprise on the first web server.
During installation it creates the needed ReportServer and
ReportServerTempDb databases.
2) Install Sql Reporting 2000 Enterprise on each subsequent server in
Farm and point them at the ReportServer DB created in step 1. (repeat
for each additional server)
3) Deploy RDL's via ReportsServer web service from any of the servers
(since they share the same DB and therefore will share the RDL's once
they are uploaded).
4) Start using your servers. (or begin applying Service packs)
Note: SP2 will require one extra step which is to run RSActivate in
order to join your additional Report Server nodes to the group. In
pre-SP2 installations, this is done automatically for you.
One thing to consider when doing the F5 setup; make sure to setup
Server Affinity using a time-based session so you don't run into any
problems with ASP.NET post-backs. Typically I set the session
expiration to 40 minutes, but it all depends upon your
user-characteristics. Also I have found it helpful to utilize the
"Least Used" algorithm rather than the default "Round Robin" approach
to load balancing.
Obviously, there are numerous architectural and infrastructural
decisions required throughout this process, but this should give you
the 10k meter view.
I am happy with F5 for load balancing so far, so I hope this works out
for you.
Enjoy.
Lance Hunt
http://weblogs.asp.net/lhunt/|||Hello Adrian,
For the second item:
2. Deploy any subsequent nodes by joining the nodes to the initial
reporting services node by specifying the RSWEBFARMSERVER property in the
installation
The RSWEBFARMSERVER property is specified in the command prompt. To install
a web farm, you have to specify the RSDATABASENAME and RSDATABASESERVER
property in the command prompt.
For more information, please refer to the following topic in BOL:
"Installing Reporting Services From the Command Line"
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/RSinstall/h
tm/gs_installingrs_v1_6h6h.asp
I hope the information is helpful.
Sophie Guo
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
=====================================================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!
I'm also F5 Hardware load balancing, but I'm running into a problem.
Right now, we have 2 web servers in a cluster, and an F5 load balancer
infront of it. Both web servers have Kerberos delegation enabled, and
I can access Reporting services via Web Service just fine when I access
the web servers directly. However, when I put the F5 load balancer
infront, I get an Authentication error. The load balancer appears to
be sending my credentials as Anonymous! Has this happened to anyone?
Is there a Kerberos setting on this F5 hardware load balancer? I'm
unfamiliar with the hardware, and I'm trying to contact my IT
department to contact the vendor. That might take a while. I'm hoping
someone here has an answer.
Thanks!
Roy Assaly
Sophie Guo [MSFT] wrote:
> Hello Adrian,
> For the second item:
> 2. Deploy any subsequent nodes by joining the nodes to the initial
> reporting services node by specifying the RSWEBFARMSERVER property in
the
> installation
> The RSWEBFARMSERVER property is specified in the command prompt. To
install
> a web farm, you have to specify the RSDATABASENAME and
RSDATABASESERVER
> property in the command prompt.
> For more information, please refer to the following topic in BOL:
> "Installing Reporting Services From the Command Line"
>
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/RSinstall/h
> tm/gs_installingrs_v1_6h6h.asp
> I hope the information is helpful.
> Sophie Guo
> Microsoft Online Partner Support
> Get Secure! - www.microsoft.com/security
> =====================================================> 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 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 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 - Unable to find the requested .Net Framework Data Provider

I am able to work fine in my development environment, however when I deploy the application to a clean machine, I get the dreaded "Unable to find the requested .Net Framework Data Provider" error.

I have included the eight dlls required by the Sql Server 2005 CE engine (per the documentation) in the deployment project.

Any help would be greatly appreciated.

(I presume that you are deploying on a desktop.)

The recommended method is to install the runtime package (through click once or otherwise). No manual intervention is needed. The data provider (i.e. System.Data.SqlServerCe.dll) is put in GAC. It is easy to update the package too.

If you do not want to use the installer for some reason, then ensure that all SSC binaries are in the executable folder.

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 from SQL 2000 to SQL 2005

I will be moving my website from my local dev server to the live environment soon. I've been using SQL 2000 to develop, but the live DB is SQL 2005. My app uses exclusively stored procedures for all data access.

What suprises are in store for me when I migrate the site?!

Thanks, Jamie

If you don't have any DTS, scheduled tasks to worry about. Then the migration is very straight forward, personally, I have not encounter any problems. What I did is to script the entire DB's table def, indexes, sp, udf. Then run it once on 2005.

This article contains step-by-step process:http://www.aspfree.com/c/a/MS-SQL-Server/Moving-Data-from-SQL-Server-2000-to-SQL-Server-2005/

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

deployment error

A report runs well in Visual Studio environment. Once it is deployed to the local report server, got an #Error indication without an actual message. The report has an embedded code with a database connection in it. Any idea what the problem is?

Thank you very much!

Could be a security issue regarding the database connection. If i understand you correctly, you connect to a database in custom code? If you have trusted connection in your custom code, maybe it is not the same user that makes the database call when the report runs in ReportServer as in Visual Studio and you get an exception?|||

Thanks for your response. I thought it could be a security issue too. So I enabled trusted connection and tried using specific uid and pwd too. Neither of them worked.

|||What dp you get if you do a try/catch and return the exception text to a textbox in the report?

What does this custom code do? What does it do with the report? The reason i am asking is that there might be some other way to solve it.|||

The custom code retrieves and outputs another set of data based on the dynamic id outputted from the first set of data.

I'll see what text message I'll get if I use try/catch and let you know.

Thanks for your help.

|||I found out it has something to do with the Code Access Security in .NET. I did some research and found this article was very helpful: http://www.devx.com/codemag/Article/33656/1954?pf=true. Once I followed it step by step, the problem was resolved. Just wanted to share with the community, in case if there is anybody encountered the same problem as I did.

deployment error

A report runs well in Visual Studio environment. Once it is deployed to the local report server, got an #Error indication without an actual message. The report has an embedded code with a database connection in it. Any idea what the problem is?

Thank you very much!

Could be a security issue regarding the database connection. If i understand you correctly, you connect to a database in custom code? If you have trusted connection in your custom code, maybe it is not the same user that makes the database call when the report runs in ReportServer as in Visual Studio and you get an exception?|||

Thanks for your response. I thought it could be a security issue too. So I enabled trusted connection and tried using specific uid and pwd too. Neither of them worked.

|||What dp you get if you do a try/catch and return the exception text to a textbox in the report?

What does this custom code do? What does it do with the report? The reason i am asking is that there might be some other way to solve it.|||

The custom code retrieves and outputs another set of data based on the dynamic id outputted from the first set of data.

I'll see what text message I'll get if I use try/catch and let you know.

Thanks for your help.

|||I found out it has something to do with the Code Access Security in .NET. I did some research and found this article was very helpful: http://www.devx.com/codemag/Article/33656/1954?pf=true. Once I followed it step by step, the problem was resolved. Just wanted to share with the community, in case if there is anybody encountered the same problem as I did.sql

Deploying System DSN to Multiple PCs

Is there any way to deploy System DSNs to multiple PCs?
I'm in a windows xp client environment with sql server 2000 running on a
windows server 200 box.
Thanks for any help.
System DSNs are stored in the registry under
HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI. Try exporting the registry node
for the data source and run it on another computer to see if it works.
Roman
Roman Rehak, MCSD, MCDBA, MCSA
SQL Server Specialist
Competitive Computing
http://sqljunkies.com/WebLog/Roman
"Josh" <Josh@.discussions.microsoft.com> wrote in message
news:FA14A0DA-A2C4-4779-ADDC-49F79016EF6E@.microsoft.com...
> Is there any way to deploy System DSNs to multiple PCs?
> I'm in a windows xp client environment with sql server 2000 running on a
> windows server 200 box.
> Thanks for any help.
|||Thanks for replying but that didn't work. I was thinking maybe there might
be a way to create a vbscript to create the system dsns.
"Roman Rehak" wrote:

> System DSNs are stored in the registry under
> HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI. Try exporting the registry node
> for the data source and run it on another computer to see if it works.
> Roman
>
> Roman Rehak, MCSD, MCDBA, MCSA
> SQL Server Specialist
> Competitive Computing
> http://sqljunkies.com/WebLog/Roman
>
> "Josh" <Josh@.discussions.microsoft.com> wrote in message
> news:FA14A0DA-A2C4-4779-ADDC-49F79016EF6E@.microsoft.com...
>
>
|||These articles might help you get going with this:
How To Create and Remove a DSN in Visual Basic
http://support.microsoft.com/?id=171146
How To Programmatically Create a DSN for SQL Server with VB
http://support.microsoft.com/?id=184608
-Sue
On Sun, 27 Feb 2005 21:47:01 -0800, "Josh"
<Josh@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>Thanks for replying but that didn't work. I was thinking maybe there might
>be a way to create a vbscript to create the system dsns.
>
>"Roman Rehak" wrote:

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 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 SSIS package to production which has a connection to oracle databse

Hi There,

In SSIS package development environment, I was able to connect to an oracle database and pull data into my sql server database. I installed the client tools for oracle and I put an entry into the tnsnames.ora and I was able to connect.

But in production environment, if I deploy the package on sql server, I was wondering if I had to do the same job of downloading the oracle client tools onto my production machine --which creates a tnsnames.ora file to it default location and then edit it with tthe tns entry-- or is there a better way to do this--avoiding the download?

Can somebody plzz help me ?

Thanks.

You need to install the Oracle Client (9i) or (10) on the actual SQL Server box.

This is for the network libraries. There is a special build of the client for Windows 2003 Server if you go to Oracles site and have a look around

cheers Dave

|||

You do need to repeat the same steps like you've done in your development environment: install Oracle client and adjust tnsnames.ora file.

There are 2 more options:

1) There is another "lighter" option - Oracle Instant Client:

http://www.oracle.com/technology/tech/oci/instantclient//index.html

2) The Oracle Data Provider for .NET (ODP.NET) . It has Oracle client bundled with it.

http://www.oracle.com/technology/tech/windows/odpnet/index.html

Regards,
Yitzhak

|||

Hi Yitzhak,

If I intstall the lighter option, where do I adjust the tnsnames.ora file? I don't find the file after installation. Do I need to manually create it and put it in a specific location? Can you please reply back?

Thanks.

Sam.

|||

Also, which of the instant client packages should I download? There are 5 downloads for install client for 64bit.

Thanks.

Sam.

|||

Oracle has Instant Client FAQ page:

http://www.oracle.com/technology/tech/oci/instantclient/ic-faq.html#A5028

How do I ensure that my "tnsnames.ora" file is being used in Instant Client?
Always set the TNS_ADMIN environment variable or registry setting to the full path of the tnsnames.ora file. This practice will ensure that you are using the appropriate tnsnames.ora for your application when running with Instant Client.

Regards,
Yitzhak

|||

Because you are using MS SQL Server 2005 SSIS on Windows OS, just 2 options are applicable for you:

Windows Itanium 64-bit 10.2.0.2|||

HiYitzhak,

Can you please bare with me? I downloaded the windows x86 64 bit install client and this is what I did.

I unzipped the folder contents to c:install\instantclient

I created a tnsnames.ora file with the tns entry under 'C:\'.

I added the full path 'c:install\instantclient\' to the path environment variable

I also added a tns_admin environment variable giving it a value 'C:\tnsnames.ora'.

Now I test executing the package using dtexec and I still can't connect to the oracle database. It still gives me an error 'Client and networking components not installed. Am I missing smth?

Can you please help me?

Thanks.

|||

There is a command line tnsping.exe Oracle utility to check both client installation and tnsnames.ora settings.

You can try to launch it at the command prompt:

c:\>tnsping oracle-instance-name

Regards,
Yitzhak

deploy permissions

Hi,
I'm trying to deploy reports from the dev. environment and I'm getting the
error:
'The permissions granted to users 'server\user' are insufficient for
performing this operation.'
That is not the user that I am logged onto my development machine,
nor is it a user on the report server. Where can I find the source of
this error. The 'server\user' must be embedded somewhere.
TIA,
MarcDoes your RS server use Basic auth turned on? This could be the user you
are seeing. You might also want to check if you have anonymous access
turned on, if so then every user will seem like the same user.
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
"Marc Miller" <mm1284@.hotmail.com> wrote in message
news:e6wwTdkWFHA.3840@.tk2msftngp13.phx.gbl...
> Hi,
> I'm trying to deploy reports from the dev. environment and I'm getting the
> error:
> 'The permissions granted to users 'server\user' are insufficient for
> performing this operation.'
> That is not the user that I am logged onto my development machine,
> nor is it a user on the report server. Where can I find the source of
> this error. The 'server\user' must be embedded somewhere.
> TIA,
> Marc
>