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.

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?


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
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

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.


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.

First Post…

Somewhere, someone has the same problems I do surrounding SharePoint and the associated technologies that make me want to whimper.  I can’t be the only one.  So when I find answers, I like to put them somewhere useful (not the elusive “safe place”).  I hope that somewhere, someone benefits from the eye-rolling and head-banging that I go through, even for the stupid stuff.

Or maybe this will remain hidden from the world and at least I’ll be able to find it again.


Can’t Open a OneNote Notebook on a SkyDrive in the OneNote client

Before my laptop was reimaged, I could open my SkyDrive Office documents list and open a OneNote notebook in the client app on my laptop.  After the reimaging, I get this error:
OneNote SkyDrive Error
Troubleshooting Steps
1. Google the error.  Here’s what Microsoft says:
2. Follow Microsoft’s advice:
  • Internet Explorer: Enable the SharePoint OpenDocuments Class add-on (enabled – no change)
  • Firefox: Enable the Microsoft Office 2010 add-on (enabled – no change)
  • Internet Explorer: Set security settings (set – no change)
  • If the above doesn’t work, then:

Open notebooks from the browser manually

If you use a browser other than Firefox or the 32-bit version of Internet Explorer, if you don’t want to install OneNote 2010, or if you don’t want to change security settings in Internet Explorer, you can open browser-based notebooks without using the add-on.

To do this, you download the notebook’s section to your computer, open it in the OneNote desktop application, and then upload it back to the website. This process is supported on a SharePoint site only, not in Windows Live SkyDrive (see notes below for SkyDrive fix – ny).

  1. On the SharePoint library page, click the Open Menu arrow next to the notebook, click Send To, and then click Download a Copy.
  2. Save the section (.one file) on your computer in a folder that you can easily find, such as Desktop or My Documents.
  3. Double-click the section to open it in the OneNote desktop application. If your version of OneNote is earlier than OneNote 2007 you must install a converter to edit the section.
  4. Edit the section. OneNote saves your changes automatically in the folder where you downloaded the section.
  5. In your browser, go back to the SharePoint library page. In the ribbon, under the Library Tools section, click the Document tab, and then in the New group, click Upload a Document.
  6. Be sure the Add as a new version to existing files checkbox is selected, and then click Browse to locate the section that you just updated.
  7. Double-click the section, and then click OK.

So… I tried that.  I downloaded it, unzipped it, modified it, and closed it.   Instead of uploading it back to my SkyDrive, as above, like Microsoft would have me do to a SharePoint workspace, I clicked File > Share > Web > Work (folder) > Share Notebook.  I clicked No, Thanks in the message box and closed the OneNote, then reopened it, made a minor change, and manually synched it.  Back on my SkyDrive, there it was in all its glory.

A bit of a pain to set it up, but at least it works.  I believe the instructions on Microsoft’s troubleshooting page are for a SharePoint workspace similar task.