Content Query webpart breaks when visit sharepoint site with FQDN

So here's a new one sports fans, was adding a custom content query webpart for a link list i made, visited the site on a test box to see how it looked and got this when i visited the site using the fully qualified domain name (that is http://intranet.ourdomain.org instead of just http://intranet)

Unable to display this Web Part. To troubleshoot the problem, open this Web page in a Windows SharePoint Services-compatible HTML editor such as Microsoft Office SharePoint Designer. If the problem persists, contact your Web server administrator.
Since my page was bound to a page layout, i tried to reproduce the error on another page, and got this error when publishing (using a FQDN):

The operation failed because the following URL does not correspond to a SharePoint site collection: http://intranet.domain.org/_layouts/IniWrkflIP.aspx.
Ah! Now we are getting somewhere! So lets look up this problem! Found out it has to do with the Access mappings on the server not being configured correctly. Even tho the site is set up inIIS and you can visit and see the site, you have to now tell sharepoint directly that hey, yes, people will be visiting you through a FQDN.

An artical on Todd Klindt's Blog outlines why this is such a headache for old admins (not me!) to figure out and how to set it up.
http://www.toddklindt.com/blog/Lists/Posts/Post.aspx?ID=39

Basic walk-through?
1. Central Administration
2. Operations
3. Alternate Access Mappings
4. Select the server giving you trouble on the right
5. Add internal URLs
6. Select internet, put in the Fully qualified domain name, click ok

Problem solved!


Comments

Post a Comment

Popular posts from this blog

CI Build broke after nugit update

One of those moments where your heart drops : Your using CI on a remote hosting service (like AppHarbor) and your build fails. You look into the fail reason and find out it is because you updated the packages in your build. Wait, my update from nuGet broke everything?! Wtf?! The error looks something like this, putting it in here for search engine's : Build started 6/10/2013 12:30:20 AM. 1>Project "D:\temp\xly5bsff.qvp\input\.sln" on node 1 (default targets). 1>ValidateSolutionConfiguration: Building solution configuration "Release|Any CPU". 1>Project "D:\temp\xly5bsff.qvp\input\.sln" (1) is building "D:\temp\xly5bsff.qvp\input\\.csproj" (2) on node 1 (default targets). 2>D:\temp\xly5bsff.qvp\input\\.csproj(880,3): error MSB4019: The imported project "D:\temp\xly5bsff.qvp\input\packages\Microsoft.Bcl.Build.1.0.7\tools\Microsoft.Bcl.Build.targets" was not found. Confirm that the path in th
Read more

Sharepoint 2007 - Access Denied when you try to edit

I'v had this solution for a little while now but never wrote it down anywhere for people to see. Here is the situation: In a site collection, you make a new list/document library in any sub-site or the main website. You then add a new item/document to the folder, and then attempt to edit the item You then see something along the lines of "Access Denied" , even if you are on the system account. This happens with every new list you create on any site or subsite. Your problem is a corrupted field definition at the site collection level. Specifically the "Effective Permissions Mask" is missing an attribute in it's xml scheme - RenderXMLUsingPattern="TRUE" The fix comes in 3 steps: 1. Update your server to the most recent cumulative update package (Service pack 2 or greater). You can get more information about this from the Sharepoint team blog post on SP2 . Included in SP2 is a hotfix that prevents this from occurring ever again on any other site co
Read more

Project 2010 and Project Pro 2007

Just a FYI since no one knew this from what i can tell already: If you are enabling BCM (Backwards Compatibility Mode) for project 2007 to connect to Project Server 2010, there are a few things you should know first. Right off the bat, clients have to be updated to Service Pack 2 . Next, when your setting up your project server, Note this key fact I could not find anywhere, and did not get hint about in the technet forms when i posted about my problems: You CAN NOT use Claims based authentication on your web application that is hosting Project Server 2010. The 2007 Client will not connect to the server. The 2010 client will connect with no problems. Quick and dirty, hope that helps everyone!
Read more