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.

RSConfigTool.exe unhandled exception after patching SP2

After patching SQL2005 SP2, an unhandled exception occurred in RSConfigTool.exe.

The error message:

Unhandled exception has occurred in your application. If you click Continue, the application will ignore this error and attempt to continue. If you click Quit, the application will close immediately.

Not found.

Is this a known issue? Thanks.

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.Management.ManagementException: Not found
at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode)
at System.Management.PropertyData.RefreshPropertyInfo()
at System.Management.PropertyDataCollection.get_Item(String propertyName)
at System.Management.ManagementBaseObject.GetPropertyValue(String propertyName)
at System.Management.ManagementBaseObject.get_Item(String propertyName)
at ReportServicesConfigUI.WMIProvider.RSReportServerAdmin.get_IsSharePointIntegrated()
at ReportServicesConfigUI.ConfigurationManager.ResetStepStatus()
at ReportServicesConfigUI.ConfigurationManager.ChangeMachine()
at ReportServicesConfigUI.ConfigurationManager.LaunchDialog()
at ReportServicesConfigUI.ConfigurationManager.tsbConnect_Click(Object sender, EventArgs e)
at System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e)
at System.Windows.Forms.ToolStripButton.OnClick(EventArgs e)
at System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e)
at System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e)
at System.Windows.Forms.ToolStripItem.FireEventInteractive(EventArgs e, ToolStripItemEventType met)
at System.Windows.Forms.ToolStripItem.FireEvent(EventArgs e, ToolStripItemEventType met)
at System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
at System.Windows.Forms.ToolStrip.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
-
RSConfigTool
Assembly Version: 9.0.242.0
Win32 Version: 9.00.3042.00
CodeBase: file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/binn/RSConfigTool.exe
-
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
-
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
-
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
-
System.Xml
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
-
System.Management
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Management/2.0.0.0__b03f5f7f11d50a3a/System.Management.dll
-
System.ServiceProcess
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.ServiceProcess/2.0.0.0__b03f5f7f11d50a3a/System.ServiceProcess.dll
-
System.DirectoryServices
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.DirectoryServices/2.0.0.0__b03f5f7f11d50a3a/System.DirectoryServices.dll
-
System.Data
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_32/System.Data/2.0.0.0__b77a5c561934e089/System.Data.dll
-
System.Configuration
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
-
System.Transactions
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_32/System.Transactions/2.0.0.0__b77a5c561934e089/System.Transactions.dll
-
System.EnterpriseServices
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_32/System.EnterpriseServices/2.0.0.0__b03f5f7f11d50a3a/System.EnterpriseServices.dll
-
Accessibility
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/Accessibility/2.0.0.0__b03f5f7f11d50a3a/Accessibility.dll
-

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.

Bobby,

Could you, please, check, what version has this dll:

%Program Files%\Microsoft SQL Server\90\Shared\ReportingServicesWMI.dll

?

For SP2 it should be 2005.90.3042.0.

I would also recommend to take a look at this file: ReportingServices.mof or ReportingServicesXPSP2UP.mof, in the same location (you should find only one if them, depending on your OS). See if you find in your mof file a class called MSReportServer_Instance and a property of this class called IsSharePointIntegrated.

Mihaela

|||

Hi Mihaela,

ReportingServicesWMI.DLL version: 2005.090.3042.00

C:\Program Files\Microsoft SQL Server\90\Shared>findstr -i MSReportServer_Instance *.mof
ReportingServicesXPSP2up.mof://* Class: MSReportServer_Instance (lives in v9)
ReportingServicesXPSP2up.mof:class MSReportServer_Instance

Directory of C:\Program Files\Microsoft SQL Server\90\Shared

11/22/2006 10:00 PM 17,447 ReportingServicesXPSP2up.mof
10/14/2005 01:41 AM 23,138 sqlmgmproviderxpsp2up.mof
2 File(s) 40,585 bytes

OS version is Microsoft Windows [Version 5.2.3790]

|||

Bobby,

It seems that you have the right version of ReportingServicesWMI.dll.

First I would suggest to restart the WMI service and after this try to connect again using the config tool and see what is happening. The WMI service "long name" is Windows Management Instrumentation.

If this is still not working, I would suggest to restart your Reporting Services service and try to connect again using the config tool.

I would also suggest to take a look in the log files located here:

%Program Files%\Microsoft SQL Server\MSSQL.3\Reporting Services\LogFiles

You should look for a file whose name starts with ReportServerService or ReportServerService_main.

I would suggest to sort the files by Date Modified descending and, after you try to connect using the config tool and you see the exception, take a look at the newest log file for the Windows service and see what was logged there.

Mihaela

|||

Hi Mihaela,

After rebooting the box, RSConfigTool.exe is working...

Not sure why it didn't work before.

Thanks for your help.

Bobby Fu

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 on Vista. could it be any more difficult?

Well, I finally got RS2005 installed on Vista, only problem is, now it won't run. I've installed SP2 (Ctp) and still no joy. It just errors when attempting to access the web service.

Here's the error:

w3wp!library!5!01/08/2007-20:36:56:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException: An internal error occurred on the report server. See the error log for more details., ;
Info: Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException: An internal error occurred on the report server. See the error log for more details. > System.NullReferenceException: Object reference not set to an instance of an object.
at Microsoft.ReportingServices.Authentication.WindowsAuthentication.GetUserInfo(IIdentity& userIdentity, IntPtr& userId)
at Microsoft.ReportingServices.WebServer.WebServiceHelper.ConstructRSServiceObjectFromSecurityExtension()
at Microsoft.ReportingServices.WebServer.Global.ConstructRSServiceFromRequest()
at Microsoft.ReportingServices.WebServer.Global.get_Service()
at Microsoft.ReportingServices.WebServer.Global.ShouldRejectAntiDos()
at Microsoft.ReportingServices.WebServer.Global.Application_AuthenticateRequest(Object sender, EventArgs e)

Any clues anyone? I'm all out.

Cheers,

Paul

I get the exact same error when trying to access the WebService from WinXP SP2. RS is running on Windows Server 2003 SP2 and SQL server has SP2.

It should be added that I have implemented Forms authentication for RS, but it works like a charm for everything else, just not for the WebService access...

Did you ever get around it?

Anyone else has a clue?

|||

Here is a thread that may relate to this.

http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=463047&SiteID=17

cheers,

Andrew

RS2005 on Vista. could it be any more difficult?

Well, I finally got RS2005 installed on Vista, only problem is, now it won't run. I've installed SP2 (Ctp) and still no joy. It just errors when attempting to access the web service.

Here's the error:

w3wp!library!5!01/08/2007-20:36:56:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException: An internal error occurred on the report server. See the error log for more details., ;
Info: Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException: An internal error occurred on the report server. See the error log for more details. > System.NullReferenceException: Object reference not set to an instance of an object.
at Microsoft.ReportingServices.Authentication.WindowsAuthentication.GetUserInfo(IIdentity& userIdentity, IntPtr& userId)
at Microsoft.ReportingServices.WebServer.WebServiceHelper.ConstructRSServiceObjectFromSecurityExtension()
at Microsoft.ReportingServices.WebServer.Global.ConstructRSServiceFromRequest()
at Microsoft.ReportingServices.WebServer.Global.get_Service()
at Microsoft.ReportingServices.WebServer.Global.ShouldRejectAntiDos()
at Microsoft.ReportingServices.WebServer.Global.Application_AuthenticateRequest(Object sender, EventArgs e)

Any clues anyone? I'm all out.

Cheers,

Paul

I get the exact same error when trying to access the WebService from WinXP SP2. RS is running on Windows Server 2003 SP2 and SQL server has SP2.

It should be added that I have implemented Forms authentication for RS, but it works like a charm for everything else, just not for the WebService access...

Did you ever get around it?

Anyone else has a clue?

|||

Here is a thread that may relate to this.

http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=463047&SiteID=17

cheers,

Andrew

RS2005 cant'connect to server

Hi. Like some others here, I'm struggling to get a production install of
RS2005 (SP2). RS is installed on a dedicated W2K3 (SP2) server. The
database is on a separate SQL 2005 (SP2) server. With the help of some posts
here I finally am able to browse to Report Manager and also deploy reports
from VS2005, but only when local to the report server. On my own
workstation, I get "cannot display the page" when I try to browse to Report
Manager , and "connection could not be made to the report server" when I try
to deploy reports. I checked local intranet sites in IE, and the whole
segment is allowed (set in GP) so that isn't th problem. Do you have any
ideas why I can't connect to RS from a workstation on my network? Thanks.Hi,
"cannot display the page" seems to be an IIS layer problem. To help
identifying your problem, can you
-verify url used to browse reports (http://<yourserver>/Reports)
-verify your web request reach IIS (chek logs at
c:\windows\system32\logfiles\)
-verify Http Status code send back by IIS
Jean-Pierre Riehl
http://blog.djeepy1.net
http://www.bewise.fr
"Coop" <Coop@.discussions.microsoft.com> wrote in message
news:48452325-3B31-4318-A3B5-B82F388A591A@.microsoft.com...
> Hi. Like some others here, I'm struggling to get a production install of
> RS2005 (SP2). RS is installed on a dedicated W2K3 (SP2) server. The
> database is on a separate SQL 2005 (SP2) server. With the help of some
> posts
> here I finally am able to browse to Report Manager and also deploy reports
> from VS2005, but only when local to the report server. On my own
> workstation, I get "cannot display the page" when I try to browse to
> Report
> Manager , and "connection could not be made to the report server" when I
> try
> to deploy reports. I checked local intranet sites in IE, and the whole
> segment is allowed (set in GP) so that isn't th problem. Do you have any
> ideas why I can't connect to RS from a workstation on my network? Thanks.|||If you can browse locally (when logged into the server) then everything is
setup correctly. I think the issue here is that you have not configured
roles properly. By default if you are a member of the local administrators
group then you are in the role that allows you to deploy. RS has its own
roles, totally separate from database security. Add your user for your
workstation to the local administrator group on the server. Then give it all
a try.
Also, try fully qualify your server (I assume when local you just used
localhost). For instance try
http://servername.whatever.com/reports
My guess is this is an issue with RS roles.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Jean-Pierre Riehl" <jean-pierre.riehl@.b-e-w-i-s-e.fr> wrote in message
news:41E3F7CE-1559-41D5-B5BD-26129028BC7B@.microsoft.com...
> Hi,
> "cannot display the page" seems to be an IIS layer problem. To help
> identifying your problem, can you
> -verify url used to browse reports (http://<yourserver>/Reports)
> -verify your web request reach IIS (chek logs at
> c:\windows\system32\logfiles\)
> -verify Http Status code send back by IIS
>
> --
> Jean-Pierre Riehl
> http://blog.djeepy1.net
> http://www.bewise.fr
>
> "Coop" <Coop@.discussions.microsoft.com> wrote in message
> news:48452325-3B31-4318-A3B5-B82F388A591A@.microsoft.com...
>> Hi. Like some others here, I'm struggling to get a production install of
>> RS2005 (SP2). RS is installed on a dedicated W2K3 (SP2) server. The
>> database is on a separate SQL 2005 (SP2) server. With the help of some
>> posts
>> here I finally am able to browse to Report Manager and also deploy
>> reports
>> from VS2005, but only when local to the report server. On my own
>> workstation, I get "cannot display the page" when I try to browse to
>> Report
>> Manager , and "connection could not be made to the report server" when I
>> try
>> to deploy reports. I checked local intranet sites in IE, and the whole
>> segment is allowed (set in GP) so that isn't th problem. Do you have any
>> ideas why I can't connect to RS from a workstation on my network?
>> Thanks.
>

RS2005 + Sharepoint 2007; installation doesn't works...

Hi,
I try to setup a server to test the integration of RS with sharepoint 2007.
The SP2 is installed on the server and the Sharepoint addin installed too.
I have created a RS instance and setup this instance to support sharepoint.
but in the application management pages of sharepoint I don't see the
reporting services section like describe in the installation document.
so the installation doesn't works and I don't see any error anywhere.
my server is an x64 version (windows, sql and sharepoint are in x64)
what can I do to diagnose what's appends?
thanks.
Jerome.Here you mean email subscription or file shared.
For file shared subcsription, you can give the authentication when you
create the subscription ,the option is available in the same page.
For email, go to Report Configuration from menu and give the server name
for authentication, you need to change the report server config file. "Search
for "SMTP" and you can give your authentication etc...
Amarnath, MCTS.
"Jeje" wrote:
> Hi,
> I try to setup a server to test the integration of RS with sharepoint 2007.
> The SP2 is installed on the server and the Sharepoint addin installed too.
> I have created a RS instance and setup this instance to support sharepoint.
> but in the application management pages of sharepoint I don't see the
> reporting services section like describe in the installation document.
> so the installation doesn't works and I don't see any error anywhere.
> my server is an x64 version (windows, sql and sharepoint are in x64)
> what can I do to diagnose what's appends?
> thanks.
> Jerome.
>
>|||Sorry wrongly posted.
Amarnath, MCTS
"Amarnath" wrote:
> Here you mean email subscription or file shared.
> For file shared subcsription, you can give the authentication when you
> create the subscription ,the option is available in the same page.
> For email, go to Report Configuration from menu and give the server name
> for authentication, you need to change the report server config file. "Search
> for "SMTP" and you can give your authentication etc...
> Amarnath, MCTS.
> "Jeje" wrote:
> > Hi,
> >
> > I try to setup a server to test the integration of RS with sharepoint 2007.
> >
> > The SP2 is installed on the server and the Sharepoint addin installed too.
> > I have created a RS instance and setup this instance to support sharepoint.
> >
> > but in the application management pages of sharepoint I don't see the
> > reporting services section like describe in the installation document.
> >
> > so the installation doesn't works and I don't see any error anywhere.
> >
> > my server is an x64 version (windows, sql and sharepoint are in x64)
> >
> > what can I do to diagnose what's appends?
> >
> > thanks.
> >
> > Jerome.
> >
> >
> >|||Jeje
I am having the same problem.
I hope someone posts a solution.
Regards,
Ben
"Jeje" <willgart@.hotmail.com> wrote in message
news:%23JHwTBQbHHA.3616@.TK2MSFTNGP05.phx.gbl...
> Hi,
> I try to setup a server to test the integration of RS with sharepoint
> 2007.
> The SP2 is installed on the server and the Sharepoint addin installed too.
> I have created a RS instance and setup this instance to support
> sharepoint.
> but in the application management pages of sharepoint I don't see the
> reporting services section like describe in the installation document.
> so the installation doesn't works and I don't see any error anywhere.
> my server is an x64 version (windows, sql and sharepoint are in x64)
> what can I do to diagnose what's appends?
> thanks.
> Jerome.
>sql

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; the link is already there

http://www.microsoft.com/windowsserversystem/default.mspx
"Download SQL Reporting Services SP2 and New Report Packs
Get the latest downloads for SQL Server Reporting Services, including
Service Pack
2 and new report packs for IIS and Great Plains."But not the SP2!!!!!
--
Mary Bray [SQL Server MVP]
Please reply only to newsgroups
"Joerg" <Joerg@.discussions.microsoft.com> wrote in message
news:1E11120D-23DE-4A0C-B21C-942210C8F2F6@.microsoft.com...
> http://www.microsoft.com/windowsserversystem/default.mspx
> "Download SQL Reporting Services SP2 and New Report Packs
> Get the latest downloads for SQL Server Reporting Services, including
> Service Pack
> 2 and new report packs for IIS and Great Plains."
>
>
>|||Oops... looks like someone at MS posted the link a little too soon on
the Server home page since there is no mention of SP2 on the RS
homepage.|||It wouldn't be so bad...except that there is no SP and no news.
Somebody say something about it. Can I get a little count down timer?
Where is that magic 8 ball? Some guy is out there right now flipping
coins until his thumb rubs his index finger raw...and the only thing
we've got to go on is a typo of sorts on the server homepage.|||We MVPs are in the dark too. I really thought I would see it this month.
Hopefully it won't be too much longer.
--
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Luke" <lukeguerrant@.gmail.com> wrote in message
news:1112222701.375010.249600@.z14g2000cwz.googlegroups.com...
> It wouldn't be so bad...except that there is no SP and no news.
> Somebody say something about it. Can I get a little count down timer?
> Where is that magic 8 ball? Some guy is out there right now flipping
> coins until his thumb rubs his index finger raw...and the only thing
> we've got to go on is a typo of sorts on the server homepage.
>|||I know that SP2 is out there somewhere.
Could I prevail on anyone to tell me where I can get a copy?
Thanks
"Bruce L-C [MVP]" wrote:
> We MVPs are in the dark too. I really thought I would see it this month.
> Hopefully it won't be too much longer.
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Luke" <lukeguerrant@.gmail.com> wrote in message
> news:1112222701.375010.249600@.z14g2000cwz.googlegroups.com...
> > It wouldn't be so bad...except that there is no SP and no news.
> > Somebody say something about it. Can I get a little count down timer?
> > Where is that magic 8 ball? Some guy is out there right now flipping
> > coins until his thumb rubs his index finger raw...and the only thing
> > we've got to go on is a typo of sorts on the server homepage.
> >
>
>|||This link has been removed. I don't think that's a sign that they're about to
release it. But this is Microsoft. Have they ever released any software on
time?
"Joerg" wrote:
> http://www.microsoft.com/windowsserversystem/default.mspx
> "Download SQL Reporting Services SP2 and New Report Packs
> Get the latest downloads for SQL Server Reporting Services, including
> Service Pack
> 2 and new report packs for IIS and Great Plains."
>
>
>|||OK, here's the story. We are working very hard to finish up SP2. We had
planned to get it out by the end of March but we found a couple of issues
very late that we felt that we really needed to address. Couple this with
the fact that we are also the team that delivered the February Community
Technology preview of SQL Server 2005 Reporting Services and this means we
had to push back a little. We have now feel confident that SP2 will be out
by mid-April. Thank you for your patience and support.
--
Brian Welcker
Group Program Manager
Microsoft SQL Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"FritoBandido" <FritoBandido@.discussions.microsoft.com> wrote in message
news:945A4957-A365-4006-A7FF-3BA356280D13@.microsoft.com...
>I know that SP2 is out there somewhere.
> Could I prevail on anyone to tell me where I can get a copy?
> Thanks
> "Bruce L-C [MVP]" wrote:
>> We MVPs are in the dark too. I really thought I would see it this month.
>> Hopefully it won't be too much longer.
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>> "Luke" <lukeguerrant@.gmail.com> wrote in message
>> news:1112222701.375010.249600@.z14g2000cwz.googlegroups.com...
>> > It wouldn't be so bad...except that there is no SP and no news.
>> > Somebody say something about it. Can I get a little count down timer?
>> > Where is that magic 8 ball? Some guy is out there right now flipping
>> > coins until his thumb rubs his index finger raw...and the only thing
>> > we've got to go on is a typo of sorts on the server homepage.
>> >
>>|||On Thu, 31 Mar 2005 22:22:19 -0800, "Brian Welcker"
<bwelcker@.online.microsoft.com> wrote:
>OK, here's the story. We are working very hard to finish up SP2. We had
>planned to get it out by the end of March but we found a couple of issues
>very late that we felt that we really needed to address. Couple this with
>the fact that we are also the team that delivered the February Community
>Technology preview of SQL Server 2005 Reporting Services and this means we
>had to push back a little. We have now feel confident that SP2 will be out
>by mid-April. Thank you for your patience and support.
Good for you Brian. It's a hard choice and I'm glad I didn't have to
make it in this case, but ya done right in my opinion.
All you can do is all you can do. Hope you get some sleep some month
soon.
Highly Obscure|||I appreciate somebody saying SOMETHING. I mean...blow smoke, I am
alright with that even...as long as I have some kind of idea when to
expect the SP. Thank Brain...you are a stand up guy in my opinion. I
know that you guys want a good SP...as well as I. Just knowing when to
expect it makes my job easier.
I don't know about everyone else..but I am buying a whole server in
which to test SRS SP2...so having a time frame makes my life easier.|||can anyone confirm if rs-sp2 will have a report viewer control for winforms
and webforms ? - is this a pure .NET control or is it ActiveX
also where can i find a list of featuers/bugfixes for sp2?
thanks
"Joerg" wrote:
> http://www.microsoft.com/windowsserversystem/default.mspx
> "Download SQL Reporting Services SP2 and New Report Packs
> Get the latest downloads for SQL Server Reporting Services, including
> Service Pack
> 2 and new report packs for IIS and Great Plains."
>
>
>|||I can confirm that SP2 does not have the new webform/winform controls. That
will be coming out with the next beta of Widbey (next version of Visual
Studio).
--
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"ranga" <ranga@.discussions.microsoft.com> wrote in message
news:82EFEFC5-44F7-425D-84D9-90538A9BDA91@.microsoft.com...
> can anyone confirm if rs-sp2 will have a report viewer control for
winforms
> and webforms ? - is this a pure .NET control or is it ActiveX
> also where can i find a list of featuers/bugfixes for sp2?
> thanks
> "Joerg" wrote:
> > http://www.microsoft.com/windowsserversystem/default.mspx
> >
> > "Download SQL Reporting Services SP2 and New Report Packs
> > Get the latest downloads for SQL Server Reporting Services, including
> > Service Pack
> > 2 and new report packs for IIS and Great Plains."
> >
> >
> >
> >
> >
> >|||>> other posts in this group seem to indicate that client side printing is
one of
the major features of sp2 - have they pulled the plug on this feature for
sp2 ?
>> if client-side printing is not going to be in sp2, then what other alternative is there ? (using pdf is ok but getting adobe to start is a slow process ; popping up
a browser window in a winform app does not look clean; using a web browser
control in a windows-forms app is also not clean (the control does not have a
print button)
"Bruce L-C [MVP]" wrote:
> I can confirm that SP2 does not have the new webform/winform controls. That
> will be coming out with the next beta of Widbey (next version of Visual
> Studio).
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "ranga" <ranga@.discussions.microsoft.com> wrote in message
> news:82EFEFC5-44F7-425D-84D9-90538A9BDA91@.microsoft.com...
> > can anyone confirm if rs-sp2 will have a report viewer control for
> winforms
> > and webforms ? - is this a pure .NET control or is it ActiveX
> >
> > also where can i find a list of featuers/bugfixes for sp2?
> >
> > thanks
> >
> > "Joerg" wrote:
> >
> > > http://www.microsoft.com/windowsserversystem/default.mspx
> > >
> > > "Download SQL Reporting Services SP2 and New Report Packs
> > > Get the latest downloads for SQL Server Reporting Services, including
> > > Service Pack
> > > 2 and new report packs for IIS and Great Plains."
> > >
> > >
> > >
> > >
> > >
> > >
>
>|||Please look at the post that I responded to. It had nothing to do with
client side printing. I responded spefically about the new web and winform
report viewer controls.
SP2 WILL have the ability for client side printing. Two different things
here.
Also, in case you haven't seen, SP2 will be out mid month. It was delayed a
couple of weeks (originally they were targeting the end of March for
release).
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"ranga" <ranga@.discussions.microsoft.com> wrote in message
news:D03BC10F-F046-4EDA-8852-330ACD8BE054@.microsoft.com...
> >> other posts in this group seem to indicate that client side printing is
> one of
> the major features of sp2 - have they pulled the plug on this feature for
> sp2 ?
> >> if client-side printing is not going to be in sp2, then what other
alternative is there ? (using pdf is ok but getting adobe to start is a slow
process ; popping up
> a browser window in a winform app does not look clean; using a web browser
> control in a windows-forms app is also not clean (the control does not
have a
> print button)
>
> "Bruce L-C [MVP]" wrote:
> > I can confirm that SP2 does not have the new webform/winform controls.
That
> > will be coming out with the next beta of Widbey (next version of Visual
> > Studio).
> >
> > --
> > Bruce Loehle-Conger
> > MVP SQL Server Reporting Services
> >
> > "ranga" <ranga@.discussions.microsoft.com> wrote in message
> > news:82EFEFC5-44F7-425D-84D9-90538A9BDA91@.microsoft.com...
> > > can anyone confirm if rs-sp2 will have a report viewer control for
> > winforms
> > > and webforms ? - is this a pure .NET control or is it ActiveX
> > >
> > > also where can i find a list of featuers/bugfixes for sp2?
> > >
> > > thanks
> > >
> > > "Joerg" wrote:
> > >
> > > > http://www.microsoft.com/windowsserversystem/default.mspx
> > > >
> > > > "Download SQL Reporting Services SP2 and New Report Packs
> > > > Get the latest downloads for SQL Server Reporting Services,
including
> > > > Service Pack
> > > > 2 and new report packs for IIS and Great Plains."
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> >
> >
> >|||How is the confidence graph looking? When does mid april end?
"Brian Welcker" wrote:
> OK, here's the story. We are working very hard to finish up SP2. We had
> planned to get it out by the end of March but we found a couple of issues
> very late that we felt that we really needed to address. Couple this with
> the fact that we are also the team that delivered the February Community
> Technology preview of SQL Server 2005 Reporting Services and this means we
> had to push back a little. We have now feel confident that SP2 will be out
> by mid-April. Thank you for your patience and support.
> --
> Brian Welcker
> Group Program Manager
> Microsoft SQL Server Reporting Services
> This posting is provided "AS IS" with no warranties, and confers no rights.
> "FritoBandido" <FritoBandido@.discussions.microsoft.com> wrote in message
> news:945A4957-A365-4006-A7FF-3BA356280D13@.microsoft.com...
> >I know that SP2 is out there somewhere.
> > Could I prevail on anyone to tell me where I can get a copy?
> > Thanks
> >
> > "Bruce L-C [MVP]" wrote:
> >
> >> We MVPs are in the dark too. I really thought I would see it this month.
> >> Hopefully it won't be too much longer.
> >>
> >> --
> >> Bruce Loehle-Conger
> >> MVP SQL Server Reporting Services
> >>
> >> "Luke" <lukeguerrant@.gmail.com> wrote in message
> >> news:1112222701.375010.249600@.z14g2000cwz.googlegroups.com...
> >> > It wouldn't be so bad...except that there is no SP and no news.
> >> > Somebody say something about it. Can I get a little count down timer?
> >> > Where is that magic 8 ball? Some guy is out there right now flipping
> >> > coins until his thumb rubs his index finger raw...and the only thing
> >> > we've got to go on is a typo of sorts on the server homepage.
> >> >
> >>
> >>
> >>
>
>|||Is there any update on when SP2 will actually be coming out? It's now April
21st & no SP2?
"Bruce L-C [MVP]" wrote:
> Please look at the post that I responded to. It had nothing to do with
> client side printing. I responded spefically about the new web and winform
> report viewer controls.
> SP2 WILL have the ability for client side printing. Two different things
> here.
> Also, in case you haven't seen, SP2 will be out mid month. It was delayed a
> couple of weeks (originally they were targeting the end of March for
> release).
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "ranga" <ranga@.discussions.microsoft.com> wrote in message
> news:D03BC10F-F046-4EDA-8852-330ACD8BE054@.microsoft.com...
> > >> other posts in this group seem to indicate that client side printing is
> > one of
> > the major features of sp2 - have they pulled the plug on this feature for
> > sp2 ?
> >
> > >> if client-side printing is not going to be in sp2, then what other
> alternative is there ? (using pdf is ok but getting adobe to start is a slow
> process ; popping up
> > a browser window in a winform app does not look clean; using a web browser
> > control in a windows-forms app is also not clean (the control does not
> have a
> > print button)
> >
> >
> > "Bruce L-C [MVP]" wrote:
> >
> > > I can confirm that SP2 does not have the new webform/winform controls.
> That
> > > will be coming out with the next beta of Widbey (next version of Visual
> > > Studio).
> > >
> > > --
> > > Bruce Loehle-Conger
> > > MVP SQL Server Reporting Services
> > >
> > > "ranga" <ranga@.discussions.microsoft.com> wrote in message
> > > news:82EFEFC5-44F7-425D-84D9-90538A9BDA91@.microsoft.com...
> > > > can anyone confirm if rs-sp2 will have a report viewer control for
> > > winforms
> > > > and webforms ? - is this a pure .NET control or is it ActiveX
> > > >
> > > > also where can i find a list of featuers/bugfixes for sp2?
> > > >
> > > > thanks
> > > >
> > > > "Joerg" wrote:
> > > >
> > > > > http://www.microsoft.com/windowsserversystem/default.mspx
> > > > >
> > > > > "Download SQL Reporting Services SP2 and New Report Packs
> > > > > Get the latest downloads for SQL Server Reporting Services,
> including
> > > > > Service Pack
> > > > > 2 and new report packs for IIS and Great Plains."
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > >
> > >
> > >
>
>|||Last word was mid-month. Doesn't look like it made that. I am hoping before
the end of the month but I have no inside scoop. I am waiting for it as well
prior to my datamart going into production.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Lori" <Lori@.discussions.microsoft.com> wrote in message
news:EDE271FC-2DB4-48C3-8831-B31A26ECDCFD@.microsoft.com...
> Is there any update on when SP2 will actually be coming out? It's now
> April
> 21st & no SP2?
> "Bruce L-C [MVP]" wrote:
>> Please look at the post that I responded to. It had nothing to do with
>> client side printing. I responded spefically about the new web and
>> winform
>> report viewer controls.
>> SP2 WILL have the ability for client side printing. Two different things
>> here.
>> Also, in case you haven't seen, SP2 will be out mid month. It was delayed
>> a
>> couple of weeks (originally they were targeting the end of March for
>> release).
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>> "ranga" <ranga@.discussions.microsoft.com> wrote in message
>> news:D03BC10F-F046-4EDA-8852-330ACD8BE054@.microsoft.com...
>> > >> other posts in this group seem to indicate that client side printing
>> > >> is
>> > one of
>> > the major features of sp2 - have they pulled the plug on this feature
>> > for
>> > sp2 ?
>> >
>> > >> if client-side printing is not going to be in sp2, then what other
>> alternative is there ? (using pdf is ok but getting adobe to start is a
>> slow
>> process ; popping up
>> > a browser window in a winform app does not look clean; using a web
>> > browser
>> > control in a windows-forms app is also not clean (the control does not
>> have a
>> > print button)
>> >
>> >
>> > "Bruce L-C [MVP]" wrote:
>> >
>> > > I can confirm that SP2 does not have the new webform/winform
>> > > controls.
>> That
>> > > will be coming out with the next beta of Widbey (next version of
>> > > Visual
>> > > Studio).
>> > >
>> > > --
>> > > Bruce Loehle-Conger
>> > > MVP SQL Server Reporting Services
>> > >
>> > > "ranga" <ranga@.discussions.microsoft.com> wrote in message
>> > > news:82EFEFC5-44F7-425D-84D9-90538A9BDA91@.microsoft.com...
>> > > > can anyone confirm if rs-sp2 will have a report viewer control for
>> > > winforms
>> > > > and webforms ? - is this a pure .NET control or is it ActiveX
>> > > >
>> > > > also where can i find a list of featuers/bugfixes for sp2?
>> > > >
>> > > > thanks
>> > > >
>> > > > "Joerg" wrote:
>> > > >
>> > > > > http://www.microsoft.com/windowsserversystem/default.mspx
>> > > > >
>> > > > > "Download SQL Reporting Services SP2 and New Report Packs
>> > > > > Get the latest downloads for SQL Server Reporting Services,
>> including
>> > > > > Service Pack
>> > > > > 2 and new report packs for IIS and Great Plains."
>> > > > >
>> > > > >
>> > > > >
>> > > > >
>> > > > >
>> > > > >
>> > >
>> > >
>> > >
>>|||Thanks for the quick response Bruce! I will keep checking back here for
updates.
"Bruce L-C [MVP]" wrote:
> Last word was mid-month. Doesn't look like it made that. I am hoping before
> the end of the month but I have no inside scoop. I am waiting for it as well
> prior to my datamart going into production.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Lori" <Lori@.discussions.microsoft.com> wrote in message
> news:EDE271FC-2DB4-48C3-8831-B31A26ECDCFD@.microsoft.com...
> > Is there any update on when SP2 will actually be coming out? It's now
> > April
> > 21st & no SP2?
> >
> > "Bruce L-C [MVP]" wrote:
> >
> >> Please look at the post that I responded to. It had nothing to do with
> >> client side printing. I responded spefically about the new web and
> >> winform
> >> report viewer controls.
> >>
> >> SP2 WILL have the ability for client side printing. Two different things
> >> here.
> >>
> >> Also, in case you haven't seen, SP2 will be out mid month. It was delayed
> >> a
> >> couple of weeks (originally they were targeting the end of March for
> >> release).
> >>
> >>
> >> --
> >> Bruce Loehle-Conger
> >> MVP SQL Server Reporting Services
> >>
> >> "ranga" <ranga@.discussions.microsoft.com> wrote in message
> >> news:D03BC10F-F046-4EDA-8852-330ACD8BE054@.microsoft.com...
> >> > >> other posts in this group seem to indicate that client side printing
> >> > >> is
> >> > one of
> >> > the major features of sp2 - have they pulled the plug on this feature
> >> > for
> >> > sp2 ?
> >> >
> >> > >> if client-side printing is not going to be in sp2, then what other
> >> alternative is there ? (using pdf is ok but getting adobe to start is a
> >> slow
> >> process ; popping up
> >> > a browser window in a winform app does not look clean; using a web
> >> > browser
> >> > control in a windows-forms app is also not clean (the control does not
> >> have a
> >> > print button)
> >> >
> >> >
> >> > "Bruce L-C [MVP]" wrote:
> >> >
> >> > > I can confirm that SP2 does not have the new webform/winform
> >> > > controls.
> >> That
> >> > > will be coming out with the next beta of Widbey (next version of
> >> > > Visual
> >> > > Studio).
> >> > >
> >> > > --
> >> > > Bruce Loehle-Conger
> >> > > MVP SQL Server Reporting Services
> >> > >
> >> > > "ranga" <ranga@.discussions.microsoft.com> wrote in message
> >> > > news:82EFEFC5-44F7-425D-84D9-90538A9BDA91@.microsoft.com...
> >> > > > can anyone confirm if rs-sp2 will have a report viewer control for
> >> > > winforms
> >> > > > and webforms ? - is this a pure .NET control or is it ActiveX
> >> > > >
> >> > > > also where can i find a list of featuers/bugfixes for sp2?
> >> > > >
> >> > > > thanks
> >> > > >
> >> > > > "Joerg" wrote:
> >> > > >
> >> > > > > http://www.microsoft.com/windowsserversystem/default.mspx
> >> > > > >
> >> > > > > "Download SQL Reporting Services SP2 and New Report Packs
> >> > > > > Get the latest downloads for SQL Server Reporting Services,
> >> including
> >> > > > > Service Pack
> >> > > > > 2 and new report packs for IIS and Great Plains."
> >> > > > >
> >> > > > >
> >> > > > >
> >> > > > >
> >> > > > >
> >> > > > >
> >> > >
> >> > >
> >> > >
> >>
> >>
> >>
>
>

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 SP2 client-printing

After installing SP2 (beta) it is possible to print on the client side, but
it seems that printing is not correct. In VS.NET I also have problems, but
it is what you really get when print from IE (browser). Has anybody
suggeestion about this ?
Thanks,
JovanBugs are being worked out of printing in the beta. Thanks for giving it a
try and your feedback is important. I am not sure if there is another beta
coming, but many print issues have been resolved.
--
| From: "Jovan Racic" <jracic@.sito.co.yu>
| Subject: RS SP2 client-printing
| Date: Tue, 25 Jan 2005 10:34:27 +0100
| Lines: 8
| X-Priority: 3
| X-MSMail-Priority: Normal
| X-Newsreader: Microsoft Outlook Express 6.00.2800.1437
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
| Message-ID: <eZuDSEsAFHA.1300@.TK2MSFTNGP14.phx.gbl>
| Newsgroups: microsoft.public.sqlserver.reportingsvcs
| NNTP-Posting-Host: 213.240.50.130
| Path:
cpmsftngxa10.phx.gbl!TK2MSFTNGXS01.phx.gbl!cpmsftngxa06.phx.gbl!TK2MSFTNGP08
.phx.gbl!TK2MSFTNGP14.phx.gbl
| Xref: cpmsftngxa10.phx.gbl microsoft.public.sqlserver.reportingsvcs:40731
| X-Tomcat-NG: microsoft.public.sqlserver.reportingsvcs
|
| After installing SP2 (beta) it is possible to print on the client side,
but
| it seems that printing is not correct. In VS.NET I also have problems, but
| it is what you really get when print from IE (browser). Has anybody
| suggeestion about this ?
| Thanks,
| Jovan
|
|
||||Someone else reported this and was told that the printing issues are still
being resolved prior to release.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Jovan Racic" <jracic@.sito.co.yu> wrote in message
news:eZuDSEsAFHA.1300@.TK2MSFTNGP14.phx.gbl...
> After installing SP2 (beta) it is possible to print on the client side,
but
> it seems that printing is not correct. In VS.NET I also have problems, but
> it is what you really get when print from IE (browser). Has anybody
> suggeestion about this ?
> Thanks,
> Jovan
>

RS SP2 / Oracle 10g Error Is Back

Yesterday RS kept bombing out from time to time with an Oracle error. Each
time we would do an iisreset and the issue would correct itself.
I reinstalled RS with SP2 last night. Today things ran smooth for about 5
hours, then the issue reappeared.
Of particular interest from the RS log file:
"The timeout period elapsed prior to obtaining a connection from the pool.
This may have occurred because all pooled connections were in use and max
pool size was reached."
Here's the context of the error in the log file:
w3wp!library!ae0!11/10/2005-13:49:06:: i INFO: Initializing
EnableExecutionLogging to 'True' as specified in Server system properties.
w3wp!webserver!ae0!11/10/2005-13:49:06:: e ERROR: Reporting Services error
Microsoft.ReportingServices.Diagnostics.Utilities.RSException: An error has
occurred during report processing. -->
Microsoft.ReportingServices.ReportProcessing.ProcessingAbortedException: An
error has occurred during report processing. -->
Microsoft.ReportingServices.ReportProcessing.ReportProcessingException:
Cannot create a connection to data source 'dbReports'. -->
System.InvalidOperationException: Timeout expired. The timeout period
elapsed prior to obtaining a connection from the pool. This may have
occurred because all pooled connections were in use and max pool size was
reached.
w3wp!runningjobs!1254!11/10/2005-13:49:48:: i INFO: Adding: 1 running jobs
to the database
w3wp!library!ae0!11/10/2005-13:54:36:: i INFO: Call to RenderFirst( '[folder
/ report name was here]')
w3wp!processing!ae0!11/10/2005-13:55:06:: e ERROR: Throwing
Microsoft.ReportingServices.ReportProcessing.ReportProcessingException:
Cannot create a connection to data source 'dbReports'., ;
Info:
Microsoft.ReportingServices.ReportProcessing.ReportProcessingException:
Cannot create a connection to data source 'dbReports'. -->
System.InvalidOperationException: Timeout expired. The timeout period
elapsed prior to obtaining a connection from the pool. This may have
occurred because all pooled connections were in use and max pool size was
reached.
at
System.Data.OracleClient.OracleConnectionPoolManager.GetPooledConnection(String
encryptedConnectionString, OracleConnectionString options, OracleConnection
owningObject, Boolean& isInTransaction)
at
System.Data.OracleClient.OracleConnection.OpenInternal(OracleConnectionString
parsedConnectionString, Object transact)
at System.Data.OracleClient.OracleConnection.Open()
at Microsoft.ReportingServices.DataExtensions.ConnectionExtension.Open()
at Microsoft.ReportingServices.ReportProcessing.s.a(DataSource A_0, ab
A_1)
Is anyone running RS with Oracle 10g? If so, have you seen anything like
this?
Thanks in advance.More info from the 10g install -
This document provides information that supplements the Oracle Data Provider
for .NET (ODP.NET) documentation.
=======================DOCUMENTATION ADDENDUMS
=======================
1. Connection Pool Management Methods (New Feature)
Two new connection pool management methods have been introduced in
ODP.NET
10.2.0.1.0. ODP.NET applications can explicitly clear connections in a
connection pool through the ClearPool() or ClearAllPools() static method
on the OracleConnection object.
I'm guessing that Reporting Services doesn't know about this and the pools
are filling up. Just an FYI in case anyone hits this in the future.
For the moment, I've attempted installing the 9i client on the box hoping
that Reporting Services will resort to the 9i drivers. I'll let you know if
I see any difference.
"Jack" <anonymous@.microsoft.com> wrote in message
news:uh2QmHk5FHA.2040@.TK2MSFTNGP14.phx.gbl...
> Yesterday RS kept bombing out from time to time with an Oracle error.
> Each time we would do an iisreset and the issue would correct itself.
> I reinstalled RS with SP2 last night. Today things ran smooth for about 5
> hours, then the issue reappeared.
> Of particular interest from the RS log file:
> "The timeout period elapsed prior to obtaining a connection from the pool.
> This may have occurred because all pooled connections were in use and max
> pool size was reached."
> Here's the context of the error in the log file:
> w3wp!library!ae0!11/10/2005-13:49:06:: i INFO: Initializing
> EnableExecutionLogging to 'True' as specified in Server system
> properties.
> w3wp!webserver!ae0!11/10/2005-13:49:06:: e ERROR: Reporting Services error
> Microsoft.ReportingServices.Diagnostics.Utilities.RSException: An error
> has occurred during report processing. -->
> Microsoft.ReportingServices.ReportProcessing.ProcessingAbortedException:
> An error has occurred during report processing. -->
> Microsoft.ReportingServices.ReportProcessing.ReportProcessingException:
> Cannot create a connection to data source 'dbReports'. -->
> System.InvalidOperationException: Timeout expired. The timeout period
> elapsed prior to obtaining a connection from the pool. This may have
> occurred because all pooled connections were in use and max pool size was
> reached.
> w3wp!runningjobs!1254!11/10/2005-13:49:48:: i INFO: Adding: 1 running jobs
> to the database
> w3wp!library!ae0!11/10/2005-13:54:36:: i INFO: Call to RenderFirst(
> '[folder / report name was here]')
> w3wp!processing!ae0!11/10/2005-13:55:06:: e ERROR: Throwing
> Microsoft.ReportingServices.ReportProcessing.ReportProcessingException:
> Cannot create a connection to data source 'dbReports'., ;
> Info:
> Microsoft.ReportingServices.ReportProcessing.ReportProcessingException:
> Cannot create a connection to data source 'dbReports'. -->
> System.InvalidOperationException: Timeout expired. The timeout period
> elapsed prior to obtaining a connection from the pool. This may have
> occurred because all pooled connections were in use and max pool size was
> reached.
> at
> System.Data.OracleClient.OracleConnectionPoolManager.GetPooledConnection(String
> encryptedConnectionString, OracleConnectionString options,
> OracleConnection owningObject, Boolean& isInTransaction)
> at
> System.Data.OracleClient.OracleConnection.OpenInternal(OracleConnectionString
> parsedConnectionString, Object transact)
> at System.Data.OracleClient.OracleConnection.Open()
> at Microsoft.ReportingServices.DataExtensions.ConnectionExtension.Open()
> at Microsoft.ReportingServices.ReportProcessing.s.a(DataSource A_0, ab
> A_1)
> Is anyone running RS with Oracle 10g? If so, have you seen anything like
> this?
> Thanks in advance.
>

Rs setup problem with version La versión encontrada es 'C.0.8.54'. La versión esperada es 'C.

Hello I got this error when installing rs 2005.

The thing is that sqlserver database is on another server, that server must have sp2 I think but the rs machine doesnt have sp2, that may be the problem?

La versión de la base de datos del servidor de informes no tiene un formato válido o no se puede leer. La versión encontrada es 'C.0.8.54'. La versión esperada es 'C.0.8.40'. Para continuar, actualice la versión de la base de datos del servidor de informes y compruebe los derechos de acceso. (rsInvalidReportServerDatabase) Obtener ayuda en pantalla

Obtener ayuda en pantalla

Inicio

I have the same problem, nobodby help you to solve it?
"La versión de la base de datos del servidor de informes no tiene un formato válido o no se puede leer. La versión encontrada es 'Unknown'. La versión esperada es 'C.0.8.40'. Para continuar, actualice la versión de la base de datos del servidor de informes y compruebe los derechos de acceso. (rsInvalidReportServerDatabase) Obtener ayuda en pantalla "
if you solved it, would you mind to help me ? thanks...