WARNING: \\ hostname \sapmnt\trans\tmp\*. SID already in use (x)

Question

Hi everybody!!
Someone can help me about the next warning when I try to make a transport from QUA to PDC. The transport doesn't pass to PDC envionment.
Best Regards
The next is the warning:
STOP  tp_getprots          PRD P      20071010121848              PATROL       SAPPRD 20071010121834                                
STOP  MOVE NAMETABS        PRD 6      20071010121848              PATROL       SAPPRD 20071010121834                                
START MAIN IMPORT          PRD I      20071010121848              PATROL       SAPPRD 20071010121834                                
START imp single           PRD        20071010125935              PATROL       SAPPRD 20071010125934                                
INFO  TBATG CONVERSION OF  PRD N      not needed                  PATROL       SAPPRD 20071010125934                                
START MOVE NAMETABS        PRD 6      20071010125936              PATROL       SAPPRD 20071010125934                                
START tp_getprots          PRD P      20071010125937              PATROL       SAPPRD 20071010125934                                
STOP  tp_getprots          PRD P      20071010125947              PATROL       SAPPRD 20071010125934                                
STOP  MOVE NAMETABS        PRD 6      20071010125947              PATROL       SAPPRD 20071010125934                                
START MAIN IMPORT          PRD I      20071010125947              PATROL       SAPPRD 20071010125934                                
WARNING:
DEVZEUSUNE\sapmnt\trans\tmp\DEVKK954505.PRD is already in use (10), I'm waiting 4 sec (20071010130015). My name: pid 5316                                                                               
WARNING:
DEVZEUSUNE\sapmnt\trans\tmp\DEVKK954505.PRD is already in use (20), I'm waiting 1 sec (20071010130039). My name: pid 5316                                                                               
WARNING:
DEVZEUSUNE\sapmnt\trans\tmp\DEVKK954505.PRD is already in use (30), I'm waiting 4 sec (20071010130104). My name: pid 5316                                                                               
WARNING:
DEVZEUSUNE\sapmnt\trans\tmp\DEVKK954505.PRD is already in use (40), I'm waiting 2 sec (20071010130135). My name: pid 5316                                                                               
WARNING:
DEVZEUSUNE\sapmnt\trans\tmp\DEVKK954505.PRD is already in use (50), I'm waiting 2 sec (20071010130210). My name: pid 5316                                                                               
WARNING:
DEVZEUSUNE\sapmnt\trans\tmp\DEVKK954505.PRD is already in use (60), I'm waiting 1 sec (20071010130246). My name: pid 5316                                                                               
WARNING:
DEVZEUSUNE\sapmnt\trans\tmp\DEVKK954505.PRD is already in use (70), I'm waiting 4 sec (20071010130308). My name: pid 5316                                                                               
WARNING:
DEVZEUSUNE\sapmnt\trans\tmp\DEVKK954505.PRD is already in use (80), I'm waiting 1 sec (20071010130345). My name: pid 5316                                                                               
WARNING:
DEVZEUSUNE\sapmnt\trans\tmp\DEVKK954505.PRD is already in use (90), I'm waiting 5 sec (20071010130410). My name: pid 5316                                                                               
WARNING:
DEVZEUSUNE\sapmnt\trans\tmp\DEVKK954505.PRD is already in use (100), I'm waiting 3 sec (20071010130442). My name: pid 531                                                                               
WARNING:
DEVZEUSUNE\sapmnt\trans\tmp\DEVKK954505.PRD is already in use (110), I'm waiting 4 sec (20071010130512). My name: pid 531                                                                               
WARNING:
DEVZEUSUNE\sapmnt\trans\tmp\DEVKK954505.PRD is already in use (120), I'm waiting 3 sec (20071010130541). My name: pid 531                                                                               
WARNING:
DEVZEUSUNE\sapmnt\trans\tmp\DEVKK954505.PRD is already in use (130), I'm waiting 2 sec (20071010130612). My name: pid 531                                                                               
WARNING:
DEVZEUSUNE\sapmnt\trans\tmp\DEVKK954505.PRD is already in use (140), I'm waiting 2 sec (20071010130644). My name: pid 531
The PID makes a reference to the tp.exe process

Answer 1

Dear Friend
The transport buffer lock file (<SID>.LOB) remains locked by the operating system (OS). The file is created by tp.exe to prevent that several tp processes access simultaneously the transport buffer. The file is deleted after the tp has modified the transport buffer. As usual the <SID>.LOB is located in the
<hostname>\sapmnt\trans\tmp folder.
When the symptom occurs, the following records are written in the transport log file:
WARNING:
<hostname>\sapmnt\trans\tmp\<SID>.LOB is already in use
(XXX), I'm waiting 5 sec (20031209205043). My name: pid XXXX on YYYY.
Other terms
.LOB, opportunistic locking, lock, EnableOplocks, LanmanServer, Q296264 , already in use, semaphore
Reason and Prerequisites
The error in opportunistic locking agorithm leads to the blocked .LOB files. Before you proceed with the steps described  below,  make sure that you have installed the latest Windows Service Pack.
Solution
To check if the problem is caused by opportunistic locking do the following:
      1. Get the tp-process ID (PID) from content of the .LOB file.
      2. Check if the PID exists on the host where tp runs.
      If it exists, the problem is not the opportunistic locking but must be investigated by the support team.
      If the PID does not exists, perform the next step.
      3. Check with the command "net file" on the transport host if the network handle for .LOB file exists and delete it with "net file <file ID>  /close".
      4. Delete the .LOB file on the transport host. If the next call of tp creates a new .LOB file and will be blocked again with the  message " WARNING:
<hostname>\sapmnt\trans\tmp\ <SID>.LOB is already in use (XXX), I'm waiting 5 sec (20031209205043). My name: pid XXXX on YYYY. " perform the next step.
      5. Login to the last tp-run host with an user that differs from the tp-user and delete the .LOB file on the transport host via administrative share (<disk>$):
      del
hostname\d$\usr\sap\trans\tmp\<SID>.LOB
      After that the tp should run smoothly for some time.
If the symptoms in steps 1-5 have been verified and confirmed this is an indication for an opportunistic locking algorithm problem of the operating system. In this case, disable the opportunistic locking on the transport host by setting the registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\ Parameters
EnableOplocks to (REG_DWORD ) 0
(see also MS KB Q296264)
If the problem was not solved or any other side effects were detected, contact your Microsoft support team.
      6. After deactivating  the opportunistic locking you may experience some performance problems with tp - the transport requests are running, but it takes more time than usual. Especially elder SAP systems (before 6.10) are affected.
      Reason: Implementation of the C-runtime libraries and Windows text files.
      Buffered IO functions (fread, fwrite, fgets, fseek etc) in Windows C-runtime library use a file pointer to an internal buffer in which a part of the text file is cached in a local buffer. In the Windows text file every end of the line (EOF) is marked with the escape sequence "carriage return" (CR) and "line feed" (LF). The C-RTL buffer represents the line in C-Style (LF only). Therefore a conversion of the input stream when transfering data from the file to the buffer has to eliminate all CRs. As a result of this, fseek (function returning the actual position of the filepointer) could not resolve the position with the information held in the local buffer only. It has to access the file every time, whereas the other buffered function will mainly operate on the buffer only. Switching off Opportunistic Locking disables SMB client site caching of the file. Therefore every fseek() request will result in a not cached network operation to the file. This does not happen, if the Unix like style LF is only used for representing EOF. tp and all other R/3 programs handle both formats correctly.
      Solution: In  a time window where no transport activities are performed, open the buffer file with SAPPAD and choose "Tools -> Save As Unix File". Save the file and close SAPPAD. You have to repeat this every time the buffer file is newly created
shailesh Tiwari