SP2010 Beta 2: MySite's Organization Browser Silverlight crashes browser

Problem:
When trying to access Organization tab on My Profile page in SharePoint 2010 My Site, the Organization Browser Silverlight control partly loads, but soon freezes the browser, and consumes all available CPU (well, on multi-core CPUs only one core, to be exact). Only option is to kill browser process and stay away from the Organization Silverlight.

Thoughts:
When looking at the HTTP traffic using Fiddler, I noticed that page Silverlight control loading seemed to halt more or less immediately after querying information of a same specific individual using /MY/_vti_bin/SilverlightProfileService.json/GetUserSLProfileData.

Solution:
So, I went to the profile of this user and found out that if a person is a Manager of himself/herself, the Silverlight control will crash. It is probably going into some never-ending loop. In my case the problematic user was the most top-level manager. After I modified the profile of this user in Central Admin and cleared the manager field, Organization control started working.

SP2010 Beta 2: Error occurred during the processing of /my/default.aspx or /my/personcontent.aspx

Problem:
When you modify My Site master page (mysite.master) either using SharePoint Designer 2010 (SPD), or by creating new master page and setting your custom master page as Custom Master Page using SPD, you will end up with error when trying to access My Network page. You are not using any server side code blocks in your master page. In fact, you only need to create a new version of the default mysite.master without modifying it, and publish the new version, to get this error.

The error you see is: An error occurred during the processing of /my/default.aspx. Code blocks are not allowed in this file.

You might also get the same error from file /my/personcontent.aspx.

Solution:
You need to modify web.config and add the following PageParserPath (although you are not using inline code in your master page):

<SharePoint>
<PageParserPaths>
<PageParserPath VirtualPath="/my/default.aspx" CompilationMode="Always" AllowServerSideScript="true" />
</PageParserPaths>
</SharePoint>

SP2010 Beta 2: Access Denied when accessing My Content

Problem:
When trying to access My Content section in MySite in SharePoint 2010 Beta 2, you get error:

There has been an error creating the personal site. Contact your site administrator for more information

Furthermore, you get these errors in Application Event Log:

Log Name: Application
Source: Microsoft-SharePoint Products-SharePoint Foundation
Date: 11.1.2010 12:54:21
Event ID: 6141
Task Category: Topology
Level: Error
Keywords:
User: DOMAIN\SPFarmAdminAccount
Computer: mycomputer.domain.com
Description:
The site /my/personal/palojus could not be created. The following exception occurred: Access denied..

and

Log Name: Application
Source: Microsoft-SharePoint Products-SharePoint Portal Server
Date: 11.1.2010 12:54:21
Event ID: 5187
Task Category: Administration
Level: Error
Keywords:
User: DOMAIN\palojus
Computer: mycomputer.domain.com
Description:
My Site creation failure for user 'domain\palojus' for site url 'http://communities.domain.com/my/personal/palojus'. The exception was: Microsoft.Office.Server.UserProfiles.PersonalSiteCreateException: A failure was encountered while attempting to create the site. ---> System.Security.SecurityException: Access denied.
at Microsoft.SharePoint.Administration.SPPersistedObject.BaseUpdate()
at Microsoft.SharePoint.Administration.SPJobDefinition.Update()
at Microsoft.SharePoint.Taxonomy.TaxonomyFeatureReceiver.EnsureHiddenListFullSyncTimerJob(SPWebApplication webApplication)
at Microsoft.SharePoint.Taxonomy.TaxonomyFeatureReceiver.FeatureActivated(SPFeatureReceiverProperties properties)
at Microsoft.SharePoint.SPFeature.DoActivationCallout(Boolean fActivate, Boolean fForce)
at Microsoft.SharePoint.SPFeature.Activate(SPSite siteParent, SPWeb webParent, SPFeaturePropertyCollection props, Boolean fForce)
at Microsoft.SharePoint.SPFeatureCollection.AddInternal(SPFeatureDefinition featdef, Version version, SPFeaturePropertyCollection properties, Boolean force, Boolean fMarkOnly)
at Microsoft.SharePoint.SPTemplateAssociationElement.EnsureTemplateAssociatedSiteFeaturesActivated(SPSite site, String sTemplateName)
at Microsoft.SharePoint.SPFeatureManager.<>c__DisplayClass16.
...
The Zone of the assembly that failed was:
MyComputer
...

Thoughts:
1. Granting direct access to the user (in addition to obviously already having access via NT AUTHORITY\Authenticated Users) didn't have any effect.


2. Verifying My Site Settings (Central Administration --> Manage Profile Service --> User Profile Service Application --> My Site Settings --> Setup My Sites) didn't have any effect, as the settings were already correct.

Solution:
In My Site Settings (Central Administration --> Manage Profile Service --> User Profile Service Application --> My Site Settings --> Setup My Sites), I changed My Site Host slightly (".../my/" to ".../my2/").


Then I tried accessing My Content again, and My Site was created successfully. Finally I changed My Site Host back to original value and got some flash-backs from the good old MOSS times when many things didn't work, and suddenly they just started to work. Some things never change.