My sites not creating site collections

Question

Steps 1) Created a web application https://site.

2) Configured user profile ,search and metadata.

3) Created a Team site collection at the root i.e.https://site

4) Create a Explicit path at 'my'

5) Created a wildcard path at my/personal'

6) Created mysite host site collection at https://site/my/personal.

7) Configured Self Site Creation and set the path to https://sites/my/personal[%usersid%]

8) Under Setup my sites in User profile service application I have set the MySite Location to My/personal.

9) The user profile site collections are not created. I have enabled self site creation using the ui and powershell for the web application.

The my sites opens but the site collection for the user is not created. It points to https://site/my/personal/person.aspx

10) Set the thumbnailphoto property for the picture and ran a full synch

11) The import worked after 3 to 4 full synch

12) In MIISCLIENT.EXE when the sync runs it shows connections successful but o adds or deletes for the export.

Answer 1

Couple of steps required in order to configure the MySites.

• Make Sure UPS & MMS are up and running.
• Create a Web application and create root site collection with MYSiteHost template
• in the Mysite Host location at UPA, give the root level site collection address
• then set the permissions.
• Enable Self-Service Creation

read more over here: http://sharepointgeorge.com/2010/configuring-my-site-sharepoint-2010/

Answer 2

You need to create a wildcard managed path named "/my/personal". Having your Personal site host in /my/personal is not a functional design. It should be the root site collection of your web application.

Answer 3

I created the Mysites using a powershell script

 $site=new-object Microsoft.SharePoint.SPSite($MySiteRootURL);            
 try            
 {            
  $serviceContext = Get-SPServiceContext $site;            
  $upm = new-object Microsoft.Office.Server.UserProfiles.UserProfileManager($serviceContext);             
  if($upm.UserExists($Username) -eq $false)            
  {            
   Write-Host "User $Username was not found in the profile store." -f yellow;            
   return;            
  }            
  $userProfile = $upm.GetUserProfile($Username);            
  if($userProfile.PersonalSite -eq $Null)            
  {            
   Write-Host "Creating MySite for user $Username" -f darkyellow;            
   $userProfile.CreatePersonalSite();                  
   Write-host "Successfully created MySite for user $Username" -f green;            
  }            
  else            
  {            
   Write-Host "User $Username already has a MySite." -f darkgreen;            
  }            
 }            
 catch            
 {            
  Write-Host "Encountered an error creating a MySite for user $Username. Error:"$_.Exception -f Red;            
 }            
 finally            
 {            
  $site.Dispose();            
 }

Answer 4

Certainly Technet seems to suggest that this is achievable though I haven't seen it. Have you got a test farm which you can try things out on?

Anyway I think the issue is that the user profile service app doesn't have the right location as to where to create my sites.

I would do the following:-

Test config out in test farm first

Remove existing my site host site collection

Create new explicit manaGed path /my so you have https://site/my

Create my site host site collection at https://site/my

Check user profile settings for where users my sites are created default to /personal or in your config https://site/personal

My site host is changed to https://site/my/

Check that users have permissions in user profile service app to create a my site (manage permissions link)