Tag Info

Hot answers tagged

4

Uninstall windows update KB2844286. Over the weekend I had to do this to two servers (much to my annoyance) but it did fix this problem. A server reboot was required. http://social.technet.microsoft.com/Forums/sharepoint/en-US/cc9a557b-93cd-40d5-965c-e0a2f107624d/unable-to-display-this-web-part-error-message-after-patch-kb2844286


2

I have tried this code snippet (from console application): using(SPSite site = new SPSite("http://mycoolsite")) { using(SPWeb web = site.OpenWeb()) { SPList list = web.Lists["My List"]; SPField fldTitle = list.Fields["Title"]; fldTitle.Required = false; fldTitle.Title = "New title"; ...


1

I saw a post somewhere in the last few days that tracked this down to two recent hot fixes from Windows Update. Sorry I can't give you more to go on, but that's all I can recall and Bingle isn't giving me any love.


1

If all you are doing is updating content in SharePoint, then it is better to impersonate the system account instead of elevating privilege. http://www.schaeflein.net/Pages/Impersonation-and-Elevation-of-Privilege.aspx Also, even though your first scenario happens to work, you should validate the token before creating the new SPSite context.


1

Have you gone through all solutions provided here ? or check the document library settings and find out that document library was set NOT to require check out although versioning was enabled. Just try to set to require check out. Note: RunWithElevatedPrivileges only works if the current thread is using impersonation, i.e. IIS. Used in other code (timer ...


1

For example, it's not safe to make updates and removal on GET requests, because someone may send you a link, you will click and item will be deleted. Thus it's strongly recommended to make updates on POST requests, thus the error is fired. In some cases it's really required to do and AllowUnsafeUpdates is used. Please see this link and that link for ...


1

I would recomand you read this article from Waldek concerning problems revolving with web.GetFile() available at http://blog.mastykarz.nl/inconvenient-spwebgetfilestring/ and confront with your code, particularly when you passing a certain URL to the method.


1

With the newer CUs for SharePoint 2010 it's not necessary according to Microsoft The packaging of cumulative updates changed as of August 31, 2011 ... As a result of the new packaging, it is no longer necessary to install the SharePoint Foundation cumulative update and then install the SharePoint Server cumulative update On a new Installation/Upgrade ...


1

It does happen all the time. This is where SharePoint thinks its smarter than the user and its dead wrong. If you use regular pages you do not get this. If I am forced to use a wiki page because of requirements I will create my web parts on a standard web part page then export/import them to my wiki page. The Wiki pages to my understanding are actually Rich ...



Only top voted, non community-wiki answers of a minimum length are eligible