CreateDocument error

Hi,

I am trying to create a document through asp.net c# with the LL web service.

I keep getting this error -- DocumentManagement.CreateDocument() failed on the Livelink Server. No results were returned. Check the Livelink Server thread logs.

I can easily create a folder, but it always fails on creating a document. I removed the categories on the parent folder, and it still doesn't work, but ultimately I will want to add the categories back in. I've attached the trace log for reference. Here is my code:

Authentication authService = new Authentication ();

DocumentManagement dm = new DocumentManagement ();

OTAuthentication auth = new OTAuthentication ();

string authToken = authService.AuthenticateUser( "ECwebservicesuser" , "Testecm123" );

auth.AuthenticationToken = authToken;

dm.OTAuthenticationValue = auth;

string projectnumber = "newfolder10" ;

string incidentid = "1" ;

dm.CreateFolder(13064258, projectnumber, null , null );

Node p = dm.GetNodeByName(13064258, projectnumber);

dm.CreateFolder(p.ID, incidentid, null , null );

Node q = dm.GetNodeByName(p.ID, incidentid);

Attachment data = new Attachment ();

data.FileName = Request.PhysicalApplicationPath + "documents\\Class1.cs" ;

data.CreatedDate = DateTime .Now;

dm.CreateDocument(q.ID, "name" , "comments" , false , null , data);

Find more posts tagged with

Comments

Kyle_Swidrovich

Hi Josephine,

Note the top stack frame in the trace file you attached:

Frame:     49FE1E88 NodeCreateAttributes (0)
   ObjRef: #97000567.'NodeCreateAttributes'
   PC:      338
   Line:    95:95
   NStkVal: 2
   NLocals: 11
   NArgs:   3
   Stack:   SP-1 = 'remoteCache'
   Stack:   SP-2 = ?

This indicates that the creation attempt failed within the NodeCreateAttributes script of the object #97000567. On the stack, we see a reference to "remoteCache".

Can you look at the thread log and find the line containing "Root: #97"?

Josephine_Bush

Hi,

I found a line in the threads that has this info and have attached it for your review.

Many thanks,

Josephine

Kyle_Swidrovich

Thanks Josephine.

From the thread log, we can see this line referring to the #97 Ospace:

#OSpace: bravaredact Root: #97000001 File: \OPENTEXT\module\bravaredact_6_2_0\ospace\bravar Size: 305920

This is the Ospace that the #97000567 object in the trace file belongs to.
In other words, the "bravaredact" module is where the code is failing.

I believe this is the Brava product by Informative Graphics.
Aside from ensuring that you're fully patched for that product, Informative Graphics will probably need to look into this problem.

I believe OpenText provides front-line support for that product, so I would suggest opening a support ticket with us after ensuring you're fully patched.

Josephine_Bush

Many thanks for this info!

Josephine_Bush

Hi again,

We updated the Brava module and I am getting a different error now.

"Error adding version to 'name'."

I am using the same code from the 1st post.

Thank you,
Josephine

Kyle_Swidrovich

Hi Josephine,

Where is this error being reported from?
What property of the exception are you pulling?

If you examine the other properties of the exception in detail, are you seeing any additional information?

If not, a review of the Content Server thread / connect logs may be necessary to know why the error is occurring.

Cheers,
Kyle

Josephine_Bush

Hi,

This is a visual studio error message - I've attached a screenshot.

I've also attached a thread log -- is there something I could be looking for in the thread log since I am not sure what to be looking for.

Many thanks,
Josephine

Kyle_Swidrovich

Quoted josephine.bush@res-americas.com on 2012-02-09 16:43:

Hi,

This is a visual studio error message - I've attached a screenshot.

I've also attached a thread log -- is there something I could be looking for in the thread log since I am not sure what to be looking for.

Many thanks,
Josephine

Hi Josephine,

I would recommend that you catch the thrown exception around your CreateDocument call and inspect each of the exception's properties for more information.

The thread log we'd be interested in would contain an "InvokeService" call with the "CreateDocument" included somewhere in the request. The particular thread you provided only contains an "index.update" call, which is the Extractor used for indexing.

You may also want to include wantLAPILogs=TRUE in the [options] section of the opentext.ini of the instance (stop/restart the services when making these changes) to ensure that all possible detail about the request is included in the thread log.

Regards,
Kyle

Josephine_Bush

Hi,

I found an error in the thread logs for CreateDocument:

Error Code: DocMan.Error
Error Message: Error adding version to 'name'.
Error Details
- Error executing an Sql statement.

I've attached the thread log that contains the above error. I found this info on line 5521.

I tried to catch the exception in VS, but only got null values on the inner exception.

Many thanks,
Josephine

Appu_Nair

Now do you run this with debug=2 ,wantlogs=true,wantlapilogs=true then if so you might have a connect log.That might tell Kyle or people using this thread a little more info.Are you able to do this in the GUI as if your program is adding the file .Is your livelink content on EFS or archive and is all that working corrcetly?Several times ppeople install modules in livelink without creating some required schema.Livelink code will then check for that and run into those errors.The best way is to try to add something thru the webgui to rule out core livelink problems.

72
BANANAPIE
***GetNode [new document] id:12747919 subtype:144
Saving 12747919
PRF - in CBMovePre
PRF - in CBMove
PRF - in CBMovePost
-72
CollectionsUtils.RemoveFromAllCollections: Removed item 12747919 from 0 collections
Service error occured
Error Code: DocMan.NodeCreationError
Error Message: Error adding version to 'new document'.
Error Details
- Error executing an Sql statement.
[APIDispatchCBScript.Execute] was called

Josephine_Bush

Hi,

I forgot to attach the connect log in the last post.

Also, creating documents through the webgui is working fine.

Thanks,
Josephine

Kyle_Swidrovich

Hi Josephine,

In the connect log (which logs database activity), we can see the problematic SQL:

02/09/2012 11:15:06 [0908722769] 0000290417: KSqlCursor::Open(2000,'insert into DVersData ( VersionID,DocID,Version,VersionName,Owner,VerCDate,VerMDate,Platform,FileName,DataSize,FileType,FileCreator,FileCDate,FileMDate,Icon,ProviderId,VerComment,Locked,LockedBy,LockedDate,Indexed,FinderFlags,MimeType,VerType,VerMajor,VerMinor,ResSize ) values (:A0,:A1,:A2,:A3,:A4,:A5,:A6,:A7,:A8,:A9,:A10,:A11,:A12,:A13,:A14,:A15,:A16,:A17,:A18,:A19,:A20,:A21,:A22,:A23,:A24,:A25,:A26)') -->'SUCCESS'
02/09/2012 11:15:06 [0908722891] 0000290418: KSqlCursor::Prepare() --> 'SUCCESS'
02/09/2012 11:15:06 [0908723619] 0000290419: KSqlCursor::Bind(27,{12747919,12747919,1,'1',12748027,D/2012/2/9:11:15:7,D/2012/2/9:11:15:7,2,'Class1.cs',L0,'CS',?,D/2012/2/9:11:15:4,D/1/1/1:0:0:0,?,12747919,?,0,?,?,0,0,?,?,0,1,?}) --> 'SUCCESS'
02/09/2012 11:15:06 [0908723788] 0000290420: ODBC diagnostic error: 1 ODBC error code: 0 ODBC state: 22008 ODBC error: [Microsoft][ODBC SQL Server Driver]Datetime field overflow
02/09/2012 11:15:06 [0908723834] 0000290421: KSqlCursor::Execute() --> 'Could not execute cursor.'
02/09/2012 11:15:06 [0908723895] 0000290422: KSqlCursor::Close() --> 'SUCCESS'
02/09/2012 11:15:06 [0908723939] 0000290423: KSql::Execute(...) --> 'Error executing an Sql statement.',0 records,[sec: 0 msec: 1]
02/09/2012 11:15:06 [0908723987] 0000290424: KSql::EndTransaction('Error executing an Sql statement.',FALSE) --> 2
02/09/2012 11:15:06 [0908724014] 0000290425: KConnect::EndTransaction --> DiffStart[sec: 0 msec: 4], DiffLast[sec: 0 msec: 4]
02/09/2012 11:15:06 [0908724098] 0000290426: KSql::EndTransaction('Scripting requested rollback.',FALSE) --> 1
02/09/2012 11:15:06 [0908724131] 0000290427: KConnect::EndTransaction --> DiffStart[sec: 0 msec: 5], DiffLast[sec: 0 msec: 0]
02/09/2012 11:15:06 [0908724498] 0000290428: KSql::EndTransaction('Scripting requested rollback.',FALSE) --> 0

This shows a problem with one of the Datetime value provided as information on the version of the document being created.
From the SQL statement's insert values, we see the following DateTimes:

VerCDate = D/2012/2/9:11:15:7
VerMDate = D/2012/2/9:11:15:7
FileCDate = D/2012/2/9:11:15:4
FileMDate = D/1/1/1:0:0:0

You can see that the FileMDate -- the modification date of the source file from the client -- is coming through with a bogus date value.
This is probably the problematic piece of data.

In your code, you are setting the CreatedDate property of the Attachment (data).
Does the problem still occur if you also set the ModifiedDate property?

Cheers,
Kyle

Josephine_Bush

Hi,

Setting the modified date does help and now it will create a document, but it isn't actually getting the data inside the file. It just creates a file with 0kb. Perhaps my attachment code is not really grabbing the file -- I thought data.FileName would set that?

Attachment data = new Attachment ();

data.FileName = Request.PhysicalApplicationPath + "documents\\testing.docx" ;

data.CreatedDate = DateTime .Now;

data.ModifiedDate = DateTime .Now;

dm.CreateDocument(12748467, "name" , "comments" , false , null , data);

Many thanks for all your help,
Josephine

Kyle_Swidrovich

Hi Josephine,

Now I see the problem.
Setting the Filename property only sets the "original filename" for the version being added as a piece of metadata in Content Server.
To actually set the contents of the attachment, you need to set the Contents property, which is a byte array.

If the file is too large to stuff into a byte array in memory, then the CreateDocument method is not for you.
You'd want to look at the CreateDocumentContext method, which would allow you to use the ContentService to stream the version data into Content Server.

Regards,
Kyle

Josephine_Bush

Hi,
It is working perfectly now.
Many thanks for all your help!
Josephine

Attachment data = new Attachment ();

data.FileName = Request.PhysicalApplicationPath + "documents\\testing.docx";

data.Contents = File .ReadAllBytes(data.FileName);

data.CreatedDate = DateTime .Now;

data.ModifiedDate = DateTime .Now;

data.FileSize = data.Contents.Length;

Node node = new Node ();

node.Type = "Document" ;

node = dm.CreateDocument(q.ID, "filename", null , false , null , data);

Guy_Pomerleau

Hi Kyle

Does "CreateDocumentContext method" , (which would allow to use the ContentService to stream the version data into Content Server) allow the use of Windows authentification? Will it work for file like 20MB for exemple? If not, will it support HTTPS?