This is a migrated thread and some comments may be shown as answers.

Resources file error: can't find for "specified or neutral culture"

1 Answer 198 Views
General Discussions
This is a migrated thread and some comments may be shown as answers.
Rose
Top achievements
Rank 1
Rose asked on 10 Feb 2011, 10:22 PM

I've got a Telerik report that was compiling and previewing just fine until I added the most recent data source, a SQL Server view that provides data to several of the crosstabs. The data source itself works fine; when I "configure" it in the Data Source section I can execute the query and return correct results. So I don't know if the data source is the problem, but as soon as I added the data source, changed the formulas and filters in the crosstabs to refer to them (instead of the old data source) and then tried to run the report, I got this error:

Exception has been thrown by the target of an invocation. Could not find any resources appropriate for the specified culture or the neutral culture. Make sure "PDS.reports_13monthrollingweb.resources" was correctly embedded or linked into assembly "PDS" at compile time, or that all the satellite assemblies required are loadable and fully signed."

I'd be happy to do all that if I knew what it meant. :) How do I make sure the ".resources" file is correctly embedded into the solution ("PDS"), and/or what are satellite assemblies and how do I know if they are loadable and fully signed?

Thanks.

Addendum: Digging around in other reports, I notice they don't have SQL data sources listed in their .resx file. In this report, none of the other SQL data sources are in the .resx file, but the new one is (see attached). Should I just remove it? Why is it appearing there when the others aren't?

1 Answer, 1 is accepted

Sort by
0
Rose
Top achievements
Rank 1
answered on 10 Feb 2011, 11:19 PM
I rebuilt the underlying view so that I wouldn't need to use the "SUM" function in my SQL query, and then attached a new SQL datasource to the report using that view. I deleted the other datasource, and that solved the issue. I'm still not sure why the other query threw an exception, but I'm guessing -- just guessing -- that it was the "SUM" in the SQL statement that it didn't like.
Tags
General Discussions
Asked by
Rose
Top achievements
Rank 1
Answers by
Rose
Top achievements
Rank 1
Share this question
or