Hi,
When I am loading a document from the client to the server, I am getting "Could not write bytes to socket" errror. Can you please help?
Thanks
Hi, Ghasem.
Check your Livelink/Content Server thread logs to see if there is an error message there. Unforunately, there are cases where an error occurs when uploading content resulting in the "Could not write bytes to socket" error, making the Content Server error unavailable.
Common problems are that a document with the same name already exists, or the specific container doesn't exist.
Thanks,
Scott
Hi Scott,
When I take the error,Thread logs are appearing,but I can't solve the logs.
Can you help about this issue?
Make sure that you have Debug=2 set in the opentext.ini. In the thread?.out files, you should be able to see each web service request. If you search for UploadContent (I think that's the method you're using) you should be able to see the error that is being produced. Also, the string "InvokeService" is good for identifying web service requests.
Having the same problem. When file already exists and invoke the ContentService UploadContent method we will get one of two different errors returned from EWS:
1. Dispatched service DocumentManagement threw exception DocMan.Error : An item with the name 'filename3.doc' already exists. (this is the error we want). 2. Could not write bytes to socket (this is the error we get about half the time, but there is no discernible pattern).
Opened a ticket and got this response from support:
Dave, one of our escalation team members ran this by our developers and found out that we have bug LESAPI-169 open for this. The size of the file seems to affect it, and documents larger than 10K seem to trigger the "unable to write bytes to socket" error.
There is no fix yet unfortunately, but I have added you to the bug. As a workaround our devs have suggested to check to see if a file exists before uploading.
I did add some code to check for an existing file, and that has "fixed" the problem, but this is definitely a bug OT should correct. One other note, the file size doesn't seem to matter as files larger or smaller than 10K get the socket error too.
We are getting the same error, even when we try and upload with a user that has no rights to said folder. does anyone know if this has been fixed?
thanks
Zak
The fix for this issue should be available in the next patch. Jason
Let me clarify that. It will be available in the patch after the upcoming cumulative patch. Jason
Hi Jason,
Do you have the patch fix for this issue? I am facing the same issue while uploading specific documents. Please help here.
Kreepa
