Showing posts with label web. Show all posts
Showing posts with label web. Show all posts

Monday, March 26, 2012

problem with aspnet_ "Could not find stored procedure"


I have developed an asp.net 2.0 web application that uses sql2000 and with storded procedures.
Everything has been working great untill i yesterday found that someone have put in new stored procedures
in the database. The procedures starts with "dbo.aspnet_" like dbo.aspnet_CheckSchemaVersion.
Because i din't create them and i surtenly not call them from the application, i deleted them all.

Now when i try to use my web application nothing works. The app, somehow calls the procedure and becuase they are deleted
an error message is thrown like: Could not find stored procedure 'dbo.aspnet_CheckSchemaVersion'.

But the strange thing is that the problem only accure when i publish the site on the web server.
if i would publish it to a local folder on my desktop ore just run in debug mode against the database there are no problems.

I don't want to use the aspnet procedures that probebly comes from aspnet_regsql.exe and that im not calling from the code but reacts somehow,
I just want it to tun as it was designed to do.
And if i need them, can someone explain why?

please help :)

Dude, the "aspnet_" stuff is from Microsoft... it's the Membership provider. To get it back run "aspnet_regsql' in c:\windows\microsoft.net\framework\v2.blah (or wherever your windows files are).

|||

Yo Dude :) I did what you said and of course it worked. But i don't know why aspnet_regsql.exe is suddenly needed and all of those procedures that comes along. It worked without it before.

thx :)

sql

Problem with asp page and ODBC on Windows 2003 SR 64 Bits

I have an Application developed on ASP, I got a few new servers 64bits, I installed microsoft WIN 2003 SR.
When I get in into the web site I receive this errors:

Microsoft OLE DB Provider for ODBC Driverserror '80004005'

[Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified

/ConnectToDatabase.asp, line 17

I made some obvios checks, I checked that the ODBC really exists and we move the IIS 6.0 to run in 32bits mode as I found in some page.

Thanks you.

Ahmed

Hi,

could you please post your connection string right in here ? We can′t see if you use a DSN or a DSNless connection.

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de
|||

You are likely using an ODBC driver that is not available for 64bits. See http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=20574&SiteID=1 for the relevnat discusion.

Can you connect to the odbc driver in question using ODBC driver manager. Start->Run->ODBCAD32.exe. Using odbc driver manager create a new dsn and test the connection.

Problem with asp page and ODBC on Windows 2003 SR 64 Bits

I have an Application developed on ASP, I got a few new servers 64bits, I installed microsoft WIN 2003 SR.
When I get in into the web site I receive this errors:

Microsoft OLE DB Provider for ODBC Drivers error '80004005'

[Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified

/ConnectToDatabase.asp, line 17

I made some obvios checks, I checked that the ODBC really exists and we move the IIS 6.0 to run in 32bits mode as I found in some page.

Thanks you.

Ahmed

Hi,

could you please post your connection string right in here ? We can′t see if you use a DSN or a DSNless connection.

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de|||

You are likely using an ODBC driver that is not available for 64bits. See http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=20574&SiteID=1 for the relevnat discusion.

Can you connect to the odbc driver in question using ODBC driver manager. Start->Run->ODBCAD32.exe. Using odbc driver manager create a new dsn and test the connection.

Problem with ASP - ODBC - SQL Server after moving to Windows 2003 Server

Hello,
We are setting up a backup server for one of our Web sites, and the current
machine is running Win 2K Server, the new one Win 2003 Server. Otherwise
everything else is the same.
Most everthing works fine, except for one ASP template, which is opening a
recordset with this line:
set RS = Server.CreateObject("ADODB.Recordset") rs.Open "DealerInfo",
Conn,adOpenKeyset,adLockOptimistic,adcmdtable
On the 2003 server it gives an error:
Microsoft OLE DB Provider for ODBC Drivers error '800401f3'
[Microsoft][ODBC SQL Server Driver]Cursor type changed
I have searched for information about thids error, but not found any so far.
Any help would be appreciated.
Ragnar
I have determined that this is not really an error message, but an
informational message. It seems pretty clear that the real error lies
somewhere else, so I will have to come up with a way to add some debug
statements without stopping the code.
Ragnar
"Ragnar Midtskogen" <ragnar_ng@.newsgroups.com> wrote in message
news:%23THcMdmpEHA.2032@.TK2MSFTNGP10.phx.gbl...
> Hello,
> We are setting up a backup server for one of our Web sites, and the
> current machine is running Win 2K Server, the new one Win 2003 Server.
> Otherwise everything else is the same.
> Most everthing works fine, except for one ASP template, which is opening a
> recordset with this line:
> set RS = Server.CreateObject("ADODB.Recordset") rs.Open "DealerInfo",
> Conn,adOpenKeyset,adLockOptimistic,adcmdtable
> On the 2003 server it gives an error:
> Microsoft OLE DB Provider for ODBC Drivers error '800401f3'
> [Microsoft][ODBC SQL Server Driver]Cursor type changed
> I have searched for information about thids error, but not found any so
> far.
> Any help would be appreciated.
> Ragnar
>

Friday, March 23, 2012

Problem with accessing SQL Server database throu web which is behind a firewall.

Hello all,
Well My office has 2 branches one in india and 1 in usa.
I am trying to connect the database in usa from india ..My usa server has a Static IP . but unfortunately it is Behind a firewall...Hence i am not able to connect..
Please provide me the suggestions...
saiOpen port #1433.

hth|||Originally posted by ac_nobrega
Open port #1433.

hth

Thanks Nobrega...
Can u please give me the exact syntax of the path
is it like <<server-ip>>:1433 ?

Please reply back as soon as possible..

sai|||Originally posted by vjeedigunta
Thanks Nobrega...
Can u please give me the exact syntax of the path
is it like <<server-ip>>:1433 ?

Please reply back as soon as possible..

sai

You're right.
Just put a rule in your FW that permit any traffic from/to your SQL server on port 1433.

hth.|||And may sure you're using sockets, not named pipes.
Originally posted by ac_nobrega
You're right.
Just put a rule in your FW that permit any traffic from/to your SQL server on port 1433.

hth.

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 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 trying to deploy a web site built with asp.net 2.0 and using SQL EXPRESS

Hi,

Plz help!

I built a web site using IIS and ASP.NET 2.0.

My web site has a log on screen and I only configured it with one user without any roles. This web site uses the SQL EXPRESS.(I Have 2 databases: 1 for the security required by the application and the other for my application. for the connectionstring I used a windows authentication security with an instance = true.)

Everything went well on my PC.

When I tried to deploy the web site on another PC, there was a big problem.

When I tried to login with the same user I created, then I have a problem.

The password is incorrect(Why? I don't know).

Maybe there is a problem with the IIS or with the SQL SERVER.

pLZ HELP!!

You should take a look at the forum at http://forums.asp.net/54/ShowForum.aspx, which covers Visual Web Designer. They will have a better idea how to address this.

Mike

problem when running "configuration web synchronization"

Hi, there;
We have device using sqlce2.0 and replicate data with sql2000.

Now we have new WM5 device which uses SqlCe3.0. So I need to install connectivity tools
using "SqlCe30setupen.msi".

I got error when I run "Configure Web Synchronization Wizard": The operation completed successfully. (Exception from HRESULT: 0x80070000) (mscorlib).

When I run this wizard, I logged in the server as "Administrator" and point to the existing snapshot folder which is used by sqlce2.0.

Can anybody advise what cause the problem? Can I install it in the same virtual directory as the current one where the sqlce2.0 sits in?

Big thanks here.

You should install in a new virtual folder.|||Thanks, Erik;
Yes, I tried to install it new virtual folder. But I have this error.

Another question is that which user should I use to install it?

Cheers|||

Hey Qiuwei,

You should install Server Tools MSI in admin account. Also note that ConnWiz that is installed by this MSI, should be run under network user who is into administrators group of the box. Please use a different Virtual Directory for 2.0 and 3.0.

Thanks,

Laxmi

|||Yes. Thank you.
I did that. And I have to add user "IUSR_machineName"(with some permission) to that folder to make it work.

Friday, March 9, 2012

Problem when opening the sql server express in visual web developmer express edition

hi

i download free starter kit timetraker application( i downloaded both Visual web devaloper and sql server express from the Internet)

when i tried to run it it is showing the following error

An error has occurred while establishing a connection tothe server. When connecting to SQL Server 2005, this failure may becaused by the fact that under the default settings SQL Server does notallow remote connections. (provider: Shared Memory Provider, error: 40- Could not open a connection to SQL Server)

plz give me the solution above error

thanks in advance

vittal

The simplest thing have u checked the Sql Server Service is started or not... This is the simplest error which occur... 50% time

Satya

|||

Type inetmgr on run.
select the verual directory -> right click and select property -> go to ASP.NET tab -> click Edit Configuration

and then Edit the connection string accordingly.

Problem When I save Data In Database

Hi

I have problem in the data when I save it in database !!!

From Windows Application I Send (nText) Data to SQL Server Database in Web Server but when I try to explore it in SQL Server Enterprise manager or ny SQL Server DB Manager I see the Fields of (nText) Data is empty but when I try to brows the data in ASP.NET page I get it like the following

? ? ? ??? ??? ?? ? ? ???, ??? ?? ?? ?? ???. ??
??". ?? ??? ?? ?? ??? ???, ?? ??? ??? ??.
?? ??, ??? ? ? ??? ???, ? ?? ?? ?? ?? ??? ??

So I thing the data has been damaged!!
Why this problem... And how can I solve it??

The Problem only in (nText) Data ..

And thanks with my best regarding??It seems you need to take two steps. The first is to change the collation of SQL to ARABIC_CI_AI. Second, you need to change your web.config to set endocing to unicode.

hope help.

Bassam Basamad|||Hi

Thanks for your reply

First of all .. you talk about (web.config) File .. But my problem in SQL Server Database .. there is no problem in ASP.NET Pages (I know how to make it support Unicode chars) but the problem in Database

And the seconded thing about the (ARABIC_CI_AI.) I have do it from the first time when I create my Tables in SQL Server

So sorry .. your solution . don't solve my problem

Monday, February 20, 2012

Problem using an AXIS Webservice

Helo:

I am trying to use an axis webservice as a datasource to a report.

I have an error : Failed to prepare web request for the specified URL

When I run the query in query designer.

I test the webservice in a windows aplication and works fine. I think that the problem I have is with the target namespace/url

I am using the folowing data in the report:

datasource conection string: http://191.158.134.200:8080/CatalogWS/services/CatalogWebService

dataset query:

<Query>

<Method Namespace="urn:CatalogWebService" Name="findArticulos"/>

<SoapAction>urn:CatalogWebService/findArticulos</SoapAction>

</Query>

And here is a fragment (the header) of the wsdl of the webservice:

http://191.158.134.200:8080/CatalogWS/services/CatalogWebService?wsdl

<wsdl:definitions targetNamespace="urn:CatalogWebService" xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:apachesoap="http://xml.apache.org/xml-soap" xmlns:impl="urn:CatalogWebService" xmlns:intf="urn:CatalogWebService" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:tns1="http://core.catalog.cepre.opp.gub.uy" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:xsd="http://www.w3.org/2001/XMLSchema">

- <wsdl:types>...

Someone can help me, to find the right way ?

Tanks!!

I had resolved the conection problem, the problem was the parameters of the method.

The problem now is that the dataset result is not the actual data, there are 3 columns and one row:

columns: href ns1 encodingStyle

values: #0 urn:CatalogWebService http://schemas.xmlsoap.org/soap/encoding/

The data type returned by the ws method is a complex object with an array inside, is this the problem ?

Tanks for any help!

|||

Yes the complex object may be the issue.

The following article may give you some ideas on how to use the element path and apply type casting in your xml data extension query: http://msdn.microsoft.com/library/en-us/dnsql90/html/RepServXMLDS.asp

-- Robert

|||

Robert

the link you send me is about Charts and have no information related to xml. Please review that.

Tanks.

|||

Sorry for the incorrect link. I fixed it.

-- Robert