Highlighted
Absent Member.
Absent Member.
855 views

GWCheck Question

I've had a question about GWCheck that I've always been curious about but never asked until now.

When I manually run it using the GWCheck.exe utility and performing a Analyze/Fix Databases, why is it that in my status/log file window that I see details on messages not related to the user. What I mean is that I see blurbs similar to the following:

GWCheck is being performed on user "JSMITH"
680830 LIN ATTACHMENT RECORD Check
Problem 82- Inaccessible attachment file [\\server\path\to\file]
Item Sent by: [Not JSMITH]
Item Sent on: [date/time]
Item Sent to: [Not JSMITH]
Attachment type: File

So to summarize, I'm doing the GWCheck on user JSMITH, and GWCheck throws this error at me, it is always Problem 82. Quite a number of times it is a message to/from JSMITH, but just as often it is something that they are neither the sender or recipient. I was just curious why/how this happens. I can run GWCheck Analyze multiple times in a row, or even do a Structural Rebuild and analyze again and the same records references keep popping up. Was just curious why that is. Thanks!
Labels (1)
0 Likes
3 Replies
Highlighted
Micro Focus Expert
Micro Focus Expert

Re: GWCheck Question

Hi,

When you run a GWCheck against a user and have both the user and message database selected then both are checked. Remember that message databases are not user specific but rather shared among multiple users.

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
Micro Focus Expert
Micro Focus Expert

Re: GWCheck Question

Hi,

Further to what I said above... about the Problem 82 error message. Find, by looking at the GWCheck log file, which message database belongs to JSMITH. This would be the message database with the errors. Run a standalone GWCheck and in the entry box for User/Resource enter the name of the message db keeping in mind that it is case sensitive. Deselect Structure, check Contents, ensure to check Attachment File Check and Fix problems. Run that twice. Then take a look at see if you are still getting Problem 82 error messages.

Please let us know how it goes.

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: GWCheck Question

In article <marklar23.7j2dzz@no-mx.forums.microfocus.com>, Marklar23
wrote:
> Item Sent by: [Not JSMITH]
> Item Sent on: [date/time]
> Item Sent to: [Not JSMITH]


Sent To: is first person on Sent To: list, it doesn't mention whom else
or who is CC:ed or BCC:ed (can't be bothered to? 😉

You can run this using the POA based GWCheck as it is closer to the
data and with less chance of any antivirus or LAN issues getting in the
way.

This TID addresses Problem 82 and it hasn't changed since then, though
do keep Laura's notes in mind as well to make sure you got it.
https://support.novell.com/docs/Tids/Solutions/10098614.html

Letting us know how it went would be appreciated.


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!

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