October 3, 2009 at 7:25 am
Hello All,
I'm receiving the following error when trying to select some data from two databases on the same SQL 2005 instance:
"An error occurred when the report was run. The details are as follows:
The server principal "NT AUTHORITY\SYSTEM" is not able to access the database "Security_Reporting" under the current security context."
Error Number: -2147467259
Source: Microsoft OLE DB Provider for SQL Server
Native Error: 916
The NT AUTHORITY\SYSTEM account has datareader access (role) in both databases.
Any ideas on this error? I've done the basic Google and some other research but nothing so far.
Thanks in advance for your help.
Ronnie
October 4, 2009 at 1:17 pm
Ronnie Jones (10/3/2009)
Hello All,I'm receiving the following error when trying to select some data from two databases on the same SQL 2005 instance:
"An error occurred when the report was run. The details are as follows:
The server principal "NT AUTHORITY\SYSTEM" is not able to access the database "Security_Reporting" under the current security context."
Error Number: -2147467259
Source: Microsoft OLE DB Provider for SQL Server
Native Error: 916
The NT AUTHORITY\SYSTEM account has datareader access (role) in both databases.
Any ideas on this error? I've done the basic Google and some other research but nothing so far.
Thanks in advance for your help.
Ronnie
In SQL Server 2005 NT Authority is used by the Asp.net runtime and that is what executes your reports so making it a datareader in the datasource database is not practical because SSRS is rejecting it as not having enough permission.
The problem is SSRS is implicitly rejecting it self because it is Asp.net dependent in IIS, giving it more permissions is not a risk because what you do in report manager is dependent on permissions defined in report manager for the user.
Kind regards,
Gift Peddie
October 19, 2009 at 9:39 am
Sorry for the slow reply on this but I wanted to provide a status on this issue. I know that I from my own experience, I hate when I go to a forum, find the exact issue but the originator never update the post as to what his solution was if any...
My issue turned out to be a SCCM (System Center Configuration Manager) issue.
SCCM uses SQL 2005 on the back end and store the majority of its data in a DB named SMS and is usually where most of the the SCCM queries are getting data from.
We received a request to create a SCCM report which basically is a SQL query create within the SCCM app which in most cases, would pull data from the SMS DB. In this case, the query that was written needed to pull data not only from the SMS DB but also from another DB in that same instance.
I could successfully run the query within SQL Management Studio using the same SQL statement and it worked perfectly. But it would not run using the front end report tools within SCCM. There appeared to be an issue/bug with SCCM's abilty to retrieve data across multiple DB's. SQL wasn't the problem this time.
As a workaround, we used SSRS, which we also have installed on that specific server, to render the report that we being requested.
That's was the outcome of this issue.
Thanks to all who offered input in affort to help resolve my issue.
Ronnie
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply