tag:blogger.com,1999:blog-158104178192097877.post5140287884021246616..comments2023-09-09T22:31:24.624+08:00Comments on Dirty Words: Unable to display this Web Part error and Alternate Access MappingsMichael Haneshttp://www.blogger.com/profile/01877569030107816208noreply@blogger.comBlogger9125tag:blogger.com,1999:blog-158104178192097877.post-49415712013063483682012-02-09T15:39:43.058+11:002012-02-09T15:39:43.058+11:00@CatatonicBug: You don't normally set permissi...@CatatonicBug: You don't normally set permissions on a web part but on a list item, list/library, or site. Just to clarify, are you working within a single site collection and the web part you're working with isn't a custom dev job? If, as you mention, making a user a site collection owner or members group, you're on the right track. Maybe create a new group and fiddle with the permissions until you can isolate the exact permission the users require?Michael Haneshttps://www.blogger.com/profile/01877569030107816208noreply@blogger.comtag:blogger.com,1999:blog-158104178192097877.post-57620978784075314902012-02-09T08:05:20.221+11:002012-02-09T08:05:20.221+11:00Michael - I think you're right about the permi...Michael - I think you're right about the permissions issue, but I can't seem to isolate it. Permissions WERE inherited, but for testing purposes, I removed that. The user is able to view the contents of the list directly already. If I give the user "Full Control" permissions on the list, nothing changes. If I add that same regular user to the "'Site Collection' Owners" group (which has Full Control, Limited Access), or the "'Site Collection' Members" group (which has Contribute, Limited Access), the problem goes away for that user. I un-did that, then added that same user to the specific site with the CQWP on it, and gave them "Full Control" of the site, but the problem remains. Shouldn't any user with "View" rights to the site be able to view the contents of the Web Part? Where might I control the permissions for a specific web part?CatatonicBughttps://www.blogger.com/profile/11316177394419374539noreply@blogger.comtag:blogger.com,1999:blog-158104178192097877.post-32234710109515502872011-12-27T18:25:25.498+11:002011-12-27T18:25:25.498+11:00@CatatonicBug: I'm not developing/administrati...@CatatonicBug: I'm not developing/administrating much these days but your problem sounds like a permissions problem to me and unrelated to naming/alternate access mappings. You say you've checked permissions--have you tried ramping up permissions for your regular users to see if that helps? Are permissions inheriting?Michael Haneshttps://www.blogger.com/profile/01877569030107816208noreply@blogger.comtag:blogger.com,1999:blog-158104178192097877.post-24658793880879951632011-12-20T05:36:38.474+11:002011-12-20T05:36:38.474+11:00I'm not sure how similar my issue is to what y...I'm not sure how similar my issue is to what you dealt with here, but I'll ask my question anyway: I have built a CQWP into several sites on my Site Collection to display a particular item out of a list I have on the main site. It works great, but only as long as I am logged in as a site admin. If I log in as a regular user, I get the "Unable to display..." error. I checked permissions on the list itself, and the regular users have "View" permissions. This is a SP2010 install. What am I missing?CatatonicBughttps://www.blogger.com/profile/11316177394419374539noreply@blogger.comtag:blogger.com,1999:blog-158104178192097877.post-86358188334132022011-08-01T08:15:00.262+08:002011-08-01T08:15:00.262+08:00@Anonymous: No, I don't think so--CAS is a .NE...@Anonymous: No, I don't think so--CAS is a .NET thing whereas this is a networking + SharePoint issue.Michael Haneshttps://www.blogger.com/profile/01877569030107816208noreply@blogger.comtag:blogger.com,1999:blog-158104178192097877.post-63594047703788677022011-07-29T20:38:54.996+08:002011-07-29T20:38:54.996+08:00thanks..great hint..worked for me
but as an altern...thanks..great hint..worked for me<br />but as an alternate can we resolve it by code access security for that web part?Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-158104178192097877.post-84253975284302542362011-05-20T21:36:35.711+08:002011-05-20T21:36:35.711+08:00@Anonymous: 'SharePoint' was a dirty word ...@Anonymous: 'SharePoint' was a dirty word around the office when were were implementing westernaustralia.com on MOSS 2007 TR2... our inexperience with the product and a wealth of bugs and issues led to much swearing ;)Michael Haneshttps://www.blogger.com/profile/01877569030107816208noreply@blogger.comtag:blogger.com,1999:blog-158104178192097877.post-84888220128967587962011-05-20T20:38:13.378+08:002011-05-20T20:38:13.378+08:00dirty words? why the name is this? though you are ...dirty words? why the name is this? though you are writing good blogsAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-158104178192097877.post-46070467193249385562010-01-05T22:45:02.503+11:002010-01-05T22:45:02.503+11:00Hey, thanks for your post man :D I had a similar i...Hey, thanks for your post man :D I had a similar issue which wasn't directly related to an IP address; in my case the configuration didn't have a public URL for the alternate access mapping, which made the content query web part display the same error. Your post helped me look in the right direction so I could eventually resolve the issue.Dennishttp://blog.dennus.netnoreply@blogger.com