Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2771
  • Last Modified:

Sharepoint 2010 - List Item Validation Failed

We have got a shared Sharepoint 2010 server running Windows Server 2008 R2 which is running multiple sharepoint sites under the same web application.

For one site, when trying to create a new permission group, we are getting a List Item Validation Error when trying to save the group. For the other sites, a new group is able to be successfully created without error so the problem appears to be isolated to the single site.

When looking at the logs for the correlation ID all that shows up is:

6/14/2013 08:44:40 AM      False      w3wp.exe (0x1DB0)      7252      SharePoint Foundation      Logging Correlation Data      xmnv      Medium      Name=Request (POST:http://intranet.######.com.au/_layouts/newgrp.aspx?Source=http%3A%2F%2Fintranet%2E######%2Ecom%2Eau%2F%5Flayouts%2Fuser%2Easpx)      ecdb7a3a-6f41-42cb-902c-618be80add52      
6/14/2013 08:44:40 AM      False      w3wp.exe (0x1DB0)      7252      SharePoint Foundation      Logging Correlation Data      xmnv      Medium      Site=/      ecdb7a3a-6f41-42cb-902c-618be80add52      
6/14/2013 08:44:41 AM      False      w3wp.exe (0x1DB0)      7252      SharePoint Foundation      General      8kh7      High      List Item Validation Failed.      ecdb7a3a-6f41-42cb-902c-618be80add52      
6/14/2013 08:44:41 AM      False      w3wp.exe (0x1DB0)      7252      SharePoint Foundation      General      8e2r      Medium      Possible mismatch between the reported error with code = 0x81079801 and message: "List Item Validation Failed." and the returned error with code 0x810200c6.      ecdb7a3a-6f41-42cb-902c-618be80add52      
6/14/2013 08:44:41 AM      False      w3wp.exe (0x1DB0)      7252      SharePoint Foundation      Runtime      tkau      Unexpected      System.Runtime.InteropServices.COMException: List Item Validation Failed.    at Microsoft.SharePoint.Library.SPRequestInternalClass.AddGroup(String bstrUrl, String bstrName, String bstrDescription, Int32 lOwnerID, Boolean bOwnerIsUser, UInt64 iPermMask, Int32 lUserId, Boolean bUseExisting, Boolean bSelfOwner)     at Microsoft.SharePoint.Library.SPRequest.AddGroup(String bstrUrl, String bstrName, String bstrDescription, Int32 lOwnerID, Boolean bOwnerIsUser, UInt64 iPermMask, Int32 lUserId, Boolean bUseExisting, Boolean bSelfOwner)      ecdb7a3a-6f41-42cb-902c-618be80add52      
6/14/2013 08:44:41 AM      False      w3wp.exe (0x1DB0)      7252      SharePoint Foundation      Monitoring      b4ly      Medium      Leaving Monitored Scope (Request (POST:http://intranet.######.com.au/_layouts/newgrp.aspx?Source=http%3A%2F%2Fintranet%2E######%2Ecom%2Eau%2F%5Flayouts%2Fuser%2Easpx)). Execution Time=284.274576      ecdb7a3a-6f41-42cb-902c-618be80add52
0
jaylaa
Asked:
jaylaa
  • 4
  • 2
1 Solution
 
AbhishekJhaCommented:
Verify the User Rights  through which you are logged in have full permission of the site. If permission is okay then try installing below Hot Fix .

http://support.microsoft.com/kb/2405789
0
 
vinsvinCommented:
The solution to the problem is to change the validation formula to handle the initial values e.g.

=[Start Date and Time]<=[End Date and Time]
0
 
jaylaaAuthor Commented:
Does that hotfix require the server to be rebooted or can it be run while people are actively using the system?

Aslo as far as I am aware, there has been no validation formula's set other then what is there by default when you add a group, so how would I check that?
0
Veeam Disaster Recovery in Microsoft Azure

Veeam PN for Microsoft Azure is a FREE solution designed to simplify and automate the setup of a DR site in Microsoft Azure using lightweight software-defined networking. It reduces the complexity of VPN deployments and is designed for businesses of ALL sizes.

 
AbhishekJhaCommented:
You don't need to reboot the server.
0
 
jaylaaAuthor Commented:
Just tried to install the hotfix and it is reporting that it is already installed
0
 
jaylaaAuthor Commented:
Found the issue - there was a list validation set on http://intranet.xxxxxx.com.au/_layouts/people.aspx that was requiring an email address but even when an email was set, was still causing the error.
0
 
jaylaaAuthor Commented:
Pointed in the right direction by vinsvin and while the error was with validation, the formula and location were different than suggested
0

Featured Post

Free learning courses: Active Directory Deep Dive

Get a firm grasp on your IT environment when you learn Active Directory best practices with Veeam! Watch all, or choose any amount, of this three-part webinar series to improve your skills. From the basics to virtualization and backup, we got you covered.

  • 4
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now