Carolramzy's Blog

DPM Cataloging to Recover SharePoint Items / DPM 2010 Backup Sharepoint to item level

carolramzy — Tue, 15 Jun 2010 09:15:05 +0000

When Backup Sharepoint 2007 , DPM catalougue MOSS items every 24 hours , if you need to force this operation to be able to restore item you can use powershell command , but the one written on technet is very tricky

http://technet.microsoft.com/en-us/library/ff634233.aspx

Start-CreateCatalog –DataSource so if you write this command and try any values for datasource will give error:

error: cannot bind parameter ‘datasource’ cannot convert the ‘…’ value of type ‘system.string’ to type microsoft.internal.enterprisestorage.dls.UI.cmdlet.protectioncmdlets.createcatalogcmdlet

this is how to enter the command, you must enter your datasource as variable, use the below

$pg1 = get-protectiongroup –dpmservername yourdpmservername

$ds1 = Get-Datasource –ProtectionGroup $pg1

start-createcatalog -datasource $ds[1]

DPM will start catalogue

SCSM beta console doesnt open giving failed to connect to server insufficient privilege

carolramzy — Thu, 18 Jun 2009 10:31:44 +0000

after installing SCSM beta when you try to open the service manager Console pop up error

error: System center service manager : failed to connect to server insufficient privileges, the user does not have sufficient permission to perform the operation

Microsoft.EnterpriseManagement.Common.UnauthorizedAccessMonitoringException

Reason: during installation all Service manager Services use domain services accounts In this configuration, the installation queries Active Directory Domain Services (AD DS) for the computer account .In a large Active Directory domain, this query may time out before AD DS returns the queried data.

Resolution:

1- open start> run>services.msc

2- change service account of servicemanager config service to local system

3- change services account of servicesmanager SDK service to local system

4- Restart Both services

open service manager console and the error is gone

Creat MySite under your Domain url with same DNS name /mysite

carolramzy — Wed, 17 Jun 2009 08:35:10 +0000

When you install MOSS (not evaluation copy) part of that process is creating a Shared Service Provider. This is essentially a set of services like User Profile store, Search, BDC, MySites etc… These services can be consumed from one or more SharePoint Web Applications (and other apps outside of SharePoint if you like).

One of the services that an SSP provides is details on where users MySites are located. This is because if you have, for example, multiple Portals then you usually only want a person to have one MySite. So by having multiple web applications consuming from one SSP you can achieve this.

However, by default when you create an SSP the MySite location is set to be under that SSP. I think an example will help here…

E.g.

Your organisational portal site is on http://OrgsIntranet

Your SSP must be on another URL domain or port so let say… SSP1 is on http://OrgsIntranet:12345

What this will mean, by default, is that your users MySites are at http://OrgsIntranet:12345/personal/

As you can probably imagine, this is not ideal for all organizations. In fact for most organizations that will only ever have one main portal this is not ideal.

The reason we host MySites on another web application is so that no matter what site you are on, when you hit the “mysite” link at the top of the page, it will take you to the right place and that place is not dependant on any individual portal.

In an ideal world you would have an address like http://my or http://mysites as a DNS name for your SSP … so that the address makes sense and you could run it on port 80 like everything else. It makes the URL look nicer I guess.

Anyway! So for orgs with only one main portal they might want their urls to look something like:

Org Main portal: http://OrgsIntranet

MySites : http://OrgsIntranet/personal/

So how do you go about configuring this? …

How-To:

I am assuming you have your intranet/portal at http://OrgsIntranet and the mysites location is currently at http://OrgsIntranet:12345/personal/

First you have to make sure you have 2 managed paths set up in the http://OrgsIntranet web application. To do this jump into central admin, “Application Management” tab, “Define Managed Paths”. Make sure you are working on the right web application once you are in that screen.
Create an Explicit inclusion for path “mysite”
Create a Wildcard inclusion for path “personal”
Jump back into the “Application Management” tab & choose “Create site collection”
Create a new site (call it MySiteHost if you like), pick “Create site that this URL” and choose “mysite”, also pick the “My Site Host” template (important).
Once that site is created jump back into Central Admin, go into your Shared Services Provider configuration, go into the “My Site settings” page
Set “Personal site provider” to “http://OrgsIntranet/mysite/” and “Location” to “personal”, click OK.

Done! Now when your users click on the “mysite” link their MySite will be created in the right place.

NOTE: if you do this after some mysites have been created then you will have to move them using STSADM to the new location. Otherwise a new mysite will be created for them.

Unable to delete default Shared Services Provider in SharePoint

carolramzy — Wed, 17 Jun 2009 08:15:32 +0000

Sometimes The SSP you create in MOSS are not created properly. This can be result of interruption while SSP was being created or in result of bad migration from SPS03 or MCMS to MOSS.
error: An object in the SharePoint administrative framework, “SharedResourceProvider Na
me=SSP Parent=SPFarm Name=SharePoint_Config”, could not be deleted because other
objects depend on it. Update all of these dependants to point to null or diffe
rent objects and retry this operation. The dependant objects are as follows:
SPWebApplication Name=SSP_MYSITE Parent=SPWebService
SPWebApplication Name=SSP2 Parent=SPWebService
SPWebApplication Name=super.company.com Parent=SPWebService
Resolution:
To get rid of the dependencies, you will have to use a trick:
Open SQL Server Management Studio and execute following query to fetch the SSP dependencies:
SELECT * from Objects WHERE Objects.name like ‘%SSP%’
Note that in the “Status” column, you’ll find “3″. Changing that back to default “0″ does the job:
UPDATE Objects SET Objects.Status=0 WHERE Objects.name=’SSP’

You should delete the SSP using stsadm command line tool (NOTE: My SSP’s name is “SSP” which is specified after “title” in command:

C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN>stsa
dm -o deletessp -title “SSP”

Your currupt SSP is gone!

Now you should be able to create a new SSP without problems

Hello world!

carolramzy — Wed, 17 Jun 2009 08:02:46 +0000

Welcome to WordPress.com. This is your first post. Edit or delete it and start blogging!