|
|
You're in the
sql server reporting services
group:RS SP2 Install Hell
sql server reporting services:
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
I 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 [quoted text, click to view] "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 [quoted text, click to view] "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. > > >
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 [quoted text, click to view] "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. > > > > > >
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: [quoted text, click to view] > 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.
Don't see what you're looking for? Try a search.
|
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
| home · blog · groups | Questions? Comments? Contact the dn |