rsInvalidReportServerDatabase-Error after installing SP2

Hello all,
I have a W2003 Server machine running Sql Server 2000 SP4 and Reporting
Services with *now* installed SP2 (before SP1). After installing the service
pack, I get the following error (sry, its german):
"Die Version der Berichtsserver-Datenbank liegt in einem Format vor, das
nicht gültig ist oder nicht gelesen werden kann. Die gefundene Version ist
'C.0.6.51'; die erwartete Version ist 'C.0.6.54'. Aktualisieren Sie die
Version der Berichtsserver-Datenbank, und überprüfen Sie die Zugriffsrechte,
um den Vorgang fortzusetzen. (rsInvalidReportServerDatabase)"
Can you give me please some advice, what I can do, to get the current
version of the database? I made backups from the report databases, but did
not manage to extract the key for encoding.
Thank you in advance.
Sandra GeislerI found a solution (well, I hope so). I just opened the stored
procedure GetDBVersion in the ReportServer database and exchanged the
last digit of the version number. I then restarted the ReportServer
service and it worked!! I tried to execute a report and it was
produced. If I am noticing some side effects, I will post them here.

rsInvalidPolicyDefinition

Greetings,
I am running SQL Server 2005 Reporting Services on a SQL Server 2000
(sp4) database and am running into an issue after a domain migration
that is preventing me from modifying any of the security settings on
the report server.
When attempting to Delete or Modify security settings on a folder i
receive the following message:
The "<All the users w/ access to the folder>" role assignment is not
valid. The role assignment is either empty or it specifies a user or
group name that is already used in an existing role assignment for the
current item. (rsInvalidPolicyDefinition) Get Online Help.
Has anyone seen this before or have suggestions as to where to start
troubleshooting it?
Thanks in advance,
Ben SullinsI've found a work around by clicking 'Revert to Parent secruty' on
these folders then going back in and modifying them. This only happens
on folders where the same user/group is listed 2x. Not sure how that
happened but I'm guessing it had to do w/ our domain migration...
sullins602 wrote:
> Greetings,
> I am running SQL Server 2005 Reporting Services on a SQL Server 2000
> (sp4) database and am running into an issue after a domain migration
> that is preventing me from modifying any of the security settings on
> the report server.
> When attempting to Delete or Modify security settings on a folder i
> receive the following message:
> The "<All the users w/ access to the folder>" role assignment is not
> valid. The role assignment is either empty or it specifies a user or
> group name that is already used in an existing role assignment for the
> current item. (rsInvalidPolicyDefinition) Get Online Help.
> Has anyone seen this before or have suggestions as to where to start
> troubleshooting it?
> Thanks in advance,
> Ben Sullins

RS2005 setup blues

I installed RS2005(SP2) with a SQL2000(sp4) db. Both are on seperate Windoes 2003 servers. I configured the reports manager to connect to a different web site on the same server instead of default web site. There were no installation prohlems. The RS server is up and running , all the virtual directories setup etc. When I try to access the reports directory via: http://dev2/Reports or browse the reports virtual directory from IIS, I get a 401 access denied error. The RS log reads:

<Header>
<Product>Microsoft SQL Server Reporting Services Version 9.00.3042.00</Product>
<Locale>en-US</Locale>
<TimeZone>Eastern Daylight Time</TimeZone>
<Path>D:\ReportingServices2005\MSSQL.1\Reporting Services\LogFiles\ReportServerWebApp__07_10_2007_11_29_21.log</Path>
<SystemName>NWISTCST99</SystemName>
<OSName>Microsoft Windows NT 5.2.3790 Service Pack 2</OSName>
<OSVersion>5.2.3790.131072</OSVersion>
</Header>
w3wp!library!1!7/10/2007-11:29:22:: i INFO: Initializing ReportBuilderTrustLevel to '0' as specified in Configuration file.
w3wp!library!1!7/10/2007-11:29:22:: i INFO: Initializing MaxActiveReqForOneUser to '20' requests(s) as specified in Configuration file.
w3wp!library!1!7/10/2007-11:29:22:: i INFO: Initializing MaxScheduleWait to default value of '1' second(s) because it was not specified in Configuration file.
w3wp!library!1!7/10/2007-11:29:22:: i INFO: Initializing DatabaseQueryTimeout to default value of '30' second(s) because it was not specified in Configuration file.
w3wp!library!1!7/10/2007-11:29:22:: i INFO: Initializing ProcessRecycleOptions to default value of '0' because it was not specified in Configuration file.
w3wp!library!1!7/10/2007-11:29:22:: i INFO: Initializing RunningRequestsScavengerCycle to default value of '30' second(s) because it was not specified in Configuration file.
w3wp!library!1!7/10/2007-11:29:22:: i INFO: Initializing RunningRequestsDbCycle to default value of '30' second(s) because it was not specified in Configuration file.
w3wp!library!1!7/10/2007-11:29:22:: i INFO: Initializing RunningRequestsAge to default value of '30' second(s) because it was not specified in Configuration file.
w3wp!library!1!7/10/2007-11:29:22:: i INFO: Initializing CleanupCycleMinutes to default value of '10' minute(s) because it was not specified in Configuration file.
w3wp!library!1!7/10/2007-11:29:22:: i INFO: Initializing DailyCleanupMinuteOfDay to default value of '120' minutes since midnight because it was not specified in Configuration file.
w3wp!library!1!7/10/2007-11:29:22:: i INFO: Initializing WatsonFlags to default value of '1064' because it was not specified in Configuration file.
w3wp!library!1!7/10/2007-11:29:22:: i INFO: Initializing WatsonDumpOnExceptions to default value of 'Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException,Microsoft.ReportingServices.Modeling.InternalModelingException' because it was not specified in Configuration file.
w3wp!library!1!7/10/2007-11:29:22:: i INFO: Initializing WatsonDumpExcludeIfContainsExceptions to default value of 'System.Data.SqlClient.SqlException,System.Threading.ThreadAbortException' because it was not specified in Configuration file.
w3wp!library!1!7/10/2007-11:29:22:: i INFO: Initializing SecureConnectionLevel to default value of '1' because it was not specified in Configuration file.
w3wp!library!1!7/10/2007-11:29:22:: i INFO: Initializing DisplayErrorLink to 'True' as specified in Configuration file.
w3wp!library!1!7/10/2007-11:29:22:: i INFO: Initializing WebServiceUseFileShareStorage to default value of 'False' because it was not specified in Configuration file.
w3wp!ui!5!7/10/2007-11:29:30:: e ERROR: The request failed with HTTP status 401: Unauthorized.
w3wp!ui!5!7/10/2007-11:29:31:: e ERROR: HTTP status code --> 500
-Details--
System.Net.WebException: The request failed with HTTP status 401: Unauthorized.

at Microsoft.SqlServer.ReportingServices2005.RSConnection.GetSecureMethods()

at Microsoft.ReportingServices.UI.Global.RSWebServiceWrapper.GetSecureMethods()

at Microsoft.SqlServer.ReportingServices2005.RSConnection.IsSecureMethod(String methodname)

at Microsoft.SqlServer.ReportingServices2005.RSConnection.ValidateConnection()

at Microsoft.ReportingServices.UI.ReportingPage.EnsureHttpsLevel(HttpsLevel level)

at Microsoft.ReportingServices.UI.ReportingPage.ReportingPage_Init(Object sender, EventArgs args)

at System.EventHandler.Invoke(Object sender, EventArgs e)

at System.Web.UI.Control.OnInit(EventArgs e)

at System.Web.UI.Page.OnInit(EventArgs e)

at System.Web.UI.Control.InitRecursive(Control namingContainer)

at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
w3wp!ui!5!7/10/2007-11:29:32:: e ERROR: Exception in ShowErrorPage: System.Threading.ThreadAbortException: Thread was being aborted.
at System.Threading.Thread.AbortInternal()
at System.Threading.Thread.Abort(Object stateInfo)
at System.Web.HttpResponse.End()
at System.Web.HttpServerUtility.Transfer(String path, Boolean preserveForm)
at Microsoft.ReportingServices.UI.ReportingPage.ShowErrorPage(String errMsg) at at System.Threading.Thread.AbortInternal()
at System.Threading.Thread.Abort(Object stateInfo)
at System.Web.HttpResponse.End()
at System.Web.HttpServerUtility.Transfer(String path, Boolean preserveForm)
at Microsoft.ReportingServices.UI.ReportingPage.ShowErrorPage(String errMsg)

Please advise.

The RSweApplication.config in the ReportManager folder has the fully qualified URL to ReportServer<ReportServerUrl> and I have blanked out the <ReportServerVirtualDirectory>

Also the <UrlRoot> in rsreportserver.config in ReportServer folder points to the fully qualified URL to ReportServer.

What am I missing here ..?

Hello,

Can you hit http://<server>/ReportServer? This is the underlying worker site for the Web Application found at http://<server>/Reports.

Here is a blog post on troubleshooting 401 errors with IIS: http://blogs.msdn.com/david.wang/archive/2005/07/14/HOWTO_Diagnose_IIS_401_Access_Denied.aspx

You could be having a Kerberos issue because SQL and IIS are on different servers. Here is an blog post from Brian Kelley on troubleshooting Kerberos: http://blogs.sqlservercentral.com/blogs/brian_kelley/archive/2006/04/05/568.aspx.

Let me know if this doesn't help.

Larry

|||

When I try http://<web site>/ReportServer, I can get to it. It comes up with a version number:

10.32.12.204/ReportServer - /

Microsoft SQL Server Reporting Services Version 9.00.3042.00

I had the virtual directories set up for Integtated windows authentication only.

When I enable anonymous access, I do not get the 401 error but there is no way I can create folders, subscriptions set up users etc. There are only 3 links: Home (to the reports directory). My subscriptions that is empty (There are no items to show in this view) and a help link.

Something is missing here ...

|||

Setting the sites to use anonymous and having it work means that it is an IIS permissions issue, thus, a SSRS configuration issue. Your installation worked. Try changing the configuration file to use the IP address or the Fully Qualified Domain Name for the Report Server location. Take a look at the 401 troubleshooting article and see if it can help you track down the problem.

The reason that you can't do anything as anonymous is that the anonymous user does not have any rights in SSRS by default. For testing purposes, you could change the accound used for anonymous access (IUSR_<machine name>) to an account with Admin rights and you would be able to manage SSRS. By default, all Admins are given full rights to an SSRS installation.

Larry

|||

thanks a lot Larry,

change the config files from name to hard coded IP address resolved the issue. I had already re-installed RS and IIS and was running out of options.

|||

No problem! Glad to hear that it worked out!

Larry

RS2005 post installation problems

I am having frustrating errors on RS2005. Here is the scenario:

RS2005 with SQL2000 SP4 db.

Both the above are on 2 seperate servers Windows 2003 SP2.

The setup had no problems. Can see the RS up and running on the RS configuration.

web-interface not configured to default web site: I get a 401 error when I try to access the Reports manager viahttp://dev/Reports . This is my test site. Here is the error from RS logs:

<Header>
<Product>Microsoft SQL Server Reporting Services Version 9.00.3042.00</Product>
<Locale>en-US</Locale>
<TimeZone>Eastern Daylight Time</TimeZone>
<Path>D:\ReportingServices2005\MSSQL.1\Reporting Services\LogFiles\ReportServerWebApp__07_10_2007_11_29_21.log</Path>
<SystemName>NWISTCST99</SystemName>
<OSName>Microsoft Windows NT 5.2.3790 Service Pack 2</OSName>
<OSVersion>5.2.3790.131072</OSVersion>
</Header>
w3wp!library!1!7/10/2007-11:29:22:: i INFO: Initializing ReportBuilderTrustLevel to '0' as specified in Configuration file.
w3wp!library!1!7/10/2007-11:29:22:: i INFO: Initializing MaxActiveReqForOneUser to '20' requests(s) as specified in Configuration file.
w3wp!library!1!7/10/2007-11:29:22:: i INFO: Initializing MaxScheduleWait to default value of '1' second(s) because it was not specified in Configuration file.
w3wp!library!1!7/10/2007-11:29:22:: i INFO: Initializing DatabaseQueryTimeout to default value of '30' second(s) because it was not specified in Configuration file.
w3wp!library!1!7/10/2007-11:29:22:: i INFO: Initializing ProcessRecycleOptions to default value of '0' because it was not specified in Configuration file.
w3wp!library!1!7/10/2007-11:29:22:: i INFO: Initializing RunningRequestsScavengerCycle to default value of '30' second(s) because it was not specified in Configuration file.
w3wp!library!1!7/10/2007-11:29:22:: i INFO: Initializing RunningRequestsDbCycle to default value of '30' second(s) because it was not specified in Configuration file.
w3wp!library!1!7/10/2007-11:29:22:: i INFO: Initializing RunningRequestsAge to default value of '30' second(s) because it was not specified in Configuration file.
w3wp!library!1!7/10/2007-11:29:22:: i INFO: Initializing CleanupCycleMinutes to default value of '10' minute(s) because it was not specified in Configuration file.
w3wp!library!1!7/10/2007-11:29:22:: i INFO: Initializing DailyCleanupMinuteOfDay to default value of '120' minutes since midnight because it was not specified in Configuration file.
w3wp!library!1!7/10/2007-11:29:22:: i INFO: Initializing WatsonFlags to default value of '1064' because it was not specified in Configuration file.
w3wp!library!1!7/10/2007-11:29:22:: i INFO: Initializing WatsonDumpOnExceptions to default value of 'Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException,Microsoft.ReportingServices.Modeling.InternalModelingException' because it was not specified in Configuration file.
w3wp!library!1!7/10/2007-11:29:22:: i INFO: Initializing WatsonDumpExcludeIfContainsExceptions to default value of 'System.Data.SqlClient.SqlException,System.Threading.ThreadAbortException' because it was not specified in Configuration file.
w3wp!library!1!7/10/2007-11:29:22:: i INFO: Initializing SecureConnectionLevel to default value of '1' because it was not specified in Configuration file.
w3wp!library!1!7/10/2007-11:29:22:: i INFO: Initializing DisplayErrorLink to 'True' as specified in Configuration file.
w3wp!library!1!7/10/2007-11:29:22:: i INFO: Initializing WebServiceUseFileShareStorage to default value of 'False' because it was not specified in Configuration file.
w3wp!ui!5!7/10/2007-11:29:30:: e ERROR: The request failed with HTTP status 401: Unauthorized.
w3wp!ui!5!7/10/2007-11:29:31:: e ERROR: HTTP status code --> 500
---Details---
System.Net.WebException: The request failed with HTTP status 401: Unauthorized.

at Microsoft.SqlServer.ReportingServices2005.RSConnection.GetSecureMethods()

at Microsoft.ReportingServices.UI.Global.RSWebServiceWrapper.GetSecureMethods()

at Microsoft.SqlServer.ReportingServices2005.RSConnection.IsSecureMethod(String methodname)

at Microsoft.SqlServer.ReportingServices2005.RSConnection.ValidateConnection()

at Microsoft.ReportingServices.UI.ReportingPage.EnsureHttpsLevel(HttpsLevel level)

at Microsoft.ReportingServices.UI.ReportingPage.ReportingPage_Init(Object sender, EventArgs args)

at System.EventHandler.Invoke(Object sender, EventArgs e)

at System.Web.UI.Control.OnInit(EventArgs e)

at System.Web.UI.Page.OnInit(EventArgs e)

at System.Web.UI.Control.InitRecursive(Control namingContainer)

at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
w3wp!ui!5!7/10/2007-11:29:32:: e ERROR: Exception in ShowErrorPage: System.Threading.ThreadAbortException: Thread was being aborted.
at System.Threading.Thread.AbortInternal()
at System.Threading.Thread.Abort(Object stateInfo)
at System.Web.HttpResponse.End()
at System.Web.HttpServerUtility.Transfer(String path, Boolean preserveForm)
at Microsoft.ReportingServices.UI.ReportingPage.ShowErrorPage(String errMsg) at at System.Threading.Thread.AbortInternal()
at System.Threading.Thread.Abort(Object stateInfo)
at System.Web.HttpResponse.End()
at System.Web.HttpServerUtility.Transfer(String path, Boolean preserveForm)
at Microsoft.ReportingServices.UI.ReportingPage.ShowErrorPage(String errMsg)

Pls advise

thanks

HI,raghu1:

Verify your NTFS permissions for the users on the folder C:\Program Files\Microsoft SQL Server\MSSQL\Reporting Services\ReportServer.

He should have ("Read & Execute", "List Folder Content" and "Read").

In IIS for Reports and ReportServer app set Authenication method to "Basic authentication" from "Integrated Windows authentication".

If i misunderstand you about your question, please feel free to correct me and i will try to help you with more information.

I hope the above information will be helpful. If you have any issues or concerns, please let me know. It's my pleasure to be of assistance

|||

HI,raghu1:

We are marking this issue as "Answered". If you have any new findings or concerns, please feel free to unmark the issue.
Thank you for your understanding!

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

RS2003 Ent Install Failing

I get the following error when doing RSW2K3 ENT Installation on WS2K3 SP1
(DC) and SQL Server 2000 SP4 environment. There is no option to ignore the
Error 1603 message , the only option is to cancel and rollback the
installation.
There is a parsing error is in the "LoadRSCatalog" Function- (see end of log)
Has anyone seen this problem before, any suggestions greatefully
appreciated,
<Func Name='CService::~CService'>
Action 22:07:52: Do_sqlScript. Configuring Microsoft SQL Server
SQL_SUCCESS_WITH_INFO (1) in SQLDriverConnectW
sqlstate=01000, level=0, state=0, native_error=5701, msg=Changed database
context to 'master'.
sqlstate=01000, level=0, state=0, native_error=5703, msg=Changed language
setting to us_english.
use master
SQL_SUCCESS_WITH_INFO (1) in SQLExecDirectW
sqlstate=01000, level=0, state=1, native_error=5701, msg=Changed database
context to 'master'.
IF (DB_ID('ReportServer') IS NULL) BEGIN CREATE DATABASE ReportServer
COLLATE Latin1_General_CI_AS_KS_WS END
0
Action 22:07:52: Do_sqlScript. Configuring Microsoft SQL Server
Do_sqlScript: Running SQL Statement
SQL_SUCCESS_WITH_INFO (1) in SQLExecDirectW
sqlstate=01000, level=0, state=1, native_error=1805, msg=The CREATE DATABASE
process is allocating 0.63 MB on disk 'ReportServer'.
sqlstate=01000, level=0, state=1, native_error=1805, msg=The CREATE DATABASE
process is allocating 0.49 MB on disk 'ReportServer_log'.
ALTER DATABASE ReportServer SET RECOVERY FULL
0
IF CHARINDEX('\', 'NT AUTHORITY\NETWORK SERVICE') != 0 BEGIN EXEC
sp_grantlogin 'NT AUTHORITY\NETWORK SERVICE' END
0
SQL_SUCCESS_WITH_INFO (1) in SQLExecDirectW
sqlstate=01000, level=0, state=1, native_error=15481, msg=Granted login
access to 'NT AUTHORITY\NETWORK SERVICE'.
IF (DB_ID('ReportServerTempDB') IS NULL) BEGIN CREATE DATABASE
ReportServerTempDB COLLATE Latin1_General_CI_AS_KS_WS END
0
SQL_SUCCESS_WITH_INFO (1) in SQLExecDirectW
sqlstate=01000, level=0, state=1, native_error=1805, msg=The CREATE DATABASE
process is allocating 0.63 MB on disk 'ReportServerTempDB'.
sqlstate=01000, level=0, state=1, native_error=1805, msg=The CREATE DATABASE
process is allocating 0.49 MB on disk 'ReportServerTempDB_log'.
ALTER DATABASE ReportServerTempDB SET RECOVERY SIMPLE
0
use ReportServerTempDB
SQL_SUCCESS_WITH_INFO (1) in SQLExecDirectW
sqlstate=01000, level=0, state=1, native_error=5701, msg=Changed database
context to 'ReportServerTempDB'.
IF NOT EXISTS (SELECT * FROM dbo.sysusers WHERE name='RSExecRole' AND
issqlrole=1) EXEC sp_addrole 'RSExecRole'
0
SQL_SUCCESS_WITH_INFO (1) in SQLExecDirectW
sqlstate=01000, level=0, state=1, native_error=15424, msg=New role added.
DECLARE @.pname AS sysname DECLARE @.i AS INT IF LOWER('NT AUTHORITY\NETWORK
SERVICE') != 'sa' AND NOT EXISTS (SELECT db1.dbid FROM
master.dbo.sysdatabases AS db1, master.dbo.syslogins AS logins1 WHERE db1.sid
= logins1.sid AND logins1.name = 'NT AUTHORITY\NETWORK SERVICE' AND db1.name
= 'ReportServerTempDB') AND NOT EXISTS (SELECT users1.name FROM dbo.sysusers
AS users1, master.dbo.syslogins AS logins1 WHERE users1.sid = logins1.sid AND
logins1.name = 'NT AUTHORITY\NETWORK SERVICE') BEGIN SET @.i = 0 SET @.pname = 'NT AUTHORITY\NETWORK SERVICE' WHILE EXISTS (SELECT name FROM dbo.sysusers
WHERE name=@.pname) BEGIN SET @.i = @.i + 1 SET @.pname = @.pname +
CONVERT(NVARCHAR(10), @.i) END EXEC sp_grantdbaccess 'NT AUTHORITY\NETWORK
SERVICE', @.pname END
0
SQL_SUCCESS_WITH_INFO (1) in SQLExecDirectW
sqlstate=01000, level=0, state=1, native_error=15341, msg=Granted database
access to 'NT AUTHORITY\NETWORK SERVICE'.
DECLARE @.pname AS sysname IF LOWER('NT AUTHORITY\NETWORK SERVICE') != 'sa'
AND NOT EXISTS (SELECT db1.dbid FROM master.dbo.sysdatabases AS db1,
master.dbo.syslogins AS logins1 WHERE db1.sid = logins1.sid AND logins1.name
= 'NT AUTHORITY\NETWORK SERVICE' AND db1.name = 'ReportServerTempDB') BEGIN
SELECT @.pname = (SELECT users1.name FROM dbo.sysusers AS users1,
master.dbo.syslogins AS logins1 WHERE users1.sid = logins1.sid AND
logins1.name = 'NT AUTHORITY\NETWORK SERVICE') EXEC sp_addrolemember
'RSExecRole', @.pname END
0
SQL_SUCCESS_WITH_INFO (1) in SQLExecDirectW
sqlstate=01000, level=0, state=1, native_error=15488, msg='NT
AUTHORITY\NETWORK SERVICE' added to role 'RSExecRole'.
D:\Program Files\Microsoft SQL Server\MSSQL\Reporting
Services\ReportServer\CatalogTempDB.sql
17
Action 22:07:52: Do_sqlScript. Configuring Microsoft SQL Server
Do_sqlScript: Running SQL Script: D:\Program Files\Microsoft SQL
Server\MSSQL\Reporting Services\ReportServer\CatalogTempDB.sql
<Func Name='LoadRSCatalog'>
error parsing script file D:\Program Files\Microsoft SQL
Server\MSSQL\Reporting Services\ReportServer\CatalogTempDB.sql: 87
Error 29525. SQL Setup failed to execute a command for server configuration.
Refer to the Server error logs and setup logs for detailed error information.
MSI (s) (F4!C8) [22:08:37:874]: Product: Microsoft SQL Server 2000 Reporting
Services Enterprise Edition -- Error 29525. SQL Setup failed to execute a
command for server configuration. Refer to the Server error logs and setup
logs for detailed error information.
<EndFunc Name='SqlScriptHlpr' Return='1603' GetLastError='0'>
<EndFunc Name='Do_sqlScript' Return='1603' GetLastError='0'>
Gathering darwin properties for failure handling.
<Func Name='DisplayErrorDialog'>
regardsIts RS2000 Enterprise Edition not RSY2K3 ENT.
"Graham Smith" wrote:
> I get the following error when doing RSW2K3 ENT Installation on WS2K3 SP1
> (DC) and SQL Server 2000 SP4 environment. There is no option to ignore the
> Error 1603 message , the only option is to cancel and rollback the
> installation.
> There is a parsing error is in the "LoadRSCatalog" Function- (see end of log)
> Has anyone seen this problem before, any suggestions greatefully
> appreciated,
>
> <Func Name='CService::~CService'>
> Action 22:07:52: Do_sqlScript. Configuring Microsoft SQL Server
> SQL_SUCCESS_WITH_INFO (1) in SQLDriverConnectW
> sqlstate=01000, level=0, state=0, native_error=5701, msg=Changed database
> context to 'master'.
> sqlstate=01000, level=0, state=0, native_error=5703, msg=Changed language
> setting to us_english.
> use master
> SQL_SUCCESS_WITH_INFO (1) in SQLExecDirectW
> sqlstate=01000, level=0, state=1, native_error=5701, msg=Changed database
> context to 'master'.
> IF (DB_ID('ReportServer') IS NULL) BEGIN CREATE DATABASE ReportServer
> COLLATE Latin1_General_CI_AS_KS_WS END
> 0
> Action 22:07:52: Do_sqlScript. Configuring Microsoft SQL Server
> Do_sqlScript: Running SQL Statement
> SQL_SUCCESS_WITH_INFO (1) in SQLExecDirectW
> sqlstate=01000, level=0, state=1, native_error=1805, msg=The CREATE DATABASE
> process is allocating 0.63 MB on disk 'ReportServer'.
> sqlstate=01000, level=0, state=1, native_error=1805, msg=The CREATE DATABASE
> process is allocating 0.49 MB on disk 'ReportServer_log'.
> ALTER DATABASE ReportServer SET RECOVERY FULL
> 0
> IF CHARINDEX('\', 'NT AUTHORITY\NETWORK SERVICE') != 0 BEGIN EXEC
> sp_grantlogin 'NT AUTHORITY\NETWORK SERVICE' END
> 0
> SQL_SUCCESS_WITH_INFO (1) in SQLExecDirectW
> sqlstate=01000, level=0, state=1, native_error=15481, msg=Granted login
> access to 'NT AUTHORITY\NETWORK SERVICE'.
> IF (DB_ID('ReportServerTempDB') IS NULL) BEGIN CREATE DATABASE
> ReportServerTempDB COLLATE Latin1_General_CI_AS_KS_WS END
> 0
> SQL_SUCCESS_WITH_INFO (1) in SQLExecDirectW
> sqlstate=01000, level=0, state=1, native_error=1805, msg=The CREATE DATABASE
> process is allocating 0.63 MB on disk 'ReportServerTempDB'.
> sqlstate=01000, level=0, state=1, native_error=1805, msg=The CREATE DATABASE
> process is allocating 0.49 MB on disk 'ReportServerTempDB_log'.
> ALTER DATABASE ReportServerTempDB SET RECOVERY SIMPLE
> 0
> use ReportServerTempDB
> SQL_SUCCESS_WITH_INFO (1) in SQLExecDirectW
> sqlstate=01000, level=0, state=1, native_error=5701, msg=Changed database
> context to 'ReportServerTempDB'.
> IF NOT EXISTS (SELECT * FROM dbo.sysusers WHERE name='RSExecRole' AND
> issqlrole=1) EXEC sp_addrole 'RSExecRole'
> 0
> SQL_SUCCESS_WITH_INFO (1) in SQLExecDirectW
> sqlstate=01000, level=0, state=1, native_error=15424, msg=New role added.
> DECLARE @.pname AS sysname DECLARE @.i AS INT IF LOWER('NT AUTHORITY\NETWORK
> SERVICE') != 'sa' AND NOT EXISTS (SELECT db1.dbid FROM
> master.dbo.sysdatabases AS db1, master.dbo.syslogins AS logins1 WHERE db1.sid
> = logins1.sid AND logins1.name = 'NT AUTHORITY\NETWORK SERVICE' AND db1.name
> = 'ReportServerTempDB') AND NOT EXISTS (SELECT users1.name FROM dbo.sysusers
> AS users1, master.dbo.syslogins AS logins1 WHERE users1.sid = logins1.sid AND
> logins1.name = 'NT AUTHORITY\NETWORK SERVICE') BEGIN SET @.i = 0 SET @.pname => 'NT AUTHORITY\NETWORK SERVICE' WHILE EXISTS (SELECT name FROM dbo.sysusers
> WHERE name=@.pname) BEGIN SET @.i = @.i + 1 SET @.pname = @.pname +
> CONVERT(NVARCHAR(10), @.i) END EXEC sp_grantdbaccess 'NT AUTHORITY\NETWORK
> SERVICE', @.pname END
> 0
> SQL_SUCCESS_WITH_INFO (1) in SQLExecDirectW
> sqlstate=01000, level=0, state=1, native_error=15341, msg=Granted database
> access to 'NT AUTHORITY\NETWORK SERVICE'.
> DECLARE @.pname AS sysname IF LOWER('NT AUTHORITY\NETWORK SERVICE') != 'sa'
> AND NOT EXISTS (SELECT db1.dbid FROM master.dbo.sysdatabases AS db1,
> master.dbo.syslogins AS logins1 WHERE db1.sid = logins1.sid AND logins1.name
> = 'NT AUTHORITY\NETWORK SERVICE' AND db1.name = 'ReportServerTempDB') BEGIN
> SELECT @.pname = (SELECT users1.name FROM dbo.sysusers AS users1,
> master.dbo.syslogins AS logins1 WHERE users1.sid = logins1.sid AND
> logins1.name = 'NT AUTHORITY\NETWORK SERVICE') EXEC sp_addrolemember
> 'RSExecRole', @.pname END
> 0
> SQL_SUCCESS_WITH_INFO (1) in SQLExecDirectW
> sqlstate=01000, level=0, state=1, native_error=15488, msg='NT
> AUTHORITY\NETWORK SERVICE' added to role 'RSExecRole'.
> D:\Program Files\Microsoft SQL Server\MSSQL\Reporting
> Services\ReportServer\CatalogTempDB.sql
> 17
> Action 22:07:52: Do_sqlScript. Configuring Microsoft SQL Server
> Do_sqlScript: Running SQL Script: D:\Program Files\Microsoft SQL
> Server\MSSQL\Reporting Services\ReportServer\CatalogTempDB.sql
> <Func Name='LoadRSCatalog'>
> error parsing script file D:\Program Files\Microsoft SQL
> Server\MSSQL\Reporting Services\ReportServer\CatalogTempDB.sql: 87
> Error 29525. SQL Setup failed to execute a command for server configuration.
> Refer to the Server error logs and setup logs for detailed error information.
> MSI (s) (F4!C8) [22:08:37:874]: Product: Microsoft SQL Server 2000 Reporting
> Services Enterprise Edition -- Error 29525. SQL Setup failed to execute a
> command for server configuration. Refer to the Server error logs and setup
> logs for detailed error information.
> <EndFunc Name='SqlScriptHlpr' Return='1603' GetLastError='0'>
> <EndFunc Name='Do_sqlScript' Return='1603' GetLastError='0'>
> Gathering darwin properties for failure handling.
> <Func Name='DisplayErrorDialog'>
> regards
>

RS2000 Cannot find server or DNS

I have installed Reporting Services 2000 SP2 and Windows Server2000 SP4.
At first access from the Client-PC (Windows XP SP2) with
http://myserver/Reports
I get always a
"Cannot find server or DNS"
error.
With Second Start Internet Explorer with http://myserver/Reports
the ReportServer works perfect.
Thanks for a tip.
ReinfriedI'm having a similar problem with RS 2000 SP2. Was there any resolution to
this?
Andrew.
"Reinfried" wrote:
> I have installed Reporting Services 2000 SP2 and Windows Server2000 SP4.
> At first access from the Client-PC (Windows XP SP2) with
> http://myserver/Reports
> I get always a
> "Cannot find server or DNS"
> error.
> With Second Start Internet Explorer with http://myserver/Reports
> the ReportServer works perfect.
> Thanks for a tip.
> Reinfried
>

RS SP2 Upgrade

Hi,
We use two IIS machine hosting each an instance of Report Server. The RS
database is located on a SQL2000 SP4 cluster where no component of RS is
installed except the RS and RSTempDB databases.
We upgraded each IIS machine and the setup completed without any errors or
warning. In the release notes for SP2, it is told that the database server
needs also to be upgraded. But there are no RS components installed on the
SQL cluster and by the way nothing to upgrade.
Is this a bug on the release notes ? Is the database upgraded by the update
process on a report server machine ?
Or do I need to do anything else to upgrade the database ? How can I check
if the database was upgraded or not ?
Thanks in advance.
SBIt sounds like you have a web farm. The process of upgrading RS will upgrade
the database.
Note that you will want to upgrade your development (report designer).
Especially if you skipped SP1.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"BENHAMOU Stéphane" <BENHAMOUStphane@.discussions.microsoft.com> wrote in
message news:E26F48E0-155E-41B6-8BCF-69D4605F57BE@.microsoft.com...
> Hi,
> We use two IIS machine hosting each an instance of Report Server. The RS
> database is located on a SQL2000 SP4 cluster where no component of RS is
> installed except the RS and RSTempDB databases.
> We upgraded each IIS machine and the setup completed without any errors or
> warning. In the release notes for SP2, it is told that the database server
> needs also to be upgraded. But there are no RS components installed on the
> SQL cluster and by the way nothing to upgrade.
> Is this a bug on the release notes ? Is the database upgraded by the
> update
> process on a report server machine ?
> Or do I need to do anything else to upgrade the database ? How can I check
> if the database was upgraded or not ?
> Thanks in advance.
> SB|||Thanks for your answer.
Is there a way to check the database structure upgrade ?
I run a "select * from information_schema.columns" on an SP1 and then on the
SP2 database used by my web farm, and the number of columns is exactly the
same (206) for both versions.
Do you know what are the database structure changes ?
"Bruce L-C [MVP]" a écrit :
> It sounds like you have a web farm. The process of upgrading RS will upgrade
> the database.
> Note that you will want to upgrade your development (report designer).
> Especially if you skipped SP1.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "BENHAMOU Stéphane" <BENHAMOUStphane@.discussions.microsoft.com> wrote in
> message news:E26F48E0-155E-41B6-8BCF-69D4605F57BE@.microsoft.com...
> > Hi,
> >
> > We use two IIS machine hosting each an instance of Report Server. The RS
> > database is located on a SQL2000 SP4 cluster where no component of RS is
> > installed except the RS and RSTempDB databases.
> >
> > We upgraded each IIS machine and the setup completed without any errors or
> > warning. In the release notes for SP2, it is told that the database server
> > needs also to be upgraded. But there are no RS components installed on the
> > SQL cluster and by the way nothing to upgrade.
> >
> > Is this a bug on the release notes ? Is the database upgraded by the
> > update
> > process on a report server machine ?
> >
> > Or do I need to do anything else to upgrade the database ? How can I check
> > if the database was upgraded or not ?
> >
> > Thanks in advance.
> > SB
>
>

RS SP2 Install Hell

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

RS Printing Issues with SP2

Hi,
I'm creating some reports using SQL RS .
Windows 2000 SP4,
SQL Server 2000, Standard Edition, SP3a
Reporting Services 2000 - SP2 ( recently updated)
Had no problems while updating with the new SP2.
But realised that the Print option in SP2 isn't working for me.
In the Web environment,
When we output the report, we can right click and click on the print ...it's
getting the printer dialog and now it goes to the printer
So, it's printing the same zoomed report whatever is currently there on the
screen..say 50% or 70%.
That's fine...but that will not print all the pages in the report.
But this new SP which is supposed to solve that prob...got the print option
When u print the report...irrespective of what u've got on the screen or
what u've zoomed..it's printing the 100% and crossing the page boundaries and
printing the report on two pages, though the width was set to 8"
Can anyone help me in resolving this.
I'm using Report Viewer to render my report.
Surprisingly, when I installed the RS SP2 on the server ( Windows 2003
SBS),open the same report and click on the print Icon, I'm getting some Error
related to GDI, and the entire application is gettiing crashed.
Thanks in advance.
srinivasTry re-deploying the report and printing again. There are some attributes
that the printing function need that only show up after redeploying the
report.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"srinivas" <srinivas@.discussions.microsoft.com> wrote in message
news:E66C5E80-CDE3-4F78-8F42-EFE356652AEE@.microsoft.com...
> Hi,
> I'm creating some reports using SQL RS .
> Windows 2000 SP4,
> SQL Server 2000, Standard Edition, SP3a
> Reporting Services 2000 - SP2 ( recently updated)
> Had no problems while updating with the new SP2.
> But realised that the Print option in SP2 isn't working for me.
> In the Web environment,
> When we output the report, we can right click and click on the print
> ...it's
> getting the printer dialog and now it goes to the printer
> So, it's printing the same zoomed report whatever is currently there on
> the
> screen..say 50% or 70%.
> That's fine...but that will not print all the pages in the report.
> But this new SP which is supposed to solve that prob...got the print
> option
> When u print the report...irrespective of what u've got on the screen or
> what u've zoomed..it's printing the 100% and crossing the page boundaries
> and
> printing the report on two pages, though the width was set to 8"
> Can anyone help me in resolving this.
> I'm using Report Viewer to render my report.
> Surprisingly, when I installed the RS SP2 on the server ( Windows 2003
> SBS),open the same report and click on the print Icon, I'm getting some
> Error
> related to GDI, and the entire application is gettiing crashed.
> Thanks in advance.
> srinivas

RS on SQL 2000 SP4

Are there any issues or can I just install SP4 ?
JackWe were running SQL 2000 sp2 and upgraded to sp4 with no issues to RS - we
are currently running rs sp1. No gaurantees obviously from me - so I'd still
try it on a dev environment or mirror first. But I haven't run into any
problems.
--Cory
"Jack Nielsen" wrote:
> Are there any issues or can I just install SP4 ?
> Jack
>
>|||Didn't have any problem here.

RS installation Problem on Win2000

Hi,
I try to install reporting services on win2000 (sp4), everything went well.
when I try to access reports folder http://servername/reports I am getting
the follwoing error.
server has VS.NET 2003 and all latest service packs. I am trying for past
one three days to resolve this problem.
T I A.,
Nemani
Server Error in '/Reports' 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 XML file
c:\winnt\microsoft.net\framework\v1.1.4322\Config\machine.config could not
be loaded. Attempted to access an unloaded AppDomain.
Source Error:
[No relevant source lines]
Source File:
c:\winnt\microsoft.net\framework\v1.1.4322\Config\machine.config Line: 0Can you access http://servername/reportserver? It sounds like the ASP.NET
identity does not have access to the configuration files.
--
Brian Welcker
Group Program Manager
SQL Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"Nemani" <mnemani@.che.state.nm.us> wrote in message
news:eXNhiJEYEHA.2672@.TK2MSFTNGP09.phx.gbl...
> Hi,
> I try to install reporting services on win2000 (sp4), everything went
> well.
> when I try to access reports folder http://servername/reports I am getting
> the follwoing error.
> server has VS.NET 2003 and all latest service packs. I am trying for past
> one three days to resolve this problem.
> T I A.,
> Nemani
> Server Error in '/Reports' 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 XML file
> c:\winnt\microsoft.net\framework\v1.1.4322\Config\machine.config could not
> be loaded. Attempted to access an unloaded AppDomain.
> Source Error:
>
> [No relevant source lines]
>
> Source File:
> c:\winnt\microsoft.net\framework\v1.1.4322\Config\machine.config Line:
> 0
>|||Thank you for your response.
Yes, I can access http://servername/reportserver . I explicitly gave
permission to ASPNET account on Reports folder too. Still the error is same.
When I first installed the RS on the machine at that time it doesn't have
the Visual Studion.NET 2003, all it has is IIS, SQL 2000 (sp3a). I installed
the RS but it didn't worked. Then I installed Visual Studion.NET 2003 on the
machine but still the same problem.
Is Visual Studion.NET 2003 is madatory in order to run RS.
Thanks,
Nemani.
"Brian Welcker [MSFT]" <bwelcker@.online.microsoft.com> wrote in message
news:Ok2qp5MYEHA.2868@.TK2MSFTNGP09.phx.gbl...
> Can you access http://servername/reportserver? It sounds like the ASP.NET
> identity does not have access to the configuration files.
> --
> Brian Welcker
> Group Program Manager
> SQL Server Reporting Services
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> "Nemani" <mnemani@.che.state.nm.us> wrote in message
> news:eXNhiJEYEHA.2672@.TK2MSFTNGP09.phx.gbl...
> > Hi,
> > I try to install reporting services on win2000 (sp4), everything went
> > well.
> > when I try to access reports folder http://servername/reports I am
getting
> > the follwoing error.
> > server has VS.NET 2003 and all latest service packs. I am trying for
past
> > one three days to resolve this problem.
> >
> > T I A.,
> > Nemani
> > Server Error in '/Reports' 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 XML file
> > c:\winnt\microsoft.net\framework\v1.1.4322\Config\machine.config could
not
> > be loaded. Attempted to access an unloaded AppDomain.
> >
> > Source Error:
> >
> >
> > [No relevant source lines]
> >
> >
> > Source File:
> > c:\winnt\microsoft.net\framework\v1.1.4322\Config\machine.config
Line:
> > 0
> >
> >
>

RS Installation Problem

while installing RS2000 developer edition on windows2000 server with sp4 the
install wizard stopped on the screen "Installing Reporting Services" without
doing nothing.After a while there was an error message which wrote that
Error signature:
"ProdCode:(null) ProdVer:(null) Action:(null) ErrNum:0 Err0:Default
Err1:Normal Err2:0"
In the tecnicl information wrote this:
"D:\DOCUME~1\ADMINI~1\Temp\Man1B5.tmp
D:\ProgramFiles\Microsoft SQL Server\80\RS Setup Bootstrap\LOG\RSStp_.cab"
This server doesn't have access 2 the net is that the problem?In the RSMSI1.log wrote those lines:
=== Logging stopped: 27/10/2005 09:55:53 ===MSI (c) (4C:38): Note: 1: 1708
MSI (c) (4C:38): Product: Microsoft SQL Server 2000 Reporting Services
Developer Edition -- Installation failed.
MSI (c) (4C:38): Grabbed execution mutex.
MSI (c) (4C:38): Cleaning up uninstalled install packages, if any exist
MSI (c) (4C:38): MainEngineThread is returning 1603
=== Verbose logging stopped: 27/10/2005 09:55:53 ===
Can someone know somthing about this?
"ש×?×?×?" wrote:
> while installing RS2000 developer edition on windows2000 server with sp4 the
> install wizard stopped on the screen "Installing Reporting Services" without
> doing nothing.After a while there was an error message which wrote that
> Error signature:
> "ProdCode:(null) ProdVer:(null) Action:(null) ErrNum:0 Err0:Default
> Err1:Normal Err2:0"
> In the tecnicl information wrote this:
> "D:\DOCUME~1\ADMINI~1\Temp\Man1B5.tmp
> D:\ProgramFiles\Microsoft SQL Server\80\RS Setup Bootstrap\LOG\RSStp_.cab"
> This server doesn't have access 2 the net is that the problem?
>

RS Installation

Hi,
When I install RS on my W2K/SP4/IIS 5.0/SQL2K EE server, I got a msg at the
end of my installation that I must Initialize RS. I looked up and found
that I have to run RSACTIVATE with the -c option. When I did that via a CMD
prompt, I got:
"Failure Starting the web service:
The Report Server Web service has not generated a public key"
Anyone help me on this one?
Thanks,
SteveHey Steve,
yeah I had the similar problem on one of the servers. One thing you might
try to do is to export whatever keys there are in db (usually normal
behaving server has 3 keys, one is all nulls, but in your case there might
be only one non-null key. To check, go to MSRS db called Keys) and then
delete them from db and reapply the keys. All is done with rskeymgmt
utility. However I am not sure if this is going to work for you, it worked
on one of my machines and didn't on another. Check the help on key
management as well (i know the help docs suck right now, but still ...)
REMEMBER: this might completely screw your installation up and you will have
to reinstall. So i am not responsible for any damages