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.

Answer:

 stsadm.exe -o unquiescefarm

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

Central Administration > Operations > Quiesce Farm

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.

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

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.

but… do this first:

http://blogs.technet.com/wbaer/archive/2007/10/30/installing-windows-sharepoint-services-3-0-on-windows-server-2008.aspx

fun?

x86:

http://www.microsoft.com/downloads/details.aspx?FamilyID=ef93e453-75f1-45df-8c6f-4565e8549c2a&DisplayLang=en

x64:

http://www.microsoft.com/downloads/details.aspx?familyid=9FB41E51-CB03-4B47-B89A-396786492CBA&displaylang=en

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.

http://office.microsoft.com/en-us/sharepointdesigner/HA100699391033.aspx

http://www.sambets.com/

It’s been around 45 days since the acquisition of FAST Search and Transfer closed and we’re moving quickly to provide interoperability for Microsoft customers between FAST ESP and Microsoft SharePoint Server.

The first deliverables from this work are a set of FAST ESP Search Web Parts for quickly integrating results from FAST ESP into SharePoint Server 2007 and a FAST ESP Search site template. 

Using these Web Parts and Site Template SharePoint administrators will be able to quickly and easily build FAST ESP-based search sites inside SharePoint 2007 by simply dropping in and configuring the appropriate components.

The Web Parts and Site Template are available as a free download (both compiled code and source code) from CodePlex at www.codeplex.com/espwebparts and are part of the Search Community Toolkit.

Some of the FAST ESP search capabilities that can be exposed within SharePoint Server 2007 using these Web Parts include:

• Search Box Web Part — Search box for query term submission and includes “did you mean” functionality for query correction

• Result List Web Part — Displays search results and supports sorting, pagination, and navigator-based filtering

• Navigator Web Part — Displays dynamic navigators that profile search results across a set of pre-defined dimensions and allow users to refine the search through navigation clicks

• Breadcrumb Web Part — Displays the search term(s) and list of navigators used to obtain the current result set

The FAST ESP Web parts are designed to be open and extensible, and we’re actively encouraging customers and partners to download them, customize them to align with their branding and extend them to fit their search and user experience requirements.

Expect the features, functionality and range of ESP Web Parts to grow through contributions from the search developer community as well as further contributions from the FAST & Microsoft Search Team!

FAST & Microsoft Search Teams.

First, check the People scope in the SSP.

Shared Services Administration: SharedServices1 > Search Administration > Scopes

http://moss1:8888/ssp/admin/_layouts/viewscopesssp.aspx?mode=ssp

This scope should have a rule of:

contentclass = urn:content-class:SPSPeople

     Behavior: Require

Take not of the Item Count.

Now take a look at the User Profiles and Properties page.

Shared Services Administration: SharedServices1 > User Profile and Properties

http://moss1:8888/ssp/admin/_layouts/ProfMain.aspx

In the Profile and Import Settings section look at the first item Number of user profiles:.  If this number doesn’t match the Item Count from the Scope you are    pulling too many items into your Local Office SharePoint Server sites  Content Sources.

To check Local Office SharePoint Server sites 

Shared Services Administration: SharedServices1 > Search Administration > Content sources

http://moss1:8888/ssp/admin/_layouts/listcontentsources.aspx

Edit  the Local Office SharePoint Server sites content source

In the Start Addresses section should be the following items

http://(server): (port)/ (SSP)

http://(portalsite)/ (URL of main portal site)

sps3://(server): (port)/ (My Site Host)      Crawl Settings: Crawl everything under the hostname for each start address

Crawl Schedules: Full Crawl: At 12:00 AM every day

Incremental Crawl: Every 2 hour(s) from 7:00 AM for 14 hour(s) every day

Updating the  Local Office SharePoint Server sites fixed my problem.

The hardware rig was provided by Fujitsu and included blade servers, rack servers, and an Eternus 4000 SAN with 10 TB of storage space. Special thanks to Greg Reuter, Jeff DeCarlo, and Brett Pierce from Fujitsu!

 KnowledgeLake, a Microsoft Gold Certified Partner, was responsible for blasting 50 million content items into SharePoint; they also played a key role in defining the architecture, creating and executing the system tests, and gathering the massive results. KnowlegeLake was ultimately able to use their load tool to send 50 million documents into SharePoint at a peak rate of over 7 million documents per day! Very special thanks to Russ Houberg, Gregg Smith, Bob Bueltmann, Chuck Nash, and Ron Cameron from KnowledgeLake!

Of course, I simply can’t forget to mention all the incredible Microsoft people, who assisted in making this effort a success. First and foremost, our fearless leader, Andy Hopkins, who led the effort from start to finish and constantly amazed me with his enthusiasm and perseverance. I was equally impressed with Andy’s ability to wordsmith while editing our whitepaper. Next comes the long list of other exceptional individuals who stepped up to help out: Steve Peschka, Mike Taghizadeh, Thomas Rizzo, Ryan Duguid, Joel Oleson, Mitch Prince, Doron Bar-Caspi, Simon Skaria, Ambrose Treacy, Sid Shah, Grant Morisette, and Mitch Powers.

I could never have completed this project without the generous help of the people mentioned above. It was truly a collaborative team effort!

In addition to the project that resulted in the Scalability and Performance whitepaper, the KnowledgeLake folks and I were recently involved in another very challenging proof-of-concept for a large pharmaceutical company, which represented a large-scale SharePoint implementation containing 40 TB of content (about 75 million content items) spread across two SharePoint farms.

I am absolutely confident that after these two projects, we’ve finally answered the looming question, "Can SharePoint scale?" with a resounding, "Yes!"

I hope that you’ll find this whitepaper beneficial in designing your SharePoint implementations whether small, medium, or large-scale. You can open or download the appropriate format of the whitepaper from the links below. If you have any questions or suggestions, please leave a comment on this blog entry.

• Word 2007 format: http://go.microsoft.com/fwlink/?LinkId=120881
• Word 2000-2003 format: http://go.microsoft.com/fwlink/?LinkID=120890
• PDF format: http://go.microsoft.com/fwlink/?LinkID=120891

Paul J. Learning
Senior Consultant, Microsoft Consulting Services