Showing posts with label source. Show all posts
Showing posts with label source. Show all posts

Monday, March 26, 2012

Problem with AS data source

I've successfully created a data source and reports against an Analysis
Services database.
The AS database is on the same machine as RS (let's call this Server
1).
I tried this against a second AS database (on Server 2), and it works
fine from Visual Studio, but when I deploy it to RS (on Server 1) and
try to run it, I get the error:
"...Cannot create a connection to data source 'DevServer'.
(rsErrorOpeningConnection)
A connection cannot be made. Ensure that the server is running.
Unable to read from the transport connection: An existing connection
was forcibly closed by the remote host."
I'm not doing anything complicated. It's just that the AS database is
on a different machine from the RS server. Shouldn't this work?
Ideas?
TIA,
JimHi Jim.
Could 'devserver' have firewall on for its network connection?
<jhcorey@.yahoo.com> wrote in message
news:1150819548.395205.74950@.r2g2000cwb.googlegroups.com...
> I've successfully created a data source and reports against an Analysis
> Services database.
> The AS database is on the same machine as RS (let's call this Server
> 1).
> I tried this against a second AS database (on Server 2), and it works
> fine from Visual Studio, but when I deploy it to RS (on Server 1) and
> try to run it, I get the error:
> "...Cannot create a connection to data source 'DevServer'.
> (rsErrorOpeningConnection)
> A connection cannot be made. Ensure that the server is running.
> Unable to read from the transport connection: An existing connection
> was forcibly closed by the remote host."
> I'm not doing anything complicated. It's just that the AS database is
> on a different machine from the RS server. Shouldn't this work?
> Ideas?
> TIA,
> Jim
>|||I just tried deploying everything to Server 2, and it works fine.
So my conclusion is that for a report that goes against an AS cube, RS
must be on the same machine as AS. But it would be great if I was
wrong.
Jim
Tim Dot NoSpam wrote:
> Hi Jim.
> Could 'devserver' have firewall on for its network connection?
> <jhcorey@.yahoo.com> wrote in message
> news:1150819548.395205.74950@.r2g2000cwb.googlegroups.com...
> > I've successfully created a data source and reports against an Analysis
> > Services database.
> > The AS database is on the same machine as RS (let's call this Server
> > 1).
> >
> > I tried this against a second AS database (on Server 2), and it works
> > fine from Visual Studio, but when I deploy it to RS (on Server 1) and
> > try to run it, I get the error:
> >
> > "...Cannot create a connection to data source 'DevServer'.
> > (rsErrorOpeningConnection)
> > A connection cannot be made. Ensure that the server is running.
> > Unable to read from the transport connection: An existing connection
> > was forcibly closed by the remote host."
> >
> > I'm not doing anything complicated. It's just that the AS database is
> > on a different machine from the RS server. Shouldn't this work?
> > Ideas?
> >
> > TIA,
> > Jim
> >|||It is great! <g>
I'm not a configuration wiz, but here are some things you could do until you
figure out how to get reporting services to correctly pass the user's
credentials to AS:
1) change the datasource in report manager for the OLAP conection to use a
domain user that has the necessary privileges on AS (preferrably a domain
account that's not an admin in AS).
Ideally, RS will pass the credentials of the user to AS during the
connection.
A good enterprise configuration for a smaller group could be to split sql
server, analysis services and reporting services across 3 boxes, preferrably
64bit.
<jhcorey@.yahoo.com> wrote in message
news:1150824174.761885.143160@.h76g2000cwa.googlegroups.com...
>I just tried deploying everything to Server 2, and it works fine.
> So my conclusion is that for a report that goes against an AS cube, RS
> must be on the same machine as AS. But it would be great if I was
> wrong.
> Jim
> Tim Dot NoSpam wrote:
>> Hi Jim.
>> Could 'devserver' have firewall on for its network connection?
>> <jhcorey@.yahoo.com> wrote in message
>> news:1150819548.395205.74950@.r2g2000cwb.googlegroups.com...
>> > I've successfully created a data source and reports against an Analysis
>> > Services database.
>> > The AS database is on the same machine as RS (let's call this Server
>> > 1).
>> >
>> > I tried this against a second AS database (on Server 2), and it works
>> > fine from Visual Studio, but when I deploy it to RS (on Server 1) and
>> > try to run it, I get the error:
>> >
>> > "...Cannot create a connection to data source 'DevServer'.
>> > (rsErrorOpeningConnection)
>> > A connection cannot be made. Ensure that the server is running.
>> > Unable to read from the transport connection: An existing connection
>> > was forcibly closed by the remote host."
>> >
>> > I'm not doing anything complicated. It's just that the AS database is
>> > on a different machine from the RS server. Shouldn't this work?
>> > Ideas?
>> >
>> > TIA,
>> > Jim
>> >
>

Tuesday, March 20, 2012

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

Friday, March 9, 2012

Problem When From Sequence file insert into Oracle Destination table in SSIS Package

Hi ,

i was used the Follwing DataFlow for my Package.using Oracle 8i

FalteFile Source -> Data Conversion >OLEDB Destination (Oracle Data table)

using above control flow to map the Source file to Destination . When i run the SSIS Package teh Folwing Error i got

"Truncation Occur maydue to inserting data from data flow column "columnName " with a length of 50 "

regarding this Error i i understood its for happening Data Length . so that i was changed the Source Column Length Exactly Match with the The Destination table.

still i am getting this Error. pls any one give me a solution . SHould i Change the DataType also?

pls give your suggestion

Thanks & Regards

Jeyakumar.M

chennai

At some point of your flow it is still defined as greater than 50. Check all outputs of all components and check external columns of your source as well.

-Jamie

|||

Hi Jamie

Thanks for your reply. all the Source column (Sequence file) and Destination Column (oracle Table ) length are same. But i didn't give Data type match for source and Destination .. Is it Required for Data Type to define in the Source column in Dataconversion control. pls Let me know.

Thanks For Your reply

Jeyakumar.M

chennai

|||

Data types in teh source are by and large determined by the OLE DB Provider. If you need them to be something else then drop a Data Conversion component into your flow.

-Jamie

Problem when adding ssis packages from microsoft visual source safe 6.0

I have created a integration services project on machine A and have added to visual source safe 6.0

When i try to take the project from source safe and store that on a different machine B i have a problem with it....

I check in everything on Machine A

When i try to add on machine B it tries to add it with "Name of package(1)" which means that its adding a copy.But it dosent do for all only for few

Could anyone let me know what the problem is?

Any time you see an unexpected "Name of package(1)" package added to you project, means the folder where the packages are stored already have a file with that name. Depending in how you do it, a file that is not part of the project may still exists in the folder. Use a windows explore to check what I am saying.

Problem when adding ssis packages from microsoft visual source safe 6.0

I have created a integration services project on machine A and have added to visual source safe 6.0

When i try to take the project from source safe and store that on a different machine B i have a problem with it....

I check in everything on Machine A

When i try to add on machine B it tries to add it with "Name of package(1)" which means that its adding a copy.But it dosent do for all only for few

Could anyone let me know what the problem is?

Any time you see an unexpected "Name of package(1)" package added to you project, means the folder where the packages are stored already have a file with that name. Depending in how you do it, a file that is not part of the project may still exists in the folder. Use a windows explore to check what I am saying.

Saturday, February 25, 2012

Problem using parameter on SQL source data control

I have an ASP page which uses an SQL data source control, as shown below:

<asp:SqlDataSource ID="mySQL" runat="server"
ConnectionString="<%$ ConnectionStrings:mySQLConnectionString %>"
SelectCommand="SELECT device FROM device_table WHERE (device_id IN (@.devicelist))">
<SelectParameters>
<asp:Parameter DefaultValue="" Name="devicelist" Type="String" />
</SelectParameters>
</asp:SqlDataSource
The problem is getting the "IN" clause of the select statement to work via the ASP page with code behind in C#. If I test the query in the page designer when configuring the SQL control by inserting 'device-1','device-2','device-3' as the value for the "devicelist" parameter, everything works as expected. However, when that same value is written programmatically into the DefaultValue of the parameter, the resulting query contains no results (as if the string contents are invalid). If I alter my program to supply a single entry (with no commas) it seems to work as well. I suspect the comma (and possibly the single-quote) characters in my string when multiple entries are involved are causing the issue.

Is there a proper technique for getting the requisite quote-delimited, comma-separated list into the SQL control command parameter correctly? Should I be using some sort of escape sequence for the single-quote and comma characters? Should I be using another "type" for the parameter; one that accepts an array of entries? I have not been able to find any examples or documentation that provides an answer.

A slight adjustment to the statements made in my earlier post: Using the "Test query" in the page design view for the control does NOT work. What does work is using SQL Server 2005 to run an equivalent query. So the page design view test query functionality and the ASP page functionality do indeed match, unlike what I stated earlier. I apologize for any confusion this may have caused.

But the problem still remains: how can I get the list of values passed into the control via the parameter?

Problem using merge join transformation in Sql server 2005(SSIS)

Hi,

I am pretty new to SSIS. I am transferring some rows from 2 source tables to 1 destination table.

The 2 source tables have 1000 rows.They act as the 2 inputs to a merge join transformation where i perform the join between the 2 tables based on a couple of fields. But for some reason the output of the merge join gives me about 1018 rows .Shouldnt the destination also have only 1000 rows?

How do i solve tis problem?

Thanks in advance

Sat

Satishr23:

But for some reason the output of the merge join gives me about 1018 rows .Shouldnt the destination also have only 1000 rows?

Not exactly. It depends on the logical operation of the merge join, for example "full outer join" may lead to such issue. You can refer to:

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/optimsql/odp_tun_1_5alv.asp

Monday, February 20, 2012

Problem uploading data into SQL Server with SSIS

Hi

I designed a package in SSIS that loads data from an Excel source into a oledb SQL database table.

The problem I have is that two of the columns that are supposed to be nvarchar type columns sometimes contain numerical strings. These values causes an error when 'Allow Null' is not set and loads as NULL if 'Allow Null' is set.

How can I force these values into the table?

I have a script transformation object in the package with this code:

If IsNumeric(Row.OCCode) Then

Row.ItemCode = CStr(Row.OCCode)

Else

Row.ItemCode = Row.OCCode

End If

ItemCode is of type unicode string and the column in the SQL DB Table it's mapped to is of type nvarchar

What is the source data type set to for those columns in the source connection?|||

I don't know how to check that, but the input columns into the transformation from the source are unicode strings.

I Also tried Forcing the Excel columns to Text.

|||In the source, the columns are set to Unicode string [DT_WSTR]|||Yeah, I don't understand what NULLs have to do with numeric data appearing in a string field. Can you shed more light on this?|||

It seems impossible to upload Text and numeric values into one Text column in the SQL database. The excel source picks up the source data as unicode string if its alphanumeric values and Numeric type when it's numeric value. if I make all the source columns in the source Unicode String it stops the running package as soon as it comes accross a numeric value with this Error Message:

There was an error with input column "ItemDescription" (889) on input "OLE DB Destination Input" (248). The column status returned was: "The value violated the integrity constraints for the column

If I make the column accept NULL values in the database, the package completes the data load, but make all the numeric values NULL.

I can enter data manually into this database to take numeric values in the nvarchar field, but I don't know how to set the SSIS package to upload the numeric values as Text.

|||Take a look here:

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1277733&SiteID=1|||

I managed to upload the data, thanks. The link you added mentioned that numerical strings in the excel file need to be re-entered after the column format is changed to Text. Seeing that I had 54000 rows, I had to perform a text-function operation on all the relative cells. Something like =trim(A2) and then copy these cells back to the original columns as values.

Thanks

|||The important thing in that link was the setting of the IMEX parameter.|||

Yeah I saw the code, but don't know where to add it or how to change the IMEX property. I had to get the data in.

It will help a lot if you can explain where to change this property. I can change the registry entries.

Problem uploading .rdl

The report server cannot process the report. The data source connection information has been deleted

I want to make a copy of a report. I go into report properties on the SSRS, click edit and download the .rdl to my computer.

I then upload the report, using a different name.

I then get the above error.

If I copy the report to the same location as the shared data source, and the above error disappears.

But now the report doesn't work - no parameters in the dropdown lists.

My question is : Why does a copy of a report, uploaded to the SSRS, not work, when the original is sitting right next to it, with the same rdl definitin, in a working state?

Are all the datasets using a single shared data source? Check that no private data sources are being used. After re-uploading the report with a different name, go to the properties page in report manager and in the data sources section make sure that you check all the datasources being used. Repoint it to the shared datasource and retype any connection strings and usernames and passwords for the data sources. I think for security reasons these are ommitted when you export the RDL.|||

Adam,

You are right. I checked the Data Sources, and there were two shared data sources that were marked invalid. However, I notice that the parameters have also been messed up. In the original report, there was no default parameter specified, whereas the new report (copied and uploaded) indicates a default parameter, which happens to be an invalid value. Because the dropdown boxes for the other parameters are linked, these dropdown boxes don't populate. My reasoning says that the uploaded .rdl should be the same as the copy I downloaded. I can see that it has been changed when referencing Data Sources. Why is there this difference in the parameters? Is this "by design"?
Question : Why does the parameter default value change when I upload the .rdl using a different name?

Question: How do I fix the problem?

|||

I notice that the new report (copy) has two problems with the parameters:

1. Parameter is no longer marked "hidden", but is marked "prompt the user"

2. Parameter contains an invalid default value.

I have changed the parameter so that it is now marked "hidden", and so that the default value is the same as the original report (which was empty). The report now works.

Perhaps somebody has an answer to the problem below (repeated from previous post):

Question : Why does the parameter default value change when I upload the .rdl using a different name?