Hi, I realy don't know what happened. But from this morning I receive logon
failures on my datasourse.
I use NTLM security but receive following error when opening a report:
An error has occurred during report processing. (rsProcessingAborted) Get
Online Help
Cannot create a connection to data source 'transportnet'.
(rsErrorOpeningConnection) Get Online Help
Cannot open database "transportnet" requested by the login. The login
failed. Login failed for user 'mydomain\SERVER$'.
The report server is configured for forms authentication. The datasource is
connecting to a sql server on another machine but in the same domain.
When I use the sql security (sa account) everything is working fine.
What could be the problem?
Thanks
BartHello Bart,
I understand that you could not use the server credential to connect to the datasource you use in the
report. If I misunderstood your concern, please feel free to let me know.
I would like to suggest you check the credential in the remote sql server whether it has the proper
permission or not first.
Also, please let me know whether you could use a UDL file to connect to the SQL server.
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||Hi Wie,
Thats correct.
Via an udl file is no problem.
What found strange is the account Server$. The server that is performing the
request is indeed called 'SERVER'. Could it be that this is the account for
the 'named pipes'? or something.
Thanks Bart
"Wei Lu [MSFT]" wrote:
> Hello Bart,
> I understand that you could not use the server credential to connect to the datasource you use in the
> report. If I misunderstood your concern, please feel free to let me know.
> I would like to suggest you check the credential in the remote sql server whether it has the proper
> permission or not first.
> Also, please let me know whether you could use a UDL file to connect to the SQL server.
> Sincerely,
> Wei Lu
> Microsoft Online Community Support
> ==================================================> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ==================================================> This posting is provided "AS IS" with no warranties, and confers no rights.
>|||Hello Bart,
It seems that your application pool of reporting services is using a local system or local service
account. Thus, it will use the machine account to connect to the remote database.
Please use the Network Service for the application pool identity and make sure it has proper
permission in the remote database.
Otherwise, you could use a domain account as the identity.
Hope this helps.
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||Hi Wei,
I already tried that, but just the same error.
What else?
Thanks
Bart
"Wei Lu [MSFT]" wrote:
> Hello Bart,
> It seems that your application pool of reporting services is using a local system or local service
> account. Thus, it will use the machine account to connect to the remote database.
> Please use the Network Service for the application pool identity and make sure it has proper
> permission in the remote database.
> Otherwise, you could use a domain account as the identity.
> Hope this helps.
> Sincerely,
> Wei Lu
> Microsoft Online Community Support
> ==================================================> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ==================================================> This posting is provided "AS IS" with no warranties, and confers no rights.
>|||Hello Bart,
How you configure the datasource? If you use the domain account as the identity of the application
pool, did you still get the same error message state that you could not open the database with login
domain\server$ ?
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||Hi ,
How is everything going? Please feel free to let me know if you need any
assistance.
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||Hello Wei,
I changed the application pool identity with the administrator account of
the domain, but the same error.
What else can I try?
Bart
"Wei Lu [MSFT]" wrote:
> Hello Bart,
> How you configure the datasource? If you use the domain account as the identity of the application
> pool, did you still get the same error message state that you could not open the database with login
> domain\server$ ?
> Sincerely,
> Wei Lu
> Microsoft Online Community Support
> ==================================================> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ==================================================> This posting is provided "AS IS" with no warranties, and confers no rights.
>|||Hello bart,
I would like to know the following things:
1. What's the datasource authentication mode you use? Do you use the
Windows Integrated Security?
2. What's the directory security setting for the Reports and ReportServer
virtual directories? Please do not enable anonymouse access and do enable
the Integrated Windows Authentication.
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||Hi Wei,
1. NTLM security
2. I use forms authentication, so I had to enable anonymouse access, but
this was never a problem.
"Wei Lu [MSFT]" wrote:
> Hello bart,
> I would like to know the following things:
> 1. What's the datasource authentication mode you use? Do you use the
> Windows Integrated Security?
> 2. What's the directory security setting for the Reports and ReportServer
> virtual directories? Please do not enable anonymouse access and do enable
> the Integrated Windows Authentication.
> Sincerely,
> Wei Lu
> Microsoft Online Community Support
> ==================================================> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ==================================================> This posting is provided "AS IS" with no warranties, and confers no rights.
>|||Hello Bart,
Since you are using the Form Authentication, by default, form
authentication will use the local Network Service account to access the
datasource. So when you set the datasource to use the windows integrated
authentication mode, you will use the Network Service to access the remote
datasource, that pass the Server$ account to the remote server.
To resolve this issue, since you are using the Form Authentication, I
suggest you create a new SQL Login in the remote server and use this SQL
Login in the data source to access the remote server. You don't have to use
the Windows Integrated Authentication in this scenario.
Hope this helps.
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||Hi ,
How is everything going? Please feel free to let me know if you need any
assistance.
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||Hi Wei,
This is not an option because I use the logged in user for filtering data in
some views
Bart
"Wei Lu [MSFT]" wrote:
> Hello Bart,
> Since you are using the Form Authentication, by default, form
> authentication will use the local Network Service account to access the
> datasource. So when you set the datasource to use the windows integrated
> authentication mode, you will use the Network Service to access the remote
> datasource, that pass the Server$ account to the remote server.
> To resolve this issue, since you are using the Form Authentication, I
> suggest you create a new SQL Login in the remote server and use this SQL
> Login in the data source to access the remote server. You don't have to use
> the Windows Integrated Authentication in this scenario.
> Hope this helps.
> Sincerely,
> Wei Lu
> Microsoft Online Community Support
> ==================================================> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ==================================================> This posting is provided "AS IS" with no warranties, and confers no rights.
>|||Hello Bart,
Since you are using the Form Authentication, when you use the windows
integrated authentication mode, it will use the working process account to
connect to the windows resources.
So I am not sure how you are using the login user to filter the data in the
view. I assume you are using the filter in the report directly. If I am
offset, please feel free to let me know.
In this scenario, you still you could use the SQL Login because Reporting
Services is using the SQL Login to access the datasource to get the data
and you could filter as the Form User in the reporting services.
If you are using stored procedure to filter the data in the view by the
login user, I assume you add some parameters in the stored procedure to
filter the data. You still could use the stored procedure to filter the
data when you use the SQL Login and pass the parameter to it.
Please let me know how you use the login user to filter the data in the
view so that I can provide further suggestions. Thank you!
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||Hi Wei,
You are 100% correct.
I use the User.UserID from the default properties in reporting server to
filter data based on the user logged in.
I was misleaded by a report that was running before on an internal server
that used ntlm security.
I changed it to use the user.userid instead of the sql suser_name() function
and it worked again.
Thanks a lot for you help
Bart
"Wei Lu [MSFT]" wrote:
> Hello Bart,
> Since you are using the Form Authentication, when you use the windows
> integrated authentication mode, it will use the working process account to
> connect to the windows resources.
> So I am not sure how you are using the login user to filter the data in the
> view. I assume you are using the filter in the report directly. If I am
> offset, please feel free to let me know.
> In this scenario, you still you could use the SQL Login because Reporting
> Services is using the SQL Login to access the datasource to get the data
> and you could filter as the Form User in the reporting services.
> If you are using stored procedure to filter the data in the view by the
> login user, I assume you add some parameters in the stored procedure to
> filter the data. You still could use the stored procedure to filter the
> data when you use the SQL Login and pass the parameter to it.
> Please let me know how you use the login user to filter the data in the
> view so that I can provide further suggestions. Thank you!
> Sincerely,
> Wei Lu
> Microsoft Online Community Support
> ==================================================> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ==================================================> This posting is provided "AS IS" with no warranties, and confers no rights.
>|||Hello bart,
Thanks for the update and if you have any question, please feel free to let
me know.
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================This posting is provided "AS IS" with no warranties, and confers no rights.
