Microsoft Knowledge Base Article
This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved.
Terms
of Use |
Trademarks
Article ID: 821127 - Last Review: June 10, 2003 - Revision: 1.3
PRB: Cleanup of Temporary File is Unsuccessful After a File Rename Conflict from $0$.$r$ Temporary Files in The Same Session
SYMPTOMS
With Application Center 2000 replication, although it is possible
to simultaneously replicate two identical files (that is, two files with the same file names) in two separate applications in Application Center 2000, the
second replication operation is unsuccessful because the file is in use.
The second
replication file is then renamed to $0$.$r$ in the temporary folder where
Application Center 2000 stores files before applying them to the file system
($ACSRPL$). Additional files will be incremented in number when they are named (for example, $
0$.$r$,
$
1$.$r$). You will see an error similar to the following on the cluster
member:
Severity: 1
TimeGenerated: 3/29/2003
5:38:45 PM
Server: SMXSPBVT06D
Category: Replication
EventID:
5079
LongMessage - Synchronization could not rename file Application
Center Synchronization could not rename the file
D:\MetabaseRepl-MBAutoSyncApp-{49C4-F8AE}\GIF_file00006.GIF for session
CLSTTESTCLUST and job SMXSPBVT05DX1017452204X665177X11dd190. Status is
0x800700b7 Cannot create a file when that file already exists.
CAUSE
This problem occurs because the file is replicated two times in the same automatic session,
and a conflict occurs when the file is renamed from the $ACSRPL$
directory.
RESOLUTION
To resolve this issue, complete a full synchronization. The temporary files are removed from the $ACSRPL$
directory only after the full synchronization is complete. Although you can remove these files
manually, it is recommended that you remove them by means of a full synchronization.
APPLIES TO
- Microsoft Application Center 2000 Standard Edition
- Microsoft Application Center 2000 Service Pack 2
Community Feedback System
Very often, it takes hours to solve a problem. Very often, you've looked high
and low, and have tried a lot of solutions. When you finally found it, chances
are, it was because someone else helped you. Here's your chance to give back.
Use our community feedback tool to let others know what worked for you and what
didn't.
Please also understand that the community feedback system is not warranted to be
correct, it's simply a system that we've built to let people try and help each
other. If something in a feedback response doesn't make sense to you, or you're
not comfortable making changes that the feedback talks about (like registry
edits), please consult a professional.
Thank you for using kbAlertz.com Feedback System.
-- Scott Cate
Be the first to leave feedback, to help others about this knowledge base
article.
(Optional) Name
(Optional)
Public URL Or Email
Comments
No
HTML -- Text Only Please