If you get an error like the one in the image below, recycle your website’s application pool.

GDI+ Is Not Properly Initialized (GDI+ Error)

In order to delete the many Content Deployment Timer Job records that are created during the automated content deployment process follow the steps below:

1. Run the following SQL statement on your SharePoint Config Database to retrieve the unique IDs (GUIDs) of all the Content Deployment Timer Jobs:

    select * from Sharepoint_Config.dbo.[Objects] REM where [Name] like 'ContentDeploymentJobDefinition%'

2. Then, use those unique IDs (GUIDs) to build a batch file to run the following STSADM command:

   STSADM -o deleteconfigurationobject -id "<object id>"

Tobias Zimmergren has a great post on his blog that explores the User Information List. 

Here is an excerpt:

The User Information List can be accessed (Only if you’re admin) via the browser by navigating to /_catalogs/users/simple.aspx from your site. (Ex: http://zimmergren/_catalogs/users/simple.aspx)

This works for both Windows SharePoint Services 3.0 (WSS 3.0) and Microsoft Office SharePoint Server 2007 (MOSS 2007)

Tobias Zimmergren has a great post on his blog that explores the User Information List. 

Here is an excerpt:

The User Information List can be accessed (Only if you’re admin) via the browser by navigating to /_catalogs/users/simple.aspx from your site. (Ex: http://zimmergren/_catalogs/users/simple.aspx)

This works for both Windows SharePoint Services 3.0 (WSS 3.0) and Microsoft Office SharePoint Server 2007 (MOSS 2007)

After applying the latest Windows updates for Windows Server 2003, we received many “Timed Out” errors when trying to run content deployment jobs.  The main culprit of there errors seemed to be the OWSTIMER.EXE process and it taking 100% of the CPU… yeah, I know “it’s a pain!”

Anyway, one of the things I did to try and get the issue resolved was to clear out the years of Content Deployment objects that had built up on the target server.

This was a 2 step process:

1. Find all the Content Deployment Job objects in the config database and get their IDs

   select * from Sharepoint_Config.dbo.[Objects]  where [Name] like 'ContentDeploymentJobDefinition%'

2. Run an stsadm command to delete the object based on its ID
   

   STSADM -o deleteconfigurationobject -id "<object id>"

I was able to do some text manipulating and get a really long .bat file that ran for a really long time. When it was done, all the Content Deployment Job objects were gone.

However, it did not seem to fix my issue with OWSTIMER.EXE taking 100% of the CPU.

The solution for that seemed to be narrowing down which Content Deployment Job was causing the issue by disabling them all and then re-enabling them one at a time and deleting the target site collection and doing a full deployment.

I’m not sure which update caused the issue but after doing a Windows Update the OWSTimer.exe job started using 100% CPU on the target server of a content deployment job.

The trace logs showed the following errors:

CSsoResourceManagerCache cannot find SSO connection string value in the registry! Error code is: -2147418113 CSsoResourceManagerCache has set SSO connection string value to be empty …  SSO is not configured any more. Error code is: -2147418113 IResourceManager::Refresh() failed Error code is: -2147024809 ForceRefreshOfSPSResMgr() failed. This may be ok if SSO has not been configured yet and the run-as service gets an access denied Error code is: –2147024809

Thanks to Kerry’s SharePoint Blog for the tip about stopping the SSO service (Microsoft Single Sign-on Service) and setting it to manual.

Security – Archives – Space

Those three reasons to get a handle on your SharePoint installation are all tied in to governance.  Jake Frazier, CIO Update, wrote an article, “Prolific SharePoint Sites Undermine Governance”  that addresses each aspect pretty well.

The only real question I have is on the second page:

…the licenses for SharePoint are “free” or at least relatively inexpensive.

What?  Jake, you can’t be serious.  If you only have 10 users, it’s not too bad.  However, the price doesn’t usually scale very well no matter how much of a volume discount you get.  The good part is, this one little sentence definitely was not the main idea of a very well written article.

Thanks, Jake!

Below is a listing of features that are included in Sharepoint 2007 MOSS
via List of Features with GUIDs

Here is a listing that I found of web parts that are in WSS versus MOSS:
via Out of the box web part listing for WSS and MOSS

Below is a list of the features available in Sharepoint 2007 MOSS compared to WSS
via What’s a MOSS 2007 vs. WSS v3 Feature

Windows SharePoint Services v3 Features:

33 Features in WSS v3

Microsoft Office SharePoint Services 2007 Features:

107 Features Added in MOSS 2007*