MOSS 2007 – Unable To Delete SSP

Attempting to delete SSP using the ‘Shared Services Administration’ section of Central Administration (or using stsadm) results in the error message:

“An object in the SharePoint administrative framework, “SharedResourceProvider Name=SSP Parent=SPFarm Name=MOSS”, could not be deleted because other objects depend on it. Update all of these dependants to point to null or different objects and retry this operation. The dependant objects are as follows: ProjectPSISharedApplicationTimerJob Name=Project Server Synchronizing Job for ‘SSP’ Parent=ProjectApplicationService Name=ProjectApplicationService”

The solution to this problem is to delete the dependant object!

First find the GUID of the dependant object:

SELECT *
FROM [Sharepoint_Config].[dbo].[Objects]
WHERE name like ‘Project Server Synchronizing Job for %’

Now delete the dependant object using stsadm:

stsadm -o deleteconfigurationobject -id “YOUR_GUID_HERE”

Attempt to delete the SSP again!

Similar solutions found online: http://sharepointmadeeasy.blogspot.com/2008/08/unable-to-delete-shared-services.html

MOSS 2007 – The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID

Problem

Messages in the event log:

The application-specific permission settings do not grant Local
Activation permission for the COM Server application with CLSID
{61738644-F196-11D0-9953-00C04FD919C1}
and APPID
{61738644-F196-11D0-9953-00C04FD919C1}
to the user xxxx\xxxxxxx SID (S-1-5-21-203257084-1554538351-1551923841-31371)
from address LocalHost (Using LRPC). This security permission can be modified using
the Component Services administrative tool.

Background

61738644-F196-11D0-9953-00C04FD919C1 is the IIS WAMREG admin service.

If you are seeing a different CLSID, fire up regedit and search for the CLSID.

Solution

Open Component Services
Find the IIS WAMREG admin service
Right click, Properties, Security Tab
Grant launch and activate permissions to the account mentioned in the error message

iisreset

MOSS 2007 – Access Denied! Only site admin can access Data Source object from user profile DB

Problem

A runtime exception was detected. Details follow.
Message: Access Denied! Only site admin can access Data Source object from user profile DB.

Techinal Details:
System.UnauthorizedAccessException: Access Denied! Only site admin can access Data Source object from user profile DB.
at Microsoft.Office.Server.UserProfiles.SRPSite.AdminCheck(String message)
at Microsoft.Office.Server.UserProfiles.DataSource._LoadDataSourceDef(IDataRecord rec)
at Microsoft.Office.Server.UserProfiles.DataSource._LoadDataSourceDef(String strDSName)
at Microsoft.Office.Server.UserProfiles.DataSource..ctor(SRPSite site, Boolean fAllowEveryoneRead)
at Microsoft.Office.Server.UserProfiles.DataSource..ctor(SRPSite site)
at Microsoft.Office.Server.UserProfiles.UserProfileConfigManager.GetDataSource()
at Microsoft.Office.Server.UserProfiles.BDCConnector.RefreshConfiguration(String sspName)

Solution

Grant ‘Manage user profiles’ and ‘manage permissions’ to the ‘Farm search service account’.

Similar solutions on the web:

http://www.raregrooverider.com/post/2008/03/12/Office-SharePoint-Server-Error-Event-ID-7888.aspx

http://social.technet.microsoft.com/Forums/en-US/sharepointadmin/thread/9ea7f691-a6ec-4b71-b0f2-733032b6ac22

MOSS 2007 Access Denied When Accessing SSP Admin Site

Problem

Browsing to some of the SSP Admin pages yields:

401 UNAUTHORIZED
or ACCESS DENIED
or prompts continuously for a user name

I first came across this problem after restoring an SSP from a backup.

Solution

The SSP service account needs to be granted permissions in the following places:

Central Admin -> Application Management -> Site Collection Administrators

SSP Admin -> Personalization Service Permissions (All)

Central Admin -> Application Management -> Policy for Web Application (Full)

MOSS 2007 Move SSP to another farm

Move An SSP To Another Farm

Use the Technet article Microsoft Technet – Move an SSP to another farm.

The five basic steps are:

Back up the original SSP
Restore the SSP to a new farm
Restore SSP associations and configure the SSP
OPTIONAL – Configure the restored SSP on the new farm to be the default
OPTIONAL – Delete the original SSP

Backup the SSP

Follow the Microsoft instructions.

Also see ../BackupSsp

Restore the SSP to a new farm

Follow the Microsoft instructions.

‘YOU ARE HERE’

Errata

5b – New Configuration!
5c – Use new database names to avoid overwriting existing

Additional

The restore will hang at 90% with lots of errors in the event log
Don’t worry – it has restored the databases and that’s all we need
Cancel the restore.
Delete the restored SSP (not the databases)

See ../UnableToDeleteSsp

Delete the restored SSP Web Application from Central Admin -> Delete Web Application

Restore SSP associations and configure the SSP

Follow the Microsoft instructions.

Additional

Access Denied when accessing SSP Admin site

Set SSP as default on the new farm

Follow the Microsoft instructions.

Delete the original SSP

Follow the Microsoft instructions.

Additional

Unable to delete SSP
Delete the Web Application for the SSP

MOSS 2007

MOSS 2007

/Devel

Procedures

Move an SSP to another farm

Problems (and Solutions)

Access Denied when accessing SSP Admin Site

Access Denied! Only site admin can access Data Source object from user profile DB

The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID

Unable to Delete Shared Services

foo

Mysite is unavailable – 404 error

stsadm -o backup gives error 5

stsadm -o restore gives The server principal x is not able to access the database x under the current security context

PDF Icon is Missing

Interesting Articles

Configure Mysites to appear under http://portal/personal/

Filename Restrictions

Sharepoint does not like filenames to contain certain characters:

Joel is a reputable source, with an exhaustive review:

http://blogs.msdn.com/joelo/archive/2007/06/27/file-name-length-size-and-invalid-character-restrictions-and-recommendations.aspx

The official microsoft reference is:

http://support.microsoft.com/default.aspx?scid=kb;en-us;905231

User Profiles

LDAP Filter for user profile import

Official Resources

http://blogs.msdn.com/sharepoint/

http://suguk.org/

The marketing site – http://sharepoint.microsoft.com

Disaster Recovery

Restoring SSP using stsadm -o restore

The server principal x is not able to access the database x under the current security context.

Solution: The user who is performing the restore (i.e. who is logged into the desktop) needs to be a member of the sysadmin role on the sql server.

Best Practice on Backups

http://blogs.msdn.com/joelo/archive/2007/07/09/best-practice-on-backups.aspx

Export User Profiles

This one only works if you have a fully working Shared Services Provider

http://userprofileimport.codeplex.com/

Export Audiences

http://stsadm.blogspot.com/2009/04/exporting-audiences-using-stsadm.html

http://stsadm.blogspot.com/2009/04/importing-audiences-using-stsadm.html

stsadm -o deletesite gives (Exception from HRESULT: 0x80070003)

So someone accidentally deleted a site collection (/sites/banana). I attempted to stsadm -o restore but got scared and cancelled it with Ctrl+C. Bizarrely, the site collection (/sites/banana) is still shown in the Central Administration Site Collection List, but without any information in the right hand panel.Presumably the database is corrupt in some way.

I want to delete the site collection so stsadm -o deletesite -url http://intranet/sites/banana but it says Exception from HRESULT: 0x80070003)

A quick google for Exception from HRESULT: 0x80070003) gives:

http://geekswithblogs.net/naijacoder/archive/2008/05/20/122283.aspx

The Technet reference for databaserepair: http://technet.microsoft.com/en-us/library/cc288636.aspx

So lets see what sites are orphaned: stsadm -o databaserepair -url http://intranet/sites/banana -databasename wss_content_banana

Lets delete the orphaned sites: stsadm -o databaserepair -url http://intranet/sites/banana -databasename wss_content_banana -deletecorruption

But that doesn’t work.

Lets try detaching and reattaching the content database.

This strategy is backed up by:

https://blogs.msdn.com/subhajitc/archive/2008/09/14/how-to-delete-corruption-orphaned-records-from-the-content-databases.aspx

http://blogs.technet.com/corybu/archive/2007/05/31/sharepoint-orphans-explained.aspx

stsadm -o preparetomove -contentdb wss_content_banana -site http://intranet/sites/banana

And remove database from farm:

stsadm -o deletecontentdb -url http://intranet/sites/banana -databaseserver wss_content_banana -databasename wss_content_banana

When you’re ready to reattach your database to the farm follow this only step:

stsadm -o addcontentdb -url http://intranet/sites/banana -databaseserver sqlserver1 -databasename wss_content_banana

Move a Sharepoint Site

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

Move a Sharepoint Document Library and Preserve Metadata

There are two inferior methods for copying data between document libraries or lists:

Using the explorer view to copy items from one tother
Creating list or library templates

These methods are inferior as they do not preserve the ‘Created By’, ‘Last Modified By’, etc. metadata.

Here is a method for moving the data whilst preserving its metadata:

Create a blank list or library as the destination
Goto the ‘Site Content and Structure’ page
Navigate to the source list or library
Select every item in the source list or library

Actions -> Move
Select your destination list or library
OK

Henry also uses this technique:

http://blog.henryong.com/2008/01/21/how-to-movemigrate-sharepoint-list-itemsdocuments-and-preserve-metadata-properties-at-the-same-time/

stsadm -o backup gives Error 5

http://www.davehunter.co.uk/Blog/Lists/Posts/Post.aspx?List=f0e16a1a-6fa9-4130-bcab-baeb97ccc4ff&ID=34

Your UNC backup folder needs to be SHARED and sharepoint service, central admin apid, sql server service need to have read/write on that share.