My Site as separate web application

By -
During the configuration of the SharePoint site, per Scot Hillier's book you are instructed to set up the Shared Services Provider creating separate Web Applications for the Shared Services (on port 8080) and Personal sites (on port 8081).

Once I did this I continued on until I got to the Shared Services section of the book (chapter 4) and began playing with the My Site feature. The first thing I noticed (after enabling Self Service Site creation) was that each My Site I tried to create (as various different users) would fail. I began digging through the Central Admin and went to the Shared Services administration. On the 'User Profile and My Sites' section, click the 'My Site Settings' link and ensure that in the 'Personal Site Services' section the 'Personal Site Provider' is your Web Application you indicated as your Personal Sites Application (if you followed the book's instructions in setting up Shared Services it should be the app on port 8081). That got the mysites working for me (from the same domain - read on if you are accessing from outside the domain).

In my test environment, I have the client PC that I access my MOSS installation outside of the domain that the SharePoint Server is in. In order to get the My Site feature fully working in this setup I had to provide alternate access mappings in Central Administration for the Personal Sites Web Application (again if you followed Hillier's setup it should be on port 8081) so that external clients are told to go to a URI that they can access.

Comments

Anonymous said…
I have a similar problem. When a new Web application is created to host My sites, any username links from central web application do not goes to corresponding My site.
Only the link My site works well.
Alternative access mappings is set appropriate.
What is missing?
May 6, 2007 at 9:25:00 AM PDT
Paul said…
I'm having a little trouble understanding what you mean. Are you saying that when you click the my site link it works?
May 15, 2007 at 1:44:00 PM PDT
Post a Comment

Popular posts from this blog

Programmatically Update Page Layouts

By -
I updated my page layouts that I deployed as a feature, but found that I could not overwrite the Layout File. The solution was to add a new page layout and then you would have to associate the new layout with every page on your site that used it. Obviously with a site of any size you'd have a lot of manual work to get this done, so doing it programmatically makes for a much better (and thorough) approach. After you've got your new page layouts, you could do something like this (in your event receiver class): public override void FeatureActivated(SPFeatureReceiverProperties properties) { //replace current page layouts with new page layouts on all pages SPWeb web = SPContext.Current.Web; SwapPageLayout(web, "FullWidthContentWithTitleV1.aspx", "FullWidthContentWithTitleV2.aspx"); } private void SwapPageLayout(SPWeb web, string oldPageLayoutName, string newPageLayoutName) { PublishingWeb pubWeb = PublishingWeb.GetPu...
Read more

Microsoft Virtualilzation Headaches

By -
As a SharePoint consultant, I am constantly moving from client to client and the best way to develop and test the code, designs and configurations for each client while maintaining complete separation is to virtualize. Since I work for a Microsoft partner, we try to use Microsoft tools and technologies as much as possible, which can be quite frustrating, as you will find out below. I recently started working for a large client with a global presence whose IT policies are well-established, difficult to change and not always up-to-date. In that vein, enter the corporate VPN: it's a web-based signin with a host checker that doesn't support any x64 OS. This prompted me, running Win 7 x64, to try to get a co-worker's Hyper-V Win2k3 x86 MOSS VM and run it in Windows Virtual PC . Seems like a logical thing to do, right? I mean, a Microsoft VHD should work, and be able to be imported by other Microsoft tools, right? Wrong. After spending quite a bit of time trying to attach the VHD...
Read more

ERROR: Failed to create feature receiver...

By -
I was working on a STSDev project which deployed a feature with a feature receiver. I had the feature working without the FeatureReceiver but as soon as I added the FeatureReceiver related attributes to my <Feature> element I got the following error: Failed to create feature receiver object from assembly "Org.Project.Solution, Version=1.0.0.0, Culture=neutral, PublicKeyToken=c632353d405b3209", type "Org.Project.Solution.MyFeature.FeatureReceiver" for feature 6a9b2358-ea4e-486d-a4e4-4f813c52ce88: System.ArgumentNullException: Value cannot be null. Parameter name: type at System.Activator.CreateInstance(Type type, Boolean nonPublic) at System.Activator.CreateInstance(Type type) at Microsoft.SharePoint.Administration.SPFeatureDefinition.get_ReceiverObject() After much digging around I discovered that STSDEV's Solution config file refers to a namespace as well as the dll. My FeatureReceiver's namespace was not prefixed with the right namespace So just...
Read more