Showing posts with label url. Show all posts
Showing posts with label url. Show all posts

Monday, March 12, 2012

Issue with URL Encoding report's hyperlink value.

Hello,

I've created a hyperlink in a report. The hyperlink action is 'Jump to URL' The URL is http://ServerName/SomePage.aspx?AccountCode=####&InvoiceLevel=1

The hyperlink works just fine in the designer, it's value becomes http://ServerName/SomePage.aspx?AccountCode=%23%%23%%23%%23&InvoiceLevel=1, however when I run from the web the report's URL is not properly URL encoded. It's value is http://ServerName/SomePage.aspx?AccountCode=#%23%23%23&InvoiceLevel=1 which is incorrect since the browser now treats the # as a hash.
I've tried explicitly URL Encoding the #### in the function but the report returns an error. "http://ServerName/SomePage.aspx?AccountCode=" + System.Web.HttpUtility.UrlEncode(####) + "&InvoiceLevel=1"

I've tried it in RS2000 & RS2005, same results.

Help..Idea
Robert.

Hi Robert,

It looks like the first pound sign (number sign, hash, tic-tac-toe, octothrope... call it what you will) is being interpreted as a URL anchor symbol.

Is the "access" param always literally "####"? If so it should work if you URLEncode yourself by typing "%23%23%23%23".

If the access param is dynamic and may or may not begin with a #, you could use the Replace function in an expression to encode any #'s.

-Chris|||

Thanks for your reply,

The AccountCode parameter value is dynamic and for the most part as meaningful data, however the data originates from the mainframe so there are values that start with #. I could encode it using the replace however the Accountcode could contain all possible characters. Any other suggestions.

Robert.

|||

Try using the UrlEncode function on the argument value, e.g.:

=Globals!ReportServerUrl+ "?" & Globals!ReportFolder & "/Report&Parameter=" &
System.Web.HttpUtility.UrlEncode(Fields!AccountID.Value)

See also MSDN:
http://msdn2.microsoft.com/en-us/library/system.web.httputility.urlencode.aspx

-- Robert

|||

I tried using System.Web.HttpUtility.UrlEncode. Look at my first post. It works in the designer but not in Report Manager. It's very easy to recreate. Here are the steps:

Add a new blank report to a project.

Drop on a text box and set the expression to System.Web.HttpUtility.UrlEncode("####")

click report properties, click the reference tag and add System.web.

Preview the report in the designer. It works just fine.

Deploy the report and then view it in Report Manager. It displays #errror. I suspected the Report Server is not able to find System.web.dll

Robert.

|||

Did you ever resolve this problem, as I've just hit it!

Issue with URL Encoding report's hyperlink value.

Hello,

I've created a hyperlink in a report. The hyperlink action is 'Jump to URL' The URL is http://ServerName/SomePage.aspx?AccountCode=####&InvoiceLevel=1

The hyperlink works just fine in the designer, it's value becomes http://ServerName/SomePage.aspx?AccountCode=%23%%23%%23%%23&InvoiceLevel=1, however when I run from the web the report's URL is not properly URL encoded. It's value is http://ServerName/SomePage.aspx?AccountCode=#%23%23%23&InvoiceLevel=1 which is incorrect since the browser now treats the # as a hash.
I've tried explicitly URL Encoding the #### in the function but the report returns an error. "http://ServerName/SomePage.aspx?AccountCode=" + System.Web.HttpUtility.UrlEncode(####) + "&InvoiceLevel=1"

I've tried it in RS2000 & RS2005, same results.

Help..Idea
Robert.

Hi Robert,

It looks like the first pound sign (number sign, hash, tic-tac-toe, octothrope... call it what you will) is being interpreted as a URL anchor symbol.

Is the "access" param always literally "####"? If so it should work if you URLEncode yourself by typing "%23%23%23%23".

If the access param is dynamic and may or may not begin with a #, you could use the Replace function in an expression to encode any #'s.

-Chris|||

Thanks for your reply,

The AccountCode parameter value is dynamic and for the most part as meaningful data, however the data originates from the mainframe so there are values that start with #. I could encode it using the replace however the Accountcode could contain all possible characters. Any other suggestions.

Robert.

|||

Try using the UrlEncode function on the argument value, e.g.:

=Globals!ReportServerUrl+ "?" & Globals!ReportFolder & "/Report&Parameter=" &
System.Web.HttpUtility.UrlEncode(Fields!AccountID.Value)

See also MSDN:
http://msdn2.microsoft.com/en-us/library/system.web.httputility.urlencode.aspx

-- Robert

|||

I tried using System.Web.HttpUtility.UrlEncode. Look at my first post. It works in the designer but not in Report Manager. It's very easy to recreate. Here are the steps:

Add a new blank report to a project.

Drop on a text box and set the expression to System.Web.HttpUtility.UrlEncode("####")

click report properties, click the reference tag and add System.web.

Preview the report in the designer. It works just fine.

Deploy the report and then view it in Report Manager. It displays #errror. I suspected the Report Server is not able to find System.web.dll

Robert.

|||

Did you ever resolve this problem, as I've just hit it!

Issue with subscription and List

Hello,
I have created a report that includes a table within a list. The report
always renders correctly and as expected when accessed through a url. The
report never renders or gets emailed if rendered through a subscription. In
the log file I noticed the following error "The processing of group
expression for the list 'list1' cannot be performed. The comparison failed.
Please check the data type returned by group expression." If I remove the
List control, the report gets rendered correctly and emailed.
Can anyone shed some light on this problem?If you can create a sample report with this behavior based on either pubs or
northwind, we can take a look at it. You can send it to me (remove online
from my address)
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
"JohnG" <JohnG@.discussions.microsoft.com> wrote in message
news:A209CD95-6710-4F72-B606-19ADA9CABE4B@.microsoft.com...
> Hello,
> I have created a report that includes a table within a list. The report
> always renders correctly and as expected when accessed through a url. The
> report never renders or gets emailed if rendered through a subscription.
> In
> the log file I noticed the following error "The processing of group
> expression for the list 'list1' cannot be performed. The comparison
> failed.
> Please check the data type returned by group expression." If I remove the
> List control, the report gets rendered correctly and emailed.
> Can anyone shed some light on this problem?

Friday, February 24, 2012

Issue to install Reporting Services

I installed SQL Server 2005 Express with Reporting Service on Windows Server 2003 Standard on a server called psmart01. I type the URL of reporting services: http://psmart01/reportserver$SQLEXPRESS and I get only:

psmart01/ReportServer$SQLExpress - /

Microsoft SQL Server Reporting Services Version 9.00.2047.00

I have gone through the Troubleshoot a Reporting Services Installation Problem of MSDN but there is not such issue.

I wonder if reporting service database is not created properly. When I restart the SQL Server Reporting Services I see in the eventvwr: Starting up database 'ReportServer$SQLExpressTempDB'. Why TempDB ?

Can someone help ?

I think you are seeing the Report Server v-dir listing, and your catalog is empty. This is expected. What do you see when you navigate to this URL:

http://psmart01/Reports$SQLExpress