Ado.net error while running a process

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • karanit246
    New Member
    • Jun 2013
    • 2

    Ado.net error while running a process

    Hi,
    My application is installed on Windows Server 2003 SP2 and the database is on Sql server 2005.
    The MDAC version of server machine is 2.82.3959.0
    Data access is done using ado.net.
    When I run some process in my application then error 800a0e78 is coming.
    The behavior is not consistent. The error is not reproduced every time. Sometimes the process runs successfully and sometime it gives me error.

    I am connecting to the Server machine remotely through Citrix plug-in.

    I tried to reproduce the problem on other machine but it works fine in other machine.

    I think the problem has to do with SQL but I am not able to find the exact reason for the problem...

    Please guide...

    Thanks,
    Karan
  • ck9663
    Recognized Expert Specialist
    • Jun 2007
    • 2878

    #2
    Lots of dependencies...

    What your process is doing to your data...
    Are there anyone else accessing the data...
    How are you connected to the database....
    Is it a timeout error...

    Good Luck!!!


    ~~ CK

    Comment

    • karanit246
      New Member
      • Jun 2013
      • 2

      #3
      My process is feteching the data from the sql server 2005 using ado.net and then doing some processing on the data.
      No one else is accessing the data.
      I am connected to the database using ado.net.
      No it is not timeout error because it don't happen consistently.
      If it has to do with connection then it will occur consistently for same batch.
      But sometime it work and sometime it shows ado error 800a0e78.
      The program is in French.
      I am not able to find the exact cause of this ado error.

      Please guide,

      Thanks,
      Karan

      Comment

      • ck9663
        Recognized Expert Specialist
        • Jun 2007
        • 2878

        #4
        A quick search shows that you're having this issue because the object you are accessing is closed. It could be that some process you untimely reached the EOF marker and still going while in some process you did not. If that's the case, this is an issue on your .net application and not SQL Server.

        Hard to say without the code.

        Good Luck!!!


        ~~ CK

        Comment

        Working...