Report Error when 2 pages for multiple records

We have a web app, built in .Net, with reporting services as our reporting
tool. The problem we are having is when we have a report that goes to
numerous people and the report is 2 pages long. When we make it 1 page,
legal size, it works fine (avg records are 500-900). When this report is
generated it is created in a pdf format. I can run it on report services
manager and in the viewer it takes approx 10 secs or less to run and render,
but when we create the pdf it spikes the processor up to 90% and if it's a 2
page report it generates an error.PDF's take significantly longer than HTML but it surprises me that a 2 page
report you see much of a difference. Do you have any service packs
installed. If not, my advice is to install SP2.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"bssolutions" <bssolutions@.discussions.microsoft.com> wrote in message
news:BBA2388F-E062-4368-987A-62CD9298BD14@.microsoft.com...
> We have a web app, built in .Net, with reporting services as our reporting
> tool. The problem we are having is when we have a report that goes to
> numerous people and the report is 2 pages long. When we make it 1 page,
> legal size, it works fine (avg records are 500-900). When this report is
> generated it is created in a pdf format. I can run it on report services
> manager and in the viewer it takes approx 10 secs or less to run and
> render,
> but when we create the pdf it spikes the processor up to 90% and if it's a
> 2
> page report it generates an error.|||I have all of the service packs installed. This is a 2 page report that
generates approx 950 pages. I have similar reports, but set to legal single
page, that generate over 1000 pages in pdf. The error message I get is:
"Server Error in '/' Application.
The underlying connection was closed: An unexpected error occurred on a
receive.
Description: An unhandled exception occurred during the execution of the
current web request. Please review the stack trace for more information about
the error and where it originated in the code.
Exception Details: System.Net.WebException: The underlying connection was
closed: An unexpected error occurred on a receive.
Source Error:
An unhandled exception was generated during the execution of the current web
request. Information regarding the origin and location of the exception can
be identified using the exception stack trace below.
Stack Trace:
[WebException: The underlying connection was closed: An unexpected error
occurred on a receive.]
System.Web.Services.Protocols.WebClientProtocol.GetWebResponse(WebReques
t request) +58
System.Web.Services.Protocols.HttpWebClientProtocol.GetWebResponse(WebRe
quest request) +5
System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String
methodName, Object[] parameters) +183
LAMS.SQLReportServer.ReportingService.Render(String Report, String
Format, String HistoryID, String DeviceInfo, ParameterValue[] Parameters,
DataSourceCredentials[] Credentials, String ShowHideToggle, String& Encoding,
String& MimeType, ParameterValue[]& ParametersUsed, Warning[]& Warnings,
String[]& StreamIds) +141
LAMS.ReportViewer.RenderPDFReport() +618
LAMS.ReportViewer.Page_Load(Object sender, EventArgs e) +88
System.Web.UI.Control.OnLoad(EventArgs e) +67
System.Web.UI.Control.LoadRecursive() +35
System.Web.UI.Page.ProcessRequestMain() +750"
"Bruce L-C [MVP]" wrote:
> PDF's take significantly longer than HTML but it surprises me that a 2 page
> report you see much of a difference. Do you have any service packs
> installed. If not, my advice is to install SP2.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "bssolutions" <bssolutions@.discussions.microsoft.com> wrote in message
> news:BBA2388F-E062-4368-987A-62CD9298BD14@.microsoft.com...
> > We have a web app, built in .Net, with reporting services as our reporting
> > tool. The problem we are having is when we have a report that goes to
> > numerous people and the report is 2 pages long. When we make it 1 page,
> > legal size, it works fine (avg records are 500-900). When this report is
> > generated it is created in a pdf format. I can run it on report services
> > manager and in the viewer it takes approx 10 secs or less to run and
> > render,
> > but when we create the pdf it spikes the processor up to 90% and if it's a
> > 2
> > page report it generates an error.
>
>|||OK, we had a failure to communicate. You said a 2 page report and I thought
it was 2 pages long. You mean 2 pages per record.
RS renders everything in RAM. Formats make a big difference in CPU
utilizations. CSV, HTML are very fast. PDF and Excel are much slower and
much much more intensive in resources required. My personal feeling is that
when you are talking about that many pages it is an inappropriate use of RS.
It is just not designed to be outputting 1000 pages of PDF. Users cannot
look at that many pages anyway. You should consider drill through technique.
Show the users what they need to see. I do know that sometimes users need to
pull data into another program but that is not what PDF format is used for.
Excel is another matter (although Excel can't handle 100,000 rows either).
For Excel you could use CSV to get around this. For PDF there is no work
around. More RAM helps but you really are overloading the server when you
are doing this.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"bssolutions" <bssolutions@.discussions.microsoft.com> wrote in message
news:790D7C48-1AB7-4F2A-A1C3-A1CF679B9B52@.microsoft.com...
>I have all of the service packs installed. This is a 2 page report that
> generates approx 950 pages. I have similar reports, but set to legal
> single
> page, that generate over 1000 pages in pdf. The error message I get is:
> "Server Error in '/' Application.
> The underlying connection was closed: An unexpected error occurred on a
> receive.
> Description: An unhandled exception occurred during the execution of the
> current web request. Please review the stack trace for more information
> about
> the error and where it originated in the code.
> Exception Details: System.Net.WebException: The underlying connection was
> closed: An unexpected error occurred on a receive.
> Source Error:
> An unhandled exception was generated during the execution of the current
> web
> request. Information regarding the origin and location of the exception
> can
> be identified using the exception stack trace below.
> Stack Trace:
> [WebException: The underlying connection was closed: An unexpected error
> occurred on a receive.]
> System.Web.Services.Protocols.WebClientProtocol.GetWebResponse(WebReques
> t request) +58
> System.Web.Services.Protocols.HttpWebClientProtocol.GetWebResponse(WebRe
> quest request) +5
> System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String
> methodName, Object[] parameters) +183
> LAMS.SQLReportServer.ReportingService.Render(String Report, String
> Format, String HistoryID, String DeviceInfo, ParameterValue[] Parameters,
> DataSourceCredentials[] Credentials, String ShowHideToggle, String&
> Encoding,
> String& MimeType, ParameterValue[]& ParametersUsed, Warning[]& Warnings,
> String[]& StreamIds) +141
> LAMS.ReportViewer.RenderPDFReport() +618
> LAMS.ReportViewer.Page_Load(Object sender, EventArgs e) +88
> System.Web.UI.Control.OnLoad(EventArgs e) +67
> System.Web.UI.Control.LoadRecursive() +35
> System.Web.UI.Page.ProcessRequestMain() +750"
> "Bruce L-C [MVP]" wrote:
>> PDF's take significantly longer than HTML but it surprises me that a 2
>> page
>> report you see much of a difference. Do you have any service packs
>> installed. If not, my advice is to install SP2.
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>> "bssolutions" <bssolutions@.discussions.microsoft.com> wrote in message
>> news:BBA2388F-E062-4368-987A-62CD9298BD14@.microsoft.com...
>> > We have a web app, built in .Net, with reporting services as our
>> > reporting
>> > tool. The problem we are having is when we have a report that goes to
>> > numerous people and the report is 2 pages long. When we make it 1
>> > page,
>> > legal size, it works fine (avg records are 500-900). When this report
>> > is
>> > generated it is created in a pdf format. I can run it on report
>> > services
>> > manager and in the viewer it takes approx 10 secs or less to run and
>> > render,
>> > but when we create the pdf it spikes the processor up to 90% and if
>> > it's a
>> > 2
>> > page report it generates an error.
>>|||Thanks for the input. The only problem is this is our leasing application
and we have to print mass batch of renewals once a year. I am thinking of
setting it on a schedule but that would remove a data range filter that is in
place and is changable by the user. Any suggestions?
"Bruce L-C [MVP]" wrote:
> OK, we had a failure to communicate. You said a 2 page report and I thought
> it was 2 pages long. You mean 2 pages per record.
> RS renders everything in RAM. Formats make a big difference in CPU
> utilizations. CSV, HTML are very fast. PDF and Excel are much slower and
> much much more intensive in resources required. My personal feeling is that
> when you are talking about that many pages it is an inappropriate use of RS.
> It is just not designed to be outputting 1000 pages of PDF. Users cannot
> look at that many pages anyway. You should consider drill through technique.
> Show the users what they need to see. I do know that sometimes users need to
> pull data into another program but that is not what PDF format is used for.
> Excel is another matter (although Excel can't handle 100,000 rows either).
> For Excel you could use CSV to get around this. For PDF there is no work
> around. More RAM helps but you really are overloading the server when you
> are doing this.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "bssolutions" <bssolutions@.discussions.microsoft.com> wrote in message
> news:790D7C48-1AB7-4F2A-A1C3-A1CF679B9B52@.microsoft.com...
> >I have all of the service packs installed. This is a 2 page report that
> > generates approx 950 pages. I have similar reports, but set to legal
> > single
> > page, that generate over 1000 pages in pdf. The error message I get is:
> >
> > "Server Error in '/' Application.
> > The underlying connection was closed: An unexpected error occurred on a
> > receive.
> > Description: An unhandled exception occurred during the execution of the
> > current web request. Please review the stack trace for more information
> > about
> > the error and where it originated in the code.
> > Exception Details: System.Net.WebException: The underlying connection was
> > closed: An unexpected error occurred on a receive.
> > Source Error:
> > An unhandled exception was generated during the execution of the current
> > web
> > request. Information regarding the origin and location of the exception
> > can
> > be identified using the exception stack trace below.
> >
> > Stack Trace:
> > [WebException: The underlying connection was closed: An unexpected error
> > occurred on a receive.]
> > System.Web.Services.Protocols.WebClientProtocol.GetWebResponse(WebReques
> > t request) +58
> > System.Web.Services.Protocols.HttpWebClientProtocol.GetWebResponse(WebRe
> > quest request) +5
> > System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String
> > methodName, Object[] parameters) +183
> > LAMS.SQLReportServer.ReportingService.Render(String Report, String
> > Format, String HistoryID, String DeviceInfo, ParameterValue[] Parameters,
> > DataSourceCredentials[] Credentials, String ShowHideToggle, String&
> > Encoding,
> > String& MimeType, ParameterValue[]& ParametersUsed, Warning[]& Warnings,
> > String[]& StreamIds) +141
> > LAMS.ReportViewer.RenderPDFReport() +618
> > LAMS.ReportViewer.Page_Load(Object sender, EventArgs e) +88
> > System.Web.UI.Control.OnLoad(EventArgs e) +67
> > System.Web.UI.Control.LoadRecursive() +35
> > System.Web.UI.Page.ProcessRequestMain() +750"
> >
> > "Bruce L-C [MVP]" wrote:
> >
> >> PDF's take significantly longer than HTML but it surprises me that a 2
> >> page
> >> report you see much of a difference. Do you have any service packs
> >> installed. If not, my advice is to install SP2.
> >>
> >>
> >> --
> >> Bruce Loehle-Conger
> >> MVP SQL Server Reporting Services
> >>
> >> "bssolutions" <bssolutions@.discussions.microsoft.com> wrote in message
> >> news:BBA2388F-E062-4368-987A-62CD9298BD14@.microsoft.com...
> >> > We have a web app, built in .Net, with reporting services as our
> >> > reporting
> >> > tool. The problem we are having is when we have a report that goes to
> >> > numerous people and the report is 2 pages long. When we make it 1
> >> > page,
> >> > legal size, it works fine (avg records are 500-900). When this report
> >> > is
> >> > generated it is created in a pdf format. I can run it on report
> >> > services
> >> > manager and in the viewer it takes approx 10 secs or less to run and
> >> > render,
> >> > but when we create the pdf it spikes the processor up to 90% and if
> >> > it's a
> >> > 2
> >> > page report it generates an error.
> >>
> >>
> >>
>
>|||If you can have parameters that allows you to do a subset then schedule the
report multiple times just varying the parameter and print say 100 pages at
a time.
--
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"bssolutions" <bssolutions@.discussions.microsoft.com> wrote in message
news:6B4C566B-C41C-49FD-BF58-2FCD7B9656E3@.microsoft.com...
> Thanks for the input. The only problem is this is our leasing application
> and we have to print mass batch of renewals once a year. I am thinking of
> setting it on a schedule but that would remove a data range filter that is
> in
> place and is changable by the user. Any suggestions?
> "Bruce L-C [MVP]" wrote:
>> OK, we had a failure to communicate. You said a 2 page report and I
>> thought
>> it was 2 pages long. You mean 2 pages per record.
>> RS renders everything in RAM. Formats make a big difference in CPU
>> utilizations. CSV, HTML are very fast. PDF and Excel are much slower and
>> much much more intensive in resources required. My personal feeling is
>> that
>> when you are talking about that many pages it is an inappropriate use of
>> RS.
>> It is just not designed to be outputting 1000 pages of PDF. Users cannot
>> look at that many pages anyway. You should consider drill through
>> technique.
>> Show the users what they need to see. I do know that sometimes users need
>> to
>> pull data into another program but that is not what PDF format is used
>> for.
>> Excel is another matter (although Excel can't handle 100,000 rows
>> either).
>> For Excel you could use CSV to get around this. For PDF there is no work
>> around. More RAM helps but you really are overloading the server when you
>> are doing this.
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>> "bssolutions" <bssolutions@.discussions.microsoft.com> wrote in message
>> news:790D7C48-1AB7-4F2A-A1C3-A1CF679B9B52@.microsoft.com...
>> >I have all of the service packs installed. This is a 2 page report that
>> > generates approx 950 pages. I have similar reports, but set to legal
>> > single
>> > page, that generate over 1000 pages in pdf. The error message I get
>> > is:
>> >
>> > "Server Error in '/' Application.
>> > The underlying connection was closed: An unexpected error occurred on a
>> > receive.
>> > Description: An unhandled exception occurred during the execution of
>> > the
>> > current web request. Please review the stack trace for more information
>> > about
>> > the error and where it originated in the code.
>> > Exception Details: System.Net.WebException: The underlying connection
>> > was
>> > closed: An unexpected error occurred on a receive.
>> > Source Error:
>> > An unhandled exception was generated during the execution of the
>> > current
>> > web
>> > request. Information regarding the origin and location of the exception
>> > can
>> > be identified using the exception stack trace below.
>> >
>> > Stack Trace:
>> > [WebException: The underlying connection was closed: An unexpected
>> > error
>> > occurred on a receive.]
>> > System.Web.Services.Protocols.WebClientProtocol.GetWebResponse(WebReques
>> > t request) +58
>> > System.Web.Services.Protocols.HttpWebClientProtocol.GetWebResponse(WebRe
>> > quest request) +5
>> > System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String
>> > methodName, Object[] parameters) +183
>> > LAMS.SQLReportServer.ReportingService.Render(String Report, String
>> > Format, String HistoryID, String DeviceInfo, ParameterValue[]
>> > Parameters,
>> > DataSourceCredentials[] Credentials, String ShowHideToggle, String&
>> > Encoding,
>> > String& MimeType, ParameterValue[]& ParametersUsed, Warning[]&
>> > Warnings,
>> > String[]& StreamIds) +141
>> > LAMS.ReportViewer.RenderPDFReport() +618
>> > LAMS.ReportViewer.Page_Load(Object sender, EventArgs e) +88
>> > System.Web.UI.Control.OnLoad(EventArgs e) +67
>> > System.Web.UI.Control.LoadRecursive() +35
>> > System.Web.UI.Page.ProcessRequestMain() +750"
>> >
>> > "Bruce L-C [MVP]" wrote:
>> >
>> >> PDF's take significantly longer than HTML but it surprises me that a 2
>> >> page
>> >> report you see much of a difference. Do you have any service packs
>> >> installed. If not, my advice is to install SP2.
>> >>
>> >>
>> >> --
>> >> Bruce Loehle-Conger
>> >> MVP SQL Server Reporting Services
>> >>
>> >> "bssolutions" <bssolutions@.discussions.microsoft.com> wrote in message
>> >> news:BBA2388F-E062-4368-987A-62CD9298BD14@.microsoft.com...
>> >> > We have a web app, built in .Net, with reporting services as our
>> >> > reporting
>> >> > tool. The problem we are having is when we have a report that goes
>> >> > to
>> >> > numerous people and the report is 2 pages long. When we make it 1
>> >> > page,
>> >> > legal size, it works fine (avg records are 500-900). When this
>> >> > report
>> >> > is
>> >> > generated it is created in a pdf format. I can run it on report
>> >> > services
>> >> > manager and in the viewer it takes approx 10 secs or less to run and
>> >> > render,
>> >> > but when we create the pdf it spikes the processor up to 90% and if
>> >> > it's a
>> >> > 2
>> >> > page report it generates an error.
>> >>
>> >>
>> >>
>>|||Thanks a bunch for the info Bruce.
"Bruce L-C [MVP]" wrote:
> If you can have parameters that allows you to do a subset then schedule the
> report multiple times just varying the parameter and print say 100 pages at
> a time.
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "bssolutions" <bssolutions@.discussions.microsoft.com> wrote in message
> news:6B4C566B-C41C-49FD-BF58-2FCD7B9656E3@.microsoft.com...
> > Thanks for the input. The only problem is this is our leasing application
> > and we have to print mass batch of renewals once a year. I am thinking of
> > setting it on a schedule but that would remove a data range filter that is
> > in
> > place and is changable by the user. Any suggestions?
> >
> > "Bruce L-C [MVP]" wrote:
> >
> >> OK, we had a failure to communicate. You said a 2 page report and I
> >> thought
> >> it was 2 pages long. You mean 2 pages per record.
> >>
> >> RS renders everything in RAM. Formats make a big difference in CPU
> >> utilizations. CSV, HTML are very fast. PDF and Excel are much slower and
> >> much much more intensive in resources required. My personal feeling is
> >> that
> >> when you are talking about that many pages it is an inappropriate use of
> >> RS.
> >> It is just not designed to be outputting 1000 pages of PDF. Users cannot
> >> look at that many pages anyway. You should consider drill through
> >> technique.
> >> Show the users what they need to see. I do know that sometimes users need
> >> to
> >> pull data into another program but that is not what PDF format is used
> >> for.
> >> Excel is another matter (although Excel can't handle 100,000 rows
> >> either).
> >> For Excel you could use CSV to get around this. For PDF there is no work
> >> around. More RAM helps but you really are overloading the server when you
> >> are doing this.
> >>
> >>
> >> --
> >> Bruce Loehle-Conger
> >> MVP SQL Server Reporting Services
> >>
> >> "bssolutions" <bssolutions@.discussions.microsoft.com> wrote in message
> >> news:790D7C48-1AB7-4F2A-A1C3-A1CF679B9B52@.microsoft.com...
> >> >I have all of the service packs installed. This is a 2 page report that
> >> > generates approx 950 pages. I have similar reports, but set to legal
> >> > single
> >> > page, that generate over 1000 pages in pdf. The error message I get
> >> > is:
> >> >
> >> > "Server Error in '/' Application.
> >> > The underlying connection was closed: An unexpected error occurred on a
> >> > receive.
> >> > Description: An unhandled exception occurred during the execution of
> >> > the
> >> > current web request. Please review the stack trace for more information
> >> > about
> >> > the error and where it originated in the code.
> >> > Exception Details: System.Net.WebException: The underlying connection
> >> > was
> >> > closed: An unexpected error occurred on a receive.
> >> > Source Error:
> >> > An unhandled exception was generated during the execution of the
> >> > current
> >> > web
> >> > request. Information regarding the origin and location of the exception
> >> > can
> >> > be identified using the exception stack trace below.
> >> >
> >> > Stack Trace:
> >> > [WebException: The underlying connection was closed: An unexpected
> >> > error
> >> > occurred on a receive.]
> >> > System.Web.Services.Protocols.WebClientProtocol.GetWebResponse(WebReques
> >> > t request) +58
> >> > System.Web.Services.Protocols.HttpWebClientProtocol.GetWebResponse(WebRe
> >> > quest request) +5
> >> > System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String
> >> > methodName, Object[] parameters) +183
> >> > LAMS.SQLReportServer.ReportingService.Render(String Report, String
> >> > Format, String HistoryID, String DeviceInfo, ParameterValue[]
> >> > Parameters,
> >> > DataSourceCredentials[] Credentials, String ShowHideToggle, String&
> >> > Encoding,
> >> > String& MimeType, ParameterValue[]& ParametersUsed, Warning[]&
> >> > Warnings,
> >> > String[]& StreamIds) +141
> >> > LAMS.ReportViewer.RenderPDFReport() +618
> >> > LAMS.ReportViewer.Page_Load(Object sender, EventArgs e) +88
> >> > System.Web.UI.Control.OnLoad(EventArgs e) +67
> >> > System.Web.UI.Control.LoadRecursive() +35
> >> > System.Web.UI.Page.ProcessRequestMain() +750"
> >> >
> >> > "Bruce L-C [MVP]" wrote:
> >> >
> >> >> PDF's take significantly longer than HTML but it surprises me that a 2
> >> >> page
> >> >> report you see much of a difference. Do you have any service packs
> >> >> installed. If not, my advice is to install SP2.
> >> >>
> >> >>
> >> >> --
> >> >> Bruce Loehle-Conger
> >> >> MVP SQL Server Reporting Services
> >> >>
> >> >> "bssolutions" <bssolutions@.discussions.microsoft.com> wrote in message
> >> >> news:BBA2388F-E062-4368-987A-62CD9298BD14@.microsoft.com...
> >> >> > We have a web app, built in .Net, with reporting services as our
> >> >> > reporting
> >> >> > tool. The problem we are having is when we have a report that goes
> >> >> > to
> >> >> > numerous people and the report is 2 pages long. When we make it 1
> >> >> > page,
> >> >> > legal size, it works fine (avg records are 500-900). When this
> >> >> > report
> >> >> > is
> >> >> > generated it is created in a pdf format. I can run it on report
> >> >> > services
> >> >> > manager and in the viewer it takes approx 10 secs or less to run and
> >> >> > render,
> >> >> > but when we create the pdf it spikes the processor up to 90% and if
> >> >> > it's a
> >> >> > 2
> >> >> > page report it generates an error.
> >> >>
> >> >>
> >> >>
> >>
> >>
> >>
>
>sql

Report designer-graphing tool

I am trying to have a horizontal bar graph which has a single bar, which
has spacing top and bottom but none left and right of the bar, however the
"side margings" doesnt seem to work, has anyone got any ideas how to do
this also I need the single bar to be as tall as the grid almost, so I need
to resize the bar manually.
Any ideas greatly received.
TIA
AndyChecking the Side Margins property should do exactly what you want. Also
check your Min and Max value property - these affect how your bar is drawn.
If you leave them empty, your chart should autoscale.
If that does not help, please post a picture of your chart, so that we can
see what you are trying to do.
--
Carsten Schielke
Software Development Engineer
SQL Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"Andy Bontoft-Robinson" <andy@.streets-heaver.com> wrote in message
news:Xns95406167DB603andystreetsheavercom@.207.46.248.16...
> I am trying to have a horizontal bar graph which has a single bar, which
> has spacing top and bottom but none left and right of the bar, however the
> "side margings" doesnt seem to work, has anyone got any ideas how to do
> this also I need the single bar to be as tall as the grid almost, so I
need
> to resize the bar manually.
> Any ideas greatly received.
> TIA
> Andysql

Report Designer tool?

The SQL 2008 product overview word document has a screenshot of "Report Designer"

The screenshot appear to be a new version of the Report Builder tool, but where is this version or this tool?

Thanks.

The new report designer is not available in the first public CTP released earlier this week. It will be in the next public CTP. An early preview and some of the other new features will be shown at TechEd sessions this week.

-- Robert

|||thanks !

Report Designer Client software

I've loaded the Report Services from Microsoft unto our server. How do I get the Client Designer tool loaded on other boxes. Does anyone know where the Install is to install the report designer into a Client machine?

Thanks
AlFound the answer already - You run the Report Services Install disk and disable the report services part of the install and only install the report designer.. dah.. Anyway it took me about a half hour to remember that SQL makes you run through the SQL Server install disk to load just the client. That was my clue to install the Designer portion of the software.

Thanks anyway.

ALsql

Report Builder: Error 401

I'm looking for some help/suggestions on how to solve an authentication problem we're having running the ad-hoc reporting tool (Report Builder). Here's the background:

1. It actually installs a client footprint the first time it is launched, and requires .NET 2.0 framework on the client. Authentication to the Report Server is through Windows NT authentication, then additional Reporting Service security controls what rights the accounts have (including the right to use Report Builder).

2. Currently, Windows NT authentication works for providing access to the Report Server, running reports published to the server, and doing other admin functions related to Reporting Services.

3. We are having a problem with accounts not being able to run Report Builder even though they have the correct rights, and it appears to be related to the specific PC being used. Serveral of us have accounts that used to work on our PCs, but no longer work. But the same account will work when used on another PC (which was actually in the same DNR subnet). I've also had someone use my account on their machine, and it worked. We've had others that have never been able to run Report Builder, even though they have the rights to do so. Bellow are error details returned to the client when trying to run the application.

4. Since the problem seems to be machine related and one of the client requirements is the .NET 2.0 framework, I tried un-installing and re-installing this, but it didn't correct the problem.

5. This problem occurs both on both the development server and the new server we will be using for production.

Not sure what to do next...any ideas? Would a network trace help? Or is there any additional info on the Report Server log that would help? Microsoft support?

Let me know what you think, or if you think there are others that might be able to help.

ERROR DETAILS:

PLATFORM VERSION INFO

Windows : 5.1.2600.131072 (Win32NT)

Common Language Runtime : 2.0.50727.42

System.Deployment.dll : 2.0.50727.42 (RTM.050727-4200)

mscorwks.dll : 2.0.50727.42 (RTM.050727-4200)

dfdll.dll : 2.0.50727.42 (RTM.050727-4200)

dfshim.dll : 2.0.50727.42 (RTM.050727-4200)

SOURCES

Deployment url : http://216.159.162.212/ReportServer/ReportBuilder/ReportBuilder.application

ERROR SUMMARY

Below is a summary of the errors, details of these errors are listed later in the log.

* Activation of http://216.159.162.212/ReportServer/ReportBuilder/ReportBuilder.application resulted in exception. Following failure messages were detected:

+ Downloading http://216.159.162.212/ReportServer/ReportBuilder/ReportBuilder.application did not succeed.

+ The remote server returned an error: (401) Unauthorized.

COMPONENT STORE TRANSACTION FAILURE SUMMARY

No transaction error was detected.

WARNINGS

There were no warnings during this operation.

OPERATION PROGRESS STATUS

* [8/3/2006 10:01:12 AM] : Activation of http://216.159.162.212/ReportServer/ReportBuilder/ReportBuilder.application has started.

ERROR DETAILS

Following errors were detected during this operation.

* [8/3/2006 10:01:12 AM] System.Deployment.Application.DeploymentDownloadException (Unknown subtype)

- Downloading http://216.159.162.212/ReportServer/ReportBuilder/ReportBuilder.application did not succeed.

- Source: System.Deployment

- Stack trace:

at System.Deployment.Application.SystemNetDownloader.DownloadSingleFile(DownloadQueueItem next)

at System.Deployment.Application.SystemNetDownloader.DownloadAllFiles()

at System.Deployment.Application.FileDownloader.Download(SubscriptionState subState)

at System.Deployment.Application.DownloadManager.DownloadManifestAsRawFile(Uri& sourceUri, String targetPath, IDownloadNotification notification, DownloadOptions options, ServerInformation& serverInformation)

at System.Deployment.Application.DownloadManager.DownloadDeploymentManifestDirectBypass(SubscriptionStore subStore, Uri& sourceUri, TempFile& tempFile, SubscriptionState& subState, IDownloadNotification notification, DownloadOptions options, ServerInformation& serverInformation)

at System.Deployment.Application.DownloadManager.DownloadDeploymentManifestBypass(SubscriptionStore subStore, Uri& sourceUri, TempFile& tempFile, SubscriptionState& subState, IDownloadNotification notification, DownloadOptions options)

at System.Deployment.Application.ApplicationActivator.PerformDeploymentActivation(Uri activationUri, Boolean isShortcut)

at System.Deployment.Application.ApplicationActivator.ActivateDeploymentWorker(Object state)

-- Inner Exception --

System.Net.WebException

- The remote server returned an error: (401) Unauthorized.

- Source: System

- Stack trace:

at System.Net.HttpWebRequest.GetResponse()

at System.Deployment.Application.SystemNetDownloader.DownloadSingleFile(DownloadQueueItem next)

COMPONENT STORE TRANSACTION DETAILS

No transaction information is available.

Did you ever figure this out? we are getting the same errors.

report builder, which edition of 2005?

My question:
Does the end-user reporting tool (report builder) in Sql Server 2005 exist
in the Standard Version or is it only in the Enterprise Version?
I have found a couple of conflicting articles on the web.
Thanks in advance.Just Enterprise.
Not sure about development version. Previously that version was identical to
enterprise.
--
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"chicagoclone" <chicagoclone@.discussions.microsoft.com> wrote in message
news:FAD2F770-CFA6-4F70-AD0C-662C2A99E7CD@.microsoft.com...
> My question:
> Does the end-user reporting tool (report builder) in Sql Server 2005 exist
> in the Standard Version or is it only in the Enterprise Version?
> I have found a couple of conflicting articles on the web.
> Thanks in advance.|||that is what I thought also but what about this link here. It has a
checkmark for standard...
http://www.microsoft.com/sql/2005/productinfo/sql2005features.mspx
More research found this information as well.
"This week, at Microsoft TechEd in Orlando, Florida, Microsoft turned a
complete 180 in the way the company will license SQL Server Reporting
Services and Report Builder. Microsoft was planning to include Report Builder
in SQL Server 2005 Enterprise Edition but not Standard Edition or other less
expensive SQL Server SKUs. I thought that was going to be a big mistake for
Microsoft, and many people in the SQL Server community agreed with me. But
this week, Microsoft Senior Vice President of Server Applications Paul
Flessner announced that Reporting Services will be included in all editions
of SQL Server 2005. In addition, the Workgroup and Standard Editions of SQL
Server 2005 will include Report Builder."
taken from this artice:
http://www.windowsitpro.com/SQLServer/Article/ArticleID/46694/46694.html
"Bruce L-C [MVP]" wrote:
> Just Enterprise.
> Not sure about development version. Previously that version was identical to
> enterprise.
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "chicagoclone" <chicagoclone@.discussions.microsoft.com> wrote in message
> news:FAD2F770-CFA6-4F70-AD0C-662C2A99E7CD@.microsoft.com...
> > My question:
> > Does the end-user reporting tool (report builder) in Sql Server 2005 exist
> > in the Standard Version or is it only in the Enterprise Version?
> >
> > I have found a couple of conflicting articles on the web.
> >
> > Thanks in advance.
>
>|||Well, how about that. The info I had was not that old but looks like prior
to TechEd they changed their mind.
--
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"chicagoclone" <chicagoclone@.discussions.microsoft.com> wrote in message
news:DF676812-82CA-4228-8EFA-56847C1282B7@.microsoft.com...
> that is what I thought also but what about this link here. It has a
> checkmark for standard...
> http://www.microsoft.com/sql/2005/productinfo/sql2005features.mspx
> More research found this information as well.
> "This week, at Microsoft TechEd in Orlando, Florida, Microsoft turned a
> complete 180 in the way the company will license SQL Server Reporting
> Services and Report Builder. Microsoft was planning to include Report
> Builder
> in SQL Server 2005 Enterprise Edition but not Standard Edition or other
> less
> expensive SQL Server SKUs. I thought that was going to be a big mistake
> for
> Microsoft, and many people in the SQL Server community agreed with me. But
> this week, Microsoft Senior Vice President of Server Applications Paul
> Flessner announced that Reporting Services will be included in all
> editions
> of SQL Server 2005. In addition, the Workgroup and Standard Editions of
> SQL
> Server 2005 will include Report Builder."
> taken from this artice:
> http://www.windowsitpro.com/SQLServer/Article/ArticleID/46694/46694.html
> "Bruce L-C [MVP]" wrote:
>> Just Enterprise.
>> Not sure about development version. Previously that version was identical
>> to
>> enterprise.
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>> "chicagoclone" <chicagoclone@.discussions.microsoft.com> wrote in message
>> news:FAD2F770-CFA6-4F70-AD0C-662C2A99E7CD@.microsoft.com...
>> > My question:
>> > Does the end-user reporting tool (report builder) in Sql Server 2005
>> > exist
>> > in the Standard Version or is it only in the Enterprise Version?
>> >
>> > I have found a couple of conflicting articles on the web.
>> >
>> > Thanks in advance.
>>|||From the official press release at TechEd 2005:
http://www.microsoft.com/presspass/press/2005/jun05/TechEd2005Day2PR.mspx
"With this CTP, customers and partners will be able to test the business
intelligence components included in SQL Server 2005. To increase customers'
and partners' abilities to utilize business insight capabilities, Flessner
also announced that Microsoft will extend SQL Server 2005 Reporting Services
from Standard and Enterprise Editions to all versions of SQL Server 2005,
including Express and Workgroup Editions. In addition, SQL Server 2005
Report Builder will be available with Workgroup, Standard and Enterprise
Editions."
-- Robert
This posting is provided "AS IS" with no warranties, and confers no rights.
"Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
news:uR2C6oPcFHA.2124@.TK2MSFTNGP14.phx.gbl...
> Well, how about that. The info I had was not that old but looks like prior
> to TechEd they changed their mind.
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "chicagoclone" <chicagoclone@.discussions.microsoft.com> wrote in message
> news:DF676812-82CA-4228-8EFA-56847C1282B7@.microsoft.com...
>> that is what I thought also but what about this link here. It has a
>> checkmark for standard...
>> http://www.microsoft.com/sql/2005/productinfo/sql2005features.mspx
>> More research found this information as well.
>> "This week, at Microsoft TechEd in Orlando, Florida, Microsoft turned a
>> complete 180 in the way the company will license SQL Server Reporting
>> Services and Report Builder. Microsoft was planning to include Report
>> Builder
>> in SQL Server 2005 Enterprise Edition but not Standard Edition or other
>> less
>> expensive SQL Server SKUs. I thought that was going to be a big mistake
>> for
>> Microsoft, and many people in the SQL Server community agreed with me.
>> But
>> this week, Microsoft Senior Vice President of Server Applications Paul
>> Flessner announced that Reporting Services will be included in all
>> editions
>> of SQL Server 2005. In addition, the Workgroup and Standard Editions of
>> SQL
>> Server 2005 will include Report Builder."
>> taken from this artice:
>> http://www.windowsitpro.com/SQLServer/Article/ArticleID/46694/46694.html
>> "Bruce L-C [MVP]" wrote:
>> Just Enterprise.
>> Not sure about development version. Previously that version was
>> identical to
>> enterprise.
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>> "chicagoclone" <chicagoclone@.discussions.microsoft.com> wrote in message
>> news:FAD2F770-CFA6-4F70-AD0C-662C2A99E7CD@.microsoft.com...
>> > My question:
>> > Does the end-user reporting tool (report builder) in Sql Server 2005
>> > exist
>> > in the Standard Version or is it only in the Enterprise Version?
>> >
>> > I have found a couple of conflicting articles on the web.
>> >
>> > Thanks in advance.
>>
>|||Robert,
Thank you for the clarification.
"Robert Bruckner [MSFT]" wrote:
> From the official press release at TechEd 2005:
> http://www.microsoft.com/presspass/press/2005/jun05/TechEd2005Day2PR.mspx
> "With this CTP, customers and partners will be able to test the business
> intelligence components included in SQL Server 2005. To increase customers'
> and partners' abilities to utilize business insight capabilities, Flessner
> also announced that Microsoft will extend SQL Server 2005 Reporting Services
> from Standard and Enterprise Editions to all versions of SQL Server 2005,
> including Express and Workgroup Editions. In addition, SQL Server 2005
> Report Builder will be available with Workgroup, Standard and Enterprise
> Editions."
>
> -- Robert
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
> news:uR2C6oPcFHA.2124@.TK2MSFTNGP14.phx.gbl...
> > Well, how about that. The info I had was not that old but looks like prior
> > to TechEd they changed their mind.
> >
> > --
> > Bruce Loehle-Conger
> > MVP SQL Server Reporting Services
> >
> > "chicagoclone" <chicagoclone@.discussions.microsoft.com> wrote in message
> > news:DF676812-82CA-4228-8EFA-56847C1282B7@.microsoft.com...
> >> that is what I thought also but what about this link here. It has a
> >> checkmark for standard...
> >>
> >> http://www.microsoft.com/sql/2005/productinfo/sql2005features.mspx
> >>
> >> More research found this information as well.
> >>
> >> "This week, at Microsoft TechEd in Orlando, Florida, Microsoft turned a
> >> complete 180 in the way the company will license SQL Server Reporting
> >> Services and Report Builder. Microsoft was planning to include Report
> >> Builder
> >> in SQL Server 2005 Enterprise Edition but not Standard Edition or other
> >> less
> >> expensive SQL Server SKUs. I thought that was going to be a big mistake
> >> for
> >> Microsoft, and many people in the SQL Server community agreed with me.
> >> But
> >> this week, Microsoft Senior Vice President of Server Applications Paul
> >> Flessner announced that Reporting Services will be included in all
> >> editions
> >> of SQL Server 2005. In addition, the Workgroup and Standard Editions of
> >> SQL
> >> Server 2005 will include Report Builder."
> >>
> >> taken from this artice:
> >> http://www.windowsitpro.com/SQLServer/Article/ArticleID/46694/46694.html
> >>
> >> "Bruce L-C [MVP]" wrote:
> >>
> >> Just Enterprise.
> >>
> >> Not sure about development version. Previously that version was
> >> identical to
> >> enterprise.
> >>
> >> --
> >> Bruce Loehle-Conger
> >> MVP SQL Server Reporting Services
> >>
> >> "chicagoclone" <chicagoclone@.discussions.microsoft.com> wrote in message
> >> news:FAD2F770-CFA6-4F70-AD0C-662C2A99E7CD@.microsoft.com...
> >> > My question:
> >> > Does the end-user reporting tool (report builder) in Sql Server 2005
> >> > exist
> >> > in the Standard Version or is it only in the Enterprise Version?
> >> >
> >> > I have found a couple of conflicting articles on the web.
> >> >
> >> > Thanks in advance.
> >>
> >>
> >>
> >
> >
>
>sql

Report Builder localized in spanish

I work with an English SQL Server 2005 license , but would like that the Report Builder tool presents itself in spanish in the client computers .

I can localize the Report Manager to spanish without problems (configuring the spanish language in IE) , but the Report Builder still presents its interface in english .

How can this be achieved ? With Regards ,

George

You must have a Spanish version of the operating system, or a multi-language pack that allows you to change the operating system UI to Spanish. IE language settings do not affect Report Builder.

Report Builder - Add a report date

any way using report builder ad hoc tool for users to add an "as of" date to
a report using the TODAY function?
Rich BelangerI figured it out, you just need to type an expression into a text box in
design view.
"Rich Belanger" <rich.belanger@.verizon.net> wrote in message
news:udq0ZW9vHHA.3508@.TK2MSFTNGP03.phx.gbl...
> any way using report builder ad hoc tool for users to add an "as of" date
> to a report using the TODAY function?
> Rich Belanger
>