Hi,

Could you check that you have exactly the same dll version on both the server and your development environment?

We have included in the samples a report for displaying version information.

Could you add this report to your report solution and run it from your VSS after having changed the datasource to some existing datasource (even though the report will not retrieve any data from SharePoint).

After having run this report properly from your vss, please deploy the report to your report server and run the report once again from your report server.

Can you confirm that both reports execution returns exactly the same version information?

The schema files are provided as an helper tool for writing queries using an xml file.

The overall idea is to add an xml file to your project, to specify ERSDE.xsd as the associated schema for the xml file, write your queries using the xml file so that you can benefit from intellisense, copy the query into the data view's generic query designer when you are finished. You don't need to keep all your queries into an xml file. When you want to modify a query, you can just copy and paste the query from the data view's query designer into your xml file and make your modifications before copying it back to your report.

Let me know about your version information. You can send me an email as well to our support address if you would like to provide some screen shots. Our support address is available in the documentation.

Regards,

---

Frederic LATOUR
ENESYS

Hi,

Could you possibly send me some logs (or part of some logs) by email so that I can have a look and try to find some possible direction to look into?

Regards,

---

Frederic LATOUR
ENESYS

Hello,

I'm getting a similar error when continually refreshing a report that works about 95% of the time. 

I have the following setup:
Master Report -> Sub Report -> Sub Report

Since that final Subreport fails about 5% of the time, the Master report outputs:
Error: Subreport could not be shown.

Hitting Refresh on the Master Report will just have the Error appear in different Rows as it seems completely random.  I only suspect that "Namespace prefix 'en' is not defined." is happening on one of the subreports is causing the Master Report to show the error for that row.

I would really appreciate some help in solving this as it's not something we can just hit refresh until it gets every row correct.  The report takes about 1 minute to generate because of the complexity.

Thanks!

 

We continue to have this problem. I've gone over all our datasets carefully and checked against the schema. I can't seem to find what's wrong with the reports, but the error intermittently happens. Refreshing fixes the issue temporarily which is fine when it's just me viewing the reports, but it's not realistic for when we're presenting them.

The only consistent thing I see in the error logs is, regardless of which dataset was being called, one of the datasets for a report will fail repeatedly for a given session. If I re load or start a new session for the same report it will work again, and if it runs into a failure, it usually trips up on another datasource, but continues to complain about that dataset for the rest of that session. Any processing failures will blame the dataset it believes failed first even if it was presenting a table that called a different dataset.

Again, it always says fails with " System.Xml.XPath.XPathException: Namespace prefix 'en' is not defined" No such prefix is being used in the rdl . The only prefix I see being used explicitly in the rdl is rd:

Although the error is hard to reproduce reliably, it definitely only occurs in reports with multiple datasets. I don't know if that's due to complexity, or some other issue.

Thanks, and let me know if I can provide further information.

I have the same problem.

Anyone found the solution?