Timeline for My Site creation failure for user after moving My Sites to dedicated web application
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 29, 2013 at 18:17 | vote | accept | John Adams | ||
| Feb 8, 2013 at 12:54 | comment | added | Matthew McDermott | Yes, you only need a different host header. You get separation of content DBs with the new web application. Glad you found a solution. | |
| Feb 5, 2013 at 17:08 | answer | added | John Adams | timeline score: 0 | |
| Feb 5, 2013 at 16:58 | comment | added | John Adams | @Matthew McDermott - Thanks for your input. My intent for choosing a different port (rather than 80) was to isolate all MySite content in a separate content database. My managed path for mysites has always been of the wildcard type. Are you saying I could have achieved a separate content database for this new web app using the same port 80 as my default Sharepoint - 80? That is, are you saying I could have 2 content DBs (2 web apps) - Sharepoint - 80 and SharepointMySites - 80 (with the latter defined with one managed path?). Ultimately, the port did me in (see my answer below). | |
| Feb 1, 2013 at 16:10 | comment | added | ghangas | I would look at the perms for the DB. You may have added one user, but does the application pool user have all the rights it needs to the DB? | |
| Jan 31, 2013 at 13:36 | comment | added | Matthew McDermott | So there are a couple things I see. First why create the web app on a port (8080) rather than port 80? Second is your my site managed path an explicit managed path? Usually the personla managed path is a wildcard MP under the explicit MP (If you configure it that way.) My preference, though, is to use the root for the My Site Host and then create the personal managed path under that. | |
| Jan 29, 2013 at 23:36 | history | asked | John Adams | CC BY-SA 3.0 |