Newbie - Problems/questions with UploadContent method

Hi Folks. I'm having trouble uploading a small PDF document into ECM. The document content is successfully created, however, the file appears to be corrupt when I try to open it in ECM (or even if I first download it and then open it). Here's by C# code below:

string contextId = docMan.CreateDocumentContext(OtAuth, destNode.ID, sessionProperties.FileName, FileComment, false, null);

resultsMessage += Environment.NewLine + string.Format("Successfully created docuemnt context. Size of file as bytes is: {0}", fileAsBytes.Length);

Stream fs = new MemoryStream(fileAsBytes);

resultsMessage += Environment.NewLine + string.Format("Converted the byte array into a file stream of size {0}. About to upload the content...", fs.Length);

contentService.UploadContent(ContentAuthentication, contextId, uploadFileAttributes, fs);

When I go into ECM and try to open the file, here's the error I'm getting:

Also, here's my binding configuration to connect to the ContentService:

<binding name="ContentServiceBinding" closeTimeout="00:05:00"

openTimeout="00:05:00" receiveTimeout="00:10:00" sendTimeout="00:05:00"

allowCookies="false" bypassProxyOnLocal="false" hostNameComparisonMode="StrongWildcard"

maxBufferSize="2147483647" maxBufferPoolSize="524288" maxReceivedMessageSize="2147483647"

messageEncoding="Mtom" transferMode="Streamed"

useDefaultWebProxy="true">

Can someone tell me what I'm doing wrong?

Thanks in advance!

- Dylan

Find more posts tagged with

Comments

Guy_Pomerleau

Why using uploadcontent. I think most poeple use : documentmanagement, espacially if you have small doc. To my knowledge, uploadcontent is mainly use for large file. Other might confirmed.

Jason_Smith

From what I can see, your code looks ok to me. Does this happen for any file you try to upload or just this one? Hard to say what the problem is without a little more information.

And to comment on Guy's post:

You are correct that you can just use the DocumentManagement service to upload smaller documents (the limits depend on how you have CWS configured on both the client and the server). However, the ContentService should work for documents of any size (possibly up to a configured maximum size).

Dylan_Milks

Yes, this problem happens with any type of file and file size. As I've been testing, I"ve been using small PDF documents, like between 10 KB and 50 KB.

Also note that when i go into the properties of the file in ECM, and look at the Specific tab, the MIME Type says "application/pdf" - which is correct. So I don't think it's an encoding issue.

Any other thoughts or ideas as to what could be wrong? (as a test, I will use the CreateDocument method intead just to seeif it works)

Jason_Smith

Encoding was the next thing I was wondering about. The MIME type detection is likely being set based on the mime.types file, so if your document name has .pdf it would set the MIME type to application/pdf. You can confirm your MIME type detection settings in the Admin pages (func=admin.MIMETypeDetection).

What version/update of Content Server are you using? Also, what is the encoding setting for CWS set to on the server?

Jason_Smith

Also, have you tried running through the sample code for uploading a document?

The sample is located here:

https://knowledge.opentext.com/knowledge/cs.dll/Open/30854542