New Installation Error

Hello all.
After suffering a complete RAID failure, I am now tasked with the
responsibility of setting up reporting services again, on a new and
different machine. I had been successful getting it running last time,
so I figured this wouldn't be too much problem. The installation goes
fine, until the end, when it reports that the service wont start for
the first time.
As for information. Server2003-sp1. For the ReportServer Windows
service I'm using account (NT AUTHORITY\NETWORK SERVICE). I've left
virtual directories the same, except that I've disabled SSL
connections. The Database is running locally, and for the runtime
connection credentials, I've chosen to use a Domain User Account (set
up especially for this purpose) "RSExec".
As I said, the install goes fine, but fails. The only thing I can
think of is that maybe my new RSExec user needs more permission than a
standard user. But I've read the books (Lachev, and Blackburn &
Vaughn), as well as the BOL, and I can't find any indication of what I
might be missing.
Opening the //machine/ReportServer page, I get the following error
message:
* The report server cannot open a connection to the report server
database. The logon failed. (rsReportServerDatabaseLogonFailed) Get
Online Help
o Logon failure: the user has not been granted the requested logon
type at this computer.
The error message from the log shows:
w3wp!ui!dc0!9/27/2005-08:25:37:: e ERROR:
System.Web.Services.Protocols.SoapException: The report server cannot
open a connection to the report server database. The logon failed. -->
Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerDatabaseLogonFailedException:
The report server cannot open a connection to the report server
database. The logon failed. -->
System.Runtime.InteropServices.COMException (0x80070569): Logon
failure: the user has not been granted the requested logon type at this
computer.
at System.Runtime.InteropServices.Marshal.ThrowExceptionForHR(Int32
errorCode, IntPtr errorInfo)
at RSRemoteRpcClient.RemoteLogon.GetRemoteImpToken(String pUserName,
String pDomain, String pPassword, Boolean bTryRemote, IntPtr&
pImpToken)
at
Microsoft.ReportingServices.Library.ConnectionManager.GetImpersonationToken(String
userName, String domain, String userPwd)
-- End of inner exception stack trace --
Thanks for all your help. It is sincerely appreciated.
Brian AckermannDid you grant RSExec permissions to logon to SQL server? If so, can you
check to see if the user has permission to the RS database?
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
"Brian Ackermann" <brian.ackermann@.gmail.com> wrote in message
news:1127830923.220944.153010@.g44g2000cwa.googlegroups.com...
> Hello all.
> After suffering a complete RAID failure, I am now tasked with the
> responsibility of setting up reporting services again, on a new and
> different machine. I had been successful getting it running last time,
> so I figured this wouldn't be too much problem. The installation goes
> fine, until the end, when it reports that the service wont start for
> the first time.
> As for information. Server2003-sp1. For the ReportServer Windows
> service I'm using account (NT AUTHORITY\NETWORK SERVICE). I've left
> virtual directories the same, except that I've disabled SSL
> connections. The Database is running locally, and for the runtime
> connection credentials, I've chosen to use a Domain User Account (set
> up especially for this purpose) "RSExec".
> As I said, the install goes fine, but fails. The only thing I can
> think of is that maybe my new RSExec user needs more permission than a
> standard user. But I've read the books (Lachev, and Blackburn &
> Vaughn), as well as the BOL, and I can't find any indication of what I
> might be missing.
> Opening the //machine/ReportServer page, I get the following error
> message:
> * The report server cannot open a connection to the report server
> database. The logon failed. (rsReportServerDatabaseLogonFailed) Get
> Online Help
> o Logon failure: the user has not been granted the requested logon
> type at this computer.
> The error message from the log shows:
> w3wp!ui!dc0!9/27/2005-08:25:37:: e ERROR:
> System.Web.Services.Protocols.SoapException: The report server cannot
> open a connection to the report server database. The logon failed. -->
> Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerDatabaseLogonFailedException:
> The report server cannot open a connection to the report server
> database. The logon failed. -->
> System.Runtime.InteropServices.COMException (0x80070569): Logon
> failure: the user has not been granted the requested logon type at this
> computer.
> at System.Runtime.InteropServices.Marshal.ThrowExceptionForHR(Int32
> errorCode, IntPtr errorInfo)
> at RSRemoteRpcClient.RemoteLogon.GetRemoteImpToken(String pUserName,
> String pDomain, String pPassword, Boolean bTryRemote, IntPtr&
> pImpToken)
> at
> Microsoft.ReportingServices.Library.ConnectionManager.GetImpersonationToken(String
> userName, String domain, String userPwd)
> -- End of inner exception stack trace --
> Thanks for all your help. It is sincerely appreciated.
> Brian Ackermann
>|||Daniel,
Thanks for the reply.
As far as I can tell, the installer gives the RSExec user permissions
on the database. I must be missing it if there was something else.
There was a user called RSExec intalled on the database, with what
appeared to be appropriate values.
Can you be more explicit as to what settings exactly need to be set.
I'm sure its quite simple, and that I'm just not seeing it.
Thanks
Brian Ackermann|||From the look of the call stack, it appears that you are using a domain
account to talk to the RS database server. It doesn't appear that user has
permission to logon to the RS box. You should verify if that is the case.
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
"Brian Ackermann" <brian.ackermann@.gmail.com> wrote in message
news:1127939219.565435.135110@.o13g2000cwo.googlegroups.com...
> Daniel,
> Thanks for the reply.
> As far as I can tell, the installer gives the RSExec user permissions
> on the database. I must be missing it if there was something else.
> There was a user called RSExec intalled on the database, with what
> appeared to be appropriate values.
> Can you be more explicit as to what settings exactly need to be set.
> I'm sure its quite simple, and that I'm just not seeing it.
> Thanks
> Brian Ackermann
>