An error occurred trying to publish this page on the set schedule. Republish the page with a new date or view the log if the problem continues.

An error occurred trying to publish this page on the set schedule. Republish the page with a new date or view the log if the problem continues.

 Following a recent server migration, we noticed that items were not being published at their designated start times.  Check Central Admin to make sure the following Timer Job Definitions are listed

Central Administration > Operations > Timer Job Definitions

Scheduled Approval 
Scheduled Page Review 
Scheduled Unpublish 
Variations Propagate Page Job Definition 
Variations Propagate Site Job Definition 

First, make sure you have the Office SharePoint Server Publishing Feature enabled.

Home > Site Settings > Site Features

Second, if the Feature is enabled, try to Deactivate then Activate.  This should install the Time Jobs in Central Admin.

The My Site of [user name] is scheduled for deletion

The My Site of [user name] is scheduled for deletion. As their manager you are now the temporary owner of their site. This temporary ownership gives you access to the site to copy any business-related information you might need. To access the site use this URL:

After a manger forwarded me this email, I realized we had a configuration problem in our environment.

The problem was we had our LDAP Active Directory (AD) import configured to import all users regardless of their status. So, when the user was deleted from AD the manager received the email and was unable to see the My Site.

To fix the problem I updated the LDAP Search Filter to:

(&(objectCategory=person)(objectClass=user)( !(userAccountControl:1.2.840.113556.1.4.803:=2)))

Now the import will only grab active users from AD. This is allows plenty of time for the manager to look that users My Site before it is deleted.

In my case, we disable users in AD then sixty days later they are deleted from AD. Once deleted from AD the My Site will be deleted from SharePoint following the next FULL import of user profiles.

Where do I edit the LDAP Search Filter?
Shared Services Administration: [Your SSP Name] > User Profile and Properties > Manage Connections

An unexpected error has occurred.

When trying to access the Shared Service Provider (SSP) I received the following generic error:

An unexpected error has occurred.

Yes, the detail is overwhelming and pointed me directly at the problem.

To allow the .aspx page to show the detail behind the error I had to make a small change to the web.config file.  In my case the web.config file in question was located in the following location:


How did I know where this was located?  If you are in Central Administration and hover over the name of your SSP with your mouse, you should see the path at the bottom of the browser windows.  If not, right click and select Copy Shortcut and paste it into notepad.



The 7788 pointed me to the folder that contained the web.config I needed to edit.

Once you have located the needed web.config file make a copy of it. Open the original web.config file and make these two changes.

<SafeMode CallStack=”true“>

<customErrors mode=”Off” />

Save the file.

The page should now show you what is wrong with the file. In my case, there were a ton of “?” all over my web.config. How they got there I will never know.

New button missing from toolbar

I was working in a Document Library and the View was missing the New button to allow for folder creation.

Simple fix.

Site Actions > Edit Page > (the web part you want to fix) click edit > Modify Shared Web Part

In the Web Part properties window click on Edit the current view

Now scroll down to until you see Folders.

Select Show items inside folders  in Folders or Flat: 



This form has been closed.

When trying to create a workflow using Internet Explorer I received the following message:

The server is currently being taken down for maintenance. Check with your system administrator to see when this server is scheduled to come back online.
Click Try Again to attempt to load the form again. If this error persists, contact the support team for the Web site.

Click Close to exit this message.

This error was then followed up by another error:

This form has been closed.

We have InfoPath forms installed with workflows that have worked seamlessly, sooooo, I was a little perplexed when i started getting this error.


 stsadm.exe -o unquiescefarm

I tried doing the same thing using Central Admin. with no luck

Central Administration > Operations > Quiesce Farm


Existing site associations will change

The Web application you have selected to host the SSP administration site and/or My Sites already hosts other content sites.  These content site will automaticcly be associated with the new SSP.

I received this error when trying to replace my intranet site with my new SSP site.

CPU maxed out on the WFE server

if the CPU is maxed out on your SharePoint 2007 server check the Indexer Performance setting in Central Administration.  My setting was set to causing my CPU’s to run at 100% and nine instances of mssdmn.exe to run.  Updating the setting to Reduced brought the CPU’s back to a normal level.

Central Administration > Operations > Services on Server > Office SharePoint Server Search Service Settings

Can’t find the Business Data Catalog

I was doing a fresh install of MOSS and didn’t see the Business Data Catalog section listed in the SSP. The Business Data Catalog wasn’t there because I hadn’t enabled Enterprise Features in the Operations page.

Simple fix, in the Operations page look at the bottom of the page for the Upgrade and Migration section.  In there you will find Enable Enterprise Feature.  Click Enterprise and input your key.

Follow the directions on the screen and you should be ready to go.

Installing SharePoint on Windows Server 2008

To install SharePoint on a Windows Server 2008 machine you will need the SharePoint install that includes SP1.

but… do this first:




Point Admin Toolset

The Idea Database Accelerator tool appears to be real handy at analyzing, reorganizing, and rebuilding indexes.

Keep in mind i’m still playing with this.

Today I sort of figured out how to backup and restore a site using Idera Site Backup.  Site Backup creates a .cmp file for the site you are backing up.  Using SharePoint Designer I was able to restore my deleted site from the .cmp file.

Here are the steps I followed:

Restore a Web site

Step 1: Create a new empty Web site as a destination

  1. On the File menu, click New.
  2. In the New dialog box, click the Web Site tab, click General, and then click Empty Web Site.
  3. In the Specify the location of the new Web site box, enter the location where you want to restore the backup site.You can restore the site to a different server, and you can restore it as either a new top-level site or a subsite under an existing top-level site.
  4. Click OK.

 Tip   You can also create an empty Web site through the browser by using the Site Settings or Create pages. For example, when viewing the site in the browser, click Site Actions, and then click Create. On the Create page, under Web Pages, click Sites and Workspaces. Complete the first four sections, but when you get to the Template Selection section, close the browser without making a selection. Do not apply any template — including the Blank Site template — or the restore operation will fail.

Step 2: Restore the backup file to the destination

  1. With the destination site open, on the Site menu, point to Administration, and then click Restore Web Site.
  2. In the File Open dialog box, browse to and click the .cmp file that you want to restore, and then click Open.
  3. If the current Web site is low on available storage space, click Advanced, and then do any of the following:
    • To store the archive files in another temporary location, enter a new location in the Temporary location for archive files box.Backing up a Web site requires a location to store temporary backup files. By default, Office SharePoint Designer 2007 uses the current Web site. You can use another site on the same server or a location on another server on the same network — for example, \\Server name\Share name.
    • To store the .log file in another location, enter a new location in the Location for import log file box.You might need to choose another location for the .log file if the server cannot write to the default location. By default, Office SharePoint Designer 2007 creates an import .log file in the current Web site. You can check this file to determine if there were errors during the restore process.
  4. In the Restore Web Site dialog box, click OK to confirm that you want to restore the .cmp file to the current empty Web site.If the site that you are backing up or restoring is large, the process can take quite a while.