I have installed Reporting Services on a production server that host a
website using SQL Express. I have set up RS in the RS configuration manager
and got green button all the way down
Requesting http://www.xx.dk/reports replies:
The request failed with HTTP status 400: Bad Request.
Requesting http://www.xx.dk/reportserver replies:
The permissions granted to user 'TF4\ms' are insufficient for performing
this operation. (rsAccessDenied)
Any idea what the problem might be ?
--
Paul SHello Paul,
Based on my research, please check the following settings:
1. Make sure you disable the Anynomous Access on IIS for the reporting
services virtual directory.
2. Make sure you enable Windows Authentication on IIS
3. Make sure you have use the rsconfig utility to connect to the correct
SQL Instance for the report server.
4. Make sure you are using a correct identity for the application pool the
reporting services using. Please try to use a domain account with local
admin privilage to have a check.
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
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.|||1)
Anynomous Access is disabled for the reportServer dir. and the reports dir.
but not for the parent dir - the original dir for the website.
2)
Windows Authentication is enabled for the reports and the reportserver dir.
3)
I only have one - it's correct
4)
The application pool for both the ReportServer and the Report manager is
DefaultAppPool
ps. In database setup the credentials type is Service credentials
--
Paul S
"Wei Lu [MSFT]" wrote:
> Hello Paul,
> Based on my research, please check the following settings:
> 1. Make sure you disable the Anynomous Access on IIS for the reporting
> services virtual directory.
> 2. Make sure you enable Windows Authentication on IIS
> 3. Make sure you have use the rsconfig utility to connect to the correct
> SQL Instance for the report server.
> 4. Make sure you are using a correct identity for the application pool the
> reporting services using. Please try to use a domain account with local
> admin privilage to have a check.
> Sincerely,
> Wei Lu
> Microsoft Online Community Support
> ==================================================> 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 Paul,
1. Please run the rsconfig utility to specify a new connection to the sql
server:
rsconfig -c -s <SQLSERVERNAME> -d reportserver -a SQL -u SA -p <SAPASSWORD>
2. Please recreate an application pool for the report server and use a
domain account which have local admin privilage as the identity to have a
try.
Please let me know the result.
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
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 Wei Lu
Your suggestions gave the follwing:
1)
No Reporting Services instance found on localhost.
2)
I created a new user with local admin rights and used him when I created a
new app pool for the reports server - the report manager still uses
DefaultAppPool.
Why is it talking about localhost - I'm not using localhost. The values
specifid in the RS Configuration manager for Report Server Virtual Directory
is:
Name: ReportServer, Website xxx
accessing http://www.xxx.dk/reports gives
The request failed with HTTP status 400: Bad Request.
acessing http://www.xxx.dk/reportserver still gives The permissions granted
to user 'TF4\ms' are insufficient for performing this operation.
(rsAccessDenied)|||Hello Paul,
I would like to get the RSWebApplication.config file and
rsreportserver.config file in the report manager and report server folder.
By default, these two folders is located at :C:\Program Files\Microsoft SQL
Server\MSSQL.3\Reporting Services\
Also, please send me the screenshot for the Configuration Tool. Make sure
you have a default instance installed in the server.
You may zip the folder and send to me directly. I understand the
information may be sensitive to you. To get my real email addresss, please
remove the ONLINE in my display mail.
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
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 ,
How is everything going? Please feel free to let me know if you need any
assistance.
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
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've send you the information needed
--
Paul S
"Wei Lu [MSFT]" wrote:
> Hi ,
> How is everything going? Please feel free to let me know if you need any
> assistance.
> Sincerely,
> Wei Lu
> Microsoft Online Community Support
> ==================================================> 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 Paul,
From your rsreportserver.config file, I did not see the LogonUser
credential is applied. So please use the rsconfig utility to specify the
credential to connect to SQL Server Report Server.
rsconfig -c -s <SQLSERVERNAME> -d reportserver -a SQL -u SA -p <SAPASSWORD>
Sincerely yours,
Wei Lu
Microsoft Online Partner Support
=====================================================
PLEASE NOTE: The partner managed newsgroups are provided to assist with
break/fix
issues and simple how to questions.
We also love to hear your product feedback!
Let us know what you think by posting
- from the web interface: Partner Feedback
- from your newsreader: microsoft.private.directaccess.partnerfeedback.
We look forward to hearing from you!
======================================================When responding to posts, please "Reply to Group" via your newsreader so
that others
may learn and benefit from this issue.
======================================================This posting is provided "AS IS" with no warranties, and confers no rights.
======================================================.|||Hello Wei
I get an error message saying
'No reporting services instance found on localhost'
when I run the rsconfig utility
I have been going through this
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=143931&SiteID=1
but I have the folders mentioned.
Paul S
--
Paul S
"Wei Lu [MSFT]" wrote:
> Hello Paul,
> From your rsreportserver.config file, I did not see the LogonUser
> credential is applied. So please use the rsconfig utility to specify the
> credential to connect to SQL Server Report Server.
> rsconfig -c -s <SQLSERVERNAME> -d reportserver -a SQL -u SA -p <SAPASSWORD>
> Sincerely yours,
> Wei Lu
> Microsoft Online Partner Support
> =====================================================> PLEASE NOTE: The partner managed newsgroups are provided to assist with
> break/fix
> issues and simple how to questions.
> We also love to hear your product feedback!
> Let us know what you think by posting
> - from the web interface: Partner Feedback
> - from your newsreader: microsoft.private.directaccess.partnerfeedback.
> We look forward to hearing from you!
> ======================================================> When responding to posts, please "Reply to Group" via your newsreader so
> that others
> may learn and benefit from this issue.
> ======================================================> This posting is provided "AS IS" with no warranties, and confers no rights.
> ======================================================.
>|||Hello Paul,
According to your email, I found that you are going to configure your
Express instance in your computer.
Please try the following:
rsconfig -c -s <SQLSERVERNAME>\Express -d reportserver -a SQL -u SA -p
<SAPASSWORD>
Sincerely yours,
Wei Lu
Microsoft Online Partner Support
=====================================================
PLEASE NOTE: The partner managed newsgroups are provided to assist with
break/fix
issues and simple how to questions.
We also love to hear your product feedback!
Let us know what you think by posting
- from the web interface: Partner Feedback
- from your newsreader: microsoft.private.directaccess.partnerfeedback.
We look forward to hearing from you!
======================================================When responding to posts, please "Reply to Group" via your newsreader so
that others
may learn and benefit from this issue.
======================================================This posting is provided "AS IS" with no warranties, and confers no rights.
======================================================|||Issuing that command was what gave me the
'No reporting services instance found on localhost'
--
Paul S
"Wei Lu [MSFT]" wrote:
> Hello Paul,
> According to your email, I found that you are going to configure your
> Express instance in your computer.
> Please try the following:
> rsconfig -c -s <SQLSERVERNAME>\Express -d reportserver -a SQL -u SA -p
> <SAPASSWORD>
>
> Sincerely yours,
> Wei Lu
> Microsoft Online Partner Support
> =====================================================> PLEASE NOTE: The partner managed newsgroups are provided to assist with
> break/fix
> issues and simple how to questions.
> We also love to hear your product feedback!
> Let us know what you think by posting
> - from the web interface: Partner Feedback
> - from your newsreader: microsoft.private.directaccess.partnerfeedback.
> We look forward to hearing from you!
> ======================================================> When responding to posts, please "Reply to Group" via your newsreader so
> that others
> may learn and benefit from this issue.
> ======================================================> This posting is provided "AS IS" with no warranties, and confers no rights.
> ======================================================>|||Hello Paul,
I would like to know how many instances you installed in the machine.
Pleas run the MPS Report .
--
a. Download MPSReport tool from below URL:
<
http://download.microsoft.com/download/b/b/1/bb139fcb-4aac-4fe5-a579-30b0bd9
15706/MPSRPT_SETUPPerf.EXE>
b. Execute the tool on the computer, and if you are prompted "Include the
MSINFO32 report?", please type Y.
c. Please send the result file (CAB file) to me
To reach me, please remove the ONLINE in my display email address.
For detailed information about the MPS Report Tools, please refer to the
following link:
Microsoft Product Support's Reporting Tools
<http://www.microsoft.com/downloads/details.aspx?FamilyId=CEBF3C7C-7CA5-408F
-88B7-F9C79B7306C0&displaylang=en>
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
==================================================(This posting is provided "AS IS", with no warranties, and confers no
rights.)|||Hi ,
How is everything going? Please feel free to let me know if you need any
assistance.
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
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
I have just send you the described CAB file
--
Paul S
"Wei Lu [MSFT]" wrote:
> Hi ,
> How is everything going? Please feel free to let me know if you need any
> assistance.
> Sincerely,
> Wei Lu
> Microsoft Online Community Support
> ==================================================> 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.
>
Showing posts with label configuration. Show all posts
Showing posts with label configuration. Show all posts
Monday, March 26, 2012
Wednesday, March 21, 2012
RS2005 configuration problem ASPNET account and DBs
Hi all,
I have instaled SQL Server 2005 on my W2K SP4 machine. When I go to RS
configuration I get problems in two areas. First under "Web Service
Identity" no account is listed. ASPNET account is set up on my machine
correctly. Second, under "Database Setup" I can't set up dbs. When I
click "New" and create ReportServer db and then click "Apply" I get an
error that says something like "Virtual Directories have to be crated
first." Under IIS I have ReportServer and Reports directories.
What may be the problem?
Thanks,
StanHi, Stan
just for fun...try running the command line tool "aspnet_regiis -i"
(you can get to it from the VS.NET Command Prompt, or by opening a
regular cmd window and browsing to
c:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\)
Once that's run, open your IIS Manager, and check the virtual
directories for Reports and ReportServer web apps. Make sure that they
are running and that the .net mappings are setup appropriately in the
Configuration... > Mappings tab, and also check the security for those
2 folders (use windows auth).
Then try running the RS2005 config tool again, and setup the virtual
directories and apply changes before moving along the different steps
in the tool.
Hope that works.
Regards,
Thiago Silva
MCAD.NET
suslikovich wrote:
> Hi all,
> I have instaled SQL Server 2005 on my W2K SP4 machine. When I go to RS
> configuration I get problems in two areas. First under "Web Service
> Identity" no account is listed. ASPNET account is set up on my machine
> correctly. Second, under "Database Setup" I can't set up dbs. When I
> click "New" and create ReportServer db and then click "Apply" I get an
> error that says something like "Virtual Directories have to be crated
> first." Under IIS I have ReportServer and Reports directories.
> What may be the problem?
> Thanks,
> Stan|||Hi Thiago,
Thanks for the quick reply. I forgot to mention I ran 'aspnet_regiis
-i' but I need to look at othet things you mentioned about mappings and
security. I will do that tonight.
Thanks again,
Stan
tafs7 wrote:
> Hi, Stan
> just for fun...try running the command line tool "aspnet_regiis -i"
> (you can get to it from the VS.NET Command Prompt, or by opening a
> regular cmd window and browsing to
> c:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\)
> Once that's run, open your IIS Manager, and check the virtual
> directories for Reports and ReportServer web apps. Make sure that they
> are running and that the .net mappings are setup appropriately in the
> Configuration... > Mappings tab, and also check the security for those
> 2 folders (use windows auth).
> Then try running the RS2005 config tool again, and setup the virtual
> directories and apply changes before moving along the different steps
> in the tool.
> Hope that works.
> Regards,
> Thiago Silva
> MCAD.NET
> suslikovich wrote:
> > Hi all,
> > I have instaled SQL Server 2005 on my W2K SP4 machine. When I go to RS
> > configuration I get problems in two areas. First under "Web Service
> > Identity" no account is listed. ASPNET account is set up on my machine
> > correctly. Second, under "Database Setup" I can't set up dbs. When I
> > click "New" and create ReportServer db and then click "Apply" I get an
> > error that says something like "Virtual Directories have to be crated
> > first." Under IIS I have ReportServer and Reports directories.
> > What may be the problem?
> >
> > Thanks,
> >
> > Stan|||I did "aspnet_regiis -i" once again. Looked at IIS directories.
Mappings look ok. I am quite puzzled about where to check
authentication. In any case, the problem remains. Any other
suggestions?
Thanks,
Stan
suslikovich wrote:
> Hi Thiago,
> Thanks for the quick reply. I forgot to mention I ran 'aspnet_regiis
> -i' but I need to look at othet things you mentioned about mappings and
> security. I will do that tonight.
> Thanks again,
> Stan
> tafs7 wrote:
> > Hi, Stan
> >
> > just for fun...try running the command line tool "aspnet_regiis -i"
> > (you can get to it from the VS.NET Command Prompt, or by opening a
> > regular cmd window and browsing to
> > c:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\)
> >
> > Once that's run, open your IIS Manager, and check the virtual
> > directories for Reports and ReportServer web apps. Make sure that they
> > are running and that the .net mappings are setup appropriately in the
> > Configuration... > Mappings tab, and also check the security for those
> > 2 folders (use windows auth).
> >
> > Then try running the RS2005 config tool again, and setup the virtual
> > directories and apply changes before moving along the different steps
> > in the tool.
> >
> > Hope that works.
> >
> > Regards,
> > Thiago Silva
> > MCAD.NET
> >
> > suslikovich wrote:
> > > Hi all,
> > > I have instaled SQL Server 2005 on my W2K SP4 machine. When I go to RS
> > > configuration I get problems in two areas. First under "Web Service
> > > Identity" no account is listed. ASPNET account is set up on my machine
> > > correctly. Second, under "Database Setup" I can't set up dbs. When I
> > > click "New" and create ReportServer db and then click "Apply" I get an
> > > error that says something like "Virtual Directories have to be crated
> > > first." Under IIS I have ReportServer and Reports directories.
> > > What may be the problem?
> > >
> > > Thanks,
> > >
> > > Stansql
I have instaled SQL Server 2005 on my W2K SP4 machine. When I go to RS
configuration I get problems in two areas. First under "Web Service
Identity" no account is listed. ASPNET account is set up on my machine
correctly. Second, under "Database Setup" I can't set up dbs. When I
click "New" and create ReportServer db and then click "Apply" I get an
error that says something like "Virtual Directories have to be crated
first." Under IIS I have ReportServer and Reports directories.
What may be the problem?
Thanks,
StanHi, Stan
just for fun...try running the command line tool "aspnet_regiis -i"
(you can get to it from the VS.NET Command Prompt, or by opening a
regular cmd window and browsing to
c:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\)
Once that's run, open your IIS Manager, and check the virtual
directories for Reports and ReportServer web apps. Make sure that they
are running and that the .net mappings are setup appropriately in the
Configuration... > Mappings tab, and also check the security for those
2 folders (use windows auth).
Then try running the RS2005 config tool again, and setup the virtual
directories and apply changes before moving along the different steps
in the tool.
Hope that works.
Regards,
Thiago Silva
MCAD.NET
suslikovich wrote:
> Hi all,
> I have instaled SQL Server 2005 on my W2K SP4 machine. When I go to RS
> configuration I get problems in two areas. First under "Web Service
> Identity" no account is listed. ASPNET account is set up on my machine
> correctly. Second, under "Database Setup" I can't set up dbs. When I
> click "New" and create ReportServer db and then click "Apply" I get an
> error that says something like "Virtual Directories have to be crated
> first." Under IIS I have ReportServer and Reports directories.
> What may be the problem?
> Thanks,
> Stan|||Hi Thiago,
Thanks for the quick reply. I forgot to mention I ran 'aspnet_regiis
-i' but I need to look at othet things you mentioned about mappings and
security. I will do that tonight.
Thanks again,
Stan
tafs7 wrote:
> Hi, Stan
> just for fun...try running the command line tool "aspnet_regiis -i"
> (you can get to it from the VS.NET Command Prompt, or by opening a
> regular cmd window and browsing to
> c:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\)
> Once that's run, open your IIS Manager, and check the virtual
> directories for Reports and ReportServer web apps. Make sure that they
> are running and that the .net mappings are setup appropriately in the
> Configuration... > Mappings tab, and also check the security for those
> 2 folders (use windows auth).
> Then try running the RS2005 config tool again, and setup the virtual
> directories and apply changes before moving along the different steps
> in the tool.
> Hope that works.
> Regards,
> Thiago Silva
> MCAD.NET
> suslikovich wrote:
> > Hi all,
> > I have instaled SQL Server 2005 on my W2K SP4 machine. When I go to RS
> > configuration I get problems in two areas. First under "Web Service
> > Identity" no account is listed. ASPNET account is set up on my machine
> > correctly. Second, under "Database Setup" I can't set up dbs. When I
> > click "New" and create ReportServer db and then click "Apply" I get an
> > error that says something like "Virtual Directories have to be crated
> > first." Under IIS I have ReportServer and Reports directories.
> > What may be the problem?
> >
> > Thanks,
> >
> > Stan|||I did "aspnet_regiis -i" once again. Looked at IIS directories.
Mappings look ok. I am quite puzzled about where to check
authentication. In any case, the problem remains. Any other
suggestions?
Thanks,
Stan
suslikovich wrote:
> Hi Thiago,
> Thanks for the quick reply. I forgot to mention I ran 'aspnet_regiis
> -i' but I need to look at othet things you mentioned about mappings and
> security. I will do that tonight.
> Thanks again,
> Stan
> tafs7 wrote:
> > Hi, Stan
> >
> > just for fun...try running the command line tool "aspnet_regiis -i"
> > (you can get to it from the VS.NET Command Prompt, or by opening a
> > regular cmd window and browsing to
> > c:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\)
> >
> > Once that's run, open your IIS Manager, and check the virtual
> > directories for Reports and ReportServer web apps. Make sure that they
> > are running and that the .net mappings are setup appropriately in the
> > Configuration... > Mappings tab, and also check the security for those
> > 2 folders (use windows auth).
> >
> > Then try running the RS2005 config tool again, and setup the virtual
> > directories and apply changes before moving along the different steps
> > in the tool.
> >
> > Hope that works.
> >
> > Regards,
> > Thiago Silva
> > MCAD.NET
> >
> > suslikovich wrote:
> > > Hi all,
> > > I have instaled SQL Server 2005 on my W2K SP4 machine. When I go to RS
> > > configuration I get problems in two areas. First under "Web Service
> > > Identity" no account is listed. ASPNET account is set up on my machine
> > > correctly. Second, under "Database Setup" I can't set up dbs. When I
> > > click "New" and create ReportServer db and then click "Apply" I get an
> > > error that says something like "Virtual Directories have to be crated
> > > first." Under IIS I have ReportServer and Reports directories.
> > > What may be the problem?
> > >
> > > Thanks,
> > >
> > > Stansql
Monday, March 12, 2012
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.Saturday, February 25, 2012
RS Configuration
I'm working on a RS 2005 demonstration for my employer. On my equipment at home, the install goes just great. (winxp pro) On the server at work (that I have limited control over), I've managed most of the install successfully using the SQL 2005 Trial Edition, however, when using the RS Configuration Tool, the Web Services Identity won't allow me to enter anything, and when I try to connect to RS through the Management Studio, I get some warning saying that it recieved text/html when it was expecting text/xml or something like that, followed by a bunch of html.
The main difference I can see in these installations is that the one that won't work is on Win2000 Server. So, I guess the one question that springs to mind is: is there something inherently different about the IIS or ASP that I (or IT) needs to configure differently on this server? If not, any other assistance would be greatly appreciated.
ThanksThis is an issue with Windows 2000. Have a look at this thread. I hope the tips listed there will help.
Subscribe to:
Posts (Atom)