Showing posts with label service. Show all posts
Showing posts with label service. Show all posts

Monday, March 26, 2012

Problem with ASP and SQL ODBC connection

Hi everyone, I need your expert advice. I have a w2k AD service with mssql on
it. and I setup another w2k server with IIS on it as webserver. my website
works on NT servers, but when I moved the website to the w2k server, it
doesn't work. It saids:
Error Type:
Microsoft OLE DB Provider for ODBC Drivers (0x80040E4D)
[Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user 'NT
AUTHORITY\ANONYMOUS LOGON'.
/media/IIS_Gen_3.0_Recordset.js, line 366
My problem not stops here, as my website created by a program, therefore, I
don't know how to change the open connection statement. so therefore, I can
only find a way to overcome this user account login problem.
=?Utf-8?B?UGF0cmljayBUYW5n?= <PatrickTang@.discussions.microsoft.com>
wrote in news:E04EF7D8-542E-455B-A5C3-D134A92653F2@.microsoft.com:
I'm up against a similar problem, but having checked out KB 247931 I'm
still baffled.
AFAICS, the browser takes the authentication happily, but sql 2k gives me
either a '\' as the failed login or the same as below.
Yet the users are all members of a domain group that has access set
up....

> Hi everyone, I need your expert advice. I have a w2k AD service with
> mssql on it. and I setup another w2k server with IIS on it as
> webserver. my website works on NT servers, but when I moved the
> website to the w2k server, it doesn't work. It saids:
> Error Type:
> Microsoft OLE DB Provider for ODBC Drivers (0x80040E4D)
> [Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user
> 'NT AUTHORITY\ANONYMOUS LOGON'.
> /media/IIS_Gen_3.0_Recordset.js, line 366
> My problem not stops here, as my website created by a program,
> therefore, I don't know how to change the open connection statement.
> so therefore, I can only find a way to overcome this user account
> login problem.
>
sql

Problem with ASP & SQL ODBC connection

Hi everyone, I need your expert advice. I have a w2k AD service with mssql on
it. and I setup another w2k server with IIS on it as webserver. my website
works on NT servers, but when I moved the website to the w2k server, it
doesn't work. It saids:
Error Type:
Microsoft OLE DB Provider for ODBC Drivers (0x80040E4D)
[Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user 'NT
AUTHORITY\ANONYMOUS LOGON'.
/media/IIS_Gen_3.0_Recordset.js, line 366
My problem not stops here, as my website created by a program, therefore, I
don't know how to change the open connection statement. so therefore, I can
only find a way to overcome this user account login problem.
Hi
Since it is and IIS site, the local NT IIS account, IUSR_<machinename>, will
be the user coming through on the connection. You need to give it rights in
you DB.
The best way to do this is to create a domain account for IIS, give it
rights in your DB and then re-configure IIS to use that for anonymous access.
There are security implications, so make sure that you give the user the
least rights at domain and DB level.
Regards
Mike
"Patrick Tang" wrote:

> Hi everyone, I need your expert advice. I have a w2k AD service with mssql on
> it. and I setup another w2k server with IIS on it as webserver. my website
> works on NT servers, but when I moved the website to the w2k server, it
> doesn't work. It saids:
> Error Type:
> Microsoft OLE DB Provider for ODBC Drivers (0x80040E4D)
> [Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user 'NT
> AUTHORITY\ANONYMOUS LOGON'.
> /media/IIS_Gen_3.0_Recordset.js, line 366
> My problem not stops here, as my website created by a program, therefore, I
> don't know how to change the open connection statement. so therefore, I can
> only find a way to overcome this user account login problem.
>

Problem with Analysis Server

I just installed 2005 and have an Enterprise Editition instance on my local machine. My SSAS service appears to be working properly in Services. However, whenever I try to deploy a cube (simple one from tutorial) or try to connect from Management Console, I get rejected. The error message is:

No connection could be made because the target machine actively refused it (System).

I've tried about everything I can think of and can't get past this. Any guidance would be greatly appreciated.

Rod, can you enable shared memory and try again? This should solve the problem.

Thanks,
Sam Lester (MSFT)

|||How do you "enable" shared memory?sql

Problem with Analysis Server

I just installed 2005 and have an Enterprise Editition instance on my local machine. My SSAS service appears to be working properly in Services. However, whenever I try to deploy a cube (simple one from tutorial) or try to connect from Management Console, I get rejected. The error message is:

No connection could be made because the target machine actively refused it (System).

I've tried about everything I can think of and can't get past this. Any guidance would be greatly appreciated.

Rod, can you enable shared memory and try again? This should solve the problem.

Thanks,
Sam Lester (MSFT)

|||How do you "enable" shared memory?

Problem with Analysis Server

I just installed 2005 and have an Enterprise Editition instance on my local machine. My SSAS service appears to be working properly in Services. However, whenever I try to deploy a cube (simple one from tutorial) or try to connect from Management Console, I get rejected. The error message is:

No connection could be made because the target machine actively refused it (System).

I've tried about everything I can think of and can't get past this. Any guidance would be greatly appreciated.

Rod, can you enable shared memory and try again? This should solve the problem.

Thanks,
Sam Lester (MSFT)

|||How do you "enable" shared memory?

Friday, March 23, 2012

Problem with a Web Service Task that uses a digital certificate

Hi every body... I will thank u the help that you could bring me...

This is my problem:

I am using a Web Service Task in Integration Services for access a Web Method, this method is not mine, it is a method provided for another company. This Web Method is published in a VPN (Virtual Private Network) and it is in a secured channel (https).

The properties of the Connection Manager that the Web Service Task uses are ok. The Server URL is the address of the asmx and the client certificate is the correct. In fact when I press Test Connection, the message Test Connection Succeed is shown. If I change the certificate, a connection error occurs (403 Forbidden), this means that the client certificate and the address is ok. I addition, I use this certificate to access another methods published by the same company in a Visual basic application (with WSE) and I don′t have problems.

When I execute the DTSX the error "403 Forbidden" occurs and I can't execute the method. I executed the DTS in the VS2005, SQL IDE and in a batch file (.bat) too, and the same error happened.

If I use the File Monitor tool (from SysInternal, that now belongs to Microsoft) I can see that when I test the connection (in the Connection Manager used by the Web Service Task), the process accesses the certificate's private key located in the RSA folder of my certificates. But when I run the DTSX (no matters which way), it never reads the private key, it only accesses the certificate repository.

I saw that the code of the DTSX includes the certificate in Base64, but I am thinking that this code doesn't include the private key (I don't know if it would have to do it)...

Well, the fact is that I can′t use this Web Service task. I am suspecting that is a bug of the Integration Service

Thanks for the help that could bring me...

Can you tell us a bit more about http connection manager's credentials? what user credentials are you using to access the web service?

|||

Sure ...

The properties of the connection manager (seen in the edition window) are:

Server URL: https://<server url>/<folder name>/webservice.asmx. Where <server url > is the direction of the server, <folder name> is the folder name where the webservice is and finally the webservice.asmx. The direction is ok because I am using another .asmx in the same direction with a .net windows service application and all works fine with my certificate.

Another important thing is that I don't need to use a special network user, or account, to access the web service from this .net windows service. In fact the windows service runs with the Local System Account. For that, I installed the certificate (with it's root certificate) in the Local Computer repository. For my tests I installed the certificate in the Current User repository too.

In the checkbox "Use Credentials" I have tried nothing and my network user, but the same error raises with both.

In the "Client Certificate" I chose the certificate.

In the Proxy settings (the another tab) I don't have to put information because the connection is not made between a proxy.

As you can see, the problem is very strange, because I can access the Web Service from the Internet Explorer and .Net applications.

Thanks for your time and help...

Tuesday, March 20, 2012

Problem while using stored procedures with temporary tables in dataset

I am trying to generate a report using SQL Server Reporting Service. The dataset is passed the results from a stored procedure. The stored proc contains a temporary table. On exceuting of proc, it fetches the result but when I try to save dataset I get following error message

Invalid object name '#AdditionalParams'. (.Net SqlClient Data Provider)

And no colums are returned in the data set created.

Any help on this would be appreciated.

Thanks in advance

If possible, try using a table variable instead, or create a physical table first.

http://www.odetocode.com/Articles/365.aspx

Here are some workarounds for temp tables.

http://www.sql-server-performance.com/rd_temp_tables.asp

If you have to, try using set fmtonly off in stored procedure.

http://www.simple-talk.com/sql/database-administration/creating-csv-files-using-bcp-and-stored-procedures/

cheers,

Andrew

|||

I exceuted the proc as stored procedure. And latter I added a new field to same dataset, as it didnt had any field because it had thrown error. I refreshed the datset and I got all the dataset fields although initally it showed error and it worked.

But their is essentially problem the way datset are handled in reporting service.

Thanks

Problem while using stored procedures with temporary tables in dataset

I am trying to generate a report using SQL Server Reporting Service. The dataset is passed the results from a stored procedure. The stored proc contains a temporary table. On exceuting of proc, it fetches the result but when I try to save dataset I get following error message

Invalid object name '#AdditionalParams'. (.Net SqlClient Data Provider)

And no colums are returned in the data set created.

Any help on this would be appreciated.

Thanks in advance

If possible, try using a table variable instead, or create a physical table first.

http://www.odetocode.com/Articles/365.aspx

Here are some workarounds for temp tables.

http://www.sql-server-performance.com/rd_temp_tables.asp

If you have to, try using set fmtonly off in stored procedure.

http://www.simple-talk.com/sql/database-administration/creating-csv-files-using-bcp-and-stored-procedures/

cheers,

Andrew

|||

I exceuted the proc as stored procedure. And latter I added a new field to same dataset, as it didnt had any field because it had thrown error. I refreshed the datset and I got all the dataset fields although initally it showed error and it worked.

But their is essentially problem the way datset are handled in reporting service.

Thanks

Problem while navigating Report on server

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

Monday, March 12, 2012

Problem while deploying Report on server

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

Problem while deploying Report on server

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

Problem while deploying Report on server

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

Problem while deploying Report on server

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

Problem while deploying Report on server

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

Problem while deploying Report on server

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

Problem while deploying Report on server

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

Problem while deploying Report on server

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

problem when using reporting service

Dear all,
i have installed reporting service a few days ago, but i encounter the
following problems,
my report server is in another machine(rather than localhost, like
most examples on the web), after teh installation, i have made rdl,
and deploy to the server, everything goes fine until i type
http://xxx.xxx.xxx.xxx/Reports to access the report. i can browse the
directories, but dead link shown once i click on teh report.
strange thing is when i type http://xxx.xxx.xxx.xxx/ReportServer/, i
can see the report generated on teh screen. could anyone suggest ways
to solve it?
another problem is i tried to use render() to generate report in my
web site (that is localhost) using the server (xxx.xxx.xxx.xxx), but
error keep sending to me ( The request failed with HTTP status 401:
Access Denied.
), i have added a web reference already, it wont work even i type
http://xxx.xxx.xxx.xxx/retest2/.... in the full path
thank you for helping in advancecontrol your .config files on your server (specially under the reportmanager
folder)
in the .config file, you have the URL of the ReportServer http virtual
folder.
Make sure this parameter = http://xxx.xxx.xxx.xxx/ReportServer/
"jasonymk" <jasonymk@.sinaman.com> a écrit dans le message de news:
a4075300.0409172006.526eb426@.posting.google.com...
> Dear all,
> i have installed reporting service a few days ago, but i encounter the
> following problems,
> my report server is in another machine(rather than localhost, like
> most examples on the web), after teh installation, i have made rdl,
> and deploy to the server, everything goes fine until i type
> http://xxx.xxx.xxx.xxx/Reports to access the report. i can browse the
> directories, but dead link shown once i click on teh report.
> strange thing is when i type http://xxx.xxx.xxx.xxx/ReportServer/, i
> can see the report generated on teh screen. could anyone suggest ways
> to solve it?
> another problem is i tried to use render() to generate report in my
> web site (that is localhost) using the server (xxx.xxx.xxx.xxx), but
> error keep sending to me ( The request failed with HTTP status 401:
> Access Denied.
> ), i have added a web reference already, it wont work even i type
> http://xxx.xxx.xxx.xxx/retest2/.... in the full path
> thank you for helping in advance|||For the second problem set your WS proxy to DefaultCredentials.
--
Hope this helps.
----
Teo Lachev, MCSD, MCT
Author: "Microsoft Reporting Services in Action"
Publisher website: http://www.manning.com/lachev
Buy it from Amazon.com: http://shrinkster.com/eq
Home page and blog: http://www.prologika.com/
----
"Jéjé" <willgart@.BBBhotmailAAA.com> wrote in message
news:%23dmIqeanEHA.1800@.TK2MSFTNGP15.phx.gbl...
> control your .config files on your server (specially under the
reportmanager
> folder)
> in the .config file, you have the URL of the ReportServer http virtual
> folder.
> Make sure this parameter = http://xxx.xxx.xxx.xxx/ReportServer/
>
> "jasonymk" <jasonymk@.sinaman.com> a écrit dans le message de news:
> a4075300.0409172006.526eb426@.posting.google.com...
> > Dear all,
> >
> > i have installed reporting service a few days ago, but i encounter the
> > following problems,
> >
> > my report server is in another machine(rather than localhost, like
> > most examples on the web), after teh installation, i have made rdl,
> > and deploy to the server, everything goes fine until i type
> > http://xxx.xxx.xxx.xxx/Reports to access the report. i can browse the
> > directories, but dead link shown once i click on teh report.
> >
> > strange thing is when i type http://xxx.xxx.xxx.xxx/ReportServer/, i
> > can see the report generated on teh screen. could anyone suggest ways
> > to solve it?
> >
> > another problem is i tried to use render() to generate report in my
> > web site (that is localhost) using the server (xxx.xxx.xxx.xxx), but
> > error keep sending to me ( The request failed with HTTP status 401:
> > Access Denied.
> > ), i have added a web reference already, it wont work even i type
> > http://xxx.xxx.xxx.xxx/retest2/.... in the full path
> >
> > thank you for helping in advance
>|||thank you so much for the advice, i will try that later on.
if you have time ,would you see the wuestion i post entitled " 3(should be
2) different conputers problem)?
thanks so much
"Jéjé" wrote:
> control your .config files on your server (specially under the reportmanager
> folder)
> in the .config file, you have the URL of the ReportServer http virtual
> folder.
> Make sure this parameter = http://xxx.xxx.xxx.xxx/ReportServer/
>
> "jasonymk" <jasonymk@.sinaman.com> a écrit dans le message de news:
> a4075300.0409172006.526eb426@.posting.google.com...
> > Dear all,
> >
> > i have installed reporting service a few days ago, but i encounter the
> > following problems,
> >
> > my report server is in another machine(rather than localhost, like
> > most examples on the web), after teh installation, i have made rdl,
> > and deploy to the server, everything goes fine until i type
> > http://xxx.xxx.xxx.xxx/Reports to access the report. i can browse the
> > directories, but dead link shown once i click on teh report.
> >
> > strange thing is when i type http://xxx.xxx.xxx.xxx/ReportServer/, i
> > can see the report generated on teh screen. could anyone suggest ways
> > to solve it?
> >
> > another problem is i tried to use render() to generate report in my
> > web site (that is localhost) using the server (xxx.xxx.xxx.xxx), but
> > error keep sending to me ( The request failed with HTTP status 401:
> > Access Denied.
> > ), i have added a web reference already, it wont work even i type
> > http://xxx.xxx.xxx.xxx/retest2/.... in the full path
> >
> > thank you for helping in advance
>
>|||Thanks Teo,
i think i have done so by follow:
Dim rs As New reportservice.ReportingService
rs.Credentials = System.Net.CredentialCache.DefaultCredentials
' Render the report as an HTML4.0 fragment using the Web service
Dim results As [Byte]()
results =rs.Render("http://xxx.xxx.xxx.xxx/ReportServer/retest2/testreport",
"HTML4.0", Nothing, Nothing, Nothing, Nothing, Nothing, Nothing, Nothing,
Nothing, Nothing, Nothing)
so...i think i have to check he computer setting before i move on...
please have a look to the topic (3 different computers problem)
thanks in advance.
"Teo Lachev" wrote:
> For the second problem set your WS proxy to DefaultCredentials.
> --
> Hope this helps.
> ----
> Teo Lachev, MCSD, MCT
> Author: "Microsoft Reporting Services in Action"
> Publisher website: http://www.manning.com/lachev
> Buy it from Amazon.com: http://shrinkster.com/eq
> Home page and blog: http://www.prologika.com/
> ----
> "Jéjé" <willgart@.BBBhotmailAAA.com> wrote in message
> news:%23dmIqeanEHA.1800@.TK2MSFTNGP15.phx.gbl...
> > control your .config files on your server (specially under the
> reportmanager
> > folder)
> > in the .config file, you have the URL of the ReportServer http virtual
> > folder.
> > Make sure this parameter = http://xxx.xxx.xxx.xxx/ReportServer/
> >
> >
> > "jasonymk" <jasonymk@.sinaman.com> a écrit dans le message de news:
> > a4075300.0409172006.526eb426@.posting.google.com...
> > > Dear all,
> > >
> > > i have installed reporting service a few days ago, but i encounter the
> > > following problems,
> > >
> > > my report server is in another machine(rather than localhost, like
> > > most examples on the web), after teh installation, i have made rdl,
> > > and deploy to the server, everything goes fine until i type
> > > http://xxx.xxx.xxx.xxx/Reports to access the report. i can browse the
> > > directories, but dead link shown once i click on teh report.
> > >
> > > strange thing is when i type http://xxx.xxx.xxx.xxx/ReportServer/, i
> > > can see the report generated on teh screen. could anyone suggest ways
> > > to solve it?
> > >
> > > another problem is i tried to use render() to generate report in my
> > > web site (that is localhost) using the server (xxx.xxx.xxx.xxx), but
> > > error keep sending to me ( The request failed with HTTP status 401:
> > > Access Denied.
> > > ), i have added a web reference already, it wont work even i type
> > > http://xxx.xxx.xxx.xxx/retest2/.... in the full path
> > >
> > > thank you for helping in advance
> >
> >
>
>

Friday, March 9, 2012

Problem when installing MS SQL Reporting Service

Hi,
I need help.
I am trying to install the Reporting Service.
When the screen was in "System Prerequisites Check", it tell me that
visual Studio.NET 2003 is not installed.
After clicking next in "System Prerequisites Check"
It jump to a page called "Welcome to ...SQL Reporting Service SETUP"
and then it automatically jump to a page called "Installing Reporting
Services"
But I haven't selected anything.
Then wait a few minutes, a general error message appears and and tell
me "... was failed to install Reporting Service" with the "Send Report"
and "Don't send" button.
Could anyone get the solution? Thank you very much.I am facing similar problem while installing Reporting Services.
At the "System Prerequisites Check" all checks are OK but at the
"Welcome to Ms SQL Server 2000 Reporting Services Setup" screen I
waited for 10-15 minutes for the NEXT button that never appeared.
Finally, a general error message appears and telling
me "... was failed to install Reporting Service" with the "Send Report"
and "Don't send" button.
Can someone help?|||I have resolved the problem by doing a windows update, shut down all
the active applications. Then proceed with the installation.
Your installer may be corrupted if this doesn't help.