Deploying to http://localhost/ReportServer
Deploying data source '/Report Project1/cnt_SDS_REQUEST'.
The Report Server Web Service is unable to access secure information in the report server. Please verify that the WebServiceAccount is specified correctly in the report server config file.
Are you reusing an existing report server database?You get this error when the report server does not have access to the symmetric key that we use to protect sensitive data in the report server.
After a default installation, you should have access. If you chose to "install but not configure", then sometimes you need to manually restart the report server windows service for the initialization to occur.
If you are reusing an existing report server database, or are deploying in a scale-out configuration, you want to do use the report server configuration tool to initialize the report server. To do this, connect to a report server that is already initialized, go to the Initialization pane of the reporting services configuration tool, select the non-initialized instance, and press Initialize.
If you are reusing an exisitng report server database, but do not have another report server that is already initialized (it was uninstalled, you're restoring from backup, etc.), you will need to use the backup of your symmetric key (restore on the the Encryption Keys tab in the reporting servcies configuration tool).
If you don't have backed up symmetric key you'll need to delete encrypted content. Then you your report server should initialize itself after you restart your rpeort server windows service.
Hope that's simple enough :-).
-Lukasz|||I have just installed the lastest version of "Microsoft SQL Server 2005 CTP" and anytime I try to reach the ReportServer website, I get the following error message:
Reporting Services Error
The Report Server Web Service is unable to access secure information in the report server. Please verify that the WebServiceAccount is specified correctly in the report server config file. (rsAccessDeniedToSecureData) Get Online Help|||Solution to this problem is 1) Open Configure Report Server Tool
2) Update 'Web Service Identity' tab to reflect Asp .Net account on the machine.
For Eg. machineName\ASPNET
3) Click Apply Button, This will update WebServiceAccount tag in your report server configuration file 'rsreportserver.config'.
Hope this helps.
Thanks,|||how do you delete it by command line? Do you type it at the "run" line?|||
There is no command line for this functionality. We provide a WMI interface you can call directly to perform the same actions as are undertaken by the configuraiton tool. You can find the reference to the WMI methods here:
http://msdn2.microsoft.com/en-us/library/ms152836(en-US,SQL.90).aspx
-Lukasz
This posting is provided "AS IS" with no warranties, and confers no rights.
When I try to update the Web Service Identity field, it is greyed out and does not allow updates. Currently set to "NT Authority\Network Service"
|||I am in the same situation as well. I'm not allowed to change the WebServiceAccount through the interface, it's disabled. Also when I change it manually through the rsreportserver.config file to something other than it's current setting, the "Web Service Identity" won't initialize until I change it back to 'NT Authority\NetworkService'. I've removed the Encryption Keys even though there shouldn't be any yet as it's a fresh install of Reporting Services.
When I attempt to deploy a Report to the Report Server, I get the following error:
"The Report Server Web Service is unable to access information in the report server. Please verify that the WebServiceAccount is specified correctly in the report server config file."
What are the next several items we should check?
|||Hi,
What OS are you on?
If you're using RS on windows XP the identity that the Report server web service runs as is the identity of ASP.Net as set in ProcessModel element in the machine.config file. If you change it there, you should be able to click the apply button in the configuration tool. (This also applies to Windows 2000 Server)
If you're on Windows Windows Server 2003, you can create a new application pool with the new identity you want. Use the "New..." button on the web service identity tab to create it.
The WebServiceAccount property in the rsreportserver.config file does not actually set the web service to run as that account. Rather it needs to contain the name of the account the web service is configured to run as, if this identity is different from ASP.Net machine account on XP, W2K, or Network Service on W2K3.
Hope that helps,
-Lukasz
|||I found the issue(s) First off, there were 2 application pools created by our Network Admin that were both configured for the same virtual Directory. This was causing me issues with the deploying issue. Second, They were both configured for either LocalSystem or NetworkService which would always tell me that I didn't have access to execute them. Once I stopped one of the 2 application pools and ensured that the Web service Identity matched the application pools security that was still running, then I could both deploy and execute. Thanks for the direction.|||
Hi - I am still having issues deploying.
WinXP
SQL2005
IIS5
The Report Server Web Service is unable to access secure information in the report server. Please verify that the WebServiceAccount is specified correctly in the report server config file. (rsAccessDeniedToSecureData) Get Online Help
Issues with both reportserver and reportmanager.
Any ideas?
thanks.
vani
|||
This is a different issue:
The Report Server Web Service is unable to access secure information in the report server. Please verify that the WebServiceAccount is specified correctly in the report server config file. (rsAccessDeniedToSecureData
This error means the web service account as specified in the (for Windows XP or Windows 2000) Machine.config file in the <ProcessModel> element is not the same as the account specified in the <WebServiceAccount> element in the rsreportserver.config file. If the account specified by the <ProcessModel> is the ASP.NET account, then the value of <WebServiceAccount> can be blank. If it is something else, then you can either use the reporting services configuration tool to set the web service identity, or you can manually edit the <WebServiceAccount> element in the rsreportserver.config file. The account name must be in domain\alias format.
Just for completeness, on Windows Server 2003 and Vista, the web service identity depends on the application pool identity that is configured for the report server virtual directory. The default application pool identity is Network Service. In this case the <WebServiceAccount> element can be blank. If the application pool identity is another account, you'll need to ensure the WebServiceAccount element is set to that identity.
Hope that helps,
-Lukasz
|||I have changed this in reportserver's rsreportserver file to reflect
<WebServiceAccount><machine_name>\ASPNET</WebServiceAccount>
another confusing part - looks like we cannot use localhost but rather need to use the computer_name to run reports?
Also - being new to 2.0 framework - for some reason it seems to be adding the port number to run file like -http://localhost:2794/ReportServer/Pages/ReportViewer.aspx
Thanks.
Vani
|||The port number is determined by the website you chose in IIS. If you're not using the default web site, or have customized it to run on a different port, you need to specify the port explicitly.
-Lukasz
|||
Dear Lukasz,
your post was very helpfull, but I've a very strange bug. If I try to open a report all work fine. But if I click on a record (that should open a new sub-report) I've this: Not sufficient rights for the NT Authority\NetworkService account to complete this operation
If I try to do the same thing using then Report Builder all work fine.
What about?
Thanks in advance
No comments:
Post a Comment