Home Dashboard Directory Help
Search

Error running report through port forwading by M. R. - Canada


Status: 

Closed


1
0
Sign in
to vote
Type: Bug
ID: 766754
Opened: 10/9/2012 10:26:46 AM
Access Restriction: Public
0
Workaround(s)
view
0
User(s) can reproduce this bug

Description

Using SQL Server Reporting Services 2012, installed on a virtual machine (VMware) and Visual Studio 2012 to create a server report (.rdl)

On this virtual machine I created a very basic rdl report that pulls data from a database and opens a second report when clicking a database item (using the item as a parameter passed to the second report). Works perfectly on the VM.

To give access to other users I use port forwarding technique in order to run this report in Internet Explorer. Everything works fine except...when user clicks on an item to see the second report, Internet Explorer will ask again and again for an user name and password but it will not accept any credentials (including the credentials used to run the main report). Why is this happening? Main report works fine, second one not... Permissions are exactly the same for both reports, I checked.

On the VM, I looked to see what URL is opened when clicking on a database item on main report. It looks like this:

http://localhost/Reports/Pages/Report.aspx?ItemPath=%2fRBS+Reports%2fReport2&ExecId=hxyt2zaiziwlrf55qkvjckbw&PingId=1yzljiq4zleimavdqaaunz45

ExecId will be something different for each database item.

I think this is a bug in Reporting Services.

Thank you,
M.R.
Details
Sign in to post a comment.
Posted by Microsoft on 10/23/2013 at 4:15 PM
Hello,
Thank you for submitting this feedback. After carefully evaluating all of the bugs in our pipeline, we are closing bugs that we will not fix in the current or future versions of SQL Server. The reasons for closing these bugs are following:
1.     The fix is risky to implement in the current version of the product (service packs)
2.     Scenarios reported in the bug are not common enough
3.     A viable workaround is available
Thanks again for reporting the product issue and continued support in improving our product.
Sign in to post a workaround.