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 to url

I have a question to ask:
I type
"http://reportserverurl/pages/reports.aspx?ItemPath=%2ftargetfolder%2ftestreport"
in jump to url box, it will go to open a report named testreport in my report
server. It is good. I want to rename the testreport to a variable name.
If I change testreport to Field!ReportName.Value in stead, then it does
not work, how do you make the Field!ReportName.Value to convert to
testreport. I have other reports in the report server="http://reportserverurl/pages/reports.aspx?ItemPath=%2ftargetfolder%2f" &
Feild!ReportName.Value
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Henry Chen" <HenryChen@.discussions.microsoft.com> wrote in message
news:85B76250-BB7F-4C78-96CB-2BB5B0C7804F@.microsoft.com...
>I have a question to ask:
> I type
> "http://reportserverurl/pages/reports.aspx?ItemPath=%2ftargetfolder%2ftestreport"
> in jump to url box, it will go to open a report named testreport in my
> report
> server. It is good. I want to rename the testreport to a variable name.
> If I change testreport to Field!ReportName.Value in stead, then it does
> not work, how do you make the Field!ReportName.Value to convert to
> testreport. I have other reports in the report server

Report times out on Export after 90 seconds.

I have a report that is timing out after 90 seconds of run-time - but only
when exporting to an alternate file type (PDF, XLS, etc)- if I use the HTML
Viewer format, the report is displayed properly and only takes a couple of
seconds to run. The error message that I get back says "The operation has
timed-out", and I'll include the stack trace at the end of this message.
My application is calling the ReportingService.Render method using SOAP
Reporting Services Web Service to perform the export to a PDF format. I'm
able to see the same problem when using the Report manager to export the
report to PDF format. This report definition is using a table to display the
query results (no matrices), and is printing in landscape mode. I have RS
Service Pack 2 installed on the server.
The report is running off of a fairly small data set (4000-5000 records),
with a couple of tricky joins, but I can execute the query using SQL Server
Enterprise Manager in about 2 seconds. I have tried setting the data set
'Timeout' value to 3600 (1 hr) and 2147483647 (documentation named maximum
value) in the Report Designer for the .rdl itself (timeout element under
query element in rdl). I've tried setting "Connect Timeout=3600" in the
connection string for my Data Set defined on the Report Server. I have also
set the Report Server to not timeout report execution both in Site Settings
and the individual settings for the submitted report definition. What
timeout am I missing?
If I trim down my data set to under 1000 records, the Render call completes
before the timeout can occur, and I get my PDF. I've spent some time trying
to figure out what's going on, and am at a loss. Here's what I see happening
over time:
0:00 - Submit report - Render() call is made
0:05 - CPU Utilization on server jumps to 100%, I can see report job in
Report Manager
1:30 - I get error message back from Render() call saying "The operation has
timed-out."
2:35 - CPU utilization on server slows back down to normal, job is no longer
visible in Report Manager
Any help or suggestions greatly appreciated!With this same report, trying different export formats - this is what I've
found:
PDF - times out after 90 seconds
XLS - times out after 90 seconds.
TIF - times out after 90 seconds.
CSV - results show up after ~ 10 seconds.
HTML - results show up after ~ 10 seconds.
XML - results show up after ~ 10 seconds.
So it looks like anything that doesn't end up in a plain text export is
timing out on me. And here's that stack trace I promised earlier:
The operation has timed-out.
at System.Web.Services.Protocols.WebClientProtocol.GetWebResponse(WebRequest
request) at
System.Web.Services.Protocols.HttpWebClientProtocol.GetWebResponse(WebRequest
request) at
System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String
methodName, Object[] parameters) at UT.RSRef.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) in C:\Documents and Settings\Ben\My
Documents\Visual Studio Projects\REPOUTIL\Web
References\RSRef\Reference.cs:line 653 at UT.repoutil.Page_Load(Object
sender, EventArgs e) in c:\documents and settings\ben\my documents\visual
studio projects\repoutil\repoutil.cs:line 5209|||Ben,
Can you render other reports without timeouts? If they all time out, I
would say its somthing wrong with the export feature...
If its just this one report it might just be taking a long time to render if
the report is large, I believe you can change the timeout values in one of
the rsserver config files to allow you more time to either get your export,
or generate some other type of error that your not seeing now because of the
timeout.
Hope this helps in some way.
"Ben Shaffer" wrote:
> With this same report, trying different export formats - this is what I've
> found:
> PDF - times out after 90 seconds
> XLS - times out after 90 seconds.
> TIF - times out after 90 seconds.
> CSV - results show up after ~ 10 seconds.
> HTML - results show up after ~ 10 seconds.
> XML - results show up after ~ 10 seconds.
> So it looks like anything that doesn't end up in a plain text export is
> timing out on me. And here's that stack trace I promised earlier:
> The operation has timed-out.
> at System.Web.Services.Protocols.WebClientProtocol.GetWebResponse(WebRequest
> request) at
> System.Web.Services.Protocols.HttpWebClientProtocol.GetWebResponse(WebRequest
> request) at
> System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String
> methodName, Object[] parameters) at UT.RSRef.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) in C:\Documents and Settings\Ben\My
> Documents\Visual Studio Projects\REPOUTIL\Web
> References\RSRef\Reference.cs:line 653 at UT.repoutil.Page_Load(Object
> sender, EventArgs e) in c:\documents and settings\ben\my documents\visual
> studio projects\repoutil\repoutil.cs:line 5209
>|||Thanks Jason,
It's only one report that is giving me this headache. I have dozens more
that export before the timeout.
Can you point me towards any documentation on what the reportserver config
files are and what the settings do? I've found various *.config files in the
report server directories on the server, but haven't seen any keys that jump
out at me as being the right one for the timeout that's giving me grief.
"Jason Brinkley" wrote:
> Ben,
> Can you render other reports without timeouts? If they all time out, I
> would say its somthing wrong with the export feature...
> If its just this one report it might just be taking a long time to render if
> the report is large, I believe you can change the timeout values in one of
> the rsserver config files to allow you more time to either get your export,
> or generate some other type of error that your not seeing now because of the
> timeout.
> Hope this helps in some way.

Report Service 2005 parameter at Date

I set Report Parameters ,

Properties

Name : StartDate

Data Type : DateTime

Prompt : StartDate

Default values = Format(Today(),"yyyy/MM/dd")

But have error (An error occurred during local report rpocessing. The properly "DefaultValue" of report parameter 'EndDate' doesn't have the expected type.)

The Result show : like "2007/05/01"

Thanks help

Moving to SQL Server Reporting Services forum. This is not an SSIS issue.|||

Hi,

I think the Format function converts your value into String datatype & that is why you're getting the error.

Just use CDate of your expression, that is:

CDate(Format(Today(),"yyyy/MM/dd")

That should get rid of the error.

-Aayush.

|||

=CDate(Format(Today(),"yyyy/MM/dd")

had error

[rsCompilerErrorInExpression] The Value expression for the report parameter ‘endDate’ contains an error: [BC30198] ')' expected.

Thanks help

|||

Oops.. I missed out a bracket Sorry for that.

Try =CDate(Format(Today(),"yyyy/MM/dd"))

-Aayush

|||Thanks You very much|||

Thanks all

The command is right, but I look in client pc, i see the date is "06/11/2007"

The =Cdate(format(today(),"yyyy/MM/dd")) could not work.

|||You're right I overlooked the fact that CDate converts it back to the default date format. So this fix does not work. Actually the expression =Format(Today(),"yyyy/MM/dd") would work but it would require you to change the Data Type of the parameter from 'DateTime' to 'String'. So I don't think it is very feasible.|||

Thanks

But not work