GroupWise Client shuts down after frying to attach a file

Hi Everyone,

I have a user who has a problem with their GroupWise 2014 Client on Windows 10 (1607 - 14393.693).

When the user makes a new email, and tries to attach a file to the email, the user receives the generic "groupwise client has stopped working", and the client shuts down.

The client has been working up until the other day and now is not.

The user had client version 14.2.1 Build 124014 and I have even tried to upgrade the users client to 14.2.1 Build 124595, but the problem still exists.

I can see the starting directory for where the client is trying to go to, and then it crashes, but I can't see the full file path, not sure if this helps, or is part of the problem.
How to you force a clear of all GroupWise settings, etc.

Any ideas?

Thanks,

Anthony :)

Tags:

  • Hi Anthony,

    There are a few things that you could try.

    1. To rule out a workstation/profile issue get the user to try do this on a different [working] computer. If the problem doesn't follow them then you most likely have an issue isolated to that one workstation.

    2. If the problem follows the user from one workstation to another you can do a reset of their client options from the GroupWise Admin Console by running maintenance (GWCheck) against just that user with the "Reset Client Options" option selected. Just make sure that the user has exited both GroupWise client and Notify before running this option. It takes less than a minute and clears all custom settings in the user database.

    Please let us know how it goes.

    Cheers,
  • Hi Laura,

    At the end of the day it was a very simple fix.
    The user was trying to access a folder / file on the network, which had a very long file name, which went off the screen.
    Once the filename on the network share was renamed to a much shorter name, everything worked.

    Thanks everyone for you help.

    Case closed.

    Anthony :)
  • On Thu, 16 Feb 2017 21:56:02 0000, anthonywhill wrote:

    > Hi Laura,
    >
    > At the end of the day it was a very simple fix.
    > The user was trying to access a folder / file on the network, which had
    > a very long file name, which went off the screen.
    > Once the filename on the network share was renamed to a much shorter
    > name, everything worked.
    >
    > Thanks everyone for you help.
    >
    > Case closed.
    >
    > Anthony :)


    Good morning,

    thank you for sharing how to solve this vary bad situation.

    But I think this is a GW client bug and should be reported to MF.
    My opinion of course.

    ---

    Best regards,

    -Jan

  • In article <GwvpA.531$tn5.118@novprvlin0913.provo.novell.com>, Dus2002
    wrote:
    > But I think this is a GW client bug and should be reported to MF.
    > My opinion of course.


    Weak error handling, though it could be partially on the Windows side
    as well. Best way for anyone to properly report it is to open a
    Service Request on the topic. Even if in the end it is a Windows issue,
    Micro Focus can nudge Microsoft about it.

    What I suspect happened is that the full name with path to the share is
    just under 255 characters, but when the file is copied to C:\users
    \username\AppData\Local\Temp\ it is just over.


    Andy of
    http://KonecnyConsulting.ca in Toronto
    Knowledge Partner
    http://forums.novell.com/member.php/75037-konecnya
    If you find a post helpful and are logged in the Web interface, please
    show your appreciation by clicking on the star below. Thanks!