Installing Web Server and Database Server not in the same DOMAIN

Hello All,
I'm installing the RS using the "Standard Deployment Model" suggested
by BOL, which uses one Web Server as the Report Server and the Report
Manager and another as the Report Server Database.
According to BOL:
"The SQL Server instance hosting the report server database must be in
the same domain as the report server or in a trusted domain with the
report server."
Although, in my case, these two machines are not in the same domain,
neither could be. Is there any workaround for it'
It's quite urgent because while I was testing RS in DEV, wich has just
one machine, everything was fine, but now that I'm deploying RS to
Production, I realized that I don't have both Prd machines on the same
domain.
I'd appreciate any help.
Thanks in advance,
Vinicius BellinoThe workaround is laid out right there -- create a domain trust.
--
Cheers,
'(' Jeff A. Stucker
\
Business Intelligence
www.criadvantage.com
---
"Vinicius Bellino" <vbellino@.uol.com.br> wrote in message
news:93d12908.0503021209.165adea4@.posting.google.com...
> Hello All,
> I'm installing the RS using the "Standard Deployment Model" suggested
> by BOL, which uses one Web Server as the Report Server and the Report
> Manager and another as the Report Server Database.
> According to BOL:
> "The SQL Server instance hosting the report server database must be in
> the same domain as the report server or in a trusted domain with the
> report server."
> Although, in my case, these two machines are not in the same domain,
> neither could be. Is there any workaround for it'
> It's quite urgent because while I was testing RS in DEV, wich has just
> one machine, everything was fine, but now that I'm deploying RS to
> Production, I realized that I don't have both Prd machines on the same
> domain.
> I'd appreciate any help.
> Thanks in advance,
> Vinicius Bellino|||Do you realize that you have to have a SQL Server license for the web server
and then one for SQL Server. My feeling is to have SQL Server on the web
server even if it is just as the object store (i.e. the data being reported
off of is somewhere else). SQL Server is very good at managing it's
resources and I have had no problem doing this.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Vinicius Bellino" <vbellino@.uol.com.br> wrote in message
news:93d12908.0503021209.165adea4@.posting.google.com...
> Hello All,
> I'm installing the RS using the "Standard Deployment Model" suggested
> by BOL, which uses one Web Server as the Report Server and the Report
> Manager and another as the Report Server Database.
> According to BOL:
> "The SQL Server instance hosting the report server database must be in
> the same domain as the report server or in a trusted domain with the
> report server."
> Although, in my case, these two machines are not in the same domain,
> neither could be. Is there any workaround for it'
> It's quite urgent because while I was testing RS in DEV, wich has just
> one machine, everything was fine, but now that I'm deploying RS to
> Production, I realized that I don't have both Prd machines on the same
> domain.
> I'd appreciate any help.
> Thanks in advance,
> Vinicius Bellino|||"Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message news:<OjYvW22HFHA.1476@.TK2MSFTNGP09.phx.gbl>...
> Do you realize that you have to have a SQL Server license for the web server
> and then one for SQL Server. My feeling is to have SQL Server on the web
> server even if it is just as the object store (i.e. the data being reported
> off of is somewhere else). SQL Server is very good at managing it's
> resources and I have had no problem doing this.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Vinicius Bellino" <vbellino@.uol.com.br> wrote in message
> news:93d12908.0503021209.165adea4@.posting.google.com...
> > Hello All,
> >
> > I'm installing the RS using the "Standard Deployment Model" suggested
> > by BOL, which uses one Web Server as the Report Server and the Report
> > Manager and another as the Report Server Database.
> >
> > According to BOL:
> >
> > "The SQL Server instance hosting the report server database must be in
> > the same domain as the report server or in a trusted domain with the
> > report server."
> >
> > Although, in my case, these two machines are not in the same domain,
> > neither could be. Is there any workaround for it'
> >
> > It's quite urgent because while I was testing RS in DEV, wich has just
> > one machine, everything was fine, but now that I'm deploying RS to
> > Production, I realized that I don't have both Prd machines on the same
> > domain.
> >
> > I'd appreciate any help.
> >
> > Thanks in advance,
> >
> > Vinicius Bellino
Bruce,
I've thought about installing SQL Server in my Web Server as well, but
the only point was the supposed new SQL Server's license. Now I have
no more reasons not to do this. So, thank you!
Regards,
Vinicius Bellinosql

installing SQL Express via commandline

So, I read this thread: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=416220&SiteID=1, which suggested that I could call SQLEXPR32.EXE (the SP2 download) with the relevant commandline args in exactly the same way I could call setup.exe. Namely, if I were to call:

Code Snippet

setup.exe /qb /settings "c:/setup.ini"

then I should be able to use

Code Snippet

SQLEXPR32.exe /qb /settings "c:/setup.ini"

where my setup.ini contains

Code Snippet

[Options]
ADDLOCAL=SQL_Data_Files,SQL_Replication,Connectivity
INSTANCENAME=AuctionI
SAPWD=auctioni_000
SECURITYMODE=SQL

However, this doesn't seem to be working at all - the commandline params to SQLEXPR32.EXE are completely ignored, and it runs as if they were not specified.

Would be great to get some help on this. I'm equally happy with the set of commands I need to call in order to extract SQLEXPR32 and then run setup, but SQLEXPR32 seems to extract to a random GUID dir, and automatically start setup, neither of which is condusive to automating it.

Thanks,

Dan

hi Dan,

you did not specify the /settings parameter, which identifies the template ini file to be consumed..

I just tested an installation as following:

c:\start /wait c:\share\sqlexpr.exe /qb /settings c:\share\sqlexpress.ini

[file sqlexpress.ini]
[OPTIONS]
ADDLOCAL=SQL_Engine
INSTANCENAME=MyInstance
SAPWD=auctioni_000
SECURITYMODE=SQL
[/file sqlexpress.ini]

and worked as expected..

regards

|||

Hi Andrea,

Isn't that exactly what I have in my code snippet? I have /settings "c:\settings.ini" right there... Also, the key here is that I want this to work with the SP2 download of SQLExpress, specifically, this file: http://go.microsoft.com/fwlink/?LinkId=65212

(not the files that are a result of extracting that file)

Probably I am missing something simple in your reply.

Thanks much,

Dan

|||-- bump --|||bump again|||

hi Dan,

Dan560472 wrote:

Hi Andrea,

Isn't that exactly what I have in my code snippet? I have /settings "c:\settings.ini" right there... Also, the key here is that I want this to work with the SP2 download of SQLExpress, specifically, this file: http://go.microsoft.com/fwlink/?LinkId=65212

(not the files that are a result of extracting that file)

Probably I am missing something simple in your reply.

Thanks much,

Dan

sorry, I've misread your post, but my test actually worked as expected... so the following question comes to mind.. is the setting file available and present in the target file system in order to be consumed by the setup?

regards

|||

Dan-

I am working with this exact process right now for an installation project in my office. In order to use the command line parameters you first have to extract the SQLEXPR32.EXE file by typing something such as c:\(dirname)\SQLEXPR32.EXE /X

Setup will then prompt you for a place to extract the files and you can then use the SETUP.EXE command from that folder with the /SETTINGS option. Hope this helps.

Braden

installing SQL Express via commandline

So, I read this thread: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=416220&SiteID=1, which suggested that I could call SQLEXPR32.EXE (the SP2 download) with the relevant commandline args in exactly the same way I could call setup.exe. Namely, if I were to call:

Code Snippet

setup.exe /qb /settings "c:/setup.ini"

then I should be able to use

Code Snippet

SQLEXPR32.exe /qb /settings "c:/setup.ini"

where my setup.ini contains

Code Snippet

[Options]
ADDLOCAL=SQL_Data_Files,SQL_Replication,Connectivity
INSTANCENAME=AuctionI
SAPWD=auctioni_000
SECURITYMODE=SQL

However, this doesn't seem to be working at all - the commandline params to SQLEXPR32.EXE are completely ignored, and it runs as if they were not specified.

Would be great to get some help on this. I'm equally happy with the set of commands I need to call in order to extract SQLEXPR32 and then run setup, but SQLEXPR32 seems to extract to a random GUID dir, and automatically start setup, neither of which is condusive to automating it.

Thanks,

Dan

hi Dan,

you did not specify the /settings parameter, which identifies the template ini file to be consumed..

I just tested an installation as following:

c:\start /wait c:\share\sqlexpr.exe /qb /settings c:\share\sqlexpress.ini

[file sqlexpress.ini]
[OPTIONS]
ADDLOCAL=SQL_Engine
INSTANCENAME=MyInstance
SAPWD=auctioni_000
SECURITYMODE=SQL
[/file sqlexpress.ini]

and worked as expected..

regards

|||

Hi Andrea,

Isn't that exactly what I have in my code snippet? I have /settings "c:\settings.ini" right there... Also, the key here is that I want this to work with the SP2 download of SQLExpress, specifically, this file: http://go.microsoft.com/fwlink/?LinkId=65212

(not the files that are a result of extracting that file)

Probably I am missing something simple in your reply.

Thanks much,

Dan

|||-- bump --|||bump again|||

hi Dan,

Dan560472 wrote:

Hi Andrea,

Isn't that exactly what I have in my code snippet? I have /settings "c:\settings.ini" right there... Also, the key here is that I want this to work with the SP2 download of SQLExpress, specifically, this file: http://go.microsoft.com/fwlink/?LinkId=65212

(not the files that are a result of extracting that file)

Probably I am missing something simple in your reply.

Thanks much,

Dan

sorry, I've misread your post, but my test actually worked as expected... so the following question comes to mind.. is the setting file available and present in the target file system in order to be consumed by the setup?

regards

|||

Dan-

I am working with this exact process right now for an installation project in my office. In order to use the command line parameters you first have to extract the SQLEXPR32.EXE file by typing something such as c:\(dirname)\SQLEXPR32.EXE /X

Setup will then prompt you for a place to extract the files and you can then use the SETUP.EXE command from that folder with the /SETTINGS option. Hope this helps.

Braden

installing SQL Express via commandline

So, I read this thread: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=416220&SiteID=1, which suggested that I could call SQLEXPR32.EXE (the SP2 download) with the relevant commandline args in exactly the same way I could call setup.exe. Namely, if I were to call:

Code Snippet

setup.exe /qb /settings "c:/setup.ini"

then I should be able to use

Code Snippet

SQLEXPR32.exe /qb /settings "c:/setup.ini"

where my setup.ini contains

Code Snippet

[Options]
ADDLOCAL=SQL_Data_Files,SQL_Replication,Connectivity
INSTANCENAME=AuctionI
SAPWD=auctioni_000
SECURITYMODE=SQL

However, this doesn't seem to be working at all - the commandline params to SQLEXPR32.EXE are completely ignored, and it runs as if they were not specified.

Would be great to get some help on this. I'm equally happy with the set of commands I need to call in order to extract SQLEXPR32 and then run setup, but SQLEXPR32 seems to extract to a random GUID dir, and automatically start setup, neither of which is condusive to automating it.

Thanks,

Dan

hi Dan,

you did not specify the /settings parameter, which identifies the template ini file to be consumed..

I just tested an installation as following:

c:\start /wait c:\share\sqlexpr.exe /qb /settings c:\share\sqlexpress.ini

[file sqlexpress.ini]
[OPTIONS]
ADDLOCAL=SQL_Engine
INSTANCENAME=MyInstance
SAPWD=auctioni_000
SECURITYMODE=SQL
[/file sqlexpress.ini]

and worked as expected..

regards

|||

Hi Andrea,

Isn't that exactly what I have in my code snippet? I have /settings "c:\settings.ini" right there... Also, the key here is that I want this to work with the SP2 download of SQLExpress, specifically, this file: http://go.microsoft.com/fwlink/?LinkId=65212

(not the files that are a result of extracting that file)

Probably I am missing something simple in your reply.

Thanks much,

Dan

|||-- bump --|||bump again|||

hi Dan,

Dan560472 wrote:

Hi Andrea,

Isn't that exactly what I have in my code snippet? I have /settings "c:\settings.ini" right there... Also, the key here is that I want this to work with the SP2 download of SQLExpress, specifically, this file: http://go.microsoft.com/fwlink/?LinkId=65212

(not the files that are a result of extracting that file)

Probably I am missing something simple in your reply.

Thanks much,

Dan

sorry, I've misread your post, but my test actually worked as expected... so the following question comes to mind.. is the setting file available and present in the target file system in order to be consumed by the setup?

regards

|||

Dan-

I am working with this exact process right now for an installation project in my office. In order to use the command line parameters you first have to extract the SQLEXPR32.EXE file by typing something such as c:\(dirname)\SQLEXPR32.EXE /X

Setup will then prompt you for a place to extract the files and you can then use the SETUP.EXE command from that folder with the /SETTINGS option. Hope this helps.

Braden

installing SQL Express via commandline

So, I read this thread: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=416220&SiteID=1, which suggested that I could call SQLEXPR32.EXE (the SP2 download) with the relevant commandline args in exactly the same way I could call setup.exe. Namely, if I were to call:

Code Snippet

setup.exe /qb /settings "c:/setup.ini"

then I should be able to use

Code Snippet

SQLEXPR32.exe /qb /settings "c:/setup.ini"

where my setup.ini contains

Code Snippet

[Options]
ADDLOCAL=SQL_Data_Files,SQL_Replication,Connectivity
INSTANCENAME=AuctionI
SAPWD=auctioni_000
SECURITYMODE=SQL

However, this doesn't seem to be working at all - the commandline params to SQLEXPR32.EXE are completely ignored, and it runs as if they were not specified.

Would be great to get some help on this. I'm equally happy with the set of commands I need to call in order to extract SQLEXPR32 and then run setup, but SQLEXPR32 seems to extract to a random GUID dir, and automatically start setup, neither of which is condusive to automating it.

Thanks,

Dan

hi Dan,

you did not specify the /settings parameter, which identifies the template ini file to be consumed..

I just tested an installation as following:

c:\start /wait c:\share\sqlexpr.exe /qb /settings c:\share\sqlexpress.ini

[file sqlexpress.ini]
[OPTIONS]
ADDLOCAL=SQL_Engine
INSTANCENAME=MyInstance
SAPWD=auctioni_000
SECURITYMODE=SQL
[/file sqlexpress.ini]

and worked as expected..

regards

|||

Hi Andrea,

Isn't that exactly what I have in my code snippet? I have /settings "c:\settings.ini" right there... Also, the key here is that I want this to work with the SP2 download of SQLExpress, specifically, this file: http://go.microsoft.com/fwlink/?LinkId=65212

(not the files that are a result of extracting that file)

Probably I am missing something simple in your reply.

Thanks much,

Dan

|||-- bump --|||bump again|||

hi Dan,

Dan560472 wrote:

Hi Andrea,

Isn't that exactly what I have in my code snippet? I have /settings "c:\settings.ini" right there... Also, the key here is that I want this to work with the SP2 download of SQLExpress, specifically, this file: http://go.microsoft.com/fwlink/?LinkId=65212

(not the files that are a result of extracting that file)

Probably I am missing something simple in your reply.

Thanks much,

Dan

sorry, I've misread your post, but my test actually worked as expected... so the following question comes to mind.. is the setting file available and present in the target file system in order to be consumed by the setup?

regards

|||

Dan-

I am working with this exact process right now for an installation project in my office. In order to use the command line parameters you first have to extract the SQLEXPR32.EXE file by typing something such as c:\(dirname)\SQLEXPR32.EXE /X

Setup will then prompt you for a place to extract the files and you can then use the SETUP.EXE command from that folder with the /SETTINGS option. Hope this helps.

Braden