@Prashanth B

I can’t guarantee that I can help you as everyone’s environment is different but I can give it a shot.

I have a few questions for you:

1. How did you set everything up? Did you pull my code and set it up manually or did you use the NuGet installer?
2. Are you running on standard MVC or on .NetCore?
3. Have you adjusted your default credentials in the ReportController? (property is named “NetworkCredentials”)

Thanks,

Alan

@Mark

Any chance you could let me know if you’re in .NetCore or standard MVC? Also, if you could give me a sample or copy of your controller that would be awesome!

Alan

@jan

The client side makes no direct post requests to the SSRS server only to your controller action (the client side of the application makes a request to the web server, then the web server makes the request to the SSRS web service). The client does not need direct access to the SSRS web service.

Alan

Hey @Stephan, I haven’t yet packaged up a NuGet package of the .NetCore version. Your issue is that you’ve pulled in the standard .net version into your .NetCore project. If you pull the code (or download) from github you can compile the AlanJuden.MvcReportViewer.NetCore project you can grab the dll from there.

Hope this helps!

Alan

I’m glad that worked for you @Stephan, thanks for the feedback!

@deco, I don’t see any reason you wouldn’t be able to use the .NetCore version of my report viewer in your project. I just created a sample project based off of your spec and was able to compile (I don’t have access to my report server at the moment to test that portion but it appeared to act as normal when accessing the ReportController).

@hussein, thanks for letting me know about this issue. This sounds like it’s most likely caused due to the encoding type I’m using in my code. I’ve selected Encoding.ASCII as the encoding when reading the data back from the report server. If you download the code from Github and modify the encoding to UTF8 (or some other encoding that would support your characters) then you can rebuild the dll and you should be all good.

Alan

@Yow, have you tried searching your error on google?

It sounds like it’s just an authentication issue so I’m assuming the credentials you’re using on the ReportController are not valid in the context of your local SSRS instance. Double check the ReportController property for NetworkCredentials are valid credentials on your SSRS instance.

Alan

@Ryan, did you attempt the fix suggested in the comments above? Someone else with the same issue made a change to their report server config file and restarted the SSRS service and it was all good. Let me know what happens from that.

Alan

@Deyan,

What are you trying to do with the ReportService2010.asmx endpoint? This page explains the use of each of the endpoints: https://msdn.microsoft.com/en-us/library/ms155398.aspx

I chose the ReportService2005.asmx endpoint because I figured it would be on the most report servers so it would work for the most people.

Standard .NET Project Instructions for changing the web service path:
1. Go to the AlanJuden.MvcReportViewer project.
2. Navigate in the solution explorer to “Web References” in the root of the project.
3. Expand the “Web References” folder.
4. Click on each reference and change the “Web Referenc URL” (located in the properties window). Changing the path will force the file to be regenerated.

.NETCore Instructions for changing the web service path:
1. Install this plugin to your Visual Studio: https://marketplace.visualstudio.com/items?itemName=erikcai-MSFT.VisualStudioWCFConnectedService
2. Go to the AlanJuden.MvcReportViewer.NetCore project.
3. Right click the project and choose “Add” –> “Connected Service” and then choose the “WCF Service – Preview” option.
4. Follow the instructions of the wizard.

Hope this helps.

Alan

@Ken, I believe that currently the Drilldown reports are not supported. I have created an enhancement issue on github to see if I can’t make it happen though. https://github.com/alanjuden/MvcReportViewer/issues/27

Alan

@napoleon, my project does not support local mode reports. It relies on having the report living in SSRS and communicating with the SSRS web service api.

@Paul, you should be able to “hide” the parameters from within the report designer that you used to design the report. My control will include them as hidden form fields if you do that.

@Bojan, thanks for letting me know that everything is going well with the library. I believe that since you’ve turned your local report into an .rdl and put it on a server it’s no longer a local report any more. My library relies on having the server component there to use for requests.

I haven’t had any chances to test out my library on Ubuntu yet and it’s a fun idea to try. From what it looks like, the logic that I’m using to communicate from .NetCore to the SSRS web services has issues (most likely not fully implemented on Ubuntu with .NetCore).

Alan

@HS, seeing as how all of your links are local, would you mind sharing the link that you go to for your report on SSRS as well as the Report controller action method for calling into your report? That would help me to determine if maybe you’re using an incorrect path or something for your report.

@Dave, I’m not sure that mobile reports would be supported by this or not. It seems that when we call into the SSRS web service it’s indicating to you that it’s not the correct type of report to be returned (rwWrongItemType).

I have created a new ticket on Github to track this: https://github.com/alanjuden/MvcReportViewer/issues/32

Alan

@Pooja, I haven’t specifically added any logic to deal with the collapsible / expandable group sections on the reports. I’m not really sure it will be possible as I had looked into similar options around user sorting which is not supported through the API at all. I’ve added a Github issue to track progress on that question.

https://github.com/alanjuden/MvcReportViewer/issues/33

Alan

@Pooja, are you by chance using the ReportController property for UseCustomReportImagePath?

I ran into this issue on my own server and here’s what’s really happening. The images were not accessible through the normal SSRS url that was passed back in the content of the report through the API. I had to enable the “UseCustomReportImagePath” property so that your website kind of behaves as a proxy to serve up the image from the report server. You should really only have to set that property to true and should see it working. The reason that you’re seeing the images in the export is because the images are embedded in the content that comes back rather than being links to the report server itself as they are when you view the report on the website (or if you export to HTML you would see the same issue).

Hope this helps!

Alan

@Pok,

I’m assuming that you’re using the .NetCore version. On your controller, you can override the “ClientCredentialType” property and specify it to be Ntlm like this:

protected override System.ServiceModel.HttpClientCredentialType ClientCredentialType
{
get
{
return System.ServiceModel.HttpClientCredentialType.Ntlm;
}
}


@Simon,

Thanks for your response, I had intended to get back to you today. Sorry I’ve been super busy lately. That was going to be my suggestion as well for just naming it as a different controller name and then pointing your ReportViewer.cshtml links that are going to “/Report/” to go to your controller instead.

Since you’re looking to hide some of the export methods, you could easily do this with some css. Each of the export menu items has a distinct css class. If you’re wanting to hide the “XML” export, then you can use:

li>.ExportXml {
display: none;
visibility: hidden;
height: 0;
}

Let me know if that works for you or not.

Thanks,

Alan

@Cristian, there is already a way available to override the Encoding.

On the ReportController you can override it at a global level (for all your reports) by overriding the “Encoding” property…or you can set it individually on each report model if you have a lot of differences in Encoding by using the “Encoding” property on the model in your ReportController action methods.

Hope this helps!

Alan

@Mike,

Obviously you’ll want to include the Kendo UI JS library in your site, but from what I’m reading on the Kendo UI dropdownlist control, you should be able to just modify my ReportViewer.cshtml file and adjust the call to $(‘select’).select2(); to be $(‘select’).kendoDropDownList();

Hope this helps!

Alan

@Alex, I’m sorry that I’m just now getting to respond to you here. I haven’t really tested against SSRS 2016 yet due to not have one stood up anywhere yet to test against. I assume it should work fine though. That’s odd that a 2012 server works for you but not the 2016. I would look into the configuration of the SSRS server components to ensure that your user account that you’re setting in the ReportController.cs has acces to the server.

@John,

Thanks for the kind words! I’m glad it’s working well for you mostly. The way I have handled the page loading quicker is by setting the AjaxLoadInitialReport property.


//This would be in your specific controller action
model.AjaxLoadInitialReport = false;

//Or this would be on your ReportController.cs
protected override bool AjaxLoadInitialReport
{
get { return false; }
}


Also, I’m looking into updating to .NetCore 2.0 just because there’s a lot of interest in that. I’ve been in the process of upgrading it in my (not much) spare time. Other than that, I haven’t been working on any new features to it really. I use it as is at my workplace and haven’t really needed anything additional.

Alan