Highlighted
Visitor.
1630 views

client Caching Mailbox codeless error message

Environment
Backend: GW 2012 Server
Frontend: Mac OS X 10.7.5 with GW client 8.0.2HP4

Machine unable to open caching DB

How I tried to fix it:
GWcheck (analyze / repair structure with index check, contents check afterwards) on Mac.
Unfortunately unsuccesful. Then I copied DB to Win7SP1 PC and ran GWcheck32 12.0.2.0.108211 (analyze / repair structure with index check, contents check afterwards) again.

When I try to access DB the same codeless error message appears on PC.

Any suggestion appreciated
--
Best regards,
jgoy
Labels (2)
Tags (1)
0 Likes
9 Replies
Highlighted
Knowledge Partner
Knowledge Partner

Re: client Caching Mailbox codeless error message

In article <jgoy.67onzf@no-mx.forums.novell.com>, Jgoy wrote:
> Backend: GW 2012 Server
> Frontend: Mac OS X 10.7.5 with GW client 8.0.2HP4
>
> Machine unable to open caching DB
>


Sometimes you just have to move the old cached DB out of the way and
create a new one.

While you are at it, make sure the anti-virus is NOT scanning the
cached DB folder as that is the fastest way to corrupt them when an
innocent enough string happens to match the A/V sigs.



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

___
“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
Highlighted
Visitor.

Re: client Caching Mailbox codeless error message

Hi Andy,
thanks for your reply.

I don't have a problem to create a new caching mailbox. My problem is data loss when I move the old cached DB out of the way.
And in the end a frustrated Mac user and a damaged GW reputation...
--
jgoy
0 Likes
Highlighted
Micro Focus Expert
Micro Focus Expert

Re: client Caching Mailbox codeless error message

Hi jgoy,

A caching mailbox is simply a "replica" of the data/message store on the server. How will creating a new caching mailbox cause data loss?

Cheers,
Laura Buckley

Views/comments expressed here are entirely my own.
If you find this post helpful, please show your appreciation and click on "Like" below...
0 Likes
Highlighted
Visitor.

Re: client Caching Mailbox codeless error message

Hi Laura,
our clients have restricted mailbox sizes and rules on their mailboxes on the server. Mailboxes are being cleaned up automatically. The reason for that is simply to drop old data from the database. Users tend to collect and save data for years.
The only way for our users to get rid of these rules is to create a local caching DB. The server stores the data of the last 30 days.
When a user has stored data of the last 45 days in the caching DB and this caching DB is corrupt data of 15 days are gone.

In this special case it won't be a tragedy. Anyone working in caching mode is informed about the risk. But finally: error messages referring to a non existent error code aren't really helpful... (see screenshot) 😉
--
Best regards,
jgoy
0 Likes
Highlighted
Micro Focus Expert
Micro Focus Expert

Re: client Caching Mailbox codeless error message

Hi jgoy,

Many thanks for the clarification. In my environment we push the mailbox size limit to the caching mailbox and ensure that caching and live are identical in order to avoid this type of issue - hence my question to you 😉

I'm not familiar with the error that you are seeing, thus am unable to comment on that. Hopefully somebody more knowledgeable on the MAC client will join the conversation soon.

Good luck.

Cheers,
Laura Buckley

Views/comments expressed here are entirely my own.
If you find this post helpful, please show your appreciation and click on "Like" below...
0 Likes
Highlighted
Knowledge Partner
Knowledge Partner

Re: client Caching Mailbox codeless error message

In article <jgoy.67q3db@no-mx.forums.novell.com>, Jgoy wrote:
> our clients have restricted mailbox sizes and rules on their mailboxes
> on the server. Mailboxes are being cleaned up automatically. The reason
> for that is simply to drop old data from the database. Users tend to
> collect and save data for years.
>

Ah, that will do it.
FYI, In some jurisdictions this set up won't be accepted by the courts as
acceptable, so make sure you aren't setting up for problems should a
legal case happen that requires old email as a part of discovery.
I have a client where the core GW system holds mail for 2 year, and if
the users need anything beyond that, they go to the archival system (in
their case Retain)

If users have data that is only stored on their local systems, perhaps
some backup is in order. After all, corruption and data loss happen
there often enough whether through viri, hardware failure, or just plain
fumble fingers.

There are other ways of managing space on a mail system than cutting out
all mail older than a certain date. Perhaps a gander through some of the
options I've written up may help you find a patch that avoids such
situations. Start with where the space is used first
http://www.konecnyad.ca/andyk/gwbig.htm and work from there.


Andy of
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!

___
“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!
Highlighted
Visitor.

Re: client Caching Mailbox codeless error message

> FYI, In some jurisdictions this set up won't be accepted by the courts

Yes, I know. Our management simply ignores the facts about it...

Nevertheless - thanks for the discussion and your links!
--
jgoy
0 Likes
Highlighted
Micro Focus Expert
Micro Focus Expert

Re: client Caching Mailbox codeless error message

Hi JGoy,

Perhaps you can open a Service Request with Novell Technical Support - they may be able to assist in ways that we can't.

Cheers,
Laura Buckley

Views/comments expressed here are entirely my own.
If you find this post helpful, please show your appreciation and click on "Like" below...
0 Likes
Highlighted
Knowledge Partner
Knowledge Partner

Re: client Caching Mailbox codeless error message

In article <jgoy.6832yo@no-mx.forums.novell.com>, Jgoy wrote:
> Yes, *I* know. Our management simply ignores the facts about it...
>

Very good, then all you really need to do now is make sure that you
have documented that you have attempted to educate management on this
so that if it does blow up, it is in their faces, aka C.Y.A.

If you want some more ammo, some of the white papers at
http://www.ostermanresearch.com/downloads.htm#Archiving_and_Related_Iss
ues can be very useful. You only get one or two emails from him a month
from that sign up, and those surveys are interesting and good at
keeping you abreast of the market.

And as Laura said, an SR is about the only option left as they can dig
deeper than the tools we have. Hopefully you have a copy of the db
before you tried to fix it.


Andy of
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!

___
“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.