Donnerstag, 17. Mai 2012 21:02
I'm faced with this really weird issue and am wondering if any of you has encountered the same. In a document library, I have created a custom document set and configured it to allow other custom content types to be used in it. This was all working fine as users are able to upload documents to the library for a couple of months until the other day when a DBA decided to change the password on one of the service accts used in SP (spFarmAdmin). Issues started popping up, so we restarted the app server, did an iisreset, sharepoint is back up and running. The issue now is that users cannot see the content types in the list of available content types in the document set that they've created in the library.
In the library settings, if I click on the document set settings to add the missing content types, they do not appear in any of the available groups of content types. But when I open up SharePoint designer and view the properties of the content type in question, it shows that it belongs to the proper content type group. I can also see the content type in question in the Content Types section in the library settings.
Any ideas on how these content types be restored without having to recreate the document set/content types?
By the way, everything works fine on document sets that were created prior to the password change 2 days ago.
Any help is appreciated.
Freitag, 18. Mai 2012 11:47
Freitag, 18. Mai 2012 13:58
Paul, thanks for your reply. No, the document sets are created in the same site collection. Something new I had discovered late yesterday. Going into the document set settings in the libraries (same site collection) where we use document sets, I found that the document set had lost all the (allowed) content types that I had previously set. I tried going through the content databases to see if I can locate these missing content types but with no luck. Am I querying the right db tables? Thanks again.
Dienstag, 29. Mai 2012 15:22An update on this issue. This issue was resolved by recreating the missing content types and document sets. Of course, I backed up the contents of the libraries that had been affected, which fortunately, only contained a few documents, then deleted its contents. This allowed me to delete and recreate the document sets. It's a pain but was the only solution I could come up with.