Exception from HRESULT: 0x800A9D9F

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • Malathi
    New Member
    • Mar 2012
    • 31

    Exception from HRESULT: 0x800A9D9F

    Hi,

    Im opening an accessdb(consis ts of forms,report,et c) via vb.net console application. This is for the purpose of scheduling jobs. Its working fine for hours. But if we are not logging in for 2 days the scheduler throws an exception as follows.
    Exception from HRESULT: 0x800A9D9F
    After logging in the error is disappearing. So I added the mdb into trust location but its of no use. I will be glad if anyone helps me.
  • TheSmileyCoder
    Recognized Expert Moderator Top Contributor
    • Dec 2009
    • 2322

    #2
    You will need to show us the code you are using, and indicating the line which fails.

    Comment

    • Malathi
      New Member
      • Mar 2012
      • 31

      #3
      Thanks for your reply smileycoder. Actually its happening at the run time, that too login issue. i.e. When the scheduling starts this app works fine, but if we are not logging for days then its throwing the above exception. If we do login again to the scheduler( by providing credentials)its working fine. This exception error disappears and continues the job as usual.
      The model of the code Im using in vb.net console app is,
      Code:
      Private Sub RunAccessSub()  
      Dim appAccess As Object
            ' Create instance of Access Application object.
           appAccess = CreateObject("Access.Application")
              ' Open WizCode database in Microsoft Access window.
          appAccess.OpenCurrentDatabase "C:\My Documents\WizCode.mdb", False
              ' Run Sub procedure.
          appAccess.Run "Greeting", "Joe"
          Set appAccess = Nothing
          End Sub
      Hope this gives you an idea.

      Comment

      • TheSmileyCoder
        Recognized Expert Moderator Top Contributor
        • Dec 2009
        • 2322

        #4
        I dont really know what the exception is, and without real code to work with there really isn't anything I can do to help you. I don't know your setup, I dont know your access version, I don't know exactly what you mean by "logging in".

        You do no provide nearly enough details to even guess where problems may arise.

        Comment

        • zmbd
          Recognized Expert Moderator Expert
          • Mar 2012
          • 5501

          #5
          I think it has something to do with the .net framework throwing the error and not access.

          If you are leaving a connection open to the .net for an extended idle time then there maybe a timeout on the connection thus a generic COM security error.

          -z

          Comment

          • zmbd
            Recognized Expert Moderator Expert
            • Mar 2012
            • 5501

            #6
            Yep,
            This is a dot-net issue.. out of my knowledge base; however, here's a little information I read:

            hopefully this will point you in the right direction.

            -z

            Comment

            • Malathi
              New Member
              • Mar 2012
              • 31

              #7
              Ya.. I too feel the same while reading the link provided by you zmbd.. Here Im getting a perspective that this com exception is thrown because of access security? Or even if its within .net, what might be the solution? Do you have any idea?

              Comment

              • zmbd
                Recognized Expert Moderator Expert
                • Mar 2012
                • 5501

                #8
                No; however, maybe moving this thread or reposting the question to the dot-net-framework forum may result in a better answer in that someone there has seen this...
                -z
                Last edited by zmbd; Aug 30 '12, 10:57 AM.

                Comment

                • Malathi
                  New Member
                  • Mar 2012
                  • 31

                  #9
                  thanks zmcd.. I will move it .net forum!

                  Comment

                  Working...