Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
Joshrinn
Posting Yak Master
118 Posts |
Posted - 2012-06-18 : 12:30:47
|
| An error has occured during report processing(rsprocessingaborted)Cannot create a connection to 'datasource'.(rserroropeningconnection)For more information about this errr navigate to report server on the local server machine or enable remote errors. I got this error message. While running my reports individually it works which is why I deployed these. Now when I try to open it on the report server it doesn't open and gives me errors. How do I fix this? |
|
|
visakh16
Very Important crosS Applying yaK Herder
52326 Posts |
Posted - 2012-06-18 : 12:36:29
|
| have you given correct credentials for datasource after deploying to server?------------------------------------------------------------------------------------------------------SQL Server MVPhttp://visakhm.blogspot.com/ |
 |
|
|
Joshrinn
Posting Yak Master
118 Posts |
Posted - 2012-06-18 : 12:41:28
|
| No how do I do that. I just pressed the deploy button and checked it in the target Url and this is what I got |
 |
|
|
Joshrinn
Posting Yak Master
118 Posts |
Posted - 2012-06-19 : 10:04:30
|
| I tried checking on the report manager and it gives me the same error message. On the report manager I went inside the folder that has my data sources. I tried setting CONNECT USING:Windows integrated security and pressed test connection it displayed me the following error :Login Failed fr user'NT AUTHORITY\ANONYMOUS LOGON'. Due you think I do not have enough permissions? Also when I press subscribe on the rdl files it displays 'subscriptions cannot be created because the credentials used to run the report are not stored, or if a linked report, the link is no longer valid'. Your help will be highly appreciated |
 |
|
|
visakh16
Very Important crosS Applying yaK Herder
52326 Posts |
Posted - 2012-06-19 : 14:08:45
|
| I think reason is because reporting service is using default nt service account. try creating a new proxy account and configure reporting service to use it instead------------------------------------------------------------------------------------------------------SQL Server MVPhttp://visakhm.blogspot.com/ |
 |
|
|
|
|
|