Hi,
we have a web farm of two IIS servers, running under Windows 2003. Because of the security requirements, the servers are not part of a domain. After installing the Reporting Services on both machines, we have an activation problem: activation of the second server de-activates the first one and vice versa.
Following configuration is being used:
- Mirrored windows accounts are used to run RS windows and web services
- A SQL account is used to connect to the ReportServer database
- A mirrored account with RS administrative privileges is used to connect to another Report Server in the web farm
Is it possible at all to install the Reporting Server in such a configuration?
Please advise.
--
Regards,
Alex Korygin.do you copy the config files?
or do you use the rsconfig tool to setup the RS database connection?
Because RS generates an encrypted key at startup. This key is unique for
each computer.
Also, do you use the enterprise edition?
"Alex Korygin" <AlexKorygin@.discussions.microsoft.com> a écrit dans le
message de news:EDE0C681-C3D2-4BCC-A853-EEEA0312CAC5@.microsoft.com...
> Hi,
> we have a web farm of two IIS servers, running under Windows 2003. Because
of the security requirements, the servers are not part of a domain. After
installing the Reporting Services on both machines, we have an activation
problem: activation of the second server de-activates the first one and vice
versa.
> Following configuration is being used:
> - Mirrored windows accounts are used to run RS windows and web services
> - A SQL account is used to connect to the ReportServer database
> - A mirrored account with RS administrative privileges is used to connect
to another Report Server in the web farm
> Is it possible at all to install the Reporting Server in such a
configuration?
> Please advise.
> --
> Regards,
> Alex Korygin.|||Jéjé,
I'm sorry for not responding earlier. We use rsconfig utility to activate the Reporting Servers. And yes, we have the Enterprise edition installed. Does it have anything to do with the fact that we use mirrored accounts and domain names of each account are different?
There must be some way to work around. I hope we do not need a domain to get it working; not having the domain in the production environment is a commonly used case. Thanks.
--
Regards,
Alex Korygin.
"Jéjé" wrote:
> do you copy the config files?
> or do you use the rsconfig tool to setup the RS database connection?
> Because RS generates an encrypted key at startup. This key is unique for
> each computer.
> Also, do you use the enterprise edition?
>
> "Alex Korygin" <AlexKorygin@.discussions.microsoft.com> a écrit dans le
> message de news:EDE0C681-C3D2-4BCC-A853-EEEA0312CAC5@.microsoft.com...
> > Hi,
> >
> > we have a web farm of two IIS servers, running under Windows 2003. Because
> of the security requirements, the servers are not part of a domain. After
> installing the Reporting Services on both machines, we have an activation
> problem: activation of the second server de-activates the first one and vice
> versa.
> > Following configuration is being used:
> > - Mirrored windows accounts are used to run RS windows and web services
> > - A SQL account is used to connect to the ReportServer database
> > - A mirrored account with RS administrative privileges is used to connect
> to another Report Server in the web farm
> >
> > Is it possible at all to install the Reporting Server in such a
> configuration?
> > Please advise.
> >
> > --
> > Regards,
> >
> > Alex Korygin.
>
>
Showing posts with label iis. Show all posts
Showing posts with label iis. Show all posts
Monday, March 12, 2012
RS SP2 Upgrade
Hi,
We use two IIS machine hosting each an instance of Report Server. The RS
database is located on a SQL2000 SP4 cluster where no component of RS is
installed except the RS and RSTempDB databases.
We upgraded each IIS machine and the setup completed without any errors or
warning. In the release notes for SP2, it is told that the database server
needs also to be upgraded. But there are no RS components installed on the
SQL cluster and by the way nothing to upgrade.
Is this a bug on the release notes ? Is the database upgraded by the update
process on a report server machine ?
Or do I need to do anything else to upgrade the database ? How can I check
if the database was upgraded or not ?
Thanks in advance.
SBIt sounds like you have a web farm. The process of upgrading RS will upgrade
the database.
Note that you will want to upgrade your development (report designer).
Especially if you skipped SP1.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"BENHAMOU Stéphane" <BENHAMOUStphane@.discussions.microsoft.com> wrote in
message news:E26F48E0-155E-41B6-8BCF-69D4605F57BE@.microsoft.com...
> Hi,
> We use two IIS machine hosting each an instance of Report Server. The RS
> database is located on a SQL2000 SP4 cluster where no component of RS is
> installed except the RS and RSTempDB databases.
> We upgraded each IIS machine and the setup completed without any errors or
> warning. In the release notes for SP2, it is told that the database server
> needs also to be upgraded. But there are no RS components installed on the
> SQL cluster and by the way nothing to upgrade.
> Is this a bug on the release notes ? Is the database upgraded by the
> update
> process on a report server machine ?
> Or do I need to do anything else to upgrade the database ? How can I check
> if the database was upgraded or not ?
> Thanks in advance.
> SB|||Thanks for your answer.
Is there a way to check the database structure upgrade ?
I run a "select * from information_schema.columns" on an SP1 and then on the
SP2 database used by my web farm, and the number of columns is exactly the
same (206) for both versions.
Do you know what are the database structure changes ?
"Bruce L-C [MVP]" a écrit :
> It sounds like you have a web farm. The process of upgrading RS will upgrade
> the database.
> Note that you will want to upgrade your development (report designer).
> Especially if you skipped SP1.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "BENHAMOU Stéphane" <BENHAMOUStphane@.discussions.microsoft.com> wrote in
> message news:E26F48E0-155E-41B6-8BCF-69D4605F57BE@.microsoft.com...
> > Hi,
> >
> > We use two IIS machine hosting each an instance of Report Server. The RS
> > database is located on a SQL2000 SP4 cluster where no component of RS is
> > installed except the RS and RSTempDB databases.
> >
> > We upgraded each IIS machine and the setup completed without any errors or
> > warning. In the release notes for SP2, it is told that the database server
> > needs also to be upgraded. But there are no RS components installed on the
> > SQL cluster and by the way nothing to upgrade.
> >
> > Is this a bug on the release notes ? Is the database upgraded by the
> > update
> > process on a report server machine ?
> >
> > Or do I need to do anything else to upgrade the database ? How can I check
> > if the database was upgraded or not ?
> >
> > Thanks in advance.
> > SB
>
>
We use two IIS machine hosting each an instance of Report Server. The RS
database is located on a SQL2000 SP4 cluster where no component of RS is
installed except the RS and RSTempDB databases.
We upgraded each IIS machine and the setup completed without any errors or
warning. In the release notes for SP2, it is told that the database server
needs also to be upgraded. But there are no RS components installed on the
SQL cluster and by the way nothing to upgrade.
Is this a bug on the release notes ? Is the database upgraded by the update
process on a report server machine ?
Or do I need to do anything else to upgrade the database ? How can I check
if the database was upgraded or not ?
Thanks in advance.
SBIt sounds like you have a web farm. The process of upgrading RS will upgrade
the database.
Note that you will want to upgrade your development (report designer).
Especially if you skipped SP1.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"BENHAMOU Stéphane" <BENHAMOUStphane@.discussions.microsoft.com> wrote in
message news:E26F48E0-155E-41B6-8BCF-69D4605F57BE@.microsoft.com...
> Hi,
> We use two IIS machine hosting each an instance of Report Server. The RS
> database is located on a SQL2000 SP4 cluster where no component of RS is
> installed except the RS and RSTempDB databases.
> We upgraded each IIS machine and the setup completed without any errors or
> warning. In the release notes for SP2, it is told that the database server
> needs also to be upgraded. But there are no RS components installed on the
> SQL cluster and by the way nothing to upgrade.
> Is this a bug on the release notes ? Is the database upgraded by the
> update
> process on a report server machine ?
> Or do I need to do anything else to upgrade the database ? How can I check
> if the database was upgraded or not ?
> Thanks in advance.
> SB|||Thanks for your answer.
Is there a way to check the database structure upgrade ?
I run a "select * from information_schema.columns" on an SP1 and then on the
SP2 database used by my web farm, and the number of columns is exactly the
same (206) for both versions.
Do you know what are the database structure changes ?
"Bruce L-C [MVP]" a écrit :
> It sounds like you have a web farm. The process of upgrading RS will upgrade
> the database.
> Note that you will want to upgrade your development (report designer).
> Especially if you skipped SP1.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "BENHAMOU Stéphane" <BENHAMOUStphane@.discussions.microsoft.com> wrote in
> message news:E26F48E0-155E-41B6-8BCF-69D4605F57BE@.microsoft.com...
> > Hi,
> >
> > We use two IIS machine hosting each an instance of Report Server. The RS
> > database is located on a SQL2000 SP4 cluster where no component of RS is
> > installed except the RS and RSTempDB databases.
> >
> > We upgraded each IIS machine and the setup completed without any errors or
> > warning. In the release notes for SP2, it is told that the database server
> > needs also to be upgraded. But there are no RS components installed on the
> > SQL cluster and by the way nothing to upgrade.
> >
> > Is this a bug on the release notes ? Is the database upgraded by the
> > update
> > process on a report server machine ?
> >
> > Or do I need to do anything else to upgrade the database ? How can I check
> > if the database was upgraded or not ?
> >
> > Thanks in advance.
> > SB
>
>
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.
>
>
>
>
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.
>
>
>
>
Friday, March 9, 2012
RS on MS Cluster Active/Passive configuration
I have insatalled RS onto an Active Passive SQL Server with IIS installed on
the cluster
as well. I have configured RS on two node work with the same ReportServer
database.
I have moved virtual directory to Shared store...
And now I can run reports on localhost on two nodes,but from Shared store RS
works
only,when Node 1 is active.Then Node 2 is active i get error message :
The encrypted value for configuration setting Dsn cannot be decrypted.
(rsFailedToDecryptConfigInformation) Get Online Help
An internal error occurred on the report server. See the error log for more
details.
(rsInternalError) Get Online Help
My configuration :
MS cluster Active/Passive Windows 2003
SQL 2000 Enterprise + SP3a + Fix 859
RS enterprise + SP1
Any help and guidance in this arena would be appreciated. Thanks.oleg,
It appears that installing RS on an active passive cluster where both
instances of IIS use the same data store it not possible. The reason
is that the DSN information is encrypted per machine and is unique to
the machine. I tried to get luck and synch up the machine keys on the
memebers in the cluster but even after they were synched up, it was
still not possible to get it working. What I have opted to do instead
is to allow each instance of IIS (default web) in the A/P cluster to
respond to the name of the SQLCluster name. When I fail from one box
to the other I am still able to serve up the other version of reporting
services. So while I am not NLB'ing the cluster I am still able to
server two instances of RS. Best idea I have had so far. I am
researching into getting both machines to use the same encryption
algorythm.
Hope that helps.
oleg wrote:
> I have insatalled RS onto an Active Passive SQL Server with IIS
installed on
> the cluster
> as well. I have configured RS on two node work with the same
ReportServer
> database.
> I have moved virtual directory to Shared store...
> And now I can run reports on localhost on two nodes,but from Shared
store RS
> works
> only,when Node 1 is active.Then Node 2 is active i get error message
:
> The encrypted value for configuration setting Dsn cannot be
decrypted.
> (rsFailedToDecryptConfigInformation) Get Online Help
> An internal error occurred on the report server. See the error log
for more
> details.
> (rsInternalError) Get Online Help
> My configuration :
> MS cluster Active/Passive Windows 2003
> SQL 2000 Enterprise + SP3a + Fix 859
> RS enterprise + SP1
> Any help and guidance in this arena would be appreciated. Thanks.
the cluster
as well. I have configured RS on two node work with the same ReportServer
database.
I have moved virtual directory to Shared store...
And now I can run reports on localhost on two nodes,but from Shared store RS
works
only,when Node 1 is active.Then Node 2 is active i get error message :
The encrypted value for configuration setting Dsn cannot be decrypted.
(rsFailedToDecryptConfigInformation) Get Online Help
An internal error occurred on the report server. See the error log for more
details.
(rsInternalError) Get Online Help
My configuration :
MS cluster Active/Passive Windows 2003
SQL 2000 Enterprise + SP3a + Fix 859
RS enterprise + SP1
Any help and guidance in this arena would be appreciated. Thanks.oleg,
It appears that installing RS on an active passive cluster where both
instances of IIS use the same data store it not possible. The reason
is that the DSN information is encrypted per machine and is unique to
the machine. I tried to get luck and synch up the machine keys on the
memebers in the cluster but even after they were synched up, it was
still not possible to get it working. What I have opted to do instead
is to allow each instance of IIS (default web) in the A/P cluster to
respond to the name of the SQLCluster name. When I fail from one box
to the other I am still able to serve up the other version of reporting
services. So while I am not NLB'ing the cluster I am still able to
server two instances of RS. Best idea I have had so far. I am
researching into getting both machines to use the same encryption
algorythm.
Hope that helps.
oleg wrote:
> I have insatalled RS onto an Active Passive SQL Server with IIS
installed on
> the cluster
> as well. I have configured RS on two node work with the same
ReportServer
> database.
> I have moved virtual directory to Shared store...
> And now I can run reports on localhost on two nodes,but from Shared
store RS
> works
> only,when Node 1 is active.Then Node 2 is active i get error message
:
> The encrypted value for configuration setting Dsn cannot be
decrypted.
> (rsFailedToDecryptConfigInformation) Get Online Help
> An internal error occurred on the report server. See the error log
for more
> details.
> (rsInternalError) Get Online Help
> My configuration :
> MS cluster Active/Passive Windows 2003
> SQL 2000 Enterprise + SP3a + Fix 859
> RS enterprise + SP1
> Any help and guidance in this arena would be appreciated. Thanks.
RS on clustered server
I installed clustered sql2k5 with RS, and went through RS configuration without error. But got following errors when try to browser RS site, IIS is running:
For reports site, I got:
Server Error in '/Reports' Application.
Parser Error
Description: An error occurred during the parsing of a resource required to service this request. Please review the following specific parse error details and modify your source file appropriately.
Parser Error Message: Could not load type 'Microsoft.ReportingServices.UI.GlobalApp'.
Source Error:
|
Source File: D:\MSSQL.3\Reporting Services\ReportManager\global.asax Line: 1
Version Information: Microsoft .NET Framework Version:1.1.4322.2300; ASP.NET Version:1.1.4322.2300
For reportserver site, I got:
Server Error in '/ReportServer' Application.
Configuration Error
Description: An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately.
Parser Error Message: The format of the file 'ReportingServicesWebServer' is invalid.
Source Error:
|
Source File: D:\MSSQL.3\Reporting Services\ReportServer\web.config Line: 30
Assembly Load Trace: The following information can be helpful to determine why the assembly 'ReportingServicesWebServer' could not be loaded.
|
Version Information: Microsoft .NET Framework Version:1.1.4322.2300; ASP.NET Version:1.1.4322.2300
Any idea? Thanks.
The error message states that the RS virtual roots (/reports, /reportserver) are mapped to ASP.NET 1.1.
RS 2005 will only work with ASP.NET 2.0. You could try to delete the virtual roots and recreate them through the RS configuration tool, or you could try to manually change the mappings to use ASP.NET 2.0 directly in IISAdmin.
-- Robert
|||Tried that but didn't work. In fact, I reinstalled reporting service last week and it fixed the problem. Thanks.Wednesday, March 7, 2012
RS Installation
Hi,
When I install RS on my W2K/SP4/IIS 5.0/SQL2K EE server, I got a msg at the
end of my installation that I must Initialize RS. I looked up and found
that I have to run RSACTIVATE with the -c option. When I did that via a CMD
prompt, I got:
"Failure Starting the web service:
The Report Server Web service has not generated a public key"
Anyone help me on this one?
Thanks,
SteveHey Steve,
yeah I had the similar problem on one of the servers. One thing you might
try to do is to export whatever keys there are in db (usually normal
behaving server has 3 keys, one is all nulls, but in your case there might
be only one non-null key. To check, go to MSRS db called Keys) and then
delete them from db and reapply the keys. All is done with rskeymgmt
utility. However I am not sure if this is going to work for you, it worked
on one of my machines and didn't on another. Check the help on key
management as well (i know the help docs suck right now, but still ...)
REMEMBER: this might completely screw your installation up and you will have
to reinstall. So i am not responsible for any damages
When I install RS on my W2K/SP4/IIS 5.0/SQL2K EE server, I got a msg at the
end of my installation that I must Initialize RS. I looked up and found
that I have to run RSACTIVATE with the -c option. When I did that via a CMD
prompt, I got:
"Failure Starting the web service:
The Report Server Web service has not generated a public key"
Anyone help me on this one?
Thanks,
SteveHey Steve,
yeah I had the similar problem on one of the servers. One thing you might
try to do is to export whatever keys there are in db (usually normal
behaving server has 3 keys, one is all nulls, but in your case there might
be only one non-null key. To check, go to MSRS db called Keys) and then
delete them from db and reapply the keys. All is done with rskeymgmt
utility. However I am not sure if this is going to work for you, it worked
on one of my machines and didn't on another. Check the help on key
management as well (i know the help docs suck right now, but still ...)
REMEMBER: this might completely screw your installation up and you will have
to reinstall. So i am not responsible for any damages
RS install problem
When I try to browse th e reports directory from the IIS MAnager It bring up
a new
browser window with the message
" Unable to find
library'/aspnet_clien/system_web/1_1_4322/WebUIValidation.js'.Try placing the
file manually ,or reinstall by running aspnet_regiis -c"
I followed the instructions & ran aspnet_regiis.exe ,but it did'nt help
anything.Asp.NET Framework1.1 is alreaddy installed in the server.
Does anybody have any indeas.Any suggestions is greatly appreciated.Did you let RS install as the default website? If not, then that is your
problem.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"RanjanFord" <RanjanFord@.discussions.microsoft.com> wrote in message
news:002D0510-DE6B-4F3E-B1AA-B12E44A42C52@.microsoft.com...
> When I try to browse th e reports directory from the IIS MAnager It bring
> up
> a new
> browser window with the message
> " Unable to find
> library'/aspnet_clien/system_web/1_1_4322/WebUIValidation.js'.Try placing
> the
> file manually ,or reinstall by running aspnet_regiis -c"
> I followed the instructions & ran aspnet_regiis.exe ,but it did'nt help
> anything.Asp.NET Framework1.1 is alreaddy installed in the server.
> Does anybody have any indeas.Any suggestions is greatly appreciated.
>|||Thanks for replying bruce.
The tool took the Virtual Directory name "Reports" and "ReportServer" under
the default website of IIS.
Should I install it in a seperate website other than the default website'
Ranjan Mitra
FORD Motor co.
"Bruce L-C [MVP]" wrote:
> Did you let RS install as the default website? If not, then that is your
> problem.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "RanjanFord" <RanjanFord@.discussions.microsoft.com> wrote in message
> news:002D0510-DE6B-4F3E-B1AA-B12E44A42C52@.microsoft.com...
> > When I try to browse th e reports directory from the IIS MAnager It bring
> > up
> > a new
> > browser window with the message
> > " Unable to find
> > library'/aspnet_clien/system_web/1_1_4322/WebUIValidation.js'.Try placing
> > the
> > file manually ,or reinstall by running aspnet_regiis -c"
> >
> > I followed the instructions & ran aspnet_regiis.exe ,but it did'nt help
> > anything.Asp.NET Framework1.1 is alreaddy installed in the server.
> >
> > Does anybody have any indeas.Any suggestions is greatly appreciated.
> >
>
>
a new
browser window with the message
" Unable to find
library'/aspnet_clien/system_web/1_1_4322/WebUIValidation.js'.Try placing the
file manually ,or reinstall by running aspnet_regiis -c"
I followed the instructions & ran aspnet_regiis.exe ,but it did'nt help
anything.Asp.NET Framework1.1 is alreaddy installed in the server.
Does anybody have any indeas.Any suggestions is greatly appreciated.Did you let RS install as the default website? If not, then that is your
problem.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"RanjanFord" <RanjanFord@.discussions.microsoft.com> wrote in message
news:002D0510-DE6B-4F3E-B1AA-B12E44A42C52@.microsoft.com...
> When I try to browse th e reports directory from the IIS MAnager It bring
> up
> a new
> browser window with the message
> " Unable to find
> library'/aspnet_clien/system_web/1_1_4322/WebUIValidation.js'.Try placing
> the
> file manually ,or reinstall by running aspnet_regiis -c"
> I followed the instructions & ran aspnet_regiis.exe ,but it did'nt help
> anything.Asp.NET Framework1.1 is alreaddy installed in the server.
> Does anybody have any indeas.Any suggestions is greatly appreciated.
>|||Thanks for replying bruce.
The tool took the Virtual Directory name "Reports" and "ReportServer" under
the default website of IIS.
Should I install it in a seperate website other than the default website'
Ranjan Mitra
FORD Motor co.
"Bruce L-C [MVP]" wrote:
> Did you let RS install as the default website? If not, then that is your
> problem.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "RanjanFord" <RanjanFord@.discussions.microsoft.com> wrote in message
> news:002D0510-DE6B-4F3E-B1AA-B12E44A42C52@.microsoft.com...
> > When I try to browse th e reports directory from the IIS MAnager It bring
> > up
> > a new
> > browser window with the message
> > " Unable to find
> > library'/aspnet_clien/system_web/1_1_4322/WebUIValidation.js'.Try placing
> > the
> > file manually ,or reinstall by running aspnet_regiis -c"
> >
> > I followed the instructions & ran aspnet_regiis.exe ,but it did'nt help
> > anything.Asp.NET Framework1.1 is alreaddy installed in the server.
> >
> > Does anybody have any indeas.Any suggestions is greatly appreciated.
> >
>
>
Saturday, February 25, 2012
RS Authoring over the Internet
It appears that to enable true authoring over the internet, you need to
create local users on the RS/IIS box, and create identical SQL logins so
remote users can build their DSN's for their reports.
Other ideas?
JeffFor one, use AD groups in SQL.|||Nope, doesn't work. Just tried it again to verify. I created a local user on
the box, added him to a local group, created a login for the group, and
added the login to the database role.
When trying to connect over the internet using ISQLW for example, I get
"login failed for user 'erstesting'". Native SQL logins work just fine.
Jeff
"Jerry Nixon" <jerrynixon@.gmail.com> wrote in message
news:36f558cf.0410131248.5c092472@.posting.google.com...
> For one, use AD groups in SQL.
create local users on the RS/IIS box, and create identical SQL logins so
remote users can build their DSN's for their reports.
Other ideas?
JeffFor one, use AD groups in SQL.|||Nope, doesn't work. Just tried it again to verify. I created a local user on
the box, added him to a local group, created a login for the group, and
added the login to the database role.
When trying to connect over the internet using ISQLW for example, I get
"login failed for user 'erstesting'". Native SQL logins work just fine.
Jeff
"Jerry Nixon" <jerrynixon@.gmail.com> wrote in message
news:36f558cf.0410131248.5c092472@.posting.google.com...
> For one, use AD groups in SQL.
Tuesday, February 21, 2012
RS 2005 Web Parts
I am using the SQL 2005 Reporting Services web parts within a WSS site.
SQLRS uses IIS virtual smtp server for delivery which works fine.
Using the report explorer web part, when I setup a subscription, the
value in the To: field defaults to the uneditable <username> rather
than a full mail address (username@.somewhere.com).
Is there a way to change this behavior such that the To: field displays
the full maill address instead?
Thanks!You can't make the UI show the host name, but you can make the server apply
a host name if one is not present. In the RSReportServer.config file, in
the element DefaultHostName, set your hostname and all address which do not
have a host name will get the value in this field.
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
"Jim" <emailjeffp@.yahoo.com> wrote in message
news:1136576961.392050.65820@.g44g2000cwa.googlegroups.com...
>I am using the SQL 2005 Reporting Services web parts within a WSS site.
> SQLRS uses IIS virtual smtp server for delivery which works fine.
> Using the report explorer web part, when I setup a subscription, the
> value in the To: field defaults to the uneditable <username> rather
> than a full mail address (username@.somewhere.com).
> Is there a way to change this behavior such that the To: field displays
> the full maill address instead?
> Thanks!
>
SQLRS uses IIS virtual smtp server for delivery which works fine.
Using the report explorer web part, when I setup a subscription, the
value in the To: field defaults to the uneditable <username> rather
than a full mail address (username@.somewhere.com).
Is there a way to change this behavior such that the To: field displays
the full maill address instead?
Thanks!You can't make the UI show the host name, but you can make the server apply
a host name if one is not present. In the RSReportServer.config file, in
the element DefaultHostName, set your hostname and all address which do not
have a host name will get the value in this field.
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
"Jim" <emailjeffp@.yahoo.com> wrote in message
news:1136576961.392050.65820@.g44g2000cwa.googlegroups.com...
>I am using the SQL 2005 Reporting Services web parts within a WSS site.
> SQLRS uses IIS virtual smtp server for delivery which works fine.
> Using the report explorer web part, when I setup a subscription, the
> value in the To: field defaults to the uneditable <username> rather
> than a full mail address (username@.somewhere.com).
> Is there a way to change this behavior such that the To: field displays
> the full maill address instead?
> Thanks!
>
Subscribe to:
Comments (Atom)