Problem: A file’s editform.aspx page doesn’t show all of the properties that belong to its content type

If a content type is added to a doc library and a file inside the library is changed to that content type, but its EditForm.aspx page doesn’t show all of the properties that belong to the content type (1 or more columns are missing from the edit page), the content type IN THAT LIBRARY may be corrupted.
Resolution:

IN THAT LIBRARY (not in the Content Types Gallery):

  1. disassociate the affected files from the struggling content type (don’t delete any existing metadata);
  2. delete the content type;
  3. re-add it to the library; and
  4. change the content type of the disassociated files.

The files should either appear where they’re supposed to in the library (if metadata exists) or will be available for complete property editing.

Does someone have a better solution?

Advertisements

Javascript error in IE8 after re-image

After my laptop was re-imaged, I couldn’t get the drop-down menus on our SharePoint 2007 Intranet home page global navigation tabs to appear, and a JavaScript error regarding the init.js file appeared in the status bar.  Drop-downs were fine in Firefox, and on other people’s machines.
I opened SharePoint Designer and ran the Office Diagnostics.  The report told me it identified a couple of issues and fixed them, and now my drop-downs are good in IE.
I am duly impressed.

There was an internal error invoking the timer job…

Actually, there were a lot of them, each looking roughly like this:

Event Type:    Error
Event Source:    Windows SharePoint Services 3
Event Category:    Timer
Event ID:    6772
Date:        6/10/2011
Time:        2:30:01 PM
User:        N/A
Computer:    GFTB-QA-02V
Description:
There was an internal error invoking the timer job ‘{FD730E80-C470-4D92-B0E5-F57C98ABDF4A}’ for service ‘{00000000-0000-0000-0000-000000000000}’.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Not only did that timer job not exist, don’t you love what you get when you click that helpless link:

No results were found for your query. Please see Search Help for suggestions.

Growl.

Long story short: of almost 200GB usable space, 5.11MB (yes, MB) was available.  Check the available space on the database disk drive and call on your local SQL Superhero.  In our case, the transaction log was bloated and needed truncating.