Install RS - Separate DB from Web

I am trying to install reporting services on a web server, which will connect
to an existing instance of the RS Sql Server backend on another machine.
This backend server already has SP2 installed - so when I install RS on the
web server machine and try to point to the existing backend during
installation, it tells me that it is not compatible.
What would be the correct steps to take in order to install on a web server
and connect to an existing RS backend DB? Any relevant articles will help...
Enjoy!
mikeFirst, are you implementing a web farm?
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Michael R" <MichaelR@.discussions.microsoft.com> wrote in message
news:9F638932-02F0-48DF-8EF9-A54EF42AF0FA@.microsoft.com...
>I am trying to install reporting services on a web server, which will
>connect
> to an existing instance of the RS Sql Server backend on another machine.
> This backend server already has SP2 installed - so when I install RS on
> the
> web server machine and try to point to the existing backend during
> installation, it tells me that it is not compatible.
> What would be the correct steps to take in order to install on a web
> server
> and connect to an existing RS backend DB? Any relevant articles will
> help...
> Enjoy!
> mike|||Not in the sense that I will have multiple ReportServer databases. I will
have a one to one relationship: 1 web server and 1 server with the
ReportServer database.
It was recommended that I do this by the server admins, in order to take the
load off of IIS.
"Bruce L-C [MVP]" wrote:
> First, are you implementing a web farm?
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Michael R" <MichaelR@.discussions.microsoft.com> wrote in message
> news:9F638932-02F0-48DF-8EF9-A54EF42AF0FA@.microsoft.com...
> >I am trying to install reporting services on a web server, which will
> >connect
> > to an existing instance of the RS Sql Server backend on another machine.
> > This backend server already has SP2 installed - so when I install RS on
> > the
> > web server machine and try to point to the existing backend during
> > installation, it tells me that it is not compatible.
> >
> > What would be the correct steps to take in order to install on a web
> > server
> > and connect to an existing RS backend DB? Any relevant articles will
> > help...
> >
> > Enjoy!
> >
> > mike
>
>|||I would try this:
1) install SQL RS on the web server, and during the install, create new
SQL RS database(s) for it to point to / use (doesn't matter where you
put the DB, you'll end up dropping them soon). At the end of the
install, you'll have a new SQL RS web app, pointing to a new SQL RS db.
2) Apply SP1 to the SQL RS instance (web & new database).
3) Apply SP2 to the SQL RS instance (web & new database).
4) Now that you're web app is up to SP2, you can point it to your
original database using the 'rsconfig' command line utility (see SQL RS
Books Online for details of usage & syntax). After using 'rsconfig' to
point your app to the original database, you'll need to run the
'rskeymgmt' command line utility to initialize / activate your Report
Server for use with the original database (allows it to read the
original database) -- see Books Online for details of syntax and usage.
5) Drop the new SQL RS databases that were created in Step #1, since
you're not going to use them, now that your web app is pointing to the
'original' SP2 database.

Install MSDE on XP Home Ed. Unable connect DB from other PC

Hi,
I tried to Install MSDE (SQL Server free ed.) on XP Home Ed. It's running
but from other computer I could not connect to that database using sa
account. Unlike when installed on XP Professional which MSDE can perform
almost like SQLServer. Does it because XP Home Ed.?
Thanks,
Martin
hi Martin,
prof_martin wrote:
> Hi,
> I tried to Install MSDE (SQL Server free ed.) on XP Home Ed. It's
> running but from other computer I could not connect to that database
> using sa account. Unlike when installed on XP Professional which MSDE
> can perform almost like SQLServer. Does it because XP Home Ed.?
>
MSDE installs by default disabling network protocols for security reasons...
you can bypass this setting at install time, providing the
DISABLENETWORKPROTOCOLS=0
parameter to the setup.exe boostrap installer and/or later, at "run time",
running the Server Network Utility (svrnetcn.exe) and enabling the
desired/required protocol(s)...
additionally, WinXP sp2 installs and enables by default the Windows
Firewall, and you have handle and manage to allow incoming remote
connections, as reported in http://support.microsoft.com/kb/841249/en-us
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Ahaa Andrea,
So you are the one the author DBAMgr2K, I'm using it ver 0.7.0. Quite useful
some more it's free. Only thing about your powerful software when database
structure need to be amended some field for datatype, its prompt something so
I was not able to do it. Anyway nearly perfect for free level.
Just confirmed with you, we got 5 PC all XP Home, PC1 I installed
MSDE2K+DBAMgr2K, the rest of PC contain application which consume Data from
PC1. Is this by right should works? And Is this smart enough for low cost
infrastructure for SME?
We have plan to upgrade PC1 using XP Professional, if necessary.
I really appreciate your answer.
Thanks you,
Martin A.N. (from Singapore)
"Andrea Montanari" wrote:

> hi Martin,
> prof_martin wrote:
> MSDE installs by default disabling network protocols for security reasons...
> you can bypass this setting at install time, providing the
> DISABLENETWORKPROTOCOLS=0
> parameter to the setup.exe boostrap installer and/or later, at "run time",
> running the Server Network Utility (svrnetcn.exe) and enabling the
> desired/required protocol(s)...
> additionally, WinXP sp2 installs and enables by default the Windows
> Firewall, and you have handle and manage to allow incoming remote
> connections, as reported in http://support.microsoft.com/kb/841249/en-us
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
>
|||prof_martin wrote:
> Ahaa Andrea,
> So you are the one the author DBAMgr2K, I'm using it ver 0.7.0. Quite
> useful some more it's free. Only thing about your powerful software
> when database structure need to be amended some field for datatype,
> its prompt something so I was not able to do it. Anyway nearly
> perfect for free level.
thank you for your interest in this prj of mine, and please feel free to
(privately) contact me for any question or concern, as long as for
suggestions and feedback...

> Just confirmed with you, we got 5 PC all XP Home, PC1 I installed
> MSDE2K+DBAMgr2K, the rest of PC contain application which consume
> Data from PC1. Is this by right should works? And Is this smart
> enough for low cost infrastructure for SME?
> We have plan to upgrade PC1 using XP Professional, if necessary.
> I really appreciate your answer.
it is ok on the client level... but I'd go for XP pro on the server for the
advanced net facilities it provides on XP home...
my $0.02
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||hi,
i installed msde in windows 2000 prof. its installed succes fully but i dont
know how to run it.becase there is no indication for installation
completion.a folder which i gave in seup file was created and some folders
like binn,data, were created . but there is no tool to run the msde.
do i have to down load any thing more.
i down loaded msde 2000 release A.
thanks
vinoth
|||hi,
vinoth wrote:
> hi,
> i installed msde in windows 2000 prof. its installed succes fully but
> i dont know how to run it.becase there is no indication for
> installation completion.a folder which i gave in seup file was
> created and some folders like binn,data, were created . but there is
> no tool to run the msde.
> do i have to down load any thing more.
> i down loaded msde 2000 release A.
> thanks
> vinoth
you are correct, the installer terminates it's work without any prompt.. if
you provided the
/L*v "c:\MsdeLog.txt"
additional parameter to the setup.exe boostrap installer you can inspect it
at it's end to verify MSDE has been succesfully installed...
you won't see anything in the tray area (the SQL Server Service Manager
icon) i f you do not restart your system, as all this requires a reboot to
register SQL Server services..
but you can connect to it using the only (command line) tool MSDE is
provided with, oSql.exe as reported in
http://support.microsoft.com/default...;EN-US;q325003
again... MSDE is not provided with graphical tools, but you can have a look
at a free prj of mine at the link followind my sign, which provides a user
interface similar to Enterprise Manager... further tools, bot commercial and
free are listed in http://www.microsoft.com/sql/msde/partners and/or
http://www.aspfaq.com/show.asp?id=2442
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply

Install MSDE But Not Connect from Other machine

Hi all
i install microsoft MSDE on one machine it work fine on that machine but
when i am trying to connect from other machine by giving osql -U
"Username" -S "ServerName" and password but it give me error message Sql
server does not exist"
and when i try to connect from Sql server Query Analyzer it also give me
error message
please help me
thanks in advanced
Regards
khurram
hi,
Syed Khurram Alam wrote:
> Hi all
> i install microsoft MSDE on one machine it work fine on that machine
> but when i am trying to connect from other machine by giving osql -U
> "Username" -S "ServerName" and password but it give me error message
> Sql server does not exist"
> and when i try to connect from Sql server Query Analyzer it also give
> me error message
MSDE installs by default disabling network protocols to help users maintain
a secure instance, and thus allowing only local connections...
you can override that feature at install time providing the
DISABLENETWORKPROTOCOLS=0
parameter to the setup.exe boostrap installer and later, running the Server
Network Utility (svrnetcn.exe) and enabling the desired network
protocol(s)...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply

Install failure: "Error 29550. Cannot connect to the SQL server instance

I'm trying to install the Dev version of Reporting Services (RS) on one
box and have it use an Sql Server 2000 (w/SP3) instance on another box.
Both the RS and SqlServer boxes are Windows 2000 Servers. Neither are
part of a "windows domain"--neither will they ever be. We only connect
to SqlServer via a user/pwd pair. Additionally, there are 2 instances of
SqlServer running on the box and both of them listen on custom ports. (I
have confirmed that I can successfully connect to the desired SqlServer
instance from the RS box.)
The error I got was the "Login failed for user '(null)'. Reason: Not
associated with a trusted SQL Server connection.". The installer
attempts a domain login when I explicitly told it *not* to. I found no
way to get the installer to successfully connect to the database. The
solutions I've found on the web/Usenet have not worked either.
Since I couldn't get it to install through the GUI, I switched to using
an .ini file. Of course, it's not working either. The (500KB!) log file
the installer produces has only one useful line in it: "Error 29550.
Cannot connect to the SQL server instance ." That meant that the problem
was the RSDATABASESERVER variable. The instructions tell me to specify
an "SQL Server 2000 instance in format MACHINE\INSTANCENAME". I played
around with that value a lot; I wondered how it could figure out what
port to connect to for one thing. While doing so, I tried sniffing the
network to see if that would help me at all--it just got me more
frustrated: no attempt is made to contact the server! Ever.
First off: WHY choose this uncommon, inadequate format for specifying a
server? Why not just use an alias from "cliconfg" like everything else?
Second: why doesn't the installer even *try* to login to the server? If
there's a reason it can't access the network, wouldn't you think that
500KB log file is a good place to mention it?
What do I do? (Hint: don't suggest making either box part of a windows
domain)
GrangerTo have setup use sql auth during setup you must pass in command line
parameters. The params are RSSETUPACCOUNT and RSSETUPPASSWORD
so run this command
setup.exe RSSETUPACCOUNT=foo RSSETUPPASSWORD=bar
This will allow you to use the setup GUI still but all communication with
the backend server will use sql auth. Note that the setup user needs to be
a dbo. You can safely use the sa account as it is only used during setup.
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
"Granger Godbold" <granger.godbold@.FILLER.prometric.com> wrote in message
news:e4VCZaIEFHA.3888@.TK2MSFTNGP10.phx.gbl...
> I'm trying to install the Dev version of Reporting Services (RS) on one
> box and have it use an Sql Server 2000 (w/SP3) instance on another box.
> Both the RS and SqlServer boxes are Windows 2000 Servers. Neither are part
> of a "windows domain"--neither will they ever be. We only connect to
> SqlServer via a user/pwd pair. Additionally, there are 2 instances of
> SqlServer running on the box and both of them listen on custom ports. (I
> have confirmed that I can successfully connect to the desired SqlServer
> instance from the RS box.)
> The error I got was the "Login failed for user '(null)'. Reason: Not
> associated with a trusted SQL Server connection.". The installer attempts
> a domain login when I explicitly told it *not* to. I found no way to get
> the installer to successfully connect to the database. The solutions I've
> found on the web/Usenet have not worked either.
> Since I couldn't get it to install through the GUI, I switched to using an
> .ini file. Of course, it's not working either. The (500KB!) log file the
> installer produces has only one useful line in it: "Error 29550. Cannot
> connect to the SQL server instance ." That meant that the problem was the
> RSDATABASESERVER variable. The instructions tell me to specify an "SQL
> Server 2000 instance in format MACHINE\INSTANCENAME". I played around with
> that value a lot; I wondered how it could figure out what port to connect
> to for one thing. While doing so, I tried sniffing the network to see if
> that would help me at all--it just got me more frustrated: no attempt is
> made to contact the server! Ever.
> First off: WHY choose this uncommon, inadequate format for specifying a
> server? Why not just use an alias from "cliconfg" like everything else?
> Second: why doesn't the installer even *try* to login to the server? If
> there's a reason it can't access the network, wouldn't you think that
> 500KB log file is a good place to mention it?
> What do I do? (Hint: don't suggest making either box part of a windows
> domain)
> Granger|||Thanks for trying, but no, that doesn't work; I was already doing that. I was
trying to use the "sa" account from the beginning because the instructions say
the "setup" account is only used during setup.
My problem is still that the installer doesn't even *try* to connect to the
database server. Once I can get around that, my problem will be that it will
want to use Windows Authentication because the connection information only
consists of "server\instance"; that's why it has to login: to figure out the
port the instance lives at.
If anyone knows the person responsible for the decision to use this connection
method, please smack them upside the head for me.
Other ideas?
Granger
Daniel Reib [MSFT] wrote:
> To have setup use sql auth during setup you must pass in command line
> parameters. The params are RSSETUPACCOUNT and RSSETUPPASSWORD
> so run this command
> setup.exe RSSETUPACCOUNT=foo RSSETUPPASSWORD=bar
> This will allow you to use the setup GUI still but all communication with
> the backend server will use sql auth. Note that the setup user needs to be
> a dbo. You can safely use the sa account as it is only used during setup.
>|||Well first of all, if you want it to connect, what does your client
configuration say?
I take it that on the general tab you have TCP/IP listed at the top - click
the properties tab and is the port set correctly for your particular
instance?
I am running reporting services stand-alone - with SQL Server NOT IN A
DOMAIN - and it runs just fine.
You can also create an ALIAS name to the server instance in the SQL Server
Client Network utility.
Finally, just to be sure we are "connecting the dots" here - fire up the SQL
Server Network utility and verify that the TCP/IP properties are also
listening on the correct port. (I bet they are since you are using the
system successfully)
Last but not least, even if you are using SQL Server authentication, you
should be able to use windows authentication only when doing the setup -
since as you said you have full control over the dev box - then you have
local admin rights - therefore you should be able to logon unless you have
modifed the BUILTIN\Administrators security for that machine. (I assume that
this is not the case).
Please let me know if you are still having an issue, I'll be happy to help
you out.
Of course, this may come as a dumb question, but I assume nothing: Did you
install SP3a for SQL Server? (I assume yes), did you install the SQL Server
hotfix 859 ?
=-Chris
"Granger Godbold" <granger.godbold@.invalid.prometric.com> wrote in message
news:ucLN4gZEFHA.3256@.tk2msftngp13.phx.gbl...
> Thanks for trying, but no, that doesn't work; I was already doing that. I
> was trying to use the "sa" account from the beginning because the
> instructions say the "setup" account is only used during setup.
> My problem is still that the installer doesn't even *try* to connect to
> the database server. Once I can get around that, my problem will be that
> it will want to use Windows Authentication because the connection
> information only consists of "server\instance"; that's why it has to
> login: to figure out the port the instance lives at.
> If anyone knows the person responsible for the decision to use this
> connection method, please smack them upside the head for me.
> Other ideas?
> Granger
>
> Daniel Reib [MSFT] wrote:
>> To have setup use sql auth during setup you must pass in command line
>> parameters. The params are RSSETUPACCOUNT and RSSETUPPASSWORD
>> so run this command
>> setup.exe RSSETUPACCOUNT=foo RSSETUPPASSWORD=bar
>> This will allow you to use the setup GUI still but all communication with
>> the backend server will use sql auth. Note that the setup user needs to
>> be a dbo. You can safely use the sa account as it is only used during
>> setup.|||Thanks Chris.
The connectivity is all OK. It appears I'm just going to have to go
sync the administrators on each of the boxes during the install.
However, that won't be for a while; I just gave up and installed
everything on my own box for now. When I've had a chance to play with it
for a while, I'll do another install attempt in a more "proper" DEV
environment.
As far as the updates on the database go, my DBA says he's only done
security bulletin stuff. I looked it over and it seems the DEV box has
SP3 not SP3a (I checked the Ssnetlib.dll; we have 2000.80.760 not
2000.80.766
(http://support.microsoft.com/default.aspx?scid=kb;en-us;819334)). Also,
since Enterprise Manager reports 8.00.760, I gather he's not done any
hotfixes. This KnowledgeBase article
(http://support.microsoft.com/default.aspx?scid=kb;en-us;888007) implies
we should be at least at .977. I'll go tease him for being a slacker. ;)
I wouldn't guess the hotfixes would have anything to do with my
problem, however, since my local database only has SP3 installed on it
and ReportingServices installed fine.
Again, thanks Chris =)
Granger
Christopher Conner wrote:
<snip>
> Last but not least, even if you are using SQL Server authentication, you
> should be able to use windows authentication only when doing the setup -
> since as you said you have full control over the dev box - then you have
> local admin rights - therefore you should be able to logon unless you have
> modifed the BUILTIN\Administrators security for that machine. (I assume that
> this is not the case).
> Please let me know if you are still having an issue, I'll be happy to help
> you out.
> Of course, this may come as a dumb question, but I assume nothing: Did you
> install SP3a for SQL Server? (I assume yes), did you install the SQL Server
> hotfix 859 ?
> =-Chris
>sql