Cannot read the next data row for the data set

Hi,

My report runs fine when I view in VS, data shows fine when I run the query in the data window, but when I publish it to the server, I get the above error. I am running SQL server 2005 RTM and I have re-deployed the entire solution.

Any ideas?

Found the problem.

This is a problem that is down to a bug in reporting services, and I sincerely hope that "they" fix it in the first sp!

Occasionally, reporting services will change your parameter types to string. This is sooooo annoying, and normally fails when you view, but in this case, it took my parameters (date/time) that were already in the parameter boxes (I am altering an existing report) and ran the report happily. I just happened to see that there were no calendar boxes next to the parameters on my web server.

^%$￡"$%^&*&%￡$%^&(*&^%$ is all I can say - this has wasted 2 hours of my time.

Please please Microsoft, fix this bug! A hot fix would be good.....beg beg

|||

Hi,

I experienced similar problems with some of my RS reports and find a solution for my case

I tried to explain the problem and solution at the article http://www.kodyaz.com/articles/article.aspx?articleid=53

For my situation, it seemed that the NULL values within aggregate functions were causing the problem.

Actually although the sql code runs successsfully the warning message "Warning: Null value is eliminated by an aggregate or other SET operation." returned from the sql server was causing the Reporting Services to fire the below error:

An error occured during report processing.
Cannot read the next data row for the data set Dataset1.
A sever error occured on the current command. The results, if any, should be discarded.

A simple way to get rid of the problem is running the t-sql codes between "SET ANSI_WARNINGS OFF" and "SET ANSI_WARNINGS ON" commands.

Eralper

http://www.kodyaz.com

|||Rather than beg microsoft to fix their own mistakes wouldn't you rather use a system that if it had a mistake you could: contact the programmers or fix the mistake yourself?

Using open source ruby (in any OS) you can contact the community or alter the code yourself. Ruby can do anything this reporting services can do.

I've found quite a few bugs in Reporting Services, but rather than beg MS to listen to me I've stopped using MS. I post the bugs to a hacker site, this is much more likely to get MS's attention.

Cannot read the next data row for the data set

Hi,

My report runs fine when I view in VS, data shows fine when I run the query in the data window, but when I publish it to the server, I get the above error. I am running SQL server 2005 RTM and I have re-deployed the entire solution.

Any ideas?

Found the problem.

This is a problem that is down to a bug in reporting services, and I sincerely hope that "they" fix it in the first sp!

Occasionally, reporting services will change your parameter types to string. This is sooooo annoying, and normally fails when you view, but in this case, it took my parameters (date/time) that were already in the parameter boxes (I am altering an existing report) and ran the report happily. I just happened to see that there were no calendar boxes next to the parameters on my web server.

^%$￡"$%^&*&%￡$%^&(*&^%$ is all I can say - this has wasted 2 hours of my time.

Please please Microsoft, fix this bug! A hot fix would be good.....beg beg

|||

Hi,

I experienced similar problems with some of my RS reports and find a solution for my case

I tried to explain the problem and solution at the article http://www.kodyaz.com/articles/article.aspx?articleid=53

For my situation, it seemed that the NULL values within aggregate functions were causing the problem.

Actually although the sql code runs successsfully the warning message "Warning: Null value is eliminated by an aggregate or other SET operation." returned from the sql server was causing the Reporting Services to fire the below error:

An error occured during report processing.
Cannot read the next data row for the data set Dataset1.
A sever error occured on the current command. The results, if any, should be discarded.

A simple way to get rid of the problem is running the t-sql codes between "SET ANSI_WARNINGS OFF" and "SET ANSI_WARNINGS ON" commands.

Eralper

http://www.kodyaz.com

|||Rather than beg microsoft to fix their own mistakes wouldn't you rather use a system that if it had a mistake you could: contact the programmers or fix the mistake yourself?

Using open source ruby (in any OS) you can contact the community or alter the code yourself. Ruby can do anything this reporting services can do.

I've found quite a few bugs in Reporting Services, but rather than beg MS to listen to me I've stopped using MS. I post the bugs to a hacker site, this is much more likely to get MS's attention.

Cannot read the next data row for the data set

Hi,

My report runs fine when I view in VS, data shows fine when I run the query in the data window, but when I publish it to the server, I get the above error. I am running SQL server 2005 RTM and I have re-deployed the entire solution.

Any ideas?

Found the problem.

This is a problem that is down to a bug in reporting services, and I sincerely hope that "they" fix it in the first sp!

Occasionally, reporting services will change your parameter types to string. This is sooooo annoying, and normally fails when you view, but in this case, it took my parameters (date/time) that were already in the parameter boxes (I am altering an existing report) and ran the report happily. I just happened to see that there were no calendar boxes next to the parameters on my web server.

^%$￡"$%^&*&%￡$%^&(*&^%$ is all I can say - this has wasted 2 hours of my time.

Please please Microsoft, fix this bug! A hot fix would be good.....beg beg

|||

Hi,

I experienced similar problems with some of my RS reports and find a solution for my case

I tried to explain the problem and solution at the article http://www.kodyaz.com/articles/article.aspx?articleid=53

For my situation, it seemed that the NULL values within aggregate functions were causing the problem.

Actually although the sql code runs successsfully the warning message "Warning: Null value is eliminated by an aggregate or other SET operation." returned from the sql server was causing the Reporting Services to fire the below error:

An error occured during report processing.
Cannot read the next data row for the data set Dataset1.
A sever error occured on the current command. The results, if any, should be discarded.

A simple way to get rid of the problem is running the t-sql codes between "SET ANSI_WARNINGS OFF" and "SET ANSI_WARNINGS ON" commands.

Eralper

http://www.kodyaz.com

|||Rather than beg microsoft to fix their own mistakes wouldn't you rather use a system that if it had a mistake you could: contact the programmers or fix the mistake yourself?

Using open source ruby (in any OS) you can contact the community or alter the code yourself. Ruby can do anything this reporting services can do.

I've found quite a few bugs in Reporting Services, but rather than beg MS to listen to me I've stopped using MS. I post the bugs to a hacker site, this is much more likely to get MS's attention.sql

Cannot overwrite deployed report with newer version

I have resized the elements of my report so that they will render correctly
in a browser window. I have deleted the report from within Report Manager,
but when I deploy my report from Report Designer (or update it from within
Report Manager), it still looks as it did before. How can I manually delete
all remnants of the old report so that I can upload the revised edition?
--
Bob Yankle sends .... Keep smiling!What is happening is your browser is caching it. Close the broswer and
reopen it.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Bob Yankle" <BobYankle@.discussions.microsoft.com> wrote in message
news:C3C32E98-E6EB-44A9-BF80-0C68B3E591F3@.microsoft.com...
> I have resized the elements of my report so that they will render
> correctly
> in a browser window. I have deleted the report from within Report
> Manager,
> but when I deploy my report from Report Designer (or update it from within
> Report Manager), it still looks as it did before. How can I manually
> delete
> all remnants of the old report so that I can upload the revised edition?
> --
> Bob Yankle sends .... Keep smiling!|||In development I always set my browser to not cache... It is in the
Tools->Internet Options->General->Settings section of IIS...
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Bob Yankle" <BobYankle@.discussions.microsoft.com> wrote in message
news:C3C32E98-E6EB-44A9-BF80-0C68B3E591F3@.microsoft.com...
> I have resized the elements of my report so that they will render
> correctly
> in a browser window. I have deleted the report from within Report
> Manager,
> but when I deploy my report from Report Designer (or update it from within
> Report Manager), it still looks as it did before. How can I manually
> delete
> all remnants of the old report so that I can upload the revised edition?
> --
> Bob Yankle sends .... Keep smiling!|||Hi,
To delete the reports that you have deployed to a report server, you should
go to the folder containing the report on the http://reportserver/Reports url.
Call the list by "Show Details" button to see all details.
When you click the checkbox near by a report "Delete" button will be active
on the above button bar.
You can remove unwanted reports by selecting and deleting at this containing
folder details page.
Eralper
http://www.kodyaz.com
"Bob Yankle" wrote:
> I have resized the elements of my report so that they will render correctly
> in a browser window. I have deleted the report from within Report Manager,
> but when I deploy my report from Report Designer (or update it from within
> Report Manager), it still looks as it did before. How can I manually delete
> all remnants of the old report so that I can upload the revised edition?
> --
> Bob Yankle sends .... Keep smiling!

Cannot open SQL Analyzer in Single User Mode

Hi

I have been having a problem with what I suspect are corrupted indexes. When I try to open the SQL Analyzer window when I have the database in Single User Mode I get the following error:

Msg 4060 Level 16

Cannot open database requested in login 'Timemaster'. Logion Fails

I am using the sa user to login and the password is correct.

SQL Analyzer opens correctly when not restricted to single user mode.

Hope you can help.

Susan

Are you trying to set the database in single user mode or the server in single user mode? This sounds like a misunderstanding of the meaing of what is being set to "single user". If you are trying to set the database into single user mode, please verify that you have database owner privilege on the targeted database.

Cannot find my SQL Server

I have installed SQL Express in my server with SQL Browser enabled. I also added an exception to the window firewall to port 1433.

My client application is installed in another machine on the same workgroup. But I cannot see the SQL Express unless I disabled the server's firewall.

Without disabling the firewall, what else should I do?

Thanks

sqlexpress is a named instance of sqlserver. thus, it does not listen on tcp 1433 by default. you can follow the below article to configure sqlexpress for accepting remote connect through the firewall.
http://support.microsoft.com/kb/914277|||If it would be on port 1433 you wouldn′t need the SQL Browser as the client always assumes this dfault port. SQL Browser is for routing the request to the appopiate port which *could* be port 1433. But the port can differ from 1433 as there can be many instances hosted on the same server, every instance taking one TCP port.

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de
|||By default, when any version of SQL Server 2005 is installed it will not talk to the network. You must use the SQL Server Configuration Manager and enable TCP/IP to talk to the network.|||See my screencast section on my site for more information.

HTH; Jens Suessmeyer.

http://www.sqlserver2005.de|||

I have done the following, but still cannot find my SQL Server 2005 Express installed on WinXP Prof.(SP2) server, My server only has one instance named "AppDefault"

Enable local and remote connections(in Surface Area Configuration for Services and Connections) on the instance of SQL Server that I want to connect to.