Highlighted
Absent Member.
Absent Member.
622 views

Groupwise Mobility - Attachment cash issues

Hi,

We keep getting an issue with Groupwise Mobility 2.1 every so often. On top of the usual groupwise gripes.

Every so often a user who forwards an email with an attachment will get a previously attached attachment with the same name attached to the email rather than the one attached, (if that makes sense?)

For example

User 1 emails user 2 via Mobility with Attachment SalesV1.xls
User 2 edits SalesV1.xls and forwards to User1 who picks up email via Mobility. They get the correct file.
User 1 then forwards to User 3 via Mobility
User 3 will get the first version of SalesV1.xls whether it be via Mobility or Groupwise Client.

We have also had a similar issue where a user attaches an image call image.png and sends via mobility. When the recipient user gets this email they will also get other images call image.png from the mobility server

This is able to be replicated time and time again without failure.

Having looked at the dsapp attachment stats there is a clear mismatch between database filestoreid and file system filestoreid (is this correct?). With numerous duplicates (which I assume is to be expected)?

Do you have any idea how to fix this? It's only a matter of time before something critical is sent and acted upon before finding the information is for a previous version.
Labels (1)
0 Likes
2 Replies
Highlighted
Outstanding Contributor.
Outstanding Contributor.

Re: Groupwise Mobility - Attachment cash issues

I would guess the first thing that is going to be suggested is upgrade to Mobility 2014 and retest, you'll obviously need to be thinking about upgrading the GW backend to 2014 at the same time.
The chances of getting a fix for 2.1 are negligible I would think, if it still occurs on 2014 and is replicable then you could get it addressed.

Mark.
0 Likes
Highlighted
Knowledge Partner
Knowledge Partner

Re: Groupwise Mobility - Attachment cash issues

In article <alarge.7lmxdh@no-mx.forums.microfocus.com>, Alarge wrote:
> We keep getting an issue with Groupwise Mobility 2.1 every so often. On
> top of the usual groupwise gripes.
>
> Every so often a user who forwards an email with an attachment will get
> a previously attached attachment with the same name attached to the
> email rather than the one attached, (if that makes sense?)


Have your run through a Vacuum and re-index with dsapp?
There is a chance something is just stuck causing this to happen, and
running through that basic maintenance may knock it free. Otherwise
updating as Mark posted becomes your best bet.


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!
GMS troubleshooting tips at http://www.konecnyad.ca/andyk/gwmobility.htm


___
“i’ve sworn an oath of solitude til the blight is purged from these lands”
Andy of Konecny Consulting in Toronto
Knowledge Partner Profile
If you find a post helpful, click the Like button below. Thanks!
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.