Bug #42618 | Exception during execution of [Stored Procedure] | ||
---|---|---|---|
Submitted: | 5 Feb 2009 12:12 | Modified: | 5 Mar 2009 17:07 |
Reporter: | Sebastian Aßmann | Email Updates: | |
Status: | No Feedback | Impact on me: | |
Category: | Connector / NET | Severity: | S3 (Non-critical) |
Version: | 5.1.3 | OS: | Windows (Server 2003) |
Assigned to: | Assigned Account | CPU Architecture: | Any |
Tags: | Null-SQL-Datensatzes, NULL-SQL-Value |
[5 Feb 2009 12:12]
Sebastian Aßmann
[5 Feb 2009 12:52]
Tonci Grgin
Hi Sebastian and thanks for your report. Btw, what version of c/NET are you using? 5.1.3 or 5.2.5? My German-speaking colleagues have translated your error as: The value of a NULL-Datarow cannot be returned (Null-SQL-Datarow) So, it appears to me you have different data/privileges on all of those boxes, and apparently, some of the data/privileges on few boxes are incorrect causing this error. Until you're able to consistently repeat the problem there's not much I can do. At least try to find out why it breaks on some of the boxes and inform me of result. As it looks right now, this could be your oversight/fault.
[5 Feb 2009 15:16]
Sebastian Aßmann
Hi Tonci, first of all we are using the c/NET Version 5.2.5. We tried now to give all privileges to our user for the stored procedure with the following command "GRANT ALL PRIVILEGES ON PROCEDURE our_procedure TO our_user" but this also didnt worked out. If you have more ideas we would really apprechiate it
[5 Feb 2009 17:07]
Tonci Grgin
Sebastian, try setting up 1 MySQL server with data and test that few machines work with it. Then try machines that didn't work before. I presume you have different *data* in different places (servers) accessed from different clients and that is the reason of exception. Is this the case or do all clients fetch same data from single MySQL server?
[6 Mar 2009 0:00]
Bugs System
No feedback was provided for this bug for over a month, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open".