Add document from file system to Livelink.

We at Brunei Shell Petroleum are also facing same issue with Livelink 9.1 in Windows 2000/Oracle env. This is been happening for quiet sometime (atleast few months). Normally, user will select a document and will upload to livelink. Most of the time it works as intented. But in those unique occurences, the file uploaded to livelink will be normally drastically big or small in size to that of original file and scrambled. We also found following facts while digging a little bit:1. The corrupted documents' size in Livelink are multiple of 320 kbytes (for ex. 320k, 640k, 960k and so on). 2. The file is corrupted when it reaches the Windows Temp directory of the Server where Livelink is installed.3. We ran FileMon utility in winnt\temp dir and found out that none other than livelink.exe and llserver.exe WRITES to files.To check the corruption, we have developed a MSAccess query that finds all those or atleast 70%-80% of the corruption by going thru livelink database.Anyone else, has this issue or got it solved somehow?

We had the same problem with livelink 9.1 in windows 2000. Is it possible to have a validity check (maybe in the next patch) that will function as follows:after adding/returning the document to livelink, this latter shall verify the size of the deposited document versus the size of the original document (in the temp directory of the user) before deleting it.such checking will save us lots of time spent these days checking all the documents, running queries, etc., to make sure we dont have this case anymore.

Here is the problem. If a large document is being saved to Livelink the server requires the document to save it into Livelink. (A slow network connection helps with this problem.)The temporary location for download is c:\winnt\temp with the file name starting with ll*.If the download times out due to the CGI timeout, the temporary file name remains. These name are recycled. If a new document uses the same temp name the file is not overwritten. The corrupted file can be repeated too many locations. It seems at random.Write a batch file and schedule a deletion for every day off hours.(IE download at a 320 KB per second blocks.)