PRB: Cleanup of Temporary File is Unsuccessful After a File Rename Conflict from $0$.$r$ Temporary Files in The Same Session (821127)
The information in this article applies to:
- Microsoft Application Center 2000
- Microsoft Application Center 2000 SP1
- Microsoft Application Center 2000 SP2
SYMPTOMSWith 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.
CAUSEThis 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.RESOLUTIONTo 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.
| Modification Type: | Major | Last Reviewed: | 6/10/2003 |
|---|
| Keywords: | kbprb KB821127 kbAudDeveloper |
|---|
|