Hi, I have recently upgraded from a very old version of Reporting to the latest, and I am having some issues.
My reports will render the headers etc but no rows are returned. I have a class library project defining the reports, used in a VB web site.
So I have a development environment and it was showing no rows, I ran a trace and saw it issuing FMTONLY in the queries. I googled that for hours and found lots of references to the use of temp tables in stored procedures in your report data sources. but my TableAdapters do not use stored procs at all. They use sql views, and have select queries in the Adapters.
So I tweaked this and that until it got to be very late at night and then finally, at some point, it started to work! It now issues correct queries and returns rows of data.
So I deployed it to my production environment... and now it has the no-rows problem.
I don't know what finally fixed the problem.
I suspect it was a SQL Server setting as I have confirmed that the code running in both environments is the same.
My reports will render the headers etc but no rows are returned. I have a class library project defining the reports, used in a VB web site.
So I have a development environment and it was showing no rows, I ran a trace and saw it issuing FMTONLY in the queries. I googled that for hours and found lots of references to the use of temp tables in stored procedures in your report data sources. but my TableAdapters do not use stored procs at all. They use sql views, and have select queries in the Adapters.
So I tweaked this and that until it got to be very late at night and then finally, at some point, it started to work! It now issues correct queries and returns rows of data.
So I deployed it to my production environment... and now it has the no-rows problem.
I don't know what finally fixed the problem.
I suspect it was a SQL Server setting as I have confirmed that the code running in both environments is the same.
3 Answers, 1 is accepted
0
don
Top achievements
Rank 1
Rank 1
answered on 17 Apr 2012, 04:14 PM
Has anyone else seen FMTONLY queries when not using stored procedures in the data source?
0
Massimiliano Bassili
Top achievements
Rank 1
Rank 1
answered on 18 Apr 2012, 08:46 AM
Are you certain the problem is with Telerik? The reporting data sources are just wrappers and only contain instructions how to get the data, they do not work with that data or do anything else to it. Did you try with any databound control like GridView?
Cheers
Cheers
0
don
Top achievements
Rank 1
Rank 1
answered on 19 Apr 2012, 05:19 PM
I'm trying to avoid re-writing a bunch of code that has worked for a long time... and still works in DEV.
But I found the production problem and it was not the FMTONLY issue. In production we got NO database traffic at all.
I edited the constructor of the report class in my report class library, removing the try..catch. This allowed me to see the error that was causing my report to not run.
And I found that my table adapters underlying the report were still trying to use the connection properties from my development environment. All of my connection string names were correct in web.config in prod, but still the report / data source were using their embedded values.
So I did what I consider to be a "hack" - I set my prod values into my dev objects, compiled and re-deployed and it all works now.
-D
But I found the production problem and it was not the FMTONLY issue. In production we got NO database traffic at all.
I edited the constructor of the report class in my report class library, removing the try..catch. This allowed me to see the error that was causing my report to not run.
And I found that my table adapters underlying the report were still trying to use the connection properties from my development environment. All of my connection string names were correct in web.config in prod, but still the report / data source were using their embedded values.
So I did what I consider to be a "hack" - I set my prod values into my dev objects, compiled and re-deployed and it all works now.
-D