DocumentManagement Service - CreateDocument throws exception 'Error adding version to...'

I'm new to the Livelink API and generally it seems straight-foward. In my .Net 3.5 application (C#) I've created service clients for the 9.7.1 services (Authentication, Document Management, etc.) and have been consuming the results in a small test application I've made (since the LLTreeView sample app is out-of-date).

My issue is that when I use the Document Management service's [CreateDocument] method it returns a FaultException stating ' Error adding version to {0}', where {0} is the filename of the document I'm requesting to be created/uploaded.

I understand this question has been asked several times before but it doesn't appear that anyone has ever posted a resolution to this item?

Alternatively I tried using the DocumentManagement service in tandem with the Content service to first create the document context (the [CreateDocumentContext] method) and then upload the content (the [UploadContent method]) -- This also was not successful. In this case I was greeted with a internal server exception of the following:

[WebException: The remote server returned an error: (500) Internal Server Error.]
System.Net.HttpWebRequest.GetResponse() +5314029
System.ServiceModel.Channels.HttpChannelRequest.WaitForReply(TimeSpan timeout) +54

[ProtocolException: The content type multipart/related; type="application/xop+xml";start="< http://tempuri.org/0>";boundary="uuid:b97d0087-f5ae-4cfc-afae-350e159e1a4d+id=6";start-info="text/xml " of the response message does not match the content type of the binding (text/xml; charset=utf-8). If using a custom encoder, be sure that the IsContentTypeSupported method is implemented properly. The first 609 bytes of the response were: '
--uuid:b97d0087-f5ae-4cfc-afae-350e159e1a4d+id=6
Content-ID: < http://tempuri.org/0 >
Content-Transfer-Encoding: 8bit
Content-Type: application/xop+xml;charset=utf-8;type="text/xml"

If neither of these methods work is not being to save binary content through the services indicative or a configuration problem with the server? Are there any suggestions that the, expert users or otherwise, can provide to help me resolve the issue? Any assistance would be appreciated.

Find more posts tagged with

Comments

Kapil_Chaudhari

Hi Chris,

I used to get "Cannot write bytes to Socket " error when I tried uploading a file. I came across another thread which mentioned that the fix will be available in next cumulative patch. Since, we can't wait until that long, I opened a ticket with customer service and they have provided a small hotfix. That hotfix worked partly as I can only upload files smaller than 10MB and can't upload files larger than 10MB.

When I try uploading a file larger than 10MB, I used to get "Error adding version to .." exception. But, now I am gettig the internal server error [500]. The ticket is still active and I will update this thread if I fix all the issues.

Thanks,

Kapil

Kapil_Chaudhari

Hi Chris,

I am still working with support to resolve the similar issue. Were you able to fix it?

Thanks,

Kapil

Eamon_Woortman

Hello,

I am also having the same problem when uploading file above 10 mb.
Currently I am using Python to send raw http requests to the server and when uploading, I send it in a chunked format, like the example application would.
I have also tried to use the soap interface of python, but that actually sends the content in the soap body(in <contents/>). This results in a different error.

Increasing httpRuntime's maxRequestLength or executionTimeout in web.config does not change anything.

When uploading a file which is larger than 10 mb on the livelink web interface, I get the following error:

Content Server Error: Error adding new item.
[Error adding version to '16385kb.txt'.
Could not close stream cursor.]

Is there someone from OpenText which can help us with this problem ?

Eamon Woortman
Maintainet AG

Kyle_Swidrovich

If you're using IIS 7.x under Windows Server 2008, you may have a problem when file sizes are over 30 MB, depending on your method for uploading. This is due to Request Filtering in this version of IIS.

You can either remove the RequestFiltering role in the Server Manager or reconfigure RequestFiltering to allow a larger file upload size.

This also applies to uploads done outside APIs, through the standard browser GUI to Content Server.

Eamon_Woortman

Hello Kyle,

I have tried to change the web.config for both les-services and the cgi folder like this:

    <system.webServer>
    <security>
        <requestFiltering>
            <requestLimits maxAllowedContentLength="2072576000"/>
        </requestFiltering>
    </security>
    </system.webServer>

    <system.web>
    <httpRuntime maxRequestLength="24192" />
    </system.web>

However, I am still receiving the 'Error adding version to x', 'couldn't close stream' error.
Strangly, the upload did work once after a config change, but the next failed again.

I was not able to remove the requestfilter role without removing ASP and some other required roles aswell.

Is this really an IIS issue, or just a livelink bug ?
What can I do to get more debug information ?

On a side note, the file I am uploading has a size of +- 17 mb.
I am using the CreateNodeAndVersionContext method plus UploadContent in HTTP mode.

With kind regards,

Eamon Woortman

Eamon_Woortman

In my case, there was something wrong with the configuration of the Livelink IIS Site.
Unfortunatly I have not yet discovered what went wrong, but all new installations seem to work fine.

Good luck with your issue.

Kapil_Chaudhari

We have JAVA webservices and we get this 'Error adding version to ..' error sometimes. It is very inconsistent. One of our application team can upload only text files successfully. When they try other files, same error is returned and we are unable to find the root-cause of this.

Anybody have JAVA webservice and got rid of this problem successfully?

Kapil_Chaudhari

In case of JAVA webservice client, UploadContent expects datahandler. DataHandler has 2 constructors. One takes a string and another takes DataSource object. When we used the first one with the string, it only let us upload .txt files and we used to get "Error adding version to ****" for other file types. After changing it to the second constructor with DataSource, the error went away and we are now able to upload all other files types without any error.

The error is misleading and kind of generic which can be thrown due to many reasons.

Kapil

Nitika_Mittu

Hi All.. We are also using CreateDocument and UploadDocument methods of CWS web services. However, we are getting exceptions 'Error adding version to {filename}'. Error creating file on the Archive Server.' even with files < 1 MB

Could anyone please share the sample CreateDocument and UploadDocument SOAP UI payloads. If anyone able to resolve the above issue at their end..please share the updates.

Thanks!

Saravanan_Gurusamy

We used to get this error when the Buffer is full. If that is the case , purging the buffer would fix the issue.