Report Error, Help!

Hi
I have beening trying to build a report with 2 parameters. When I run it
under VS.net, it all went well, but after I deploy it to the server, I got
the message as following: Reporting Services Error--The path of the item ''
is not valid. The full path must be less than 260 characters long, must start
with slash; other restrictions apply. Check the documentation for complete
set of restrictions. (rsInvalidItemPath) Get Online Help
what went wrong, please help. TIAYou sure have to post your URL to help you.
Jens Suessmeyer.
"wd1153" <wd1153@.discussions.microsoft.com> schrieb im Newsbeitrag
news:5138A906-7AA9-4D7A-A1B5-E3C9756BE7E1@.microsoft.com...
> Hi
> I have beening trying to build a report with 2 parameters. When I run it
> under VS.net, it all went well, but after I deploy it to the server, I got
> the message as following: Reporting Services Error--The path of the item
> ''
> is not valid. The full path must be less than 260 characters long, must
> start
> with slash; other restrictions apply. Check the documentation for complete
> set of restrictions. (rsInvalidItemPath) Get Online Help
> what went wrong, please help. TIA
>
>|||Sorry, the URL as following:
http://localhost/reportserver?%2fRev_Stats%2fRev_Stats&rs:Command=Render
"Jens Sü�meyer" wrote:
> You sure have to post your URL to help you.
> Jens Suessmeyer.
>
> "wd1153" <wd1153@.discussions.microsoft.com> schrieb im Newsbeitrag
> news:5138A906-7AA9-4D7A-A1B5-E3C9756BE7E1@.microsoft.com...
> > Hi
> >
> > I have beening trying to build a report with 2 parameters. When I run it
> > under VS.net, it all went well, but after I deploy it to the server, I got
> > the message as following: Reporting Services Error--The path of the item
> > ''
> > is not valid. The full path must be less than 260 characters long, must
> > start
> > with slash; other restrictions apply. Check the documentation for complete
> > set of restrictions. (rsInvalidItemPath) Get Online Help
> > what went wrong, please help. TIA
> >
> >
> >
>
>

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 error

Hi all,

I just setup SQL 2005 Report Service, and then I used the browser to view the "folder.aspx"

Nothing showed up but I received an error page with the message like the following:

"The request failed with HTTP status 400: Bad Request."

So, what did I do wrong?

Thanks,

Frank

System Engineer

Start debugging with your http://localhost/reportserver. How were the RS virtual directories created? Try creating them using the configuration tools, and re-apply the script mappings.|||If the suggestions from James is not working, try to dive deeper into the error of the reporting services engine, by setting the logging mode to verbose and see where the error is based on. If you have a blank report server with not much reports one, try to reinstall the whole thing, that is sometimes better than (try) fixing the issues that popup. I had that a while ago, the cause was that there were file locks on the files that needed to be changed. The installer didn′t pop up a message and *bump* there were many erros coming up regarding authentication etc.

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de

Report erroe

Hi All ,

i got tired from the component crytsal reports but i need it to finish an application i'm building .

i got the folloiwng error when i try to run the report.

ONE : Cannot implicitly convert type 'CrystalDecisions.Shared.TableLogOnInfos' to 'CrystalDecisions.Shared.TableLogOnInfo'

TWO: foreach statement cannot operate on variables of type 'CrystalDecisions.Shared.TableLogOnInfo' because 'CrystalDecisions.Shared.TableLogOnInfo' does not contain a public definition for 'GetEnumerator'

and here is the code that i'm using:

using CrystalDecisions.CrystalReports.Engine;
using CrystalDecisions.Shared;

namespace Hope
{
public partial class Form1 : Form
{
public Form1()
{
InitializeComponent();
}
private void ConfigureCrystalReports()
{

ConnectionInfo connectionInfo = new ConnectionInfo();
connectionInfo.DatabaseName = "NorthWind";
connectionInfo.UserID = "";
connectionInfo.Password = "";

string reportPath = Application.StartupPath + "\\" +
"NorthwindCustomers.rpt";
crystalReportViewer.ReportSource = reportPath;



SetDBLogonForReport(connectionInfo);

}

private void Form1_Load(object sender, EventArgs e)
{
ConfigureCrystalReports();

}

private void SetDBLogonForReport(ConnectionInfo connectionInfo)
{
TableLogOnInfo tableLogOnInfos = crystalReportViewer.LogOnInfo;

foreach (TableLogOnInfo tableLogOnInfo in tableLogOnInfos)
{
tableLogOnInfo.ConnectionInfo = connectionInfo;
}


please try to help me find out , what's the problem , i'll get mad soon,hi
this is saurabh

i have creating a crystal report. in this report i want inserting no. of images .
can i put these images directly into the folders.
without saving in database.

plz... give reply as soon as possible....!|||Are you jokking ,

why to post here in my thread , create your own.

i'm so amazed from your action ,

Report equivalent of a <BR> or a vbCrLf

What do I have to embed in my data to get a report cell to line break?

If I have:
ABC?XYZ

what do I have to store in the ? position to get it to look like:
ABC
XYZ

in my report?

Try with \n or \r or \n\r.
But I don't understand how you convert ? to this characters. Are you evaluating an expression or this is data from a dataset?
If you are evaluating an expression put "first string"+CHAR(13)+"last string"
Can you be more specific?|||

The data is from a Dataset. What I'm trying to figure out is what can I put in the data to make a Report perform a line break? Whatever I put in there is just take as part of the data. I've tried putting:ABC\n\rXYZ and that's exactly what shows up in the cell on the report.

|||If you are using T-SQL and you are making the dataset from a query try this:
SELECT field1+CHAR(13)+field2
or
SELECT field1+CHAR(10)+CHAR(13)+field2
tell me if it works!!!|||Yeah close enough. I embeded char(13) & char(10) when I save the data and it displayed fine in the report.

Thanks
Steve|||I think you can also split the column in an expression and use vbcrlf. e.g string1 & vbcrlf & string2|||It's faster solving that in the dataset than in the report side.
But it's valid too and it's good to know as many ways to solve problem as you can.sql

Report Engine

Does Report Services 2005 have a Report Distribution engine. So that I
can for instance say; I want user 'A' to get report 'B' in a format of
'C' at 17:05 every day.
Many thanks
DavidYes, it is called Subscriptions. You can specify all of that. It is
available both Standard and Enterprise. However, Enterprise adds data driven
subscriptions.
Here is from books online about data driven subscriptions:
>>>
A data-driven subscription provides a way to deliver reports to a list of
subscribers that is determined at run time. You can use data-driven
subscriptions as follows:
a.. Customize report output at run time for each recipient of a delivery.
b.. Support the wide distribution of a report with a fluctuating list of
subscribers. For example, you can use data-driven subscriptions to
distribute a report throughout a large organization where subscribers vary
from one month to the next, or use other criteria that determines group
membership from an existing set of users.
A data-driven subscription differs from a standard subscription in the way
it gets subscription information. A data-driven subscription gets some
settings from a data source at run time, and other settings from the
subscription definition. Fixed aspects of a data-driven subscription include
the report that is delivered, the delivery extension, connection information
to an external data source that contains subscriber data, and a query that
retrieves subscription information. Dynamic settings of the subscription are
obtained from the query, including a subscriber list and user-specific
delivery extension preferences or parameter values. This data is retrieved
from a data source each time the subscription is processed.
>>>>>
Bruce Loehle-Conger
MVP SQL Server Reporting Services
<davidswain2005@.yahoo.co.uk> wrote in message
news:1141318397.513927.57680@.i39g2000cwa.googlegroups.com...
> Does Report Services 2005 have a Report Distribution engine. So that I
> can for instance say; I want user 'A' to get report 'B' in a format of
> 'C' at 17:05 every day.
>
> Many thanks
> David
>|||Yes, it's called creating a subscription
"davidswain2005@.yahoo.co.uk" wrote:
> Does Report Services 2005 have a Report Distribution engine. So that I
> can for instance say; I want user 'A' to get report 'B' in a format of
> 'C' at 17:05 every day.
>
> Many thanks
> David
>

Report empty?

I have created a basic report that just shows some columns from a query, I'm using a dataadapter and the reportviewer component.

If I execute the query it calles it returns some rows, but the report is empty.

What's wrong with the reportviewer and the report objects?

I'm thinking about just using gridviews because the reports don't work, altough I'd like to use the reportviewer because it can export to excel/pdf.

Thanks.

HI,onishirox:

I can not debug it without any codes from your scenario, but you can have a check with this following walkround to make your codes work:

Binding Data to the ReportViewer Control Dynamically in ASP.NET 2.0 -

http://www.aspfree.com/c/a/ASP.NET/Binding-Data-to-the-ReportViewer-Control-Dynamically-in-ASPNET-20/1/

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

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

of assistance

|||

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

|||

Thanks. I think the problem was that I was using sqlserver2000, seems to work ok now with sql2005.