all groups > sql server reporting services > august 2004 >
You're in the

sql server reporting services

group:

A severe error occurred on the current command.


A severe error occurred on the current command. bmurtha
8/14/2004 6:58:48 PM
sql server reporting services:
When ever I run a particular report. Even if I set the
connection to don't time out. I keep getting this:

An error has occurred during report processing.
(rsProcessingAborted) Get Online Help Cannot read the next
data row for the data set MOPhoneSkins.
(rsErrorReadingNextDataRow) Get Online Help
A severe error occurred on the current command. The
results, if any, should be discarded.

I don't understand what's going on. Please help me out if
you've had this problem.

Thanks in advance,
Re: A severe error occurred on the current command. Robert Bruckner [MSFT]
8/15/2004 3:51:37 PM
This exception comes from the ADO.NET / the underlying data provider.
Reporting Services just wraps the exception.
There are many possible reasons why this exception can happen. One example:
you specify a stored procedure on server A in your report as data source. At
runtime this stored procedure tries to invoke another stored procedure on
server B through the linked server feature and fails because of missing
privileges to execute stored procedures on server B.

You might want to search ADO related newsgroups (e.g.
news:microsoft.public.dotnet.framework.adonet) or on the internet for the
exception message string "A severe error occurred on the current command.
The results, if any, should be discarded."

--
This posting is provided "AS IS" with no warranties, and confers no rights.



[quoted text, click to view]

AddThis Social Bookmark Button