When trying to export a report I receive a WCF error saying "Endpoint not found". The reports are running OK and display fine in the HTML viewer application, it's just the export which doesn't work. I have tried all of the export options available and all give this error message.
The server in question is Windows Server 2003 and runs IIS 6.
Tips to troubleshoot would be appreciated as I've exhausted my knowledge of IIS 6 now.
Hello Shaun,
Thank you for contacting Infragistics!
I have done some looking into this matter and have the following questions concerning this matter:
What is the full error message you are receiving?When you say export report do you mean with the report viewer, or are you referring to another tool?What version of the Infragistics controls are you using?What are you exporting to: pdf, excel?
Hi Mike,
Thanks for your reply. We are using version 12.2.
The error I mentioned is the full error message, please see a screenshot at http://imgur.com/MesJpvi
We are exporting using the report viewer and all types of export fail with the same error, PDF, Excel and XPS.
Best regards.
Thank you for the update. I have done some looking into this matter and have the following information. I recommend you read the following links concerning this error:
http://stackoverflow.com/questions/15130879/wcf-endpoint-not-found
http://community.discountasp.net/threads/wcf-endpoint-not-found.21316/
Please let me know if you have any further questions concerning this matter.
Apologies for the delay. I have had a look at those links but unfortunately they do not seem to help.
I do already have the endpoint configuration in the web.config, the only thing I did not have was a <baseAddress> but adding this did not help. If I browse to the service directly without anything after the .svc part of the URL (i.e http://localhost/Applications/ReportService.svc) I do receive the standard WCF endpoint details page, it's when you start adding thigs after the .svc part of the URL we receive the "Endpoint not found" error.
We also have this exact same deployment package working on numerous customer servers without issue, it's just this one installation which gives us this error. The only difference with this installation is this is running on Windows Server 2003 and IIS6, the rest run successfully on either IIS7 or IIS8.
Kind regards.
Thank you for the update. I have also found the following questions:
Do you get any other errors?Can you open the browser dev tools console and see any error or messages appear there?