| Hello Ching-U.
I am responsible for housekeeping in general, but this looks like a
specific problem with archiving, so I got some suggestions from the
resident archiving guru.
. first, can you confirm that this is V2.4? (or earlier).
. if V2.4, then lots of NEWDIRing was used and this error is probably
coming out when the archiving is finished and the job tries to NEWDIR
back into the Manager account. Is there any reason why this might not
be possible? Someone logged into Manager account?
. this is unlikely to be a serious problem, and we think that the
archiving has completed successfully.
. it may well be a 'problem' in V2.4
Cheers
DaveT
|
| Hello Ching-U.
I am unable to replicate this on our V2.4 system here. There is the
possibility that there is something wrong with the Manager's profile
entry on your system, but without checking the system itself, I can't
be sure.
I think that the best place to start looking further is in
OA$DO:ARCHIVE_SYS_USER_FOLDERS.SCP. You could set up an archive run,
limited to very few users, e.g in one Department (set the field in their
Profiles) and few folders. Then you could possibly Set Trace on this
script, sending the trace output to a log file. This might display
where exactly this error message is coming from.
Either way, I think the archiving is completing successfully.
Sorry I can't help further.
DaveT
|