/ Forums / Advansys Formativ / Formativ Runtime / Access violation error

  • Creator
    Topic
  • #3754
    SandD
    Participant

    We are starting to see the following problem on more than one user groupwise. ” Access violation at address
    53434768 in module ‘Gwcma1.dll read of address 00000000″
    The user client version is groupwise 6.5.1 and the Server is on 6.5.4

    I have traced the applet that is making the error pop up. I have removed the applet from the users. The strange thing is that the users it is working for are using the same file as it is in shared location.

    Thanks

  • Author
    Replies
  • #6045
    Support 2
    Moderator

    Is it a custom applet? What does the applet do and how is it integrated with the GroupWise client (toolbars, events etc.)?

    From experience and although rare, we’ve seen that it is possible for an applet’s operation to be sensitive to the state of a GroupWise user’s account. This can vary according to how the applet uses the GroupWise APIs and events and to the GroupWise Client version. A thorough GWCheck of a user’s account may help.

    For at least on of the workstations with the problem, it is recommended that you upgrade to GroupWise 6.5.4 or later (6.5.6 is the latest).

    Regards,

    Advansys Support

    #6046
    SandD
    Participant

    Yes it is a custom applet.
    When I have change the user up to groupwise client 6.5.4 we is a memory leak on the groupwise client when this applet is running.

    Thanks
    David

    #6044
    Support 3
    Participant

    Memory leak on the GroupWise client can arise due to the applet calling the Object API in a sequence which leads to the API state becoming unstable.

    Our experience with the GroupWise APIs has taught us that sometimes an obvious or intuitive approach is not feasible; that an applet must be redesigned to work around an API defect or to manage internal API resources.

    The difficulty is usually in figuring out which API is responsible for the problem. Using the process of elimination, however, you can usually narrow the problem down rather quickly by making small logical changes and observing the impact on the problem. The key is to make only one change at a time and then see if the problem goes away. You can use the Trace commands to your source code to get a real-time picture of the execution sequence. See the Developers Guide section Error Handling and Debugging for details.

    Hope this helps.

    Regards,
    Advansys Support

Viewing 3 replies - 1 through 3 (of 3 total)
  • You must be logged in to reply to this topic.