Debug: Security check failed in OnWebImport

Importing Folder /cgs

FatalError: Value does not fall within the expected range

GetWebRelativeUrlFromUrl

I was able to create a blank subsite and then do the import to that new subsite, but it would not create the subsite for me.  On my standalone install, this worked without having to precreate the site.

I was able to solve these issues by granting owner permissions on the unselectable subsites to the user I was logged into central admin as. 

Alternatively, you can log into Central Admin as a user who has Site Collection Admin permissions on the Site Collection you are exporting or grant the Central Admin user Site Collection Admin permissions.

The following articles provide the details:

How to configure SharePoint to use Kerberos:
http://technet2.microsoft.com/Office/f/?en-us/library/40117fda-70a0-4e3d-8cd3-0def768da16c1033.mspx

How to create an SPN:
http://msdn2.microsoft.com/en-us/library/aa480609.aspx

Stemming = plural, tense, and case insensitivity.

Answer: Here is the info on enabling stemming.

Note: If either the backup or restore fails, you will need to delete the job from Operations, Global Configuration, Timer job definitions before running again

• Backup the application you wish to migrate
• Central Administration, Operations, Backup and Restore Section, Perform a Backup
• Select the sites being migrated and set a destination folder for the backup.
• The destination folder will need the following permissions
• Read/write for the SQL Server process account
• Standard install uses the network service account
  (MyDomain/SqlServerName$)
• Read/write for the SharePoint process account
• Restore from backup onto the destination server
• Central Administration, Operations, Backup and Restore Section, Restore from Backup
• Specify the location of the backup files
• Select the backup
• Select the application(s) within the backup that you wish to migrate and click "Continue Restore Process"
• Set your Restore Options
• New Configuration
• Provide credentials for a SQL Server user account or leave blank to use the Sharepoint process account via Windows Authentication
• The account must be a member of the dbcreator role
• Provide the new URL
• User the new http:ComputerName:Port
• Provide the new SQL server name
• Verify the SQL server data directory is correct
• SQL2005 uses a slightly different default path than SQL2000
• Optionally change the Application and Database names
• Click OK to begin the restoration then come back in a half hour to see if it worked.
• If moving to a different domain, use an account with admin on the SharePoint server to configure the new user accounts in each site's People and Groups interface.

• Master page incompatible
  • 'TrimNonCurrentHeadings' error
  • Due to customizing the B2 master page templates.  See here for details/fix.
• Approval workflow error
• InfoPath Forms services "Critical Error" message
• "'undefined' is null or not an object"
• Resolution:
• Restart IIS on each SharePoint server after running the stsadm.exe -o reconvertallformtemplates command
• Windows Sharepoint Search Service will not start
  • Errors out when enabling the service for the first time
  • Circumstances
  • Filled out the form after Enabling.  Error occurs just after submitting.
  • Office Sharepoint Search Service was enabled
  • Shared Services was configured
  • B2TR was applied before any services were enabled
  • This service is non-critical in a MOSS install since the MOSS Sharepoint Search service provides all search capabilities except for Sharepoint Help indexing.
  • Currently unresolved – Suggestions?
• Modify Site Content Type: Name, Description, and Group
  • The resource object with key 'cyptedit_select_group' was not found.

The default image on the Internet presence site is an italicized A or leaning arrow in the color of the selected style sheet.  In order to modify the graphic, you can either change the master page template to hide or remove the existing logo area and add your own hard coded image link or you can continue with the style-sheet approach built into the site.  The benefits of using the style sheet approach is the ability to define multiple images and link them to different styles.  The disadvantage is that the image is included as a background image and will not be printed by default and is more difficult to resize.

To change the image in the Style Sheets:

1. If using the same sized image:
_________________________________________________
Just go to the Site Content And Structure tool within the Sharepoint site. Go to Style Library, then to Images.  Upload your new graphic, then overwrite the default graphic for each style (bl_logo, blk_logo, gr_logo).
Alternatively, go to the Style Library and change the background-image:url in the .logo style for each of the styles (Black, BlackGlass, Blue, BlueGlass, Green, Green Glass) and in the en-us/*.css files where * is each master page template you are using in the site.

Note: You only have to change the style you plan to implement.

2. If using a different sized image:
__________________________________________________
You will need to modify the style sheet elements in the master page style sheet en-us/*.css file. 

The following is an example for a 238×33 logo in TopNavFlyouts.css:

.topArea
{
 background:url("../../images/bl_band.jpg") no-repeat;
 background-position:top right;
 padding-left:10px;
}
.topArea :active
{
 text-decoration:none;
}
.logo
{
    background-image:url("../../images/kieferlogo.png");
 background-repeat:no-repeat;
 background-position:left center;
 font-size:14pt;
 padding-top:16px;
 font-family: tahoma;
 height:38px;
}
.logo a
{
 color: #656B77;
 padding-left:245px;
}