What is the function of the RSExecRole? Should I be granting this to users
in a development environment who need to create reports?
Thanks,
SteveHi,
"RSExecRole" permission is given to ReportServer database. This can be used
for accessing master, msdb and reportserver tempdb. But when you configure
using report configuration tool, these permissions are granted automatically.
So dont have to give it again.
Regards
Amarnath
"Steven" wrote:
> What is the function of the RSExecRole? Should I be granting this to users
> in a development environment who need to create reports?
> Thanks,
> Steve
>
>
Showing posts with label environment. Show all posts
Showing posts with label environment. Show all posts
Wednesday, March 28, 2012
RSExecRole
RServer in 3 tier environment
Can anybody shed some light on this for me?
I have to deploy Reporting Services in what I think is a fairly
typical 3-tier Internet environment.
I have the following
Firewall - 443 only
IIS Server (x2)
Firewall - 443 only
App Server (IIS)(x2)
Firewall - 1433 only
SQL Server
Question. How do I deply Reporting Services in this when the IIS
server can't talk directly to the SQL Server?
Is there some form of proxy I can use to pass through requests, via
the App Servers?
Any ideas appreciated
CliffRS is a webservice
so you can install it on your App server
and you have to create your own front end application for your IIS Server
which talk to RS
"CliffH" <Cliff_Harker@.hotmail.com> a écrit dans le message de news:
c13c8375.0409131514.6969f970@.posting.google.com...
> Can anybody shed some light on this for me?
> I have to deploy Reporting Services in what I think is a fairly
> typical 3-tier Internet environment.
> I have the following
> Firewall - 443 only
> IIS Server (x2)
> Firewall - 443 only
> App Server (IIS)(x2)
> Firewall - 1433 only
> SQL Server
> Question. How do I deply Reporting Services in this when the IIS
> server can't talk directly to the SQL Server?
> Is there some form of proxy I can use to pass through requests, via
> the App Servers?
> Any ideas appreciated
> Cliff|||Cliff
The best solution for this would be to install Reporting Services (IIS) on
your Application Server, this will be able to communicate with your SQL
Server and so deployment would be a simple task using the RS command line
util or ReportingServices() .NET class.
To access the application server ReportingServices from the first (UI?) IIS
server you'll need to create a proxy class to the Application Server
Reporting Services using WSDL. You will be able to reference the proxy class
using code in the UI layer.
Hope this helps
"CliffH" wrote:
> Can anybody shed some light on this for me?
> I have to deploy Reporting Services in what I think is a fairly
> typical 3-tier Internet environment.
> I have the following
> Firewall - 443 only
> IIS Server (x2)
> Firewall - 443 only
> App Server (IIS)(x2)
> Firewall - 1433 only
> SQL Server
> Question. How do I deply Reporting Services in this when the IIS
> server can't talk directly to the SQL Server?
> Is there some form of proxy I can use to pass through requests, via
> the App Servers?
> Any ideas appreciated
> Cliff
>|||Thanks for the replies, I'll get our guys to have a look at creating
this "proxy" on the UI IIS server.
Given this is a fairly typical deployment setup I'm surprised there
isn't something in the package itself to facilitate this
Cliff
"Buzz" <Buzz@.discussions.microsoft.com> wrote in message news:<1BE284C9-C5CB-47E0-AAF3-B07021D3CB79@.microsoft.com>...
> Cliff
> The best solution for this would be to install Reporting Services (IIS) on
> your Application Server, this will be able to communicate with your SQL
> Server and so deployment would be a simple task using the RS command line
> util or ReportingServices() .NET class.
> To access the application server ReportingServices from the first (UI?) IIS
> server you'll need to create a proxy class to the Application Server
> Reporting Services using WSDL. You will be able to reference the proxy class
> using code in the UI layer.
> Hope this helps
>
> "CliffH" wrote:
> > Can anybody shed some light on this for me?
> >
> > I have to deploy Reporting Services in what I think is a fairly
> > typical 3-tier Internet environment.
> >
> > I have the following
> >
> > Firewall - 443 only
> > IIS Server (x2)
> > Firewall - 443 only
> > App Server (IIS)(x2)
> > Firewall - 1433 only
> > SQL Server
> >
> > Question. How do I deply Reporting Services in this when the IIS
> > server can't talk directly to the SQL Server?
> >
> > Is there some form of proxy I can use to pass through requests, via
> > the App Servers?
> >
> > Any ideas appreciated
> >
> > Cliff
> >
I have to deploy Reporting Services in what I think is a fairly
typical 3-tier Internet environment.
I have the following
Firewall - 443 only
IIS Server (x2)
Firewall - 443 only
App Server (IIS)(x2)
Firewall - 1433 only
SQL Server
Question. How do I deply Reporting Services in this when the IIS
server can't talk directly to the SQL Server?
Is there some form of proxy I can use to pass through requests, via
the App Servers?
Any ideas appreciated
CliffRS is a webservice
so you can install it on your App server
and you have to create your own front end application for your IIS Server
which talk to RS
"CliffH" <Cliff_Harker@.hotmail.com> a écrit dans le message de news:
c13c8375.0409131514.6969f970@.posting.google.com...
> Can anybody shed some light on this for me?
> I have to deploy Reporting Services in what I think is a fairly
> typical 3-tier Internet environment.
> I have the following
> Firewall - 443 only
> IIS Server (x2)
> Firewall - 443 only
> App Server (IIS)(x2)
> Firewall - 1433 only
> SQL Server
> Question. How do I deply Reporting Services in this when the IIS
> server can't talk directly to the SQL Server?
> Is there some form of proxy I can use to pass through requests, via
> the App Servers?
> Any ideas appreciated
> Cliff|||Cliff
The best solution for this would be to install Reporting Services (IIS) on
your Application Server, this will be able to communicate with your SQL
Server and so deployment would be a simple task using the RS command line
util or ReportingServices() .NET class.
To access the application server ReportingServices from the first (UI?) IIS
server you'll need to create a proxy class to the Application Server
Reporting Services using WSDL. You will be able to reference the proxy class
using code in the UI layer.
Hope this helps
"CliffH" wrote:
> Can anybody shed some light on this for me?
> I have to deploy Reporting Services in what I think is a fairly
> typical 3-tier Internet environment.
> I have the following
> Firewall - 443 only
> IIS Server (x2)
> Firewall - 443 only
> App Server (IIS)(x2)
> Firewall - 1433 only
> SQL Server
> Question. How do I deply Reporting Services in this when the IIS
> server can't talk directly to the SQL Server?
> Is there some form of proxy I can use to pass through requests, via
> the App Servers?
> Any ideas appreciated
> Cliff
>|||Thanks for the replies, I'll get our guys to have a look at creating
this "proxy" on the UI IIS server.
Given this is a fairly typical deployment setup I'm surprised there
isn't something in the package itself to facilitate this
Cliff
"Buzz" <Buzz@.discussions.microsoft.com> wrote in message news:<1BE284C9-C5CB-47E0-AAF3-B07021D3CB79@.microsoft.com>...
> Cliff
> The best solution for this would be to install Reporting Services (IIS) on
> your Application Server, this will be able to communicate with your SQL
> Server and so deployment would be a simple task using the RS command line
> util or ReportingServices() .NET class.
> To access the application server ReportingServices from the first (UI?) IIS
> server you'll need to create a proxy class to the Application Server
> Reporting Services using WSDL. You will be able to reference the proxy class
> using code in the UI layer.
> Hope this helps
>
> "CliffH" wrote:
> > Can anybody shed some light on this for me?
> >
> > I have to deploy Reporting Services in what I think is a fairly
> > typical 3-tier Internet environment.
> >
> > I have the following
> >
> > Firewall - 443 only
> > IIS Server (x2)
> > Firewall - 443 only
> > App Server (IIS)(x2)
> > Firewall - 1433 only
> > SQL Server
> >
> > Question. How do I deply Reporting Services in this when the IIS
> > server can't talk directly to the SQL Server?
> >
> > Is there some form of proxy I can use to pass through requests, via
> > the App Servers?
> >
> > Any ideas appreciated
> >
> > Cliff
> >
Monday, March 26, 2012
rsAccessDenied
Hi All,
I have just installed Reporting Services on our production environment.
Everything is set up, the permissions etc and all seems fine until we try to
publish a report
I get the error :
Error rsAccessDenied : The permissions granted to user '[User Name]' are
insufficient for performing this operation.
Deploy complete -- 1 errors, 0 warnings
What have I missed here - on our Dev box I was an Administrator so there
weren't any problems
What permissions does the publisher have to have on the web server to be
able to publish reports?
Thanks
KathrynThe user needs the Manage Reports task. We role this task in a role called
Content Manager (although you could create your own roles with specific
tasks if you want). If you give the user this role then they will be able
to publish reports. To give them permission, go to the folder you want to
give them permission to (in report Manager) and click on the properties tab,
then on the security sub tab. From there you can give them the permissions
you want.
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
"Kathy" <joe@.soap.com> wrote in message
news:PvmdnfocNYNSE3_cRVn-vQ@.is.co.za...
> Hi All,
> I have just installed Reporting Services on our production environment.
> Everything is set up, the permissions etc and all seems fine until we try
> to
> publish a report
> I get the error :
> Error rsAccessDenied : The permissions granted to user '[User Name]' are
> insufficient for performing this operation.
> Deploy complete -- 1 errors, 0 warnings
> What have I missed here - on our Dev box I was an Administrator so there
> weren't any problems
> What permissions does the publisher have to have on the web server to be
> able to publish reports?
> Thanks
> Kathryn
>
>|||Thanks Daniel
Turns out this wasn't the problem.
I actually had to give our group permissions on the Report Server and Report
Manager folders.
"Daniel Reib [MSFT]" <danreib@.online.microsoft.com> wrote in message
news:eB%23dH%23z9EHA.3944@.TK2MSFTNGP12.phx.gbl...
> The user needs the Manage Reports task. We role this task in a role
called
> Content Manager (although you could create your own roles with specific
> tasks if you want). If you give the user this role then they will be able
> to publish reports. To give them permission, go to the folder you want to
> give them permission to (in report Manager) and click on the properties
tab,
> then on the security sub tab. From there you can give them the
permissions
> you want.
> --
> -Daniel
> This posting is provided "AS IS" with no warranties, and confers no
rights.
>
> "Kathy" <joe@.soap.com> wrote in message
> news:PvmdnfocNYNSE3_cRVn-vQ@.is.co.za...
> > Hi All,
> >
> > I have just installed Reporting Services on our production environment.
> > Everything is set up, the permissions etc and all seems fine until we
try
> > to
> > publish a report
> > I get the error :
> > Error rsAccessDenied : The permissions granted to user '[User Name]' are
> > insufficient for performing this operation.
> >
> > Deploy complete -- 1 errors, 0 warnings
> >
> > What have I missed here - on our Dev box I was an Administrator so there
> > weren't any problems
> > What permissions does the publisher have to have on the web server to be
> > able to publish reports?
> >
> > Thanks
> > Kathryn
> >
> >
> >
>
I have just installed Reporting Services on our production environment.
Everything is set up, the permissions etc and all seems fine until we try to
publish a report
I get the error :
Error rsAccessDenied : The permissions granted to user '[User Name]' are
insufficient for performing this operation.
Deploy complete -- 1 errors, 0 warnings
What have I missed here - on our Dev box I was an Administrator so there
weren't any problems
What permissions does the publisher have to have on the web server to be
able to publish reports?
Thanks
KathrynThe user needs the Manage Reports task. We role this task in a role called
Content Manager (although you could create your own roles with specific
tasks if you want). If you give the user this role then they will be able
to publish reports. To give them permission, go to the folder you want to
give them permission to (in report Manager) and click on the properties tab,
then on the security sub tab. From there you can give them the permissions
you want.
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
"Kathy" <joe@.soap.com> wrote in message
news:PvmdnfocNYNSE3_cRVn-vQ@.is.co.za...
> Hi All,
> I have just installed Reporting Services on our production environment.
> Everything is set up, the permissions etc and all seems fine until we try
> to
> publish a report
> I get the error :
> Error rsAccessDenied : The permissions granted to user '[User Name]' are
> insufficient for performing this operation.
> Deploy complete -- 1 errors, 0 warnings
> What have I missed here - on our Dev box I was an Administrator so there
> weren't any problems
> What permissions does the publisher have to have on the web server to be
> able to publish reports?
> Thanks
> Kathryn
>
>|||Thanks Daniel
Turns out this wasn't the problem.
I actually had to give our group permissions on the Report Server and Report
Manager folders.
"Daniel Reib [MSFT]" <danreib@.online.microsoft.com> wrote in message
news:eB%23dH%23z9EHA.3944@.TK2MSFTNGP12.phx.gbl...
> The user needs the Manage Reports task. We role this task in a role
called
> Content Manager (although you could create your own roles with specific
> tasks if you want). If you give the user this role then they will be able
> to publish reports. To give them permission, go to the folder you want to
> give them permission to (in report Manager) and click on the properties
tab,
> then on the security sub tab. From there you can give them the
permissions
> you want.
> --
> -Daniel
> This posting is provided "AS IS" with no warranties, and confers no
rights.
>
> "Kathy" <joe@.soap.com> wrote in message
> news:PvmdnfocNYNSE3_cRVn-vQ@.is.co.za...
> > Hi All,
> >
> > I have just installed Reporting Services on our production environment.
> > Everything is set up, the permissions etc and all seems fine until we
try
> > to
> > publish a report
> > I get the error :
> > Error rsAccessDenied : The permissions granted to user '[User Name]' are
> > insufficient for performing this operation.
> >
> > Deploy complete -- 1 errors, 0 warnings
> >
> > What have I missed here - on our Dev box I was an Administrator so there
> > weren't any problems
> > What permissions does the publisher have to have on the web server to be
> > able to publish reports?
> >
> > Thanks
> > Kathryn
> >
> >
> >
>
Labels:
database,
environment,
installed,
microsoft,
mysql,
oracle,
permissions,
production,
reporting,
rsaccessdenied,
server,
services,
sql
Wednesday, March 21, 2012
RS2003 Ent Install Failing
I get the following error when doing RSW2K3 ENT Installation on WS2K3 SP1
(DC) and SQL Server 2000 SP4 environment. There is no option to ignore the
Error 1603 message , the only option is to cancel and rollback the
installation.
There is a parsing error is in the "LoadRSCatalog" Function- (see end of log)
Has anyone seen this problem before, any suggestions greatefully
appreciated,
<Func Name='CService::~CService'>
Action 22:07:52: Do_sqlScript. Configuring Microsoft SQL Server
SQL_SUCCESS_WITH_INFO (1) in SQLDriverConnectW
sqlstate=01000, level=0, state=0, native_error=5701, msg=Changed database
context to 'master'.
sqlstate=01000, level=0, state=0, native_error=5703, msg=Changed language
setting to us_english.
use master
SQL_SUCCESS_WITH_INFO (1) in SQLExecDirectW
sqlstate=01000, level=0, state=1, native_error=5701, msg=Changed database
context to 'master'.
IF (DB_ID('ReportServer') IS NULL) BEGIN CREATE DATABASE ReportServer
COLLATE Latin1_General_CI_AS_KS_WS END
0
Action 22:07:52: Do_sqlScript. Configuring Microsoft SQL Server
Do_sqlScript: Running SQL Statement
SQL_SUCCESS_WITH_INFO (1) in SQLExecDirectW
sqlstate=01000, level=0, state=1, native_error=1805, msg=The CREATE DATABASE
process is allocating 0.63 MB on disk 'ReportServer'.
sqlstate=01000, level=0, state=1, native_error=1805, msg=The CREATE DATABASE
process is allocating 0.49 MB on disk 'ReportServer_log'.
ALTER DATABASE ReportServer SET RECOVERY FULL
0
IF CHARINDEX('\', 'NT AUTHORITY\NETWORK SERVICE') != 0 BEGIN EXEC
sp_grantlogin 'NT AUTHORITY\NETWORK SERVICE' END
0
SQL_SUCCESS_WITH_INFO (1) in SQLExecDirectW
sqlstate=01000, level=0, state=1, native_error=15481, msg=Granted login
access to 'NT AUTHORITY\NETWORK SERVICE'.
IF (DB_ID('ReportServerTempDB') IS NULL) BEGIN CREATE DATABASE
ReportServerTempDB COLLATE Latin1_General_CI_AS_KS_WS END
0
SQL_SUCCESS_WITH_INFO (1) in SQLExecDirectW
sqlstate=01000, level=0, state=1, native_error=1805, msg=The CREATE DATABASE
process is allocating 0.63 MB on disk 'ReportServerTempDB'.
sqlstate=01000, level=0, state=1, native_error=1805, msg=The CREATE DATABASE
process is allocating 0.49 MB on disk 'ReportServerTempDB_log'.
ALTER DATABASE ReportServerTempDB SET RECOVERY SIMPLE
0
use ReportServerTempDB
SQL_SUCCESS_WITH_INFO (1) in SQLExecDirectW
sqlstate=01000, level=0, state=1, native_error=5701, msg=Changed database
context to 'ReportServerTempDB'.
IF NOT EXISTS (SELECT * FROM dbo.sysusers WHERE name='RSExecRole' AND
issqlrole=1) EXEC sp_addrole 'RSExecRole'
0
SQL_SUCCESS_WITH_INFO (1) in SQLExecDirectW
sqlstate=01000, level=0, state=1, native_error=15424, msg=New role added.
DECLARE @.pname AS sysname DECLARE @.i AS INT IF LOWER('NT AUTHORITY\NETWORK
SERVICE') != 'sa' AND NOT EXISTS (SELECT db1.dbid FROM
master.dbo.sysdatabases AS db1, master.dbo.syslogins AS logins1 WHERE db1.sid
= logins1.sid AND logins1.name = 'NT AUTHORITY\NETWORK SERVICE' AND db1.name
= 'ReportServerTempDB') AND NOT EXISTS (SELECT users1.name FROM dbo.sysusers
AS users1, master.dbo.syslogins AS logins1 WHERE users1.sid = logins1.sid AND
logins1.name = 'NT AUTHORITY\NETWORK SERVICE') BEGIN SET @.i = 0 SET @.pname = 'NT AUTHORITY\NETWORK SERVICE' WHILE EXISTS (SELECT name FROM dbo.sysusers
WHERE name=@.pname) BEGIN SET @.i = @.i + 1 SET @.pname = @.pname +
CONVERT(NVARCHAR(10), @.i) END EXEC sp_grantdbaccess 'NT AUTHORITY\NETWORK
SERVICE', @.pname END
0
SQL_SUCCESS_WITH_INFO (1) in SQLExecDirectW
sqlstate=01000, level=0, state=1, native_error=15341, msg=Granted database
access to 'NT AUTHORITY\NETWORK SERVICE'.
DECLARE @.pname AS sysname IF LOWER('NT AUTHORITY\NETWORK SERVICE') != 'sa'
AND NOT EXISTS (SELECT db1.dbid FROM master.dbo.sysdatabases AS db1,
master.dbo.syslogins AS logins1 WHERE db1.sid = logins1.sid AND logins1.name
= 'NT AUTHORITY\NETWORK SERVICE' AND db1.name = 'ReportServerTempDB') BEGIN
SELECT @.pname = (SELECT users1.name FROM dbo.sysusers AS users1,
master.dbo.syslogins AS logins1 WHERE users1.sid = logins1.sid AND
logins1.name = 'NT AUTHORITY\NETWORK SERVICE') EXEC sp_addrolemember
'RSExecRole', @.pname END
0
SQL_SUCCESS_WITH_INFO (1) in SQLExecDirectW
sqlstate=01000, level=0, state=1, native_error=15488, msg='NT
AUTHORITY\NETWORK SERVICE' added to role 'RSExecRole'.
D:\Program Files\Microsoft SQL Server\MSSQL\Reporting
Services\ReportServer\CatalogTempDB.sql
17
Action 22:07:52: Do_sqlScript. Configuring Microsoft SQL Server
Do_sqlScript: Running SQL Script: D:\Program Files\Microsoft SQL
Server\MSSQL\Reporting Services\ReportServer\CatalogTempDB.sql
<Func Name='LoadRSCatalog'>
error parsing script file D:\Program Files\Microsoft SQL
Server\MSSQL\Reporting Services\ReportServer\CatalogTempDB.sql: 87
Error 29525. SQL Setup failed to execute a command for server configuration.
Refer to the Server error logs and setup logs for detailed error information.
MSI (s) (F4!C8) [22:08:37:874]: Product: Microsoft SQL Server 2000 Reporting
Services Enterprise Edition -- Error 29525. SQL Setup failed to execute a
command for server configuration. Refer to the Server error logs and setup
logs for detailed error information.
<EndFunc Name='SqlScriptHlpr' Return='1603' GetLastError='0'>
<EndFunc Name='Do_sqlScript' Return='1603' GetLastError='0'>
Gathering darwin properties for failure handling.
<Func Name='DisplayErrorDialog'>
regardsIts RS2000 Enterprise Edition not RSY2K3 ENT.
"Graham Smith" wrote:
> I get the following error when doing RSW2K3 ENT Installation on WS2K3 SP1
> (DC) and SQL Server 2000 SP4 environment. There is no option to ignore the
> Error 1603 message , the only option is to cancel and rollback the
> installation.
> There is a parsing error is in the "LoadRSCatalog" Function- (see end of log)
> Has anyone seen this problem before, any suggestions greatefully
> appreciated,
>
> <Func Name='CService::~CService'>
> Action 22:07:52: Do_sqlScript. Configuring Microsoft SQL Server
> SQL_SUCCESS_WITH_INFO (1) in SQLDriverConnectW
> sqlstate=01000, level=0, state=0, native_error=5701, msg=Changed database
> context to 'master'.
> sqlstate=01000, level=0, state=0, native_error=5703, msg=Changed language
> setting to us_english.
> use master
> SQL_SUCCESS_WITH_INFO (1) in SQLExecDirectW
> sqlstate=01000, level=0, state=1, native_error=5701, msg=Changed database
> context to 'master'.
> IF (DB_ID('ReportServer') IS NULL) BEGIN CREATE DATABASE ReportServer
> COLLATE Latin1_General_CI_AS_KS_WS END
> 0
> Action 22:07:52: Do_sqlScript. Configuring Microsoft SQL Server
> Do_sqlScript: Running SQL Statement
> SQL_SUCCESS_WITH_INFO (1) in SQLExecDirectW
> sqlstate=01000, level=0, state=1, native_error=1805, msg=The CREATE DATABASE
> process is allocating 0.63 MB on disk 'ReportServer'.
> sqlstate=01000, level=0, state=1, native_error=1805, msg=The CREATE DATABASE
> process is allocating 0.49 MB on disk 'ReportServer_log'.
> ALTER DATABASE ReportServer SET RECOVERY FULL
> 0
> IF CHARINDEX('\', 'NT AUTHORITY\NETWORK SERVICE') != 0 BEGIN EXEC
> sp_grantlogin 'NT AUTHORITY\NETWORK SERVICE' END
> 0
> SQL_SUCCESS_WITH_INFO (1) in SQLExecDirectW
> sqlstate=01000, level=0, state=1, native_error=15481, msg=Granted login
> access to 'NT AUTHORITY\NETWORK SERVICE'.
> IF (DB_ID('ReportServerTempDB') IS NULL) BEGIN CREATE DATABASE
> ReportServerTempDB COLLATE Latin1_General_CI_AS_KS_WS END
> 0
> SQL_SUCCESS_WITH_INFO (1) in SQLExecDirectW
> sqlstate=01000, level=0, state=1, native_error=1805, msg=The CREATE DATABASE
> process is allocating 0.63 MB on disk 'ReportServerTempDB'.
> sqlstate=01000, level=0, state=1, native_error=1805, msg=The CREATE DATABASE
> process is allocating 0.49 MB on disk 'ReportServerTempDB_log'.
> ALTER DATABASE ReportServerTempDB SET RECOVERY SIMPLE
> 0
> use ReportServerTempDB
> SQL_SUCCESS_WITH_INFO (1) in SQLExecDirectW
> sqlstate=01000, level=0, state=1, native_error=5701, msg=Changed database
> context to 'ReportServerTempDB'.
> IF NOT EXISTS (SELECT * FROM dbo.sysusers WHERE name='RSExecRole' AND
> issqlrole=1) EXEC sp_addrole 'RSExecRole'
> 0
> SQL_SUCCESS_WITH_INFO (1) in SQLExecDirectW
> sqlstate=01000, level=0, state=1, native_error=15424, msg=New role added.
> DECLARE @.pname AS sysname DECLARE @.i AS INT IF LOWER('NT AUTHORITY\NETWORK
> SERVICE') != 'sa' AND NOT EXISTS (SELECT db1.dbid FROM
> master.dbo.sysdatabases AS db1, master.dbo.syslogins AS logins1 WHERE db1.sid
> = logins1.sid AND logins1.name = 'NT AUTHORITY\NETWORK SERVICE' AND db1.name
> = 'ReportServerTempDB') AND NOT EXISTS (SELECT users1.name FROM dbo.sysusers
> AS users1, master.dbo.syslogins AS logins1 WHERE users1.sid = logins1.sid AND
> logins1.name = 'NT AUTHORITY\NETWORK SERVICE') BEGIN SET @.i = 0 SET @.pname => 'NT AUTHORITY\NETWORK SERVICE' WHILE EXISTS (SELECT name FROM dbo.sysusers
> WHERE name=@.pname) BEGIN SET @.i = @.i + 1 SET @.pname = @.pname +
> CONVERT(NVARCHAR(10), @.i) END EXEC sp_grantdbaccess 'NT AUTHORITY\NETWORK
> SERVICE', @.pname END
> 0
> SQL_SUCCESS_WITH_INFO (1) in SQLExecDirectW
> sqlstate=01000, level=0, state=1, native_error=15341, msg=Granted database
> access to 'NT AUTHORITY\NETWORK SERVICE'.
> DECLARE @.pname AS sysname IF LOWER('NT AUTHORITY\NETWORK SERVICE') != 'sa'
> AND NOT EXISTS (SELECT db1.dbid FROM master.dbo.sysdatabases AS db1,
> master.dbo.syslogins AS logins1 WHERE db1.sid = logins1.sid AND logins1.name
> = 'NT AUTHORITY\NETWORK SERVICE' AND db1.name = 'ReportServerTempDB') BEGIN
> SELECT @.pname = (SELECT users1.name FROM dbo.sysusers AS users1,
> master.dbo.syslogins AS logins1 WHERE users1.sid = logins1.sid AND
> logins1.name = 'NT AUTHORITY\NETWORK SERVICE') EXEC sp_addrolemember
> 'RSExecRole', @.pname END
> 0
> SQL_SUCCESS_WITH_INFO (1) in SQLExecDirectW
> sqlstate=01000, level=0, state=1, native_error=15488, msg='NT
> AUTHORITY\NETWORK SERVICE' added to role 'RSExecRole'.
> D:\Program Files\Microsoft SQL Server\MSSQL\Reporting
> Services\ReportServer\CatalogTempDB.sql
> 17
> Action 22:07:52: Do_sqlScript. Configuring Microsoft SQL Server
> Do_sqlScript: Running SQL Script: D:\Program Files\Microsoft SQL
> Server\MSSQL\Reporting Services\ReportServer\CatalogTempDB.sql
> <Func Name='LoadRSCatalog'>
> error parsing script file D:\Program Files\Microsoft SQL
> Server\MSSQL\Reporting Services\ReportServer\CatalogTempDB.sql: 87
> Error 29525. SQL Setup failed to execute a command for server configuration.
> Refer to the Server error logs and setup logs for detailed error information.
> MSI (s) (F4!C8) [22:08:37:874]: Product: Microsoft SQL Server 2000 Reporting
> Services Enterprise Edition -- Error 29525. SQL Setup failed to execute a
> command for server configuration. Refer to the Server error logs and setup
> logs for detailed error information.
> <EndFunc Name='SqlScriptHlpr' Return='1603' GetLastError='0'>
> <EndFunc Name='Do_sqlScript' Return='1603' GetLastError='0'>
> Gathering darwin properties for failure handling.
> <Func Name='DisplayErrorDialog'>
> regards
>
(DC) and SQL Server 2000 SP4 environment. There is no option to ignore the
Error 1603 message , the only option is to cancel and rollback the
installation.
There is a parsing error is in the "LoadRSCatalog" Function- (see end of log)
Has anyone seen this problem before, any suggestions greatefully
appreciated,
<Func Name='CService::~CService'>
Action 22:07:52: Do_sqlScript. Configuring Microsoft SQL Server
SQL_SUCCESS_WITH_INFO (1) in SQLDriverConnectW
sqlstate=01000, level=0, state=0, native_error=5701, msg=Changed database
context to 'master'.
sqlstate=01000, level=0, state=0, native_error=5703, msg=Changed language
setting to us_english.
use master
SQL_SUCCESS_WITH_INFO (1) in SQLExecDirectW
sqlstate=01000, level=0, state=1, native_error=5701, msg=Changed database
context to 'master'.
IF (DB_ID('ReportServer') IS NULL) BEGIN CREATE DATABASE ReportServer
COLLATE Latin1_General_CI_AS_KS_WS END
0
Action 22:07:52: Do_sqlScript. Configuring Microsoft SQL Server
Do_sqlScript: Running SQL Statement
SQL_SUCCESS_WITH_INFO (1) in SQLExecDirectW
sqlstate=01000, level=0, state=1, native_error=1805, msg=The CREATE DATABASE
process is allocating 0.63 MB on disk 'ReportServer'.
sqlstate=01000, level=0, state=1, native_error=1805, msg=The CREATE DATABASE
process is allocating 0.49 MB on disk 'ReportServer_log'.
ALTER DATABASE ReportServer SET RECOVERY FULL
0
IF CHARINDEX('\', 'NT AUTHORITY\NETWORK SERVICE') != 0 BEGIN EXEC
sp_grantlogin 'NT AUTHORITY\NETWORK SERVICE' END
0
SQL_SUCCESS_WITH_INFO (1) in SQLExecDirectW
sqlstate=01000, level=0, state=1, native_error=15481, msg=Granted login
access to 'NT AUTHORITY\NETWORK SERVICE'.
IF (DB_ID('ReportServerTempDB') IS NULL) BEGIN CREATE DATABASE
ReportServerTempDB COLLATE Latin1_General_CI_AS_KS_WS END
0
SQL_SUCCESS_WITH_INFO (1) in SQLExecDirectW
sqlstate=01000, level=0, state=1, native_error=1805, msg=The CREATE DATABASE
process is allocating 0.63 MB on disk 'ReportServerTempDB'.
sqlstate=01000, level=0, state=1, native_error=1805, msg=The CREATE DATABASE
process is allocating 0.49 MB on disk 'ReportServerTempDB_log'.
ALTER DATABASE ReportServerTempDB SET RECOVERY SIMPLE
0
use ReportServerTempDB
SQL_SUCCESS_WITH_INFO (1) in SQLExecDirectW
sqlstate=01000, level=0, state=1, native_error=5701, msg=Changed database
context to 'ReportServerTempDB'.
IF NOT EXISTS (SELECT * FROM dbo.sysusers WHERE name='RSExecRole' AND
issqlrole=1) EXEC sp_addrole 'RSExecRole'
0
SQL_SUCCESS_WITH_INFO (1) in SQLExecDirectW
sqlstate=01000, level=0, state=1, native_error=15424, msg=New role added.
DECLARE @.pname AS sysname DECLARE @.i AS INT IF LOWER('NT AUTHORITY\NETWORK
SERVICE') != 'sa' AND NOT EXISTS (SELECT db1.dbid FROM
master.dbo.sysdatabases AS db1, master.dbo.syslogins AS logins1 WHERE db1.sid
= logins1.sid AND logins1.name = 'NT AUTHORITY\NETWORK SERVICE' AND db1.name
= 'ReportServerTempDB') AND NOT EXISTS (SELECT users1.name FROM dbo.sysusers
AS users1, master.dbo.syslogins AS logins1 WHERE users1.sid = logins1.sid AND
logins1.name = 'NT AUTHORITY\NETWORK SERVICE') BEGIN SET @.i = 0 SET @.pname = 'NT AUTHORITY\NETWORK SERVICE' WHILE EXISTS (SELECT name FROM dbo.sysusers
WHERE name=@.pname) BEGIN SET @.i = @.i + 1 SET @.pname = @.pname +
CONVERT(NVARCHAR(10), @.i) END EXEC sp_grantdbaccess 'NT AUTHORITY\NETWORK
SERVICE', @.pname END
0
SQL_SUCCESS_WITH_INFO (1) in SQLExecDirectW
sqlstate=01000, level=0, state=1, native_error=15341, msg=Granted database
access to 'NT AUTHORITY\NETWORK SERVICE'.
DECLARE @.pname AS sysname IF LOWER('NT AUTHORITY\NETWORK SERVICE') != 'sa'
AND NOT EXISTS (SELECT db1.dbid FROM master.dbo.sysdatabases AS db1,
master.dbo.syslogins AS logins1 WHERE db1.sid = logins1.sid AND logins1.name
= 'NT AUTHORITY\NETWORK SERVICE' AND db1.name = 'ReportServerTempDB') BEGIN
SELECT @.pname = (SELECT users1.name FROM dbo.sysusers AS users1,
master.dbo.syslogins AS logins1 WHERE users1.sid = logins1.sid AND
logins1.name = 'NT AUTHORITY\NETWORK SERVICE') EXEC sp_addrolemember
'RSExecRole', @.pname END
0
SQL_SUCCESS_WITH_INFO (1) in SQLExecDirectW
sqlstate=01000, level=0, state=1, native_error=15488, msg='NT
AUTHORITY\NETWORK SERVICE' added to role 'RSExecRole'.
D:\Program Files\Microsoft SQL Server\MSSQL\Reporting
Services\ReportServer\CatalogTempDB.sql
17
Action 22:07:52: Do_sqlScript. Configuring Microsoft SQL Server
Do_sqlScript: Running SQL Script: D:\Program Files\Microsoft SQL
Server\MSSQL\Reporting Services\ReportServer\CatalogTempDB.sql
<Func Name='LoadRSCatalog'>
error parsing script file D:\Program Files\Microsoft SQL
Server\MSSQL\Reporting Services\ReportServer\CatalogTempDB.sql: 87
Error 29525. SQL Setup failed to execute a command for server configuration.
Refer to the Server error logs and setup logs for detailed error information.
MSI (s) (F4!C8) [22:08:37:874]: Product: Microsoft SQL Server 2000 Reporting
Services Enterprise Edition -- Error 29525. SQL Setup failed to execute a
command for server configuration. Refer to the Server error logs and setup
logs for detailed error information.
<EndFunc Name='SqlScriptHlpr' Return='1603' GetLastError='0'>
<EndFunc Name='Do_sqlScript' Return='1603' GetLastError='0'>
Gathering darwin properties for failure handling.
<Func Name='DisplayErrorDialog'>
regardsIts RS2000 Enterprise Edition not RSY2K3 ENT.
"Graham Smith" wrote:
> I get the following error when doing RSW2K3 ENT Installation on WS2K3 SP1
> (DC) and SQL Server 2000 SP4 environment. There is no option to ignore the
> Error 1603 message , the only option is to cancel and rollback the
> installation.
> There is a parsing error is in the "LoadRSCatalog" Function- (see end of log)
> Has anyone seen this problem before, any suggestions greatefully
> appreciated,
>
> <Func Name='CService::~CService'>
> Action 22:07:52: Do_sqlScript. Configuring Microsoft SQL Server
> SQL_SUCCESS_WITH_INFO (1) in SQLDriverConnectW
> sqlstate=01000, level=0, state=0, native_error=5701, msg=Changed database
> context to 'master'.
> sqlstate=01000, level=0, state=0, native_error=5703, msg=Changed language
> setting to us_english.
> use master
> SQL_SUCCESS_WITH_INFO (1) in SQLExecDirectW
> sqlstate=01000, level=0, state=1, native_error=5701, msg=Changed database
> context to 'master'.
> IF (DB_ID('ReportServer') IS NULL) BEGIN CREATE DATABASE ReportServer
> COLLATE Latin1_General_CI_AS_KS_WS END
> 0
> Action 22:07:52: Do_sqlScript. Configuring Microsoft SQL Server
> Do_sqlScript: Running SQL Statement
> SQL_SUCCESS_WITH_INFO (1) in SQLExecDirectW
> sqlstate=01000, level=0, state=1, native_error=1805, msg=The CREATE DATABASE
> process is allocating 0.63 MB on disk 'ReportServer'.
> sqlstate=01000, level=0, state=1, native_error=1805, msg=The CREATE DATABASE
> process is allocating 0.49 MB on disk 'ReportServer_log'.
> ALTER DATABASE ReportServer SET RECOVERY FULL
> 0
> IF CHARINDEX('\', 'NT AUTHORITY\NETWORK SERVICE') != 0 BEGIN EXEC
> sp_grantlogin 'NT AUTHORITY\NETWORK SERVICE' END
> 0
> SQL_SUCCESS_WITH_INFO (1) in SQLExecDirectW
> sqlstate=01000, level=0, state=1, native_error=15481, msg=Granted login
> access to 'NT AUTHORITY\NETWORK SERVICE'.
> IF (DB_ID('ReportServerTempDB') IS NULL) BEGIN CREATE DATABASE
> ReportServerTempDB COLLATE Latin1_General_CI_AS_KS_WS END
> 0
> SQL_SUCCESS_WITH_INFO (1) in SQLExecDirectW
> sqlstate=01000, level=0, state=1, native_error=1805, msg=The CREATE DATABASE
> process is allocating 0.63 MB on disk 'ReportServerTempDB'.
> sqlstate=01000, level=0, state=1, native_error=1805, msg=The CREATE DATABASE
> process is allocating 0.49 MB on disk 'ReportServerTempDB_log'.
> ALTER DATABASE ReportServerTempDB SET RECOVERY SIMPLE
> 0
> use ReportServerTempDB
> SQL_SUCCESS_WITH_INFO (1) in SQLExecDirectW
> sqlstate=01000, level=0, state=1, native_error=5701, msg=Changed database
> context to 'ReportServerTempDB'.
> IF NOT EXISTS (SELECT * FROM dbo.sysusers WHERE name='RSExecRole' AND
> issqlrole=1) EXEC sp_addrole 'RSExecRole'
> 0
> SQL_SUCCESS_WITH_INFO (1) in SQLExecDirectW
> sqlstate=01000, level=0, state=1, native_error=15424, msg=New role added.
> DECLARE @.pname AS sysname DECLARE @.i AS INT IF LOWER('NT AUTHORITY\NETWORK
> SERVICE') != 'sa' AND NOT EXISTS (SELECT db1.dbid FROM
> master.dbo.sysdatabases AS db1, master.dbo.syslogins AS logins1 WHERE db1.sid
> = logins1.sid AND logins1.name = 'NT AUTHORITY\NETWORK SERVICE' AND db1.name
> = 'ReportServerTempDB') AND NOT EXISTS (SELECT users1.name FROM dbo.sysusers
> AS users1, master.dbo.syslogins AS logins1 WHERE users1.sid = logins1.sid AND
> logins1.name = 'NT AUTHORITY\NETWORK SERVICE') BEGIN SET @.i = 0 SET @.pname => 'NT AUTHORITY\NETWORK SERVICE' WHILE EXISTS (SELECT name FROM dbo.sysusers
> WHERE name=@.pname) BEGIN SET @.i = @.i + 1 SET @.pname = @.pname +
> CONVERT(NVARCHAR(10), @.i) END EXEC sp_grantdbaccess 'NT AUTHORITY\NETWORK
> SERVICE', @.pname END
> 0
> SQL_SUCCESS_WITH_INFO (1) in SQLExecDirectW
> sqlstate=01000, level=0, state=1, native_error=15341, msg=Granted database
> access to 'NT AUTHORITY\NETWORK SERVICE'.
> DECLARE @.pname AS sysname IF LOWER('NT AUTHORITY\NETWORK SERVICE') != 'sa'
> AND NOT EXISTS (SELECT db1.dbid FROM master.dbo.sysdatabases AS db1,
> master.dbo.syslogins AS logins1 WHERE db1.sid = logins1.sid AND logins1.name
> = 'NT AUTHORITY\NETWORK SERVICE' AND db1.name = 'ReportServerTempDB') BEGIN
> SELECT @.pname = (SELECT users1.name FROM dbo.sysusers AS users1,
> master.dbo.syslogins AS logins1 WHERE users1.sid = logins1.sid AND
> logins1.name = 'NT AUTHORITY\NETWORK SERVICE') EXEC sp_addrolemember
> 'RSExecRole', @.pname END
> 0
> SQL_SUCCESS_WITH_INFO (1) in SQLExecDirectW
> sqlstate=01000, level=0, state=1, native_error=15488, msg='NT
> AUTHORITY\NETWORK SERVICE' added to role 'RSExecRole'.
> D:\Program Files\Microsoft SQL Server\MSSQL\Reporting
> Services\ReportServer\CatalogTempDB.sql
> 17
> Action 22:07:52: Do_sqlScript. Configuring Microsoft SQL Server
> Do_sqlScript: Running SQL Script: D:\Program Files\Microsoft SQL
> Server\MSSQL\Reporting Services\ReportServer\CatalogTempDB.sql
> <Func Name='LoadRSCatalog'>
> error parsing script file D:\Program Files\Microsoft SQL
> Server\MSSQL\Reporting Services\ReportServer\CatalogTempDB.sql: 87
> Error 29525. SQL Setup failed to execute a command for server configuration.
> Refer to the Server error logs and setup logs for detailed error information.
> MSI (s) (F4!C8) [22:08:37:874]: Product: Microsoft SQL Server 2000 Reporting
> Services Enterprise Edition -- Error 29525. SQL Setup failed to execute a
> command for server configuration. Refer to the Server error logs and setup
> logs for detailed error information.
> <EndFunc Name='SqlScriptHlpr' Return='1603' GetLastError='0'>
> <EndFunc Name='Do_sqlScript' Return='1603' GetLastError='0'>
> Gathering darwin properties for failure handling.
> <Func Name='DisplayErrorDialog'>
> regards
>
Tuesday, March 20, 2012
rs.exe scripts
I'm a SQL Server DBA and will be playing the role of a
SQL2000 Reporting Services administrator. To tightly
control the environment and keep track of all the changes,
I'm considering to implement a policy that requires all
changes to Reporting Services and reports be released into
production via VB.NET scripts for rs.exe, and all such
scripts be submitted to me for review first.
I'd like to bounce this off you guys to see (1) whether
I'm going overboard, and (2) whether all changes can be
implemented via RS scripts.
JoeAs far as your first question, about going overboard... it's not clear to me
how this policy can be enforced. Users could just run any script, or write
their own app to talk to the server. If you really want to prevent users
from performing certain actions, I recommend using the built in security to
give users only the permissions they need for the actions you want them to
take.
As far as functionality... rs.exe has complete access to the SOAP API.
--
This posting is provided "AS IS" with no warranties, and confers no rights
"Joe Bourne" <anonymous@.discussions.microsoft.com> wrote in message
news:46ae01c4734b$5b917fa0$a401280a@.phx.gbl...
> I'm a SQL Server DBA and will be playing the role of a
> SQL2000 Reporting Services administrator. To tightly
> control the environment and keep track of all the changes,
> I'm considering to implement a policy that requires all
> changes to Reporting Services and reports be released into
> production via VB.NET scripts for rs.exe, and all such
> scripts be submitted to me for review first.
> I'd like to bounce this off you guys to see (1) whether
> I'm going overboard, and (2) whether all changes can be
> implemented via RS scripts.
> Joe|||Thanks, Brian!
I was thinking in the line of SQL Server's DDL vs DML, if
I can make such a similar distinction in SSRS. So
for 'DDL' type of changes, I'll try to enforce the rs
scripting requirement, whereas for 'DML' type of changes,
the users can make whatever changes however they want.
Just like in SQL Server, the users can
insert/delete/update their data with their permissions,
and I really don't care what they do. But when it comes to
schema changes, I make sure that thye submit scripts to me
first.
Now, can I classify SSRS tasks into 'DDL' and 'DML', and
assign security to allow DML changes only?
Joe
>--Original Message--
>As far as your first question, about going overboard...
it's not clear to me
>how this policy can be enforced. Users could just run
any script, or write
>their own app to talk to the server. If you really want
to prevent users
>from performing certain actions, I recommend using the
built in security to
>give users only the permissions they need for the actions
you want them to
>take.
>As far as functionality... rs.exe has complete access to
the SOAP API.
>--
>This posting is provided "AS IS" with no warranties, and
confers no rights
>"Joe Bourne" <anonymous@.discussions.microsoft.com> wrote
in message
>news:46ae01c4734b$5b917fa0$a401280a@.phx.gbl...
>> I'm a SQL Server DBA and will be playing the role of a
>> SQL2000 Reporting Services administrator. To tightly
>> control the environment and keep track of all the
changes,
>> I'm considering to implement a policy that requires all
>> changes to Reporting Services and reports be released
into
>> production via VB.NET scripts for rs.exe, and all such
>> scripts be submitted to me for review first.
>> I'd like to bounce this off you guys to see (1) whether
>> I'm going overboard, and (2) whether all changes can be
>> implemented via RS scripts.
>> Joe
>
>.
>
SQL2000 Reporting Services administrator. To tightly
control the environment and keep track of all the changes,
I'm considering to implement a policy that requires all
changes to Reporting Services and reports be released into
production via VB.NET scripts for rs.exe, and all such
scripts be submitted to me for review first.
I'd like to bounce this off you guys to see (1) whether
I'm going overboard, and (2) whether all changes can be
implemented via RS scripts.
JoeAs far as your first question, about going overboard... it's not clear to me
how this policy can be enforced. Users could just run any script, or write
their own app to talk to the server. If you really want to prevent users
from performing certain actions, I recommend using the built in security to
give users only the permissions they need for the actions you want them to
take.
As far as functionality... rs.exe has complete access to the SOAP API.
--
This posting is provided "AS IS" with no warranties, and confers no rights
"Joe Bourne" <anonymous@.discussions.microsoft.com> wrote in message
news:46ae01c4734b$5b917fa0$a401280a@.phx.gbl...
> I'm a SQL Server DBA and will be playing the role of a
> SQL2000 Reporting Services administrator. To tightly
> control the environment and keep track of all the changes,
> I'm considering to implement a policy that requires all
> changes to Reporting Services and reports be released into
> production via VB.NET scripts for rs.exe, and all such
> scripts be submitted to me for review first.
> I'd like to bounce this off you guys to see (1) whether
> I'm going overboard, and (2) whether all changes can be
> implemented via RS scripts.
> Joe|||Thanks, Brian!
I was thinking in the line of SQL Server's DDL vs DML, if
I can make such a similar distinction in SSRS. So
for 'DDL' type of changes, I'll try to enforce the rs
scripting requirement, whereas for 'DML' type of changes,
the users can make whatever changes however they want.
Just like in SQL Server, the users can
insert/delete/update their data with their permissions,
and I really don't care what they do. But when it comes to
schema changes, I make sure that thye submit scripts to me
first.
Now, can I classify SSRS tasks into 'DDL' and 'DML', and
assign security to allow DML changes only?
Joe
>--Original Message--
>As far as your first question, about going overboard...
it's not clear to me
>how this policy can be enforced. Users could just run
any script, or write
>their own app to talk to the server. If you really want
to prevent users
>from performing certain actions, I recommend using the
built in security to
>give users only the permissions they need for the actions
you want them to
>take.
>As far as functionality... rs.exe has complete access to
the SOAP API.
>--
>This posting is provided "AS IS" with no warranties, and
confers no rights
>"Joe Bourne" <anonymous@.discussions.microsoft.com> wrote
in message
>news:46ae01c4734b$5b917fa0$a401280a@.phx.gbl...
>> I'm a SQL Server DBA and will be playing the role of a
>> SQL2000 Reporting Services administrator. To tightly
>> control the environment and keep track of all the
changes,
>> I'm considering to implement a policy that requires all
>> changes to Reporting Services and reports be released
into
>> production via VB.NET scripts for rs.exe, and all such
>> scripts be submitted to me for review first.
>> I'd like to bounce this off you guys to see (1) whether
>> I'm going overboard, and (2) whether all changes can be
>> implemented via RS scripts.
>> Joe
>
>.
>
Monday, March 12, 2012
RS to DMZ
Hello,
If I am using a DMZ machine, how can I deploy my report from my development environment to a DMZ machine? Should I install Reporting Services client or server to DMZ or can I still use the reporting services server I installed in my Development environment.
Thanks,
Kinda Good Morning or Good Evening!In my humble insight to your question -
I am sure it doesn't matter if your environment (servers) are within or outside of the DMZ or not!
But if you want to deploy any and all Reporting Services reports to another server - you need Reporting Services installed on that target machine - unless
1. You provide a TCP port that is exclusive from the DMZ to the server where Reporting Services is installed, and VOILA
2. If you do not want to provide the exclusive and secured port from the DMZ to the server where Reporting Services is installed - then install Reporting Services on the DMZ or point to another server within the DMZ (once again, RS needs to be installed there) !
Best Regards
Subscribe to:
Posts (Atom)