Hi, I have this odd error uploading a file from a ll971 server toa  cs10 one. This operation tranfers the file with it's intact audit; so  I have to proceed with an impersonnation token before starting my  operation. This error happends on 2 of 4000 files I am trying to migrate. 
  Here is a snippet of my code:
  attach =  cs971.fDocManService.GetVersionContents(cs971.fDocManAuthentication,  SourceNode.ID, OneVersion.Number); // Version = 0 will return the  latest version
    ContentService10.FileAtts fileAtts = new  ContentService10.FileAtts()
        fileAtts.CreatedDate = OneVersion.CreateDate;
       fileAtts.FileName =  OneVersion.Name;
      fileAtts.FileSize =  OneVersion.FileDataSize;
       fileAtts.ModifiedDate = OneVersion.ModifyDate;
      fileAtts.FileName = OneVersion.Filename;
  ** ERror**  Executing ...        Stream theContent = new MemoryStream(attach.Contents);
  **  error**     newNodeID =  fContentService.UploadContent(ref fContentAuthentication, contextID,  fileAtts, theContent);
  docId = int.Parse(newNodeID);
  //Where I have put the ** is where the exception is trown; but by the  les service. Going to the LES service logs I see the following...
   using authentication service for impersonnating as a  user. another.Here is the partial lapi logs from the server it's  executing on (The destination server, not the source)
  2012-07-19 09:28:05,5513 INFO [5] Content Web Services 10.0.4 File  Version: 10.0.4.1390
  2012-07-19 09:28:05,5513 INFO [5] OS  Version: Microsoft Windows NT 6.1.7601 Service Pack 1
  2012-07-19 09:28:05,5513 INFO [5] CLR Version: 2.0.50727.5448
  2012-07-19 09:28:05,5513 INFO [5] Machine Name: xxxx
  2012-07-19  09:28:05,5825 INFO [5] User Domain: ****
  2012-07-19  09:28:05,6138 INFO [5] User Name: xxxxx
  2012-07-19  09:28:05,6138 INFO [5] Command Line:  c:\windows\system32\inetsrv\w3wp.exe -ap  "les-content-services" -v "v2.0" -l  "webengine4.dll" -a  \\.\pipe\iisipm5e9e3bcb-7239-49f2-a336-576019c41a68 -h  "C:\inetpub\temp\apppools\les-content-services\les-content-services.config"  -w "" -m 0 -t 20
  2012-07-19 09:28:05,6138 INFO [5]  Culture: en-US
  2012-07-19 09:28:05,6138 INFO [5]  ---------------
  2012-07-19 09:32:14,7429 WARN [7] Livelink  error occurred
  2012-07-19 09:32:14,7429 WARN [7]    Status: 903101
  2012-07-19 09:32:14,7429 WARN [7]    Error Code: Core.DispatchedServiceThrewException
  2012-07-19  09:32:14,7429 WARN [7]   Error Message: Dispatched service  DocumentManagement threw exception ? : ? <-- ***** THIS ERROR SUCKS  *** 
  2012-07-19 09:32:14,7429 WARN [7]    ApiError:
  2012-07-19 09:37:08,7761 WARN [12] Livelink error  occurred
  2012-07-19 09:37:08,7761 WARN [12]   Status:  903101
  2012-07-19 09:37:08,7761 WARN [12]   Error  Code: Core.DispatchedServiceThrewException
  2012-07-19  09:37:08,7761 WARN [12]   Error Message: Dispatched service  DocumentManagement threw exception ? : ? <-- *****
  2012-07-19 09:37:08,7761 WARN [12]   ApiError:
  2012-07-19 09:44:39,9382 WARN [12] Livelink error occurred
  2012-07-19 09:44:39,9382 WARN [12]   Status: 903101
  2012-07-19 09:44:39,9382 WARN [12]   Error Code:  Core.DispatchedServiceThrewException
  2012-07-19 09:44:39,9382  WARN [12]   Error Message: Dispatched service  DocumentManagement threw exception ? : ? <-- *****
  2012-07-19 09:44:39,9382 WARN [12]   ApiError:
  2012-07-19 10:05:05,8838 INFO [9] ---------------
  2012-07-19  10:05:05,8838 INFO [9] Application shutdown
  2012-07-19  10:05:05,8838 INFO [9] --------------- ... I
  I ran it three times.... Permissions are right, the the  providerdata and the dversdata entries seem ok ... Both versions from  the file are retrievable by the GUI (?func=ll) in the source system.
   Obviously this is a very vague error ... so here are the full  lapi log error tags...
  If I enable the full lapi logs; here if the error that gets my  attention...
  Extra input data left on socket (63266 bytes) Thu  Jul 19 13:37:33 2012 - 126803    Func='lapi.InvokeService:ContentService.UploadContent()'       Timing:     2.328 2.321 2.328
  Now the DAT file is the good size on the SAN; the dversdata.size is  correct, and it's displayed right in the source GUI (62kb)
  ... I have sent the file to email support and they affirm that they  can retreive and copy the file using this call...
                           string filePath =  @C:\temp\xxxxxx-109291_93b2996b-f052-499d-833d-4cab056fedeb.html;
                           FileInfo fi = new FileInfo(filePath);
                           FileStream fs = new FileStream(filePath, FileMode.Open,  FileAccess.Read);
                          ContentService.FileAtts fa = new ContentService.FileAtts();
                            // Store file attributes for the document
                           fa.CreatedDate = fi.CreationTime;
                           fa.ModifiedDate = fi.LastWriteTime;
                           fa.FileName = fi.Name;
                           fa.FileSize = fi.Length;
  I suspect storage to be an issue; but I have no clue !!! HElp 