Problems with excel links after applying SP 1

Hi,
I've just applied the SP 1 for Reporting Services. When I export
reports to Excel having actions linked to other reports, I've tried
the sample report -Employee summary report-, the links stopped
working. They just say Unable to open http://(myhostname)/. .. .
Cannot download the information you requested.
Has anyone succeded doing this with the new SP 1?
Is it safe to apply the new SP?
/J HasselJ Hasselgren wrote:
> Hi,
> I've just applied the SP 1 for Reporting Services. When I export
> reports to Excel having actions linked to other reports, I've tried
> the sample report -Employee summary report-, the links stopped
> working. They just say Unable to open http://(myhostname)/. .. .
> Cannot download the information you requested.
> Has anyone succeded doing this with the new SP 1?
> Is it safe to apply the new SP?
> /J Hassel
Yes this works for me. Have a look whether some URL encoding for special
characters does prevent the link from working. I had similar problems with
linking to report names containing german umlaute (I had to rename my
reports, puuuhh, good old eighties plain ASCII feeling :))
roland|||Yes, we are investigating an issue with encoded report names in links. We
are looking at options to resolve this.
--
Brian Welcker
Group Program Manager
SQL Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"Roland" <nomail@.spamprotect.com> wrote in message
news:eegnYEWXEHA.1152@.TK2MSFTNGP09.phx.gbl...
>J Hasselgren wrote:
>> Hi,
>> I've just applied the SP 1 for Reporting Services. When I export
>> reports to Excel having actions linked to other reports, I've tried
>> the sample report -Employee summary report-, the links stopped
>> working. They just say Unable to open http://(myhostname)/. .. .
>> Cannot download the information you requested.
>> Has anyone succeded doing this with the new SP 1?
>> Is it safe to apply the new SP?
>> /J Hassel
> Yes this works for me. Have a look whether some URL encoding for special
> characters does prevent the link from working. I had similar problems with
> linking to report names containing german umlaute (I had to rename my
> reports, puuuhh, good old eighties plain ASCII feeling :))
> roland
>