Hello, I have setup a couple of managed paths in my initial portal. They are search and personal. I have created two site collections through central administration. The first is a Search Center template mapped to the search path, http://portal/search, and the other is a My Site Host which is created at this path, http://portal/personal/host. The problem is that when you attempt to browse to these sites, even immediately after creation, I receive a 404 error. I have attempted the following to attempt to resolve this issue: Delete / Recreate Site Collection Created New Managed Paths (searchcenter) Reset IIS Rebooted Server Reviewed Logs (Only information is that it is unable to find site at URLs listed above) I am unsure what else to do at this point to resolve the issue and would greatly appreciate any assistance! Thanks!-Bagles1

What type of managed paths are you creating? Wildcard or Explicit?John SharePoint911: SharePoint Consulting Blog: http://www.rossonmoss.com Twitter: JohnRossJr MOSS Explained: An Information Workers Deep Dive into Microsoft Office SharePoint Server 2007

The search center path is an Explicit managed path and the personal path is a Wildcard managed path. -Bagles1

Can you get to the root site? In your example that would be http://portal John SharePoint911: SharePoint Consulting Blog: http://www.rossonmoss.com Twitter: JohnRossJr MOSS Explained: An Information Workers Deep Dive into Microsoft Office SharePoint Server 2007

Yes, I am able to get to the main portal, create sites, pages and other sharepoint objects. I just can't get to any of the managed paths I create. Quite bizarre!-Bagles1

If you go to your list of site collections do you see the site collections listed? Is it possible that there might be an issue with an AAM? Just guessing here :-)John SharePoint911: SharePoint Consulting Blog: http://www.rossonmoss.com Twitter: JohnRossJr MOSS Explained: An Information Workers Deep Dive into Microsoft Office SharePoint Server 2007

I am able to see it in the list. I can live without the search center being a managed path but not sure how to get around the My Sites problem. Thoughts, suggestions or guesses? ;o)-Bagles1

Normally when you create an SSP a My Site Host is created automatically. Do you not already have one? Are you sure this isn't an AAM issue?John SharePoint911: SharePoint Consulting Blog: http://www.rossonmoss.com Twitter: JohnRossJr MOSS Explained: An Information Workers Deep Dive into Microsoft Office SharePoint Server 2007

Hi John, I think there may be a misunderstanding. There is no SSP, I am working in a SP2010 environment. I don't believe this is an AAM issue, but to be sure I will explain the AAMs I have defined. AAMs: default : http://portal.domain.com intranet: http://portal Managed Paths: / sites search personal Site Collection Lists: / /search /personal/host Upon clicking on the Site Collection link it displays on the right: http://portal.domain.com/search. Entering that link into the browser results in a 404 error. I will gladly post other information if you need it. Thanks for all your help! -Bagles1

Just to be clear -- this question was posted in the pre-SP2010 Admin forum so I think you can understand why I assumed there might be an SSP involved. Are you trying to get to this URL directly from the server or from a remote machine?John SharePoint911: SharePoint Consulting Blog: http://www.rossonmoss.com Twitter: JohnRossJr MOSS Explained: An Information Workers Deep Dive into Microsoft Office SharePoint Server 2007

Hi John, I have tried to access the paths from a couple different computers, all unsuccessfully. Any place else you would suggest I look for clues on what might be wrong? Thanks!-Bagles1

Personally, I've never had issues with managed paths at all. If you are able to access the root site just fine, and the site collection is listed in the list of site collections I can't imagine what the issue would be. You could always try deleting and recreating. Make sure AAMs and DNS are setup correctly -- ping the site and make sure the correct IP comes back Normally after you create a site colleciton it opens shows a link to the newly create site collection. Does that fail too? Try creating a new web application and see if you can add a managed path to it or if you get the same behavior.John SharePoint911: SharePoint Consulting Blog: http://www.rossonmoss.com Twitter: JohnRossJr MOSS Explained: An Information Workers Deep Dive into Microsoft Office SharePoint Server 2007

Hi, We are seeing the same thing that Bagles1 is describing at a client site. We can open the root site fine and everything is nominal on all servers (2 WFE | 2 APP). But we always get a 404 whenever we try to connect to a site under a managed path. We can see the managed paths and the site collections perfectly in Central Administration, it looks like everything should work. But when you navigate to the link after the creation of a site using a manged path, it just 404s on us. Was anything else discovered concerning this problem? ~JC

What's the output look like if you access the site with Fiddler running?John Ross SharePoint Server MVP | Sr. Consultant SharePoint911: SharePoint Consulting Blog: http://www.sharepoint911.com/blogs/john Twitter: @JohnRossJr Professional SharePoint 2010 Branding and User Interface Design

What's the output look like if you access the site with Fiddler running? John Ross SharePoint Server MVP | Sr. Consultant SharePoint911: SharePoint Consulting Blog: http://www.sharepoint911.com/blogs/john Twitter: @JohnRossJr Professional SharePoint 2010 Branding and User Interface Design Hi John, thanks for the response. We are attempted to stand up a large production farm at a city agency and they correctly will not allow us to install debugging tools in environment. I can tell you that we have had some hiccups with setup along the way, but have managed to move forward until this problem. I am confident we can figure it out given the time, but since this post practically mirrored the symptoms we are experiencing, I figured I would fish for a possible solution. At the moment we are running a day 1 farm of 2 WFE and 2 APP servers. We have installed our services and everything seems to be running correctly. We have a root site on port 80 @ http://server/ and we can access it with no problem. When we add a site collection to the application (http://server/sites/sitename), the site provisioning tool runs and produces a successful result message with the url link to the collection(we can also see the new site collection listed in the site collection manifest under the application); but when we click on it we get a 404 error message. ~JC

Fiddler installs on the client machine. They won't let you even do that? As debugging tools go there is almost no risk to the server -- no more so than with IE. All it does is watch the packets that are sent to-from the server via IE. I'd be interested to see if there are any packets being received at all.John Ross SharePoint Server MVP | Sr. Consultant SharePoint911: SharePoint Consulting Blog: http://www.sharepoint911.com/blogs/john Twitter: @JohnRossJr Professional SharePoint 2010 Branding and User Interface Design

Had the same issue: You need to create a site collection on this location after you created the managed path. Go figure . .