Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion Groups
DB Engine
SQL ServerMSDESQL Server CE
Services
Analysis (Data Mining)Analysis (OLAP)DTSIntegration ServicesNotification ServicesReporting Services
Programming
CLRConnectivitySQLXML
Other Technologies
ClusteringEnglish QueryFull-Text SearchReplicationService Broker
General
Data WarehousingPerformanceSecuritySetupSQL Server ToolsOther SQL Server Topics
DirectoryUser Groups
Related Topics
MS AccessOther DB ProductsMS Server Products.NET DevelopmentVB DevelopmentJava DevelopmentMore Topics ...

SQL Server Forum / General / Security / July 2008

Tip: Looking for answers? Try searching our database.

Reporing service failure

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Puru - 12 May 2008 05:12 GMT
we have setup up reporting server and while configuring database
Database setup > domain account is provided

It fails here @ grant rights. with following error

------------------------------------------------------------------------------------------------
w3wp!library!c!5/12/2008-00:25:22:: e ERROR: Throwing
Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerDatabaseLogonFailedException:
The report server cannot open a connection to the report server database. The
logon failed., ;
Info:
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. (Exception from HRESULT: 0x80070569)
  at
System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32
errorCode, IntPtr errorInfo)
  at RSRemoteRpcClient.RemoteLogon.GetRemoteImpToken(String
pRPCEndpointName, Int32 type, Guid dataSourceId, String pUserName, String
pDomain, String pPassword)
  at
Microsoft.ReportingServices.Library.ConnectionConfig.GetImpersonationUser(String userName, String domain, String userPwd)
  --- End of inner exception stack trace ---
w3wp!webserver!a!5/12/2008-00:46:21:: i INFO: Reporting Web Server stoppe
------------------------------------------------------------------------------------------------------

Any help would be appreciated.

i also get following error in security log.

------------------------------------------------------------------------------------------------

Event Type:    Failure Audit
Event Source:    Security
Event Category:    Logon/Logoff
Event ID:    534
Date:        5/12/2008
Time:        4:10:20 AM
User:        NT AUTHORITY\SYSTEM
Computer:    FM1MESQUITE
Description:
Logon Failure:
    Reason:    The user has not been granted the requested
        logon type at this machine
    User Name:    sys_isppmsrs
    Domain:        ED
    Logon Type:    2
    Logon Process:    Advapi  
    Authentication Package:    Negotiate
    Workstation Name:    FM1MESQUITE
    Caller User Name:    sys_isppmsrs
    Caller Domain:    ED
    Caller Logon ID:    (0x0,0x841BB6A)
    Caller Process ID:    3872
    Transited Services:    -
    Source Network Address:    -
    Source Port:    -

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
__________________________________________________________________-

thank YOu in Advance
Charles Wang[MSFT] - 12 May 2008 12:26 GMT
Hi Puru,
I understand that when you tried to configure your database for your SQL
Server Reporting Services, you encountered the logon failure error.
If I have misunderstood, please let me know.

From the error message, it indicated that your SQL Server 2005 instance did
not accept your domain user account for login. However from the event error,
it was strange that the audit failure was for another user account NT
AUTHORITY\SYSTEM which was not your domain user account.

To isolate this issue more specifically, I recommend that you run SQL
Profiler to monitor your SQL Server instance:.
Open your SQL Profiler from Start->All Programs->Microsoft SQL Server
2005->Performance Tools->SQL Server Profiler, click File-> New Trace...,
connect to your SQL Server instance with a sysadmin account, then in the
Trace Properties window, switch to the Event Selection tab, check "Show all
events", check Security Audit->Audit Login Failed and click Run.

And then configure your SSRS databases via Reporting Services Configuration
Tools. I suppose that you originally configured your SSRS databases in
Reporting Services Configuration Tools with the following steps:
Selected Database Setup, clicked New... to create the ReportServer database
and ReportServerTempDB database, selected Credential Type as Windows
Credentials and then input the domain user account and password.
You can mail me (changliw_at_microsoft_dot_com) the trace file for further
research.

Also could you please check if the databases ReportServer and
ReportServerTempDB had been created in your SQL Server instance before this
error arised? If the databases had been created, I recommend that you check
if your Reporting Services's service account is Local System. If so and if
your Report Server is located on a different machine from your database
server, this issue may be related to your SSRS service account. By default,
Report Server will use SSRS service account to connect to the ReportServer
database, however at this time, the Windows authentication on SQL Server
will fail since Local System cannot be used as a network credential. In this
case, you can change your Reporting Services's service account to a domain
user account and manually assign it permissions in your SQL Server instance.
To check and change the service account, you can refer to the following
steps:
1. Click Start->Run..., type services.msc and click OK;
2. Double click the service SQL Server Reporting Services (INSTANCE NAME),
switch to the Log On tab and specify the domain user account as the logon
account.

If this issue persists, I recommend that you mail me the SSRS error logs
which are located in the folder %ProgramFiles%\Microsoft SQL
Server\MSSQL.x\Reporting Services\LogFiles. Also I appreciate if you could
send me some screenshots of your configurations via email.

Please feel free to let me know if you have any other questions or concerns.
Have a nice day!

Best regards,
Charles Wang
Microsoft Online Community 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.
====================================================
Signature

This posting is provided "AS IS" with no warranties, and confers no rights.

====================================================

> we have setup up reporting server and while configuring database
> Database setup > domain account is provided
[quoted text clipped - 66 lines]
>
> thank YOu in Advance
Puru - 13 May 2008 05:44 GMT
Hi Charles Wang

Thank you for replying to the post in news group.

Below is my respone.

Hi Puru,
I understand that when you tried to configure your database for your SQL
Server Reporting Services, you encountered the logon failure error.
If I have misunderstood, please let me know.

Yes you are right. it fails at grants right.

From the error message, it indicated that your SQL Server 2005 instance did
not accept your domain user account for login. However from the event error,
it was strange that the audit failure was for another user account NT
AUTHORITY\SYSTEM which was not your domain user account.

To isolate this issue more specifically, I recommend that you run SQL
Profiler to monitor your SQL Server instance:.
Open your SQL Profiler from Start->All Programs->Microsoft SQL Server
2005->Performance Tools->SQL Server Profiler, click File-> New Trace...,
connect to your SQL Server instance with a sysadmin account, then in the
Trace Properties window, switch to the Event Selection tab, check "Show all
events", check Security Audit->Audit Login Failed and click Run.

Pls find the attached trace log and SSRS log files.

And then configure your SSRS databases via Reporting Services Configuration
Tools. I suppose that you originally configured your SSRS databases in
Reporting Services Configuration Tools with the following steps:
Selected Database Setup, clicked New... to create the ReportServer database
and ReportServerTempDB database, selected Credential Type as Windows
Credentials and then input the domain user account and password.

Yes you are right. its was configured as mentioned above.The DB's are created.

You can mail me (changliw_at_microsoft_dot_com) the trace file for further
research.

Also could you please check if the databases ReportServer and
ReportServerTempDB had been created in your SQL Server instance before this
error arised? If the databases had been created, I recommend that you check
if your Reporting Services's service account is Local System. If so and if
your Report Server is located on a different machine from your database
server, this issue may be related to your SSRS service account. By default,
Report Server will use SSRS service account to connect to the ReportServer
database, however at this time, the Windows authentication on SQL Server
will fail since Local System cannot be used as a network credential. In this
case, you can change your Reporting Services's service account to a domain
user account and manually assign it permissions in your SQL Server instance.
To check and change the service account, you can refer to the following
steps:
1. Click Start->Run..., type services.msc and click OK;
2. Double click the service SQL Server Reporting Services (INSTANCE NAME),
switch to the Log On tab and specify the domain user account as the logon
account.

I have setup the account to use domain account and this still fails..

but in our pre-pord systesm we still use local account for servcie and its
been working fine.

If this issue persists, I recommend that you mail me the SSRS error logs
which are located in the folder %ProgramFiles%\Microsoft SQL
Server\MSSQL.x\Reporting Services\LogFiles. Also I appreciate if you could
send me some screenshots of your configurations via email.

pls find the attached logs files

Please feel free to let me know if you have any other questions or concerns.
Have a nice day!

> we have setup up reporting server and while configuring database
> Database setup > domain account is provided
[quoted text clipped - 61 lines]
>
> thank YOu in Advance
Charles Wang [MSFT] - 14 May 2008 09:44 GMT
Hi Puru,
Thank you for your response.

Just check with you whether you added the "Audit Login Failed" event in
your SQL Profiler trace. I did not find any login failure in the trace file.

Also I recommend that you try explicitly adding your domain user account as
a login to your SQL Server instance and assign it with db_owner role on
your ReportServer and ReportServerTempDB databases. You can refer to the
following steps:
1.    Logon your SQL Server instance from SSMS;
2.    Expand the Security folder under your server, expand the Logins folder.
3.    If the domain user account is not here, please right click the Logins
folder, click New Login..., input the Login name (ED\isppmsrs), select
Windows authentication, select "User Mapping" in the left column, check
ReportServer, check db_owner, check ReportServerTempDB, check db_owner and
then click OK.

After these steps, try configuring your Database Setup in your Reporting
Services Configuration Manager again.

Hope this helps.

Best regards,
Charles Wang
Microsoft Online Community Support

Best regards,
Charles Wang
Microsoft Online Community Support
=========================================================
Delighting our customers is our #1 priority. We welcome your
comments and suggestions about how we can improve the
support we provide to you. Please feel free to let my manager
know what you think of the level of service provided. You can
send feedback directly to my manager at: msdnmg@microsoft.com.
=========================================================
Signature

This posting is provided "AS IS" with no warranties, and confers no rights.

=========================================================
Jerry Chen - 23 Jul 2008 07:22 GMT
Hi Puru,

I have the exactly same issue here. at the end of the day, i found that you
need to make sure the domain user is in local administrators group. this is
another important step to fix this issue.

hope this helps.

cheers!
Jerry Chen

> Hi Puru,
> Thank you for your response.
[quoted text clipped - 35 lines]
> This posting is provided "AS IS" with no warranties, and confers no rights.
> =========================================================
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.