No defined path – MySite

If you get an error message saying that MySite cannot be created due to a missing tag in the URL or error in the defined managed path, then you have to do this:

Open Central Administration
Application Management
Define managed paths
Add the path, like “personnel”

Create a new search scope

This is very useful. Say you have several web sites and you don’t want to display the same search results on every web site – only the results relevant to the current site! Do this:

Open Central Administration
Open your SSP
Click on “Search settings” and then “Content sources”.
There is a list of current content sources, there might just be only one:

Anyway, click “New content source”
Fill in the following fields like this
“Name of the Content Source” = your web site name
“Content Source Type”
“Start Addresses or Applications” (if you choose the Business Data option)
” Crawl Settings and Schedules”
I always enter the name of my content source to the name of the site, it makes it easy to know where it is applied 🙂
The start address is the URL of my site, for example

If the content source is a public site then you may not have to index the site so often. I usually run the Incremental Crawl each hour or so instead.
Now save your settings and perform a Full Crawl on your new Content Source.
When that is done, go back to “Search Settings” and select “View Scopes”:

This page shows what scopes this SSP handles. Add a new scope and call it the same name as your content source, ie “mysite”. Now, you have to add some rules to your scope:

Click on “Add rules” and add the following:

I checked the “Content Source” so that I could select my content source “mysite”. Then I checked “Include” because I want all info on this site to be returned in the search results. Now you have to update your new scope.

Click on “Start update now” from the Search settings page.
When the update is ready, you have to associate the scope to your site. Go to Site Settings on your site, click on “Search Scopes” under “Site Collection Administration”. Click on the “Search Dropdown” link:

Now all available scopes are shown including our new scope:

Select your new scope – wow! Uncheck the other scopes, we do not want them on this site.
Your list should now look like this:

Now try your site search. When I did this, other search results STILL showed up. To change this, click on “Edit page” and select “Modify shared webpart” on your search result page. There is a field called “Scope” and even if there is no list to select your scope from, you can simply write in the name of your scope, like “mysite”.

Now when you perform a new search, only results from your site will be displayed!

Event id 7888 in Eventviewer

A while ago I got a lot of error messages in Event Viewer on our MOSS server. I found the following solution:

run stsadm -o sync -DeleteOldDatabases 0

and the message disappears.
What it does is enter the table “sitesynch” on the SQL server and deletes connections to any old Sharepoint config database that you may have on your server.

The entire message:

A runtime exception was detected. Details follow.
Message: A duplicate site ID 3b2fa192-1efb-4715-970f-2e550122faf0(
https://xxxx) was found. This might be caused by restoring a content database from one server farm into a different server farm without first removing the original database and then running stsadm -o preparetomove. If this is the cause, the stsadm -o preparetomove command can be used with the -OldContentDB command line option to resolve this issue.
Techinal Details:
Microsoft.Office.Server.UserProfiles.ProfileSynchronizationDuplicateSiteIDException: A duplicate site ID 3b2fa192-1efb-4715-970f-2e550122faf0(
https://xxx) was found. This might be caused by restoring a content database from one server farm into a different server farm without first removing the original database and then running stsadm -o preparetomove. If this is the cause, the stsadm -o preparetomove command can be used with the -OldContentDB command line option to resolve this issue.
at Microsoft.Office.Server.UserProfiles.ContentDBSynchronizer.RegisterSitesForSynch(Guid[] rgGuid, Int32 nGuids, Object dummy)
at Microsoft.Office.Server.UserProfiles.SynchCollection`2.FlushAdds()
at Microsoft.Office.Server.UserProfiles.SynchCollection`2.Add(T objAdd)
at Microsoft.Office.Server.UserProfiles.ContentDBSynchronizer.AddRemoveSites(String strFirstChangeToken, SPChangeToken lastChangeToken)
at Microsoft.Office.Server.UserProfiles.ContentDBSynchronizer.SynchContentDB()
at Microsoft.Office.Server.Diagnostics.FirstChanceHandler.ExceptionFilter(Boolean fRethrowException, TryBlock tryBlock, FilterBlock filter, CatchBlock catchBlock, FinallyBlock finallyBlock)

Install IFilter on MOSS

How to install the PDF iFilter so that pdf files are searchable (and given an icon too)

Download the latest Adobe PDF IFilter from
Stop the IIS service
Run the Adobe PDF IFilter Setup on your MOSS server
Copy the ICPDF.GIF file (search your server) to “C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12TemplateImages”
Open “C:Program FilesCommon FilesMicrosoft SharedWeb server extensions12TemplateXmlDOCICON.XML”
Add the following to the .pdf type:
Run iisreset
Add the .pdf file type in the following list:
Open Central Administration, Shared Services Administration (SSP), Search Settings and select File Type
Add the new filetype pdf
Perform a fullcrawl of your content source

Useful STSADM commands

path to STSADM is
cd C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12BIN

stsadm -o addcontentdb -url URL [-databaseserver servername] –databasename databasename [-DatabaseUser username -DatabasePassword password] [-SiteWarning number] [-SiteMaximum number] [-SearchServer servername]

stsadm -o addcontentdb -url http://srv007:42464 -databasename Sharepoi1_SITE

stsadm.exe -o restore -url http://srv007:24003 -filename c:backupmigrera-SRV005-ComSolut1_SITE.SPB

create a new site using a template in another language (in this case… surprise, Swedish!!)
stsadm.exe -o createweb -url http://server:port/sitename
-lcid 1053

export a site with version history and security remained
stsadm.exe -o export -url http://url/site -filename c:backupsiteds.bak -includeusersecurity -haltonfatalerror -versions 4

import a site with version history and security remained
stsadm.exe -o import -url http://url/site -filename c:backupsiteds.bak -includeusersecurity -haltonfatalerror -updateversions 1

Create a content type for Word

I love content types in Sharepoint. I use them when I create new publishing pages, new templates, new columns and yeah that’s it. So useful and powerful. Change in one place – update all others!

If you want to publish a Word template to a library you… that’s right – create a new content type and associate your library with it. If you make any changes to your template, all libraries that use that template are…. updated!

Do this:
Site Actions, Site Settings, Modify All Site Settings
Click on ”Site content types” and ”Create”
Create a new with the name of your template, ie “Agreement”
Select ”Document Content Type” as Parent Type, and ”Document”
Put your content type in a new group with your company’s name for example (this is so that you know which content types you have created and you will also find them easier)
Click OK (needed for any dummies :))
Click on ”Advanced settings” and select the template that should be associated with this content type by clicking on ”Upload new document template”
You don’t have to mark it as readonly, but do select that it should be updated.
Open the document library where you want to use this new content type and do:
Click on ”Document library setttings” and select ”Advanced settings”
Activate ”Allow management of content types”
Click OK
On the middle of that page a new group is visible. Click on ”Add from existing site content types”
Select your group (your company name for example) and get your new content type
That was not so many steps…. 🙂
Now, when you look at your “New”-button in your library the new button “Agreement” should be visible! You can also metatag those templates with their own metatags, if you want to use several templates in the same library. Cool!

Content Deployment error

When I should activate Content Deployment on our Sharepoint server I got the following error message:
“Value does not fall within the expected range”
Oh I just love the error messages in Sharepoint, they are so informative 🙂

Ran the following commands instead:

Stsadm -o deactivatefeature -name deployment -url
Stsadm -o deactivatefeature -name migration -url
Stsadm -o activatefeature -name deployment -url
Stsadm -o activatefeature -name migration -url

Got the message
“Failed to find the XML file at location ’12TemplateFeaturesmigrationfeature.
Opened the folder and saw that the folders “migration” and “deployment” were missing, but there was another called “Deployment Links” and “Migration Links”. Copied those and renamed them to only “Deployment” and “Migration”. Success! I was able to activate the new feature!

Missing features

When you install the language templates I have discovered that many functions are missing. The solution is to compare the 1033 folder with the 1053 and copy the files that are missing to your new language folder.

For example the search function on WSS pages:

I had to copy the file search.js into the 1053 (which is for Swedish) folder, and magic – it’s visible!

“Save site as template” is missing… or?

Yes but it’s available with a little trick 🙂

If you try to save a website as a template, you’ll find out that there is no link to it in administration mode (web site settings). You must change the following in the URL and it will be available:
Change from this URL:
To this URL:
and you may save your website as a template!