Failed to instantiate file “default.master” from module “DefaultMasterPage”

You probably have two site definitions with the same id. One is retracted and deleted and now the site creation fails; check the log for details.

General

1. Enable the Windows SharePoint Services Administration to be able to schedule retracting jobs in the Central Admin
2. Download the newest WSPBuilder bits
3. Remember to remove the default bin of VS2008 and store the dll’s in 80bin (dll’s in the default bin are going to be deployed to the GAC!)
4. Add solution to the solution store:
   

   %STSADMPRG% -o addsolution -filename “..Solution1.wsp”

   (No files available in the 12 hive yet)

5. Deploy a solution:
   

   %STSADMPRG% -o deploysolution -name “Solution1” -immediate -force -allowCasPolicies -allowGacDeployment

   (Now you can see the files are added to the 12 hive; features are installed NOT activated)

6. Activate the feature:
   

   %STSADMPRG% -o deactivatefeature -filename Feature1feature.xml -url http://ServerName

7. To enable intellisense with your xml definitions within sharepoint install CAML.IntelliSense.msi
8. Be sure that the “Windows SharePoint Services Administration” service is running for deploying WSP solutions

1. Start VS 200[5][8] and create a new class library
2. Sign your class library and determine the publickey token (use reflector.NET for example)
3. Create a new class in your library with the following code:

   using System;
   using System.Collections.Generic;
   using System.Text;
   using System.Web.UI.WebControls.WebParts;
   namespace SimpleWebpart
   {
       public class SimpleWebPart : WebPart
       {
           private string displayText = "Hello World!";
   
           [WebBrowsable(true), Personalizable(true)]
           public string DisplayText
           {
               get { return displayText; }
               set { displayText = value; }
           }
   
           protected override void Render(System.Web.UI.HtmlTextWriter writer)
           {
               writer.Write(displayText);
           }
       }
   }
   

4. Add the following line of code to your AssemblyInfo.cs:

   [assembly: AllowPartiallyTrustedCallers]
   

5. Edit your web.config to add a safecontrol entry (remember to use the public key token as determined in step 2):

   <SafeControl Assembly="SimpleWebpart,Version=1.0.0.0,
     Culture=neutral,PublicKeyToken=XXXXXXXXXXXXXXX"
     Namespace="SimpleWebpart" TypeName="*" Safe="True" />
   

6. Copy the class library dll to the bin directory of your webapplication
7. Create a site collection if not already available
8. Go to Site Actions –> All settings –> Web parts. Choose New and add your web part to the site gallery.
9. Edit the page and add your webpart.

1. Create a SSP on a new web application (optional; you can assing your website to an existing SSP)
2. Change association to use the new SSP
3. Open the new SSP via Shared Services Administration
4. Click User Profiles and Properties
5. Click Full Import
6. Go back to SSP
7. Click Search Settings
8. Click Content Sources and Crawl Schedules
9. Set “Use this server for serving search queries” enabled (Operations –> Services on Server –> Office Search server”
10. Be sure that the specified accounts have enough rights to access the websites

When you have webparts on your page that are no longer available SharePoint throws an exception. To remove the webparts from the page that are no longer available navigate to the url

http://YourServer/Pages/[your page in error]?contents=1

Checkout the page; delete the webpart; and check in. Page can be loaded again!

Add the following line to your configuration section in the machine.config (be sure to locate any existing runtime item first)

<runtime><generatePublisherEvidence enabled="false"/></runtime> 

General

• Enable the Windows SharePoint Services Administration to be able to schedule retracting jobs in the Central Admin
• Download the newest WSPBuilder bits
• Remember to remove the default bin of VS2008 and store the dll’s in 80bin (dll’s in the default bin are going to be deployed to the GAC!)
• Add solution to the solution store: %STSADMPRG% -o addsolution -filename “..Solution1.wsp” (No files available in the 12 hive yet)
• Deploy a solution: %STSADMPRG% -o deploysolution -name “Solution1” -immediate -force -allowCasPolicies -allowGacDeployment (Now you can see the files are added to the 12 hive; features are installed NOT activated)
• Activate the feature: %STSADMPRG% -o deactivatefeature -filename Feature1feature.xml -url http://ServerName

Failed to instantiate file “default.master” from module “DefaultMasterPage”

You probably have two site definitions with the same id. One is retracted and deleted and now the site creation fails; check the log for details.