• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 833
  • Last Modified:

Unable to create a document library

I have a couple of site collections that started doing something strange.
Whenever someone tries to create a document library they get an error.  Standard MOSS error screen.

The funny thing is that I can create them via SharePoint Designer but not the browser.

Here's our infrastructure and info:
All MOSS servers are Windows 2008 X64
Database servers are Windows 2003 X64
2 Front End servers
1 Central admin server
1 Search/Index/Excel server
2 database servers
MOSS Enterprise.

Any direction or help would be greatly appreciated.
Thanks Ron.
0
Capt_Ron
Asked:
Capt_Ron
  • 9
  • 4
  • 2
1 Solution
 
Capt_RonAuthor Commented:
Note:
I set custom errors to off and this is the error message that appears on the browser screen:

at Microsoft.SharePoint.Library.SPRequestInternalClass.GetSchemaXML(String bstrUrl, String bstrListName, UInt32 sch, Boolean bOnlyViewAttributes, Boolean bExtendedFieldsProperties, ISPDataCallback pXMLCallback)
   at Microsoft.SharePoint.Library.SPRequest.GetSchemaXML(String bstrUrl, String bstrListName, UInt32 sch, Boolean bOnlyViewAttributes, Boolean bExtendedFieldsProperties, ISPDataCallback pXMLCallback)
0
 
MsShadowCommented:
If you create a new document library on the same site collection, does it still fail? Or is it only for specific document libraries in that site collection?
Did you apply a custom site definition to those site collections as that might be the cause:
http://blog.brianfarnhill.com/2009/04/07/cannot-complete-this-action-when-trying-to-create-a-document-library/
0
 
Capt_RonAuthor Commented:
No custom site Definitions.
The problem happens when you click Create | Document Library.

Thanks
Ron
0
Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
janicet123Commented:
If you click Create - Form LIbrary, do you get the same error? Do you have an existing library that you could save as a template and try to create a new library from that?
0
 
Capt_RonAuthor Commented:
I get the same error on Form Library, but nothing else.  Wiki, Slide, lists, etc... all work
0
 
janicet123Commented:
If you create a new library from a template of an existing library, does that fail as well?
0
 
Capt_RonAuthor Commented:
Yes that works
0
 
MsShadowCommented:
Going back to my idea then, it seems like its not your custom site definition that is "fucked up" but the out of the box ones for the existing site definitions. I would look into those and see if anyone made any modifications to them recently.
0
 
Capt_RonAuthor Commented:
I don't think that sonyone changed them.  I'm the only one who has access to the servers (other thhan the domain admins)

This happened after the data center was shut down for a halon test and updates to the infrastructure.  I don't think the servers were taken down correctly.
Our search blew up too and I was able to fix that.

Does the create DL function in SharePoint designer use the same definition file as the browser method?  SharePoint designer works fine when creating DLs.
0
 
Capt_RonAuthor Commented:
New information:
It seems that the issue revolves around a site template.  I looked at the ONET.XML files and the <DocumentTemplates> section is there.

How can I find out which site template the site uses?
Thanks
Ron
0
 
MsShadowCommented:
Seems like I was on the right track after all :-) Don't you have an ONET from a previous backup (before the crash) that you can just move over the existing ones (just make sure you didn't upgrade with a service pack between the backup and the current situation.
0
 
Capt_RonAuthor Commented:
I can check, but the WFE servers aren't backed up other that System state.

But if the ONET file was corrupted then isn't it strange that both my frone end servers have the exact same corruption?

I'm testing most of my sites now and I can say with 99% certainty that the one thing they all have in common is the site template used to create the site.  I do not believe that the template is still in use.  I'd really like to change the site template but I know that that is not possible.

Ron
0
 
MsShadowCommented:
Ron, you are correct. If you have it on all WFE's it would be quite weird that they all got corrupted at the same time. You are 100% sure that you didn't deploy any custom solution? As in that case that does get copied to the webfrontends and messes up them all.
0
 
Capt_RonAuthor Commented:
I'm the only farm admin.
I'm also one of 2 site collection admins and the other one is there only as a backup.

Nothing was deployed.
0
 
Capt_RonAuthor Commented:
I've been able to determine what happened but I have no idea how I can fix this.
Several months ago we had a major issue with MOSS.  Microsoft helped me rebuild the entire farm from scratch.  We didn't lose any data except the config databases. (There was a corruption in the config databases)
We took the opportunity during the fix to convert all sharepoint servers to Windows 2008 X64.
During that process the CustomTemplate was lost.  The old servers are no longer available.
The template ID that is missing is 11666 but it was based on the STS template. (actually identical to STS)

Is there a way to change the template on an existing site?
Ron
0

Featured Post

Microsoft Certification Exam 74-409

VeeamĀ® is happy to provide the Microsoft community with a study guide prepared by MVP and MCT, Orin Thomas. This guide will take you through each of the exam objectives, helping you to prepare for and pass the examination.

  • 9
  • 4
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now