ADSM-L

Re: Journal Service Return Codes

2003-01-22 09:55:30
Subject: Re: Journal Service Return Codes
From: Pete Tanenhaus <tanenhau AT US.IBM DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Wed, 22 Jan 2003 09:54:23 -0500
The error occurs when the journal daemon is processing a change
notification of an object and attempts to obtain
the object's timestamp.

The timestamp is obtained using the Win32 FindFirstFile api, which is the
programmatic equivalent of a user obtaining
the properties of the object in Windows explorer.

While it is unusual for a service running under the local system account
being denied access to an object it, it  isn't
impossible.

A very restrictive security permission may be placed on the object (source
of the rc=5 Access Denied Error), or another process may
open the object exclusively for read, write, and property viewing (source
of the rc=32 sharing violation).

Each non-delete journal entry must contain the file system timestamp of the
object to maintain the integrity of the journal, which
is why an object which causes this error can't be added.

Hope this answers your question ....


Pete Tanenhaus
Tivoli Storage Solutions Software Development
email: tanenhau AT us.ibm DOT com
tieline: 320.8778, external: 607.754.4213

"Those who refuse to challenge authority are condemned to conform to it"

---------------------- Forwarded by Pete Tanenhaus/San Jose/IBM on
01/22/2003 09:44 AM ---------------------------

"Loon, E.J. van - SPLXM" <Eric-van.Loon AT KLM DOT COM>@VM.MARIST.EDU> on
01/22/2003 05:17:21 AM

Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>

Sent by:    "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>


To:    ADSM-L AT VM.MARIST DOT EDU
cc:
Subject:    Re: Journal Service Return Codes



Hi Nancy!
The return codes are Windows OS return codes. I found them some time ago in
a file that came with some Windows source coding. I think Microsoft has
them
online somewhere too.
RC=5 means "access is denied" and RC=32 means "The process cannot access
the
file because it is being used by another process".
The RC=5 is strange. If you are using an administrative account it should
have access to all files.
Kindest regards,
Eric van Loon
KLM Royal Dutch Airlines

-----Original Message-----
From: Nancy R. Brizuela [mailto:Brizuela AT UWYO DOT EDU]
Sent: Tuesday, January 21, 2003 23:48
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Journal Service Return Codes


All,

We are receiving the below error messages in our jbberror.log.  What do
these RC's mean and where does one find the documentation on these RC's?

 FindFirstFile(F:\Test\o\ORANGE3\Application Data\Microsoft\Internet
Explorer\Quick Launch): RC=5
01/13/2003 15:34:22 psMonitorThread(tid 1728): Object
'F:\Test\o\ORANGE3\Application Data\Microsoft\Internet Explorer\Quick
Launch' skipped,will not be added to the journal.
01/13/2003 16:18:55 psMonitorThread(tid 1836):
FindFirstFile(E:\Test\b\BARGE\APPLIC~1\MICROS~1\Windows\Themes): RC=32
01/13/2003 16:18:55 psMonitorThread(tid 1836): Object
'E:\Test\b\BARGE\APPLIC~1\MICROS~1\Windows\Themes' skipped,will not be
added to the journal.
01/13/2003 16:19:06 psMonitorThread(tid 1836):
FindFirstFile(E:\Test\b\BATTA\Personal\MYWEBS~1\myweb3\_themes\_vti_cnf)
: RC=32

Thanks,

Nancy Brizuela
University of Wyoming
IBM Systems Group
Ivinson Room 238
(307)766-2958


**********************************************************************
For information, services and offers, please visit our web site:
http://www.klm.com. This e-mail and any attachment may contain confidential
and privileged material intended for the addressee only. If you are not the
addressee, you are notified that no part of the e-mail or any attachment
may be disclosed, copied or distributed, and that any other action related
to this e-mail or attachment is strictly prohibited, and may be unlawful.
If you have received this e-mail by error, please notify the sender
immediately by return e-mail, and delete this message. Koninklijke
Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees
shall not be liable for the incorrect or incomplete transmission of this
e-mail or any attachments, nor responsible for any delay in receipt.
 **********************************************************************

<Prev in Thread] Current Thread [Next in Thread>