I am trying to create a document set programmatically, and I am using the following code:
//Get the folder into which to insert the document set.
SPWeb web =
View Complete Post
View Complete Post
when creating a new document library on our site, we get an unknown error
the libraries create fine on the subsites just not on the top level sites.
MSDN Magazine June 2000
I hope someone here can shed some light on this one...
We have a document library configured with a few content types and document information panels for those items. Also on this list we have a BDC column setup to pull client names from MS CRM. This works fine on the list itself, however, in Word 2007 - the picker does not show up in the DIP, so we cannot easily select clients without knowing the name (first issue).Secondly, if we enter in a client name, or partial, we recieve the following error:"There was an error in the validation code" - with the following details:Document Information Panel cannot complete this action, because of an error in the form's code.The following error occurred:Object requiredFilecript.jsLine:171Any help is appreciated!
I have a document library with the standard name column linking to the document. However, we'd like to create a custom field and have that link to the document (and edit item menu).
How is this best accomplished?
Thanks in advance!
I am receiving the error "Cannot complete this action. Please try again" when trying to add a document library to one of the sites. This is Sharepoint 2007 SP1. I seem to be able to do it thru designer but not the web interface.
Does anyone know how to fix this?
I am running MOSS 3007 Standard on Windows 2003. When trying to upload files larger than about 29Mb, I am getting an HTTP 400 Bad request error. The error states "HTTP Error 400 - Request is badly formed." I am able to successfully upload a 28Mb file. Sharepoint
is configured to accept files up to 75Mb.
I have done a fair amount of research on this, but none of the solutions seem to apply to our environment. The two most likely candidates do not apply, for example we are NOT running URLScan (there are a variety of solutions suggesting this could be an issue
with uploads of 30Mb or more), and we are on 2003 with IIS6, so again the issue relating to 2008 and IIS7 do not apply.
The "Request is badly formed" part of the request is particularly confusing as most issues I have come across where this error is the symptom point to errors in custom code that is trying to talk to SharePoint. We have done none of our own custom coding
and this error is occurring when attempting a simple upload to a document library.
Trying to drag and drop the file across when the document library is open in windows explorer also fails.
I did come across someone saying they had a similar problem which was caused by a damaged content database, however in this case, it is occuring regardless of which content database I use, so either they are all corrupt