faulting module

Collapse
This topic is closed.
X
X
Collapse
 
  • Page of 1
  • Time
  • Show
Clear All
new posts
Previous template Next
  • Mark A. Weber
    #1

    faulting module

    Hello everyone! This is my first post so please bear with me. We have
    recently re-vamped an Access application such that in each of our 5
    locations
    a local SQL server receives published updates from our main office server.
    Remote servers also send their local updates to the master and they are in
    turn propogated to all of the other remote servers. The new design works
    great except for one annoying bug we have been chasing for two weeks:
    "Faulting application msaccess.exe, version 9.0.0.2719, faulting module
    mso9.dll, version 9.0.0.2720, fault address 0x0007ee2d." When a user gets
    the
    error, they hit close and it terminates Access. If they move the error off
    the screen and continue working the application continues. They have
    discovered this and have been doing so but the fact that the error appears
    must be fixed. If anyone can point me in the right direction it would be
    muchly appreciated. Thanks in advance!

    - Mark
    mweber_at_warre nlumber_dot_com


    Tags: None
    • MacDermott
      #2
      Re: faulting module

      Is there any consistency as to when this error appears?
      Is a particular form/report open?
      Are your users performing a particular task?
      Does it appear when your back-end resynchronizati on occurs?

      - Turtle

      "Mark A. Weber" <mweber@warrenl umber.com> wrote in message
      news:10k15g6dni s829@corp.super news.com...[color=blue]
      > Hello everyone! This is my first post so please bear with me. We have
      > recently re-vamped an Access application such that in each of our 5
      > locations
      > a local SQL server receives published updates from our main office server.
      > Remote servers also send their local updates to the master and they are in
      > turn propogated to all of the other remote servers. The new design works
      > great except for one annoying bug we have been chasing for two weeks:
      > "Faulting application msaccess.exe, version 9.0.0.2719, faulting module
      > mso9.dll, version 9.0.0.2720, fault address 0x0007ee2d." When a user gets
      > the
      > error, they hit close and it terminates Access. If they move the error off
      > the screen and continue working the application continues. They have
      > discovered this and have been doing so but the fact that the error appears
      > must be fixed. If anyone can point me in the right direction it would be
      > muchly appreciated. Thanks in advance!
      >
      > - Mark
      > mweber_at_warre nlumber_dot_com
      >
      >[/color]


        Comment

        • Mark A. Weber
          #3
          Re: faulting module

          Thanak you for your reply! Unfortunately the error occurs randomly and users
          are all using different forms and performing different tasks in the
          application. For the most part, it frequently happens when users have the
          app minimized or leave it on the screen for a few minutes but it also
          happens while they are actively using the system. It sometime occurs when a
          user starts the application. Our network engineer says there is nothing
          indicating a problem in the back-end re-synch logs. We are at a loss. Any
          other thoughts would be invaluable. Thanks again Turtle!

          - Mark

          mweber_at_warre nlumber_dot_com

          "MacDermott " <macdermott@nos pam.com> wrote in message
          news:<pZ50d.150 53$Vl5.11886@ne wsread2.news.at l.earthlink.net >...
          [color=blue]
          > Is there any consistency as to when this error appears?[/color]
          [color=blue]
          > Is a particular form/report open?[/color]
          [color=blue]
          > Are your users performing a particular task?[/color]
          [color=blue]
          > Does it appear when your back-end resynchronizati on occurs?[/color]
          [color=blue]
          >[/color]
          [color=blue]
          > - Turtle[/color]
          [color=blue]
          >[/color]
          [color=blue]
          > "Mark A. Weber" <mweber@warrenl umber.com> wrote in message[/color]
          [color=blue]
          > news:10k15g6dni s829@corp.super news.com...[/color]
          [color=blue][color=green]
          > > Hello everyone! This is my first post so please bear with me. We have[/color][/color]
          [color=blue][color=green]
          > > recently re-vamped an Access application such that in each of our 5[/color][/color]
          [color=blue][color=green]
          > > locations[/color][/color]
          [color=blue][color=green]
          > > a local SQL server receives published updates from our main office[/color][/color]
          server.
          [color=blue][color=green]
          > > Remote servers also send their local updates to the master and they are[/color][/color]
          in
          [color=blue][color=green]
          > > turn propogated to all of the other remote servers. The new design works[/color][/color]
          [color=blue][color=green]
          > > great except for one annoying bug we have been chasing for two weeks:[/color][/color]
          [color=blue][color=green]
          > > "Faulting application msaccess.exe, version 9.0.0.2719, faulting module[/color][/color]
          [color=blue][color=green]
          > > mso9.dll, version 9.0.0.2720, fault address 0x0007ee2d." When a user[/color][/color]
          gets
          [color=blue][color=green]
          > > the[/color][/color]
          [color=blue][color=green]
          > > error, they hit close and it terminates Access. If they move the error[/color][/color]
          off
          [color=blue][color=green]
          > > the screen and continue working the application continues. They have[/color][/color]
          [color=blue][color=green]
          > > discovered this and have been doing so but the fact that the error[/color][/color]
          appears
          [color=blue][color=green]
          > > must be fixed. If anyone can point me in the right direction it would be[/color][/color]
          [color=blue][color=green]
          > > muchly appreciated. Thanks in advance![/color][/color]
          [color=blue][color=green]
          > >[/color][/color]
          [color=blue][color=green]
          > > - Mark[/color][/color]
          [color=blue][color=green]
          > > mweber_at_warre nlumber_dot_com[/color][/color]
          [color=blue][color=green]
          > >[/color][/color]
          [color=blue][color=green]
          > >[/color][/color]
          [color=blue]
          >[/color]
          [color=blue]
          >[/color]

          "MacDermott " <macdermott@nos pam.com> wrote in message
          news:pZ50d.1505 3$Vl5.11886@new sread2.news.atl .earthlink.net. ..[color=blue]
          > Is there any consistency as to when this error appears?
          > Is a particular form/report open?
          > Are your users performing a particular task?
          > Does it appear when your back-end resynchronizati on occurs?
          >
          > - Turtle
          >
          > "Mark A. Weber" <mweber@warrenl umber.com> wrote in message
          > news:10k15g6dni s829@corp.super news.com...[color=green]
          > > Hello everyone! This is my first post so please bear with me. We have
          > > recently re-vamped an Access application such that in each of our 5
          > > locations
          > > a local SQL server receives published updates from our main office[/color][/color]
          server.[color=blue][color=green]
          > > Remote servers also send their local updates to the master and they are[/color][/color]
          in[color=blue][color=green]
          > > turn propogated to all of the other remote servers. The new design works
          > > great except for one annoying bug we have been chasing for two weeks:
          > > "Faulting application msaccess.exe, version 9.0.0.2719, faulting module
          > > mso9.dll, version 9.0.0.2720, fault address 0x0007ee2d." When a user[/color][/color]
          gets[color=blue][color=green]
          > > the
          > > error, they hit close and it terminates Access. If they move the error[/color][/color]
          off[color=blue][color=green]
          > > the screen and continue working the application continues. They have
          > > discovered this and have been doing so but the fact that the error[/color][/color]
          appears[color=blue][color=green]
          > > must be fixed. If anyone can point me in the right direction it would be
          > > muchly appreciated. Thanks in advance!
          > >
          > > - Mark
          > > mweber_at_warre nlumber_dot_com
          > >
          > >[/color]
          >
          >[/color]


            Comment

            • MacDermott
              #4
              Re: faulting module

              Is there an error number reported?

              What does the title bar of the error message say?

              Are your users running an mdb or an mde (or perhaps an adp or ade) file?

              - Turtle

              "Mark A. Weber" <mweber@warrenl umber.com> wrote in message
              news:10kdn0vje3 9h8f8@corp.supe rnews.com...[color=blue]
              > Thanak you for your reply! Unfortunately the error occurs randomly and[/color]
              users[color=blue]
              > are all using different forms and performing different tasks in the
              > application. For the most part, it frequently happens when users have the
              > app minimized or leave it on the screen for a few minutes but it also
              > happens while they are actively using the system. It sometime occurs when[/color]
              a[color=blue]
              > user starts the application. Our network engineer says there is nothing
              > indicating a problem in the back-end re-synch logs. We are at a loss. Any
              > other thoughts would be invaluable. Thanks again Turtle!
              >
              > - Mark
              >
              > mweber_at_warre nlumber_dot_com
              >
              > "MacDermott " <macdermott@nos pam.com> wrote in message
              > news:<pZ50d.150 53$Vl5.11886@ne wsread2.news.at l.earthlink.net >...
              >[color=green]
              > > Is there any consistency as to when this error appears?[/color]
              >[color=green]
              > > Is a particular form/report open?[/color]
              >[color=green]
              > > Are your users performing a particular task?[/color]
              >[color=green]
              > > Does it appear when your back-end resynchronizati on occurs?[/color]
              >[color=green]
              > >[/color]
              >[color=green]
              > > - Turtle[/color]
              >[color=green]
              > >[/color]
              >[color=green]
              > > "Mark A. Weber" <mweber@warrenl umber.com> wrote in message[/color]
              >[color=green]
              > > news:10k15g6dni s829@corp.super news.com...[/color]
              >[color=green][color=darkred]
              > > > Hello everyone! This is my first post so please bear with me. We have[/color][/color]
              >[color=green][color=darkred]
              > > > recently re-vamped an Access application such that in each of our 5[/color][/color]
              >[color=green][color=darkred]
              > > > locations[/color][/color]
              >[color=green][color=darkred]
              > > > a local SQL server receives published updates from our main office[/color][/color]
              > server.
              >[color=green][color=darkred]
              > > > Remote servers also send their local updates to the master and they[/color][/color][/color]
              are[color=blue]
              > in
              >[color=green][color=darkred]
              > > > turn propogated to all of the other remote servers. The new design[/color][/color][/color]
              works[color=blue]
              >[color=green][color=darkred]
              > > > great except for one annoying bug we have been chasing for two weeks:[/color][/color]
              >[color=green][color=darkred]
              > > > "Faulting application msaccess.exe, version 9.0.0.2719, faulting[/color][/color][/color]
              module[color=blue]
              >[color=green][color=darkred]
              > > > mso9.dll, version 9.0.0.2720, fault address 0x0007ee2d." When a user[/color][/color]
              > gets
              >[color=green][color=darkred]
              > > > the[/color][/color]
              >[color=green][color=darkred]
              > > > error, they hit close and it terminates Access. If they move the error[/color][/color]
              > off
              >[color=green][color=darkred]
              > > > the screen and continue working the application continues. They have[/color][/color]
              >[color=green][color=darkred]
              > > > discovered this and have been doing so but the fact that the error[/color][/color]
              > appears
              >[color=green][color=darkred]
              > > > must be fixed. If anyone can point me in the right direction it would[/color][/color][/color]
              be[color=blue]
              >[color=green][color=darkred]
              > > > muchly appreciated. Thanks in advance![/color][/color]
              >[color=green][color=darkred]
              > > >[/color][/color]
              >[color=green][color=darkred]
              > > > - Mark[/color][/color]
              >[color=green][color=darkred]
              > > > mweber_at_warre nlumber_dot_com[/color][/color]
              >[color=green][color=darkred]
              > > >[/color][/color]
              >[color=green][color=darkred]
              > > >[/color][/color]
              >[color=green]
              > >[/color]
              >[color=green]
              > >[/color]
              >
              > "MacDermott " <macdermott@nos pam.com> wrote in message
              > news:pZ50d.1505 3$Vl5.11886@new sread2.news.atl .earthlink.net. ..[color=green]
              > > Is there any consistency as to when this error appears?
              > > Is a particular form/report open?
              > > Are your users performing a particular task?
              > > Does it appear when your back-end resynchronizati on occurs?
              > >
              > > - Turtle
              > >
              > > "Mark A. Weber" <mweber@warrenl umber.com> wrote in message
              > > news:10k15g6dni s829@corp.super news.com...[color=darkred]
              > > > Hello everyone! This is my first post so please bear with me. We have
              > > > recently re-vamped an Access application such that in each of our 5
              > > > locations
              > > > a local SQL server receives published updates from our main office[/color][/color]
              > server.[color=green][color=darkred]
              > > > Remote servers also send their local updates to the master and they[/color][/color][/color]
              are[color=blue]
              > in[color=green][color=darkred]
              > > > turn propogated to all of the other remote servers. The new design[/color][/color][/color]
              works[color=blue][color=green][color=darkred]
              > > > great except for one annoying bug we have been chasing for two weeks:
              > > > "Faulting application msaccess.exe, version 9.0.0.2719, faulting[/color][/color][/color]
              module[color=blue][color=green][color=darkred]
              > > > mso9.dll, version 9.0.0.2720, fault address 0x0007ee2d." When a user[/color][/color]
              > gets[color=green][color=darkred]
              > > > the
              > > > error, they hit close and it terminates Access. If they move the error[/color][/color]
              > off[color=green][color=darkred]
              > > > the screen and continue working the application continues. They have
              > > > discovered this and have been doing so but the fact that the error[/color][/color]
              > appears[color=green][color=darkred]
              > > > must be fixed. If anyone can point me in the right direction it would[/color][/color][/color]
              be[color=blue][color=green][color=darkred]
              > > > muchly appreciated. Thanks in advance!
              > > >
              > > > - Mark
              > > > mweber_at_warre nlumber_dot_com
              > > >
              > > >[/color]
              > >
              > >[/color]
              >
              >[/color]


                Comment

                Previous template Next
                Working...