Discussions
Categories
Groups
Community Home
Categories
INTERNAL ENABLEMENT
POPULAR
THRUST SERVICES & TOOLS
CLOUD EDITIONS
Quick Links
MY LINKS
HELPFUL TIPS
Back to website
Home
Content Management (Extended ECM)
API, SDK, REST and Web Services
Adding Documents or items to livelink ERROR....!??????
Ahmad Ayyoub
Dear All i had the attached error whrn i try to add any new document or item like workflows to livelink , the error forbed me to add it using add doc's or even Drag and drop .after the error i find the created object or doc but with 0KB size , i hope that anyone could help me .......Thanks A Lot AHMAD AYYOUB
Find more posts tagged with
Comments
Pravs4
Please check the EFS is working properly. This has to do something with EFS...Pravin.
Ahmad Ayyoub
Thanks for your replay,I think you mean Enterprise Storage File (ESF), our EDMS Server is saving the files using the SQL server itself without (I mean we didn't specify a path or external path for saving doc's ), it?s not good but I hope it doesn?t effect.It was working good but now it?s not and giving the previous error
Appu_Nair
if that is the case(internal storage is hosed) I would try adding a new document into a new folder and then try adding a version to the newly formed document to rule out if SQL server table space itself is running out.If you can add documents in other places and can narrow it down to specific failures then OT support should be involved.I would open a ticket and run the instance with debug=2 and wantlogs=true
Benjamin_Shapiro_(benshapiro_-_(deleted))
Hi AhmadThree things come to my mind when I see what you've written.The first, is to look at the "Details" button that is presented with the error. It sometimes give that extra bit of information that can help you to determine it (i.e. "Cannot create external path" or "Cannot extend tablespace").The second - to help determine if it *is* an external issue (though you've said that you have internal storage) would be to create a new "text" document. This would add text content via the browser interface and doesn't require an upload per se. If that works, then it truly is some sort of issue with the transmission of the document from the user to the final storage location.Finally, it may be that somewhere along the lines, a module has been installed or some other change has been made that has (for some reason) put you to external storage from internal. I'd suggest checking your database maintenance to see if Livelink thinks you're external when you shouldn't be.Cheers,Ben