Error with report being generated from another system
in [Reports]
|
From: SQL Guy on 30 Sep 2009 11:30 We have this system at work called LABWARE LIMS. They have some subroutines programmed that take a value and pass it to a hyperlink which is a RS report. Here is a copy of the hyperlink: http://<ServerName>/ReportServer/Pages/ReportViewer.aspx?%2fAnalytical+Services%2fSample+Submission&rs:Command=Render&sample= <The variable is placed here> This has been working great, however some people with IE 7 are getting the following error: "The path of the item '/Analytical Services/Sample Submission,rs' is not valid. The full path must be less than 260 characters long; other restrictions apply. If the report server is in native mode, the path must start with slash. (rsInvalidItemPath)" Those with IE 6 are not getting this error. We tried to replicate the steps the users are going through to get the report and we noticed in the address bar the following link is passed in: http://<ServerName>/ReportServer/Pages/ReportViewer.aspx?%2fAnalytical+Services%2fSample+Submission&rs It seems like part of the hyperlink is being cut off, but not when going through IE 6! The users just click on a button in their LIMS LABWARE application and it should take the variable they entered and place it at the end of the hyper link. Because the issue is specific to this system calling our reports, it is hard to find a solution online. Any help would be appreciated. Downgrading hundreds of PCs to IE 6 is not an option at this point. Help!
From: Phil Meeks on 30 Sep 2009 12:46 Here is a MSKB article explaining a URL encoding change in IE7: http://support.microsoft.com/kb/934279 Looks like the problem is the colon. I don't think you are close to the 2083 character URL limit. Since there is no workaround given, you may want to try and alter the URL at the report server to eliminate the offending colon. You indicated there are some subroutines generating this link, so you can attack that angle. Can you wrap the generated link with a Server.URLEncode() ? That would fix the problem. Probably easier to modify the program than to downgrade everyone to IE6. Good luck! Phil "SQL Guy" <aymantg(a)gmail.com> wrote in message news:5bb7d7f5-52c9-4ab3-a65c-6cdc8b4c5735(a)a21g2000yqc.googlegroups.com... > We have this system at work called LABWARE LIMS. They have some > subroutines programmed that take a value and pass it to a hyperlink > which is a RS report.
From: Person2 on 30 Sep 2009 14:42 A colleague of mine got it to work in IE 7, so my theory is faulty.
From: SQL Guy on 30 Sep 2009 14:43 On Sep 30, 2:42 pm, Person2 <ayma...(a)gmail.com> wrote: > A colleague of mine got it to work in IE 7, so my theory is faulty. SQL GUY is Person2... not sure why it changed my name.
From: SQL Guy on 30 Sep 2009 14:45
On Sep 30, 12:46 pm, "Phil Meeks" <phil...(a)pm6.com> wrote: > Here is a MSKB article explaining a URL encoding change in IE7:http://support.microsoft.com/kb/934279 > > Looks like the problem is the colon. I don't think you are close to the 2083 > character URL limit. > > Since there is no workaround given, you may want to try and alter the URL at > the report server to eliminate the offending colon. You indicated there are > some subroutines generating this link, so you can attack that angle. > > Can you wrap the generated link with a Server.URLEncode() ? That would fix > the problem. > > Probably easier to modify the program than to downgrade everyone to IE6. > > Good luck! > > Phil > > "SQL Guy" <ayma...(a)gmail.com> wrote in message > > news:5bb7d7f5-52c9-4ab3-a65c-6cdc8b4c5735(a)a21g2000yqc.googlegroups.com... > > > We have this system at work called LABWARE LIMS. They have some > > subroutines programmed that take a value and pass it to a hyperlink > > which is a RS report. A colleague of mine got it to work in IE 7, so my theory is faulty. |