Highlighted
Absent Member.
Absent Member.
1714 views

Archive Error 83

Hi Forum,

one user generates thousands of entries in his gwcheck log from our weekend checks
Error 83- Item failed to archive
- Subject: $subject
- From: $sender
- Date: Aug 22, 2011 - 3:22 pm
- First archive attempt date: Feb 20, 2014
- Number of archive attempts: 19
- Error number on last Archive attempt: 0xC050


I guess the first try was at a time where the archive was not accessible... Now every gwcheck at weekends tries to archive them but has no access to his network drive where the archive resides.
Archiving a single mail works at the moment!
IMHO there was a way to trigger the archive of these messages from the client?!
If this is not the case I let him search for mails older then his settings an try to archive from the search window.
Hopefully in the next gwcheck all Error 83 messages are gone 🙂

Thanks in advance!

Cheers,
Pascal

"Have you tried turn it off and on again?"
Labels (2)
0 Likes
7 Replies
Highlighted
Absent Member.
Absent Member.

Re: Archive Error 83

What check is that?

Uwe


--
Novell Knowledge Associate
Please don't send me support related e-mail unless I ask you to do so.
0 Likes
Highlighted
Absent Member.
Absent Member.

Re: Archive Error 83

Hi Uwe,

this is a gwcheck with analyze/fix databases and content/structure enabled which I configured in C1 for a POA in its properties under the groupwise tab -> scheduled events.

Is it true that the archive path is stored for every mail the Client tries to archive? So if the path is not available any more and archiving fails, then changing the path to an accessible folder will not help!?
If this is the case, can I overwrite the path information somehow? Or is it possible to remove the information completely, that a mail should be archived?

Thanks in advance,
Pascal

"Have you tried turn it off and on again?"
0 Likes
Highlighted
Knowledge Partner
Knowledge Partner

Re: Archive Error 83

In article <bendeichp.6bhr5z@no-mx.forums.novell.com>, Bendeichp wrote:
> Is it true that the archive path is stored for every mail the Client
> tries to archive?

I would rather doubt this
Step one, do you really want to archive messages? Because if not we
could just turn that off.
Otherwise just set the archive path for this user to something that
the client and/or the POA can get to.


Andy Konecny
Knowledge Partner (voluntary SysOp)
Konecny Consulting Inc. in Toronto

"Give more than others think is wise
Challenge yourself beyond what others think is right"
Michael 'Pinball' Clemens

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

Re: Archive Error 83

Pascal,

I wouldn't run a check which does structure AND contents at the same time.
What happens if you run the check(s) manually?
Different results?

Uwe


--
Novell Knowledge Associate
Please don't send me support related e-mail unless I ask you to do so.
0 Likes
Highlighted
Absent Member.
Absent Member.

Re: Archive Error 83

Hi Uwe,

it's only a content check, not both (content and structure)! Sorry for misinformation 😞 I setup different checks quite some time ago. Sturcture checks run every night from Monday to Friday and Content Checks run at the weekend.

Back to the problem user: I started a content gwcheck via c1... I will post the result.
Or would you rather do a standalone gwcheck on his workstation for his caching mailbox?

Besides: I let the user archive 5 mails which are mentioned in the log file as error 83. He told me that all could be archived successfully.

Cheers,
Pascal

"Have you tried turn it off and on again?"
0 Likes
Highlighted
Absent Member.
Absent Member.

Re: Archive Error 83

Hi Again,

the result looks like this:

383627 ITEM_RECORD check
Error 83- Item failed to archive
- Subject: $SUBJECT
- From: $ACCOUNT
- Date: Jul 28, 2011 - 12:45 pm
- First archive attempt date: Feb 20, 2014
- Number of archive attempts: 30
- Error number on last Archive attempt: 0xC050


There are 4117 occurrences like the one above. Only the "Number of archive attempts" varied from 1 to 30.

Cheers,
Pascal

"Have you tried turn it off and on again?"
0 Likes
Highlighted
Knowledge Partner
Knowledge Partner

Re: Archive Error 83

In article <bendeichp.6bjhnz@no-mx.forums.novell.com>, Bendeichp wrote:
> There are 4117 occurrences like the one above. Only the "Number of
> archive attempts" varied from 1 to 30.
>

The 'archive attempts' should increment on each attempt, so looking at
dates associated with the highest numbers, any recollection of what
happened about or just before then?

What is this user's archive folder set to? Make sure it is a real
place.

Running a GWCheck on the caching box isn't a bad idea, and the stand
alone GWCheck code is right there with the client executable as well.


Andy Konecny
Knowledge Partner (voluntary SysOp)
Konecny Consulting Inc. in Toronto

"Give more than others think is wise
Challenge yourself beyond what others think is right"
Michael 'Pinball' Clemens

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