Rainer,
Thank you sir!
I see that my search was too narrow. I looked up the error, not the file. I
assumed that files were of value.
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Rainer Schöpf
Sent: Monday, October 12, 2009 3:17 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] BA Client error - CreateFile() returned '5'
Hello,
I encountered the same problem a while ago. Searching for "security.config.cch
backup" with Google shows that this is a common problem.
I suspect that these files are locked or have even been deleted while locked/in
use by another process.
As per Microsoft Knowledge Base,
"The files that have the extension .cch are dynamically generated and do not
have to be backed up or restored."
http://support.microsoft.com/default.aspx?scid=kb;en-us;815168
Rainer Schöpf
____________________________________________________________________________________
On Mon, 12 Oct 2009 at 14:31 -0400, Huebschman, George J. wrote:
> Hello everyone, I am trying to track down a client backup error.
>
> TSM Server 5.5.1, AIX 5.3.0.0
> TSM ba Client 5.5.1.0, Win2K3 R2 SP2 - The server is part of an HP >
> Polyserver cluster. We have excluded the Polyserve related mountpoints.
> We have not edited the registry.
>
> I am trying to figure out if the error I see is caused by the
> same root problem as mentioned in IC 56269.
> My error:
> 10/12/2009 00:12:04 ANS5250E An unexpected error was
> encountered.
> TSM function name : NTSecurityReadV2
> TSM function : CreateFile() returned '5' for file
> 'C:\WINDOWS\microsoft.net\Framework64\v2.0.50727\CONFIG\security.config.
> cch.6528.2904562'
>
> ----------------------------------------------------------
>
> - IC 56269 describes this error -
> "The TSM Backup-Archive client reports the following error during > backup
> in some cases:
> ANS1228E Sending of object 'filename' failed > ANS4007E Error processing
> 'filename': access to the object is > denied > In this case, the error
> happened on all objects when backing up > a EMC NAS share mounted in
> read-only mode through CIFS."
>
> ----------------------------------------------------------
>
> This error message is different.
> The file is not a CIFS share, but in on the C: drive.
>
> However, the details of IC56269 describe a problem with the value for >
> dwDesiredAccess that is passed to the MS API function "CreateFile()".
> The value TSM uses is for a Read/Write operation, could result in >
> CreateFile() returning an > access denied error incorrectly. MS recommends
> a different value that > only request Read access.
>
> ----------------------------------------------------------
>
>
> ?? Is this the same issue, or should I open a case with IBM?
>
> George Huebschman
> Legg Mason
>
> IMPORTANT: E-mail sent through the Internet is not secure. Legg Mason
> therefore recommends that you do not send any confidential or sensitive
> information to us via electronic mail, including social security numbers,
> account numbers, or personal identification numbers. Delivery, and or timely
> delivery of Internet mail is not guaranteed. Legg Mason therefore recommends
> that you do not send time sensitive > or action-oriented messages to us via
> electronic mail.
>
> This message is intended for the addressee only and may contain privileged
> or confidential information. Unless you are the intended recipient, you may
> not use, copy or disclose to anyone any information contained in this
> message. If you have received this message in error, please notify the
> author by replying to this message and then kindly delete the message. Thank
> you.
>
IMPORTANT: E-mail sent through the Internet is not secure. Legg Mason
therefore recommends that you do not send any confidential or sensitive
information to us via electronic mail, including social security numbers,
account numbers, or personal identification numbers. Delivery, and or timely
delivery of Internet mail is not guaranteed. Legg Mason therefore recommends
that you do not send time sensitive
or action-oriented messages to us via electronic mail.
This message is intended for the addressee only and may contain privileged or
confidential information. Unless you are the intended recipient, you may not
use, copy or disclose to anyone any information contained in this message. If
you have received this message in error, please notify the author by replying
to this message and then kindly delete the message. Thank you.
|