Bug #44374 | Error on connect | ||
---|---|---|---|
Submitted: | 20 Apr 2009 22:59 | Modified: | 21 May 2009 8:59 |
Reporter: | Jared S (Silver Quality Contributor) | Email Updates: | |
Status: | No Feedback | Impact on me: | |
Category: | Connector / NET | Severity: | S2 (Serious) |
Version: | 5.2.5 | OS: | Windows (XP) |
Assigned to: | Assigned Account | CPU Architecture: | Any |
Tags: | An, An, Collections, Instance, ListDictionaryInternal, not, object, object, of, reference, SET, system, to |
[20 Apr 2009 22:59]
Jared S
[21 Apr 2009 8:59]
Tonci Grgin
Hi Jared and thanks for your report. What am I to do with it? Let's examine "How to repeat" section: How to repeat: -- Source MyCouriers <<< Not our code -- Message Object reference not set to an instance of an object. -- Data System.Collections.ListDictionaryInternal <<< Not our code -- StackTrace at MyCouriers.queryc.mysql_connect(Boolean xEmergencyCon) at <<< Not our code Do you see my problem? Please post compact but complete test case demonstrating this error I can work with.
[21 May 2009 23: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".