rsAccessDenied when accessing Report Server

I have SQLServer 2005 with reporting services running on win 2003 server.
I'm trying to configure SSRS with Anonymous access configured on
ReportServer Web Site and verified NTFS security on ReportServer folder
include Iusr and Iwam with read/execute permmisions
Does ReportServer stand on its own or does the ReportManager Web Site also
need Anonymous access?
Are there any config files that need to be updated?
What am I missing?
IE Message when accessing http://<Server>/ReportServer
The permissions granted to user 'VWIN2003SERVER\IUSR_VWIN2003SERVER' are
insufficient for performing this operation. (rsAccessDenied)
ReportServer Log File
w3wp!library!1!02/15/2006-11:54:17:: i INFO: Catalog SQL Server Edition = Developer
w3wp!library!1!02/15/2006-11:54:17:: e ERROR: Throwing
Microsoft.ReportingServices.Diagnostics.Utilities.AccessDeniedException: The
permissions granted to user 'VWIN2003SERVER\IUSR_VWIN2003SERVER' are
insufficient for performing this operation., ;
Info:
Microsoft.ReportingServices.Diagnostics.Utilities.AccessDeniedException: The
permissions granted to user 'VWIN2003SERVER\IUSR_VWIN2003SERVER' are
insufficient for performing this operation.
ReportServerService_Main Log File
ReportingServicesService!library!4!2/15/2006-08:54:25:: i INFO: Initializing
ConnectionType to '0' as specified in Configuration file.
ReportingServicesService!library!4!2/15/2006-08:54:25:: i INFO: Initializing
IsSchedulingService to 'True' as specified in Configuration file.
ReportingServicesService!library!4!2/15/2006-08:54:25:: i INFO: Initializing
IsNotificationService to 'True' as specified in Configuration file.
ReportingServicesService!library!4!2/15/2006-08:54:25:: i INFO: Initializing
IsEventService to 'True' as specified in Configuration file.
ReportingServicesService!library!4!2/15/2006-08:54:25:: i INFO: Initializing
PollingInterval to '10' second(s) as specified in Configuration file.
ReportingServicesService!library!4!2/15/2006-08:54:25:: i INFO: Initializing
WindowsServiceUseFileShareStorage to 'False' as specified in Configuration
file.
ReportingServicesService!library!4!2/15/2006-08:54:25:: i INFO: Initializing
MemoryLimit to '60' percent as specified in Configuration file.
ReportingServicesService!library!4!2/15/2006-08:54:25:: i INFO: Initializing
RecycleTime to '720' minute(s) as specified in Configuration file.
ReportingServicesService!library!4!2/15/2006-08:54:25:: i INFO: Initializing
MaximumMemoryLimit to '80' percent as specified in Configuration file.
ReportingServicesService!library!4!2/15/2006-08:54:25:: i INFO: Initializing
MaxAppDomainUnloadTime to '30' minute(s) as specified in Configuration file.
ReportingServicesService!library!4!2/15/2006-08:54:25:: i INFO: Initializing
MaxQueueThreads to '0' thread(s) as specified in Configuration file.
ReportingServicesService!library!4!2/15/2006-08:54:25:: i INFO: Initializing
IsWebServiceEnabled to 'True' as specified in Configuration file.
ReportingServicesService!library!4!2/15/2006-08:54:25:: i INFO: Initializing
MaxActiveReqForOneUser to '20' requests(s) as specified in Configuration
file.
ReportingServicesService!library!4!2/15/2006-08:54:25:: i INFO: Initializing
MaxScheduleWait to '5' second(s) as specified in Configuration file.
ReportingServicesService!library!4!2/15/2006-08:54:25:: i INFO: Initializing
DatabaseQueryTimeout to '120' second(s) as specified in Configuration file.
ReportingServicesService!library!4!2/15/2006-08:54:25:: i INFO: Initializing
ProcessRecycleOptions to '0' as specified in Configuration file.
ReportingServicesService!library!4!2/15/2006-08:54:25:: i INFO: Initializing
RunningRequestsScavengerCycle to '60' second(s) as specified in
Configuration file.
ReportingServicesService!library!4!2/15/2006-08:54:25:: i INFO: Initializing
RunningRequestsDbCycle to '60' second(s) as specified in Configuration file.
ReportingServicesService!library!4!2/15/2006-08:54:25:: i INFO: Initializing
RunningRequestsAge to '30' second(s) as specified in Configuration file.
ReportingServicesService!library!4!2/15/2006-08:54:25:: i INFO: Initializing
CleanupCycleMinutes to '10' minute(s) as specified in Configuration file.
ReportingServicesService!library!4!2/15/2006-08:54:25:: i INFO: Initializing
DailyCleanupMinuteOfDay to default value of '120' minutes since midnight
because it was not specified in Configuration file.
ReportingServicesService!library!4!2/15/2006-08:54:25:: i INFO: Initializing
WatsonFlags to '1064' as specified in Configuration file.
ReportingServicesService!library!4!2/15/2006-08:54:25:: i INFO: Initializing
WatsonDumpOnExceptions to
'Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException,Microsoft.ReportingServices.Modeling.InternalModelingException'
as specified in Configuration file.
ReportingServicesService!library!4!2/15/2006-08:54:25:: i INFO: Initializing
WatsonDumpExcludeIfContainsExceptions to
'System.Data.SqlClient.SqlException,System.Threading.ThreadAbortException'
as specified in Configuration file.
ReportingServicesService!library!4!2/15/2006-08:54:25:: i INFO: Initializing
SecureConnectionLevel to '0' as specified in Configuration file.
ReportingServicesService!library!4!2/15/2006-08:54:25:: i INFO: Initializing
DisplayErrorLink to 'True' as specified in Configuration file.
ReportingServicesService!library!4!2/15/2006-08:54:25:: i INFO: Initializing
WebServiceUseFileShareStorage to 'False' as specified in Configuration
file.
ReportingServicesService!servicecontroller!9!2/15/2006-08:54:31:: Total
Physical memory: 685219840
ReportingServicesService!servicecontroller!4!2/15/2006-08:54:31:: i INFO:
RPC Server started. Endpoint name ='ReportingServices$MSSQL.3'
ReportingServicesService!library!d!2/15/2006-08:57:45:: i INFO: Catalog SQL
Server Edition = Developer
ReportingServicesService!resourceutilities!d!2/15/2006-08:57:45:: i INFO:
Reporting Services starting SKU: Developer
ReportingServicesService!resourceutilities!d!2/15/2006-08:57:45:: i INFO:
Evaluation copy: 0 days left
ReportingServicesService!library!e!2/15/2006-08:57:45:: i INFO: Catalog SQL
Server Edition = Developer
ReportingServicesService!library!f!2/15/2006-08:57:45:: i INFO: Catalog SQL
Server Edition = Developer
ReportingServicesService!crypto!d!2/15/2006-08:57:45:: i INFO: Initializing
crypto as user: NT AUTHORITY\SYSTEM
ReportingServicesService!crypto!d!2/15/2006-08:57:46:: i INFO: Exporting
public key
ReportingServicesService!crypto!d!2/15/2006-08:57:46:: i INFO: Performing
sku validation
ReportingServicesService!crypto!d!2/15/2006-08:57:46:: i INFO: Importing
existing encryption key
Thanks
Marc BumgarnerNo a good idea (anonymous access). As soon as you do this you will find out
that you have lost all admin rights even when you are an administrator on
the box. Why? Because it is anonymous, RS does not know who you are.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Marc Bumgarner" <mbumgarner@.ecomponentstech.com> wrote in message
news:8P6dnaUqm6P1Gm7enZ2dnUVZ_sidnZ2d@.mt.net...
>I have SQLServer 2005 with reporting services running on win 2003 server.
> I'm trying to configure SSRS with Anonymous access configured on
> ReportServer Web Site and verified NTFS security on ReportServer folder
> include Iusr and Iwam with read/execute permmisions
> Does ReportServer stand on its own or does the ReportManager Web Site also
> need Anonymous access?
> Are there any config files that need to be updated?
> What am I missing?
>
> IE Message when accessing http://<Server>/ReportServer
> The permissions granted to user 'VWIN2003SERVER\IUSR_VWIN2003SERVER' are
> insufficient for performing this operation. (rsAccessDenied)
>
> ReportServer Log File
> w3wp!library!1!02/15/2006-11:54:17:: i INFO: Catalog SQL Server Edition => Developer
> w3wp!library!1!02/15/2006-11:54:17:: e ERROR: Throwing
> Microsoft.ReportingServices.Diagnostics.Utilities.AccessDeniedException:
> The permissions granted to user 'VWIN2003SERVER\IUSR_VWIN2003SERVER' are
> insufficient for performing this operation., ;
> Info:
> Microsoft.ReportingServices.Diagnostics.Utilities.AccessDeniedException:
> The permissions granted to user 'VWIN2003SERVER\IUSR_VWIN2003SERVER' are
> insufficient for performing this operation.
>
> ReportServerService_Main Log File
>
> ReportingServicesService!library!4!2/15/2006-08:54:25:: i INFO:
> Initializing ConnectionType to '0' as specified in Configuration file.
> ReportingServicesService!library!4!2/15/2006-08:54:25:: i INFO:
> Initializing IsSchedulingService to 'True' as specified in Configuration
> file.
> ReportingServicesService!library!4!2/15/2006-08:54:25:: i INFO:
> Initializing IsNotificationService to 'True' as specified in
> Configuration file.
> ReportingServicesService!library!4!2/15/2006-08:54:25:: i INFO:
> Initializing IsEventService to 'True' as specified in Configuration file.
> ReportingServicesService!library!4!2/15/2006-08:54:25:: i INFO:
> Initializing PollingInterval to '10' second(s) as specified in
> Configuration file.
> ReportingServicesService!library!4!2/15/2006-08:54:25:: i INFO:
> Initializing WindowsServiceUseFileShareStorage to 'False' as specified in
> Configuration file.
> ReportingServicesService!library!4!2/15/2006-08:54:25:: i INFO:
> Initializing MemoryLimit to '60' percent as specified in Configuration
> file.
> ReportingServicesService!library!4!2/15/2006-08:54:25:: i INFO:
> Initializing RecycleTime to '720' minute(s) as specified in Configuration
> file.
> ReportingServicesService!library!4!2/15/2006-08:54:25:: i INFO:
> Initializing MaximumMemoryLimit to '80' percent as specified in
> Configuration file.
> ReportingServicesService!library!4!2/15/2006-08:54:25:: i INFO:
> Initializing MaxAppDomainUnloadTime to '30' minute(s) as specified in
> Configuration file.
> ReportingServicesService!library!4!2/15/2006-08:54:25:: i INFO:
> Initializing MaxQueueThreads to '0' thread(s) as specified in
> Configuration file.
> ReportingServicesService!library!4!2/15/2006-08:54:25:: i INFO:
> Initializing IsWebServiceEnabled to 'True' as specified in Configuration
> file.
> ReportingServicesService!library!4!2/15/2006-08:54:25:: i INFO:
> Initializing MaxActiveReqForOneUser to '20' requests(s) as specified in
> Configuration file.
> ReportingServicesService!library!4!2/15/2006-08:54:25:: i INFO:
> Initializing MaxScheduleWait to '5' second(s) as specified in
> Configuration file.
> ReportingServicesService!library!4!2/15/2006-08:54:25:: i INFO:
> Initializing DatabaseQueryTimeout to '120' second(s) as specified in
> Configuration file.
> ReportingServicesService!library!4!2/15/2006-08:54:25:: i INFO:
> Initializing ProcessRecycleOptions to '0' as specified in Configuration
> file.
> ReportingServicesService!library!4!2/15/2006-08:54:25:: i INFO:
> Initializing RunningRequestsScavengerCycle to '60' second(s) as specified
> in Configuration file.
> ReportingServicesService!library!4!2/15/2006-08:54:25:: i INFO:
> Initializing RunningRequestsDbCycle to '60' second(s) as specified in
> Configuration file.
> ReportingServicesService!library!4!2/15/2006-08:54:25:: i INFO:
> Initializing RunningRequestsAge to '30' second(s) as specified in
> Configuration file.
> ReportingServicesService!library!4!2/15/2006-08:54:25:: i INFO:
> Initializing CleanupCycleMinutes to '10' minute(s) as specified in
> Configuration file.
> ReportingServicesService!library!4!2/15/2006-08:54:25:: i INFO:
> Initializing DailyCleanupMinuteOfDay to default value of '120' minutes
> since midnight because it was not specified in Configuration file.
> ReportingServicesService!library!4!2/15/2006-08:54:25:: i INFO:
> Initializing WatsonFlags to '1064' as specified in Configuration file.
> ReportingServicesService!library!4!2/15/2006-08:54:25:: i INFO:
> Initializing WatsonDumpOnExceptions to
> 'Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException,Microsoft.ReportingServices.Modeling.InternalModelingException'
> as specified in Configuration file.
> ReportingServicesService!library!4!2/15/2006-08:54:25:: i INFO:
> Initializing WatsonDumpExcludeIfContainsExceptions to
> 'System.Data.SqlClient.SqlException,System.Threading.ThreadAbortException'
> as specified in Configuration file.
> ReportingServicesService!library!4!2/15/2006-08:54:25:: i INFO:
> Initializing SecureConnectionLevel to '0' as specified in Configuration
> file.
> ReportingServicesService!library!4!2/15/2006-08:54:25:: i INFO:
> Initializing DisplayErrorLink to 'True' as specified in Configuration
> file.
> ReportingServicesService!library!4!2/15/2006-08:54:25:: i INFO:
> Initializing WebServiceUseFileShareStorage to 'False' as specified in
> Configuration file.
> ReportingServicesService!servicecontroller!9!2/15/2006-08:54:31:: Total
> Physical memory: 685219840
> ReportingServicesService!servicecontroller!4!2/15/2006-08:54:31:: i INFO:
> RPC Server started. Endpoint name ='ReportingServices$MSSQL.3'
> ReportingServicesService!library!d!2/15/2006-08:57:45:: i INFO: Catalog
> SQL Server Edition = Developer
> ReportingServicesService!resourceutilities!d!2/15/2006-08:57:45:: i INFO:
> Reporting Services starting SKU: Developer
> ReportingServicesService!resourceutilities!d!2/15/2006-08:57:45:: i INFO:
> Evaluation copy: 0 days left
> ReportingServicesService!library!e!2/15/2006-08:57:45:: i INFO: Catalog
> SQL Server Edition = Developer
> ReportingServicesService!library!f!2/15/2006-08:57:45:: i INFO: Catalog
> SQL Server Edition = Developer
> ReportingServicesService!crypto!d!2/15/2006-08:57:45:: i INFO:
> Initializing crypto as user: NT AUTHORITY\SYSTEM
> ReportingServicesService!crypto!d!2/15/2006-08:57:46:: i INFO: Exporting
> public key
> ReportingServicesService!crypto!d!2/15/2006-08:57:46:: i INFO: Performing
> sku validation
> ReportingServicesService!crypto!d!2/15/2006-08:57:46:: i INFO: Importing
> existing encryption key
>
> Thanks
> Marc Bumgarner
>

RS2005 on Win2000

I've followed a couple of threads on this, but still haven't quite resolved the issue. RS 2005 is installed on a Win 2000 Server. The service seems to be running perfectly, but when I navigate to <localhost>\ReportServer, I get:

Reporting Services Error
--
The report server has encountered a configuration error. See the report server log files for more information. (rsServerConfigurationError)
Access to the path 'D:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\ReportServer\RSReportServer.config' is denied.

--
SQL Server Reporting Services

I've manually configured the webserviceaccount to the default aspnet machine logon since it's greyed out in the rs configuration screen. Once I manually added that logon, I've not had any errors or warnings in my log files. I've also tried messing with the folder permissions for this path, but no luck. So, I've read and tried a lot of things suggested on this forum. Anyone have the magic wand out there?

Thanks

OK, problem solved. The ASPNET machine logon permissions weren't propogating down the full folder structure for some reason. It works now.

RS SP2 Install Hell

Configuration: IIS Server on Win Server 2003, SQL Server 2000 SP4 on Win
Server 2004
Was able to install RS on IIS Server with command line using setup.exe
RSSETUPACCOUNT=sa RSSETUPPASSWORD=â'sapwâ'.
Then ran rsconfig â'c â'mâ'reportserver servernameâ' -s â'SQLServer machine nameâ'
â'aWindows â'uâ'domain\usernameâ' â'pâ'usernamepwâ'. Where â'domain\usernameâ' has
admin privs on the SQL Server.
Deployed some reports and received the error:
â'The version of the report server database is either in a format that is not
valid, or it cannot be read. The found version is 'Unknown'. The expected
version is 'C.0.6.43'. To continue, update the version of the report server
database and verify access rights.â'
I logged on to the IIS Server as with the domain\username used in rsconfig
and tried to install RSSP2 by running RSSP2.exe, then I tried running the
command line â'setup.exe RSSETUPACCOUNT=â'domain\usernameâ'
RSSETUPPASSWORD=usernamepwâ'.
Both failed with the following error:
â'SQL failed to connect to the database service for server configuration.
Refer to the Server error logs and set logs for more detailed error
information.â'
Then I tried several combinations of rsconfig with accounts (including sa)
that have administrator privs on SQL Server. Also tried â'aSQL option. All
attempts ended in the above connection error.
Is this a RS problem or SQL Server problem'
--
Thanks in advance
GHI can't install RS SP2 for the exact same reason :( Same config as you.|||Hello,
Please refer to the following information in the "Installing Reporting
Services From the Command Line" topic in Reporting Services Books
Online(BOL):
RSDATABASESERVER="servername\instancename"
Optional. Default value is the default instance of SQL Server on the local
machine.
This property applies to the RS_Server feature selection.
Specifies the SQL Server instance that hosts the report server database.
All editions of Reporting Services require SQL Server 2000 with SP3a or
later. For Standard Edition, the instance of SQL Server must be local. For
all others, it can either be local or available over the network. The
servername portion of the parameter can be a hostname, or an IP address.
Reporting Services does not support MSDE as a SQL Server instance.
--
Please notice that default value of RSDATABASESERVER is the DEFAULT
INSTANCE of SQL Server on the LOCAL machine. Since your SQL Server 2000
SP4 is installed on a Windows 2000 Server machine which is not the machine
your RS installed, you have to specify the RSDATABASESERVER properties when
installing RS. If not, RS may not be installed successfully.
I recommend you perform the following steps to narrow down the issue:
Step 1: Backup your files and remove RS entirely.
==================================If RS cannot be removed successfully, perform the following steps:
1. Re-run the setup.exe of Reporting Services that you had installed on
the machine before. Once this setup routine started it will detect the
existing installation and gave you an option to remove it.
2. If the issue still exists, run MSI installer clean up tool to uninstall
Reporting Services:
a. Please download the MSI installer clean up tool from the following web
site:
Description of the Windows Installer CleanUp Utility
http://support.microsoft.com/default.aspx?scid=kb;en-us;290301
b. Double click msicuu2.exe. Follow the wizard's instructions to install
the tool.
c. Launch the tool.
d. At the tool's UI, select "SQL Server 2000 Reporting Services" from the
product name listbox.
e. Click the "Remove" button and note the results.
Note: make sure that you only select "SQL Server 2000 Reporting Services"
item.
Step 2: Reinstalling RS
=============
Use the graphical setup wizard to install RS. If you use the command prompt
utility to install, you must provide information for each required
parameter. For example, you must specify the RSDATABASESERVER parameter.
Note:
1. For Standard Edition, the instance of SQL Server must be local. Check
your RS version to make sure it isn't Standard Edition.
2. Use the [/l*v log_file] parameter to specifies the name and path to a
verbose log file containing all Windows Installer log options. If you do
not specify this argument, no log file is created.
After installing, refer to the "Verifying an Installation of Reporting
Services" topic in BOL to verify RS is installed successfully.
If it cannot be installed successfully, check the verbose log file to find
related errors.
I hope the information is helpful.
Sophie Guo
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
=====================================================When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||Hi Sophie,
Thanks for your reply.
The system on which I am installin RS is busy during the day so I will not
have an opportunity to do a reinstall before tonight.
I do want to make sure we need to do a reinstall of RS. This all started
when I was trying to install SP2.
Let me review ...
When I initially installed RS I used the command "setup.exe
RSSETUPACCOUNT=sa RSSETUPPASSWORD=sapassword" to launch the graphical
interface from which was the same as starting with the graphical interface
except it forced the 'sa' credentials to be used to connect to the remote SQL
Server instance.
RS installed, the virtual directories were installed under the Default web
site, and the RS databases were installed on the remote SS.
I then ran rsconfig to establish the connection properties.
When trying to deploy a report I received the error indicating there was a
version issue with the RS db. (In checking the install log there was an
indication that the sp 'GetDBVersion' could not be found ... I verified that
it was indeed installed).
I checked the KB for this error and found an article that recommended
installing SP2 as the solution.
The SP2 install keeps failing because it cannot connect to SS.
So, based upon this scenerio you are recommending a total reinstall of RS'
Thanks again for your assistance.
Gene
--
Thanks in advance
GH
"Sophie Guo [MSFT]" wrote:
> Hello,
> Please refer to the following information in the "Installing Reporting
> Services From the Command Line" topic in Reporting Services Books
> Online(BOL):
>
> --
> RSDATABASESERVER="servername\instancename"
> Optional. Default value is the default instance of SQL Server on the local
> machine.
> This property applies to the RS_Server feature selection.
> Specifies the SQL Server instance that hosts the report server database.
> All editions of Reporting Services require SQL Server 2000 with SP3a or
> later. For Standard Edition, the instance of SQL Server must be local. For
> all others, it can either be local or available over the network. The
> servername portion of the parameter can be a hostname, or an IP address.
> Reporting Services does not support MSDE as a SQL Server instance.
> --
> Please notice that default value of RSDATABASESERVER is the DEFAULT
> INSTANCE of SQL Server on the LOCAL machine. Since your SQL Server 2000
> SP4 is installed on a Windows 2000 Server machine which is not the machine
> your RS installed, you have to specify the RSDATABASESERVER properties when
> installing RS. If not, RS may not be installed successfully.
> I recommend you perform the following steps to narrow down the issue:
>
> Step 1: Backup your files and remove RS entirely.
> ==================================> If RS cannot be removed successfully, perform the following steps:
>
> 1. Re-run the setup.exe of Reporting Services that you had installed on
> the machine before. Once this setup routine started it will detect the
> existing installation and gave you an option to remove it.
>
> 2. If the issue still exists, run MSI installer clean up tool to uninstall
> Reporting Services:
> a. Please download the MSI installer clean up tool from the following web
> site:
> Description of the Windows Installer CleanUp Utility
> http://support.microsoft.com/default.aspx?scid=kb;en-us;290301
>
> b. Double click msicuu2.exe. Follow the wizard's instructions to install
> the tool.
> c. Launch the tool.
> d. At the tool's UI, select "SQL Server 2000 Reporting Services" from the
> product name listbox.
> e. Click the "Remove" button and note the results.
> Note: make sure that you only select "SQL Server 2000 Reporting Services"
> item.
>
> Step 2: Reinstalling RS
> =============> Use the graphical setup wizard to install RS. If you use the command prompt
> utility to install, you must provide information for each required
> parameter. For example, you must specify the RSDATABASESERVER parameter.
> Note:
> 1. For Standard Edition, the instance of SQL Server must be local. Check
> your RS version to make sure it isn't Standard Edition.
> 2. Use the [/l*v log_file] parameter to specifies the name and path to a
> verbose log file containing all Windows Installer log options. If you do
> not specify this argument, no log file is created.
> After installing, refer to the "Verifying an Installation of Reporting
> Services" topic in BOL to verify RS is installed successfully.
> If it cannot be installed successfully, check the verbose log file to find
> related errors.
> I hope the information is helpful.
> Sophie Guo
> Microsoft Online Partner Support
> Get Secure! - www.microsoft.com/security
> =====================================================> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> =====================================================> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>
>|||Hello,
I understand that your concern. However, some times reinstallation is a
efficient way to resolve the issue.
Based on my further research, customers who recevied similar error messages
resolved their issue by performing the following methods:
1. Connect to SQL using a standard SQL login
rsconfig -c -s servername -d reportserver -a SQL -u sa -p password
2. Install SRS SP2
3. Reinstallation:
http://www.microsoft.com/products/ee/transform.aspx?EvtSrc=Microsoft.Reporti
ngServices.Diagnostics.Utilities.ErrorStrings.resources.Strings&EvtID=rsInva
lidReportServerDatabase&ProdName=Microsoft%20SQL%20Server%20Reporting%20Serv
ices&ProdVer=8.00
Explanation
This error occurs when the report server database is not the same version
as the report server engine. This error can occur if you move components or
modify your configuration (for example, moving a report server into a Web
farm, and the existing report servers in the Web farm are a different
version).
User Action
There are no database repair tools that you can use to modify the version
of a database. You must run Setup to install a report server and create a
report server database that has the same version. You can run rs.exe to
copy data from one report server database to another. For more information,
search for rs utility in Books Online.
--
I suggest that you perform the following steps to narrow down the issue:
Step 1: Run the following commands in the command line window:
RSConfig.exe -c -m <computername> -s <sql_svr_name> -d <srs_db_name> -a
sql -u sa -p <pwd>
IISReset
net stop reportserver
net start reportserver
Note:
1. The "-m" parameter specifies the name of the computer on which the
report server is installed. In this case, it should be the name of the
Windows 2000 server.
2. The "-s" specifies the name of the SQL Server instance on which the
report server database is installed.
For default SQL instance, the name is same as the computer name.
For named SQL instance, the name is <computer name>\<SQL server instance
name>
The SQL Server instance name is case-sensitive if you are enforcing case
sensitivity on your SQL Server instance.
You mentioned that you have run rsconfig commands several times. However, I
notice that you used
-s 'SQLServer machine name'
in the command. Please notice that the "-s" specifies the SQL Server
instance name instead of a machine name.
Check the issue. If the issue still exists, check if you can install SRS
SP2 successfully.
If you still received the error message "SQL failed to connect to the
database service for server configuration. " Check the RS log files, SQL
server log files and Windows NT application and system log files to see if
there are any related errors.
By default, RS log files are located in C:\Program Files\Microsoft SQL
Server\MSSQL\Reporting Services\LogFiles folder. SQL server error logs are
located in the
C:\Program Files\Microsoft SQL Server\MSSQL\LOG folder.
If the issue still exists, reinstallation may be a efficient way to resolve
the issue. If anything is unclear, get in touch.
Sophie Guo
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
=====================================================When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||I tried this on another server, one I can bounce at will!! And it worked to
install RS and RSSP2.
Howerver I am back to the following error being displayed in IE:
â'The version of the report server database is either in a format that is not
valid, or it cannot be read. The found version is 'Unknown'. The expected
version is 'C.0.6.43'. To continue, update the version of the report server
database and verify access rights.â'
Looking at the RS Log the following was displayed:
w3wp!library!d48!07/11/2005-13:15:44:: e ERROR: Sql
error:System.Data.SqlClient.SqlException: Could not find stored procedure
'GetDBVersion'.
at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior
cmdBehavior, RunBehavior runBehavior, Boolean returnStream)
at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
at
Microsoft.ReportingServices.Library.InstrumentedSqlCommand.ExecuteNonQuery()
at
Microsoft.ReportingServices.Library.ConnectionManager.EnsureCorrectDBVersion()
w3wp!library!d48!07/11/2005-13:15:44:: e ERROR: Throwing
Microsoft.ReportingServices.Diagnostics.Utilities.InvalidReportServerDatabaseException:
The version of the report server database is either in a format that is not
valid, or it cannot be read. The found version is 'Unknown'. The expected
version is 'C.0.6.54'. To continue, update the version of the report server
database and verify access rights.,
The proc 'GetDBVersion' IS INSTALLED. It is:
CREATE PROCEDURE [dbo].[GetDBVersion]
@.DBVersion nvarchar(32) OUTPUT
AS
set @.DBVersion = 'C.0.6.54'
GO
My question what calls GetDBVersion'
That seems to be the issue ..
--
Thanks in advance
GH
"Sophie Guo [MSFT]" wrote:
> Hello,
> I understand that your concern. However, some times reinstallation is a
> efficient way to resolve the issue.
> Based on my further research, customers who recevied similar error messages
> resolved their issue by performing the following methods:
> 1. Connect to SQL using a standard SQL login
> rsconfig -c -s servername -d reportserver -a SQL -u sa -p password
>
> 2. Install SRS SP2
> 3. Reinstallation:
>
> http://www.microsoft.com/products/ee/transform.aspx?EvtSrc=Microsoft.Reporti
> ngServices.Diagnostics.Utilities.ErrorStrings.resources.Strings&EvtID=rsInva
> lidReportServerDatabase&ProdName=Microsoft%20SQL%20Server%20Reporting%20Serv
> ices&ProdVer=8.00
>
> --
> Explanation
> This error occurs when the report server database is not the same version
> as the report server engine. This error can occur if you move components or
> modify your configuration (for example, moving a report server into a Web
> farm, and the existing report servers in the Web farm are a different
> version).
> User Action
> There are no database repair tools that you can use to modify the version
> of a database. You must run Setup to install a report server and create a
> report server database that has the same version. You can run rs.exe to
> copy data from one report server database to another. For more information,
> search for rs utility in Books Online.
> --
> I suggest that you perform the following steps to narrow down the issue:
>
> Step 1: Run the following commands in the command line window:
>
> RSConfig.exe -c -m <computername> -s <sql_svr_name> -d <srs_db_name> -a
> sql -u sa -p <pwd>
> IISReset
> net stop reportserver
> net start reportserver
>
> Note:
> 1. The "-m" parameter specifies the name of the computer on which the
> report server is installed. In this case, it should be the name of the
> Windows 2000 server.
> 2. The "-s" specifies the name of the SQL Server instance on which the
> report server database is installed.
> For default SQL instance, the name is same as the computer name.
> For named SQL instance, the name is <computer name>\<SQL server instance
> name>
> The SQL Server instance name is case-sensitive if you are enforcing case
> sensitivity on your SQL Server instance.
> You mentioned that you have run rsconfig commands several times. However, I
> notice that you used
> -s 'SQLServer machine name'
> in the command. Please notice that the "-s" specifies the SQL Server
> instance name instead of a machine name.
> Check the issue. If the issue still exists, check if you can install SRS
> SP2 successfully.
> If you still received the error message "SQL failed to connect to the
> database service for server configuration. " Check the RS log files, SQL
> server log files and Windows NT application and system log files to see if
> there are any related errors.
> By default, RS log files are located in C:\Program Files\Microsoft SQL
> Server\MSSQL\Reporting Services\LogFiles folder. SQL server error logs are
> located in the
> C:\Program Files\Microsoft SQL Server\MSSQL\LOG folder.
> If the issue still exists, reinstallation may be a efficient way to resolve
> the issue. If anything is unclear, get in touch.
>
> Sophie Guo
> Microsoft Online Partner Support
> Get Secure! - www.microsoft.com/security
> =====================================================> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> =====================================================> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>|||Hello,
Rsconfig should be run only against report server catalog database and not
against any database. Based on my research, if Rsconfig run against other
database, it will corrupt the config files and the error "Could not find
stored procedure 'GetDBVersion'" may occur.
I am not clear about the current situation:
> I tried this on another server, one I can bounce at will!! And it worked
to install RS and RSSP2.
Would you please answer the following questions to clarify?
1. When you installed RS on another server, have you created a new SQL SRS
database? Please understand that we cannot be using the same SQL SRS
database if they are not in a report server Web farm.
2. If you create a new SRS database, is it a local SQL server database? Do
you mean you reproduced the issue on a new installation?
3. If you didn't create a new database, are all the RS servers in a web
farm?
The following steps are for your reference:
1. On another server, install RS and let it create a new LOCAL ReportServer
database (for example, ReportServerTestOnly) from scratch. Install RS SP2.
2. Test installation by browsing to localhost/reportserver and
localhost/reports.
Make sure it works fine before continue with the folloiwng steps.
3. Use rsconfig to make the new RS point to the original RS database:
"RSConfig -c -m <computername> -s <SQL Server instance name> -d <Reporting
Services database name> -a Sql|Windows -u <User name> -p <User password>"
(without the quotation marks)
Note For more information about the Rsconfig.exe command-line utility, run
the following command at a command prompt: "RSConfig /?" (without the
quotation marks)
IISReset
net stop reportserver
net start reportserver
4. Test it by browsing to localhost/reportserver and localhost/reports
If it fails, the original RS database may have problems.
If it succeees, you can remove and reinstall RS and RS SP2 on the original
problematic RS server and point back to the original RS database.
For more information, you can refer to the following article:
842425 How to move a Reporting Services database from a computer that is
http://support.microsoft.com/?id=842425
I hope the information is helpful.
Sophie Guo
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
=====================================================When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||Hi Sophie,
Great news after going back and doing a reinstall (command line) ... adding
the VPModule changes to the cofig files then installing SP2 and following
your rsconfig instructions things are working ...
Thank you so much for your assistance.
GH
"Sophie Guo [MSFT]" wrote:
> Hello,
> Rsconfig should be run only against report server catalog database and not
> against any database. Based on my research, if Rsconfig run against other
> database, it will corrupt the config files and the error "Could not find
> stored procedure 'GetDBVersion'" may occur.
> I am not clear about the current situation:
> > I tried this on another server, one I can bounce at will!! And it worked
> to install RS and RSSP2.
> Would you please answer the following questions to clarify?
> 1. When you installed RS on another server, have you created a new SQL SRS
> database? Please understand that we cannot be using the same SQL SRS
> database if they are not in a report server Web farm.
> 2. If you create a new SRS database, is it a local SQL server database? Do
> you mean you reproduced the issue on a new installation?
> 3. If you didn't create a new database, are all the RS servers in a web
> farm?
>
> The following steps are for your reference:
> 1. On another server, install RS and let it create a new LOCAL ReportServer
> database (for example, ReportServerTestOnly) from scratch. Install RS SP2.
> 2. Test installation by browsing to localhost/reportserver and
> localhost/reports.
> Make sure it works fine before continue with the folloiwng steps.
> 3. Use rsconfig to make the new RS point to the original RS database:
> "RSConfig -c -m <computername> -s <SQL Server instance name> -d <Reporting
> Services database name> -a Sql|Windows -u <User name> -p <User password>"
> (without the quotation marks)
> Note For more information about the Rsconfig.exe command-line utility, run
> the following command at a command prompt: "RSConfig /?" (without the
> quotation marks)
> IISReset
> net stop reportserver
> net start reportserver
>
> 4. Test it by browsing to localhost/reportserver and localhost/reports
> If it fails, the original RS database may have problems.
> If it succeees, you can remove and reinstall RS and RS SP2 on the original
> problematic RS server and point back to the original RS database.
> For more information, you can refer to the following article:
> 842425 How to move a Reporting Services database from a computer that is
> http://support.microsoft.com/?id=842425
> I hope the information is helpful.
>
> Sophie Guo
> Microsoft Online Partner Support
> Get Secure! - www.microsoft.com/security
> =====================================================> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> =====================================================> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>
>
>

RS service won't start

I have RS 2005 on a Win 2003 SP1 x64 with SQL2005 & SQL 2000 installed. RS
was installed and running fine with several reports until one of my DC died.
I have a 2nd DC which I then had to install DHCP service, but other than that
everything else seems to running. Now the RS service wont start and I get the
following errors:
Event Type: Error
Event Source: Report Server Windows Service (SQL2005)
Event Category: Startup/Shutdown
Event ID: 121
Date: 6/2/2006
Time: 2:53:25 PM
User: N/A
Computer: ATHENA
Description:
The Remote Procedure Call (RPC) service failed to start.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Event Type: Error
Event Source: SQL Server Report Service
Event Category: None
Event ID: 0
Date: 6/2/2006
Time: 2:53:25 PM
User: N/A
Computer: ATHENA
Description:
Service cannot be started.
Microsoft.ReportingServices.Diagnostics.Utilities.UnknownUserNameException:
The user or group name 'LocalSystem' is not recognized.
at Microsoft.ReportingServices.Library.Native.NameToSid(String name)
at
Microsoft.ReportingServices.Library.ServiceAppDomainController.StartRPCServer(Boolean firstTime)
at
Microsoft.ReportingServices.Library.ServiceAppDomainController.Start(Boolean
firstTime)
at Microsoft.ReportingServices.NTService.ReportService.OnStart(String[]
args)
at System.ServiceProcess.ServiceBase.ServiceQueuedMainCallback(Object
state)
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
ANy ideas?
I assume the service for some reason is looking for the missing dc, but
where can I change the configuration?I have Windows 2000 server. I installed my IIS 5.0 and then installed MS SQL
Server 2005. I am using the Reporting Services Feature.I am able to create
projects and make reports but am not able to deploy them on the Report
Server.It seems like the Report Server is not configured.In the Reporting
Services Configuration window it gives a not configured legend on the Web
Server and Web Service Identity. The error that i get is :
Service cannot be started.
Microsoft.ReportingServices.Diagnostics.Utilities.UnknownUserNameException:
The user or group name 'WSR2K099\ASPNET' is not recognized.
I am new to SQL server 2005 reporting services plz help.
Thanks
saurabh
"Joe S." wrote:
> I have RS 2005 on a Win 2003 SP1 x64 with SQL2005 & SQL 2000 installed. RS
> was installed and running fine with several reports until one of my DC died.
> I have a 2nd DC which I then had to install DHCP service, but other than that
> everything else seems to running. Now the RS service wont start and I get the
> following errors:
> Event Type: Error
> Event Source: Report Server Windows Service (SQL2005)
> Event Category: Startup/Shutdown
> Event ID: 121
> Date: 6/2/2006
> Time: 2:53:25 PM
> User: N/A
> Computer: ATHENA
> Description:
> The Remote Procedure Call (RPC) service failed to start.
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
>
>
> Event Type: Error
> Event Source: SQL Server Report Service
> Event Category: None
> Event ID: 0
> Date: 6/2/2006
> Time: 2:53:25 PM
> User: N/A
> Computer: ATHENA
> Description:
> Service cannot be started.
> Microsoft.ReportingServices.Diagnostics.Utilities.UnknownUserNameException:
> The user or group name 'LocalSystem' is not recognized.
> at Microsoft.ReportingServices.Library.Native.NameToSid(String name)
> at
> Microsoft.ReportingServices.Library.ServiceAppDomainController.StartRPCServer(Boolean firstTime)
> at
> Microsoft.ReportingServices.Library.ServiceAppDomainController.Start(Boolean
> firstTime)
> at Microsoft.ReportingServices.NTService.ReportService.OnStart(String[]
> args)
> at System.ServiceProcess.ServiceBase.ServiceQueuedMainCallback(Object
> state)
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
>
> ANy ideas?
> I assume the service for some reason is looking for the missing dc, but
> where can I change the configuration?
>|||I solved my problem. Some how with the departure of the DC my RS config file
went back to the wrong account as outlined in this MS article with regards to
the system account. Hopefully this will solve ur problem also.
http://support.microsoft.com/kb/907267/en-us
"Saurabh" wrote:
> I have Windows 2000 server. I installed my IIS 5.0 and then installed MS SQL
> Server 2005. I am using the Reporting Services Feature.I am able to create
> projects and make reports but am not able to deploy them on the Report
> Server.It seems like the Report Server is not configured.In the Reporting
> Services Configuration window it gives a not configured legend on the Web
> Server and Web Service Identity. The error that i get is :
> Service cannot be started.
> Microsoft.ReportingServices.Diagnostics.Utilities.UnknownUserNameException:
> The user or group name 'WSR2K099\ASPNET' is not recognized.
> I am new to SQL server 2005 reporting services plz help.
> Thanks
> saurabh
> "Joe S." wrote:
> > I have RS 2005 on a Win 2003 SP1 x64 with SQL2005 & SQL 2000 installed. RS
> > was installed and running fine with several reports until one of my DC died.
> > I have a 2nd DC which I then had to install DHCP service, but other than that
> > everything else seems to running. Now the RS service wont start and I get the
> > following errors:
> >
> > Event Type: Error
> > Event Source: Report Server Windows Service (SQL2005)
> > Event Category: Startup/Shutdown
> > Event ID: 121
> > Date: 6/2/2006
> > Time: 2:53:25 PM
> > User: N/A
> > Computer: ATHENA
> > Description:
> > The Remote Procedure Call (RPC) service failed to start.
> >
> > For more information, see Help and Support Center at
> > http://go.microsoft.com/fwlink/events.asp.
> >
> >
> >
> >
> >
> > Event Type: Error
> > Event Source: SQL Server Report Service
> > Event Category: None
> > Event ID: 0
> > Date: 6/2/2006
> > Time: 2:53:25 PM
> > User: N/A
> > Computer: ATHENA
> > Description:
> > Service cannot be started.
> > Microsoft.ReportingServices.Diagnostics.Utilities.UnknownUserNameException:
> > The user or group name 'LocalSystem' is not recognized.
> > at Microsoft.ReportingServices.Library.Native.NameToSid(String name)
> > at
> > Microsoft.ReportingServices.Library.ServiceAppDomainController.StartRPCServer(Boolean firstTime)
> > at
> > Microsoft.ReportingServices.Library.ServiceAppDomainController.Start(Boolean
> > firstTime)
> > at Microsoft.ReportingServices.NTService.ReportService.OnStart(String[]
> > args)
> > at System.ServiceProcess.ServiceBase.ServiceQueuedMainCallback(Object
> > state)
> >
> > For more information, see Help and Support Center at
> > http://go.microsoft.com/fwlink/events.asp.
> >
> >
> > ANy ideas?
> >
> > I assume the service for some reason is looking for the missing dc, but
> > where can I change the configuration?
> >

RS on Win2003 cannot connect to Analysis Service

I have RS installed on Win 2003 (not domain controller) and SQL server/AS on
a Win 2000 machine. I have no problem openning the report locally through IE
on the RS machine (Win 2003). However, I could not open the same report from
client machines (XP professional, Win 2000). The error message says "An error
has occurred during report processing. (rsProcessingAborted) Get Online Help
Cannot create a connection to data source 'DataSourceName'.
(rsErrorOpeningConnection) Get Online Help
Database 'DatabaseName' does not exist. ".
If I pulish the same report to RS on a Win 2000 machines, I don't have any
problem to open the report from any of client machines. I guess it might
related to credentials not being passed correctly. What kind of configurate I
need on a Win 2003 machine.
Thanks.It is a security issue. IIS user on Win 2003 needs to be a member of OLAP
admins.
Regards,
Cem Demircioglu
"BBH" <BBH@.discussions.microsoft.com> wrote in message
news:13B92E7D-C230-4C94-94C2-65C9411FA1F0@.microsoft.com...
>I have RS installed on Win 2003 (not domain controller) and SQL server/AS
>on
> a Win 2000 machine. I have no problem openning the report locally through
> IE
> on the RS machine (Win 2003). However, I could not open the same report
> from
> client machines (XP professional, Win 2000). The error message says "An
> error
> has occurred during report processing. (rsProcessingAborted) Get Online
> Help
> Cannot create a connection to data source 'DataSourceName'.
> (rsErrorOpeningConnection) Get Online Help
> Database 'DatabaseName' does not exist. ".
> If I pulish the same report to RS on a Win 2000 machines, I don't have any
> problem to open the report from any of client machines. I guess it might
> related to credentials not being passed correctly. What kind of
> configurate I
> need on a Win 2003 machine.
> Thanks.
>|||Thanks fro your reply. Are you referring to the service account which starts
the IIS?
"Cem Demircioglu" wrote:
> It is a security issue. IIS user on Win 2003 needs to be a member of OLAP
> admins.
> Regards,
> Cem Demircioglu
>
> "BBH" <BBH@.discussions.microsoft.com> wrote in message
> news:13B92E7D-C230-4C94-94C2-65C9411FA1F0@.microsoft.com...
> >I have RS installed on Win 2003 (not domain controller) and SQL server/AS
> >on
> > a Win 2000 machine. I have no problem openning the report locally through
> > IE
> > on the RS machine (Win 2003). However, I could not open the same report
> > from
> > client machines (XP professional, Win 2000). The error message says "An
> > error
> > has occurred during report processing. (rsProcessingAborted) Get Online
> > Help
> > Cannot create a connection to data source 'DataSourceName'.
> > (rsErrorOpeningConnection) Get Online Help
> > Database 'DatabaseName' does not exist. ".
> >
> > If I pulish the same report to RS on a Win 2000 machines, I don't have any
> > problem to open the report from any of client machines. I guess it might
> > related to credentials not being passed correctly. What kind of
> > configurate I
> > need on a Win 2003 machine.
> >
> > Thanks.
> >
>
>|||I can't remember the account name but it is either IIS (IUSR*) or Report
Server account (NT Authority\Network Service). You can test it by granting
read access to everyone.
Analysis Manager > XYZ Cube > Database Roles > New ... > Membership:
Everyone
Use Windows NT integrated security on the server while creating the data
source.
Hope this helps.
Regards,
Cem Demircioglu
"BBH" <BBH@.discussions.microsoft.com> wrote in message
news:BB12FAB7-F3CE-42D8-8CD4-F3F707A0A0FF@.microsoft.com...
> Thanks fro your reply. Are you referring to the service account which
> starts
> the IIS?
> "Cem Demircioglu" wrote:
>> It is a security issue. IIS user on Win 2003 needs to be a member of OLAP
>> admins.
>> Regards,
>> Cem Demircioglu
>>
>> "BBH" <BBH@.discussions.microsoft.com> wrote in message
>> news:13B92E7D-C230-4C94-94C2-65C9411FA1F0@.microsoft.com...
>> >I have RS installed on Win 2003 (not domain controller) and SQL
>> >server/AS
>> >on
>> > a Win 2000 machine. I have no problem openning the report locally
>> > through
>> > IE
>> > on the RS machine (Win 2003). However, I could not open the same report
>> > from
>> > client machines (XP professional, Win 2000). The error message says "An
>> > error
>> > has occurred during report processing. (rsProcessingAborted) Get Online
>> > Help
>> > Cannot create a connection to data source 'DataSourceName'.
>> > (rsErrorOpeningConnection) Get Online Help
>> > Database 'DatabaseName' does not exist. ".
>> >
>> > If I pulish the same report to RS on a Win 2000 machines, I don't have
>> > any
>> > problem to open the report from any of client machines. I guess it
>> > might
>> > related to credentials not being passed correctly. What kind of
>> > configurate I
>> > need on a Win 2003 machine.
>> >
>> > Thanks.
>> >
>>

RS deactivated after upgrade from Win 2000 to W2k3

Hi,
After I have upgraded my server, RS stop working .
a.. The report server cannot decrypt the symmetric key used to access
sensitive or encrypted data in a report server database. You must either
restore a backup key or delete all encrypted content and then restart the
service. Check the documentation for more information.
(rsReportServerDisabled) Get Online Help
a.. Bad Data.
I have the Key (exported using the rskeymgmt utility)
But I can't reapply the key:
an "Unable to connect to the database" error appear when I try to reapply
the key.
I have lost a document on the Microsoft web site which explain the entire
process to reactivate RS.
Anyone has the link?
or can explain the procedure?
thanks
Jerome.You may need to use rsconfig to reset that database connection if it is
having issues:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/rsuiref/htm/cpu_rsconfig_v1_5f1e.asp
Here is an activation doc for the rsactivate utility:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/rsuiref/htm/cpu_rsconfig_v1_6yqq.asp
--
Douglas McDowell douglas@.nospam.solidqualitylearning.com
"Jéjé" <willgart_A_@.hotmail_A_.com> wrote in message
news:OSWdzrDJFHA.1360@.TK2MSFTNGP10.phx.gbl...
> Hi,
> After I have upgraded my server, RS stop working .
> a.. The report server cannot decrypt the symmetric key used to access
> sensitive or encrypted data in a report server database. You must either
> restore a backup key or delete all encrypted content and then restart the
> service. Check the documentation for more information.
> (rsReportServerDisabled) Get Online Help
> a.. Bad Data.
> I have the Key (exported using the rskeymgmt utility)
> But I can't reapply the key:
> an "Unable to connect to the database" error appear when I try to reapply
> the key.
> I have lost a document on the Microsoft web site which explain the entire
> process to reactivate RS.
> Anyone has the link?
> or can explain the procedure?
> thanks
> Jerome.
>|||I think this is the key management article you are referring to...
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/rsadmin/htm/arp_dbadmin_v1_98xh.asp?frame=true
"Jéjé" wrote:
> Hi,
> After I have upgraded my server, RS stop working .
> a.. The report server cannot decrypt the symmetric key used to access
> sensitive or encrypted data in a report server database. You must either
> restore a backup key or delete all encrypted content and then restart the
> service. Check the documentation for more information.
> (rsReportServerDisabled) Get Online Help
> a.. Bad Data.
> I have the Key (exported using the rskeymgmt utility)
> But I can't reapply the key:
> an "Unable to connect to the database" error appear when I try to reapply
> the key.
> I have lost a document on the Microsoft web site which explain the entire
> process to reactivate RS.
> Anyone has the link?
> or can explain the procedure?
> thanks
> Jerome.
>
>|||its ok
I'have found (or re-found ) the solution.
I have replaced the oledb32.dll file on the server by the 2.8 version
(instead-of the 2.7 version which is not upgraded during the Win2003
upgrade)
"Jéjé" <willgart_A_@.hotmail_A_.com> wrote in message
news:OSWdzrDJFHA.1360@.TK2MSFTNGP10.phx.gbl...
> Hi,
> After I have upgraded my server, RS stop working .
> a.. The report server cannot decrypt the symmetric key used to access
> sensitive or encrypted data in a report server database. You must either
> restore a backup key or delete all encrypted content and then restart the
> service. Check the documentation for more information.
> (rsReportServerDisabled) Get Online Help
> a.. Bad Data.
> I have the Key (exported using the rskeymgmt utility)
> But I can't reapply the key:
> an "Unable to connect to the database" error appear when I try to reapply
> the key.
> I have lost a document on the Microsoft web site which explain the entire
> process to reactivate RS.
> Anyone has the link?
> or can explain the procedure?
> thanks
> Jerome.
>