ReportBuilder

I installed RS 2005 on my machine. Everything works except the reportbuilder.
When I launch it I get the message
An unhandled exception of type
'Microsoft.SqlServer.ReportingServices2005.RSConnection.MissingEndpointException' occurred in ReportBuilder.exe
Additional information: The attempt to connect to the report server failed.
Check your connection information and that the report server is a compatible
version.
Any ideasRoland,
Which build of SQL Server 2005 are you using?
Which OS?
Was it a clean install or after uninstall of earlier builds?
I don't recall seeing this specific error reported before although
there were some problems with early builds of Report Builder.
You might want to visit
http://lab.msdn.microsoft.com/productfeedback/default.aspx and search
for any similar reports.
Andrew Watt
MVP - InfoPath
On Sat, 15 Oct 2005 01:13:01 -0700, Roland
<Roland@.discussions.microsoft.com> wrote:
>I installed RS 2005 on my machine. Everything works except the reportbuilder.
>When I launch it I get the message
>An unhandled exception of type
>'Microsoft.SqlServer.ReportingServices2005.RSConnection.MissingEndpointException' occurred in ReportBuilder.exe
>Additional information: The attempt to connect to the report server failed.
>Check your connection information and that the report server is a compatible
>version.
>Any ideas|||I installed it from the MSDN Visual Studio 2005 Beta 2 DVD
Select @.@.version in SQL gives
Microsoft SQL Server 2005 - 9.00.1116 (Intel X86)
Apr 9 2005 20:56:37
Copyright (c) 1988-2004 Microsoft Corporation
Beta Edition on Windows NT 5.1 (Build 2600: Service Pack 2)
The reportbuilder.exe : version 9.0.1116.0, assembly version 9.0.242.0
Installed on a Windows XP (with SP2) machine
Is it possible that the fact my installed OS is Dutch, is causing the
problem ?
"Andrew Watt [MVP - InfoPath]" wrote:
> Roland,
> Which build of SQL Server 2005 are you using?
> Which OS?
> Was it a clean install or after uninstall of earlier builds?
> I don't recall seeing this specific error reported before although
> there were some problems with early builds of Report Builder.
> You might want to visit
> http://lab.msdn.microsoft.com/productfeedback/default.aspx and search
> for any similar reports.
> Andrew Watt
> MVP - InfoPath
> On Sat, 15 Oct 2005 01:13:01 -0700, Roland
> <Roland@.discussions.microsoft.com> wrote:
> >I installed RS 2005 on my machine. Everything works except the reportbuilder.
> >When I launch it I get the message
> >An unhandled exception of type
> >'Microsoft.SqlServer.ReportingServices2005.RSConnection.MissingEndpointException' occurred in ReportBuilder.exe
> >
> >Additional information: The attempt to connect to the report server failed.
> >Check your connection information and that the report server is a compatible
> >version.
> >
> >Any ideas
>|||Hi
That was the April CTP.
Between then and now, there were 2 more CTP's. Probably a bug with that old
version.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Roland" <Roland@.discussions.microsoft.com> wrote in message
news:CE1A6B37-EFE2-4537-A39A-0016A7B7A503@.microsoft.com...
>I installed it from the MSDN Visual Studio 2005 Beta 2 DVD
> Select @.@.version in SQL gives
> Microsoft SQL Server 2005 - 9.00.1116 (Intel X86)
> Apr 9 2005 20:56:37
> Copyright (c) 1988-2004 Microsoft Corporation
> Beta Edition on Windows NT 5.1 (Build 2600: Service Pack 2)
> The reportbuilder.exe : version 9.0.1116.0, assembly version 9.0.242.0
> Installed on a Windows XP (with SP2) machine
> Is it possible that the fact my installed OS is Dutch, is causing the
> problem ?
> "Andrew Watt [MVP - InfoPath]" wrote:
>> Roland,
>> Which build of SQL Server 2005 are you using?
>> Which OS?
>> Was it a clean install or after uninstall of earlier builds?
>> I don't recall seeing this specific error reported before although
>> there were some problems with early builds of Report Builder.
>> You might want to visit
>> http://lab.msdn.microsoft.com/productfeedback/default.aspx and search
>> for any similar reports.
>> Andrew Watt
>> MVP - InfoPath
>> On Sat, 15 Oct 2005 01:13:01 -0700, Roland
>> <Roland@.discussions.microsoft.com> wrote:
>> >I installed RS 2005 on my machine. Everything works except the
>> >reportbuilder.
>> >When I launch it I get the message
>> >An unhandled exception of type
>> >'Microsoft.SqlServer.ReportingServices2005.RSConnection.MissingEndpointException'
>> >occurred in ReportBuilder.exe
>> >
>> >Additional information: The attempt to connect to the report server
>> >failed.
>> >Check your connection information and that the report server is a
>> >compatible
>> >version.
>> >
>> >Any ideas|||Roland,
April CTP was, if I remember correctly, only the second public build
with Report Builder in it. I remember having problems connecting to
Report Builder in one early build but don't remember if it was April
CTP.
If you have access to MSDN or BetaPlace I suggest you update to
September CTP. You will need a matching copy of Visual Studio 2005
(which is the VS2005 Release Candidate).
Uninstall order of the April CTP is VERY important. Read the Sept CTP
/ Visual Studio 2005 RC documentation CAREFULLY.
After a successful uninstall, the install order is SQL Server 2005
Sept CTP first then Visual Studio 2005 Release Candidate.
Andrew Watt
MVP - InfoPath
On Sun, 16 Oct 2005 11:13:01 -0700, Roland
<Roland@.discussions.microsoft.com> wrote:
>I installed it from the MSDN Visual Studio 2005 Beta 2 DVD
>Select @.@.version in SQL gives
>Microsoft SQL Server 2005 - 9.00.1116 (Intel X86)
> Apr 9 2005 20:56:37
> Copyright (c) 1988-2004 Microsoft Corporation
> Beta Edition on Windows NT 5.1 (Build 2600: Service Pack 2)
>The reportbuilder.exe : version 9.0.1116.0, assembly version 9.0.242.0
>Installed on a Windows XP (with SP2) machine
>Is it possible that the fact my installed OS is Dutch, is causing the
>problem ?
>"Andrew Watt [MVP - InfoPath]" wrote:
>> Roland,
>> Which build of SQL Server 2005 are you using?
>> Which OS?
>> Was it a clean install or after uninstall of earlier builds?
>> I don't recall seeing this specific error reported before although
>> there were some problems with early builds of Report Builder.
>> You might want to visit
>> http://lab.msdn.microsoft.com/productfeedback/default.aspx and search
>> for any similar reports.
>> Andrew Watt
>> MVP - InfoPath
>> On Sat, 15 Oct 2005 01:13:01 -0700, Roland
>> <Roland@.discussions.microsoft.com> wrote:
>> >I installed RS 2005 on my machine. Everything works except the reportbuilder.
>> >When I launch it I get the message
>> >An unhandled exception of type
>> >'Microsoft.SqlServer.ReportingServices2005.RSConnection.MissingEndpointException' occurred in ReportBuilder.exe
>> >
>> >Additional information: The attempt to connect to the report server failed.
>> >Check your connection information and that the report server is a compatible
>> >version.
>> >
>> >Any ideas|||Installing the Sept CTP Release of SQL 2005 did solve my problem of using the
reportbuilder. Indeed the installation order is important; as I also have SQL
2000 with Reporting Services 2000/SP2 on the same machine I had to reinstall
also the SP2 of RS 2000 because the uninstall of the version of RS2005 also
influences the behaviour of RS2000
"Andrew Watt [MVP - InfoPath]" wrote:
> Roland,
> April CTP was, if I remember correctly, only the second public build
> with Report Builder in it. I remember having problems connecting to
> Report Builder in one early build but don't remember if it was April
> CTP.
> If you have access to MSDN or BetaPlace I suggest you update to
> September CTP. You will need a matching copy of Visual Studio 2005
> (which is the VS2005 Release Candidate).
> Uninstall order of the April CTP is VERY important. Read the Sept CTP
> / Visual Studio 2005 RC documentation CAREFULLY.
> After a successful uninstall, the install order is SQL Server 2005
> Sept CTP first then Visual Studio 2005 Release Candidate.
> Andrew Watt
> MVP - InfoPath
> On Sun, 16 Oct 2005 11:13:01 -0700, Roland
> <Roland@.discussions.microsoft.com> wrote:
> >I installed it from the MSDN Visual Studio 2005 Beta 2 DVD
> >Select @.@.version in SQL gives
> >
> >Microsoft SQL Server 2005 - 9.00.1116 (Intel X86)
> > Apr 9 2005 20:56:37
> > Copyright (c) 1988-2004 Microsoft Corporation
> > Beta Edition on Windows NT 5.1 (Build 2600: Service Pack 2)
> >
> >The reportbuilder.exe : version 9.0.1116.0, assembly version 9.0.242.0
> >
> >Installed on a Windows XP (with SP2) machine
> >Is it possible that the fact my installed OS is Dutch, is causing the
> >problem ?
> >
> >"Andrew Watt [MVP - InfoPath]" wrote:
> >
> >> Roland,
> >>
> >> Which build of SQL Server 2005 are you using?
> >>
> >> Which OS?
> >>
> >> Was it a clean install or after uninstall of earlier builds?
> >>
> >> I don't recall seeing this specific error reported before although
> >> there were some problems with early builds of Report Builder.
> >>
> >> You might want to visit
> >> http://lab.msdn.microsoft.com/productfeedback/default.aspx and search
> >> for any similar reports.
> >>
> >> Andrew Watt
> >> MVP - InfoPath
> >>
> >> On Sat, 15 Oct 2005 01:13:01 -0700, Roland
> >> <Roland@.discussions.microsoft.com> wrote:
> >>
> >> >I installed RS 2005 on my machine. Everything works except the reportbuilder.
> >> >When I launch it I get the message
> >> >An unhandled exception of type
> >> >'Microsoft.SqlServer.ReportingServices2005.RSConnection.MissingEndpointException' occurred in ReportBuilder.exe
> >> >
> >> >Additional information: The attempt to connect to the report server failed.
> >> >Check your connection information and that the report server is a compatible
> >> >version.
> >> >
> >> >Any ideas
> >>
>sql

report with ssis package as source

The report having SSIS package as source works fine on my local 32 bit windows xp machine from Report Manager. But same doesn't work from 64bit windows 2003 machine... fails with below error... what could be an issue?

An error has occurred during report processing.

Cannot create a connection to data source 'DataSource1'.

is not a valid Win32 application. (Exception from HRESULT: 0x800700C1)

The same works fine when previewed from visual studio on 64 bit machine.

Thanks

Mahesh

If you search for SSIS AND 64 on these forums, you will find a lot of woes and advice. I don't know anything about the driver you're using for the connection to this datasource, but I suspect that this thread http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=610493&SiteID=1

and similar will be helpful....

>L<

|||

I still could not fix the issue.

I have very simple packages which pulls data from flat file to DataReader Destination. (Data reader destination uses ADO.NET )

Let me know how to make use 32 bit OLE DB and ADO.NET connection providers instead of 64 bit.

Thanks

Mahesh

|||

>> Let me know

I'm afraid I can't do your research for you on this one, just point you to resources.

Did you search the forums? For example,

c. For an OLE DB provider to be available only in 32bit (i.e. JET), does not necessarily mean that you cannot run it on 64bit machines. You can, but it will be in WOW64 emulation mode. The only downside to that is if you need the 64bit address space of huge memory (i.e. greater than 4GB). Otherwise, it’s not a problem.

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1785799&SiteID=1

... Which also points to a white paper.

YOu will find more information about the emulation mode here http://ssis.wik.is/64-bit_Story

I'm sorry -- this is all I can do for you.

>L<

|||

The problem got automatically resolved after installing SP2.

Thanks Lisa for trying to help.

|||

Oh for goodness' sakes <sigh>. Thanks for posting back with the answer, I'm sure it will help other people...

>L<

report with ssis package as source

The report having SSIS package as source works fine on my local 32 bit windows xp machine from Report Manager. But same doesn't work from 64bit windows 2003 machine... fails with below error... what could be an issue?

An error has occurred during report processing.

Cannot create a connection to data source 'DataSource1'.

is not a valid Win32 application. (Exception from HRESULT: 0x800700C1)

The same works fine when previewed from visual studio on 64 bit machine.

Thanks

Mahesh

If you search for SSIS AND 64 on these forums, you will find a lot of woes and advice. I don't know anything about the driver you're using for the connection to this datasource, but I suspect that this thread http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=610493&SiteID=1

and similar will be helpful....

>L<

|||

I still could not fix the issue.

I have very simple packages which pulls data from flat file to DataReader Destination. (Data reader destination uses ADO.NET )

Let me know how to make use 32 bit OLE DB and ADO.NET connection providers instead of 64 bit.

Thanks

Mahesh

|||

>> Let me know

I'm afraid I can't do your research for you on this one, just point you to resources.

Did you search the forums? For example,

c. For an OLE DB provider to be available only in 32bit (i.e. JET), does not necessarily mean that you cannot run it on 64bit machines. You can, but it will be in WOW64 emulation mode. The only downside to that is if you need the 64bit address space of huge memory (i.e. greater than 4GB). Otherwise, it’s not a problem.

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1785799&SiteID=1

... Which also points to a white paper.

YOu will find more information about the emulation mode here http://ssis.wik.is/64-bit_Story

I'm sorry -- this is all I can do for you.

>L<

|||

The problem got automatically resolved after installing SP2.

Thanks Lisa for trying to help.

|||

Oh for goodness' sakes <sigh>. Thanks for posting back with the answer, I'm sure it will help other people...

>L<

report with ssis package as source

The report having SSIS package as source works fine on my local 32 bit windows xp machine from Report Manager. But same doesn't work from 64bit windows 2003 machine... fails with below error... what could be an issue?

An error has occurred during report processing.

Cannot create a connection to data source 'DataSource1'.

is not a valid Win32 application. (Exception from HRESULT: 0x800700C1)

The same works fine when previewed from visual studio on 64 bit machine.

Thanks

Mahesh

If you search for SSIS AND 64 on these forums, you will find a lot of woes and advice. I don't know anything about the driver you're using for the connection to this datasource, but I suspect that this thread http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=610493&SiteID=1

and similar will be helpful....

>L<

|||

I still could not fix the issue.

I have very simple packages which pulls data from flat file to DataReader Destination. (Data reader destination uses ADO.NET )

Let me know how to make use 32 bit OLE DB and ADO.NET connection providers instead of 64 bit.

Thanks

Mahesh

|||

>> Let me know

I'm afraid I can't do your research for you on this one, just point you to resources.

Did you search the forums? For example,

c. For an OLE DB provider to be available only in 32bit (i.e. JET), does not necessarily mean that you cannot run it on 64bit machines. You can, but it will be in WOW64 emulation mode. The only downside to that is if you need the 64bit address space of huge memory (i.e. greater than 4GB). Otherwise, it’s not a problem.

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1785799&SiteID=1

... Which also points to a white paper.

YOu will find more information about the emulation mode here http://ssis.wik.is/64-bit_Story

I'm sorry -- this is all I can do for you.

>L<

|||

The problem got automatically resolved after installing SP2.

Thanks Lisa for trying to help.

|||

Oh for goodness' sakes <sigh>. Thanks for posting back with the answer, I'm sure it will help other people...

>L<

Report Viewing and Vista

Hi

I am facing a strange problem while viewing a Windows Report in Windows Vista.

I have a machine which has Vista installed as the Operating system. I have two user id created to log into the system.

(Assumed user A and User B). Both the users have the same login credentials. However, the default user of the system is

User B.

I have a windows application, which uses Winreports for viewing the reports. I am creating the entire rdlc on - the - fly based on

the parameters specified from the User Interface. If I log into the system using user A and try to view the reports, the report is

perfectly generated and is being viewed properly without any error. However, if I log into the system using User B (the

default user of the system) and then try to view the same report (with all the parameters same) I am getting an Unauthorised

Access Violation error.

Please help with some of our valuable suggestions.

FYI: This happens only on PC having Windows Vista as the Operating System

Thanking you in advance,

Kind Regards,

PS

Hi Everybody,

Thank you very much to everybody who went through this issue.

Actually, the profile of user B had some issues. I deleted the account User B and re - created again, and it worked fine.

Thanking You once again,

Kind Regards,

Pratik

Report Viewer webpart did not work in wss 3.0

Hi,

I just installed a fresh lab machine with WSS 3.0 and SQL 2005. I registered the RS web parts.

In the home page I added the Reports Explorer and the Report viewer web parts. I set up the Reports Explorer and the list of reports are showed.

When I connect the Report Viewer Web part to get report from the Report Explorer web part I get the maintenance WSS page. I have to delete the Report Viewer web part to have the page working again.

If I use only the Reports Viewer with a report (not connected to Reports Explorer) is working just fine.

Any ideas what could be the problem? Any hints on how to investigate this is also much appreciated.

Thanks,

Dan

I also ran into this and I reported it as an issue on connect.microsoft.com. However, according to the feedback, it is by design and it won't be fixed.|||

Thanks Teo,

I hope it will be solved at some point. Until then, I am using RS in integration mode. It works very nice.

Dan

|||

Take a look at this;

http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/webrssp2.mspx

When I try to add a Web Part to a SharePoint page, I get the following error message: "A Web Part or Web Form Control on this Web Part Page cannot be displayed or imported because it is not registered on this site as safe."

Make sure you have followed all of the steps in the Installing the Web Parts section, Installation Process subsection of this paper, including using the –url option to stsadm. If you used the –globalinstall option, try leaving it out so the Web Part package is installed to the bin directory of the virtual server. Manually verify that the bin directory under your SharePoint Web root contains a file called RSWebParts.dll. If you installed SharePoint in the default Web root, this directory would be C:\Inetpub\wwwroot\bin. A copy of this DLL may be found in C:\Program Files\Microsoft SQL Server\80\Tools\Reporting Services\SharePoint\RSWebParts.cab (assuming that Reporting Services is installed in the default location).

|||He has the web parts working allright. It's just that the RS 2005 web parts are coded against the WSS 2.0 object model and don't support connections. Based on what I've heard they won't be enhanced to support the WSS 3.0 connections feature.sql

Report Viewer webpart did not work in wss 3.0

Hi,

I just installed a fresh lab machine with WSS 3.0 and SQL 2005. I registered the RS web parts.

In the home page I added the Reports Explorer and the Report viewer web parts. I set up the Reports Explorer and the list of reports are showed.

When I connect the Report Viewer Web part to get report from the Report Explorer web part I get the maintenance WSS page. I have to delete the Report Viewer web part to have the page working again.

If I use only the Reports Viewer with a report (not connected to Reports Explorer) is working just fine.

Any ideas what could be the problem? Any hints on how to investigate this is also much appreciated.

Thanks,

Dan

I also ran into this and I reported it as an issue on connect.microsoft.com. However, according to the feedback, it is by design and it won't be fixed.|||

Thanks Teo,

I hope it will be solved at some point. Until then, I am using RS in integration mode. It works very nice.

Dan

|||

Take a look at this;

http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/webrssp2.mspx

When I try to add a Web Part to a SharePoint page, I get the following error message: "A Web Part or Web Form Control on this Web Part Page cannot be displayed or imported because it is not registered on this site as safe."

Make sure you have followed all of the steps in the Installing the Web Parts section, Installation Process subsection of this paper, including using the –url option to stsadm. If you used the –globalinstall option, try leaving it out so the Web Part package is installed to the bin directory of the virtual server. Manually verify that the bin directory under your SharePoint Web root contains a file called RSWebParts.dll. If you installed SharePoint in the default Web root, this directory would be C:\Inetpub\wwwroot\bin. A copy of this DLL may be found in C:\Program Files\Microsoft SQL Server\80\Tools\Reporting Services\SharePoint\RSWebParts.cab (assuming that Reporting Services is installed in the default location).

|||He has the web parts working allright. It's just that the RS 2005 web parts are coded against the WSS 2.0 object model and don't support connections. Based on what I've heard they won't be enhanced to support the WSS 3.0 connections feature.

Report Viewer Error after Deployment

I have created a report on my local machine and deployed it on a server. As I am the administrator of the server, I can access the reports with servername\Reports. The report has got three data sets. Out of these three one is a Stored procedure and other two data sets have sql queries. The user selects the 'Business year' and 'sales type' from list box. This report works perfect from my local machine as well as from teh server when I am running it

I have some other users who wish to access these reports. I did the following steps:

Created a new role and assigned it at the Data Source Folder and Reports Folder

I also made the user a Database user on the server.

After doing these steps, the user can access the Reports site by servername\Reports.

The user then can go into the Reports folder. But when the user tries to run the report, he gets an error with:

An error has occurred during report processing. (rsProcessingAborted)

Query execution failed for data set 'BusinessYear'. (rsErrorExecutingCommand)

For more information about this error navigate to the report server on the local server machine, or enable remote errors

Can anyone help me with this? Is htere something to do with setting up of the datasource?

I have tried to search, but could not find relevant info.

Any help/Pointers will be really appreciated.

regards

Joshker

Hi Joshker,

Can you provide us with the RS Log Files so we can look into the error in more detail......

Potenitally you could have a "datatype" issue wrong with the Business Year....

Report Services installation problem

I've installed SQL Express 2005 on an XP Professional machine and I'm trying to configure Report Services. In Reporting Services Configuration Manager, all items are "green" except "Web Service Identity". The value is <machinename>\ASPNET and isn't configurable. I've searched the forums and followed the advice I've found to remove and reinstall .NET, but it hasn't helped. User ASPNET does exist on the machine with a local account, and IIS5 is running. SQL gurus, please help me figure out what to do! Thanks.The Web Service Identity is supposed to be read-only. If everything is grean RS should be already configured and good to go. What's not working?|||

I apologize - I didn't offer full details. I was frustrated!

Clicking "Apply" on the "Web Service Identity" dialogue results in an error. Clicking the link for details reveals this:

---

ReportServicesConfigUI.WMIProvider.WMIProviderException: The account name is not valid. Specify an account in the form domain\alias.

at ReportServicesConfigUI.WMIProvider.RSReportServerAdmin.SetWebServiceIdentity(String applicationPool)

---

The ASPNET user does exist however! I don't understand what's wrong. Thanks for your help.

|||

Not sure what's going on. It's seeme like there is something wrong with the ASPNET account. Is ReportServer vroot in IIS running under asp.net 2.0. Are any other web applications on that machine working OK?

|||That's a little over my head, I know little about IIS. Other "web pages" are accessible, such as http://localhost/printers and http://localhost/tsweb. This machine is dedicated to running SQL Server Express, so no other applications are running that I can test for web connectivity. Any direction you can point me in is greatly appreciated! Thanks again for your help.|||

1. Open up Internet Information Services applet in the Administrators group.

2. Right-click on the ReportServer node and choose Properties. Flip to the ASP.NET tab. What's the ASP.NET version?

|||The ASP.NET version is 2.0.50727. Thanks for helping me through this!

Report Services installation problem

I've installed SQL Express 2005 on an XP Professional machine and I'm trying to configure Report Services. In Reporting Services Configuration Manager, all items are "green" except "Web Service Identity". The value is <machinename>\ASPNET and isn't configurable. I've searched the forums and followed the advice I've found to remove and reinstall .NET, but it hasn't helped. User ASPNET does exist on the machine with a local account, and IIS5 is running. SQL gurus, please help me figure out what to do! Thanks.The Web Service Identity is supposed to be read-only. If everything is grean RS should be already configured and good to go. What's not working?|||

I apologize - I didn't offer full details. I was frustrated!

Clicking "Apply" on the "Web Service Identity" dialogue results in an error. Clicking the link for details reveals this:

---

ReportServicesConfigUI.WMIProvider.WMIProviderException: The account name is not valid. Specify an account in the form domain\alias.

at ReportServicesConfigUI.WMIProvider.RSReportServerAdmin.SetWebServiceIdentity(String applicationPool)

---

The ASPNET user does exist however! I don't understand what's wrong. Thanks for your help.

|||

Not sure what's going on. It's seeme like there is something wrong with the ASPNET account. Is ReportServer vroot in IIS running under asp.net 2.0. Are any other web applications on that machine working OK?

|||That's a little over my head, I know little about IIS. Other "web pages" are accessible, such as http://localhost/printers and http://localhost/tsweb. This machine is dedicated to running SQL Server Express, so no other applications are running that I can test for web connectivity. Any direction you can point me in is greatly appreciated! Thanks again for your help.|||

1. Open up Internet Information Services applet in the Administrators group.

2. Right-click on the ReportServer node and choose Properties. Flip to the ASP.NET tab. What's the ASP.NET version?

|||The ASP.NET version is 2.0.50727. Thanks for helping me through this!

Report Services Install problems!

Installing Reporting Services with IIS and Report Services running on one
machine and Reporting databases on remote SQL Server. Getting the error below
when attempting to view http://servername/reports page.
Any ideas?
Thanks.
Frank
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: Unable to load file
'ReportingServicesEmailDeliveryProvider'.
Source Error:
Line 256: <add assembly="System.EnterpriseServices,
Version=1.0.5000.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"/>
Line 257: <add assembly="System.Web.Mobile,
Version=1.0.5000.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"/>
Line 258: <add assembly="*"/>
Line 259: </assemblies>
Line 260:
Source File: c:\nos\microsoft.net\framework\v1.1.4322\Config\machine.config
Line: 258
Assembly Load Trace: The following information can be helpful to determine
why the assembly 'ReportingServicesEmailDeliveryProvider' could not be loaded.
=== Pre-bind state information === LOG: DisplayName = ReportingServicesEmailDeliveryProvider
(Partial)
LOG: Appbase = file:///D:/ReportingServices/MSSQL/Reporting
Services/ReportManager
LOG: Initial PrivatePath = bin
Calling assembly : (Unknown).
===
LOG: Policy not being applied to reference at this time (private, custom,
partial, or location-based assembly bind).
LOG: Post-policy reference: ReportingServicesEmailDeliveryProvider
LOG: Attempting download of new URL
file:///C:/NOS/Microsoft.NET/Framework/v1.1.4322/Temporary ASP.NET
Files/reports/a21cac91/f4eaffac/ReportingServicesEmailDeliveryProvider.DLL.
LOG: Attempting download of new URL
file:///C:/NOS/Microsoft.NET/Framework/v1.1.4322/Temporary ASP.NET
Files/reports/a21cac91/f4eaffac/ReportingServicesEmailDeliveryProvider/ReportingServicesEmailDeliveryProvider.DLL.
LOG: Attempting download of new URL
file:///D:/ReportingServices/MSSQL/Reporting
Services/ReportManager/bin/ReportingServicesEmailDeliveryProvider.DLL.
LOG: Publisher policy file is not found.
LOG: No redirect found in host configuration file
(C:\NOS\Microsoft.NET\Framework\v1.1.4322\aspnet.config).
LOG: Using machine configuration file from
C:\NOS\Microsoft.NET\Framework\v1.1.4322\config\machine.config.
LOG: Post-policy reference: ReportingServicesEmailDeliveryProvider,
Version=8.0.242.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91
----
Version Information: Microsoft .NET Framework Version:1.1.4322.2032; ASP.NET
Version:1.1.4322.2032> 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: Unable to load file
> 'ReportingServicesEmailDeliveryProvider'.
> Source Error:
>
> Line 256: <add assembly="System.EnterpriseServices,
> Version=1.0.5000.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"/>
> Line 257: <add assembly="System.Web.Mobile,
> Version=1.0.5000.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"/>
> Line 258: <add assembly="*"/>
> Line 259: </assemblies>
> Line 260:
>
Which OS? Is it a Domain controller?
I received the same message on my lab computer after making it domain
controller (Win2K, SP4). In KB824308 I found some useful information that
helped me to some extent. Now rs is at least able to show part of the
standard page.
I still receive an error, though: "Internal error. The profile for the user
is a temporary profile". Aaaaaargh!
Leif|||Windows 2003 Server. I was told that it is not a domain controller. I will
look at the kb article. hopefully it applies. Thanks. Frank
"Leif" wrote:
> > 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: Unable to load file
> > 'ReportingServicesEmailDeliveryProvider'.
> >
> > Source Error:
> >
> >
> > Line 256: <add assembly="System.EnterpriseServices,
> > Version=1.0.5000.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"/>
> > Line 257: <add assembly="System.Web.Mobile,
> > Version=1.0.5000.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"/>
> > Line 258: <add assembly="*"/>
> > Line 259: </assemblies>
> > Line 260:
> >
> Which OS? Is it a Domain controller?
> I received the same message on my lab computer after making it domain
> controller (Win2K, SP4). In KB824308 I found some useful information that
> helped me to some extent. Now rs is at least able to show part of the
> standard page.
> I still receive an error, though: "Internal error. The profile for the user
> is a temporary profile". Aaaaaargh!
> Leif
>
>

Report server spawning multiple w3wp.exe threads

We have Win2003 SP1, SQL 2000 SP4, RS 2000 SP2 installed on our dev
machine and it works ok - having problems using anonamous access under
IIS but that is another issue.....
On our production server ( win2003 SP1, SQL 2000 SP4 ) we installed RS
2000 and SP2, accepting all the default installation options accept
SSL, and we have the following problems....
When we try to access http:\\servername\reports it takes a good few
minutes to load the web page, after asking for a domain user account,
and then the whole server runs like a dog.
Just getting to the first web page creates 12-15 copies of w3wp.exe,
each of which swallow between 20 and 130 MB of memory, and ramps up the
CPU usage.
I you try to upload a report, or access an existing report it spawns
off another 8-10 copies of w3wp.exe and eats more memory, and seriously
slows the server down.
The only way to release the resources it has useems to be to restart
IIS.
I "think" that this may be due to some hardening or lock down of
production server, but I am struggling on what to do next.
The RS logs do not seem to show any problems, but the Win App log shows
"ID 124 ReportServer Service has been activated" 5-6 times for every
action you take against reporting services.
I have been through the "checking reporting services is installed"
guides and it all seems ok, so there is something key I am missing here
!!!
Anyone else had similar problems and found the solution, or could at
least point me in the right direction to progress this issue !An update...
Thanks our freinds at the hosting company, it turns out this was all
due to .Net framework and IIS
We have apps running under 1.1 and 2.0 frameworks, and RS was set to
use default app pool on the IIS config.
Created a new app pool, and let both RS directories use that instead -
bingo !
Lots of w3wp.exe still created, but not hosing the box, and the number
goes up and down as usage changes.
Advice has been to create a new app pool just for reporting services,
as it is a hungry beast !

Report Server Security Issue.

Hi,
We have installed SQL Server ReportingServices on a machine which can
be accessed from out side. now any one who types
http:\\sitename.com\reportserver can access the reports hosted here.
pls give me some solution how to solve this issue.
We tried removing anonymous access for that reportserver in IIS . but
then our application is not able to access the reports as we stored the
URLs of reports in database and call the reports when its required to
create a report.
is this the right way to implement the reporting services ?
JeswanthYou need to implement forms authentication. You do not want to have
anonymous.
--
Bruce Loehle-Conger
MVP SQL Server Reporting Services
<jeswanthj@.gmail.com> wrote in message
news:1147948860.574176.133460@.i40g2000cwc.googlegroups.com...
> Hi,
> We have installed SQL Server ReportingServices on a machine which can
> be accessed from out side. now any one who types
> http:\\sitename.com\reportserver can access the reports hosted here.
> pls give me some solution how to solve this issue.
> We tried removing anonymous access for that reportserver in IIS . but
> then our application is not able to access the reports as we stored the
> URLs of reports in database and call the reports when its required to
> create a report.
> is this the right way to implement the reporting services ?
>
> Jeswanth
>

Report Server Not Responding

Hi ..
I installed SSRS on W2K Server machine also running SQL Server 2005; after
the install completion I keep getting the following message:
"The report server is not responding. Verify that the report server is
running and can be accessed from this computer"
when I type http://<serverName>/ReportManager into the Address box in IE 6
if I type http://<serverName>/ReportServer in I get the following:
"Reporting Services Error
An internal error occurred on the report server. See the error log for more
details. (rsInternalError)
For more information about this error navigate to the report server on the
local server machine, or enable remote errors"
All other virtual directories on the web server are working ok; one thing I
notice is that it looks like the configuration was set up to access SQL
Server Express in a connection string named "LocalSqlServer" ... I don't
have SQL Server Express installed on the machine .. and there is a
connection string pointing to an MDF file that I don't see anywhere; I
changed the connection string to point to my the SQL2005 instance but it
really seems kind of stupid and useless to do that since I don't know what
database ReportServer and ReportManager want to use ...
Right now, I'm baffled with this thing; it looks like it probably works
fine if you happen to have just the right original configuration anticipated
by the team that designed the installers ... otherwise, you have a headache
...
so if anyone has some suggestions or info links I'd really appreciate it
...
TIAHi,
I am also working on the installing reporting Services , getting a different
error .
The XML page cannot be displayed
Cannot view XML input using XSL style sheet. Please correct the error and
then click the Refresh button, or try again later.
did you replace <servername> with localhost ?|||"Reshma" <Reshma@.discussions.microsoft.com> wrote in message
news:3DBD066C-F341-4AE9-9FF3-70AA30621E77@.microsoft.com...
> Hi,
> I am also working on the installing reporting Services , getting a
> different
> error .
> The XML page cannot be displayed
> Cannot view XML input using XSL style sheet. Please correct the error and
> then click the Refresh button, or try again later.
>
> did you replace <servername> with localhost ?
replace it where? I've used it in the IE address box ... doesn't work with
<localhost> OR <serverName> ...
all I'm getting is, "The report server is not responding. Verify that the
report server is running and can be accessed from this computer" ... well,
I'm trying to "verify" and this is the answer ... kind of stuck in a loop
here ...
The underlying Windows Service IS running, at least according to Service
Manager ... but that's not helping ...

REPORT SERVER COULD NOT FOUND http:\\localhost ?

Hi Gurus;

How can Start Report Server At my local Machine

I installed Reporting Services and Reporting Services SP2, Sql Server 2000 and Sql Server 2004 SP4 ,IIS and VS.net 2003 and 2005.

And Another Question ?f you not busy :)

How can show my report in my programs ?

Your report server can be reached with this url

http://localhost/reports

If you want to put reports on your apllications the easies way is to use the reportviewer, its a free control that you can download for visual studio .net 2003 and its included on the toolbox on visual studio 2005.

There are many ways more to render but thats the easier to start.

|||

thanks for your reply .

but ? cant work report server so http://localhost/reports doesn't consist on my machine and it is not appear Services(Local).

My first problem this is. How I can make Report Server works in my machine?

|||

welll your english a little difficult to understand.

1. Did u already install it?

2. It seems that you installed sql server without reporting services because there is no service on the service manager.

Install it again.

Report server cannot open a connection to the report server database

I am getting the following error, when trying to deploy. the report should point to a server which is in my network, but the report is on my machine. where i am trying to deploy locally but point to a different machine.

******************************************************

The report server cannot open a connection to the report server database. A connection to the database is required for all requests and processing.

***********************************

Thank you very much for the information.

Within Business Intelligence Development Studio, open your report project and select '-ProjectName- Properties' from the Project menu (should be at the bottom of the menu). Does the TargetServerURL show http://NetworkServerName/ReportServer or does it show http://localhost/ReportServer?

Jarret

|||

Jarret,

That was my mistake i recently changed my systems password, that did'nt get updated for the services.

so the services are not running, i had to go to each service and update the new password, and started all of them and then the sql sderver with reporting services all are up.

Thanks.

Report Server and Report Manager on different machines

It is possible to configure a system of servers such that
the Report Manager can be running on a separate machine
than the Report Server?
We are concerned about the security issues of exposing a
server with the Front Page Server Extensions installed on
it, because it will reside outside of our corporate
firewall. As an alternative, we are hoping we can host
the Web Server/IIS box outside the firewall, and have
this machine run the Report Manager, while another box
inside the firewall runs the Report Server (which,
incidentally, will also be a separate box than the data
server).
Whether the security concerns of FPSE are real or
perceived, our clients might not like them. So, is the
type of configuration described above at all possible?
If not, please explain why. If it is possible, please
explain how.
Thanks in advance!Front Page Server extensions are not necessary for Report Manager. Just to
make sure I checked one of my servers (Windows 2003) and the default website
which has Report Manager does not have FP server extension.
--
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Justin" <anonymous@.discussions.microsoft.com> wrote in message
news:13c701c4cc24$f8a701c0$a501280a@.phx.gbl...
> It is possible to configure a system of servers such that
> the Report Manager can be running on a separate machine
> than the Report Server?
> We are concerned about the security issues of exposing a
> server with the Front Page Server Extensions installed on
> it, because it will reside outside of our corporate
> firewall. As an alternative, we are hoping we can host
> the Web Server/IIS box outside the firewall, and have
> this machine run the Report Manager, while another box
> inside the firewall runs the Report Server (which,
> incidentally, will also be a separate box than the data
> server).
> Whether the security concerns of FPSE are real or
> perceived, our clients might not like them. So, is the
> type of configuration described above at all possible?
> If not, please explain why. If it is possible, please
> explain how.
> Thanks in advance!
>|||So, FPSE are only required on a Report Designer
installtion -- is that correct?
FPSE are a requirement for VisualStudio.NET installation,
which are required for Report Designer, right?
>--Original Message--
>Front Page Server extensions are not necessary for
Report Manager. Just to
>make sure I checked one of my servers (Windows 2003) and
the default website
>which has Report Manager does not have FP server
extension.
>--
>Bruce Loehle-Conger
>MVP SQL Server Reporting Services
>"Justin" <anonymous@.discussions.microsoft.com> wrote in
message
>news:13c701c4cc24$f8a701c0$a501280a@.phx.gbl...
>> It is possible to configure a system of servers such
that
>> the Report Manager can be running on a separate machine
>> than the Report Server?
>> We are concerned about the security issues of exposing
a
>> server with the Front Page Server Extensions installed
on
>> it, because it will reside outside of our corporate
>> firewall. As an alternative, we are hoping we can host
>> the Web Server/IIS box outside the firewall, and have
>> this machine run the Report Manager, while another box
>> inside the firewall runs the Report Server (which,
>> incidentally, will also be a separate box than the data
>> server).
>> Whether the security concerns of FPSE are real or
>> perceived, our clients might not like them. So, is the
>> type of configuration described above at all possible?
>> If not, please explain why. If it is possible, please
>> explain how.
>> Thanks in advance!
>
>.
>|||No. FPSE are not required for anything. The report designer does not even
have to have IIS.
You've gotten a misconception from somewhere that this is required.
--
Bruce Loehle-Conger
MVP SQL Server Reporting Services
<anonymous@.discussions.microsoft.com> wrote in message
news:623d01c4cc37$d426d9c0$a401280a@.phx.gbl...
> So, FPSE are only required on a Report Designer
> installtion -- is that correct?
> FPSE are a requirement for VisualStudio.NET installation,
> which are required for Report Designer, right?
>
> >--Original Message--
> >Front Page Server extensions are not necessary for
> Report Manager. Just to
> >make sure I checked one of my servers (Windows 2003) and
> the default website
> >which has Report Manager does not have FP server
> extension.
> >
> >--
> >Bruce Loehle-Conger
> >MVP SQL Server Reporting Services
> >
> >"Justin" <anonymous@.discussions.microsoft.com> wrote in
> message
> >news:13c701c4cc24$f8a701c0$a501280a@.phx.gbl...
> >> It is possible to configure a system of servers such
> that
> >> the Report Manager can be running on a separate machine
> >> than the Report Server?
> >>
> >> We are concerned about the security issues of exposing
> a
> >> server with the Front Page Server Extensions installed
> on
> >> it, because it will reside outside of our corporate
> >> firewall. As an alternative, we are hoping we can host
> >> the Web Server/IIS box outside the firewall, and have
> >> this machine run the Report Manager, while another box
> >> inside the firewall runs the Report Server (which,
> >> incidentally, will also be a separate box than the data
> >> server).
> >>
> >> Whether the security concerns of FPSE are real or
> >> perceived, our clients might not like them. So, is the
> >> type of configuration described above at all possible?
> >> If not, please explain why. If it is possible, please
> >> explain how.
> >>
> >> Thanks in advance!
> >>
> >
> >
> >.
> >|||Yes, I guess I do have that misconception. I thought
that in order to deploy a report from the report designer
to the report server, FPSE were required.
I'm glad to hear that this is not the case. I'll check
out our servers again and try to verify this.
Thanks.
>--Original Message--
>No. FPSE are not required for anything. The report
designer does not even
>have to have IIS.
>You've gotten a misconception from somewhere that this
is required.
>--
>Bruce Loehle-Conger
>MVP SQL Server Reporting Services
><anonymous@.discussions.microsoft.com> wrote in message
>news:623d01c4cc37$d426d9c0$a401280a@.phx.gbl...
>> So, FPSE are only required on a Report Designer
>> installtion -- is that correct?
>> FPSE are a requirement for VisualStudio.NET
installation,
>> which are required for Report Designer, right?
>>
>> >--Original Message--
>> >Front Page Server extensions are not necessary for
>> Report Manager. Just to
>> >make sure I checked one of my servers (Windows 2003)
and
>> the default website
>> >which has Report Manager does not have FP server
>> extension.
>> >
>> >--
>> >Bruce Loehle-Conger
>> >MVP SQL Server Reporting Services
>> >
>> >"Justin" <anonymous@.discussions.microsoft.com> wrote
in
>> message
>> >news:13c701c4cc24$f8a701c0$a501280a@.phx.gbl...
>> >> It is possible to configure a system of servers such
>> that
>> >> the Report Manager can be running on a separate
machine
>> >> than the Report Server?
>> >>
>> >> We are concerned about the security issues of
exposing
>> a
>> >> server with the Front Page Server Extensions
installed
>> on
>> >> it, because it will reside outside of our corporate
>> >> firewall. As an alternative, we are hoping we can
host
>> >> the Web Server/IIS box outside the firewall, and
have
>> >> this machine run the Report Manager, while another
box
>> >> inside the firewall runs the Report Server (which,
>> >> incidentally, will also be a separate box than the
data
>> >> server).
>> >>
>> >> Whether the security concerns of FPSE are real or
>> >> perceived, our clients might not like them. So, is
the
>> >> type of configuration described above at all
possible?
>> >> If not, please explain why. If it is possible,
please
>> >> explain how.
>> >>
>> >> Thanks in advance!
>> >>
>> >
>> >
>> >.
>> >
>
>.
>|||What you might be confused about is thinking about using Visual Studio for
regular ASP.Net development. It is common to have FPSE for that. However,
with RS you are not deploying webpages. What you are doing is using
webservices to deploy the RDL. If you look on the server you will see that
no files are even showing up there when you deploy. That is because the RDL
is being stored in the database, not in the file system.
--
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Justin" <anonymous@.discussions.microsoft.com> wrote in message
news:176001c4ccc2$b3afef70$a501280a@.phx.gbl...
> Yes, I guess I do have that misconception. I thought
> that in order to deploy a report from the report designer
> to the report server, FPSE were required.
> I'm glad to hear that this is not the case. I'll check
> out our servers again and try to verify this.
> Thanks.
> >--Original Message--
> >No. FPSE are not required for anything. The report
> designer does not even
> >have to have IIS.
> >
> >You've gotten a misconception from somewhere that this
> is required.
> >
> >--
> >Bruce Loehle-Conger
> >MVP SQL Server Reporting Services
> >
> ><anonymous@.discussions.microsoft.com> wrote in message
> >news:623d01c4cc37$d426d9c0$a401280a@.phx.gbl...
> >> So, FPSE are only required on a Report Designer
> >> installtion -- is that correct?
> >>
> >> FPSE are a requirement for VisualStudio.NET
> installation,
> >> which are required for Report Designer, right?
> >>
> >>
> >> >--Original Message--
> >> >Front Page Server extensions are not necessary for
> >> Report Manager. Just to
> >> >make sure I checked one of my servers (Windows 2003)
> and
> >> the default website
> >> >which has Report Manager does not have FP server
> >> extension.
> >> >
> >> >--
> >> >Bruce Loehle-Conger
> >> >MVP SQL Server Reporting Services
> >> >
> >> >"Justin" <anonymous@.discussions.microsoft.com> wrote
> in
> >> message
> >> >news:13c701c4cc24$f8a701c0$a501280a@.phx.gbl...
> >> >> It is possible to configure a system of servers such
> >> that
> >> >> the Report Manager can be running on a separate
> machine
> >> >> than the Report Server?
> >> >>
> >> >> We are concerned about the security issues of
> exposing
> >> a
> >> >> server with the Front Page Server Extensions
> installed
> >> on
> >> >> it, because it will reside outside of our corporate
> >> >> firewall. As an alternative, we are hoping we can
> host
> >> >> the Web Server/IIS box outside the firewall, and
> have
> >> >> this machine run the Report Manager, while another
> box
> >> >> inside the firewall runs the Report Server (which,
> >> >> incidentally, will also be a separate box than the
> data
> >> >> server).
> >> >>
> >> >> Whether the security concerns of FPSE are real or
> >> >> perceived, our clients might not like them. So, is
> the
> >> >> type of configuration described above at all
> possible?
> >> >> If not, please explain why. If it is possible,
> please
> >> >> explain how.
> >> >>
> >> >> Thanks in advance!
> >> >>
> >> >
> >> >
> >> >.
> >> >
> >
> >
> >.
> >|||Yes, that makes sense. I think that is exactly where I
was going wrong.
Thanks again!
>--Original Message--
>What you might be confused about is thinking about using
Visual Studio for
>regular ASP.Net development. It is common to have FPSE
for that. However,
>with RS you are not deploying webpages. What you are
doing is using
>webservices to deploy the RDL. If you look on the server
you will see that
>no files are even showing up there when you deploy. That
is because the RDL
>is being stored in the database, not in the file system.
>--
>Bruce Loehle-Conger
>MVP SQL Server Reporting Services
>"Justin" <anonymous@.discussions.microsoft.com> wrote in
message
>news:176001c4ccc2$b3afef70$a501280a@.phx.gbl...
>> Yes, I guess I do have that misconception. I thought
>> that in order to deploy a report from the report
designer
>> to the report server, FPSE were required.
>> I'm glad to hear that this is not the case. I'll check
>> out our servers again and try to verify this.
>> Thanks.
>> >--Original Message--
>> >No. FPSE are not required for anything. The report
>> designer does not even
>> >have to have IIS.
>> >
>> >You've gotten a misconception from somewhere that this
>> is required.
>> >
>> >--
>> >Bruce Loehle-Conger
>> >MVP SQL Server Reporting Services
>> >
>> ><anonymous@.discussions.microsoft.com> wrote in message
>> >news:623d01c4cc37$d426d9c0$a401280a@.phx.gbl...
>> >> So, FPSE are only required on a Report Designer
>> >> installtion -- is that correct?
>> >>
>> >> FPSE are a requirement for VisualStudio.NET
>> installation,
>> >> which are required for Report Designer, right?
>> >>
>> >>
>> >> >--Original Message--
>> >> >Front Page Server extensions are not necessary for
>> >> Report Manager. Just to
>> >> >make sure I checked one of my servers (Windows
2003)
>> and
>> >> the default website
>> >> >which has Report Manager does not have FP server
>> >> extension.
>> >> >
>> >> >--
>> >> >Bruce Loehle-Conger
>> >> >MVP SQL Server Reporting Services
>> >> >
>> >> >"Justin" <anonymous@.discussions.microsoft.com>
wrote
>> in
>> >> message
>> >> >news:13c701c4cc24$f8a701c0$a501280a@.phx.gbl...
>> >> >> It is possible to configure a system of servers
such
>> >> that
>> >> >> the Report Manager can be running on a separate
>> machine
>> >> >> than the Report Server?
>> >> >>
>> >> >> We are concerned about the security issues of
>> exposing
>> >> a
>> >> >> server with the Front Page Server Extensions
>> installed
>> >> on
>> >> >> it, because it will reside outside of our
corporate
>> >> >> firewall. As an alternative, we are hoping we
can
>> host
>> >> >> the Web Server/IIS box outside the firewall, and
>> have
>> >> >> this machine run the Report Manager, while
another
>> box
>> >> >> inside the firewall runs the Report Server
(which,
>> >> >> incidentally, will also be a separate box than
the
>> data
>> >> >> server).
>> >> >>
>> >> >> Whether the security concerns of FPSE are real or
>> >> >> perceived, our clients might not like them. So,
is
>> the
>> >> >> type of configuration described above at all
>> possible?
>> >> >> If not, please explain why. If it is possible,
>> please
>> >> >> explain how.
>> >> >>
>> >> >> Thanks in advance!
>> >> >>
>> >> >
>> >> >
>> >> >.
>> >> >
>> >
>> >
>> >.
>> >
>
>.
>

Report Server - Access Error

Any help appreciated...
Installed Reporting Services on Win2003 machine with a SQL2000 db.
Reporting Services was installed with an IIS without default website, running
IIS5.0 Isolation mode.
When navigating to http://<hostheader>/reports I get the folllowing error...
The report server is not responding. Verify that the report server is
running and can be accessed from this computer.
When navigating to http://<hostheader>/ReportServer, the following error
occurs...
The report server is not responding. Verify that the report server is
running and can be accessed from this computer.
I have ensure the account running reports is included in the group running
the webservices. Also made the change to utilise <ReportServerURL> to the
http://<hostheader>/ReportServer.
Any assistance appreciated...
JamesHi, James
You either need to have the default website in IIS in order to use
Reporting Services, or you must specify a different website in which
the Reports and ReportService virtual directories will be created.
To use a different website than the Default IIS site, you will need to
change the configuration files for the report server app, service, and
report manager app. Please see the following article for more
information on how to setup RS for a non-Default website:
RS 2005 BOL => http://msdn2.microsoft.com/en-us/library/ms155921.aspx
couldn't find the equivalent BOL article for RS2000 in the MSDN, so
here is a link to an article on the web that will suffice:
http://www.awprofessional.com/articles/article.asp?p=357694&seqNum=3&rl=1
Have fun!
Regards,
Thiago Silva
JamesC wrote:
> Any help appreciated...
> Installed Reporting Services on Win2003 machine with a SQL2000 db.
> Reporting Services was installed with an IIS without default website, running
> IIS5.0 Isolation mode.
> When navigating to http://<hostheader>/reports I get the folllowing error...
> The report server is not responding. Verify that the report server is
> running and can be accessed from this computer.
>
> When navigating to http://<hostheader>/ReportServer, the following error
> occurs...
>
> The report server is not responding. Verify that the report server is
> running and can be accessed from this computer.
>
> I have ensure the account running reports is included in the group running
> the webservices. Also made the change to utilise <ReportServerURL> to the
> http://<hostheader>/ReportServer.
> Any assistance appreciated...
> James|||All resolved, needed to ensure that the web server was not running in IIS5.0
isolation mode.
Thanks.
"tafs7" wrote:
> Hi, James
> You either need to have the default website in IIS in order to use
> Reporting Services, or you must specify a different website in which
> the Reports and ReportService virtual directories will be created.
> To use a different website than the Default IIS site, you will need to
> change the configuration files for the report server app, service, and
> report manager app. Please see the following article for more
> information on how to setup RS for a non-Default website:
> RS 2005 BOL => http://msdn2.microsoft.com/en-us/library/ms155921.aspx
> couldn't find the equivalent BOL article for RS2000 in the MSDN, so
> here is a link to an article on the web that will suffice:
> http://www.awprofessional.com/articles/article.asp?p=357694&seqNum=3&rl=1
> Have fun!
> Regards,
> Thiago Silva
> JamesC wrote:
> > Any help appreciated...
> >
> > Installed Reporting Services on Win2003 machine with a SQL2000 db.
> > Reporting Services was installed with an IIS without default website, running
> > IIS5.0 Isolation mode.
> >
> > When navigating to http://<hostheader>/reports I get the folllowing error...
> >
> > The report server is not responding. Verify that the report server is
> > running and can be accessed from this computer.
> >
> >
> > When navigating to http://<hostheader>/ReportServer, the following error
> > occurs...
> >
> >
> > The report server is not responding. Verify that the report server is
> > running and can be accessed from this computer.
> >
> >
> > I have ensure the account running reports is included in the group running
> > the webservices. Also made the change to utilise <ReportServerURL> to the
> > http://<hostheader>/ReportServer.
> >
> > Any assistance appreciated...
> >
> > James
>

Report render to PDF hangs

I've got a complex report with many subreports that is running on a reporting services 2005 machine with sp2 installed. The report was working well, producing a 2800 page report in under 10 minutes. I made a change to an expression in a table's column header and one change to the detail and the report stopped working. It would just hang for hours with no messages in the logs.

I tried to simplify what the report server had to do by removing the sum's to the database side's stored proc but that didn't work. I finally managed to get the report to work by removing a totals section to a subreport. I've also had the same hanging condition occur when I merged some columns in the table. I also found a workaround for this problem.

Is anyone else finding problems like this? They don't seem to be code related.

Is there a limit to how complex a report can be in reporting services or the PDF rendering part of the process?

Thanks for any info

There is no easy to define limit to how "much" of a report can be rendered to PDF. It depends on size and complexity of the report and muscle of the server(s). Can you describe the hardware a bit? If you capture a perfmon while the hang is occuring, how does CPU, memory, disk, and network look? Also, is this reproducible? If you revert the change, does the report export?

Thank you.

|||

The machines running are 4 processor 3.2Ghz zeon's with 3GB Ram.

We didn't run perfmon, but normally get paged if there are performance issues.

I am able to reproduce this problem. I narrowed the recordset down to a particular agency, a subset of the full recordset The subset recordset contains 59 rows for the main report and 20 rows for the subreport, so it's not a large amount of data. We have agencies that are many times more complicated that print fine.

Strangely enough, I got it to work, when I pushed off the totals section to a subreport. That section had 2 running sums in it and some expressions based on data fields. I passed those over to the subreport as parameters and it worked fine.

This is not the only time, we've had this hang and had to look for a workaround. I also had a problem like this when I merged some columns in a table. The problem was happening to a completely different agency than before. Now when I develop in this report, I do one thing at a time, then deploy and run to be sure I didn't introduce another hang situation.

Is this behavior common to reporting services?

|||

If the dataset is large, the report is complex, the hardware is underpowered, or some combination of the three, exporting to PDF can get bogged down, even in SQL Server 2005 SP2. One way to figure out what's going on is to look at the ExecutionLog table in the ReportServer database.

Execute the report and then look at the last 5 columns. If RowCount is large, consider pushing off some data filtering into the TSQL - this should also decrease TimeDataRetrieval. If TimeProcessing is large, see if there is anything you're doing in the report that can be better handled by SQL server - like, sorting or aggregation. Also, try and reduce the complexity of any expressions you have in the report. If TimeRendering is large, it could be you're running into inefficiencies in the rendering engine. We've made good progress and improved perf in RS 2005 but we're still not where I'd like us to be so have more work to do. If ByteCount is large, consider breaking the report up so users don't have to deal with 50M PDF files. If archival is your goal, you might consider a different format like HTML that is much easier to grep later than PDF. Tudor has some suggestions as well on http://blogs.msdn.com/tudortr/archive/2004/06/28/167969.aspx.

"Hanging" is not common, though slow rendering when there's a lot to do or not enough hardware to do it on is more common.

I don't understand why merging columns would make that much of an impact, however. If you have a repro, please open a bug so I can take a look. If you can't get to http://connect.microsoft.com, you can email me the details directly (click on my name to the left and you'll find my email address).

Thank you.

|||

Hi Donovan,

Thanks for your help.

I've got a question still, I'm not sure that this is bug ticket worthy so I figured I'll run it by you here first.

This is from the ExecutionLog table.

This report was successful. This record is the full recordset and produced. I moved a totals section to a sub report to get it to work.

RequestType Format TimeStart TimeEnd TimeDataRetrieval TimeProcessing TimeRendering Source Status ByteCount RowCount

-- -- -- -- -- - --

0 PDF 2007-03-09 10:14:42.723 2007-03-09 10:22:30.500 19070 269112 179356 1 rsSuccess 8969543 8569

This recordset here, is one that didn't work. This code is prior to me moving the totals section out to a subreport. Also, this recordset is a subset, just one agency and it's associated records. After a half hour I cancelled the job.

The TimeRendering is very large and the TimeDataRetrieval also seems large for that recordset.

RequestType Format TimeStart TimeEnd TimeDataRetrieval TimeProcessing TimeRendering Source Status ByteCount RowCount

-- - -- -- -- -- - - --

0 PDF 2007-03-08 10:47:09.303 2007-03-08 11:15:53.803 20642 2690 1700930 1 rsJobWasCanceled 0 131

The difference between the 2 versions of code, is that the one that's failing has 3 footer rows for the same grouping, 4 of the text boxes contain =FormatCurrency(Fields!XYZ.Value) type values and one contains an =IIF(Fields!CompType.Value = "SA", "XYZ Based Compensation", "ABC Based Compensation") + " Totals For This Period:"

I replaced those 3 footers, with one footer that calls a subreport, ironically, the sub reports parameters contains the same formatcurrency items and the iif.

I'm not sure what to think, it looks like a bug, but wouldn't TimeDataRetrieval indicate database side inefficiency?

What do you think?

Scott

|||

That doesn't sound right - time rendering seems too high. Would you please email me a copy of the rdls so I can see what's happening in the code?

The TIFF and PDF renderer share a lot of the same code. Is TIFF also that slow in exporting that report?

Regarding the TimeDataRetrieval column, if you take the queries out of the reports and run them against the server manually, how do the times compare?

Thank you.

Report render to PDF hangs

I've got a complex report with many subreports that is running on a reporting services 2005 machine with sp2 installed. The report was working well, producing a 2800 page report in under 10 minutes. I made a change to an expression in a table's column header and one change to the detail and the report stopped working. It would just hang for hours with no messages in the logs.

I tried to simplify what the report server had to do by removing the sum's to the database side's stored proc but that didn't work. I finally managed to get the report to work by removing a totals section to a subreport. I've also had the same hanging condition occur when I merged some columns in the table. I also found a workaround for this problem.

Is anyone else finding problems like this? They don't seem to be code related.

Is there a limit to how complex a report can be in reporting services or the PDF rendering part of the process?

Thanks for any info

There is no easy to define limit to how "much" of a report can be rendered to PDF. It depends on size and complexity of the report and muscle of the server(s). Can you describe the hardware a bit? If you capture a perfmon while the hang is occuring, how does CPU, memory, disk, and network look? Also, is this reproducible? If you revert the change, does the report export?

Thank you.

|||

The machines running are 4 processor 3.2Ghz zeon's with 3GB Ram.

We didn't run perfmon, but normally get paged if there are performance issues.

I am able to reproduce this problem. I narrowed the recordset down to a particular agency, a subset of the full recordset The subset recordset contains 59 rows for the main report and 20 rows for the subreport, so it's not a large amount of data. We have agencies that are many times more complicated that print fine.

Strangely enough, I got it to work, when I pushed off the totals section to a subreport. That section had 2 running sums in it and some expressions based on data fields. I passed those over to the subreport as parameters and it worked fine.

This is not the only time, we've had this hang and had to look for a workaround. I also had a problem like this when I merged some columns in a table. The problem was happening to a completely different agency than before. Now when I develop in this report, I do one thing at a time, then deploy and run to be sure I didn't introduce another hang situation.

Is this behavior common to reporting services?

|||

If the dataset is large, the report is complex, the hardware is underpowered, or some combination of the three, exporting to PDF can get bogged down, even in SQL Server 2005 SP2. One way to figure out what's going on is to look at the ExecutionLog table in the ReportServer database.

Execute the report and then look at the last 5 columns. If RowCount is large, consider pushing off some data filtering into the TSQL - this should also decrease TimeDataRetrieval. If TimeProcessing is large, see if there is anything you're doing in the report that can be better handled by SQL server - like, sorting or aggregation. Also, try and reduce the complexity of any expressions you have in the report. If TimeRendering is large, it could be you're running into inefficiencies in the rendering engine. We've made good progress and improved perf in RS 2005 but we're still not where I'd like us to be so have more work to do. If ByteCount is large, consider breaking the report up so users don't have to deal with 50M PDF files. If archival is your goal, you might consider a different format like HTML that is much easier to grep later than PDF. Tudor has some suggestions as well on http://blogs.msdn.com/tudortr/archive/2004/06/28/167969.aspx.

"Hanging" is not common, though slow rendering when there's a lot to do or not enough hardware to do it on is more common.

I don't understand why merging columns would make that much of an impact, however. If you have a repro, please open a bug so I can take a look. If you can't get to http://connect.microsoft.com, you can email me the details directly (click on my name to the left and you'll find my email address).

Thank you.

|||

Hi Donovan,

Thanks for your help.

I've got a question still, I'm not sure that this is bug ticket worthy so I figured I'll run it by you here first.

This is from the ExecutionLog table.

This report was successful. This record is the full recordset and produced. I moved a totals section to a sub report to get it to work.

RequestType Format TimeStart TimeEnd TimeDataRetrieval TimeProcessing TimeRendering Source Status ByteCount RowCount -- -- -- -- -- - -- 0 PDF 2007-03-09 10:14:42.723 2007-03-09 10:22:30.500 19070 269112 179356 1 rsSuccess 8969543 8569

This recordset here, is one that didn't work. This code is prior to me moving the totals section out to a subreport. Also, this recordset is a subset, just one agency and it's associated records. After a half hour I cancelled the job.

The TimeRendering is very large and the TimeDataRetrieval also seems large for that recordset.

RequestType Format TimeStart TimeEnd TimeDataRetrieval TimeProcessing TimeRendering Source Status ByteCount RowCount -- - -- -- -- -- - - -- 0 PDF 2007-03-08 10:47:09.303 2007-03-08 11:15:53.803 20642 2690 1700930 1 rsJobWasCanceled 0 131

The difference between the 2 versions of code, is that the one that's failing has 3 footer rows for the same grouping, 4 of the text boxes contain =FormatCurrency(Fields!XYZ.Value) type values and one contains an =IIF(Fields!CompType.Value = "SA", "XYZ Based Compensation", "ABC Based Compensation") + " Totals For This Period:"

I replaced those 3 footers, with one footer that calls a subreport, ironically, the sub reports parameters contains the same formatcurrency items and the iif.

I'm not sure what to think, it looks like a bug, but wouldn't TimeDataRetrieval indicate database side inefficiency?

What do you think?

Scott

|||

That doesn't sound right - time rendering seems too high. Would you please email me a copy of the rdls so I can see what's happening in the code?

The TIFF and PDF renderer share a lot of the same code. Is TIFF also that slow in exporting that report?

Regarding the TimeDataRetrieval column, if you take the queries out of the reports and run them against the server manually, how do the times compare?

Thank you.