[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

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

PermissionMask check failed. asking for 0x00000015, have 0x3C4312EF

I have a SharePoint Farm with 19 site collections, each with its own application pool.  One site collection has some custom code and workflows that were developed by our in house Software team.  We have some custom crawls setup that use the BDC to access data from DB's outside the farm.  This site collection has over 2000 sites.  The site collection has caused issues 3 times over the last 4 weeks in which it begins to consume memory and cpu until the WFE becomes unresponsive.

This happened last night and I've been looking through the logs and I keep seing the same entry repeated

12/29/2009 16:59:51.23       w3wp.exe (0x191C)                             0x17B4      Windows SharePoint Services         General                             8xfr      Verbose       PermissionMask check failed. asking for 0x00000015, have 0x3C4312EF      

The farm used Kerberos authentication and consists of
 1 WFE
1 App server hosting the search index and Excel Services
Clustered SQL

I also see event id errors 27745

Event Type:      Error
Event Source:      Windows SharePoint Services 3
Event Category:      General
Event ID:      27745
Date:            12/29/2009
Time:            5:44:02 PM
User:            N/A
Computer:      SRMOSSFE1
Description:
The description for Event ID ( 27745 ) in Source ( Windows SharePoint Services 3 ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: #50071: Unable to connect to the database SharePoint_Config on srsql2005prod2.  Check the database connection information and make sure that the database server is running..

I've searched the web and I cannot figure out why the entry in the SharePoint log is firing.  Does anyone know what is causing this?

8xfr      Verbose       PermissionMask check failed. asking for 0x00000015, have 0x3C4312EF
0
james_higgs
Asked:
james_higgs
  • 3
  • 2
2 Solutions
 
MsShadowCommented:
I've read up on some stuff online, root cause I haven't found, but have you tried backing the site collection up and restoring it to a new site collection?
I know it sounds weird that it'll fix it, but this blog post seems to say so:
http://www.binarywave.com/blogs/eshupps/Lists/Posts/Post.aspx?List=9c93c708-e5ce-4714-bdea-499330361130&ID=94

A permission mask is defined here:
http://msdn.microsoft.com/en-us/library/microsoft.sharepoint.sppermission.permissionmask.aspx

After further reading it seems that the values in "asking for 0x00000015, have 0x3C4312EF" mean that you require permission A (being 0x00000015) and that you have permission level B (0x3C4312EF)

What these values mean can be found here:
http://msdn.microsoft.com/en-us/library/microsoft.sharepoint.sprights.aspx
http://msdn2.microsoft.com/en-us/library/microsoft.sharepoint.spbasepermissions.aspx

Strangely enough your values aren't in that list.

If I look more into detail of your question, part of the error is that you seem to be unable to connect to your configuration database. Have you checked the identity under whch the application pool is running and have you checked that it has the necessary access to your SQL db?
0
 
james_higgsAuthor Commented:
Thank you for your responses.

I have also read that restoring a backup of the site collection will resolve the issues. However, I'm trying desperately to avoid that.

Since my values are not present I'm beginning to think my value may be a custom permission developed by our software team. I'm not sure that they would/could do this.

Also, in this article http://msdn.microsoft.com/en-us/library/microsoft.sharepoint.sppermission.permissionmask.aspx there is a note stating the following: Certain objects implement the IDisposable interface, and you must avoid retaining these objects in memory after they are no longer needed. For information about good coding practices, see Best Practices: Using Disposable Windows SharePoint Services Objects.
I've brought this up with our development team and they are checking to ensure that this is not occuring.  To me it seems that something like this is occuring and triggering the high resource utilization.
I'll provide an update once I have a response from the development team.
Once again, thanks for the responses.  If you have any additional thoughts, I'm all ears.

0
Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
MsShadowCommented:
You can restore your site collection to a new site collection and check if that fixes the issue. It is a good check to see if your backup / restore works fine and you will be able to keep the old site collection running at the same time.
0
 
james_higgsAuthor Commented:
The developers have checked on piece of custom code and did not find anything.  There is one other area of custom code they are checking.  I'll provide an update as soon as they are finished.
0
 
james_higgsAuthor Commented:
These solutions were very helpful in guiding me to the area of SharePoint that requires attention.  The development team is using this to review their custom code to ensure they are not causing this issue.  Although this review is incomplete, these responses have been key in guiding us to the area causing the problem.
0

Featured Post

Visualize your virtual and backup environments

Create well-organized and polished visualizations of your virtual and backup environments when planning VMware vSphere, Microsoft Hyper-V or Veeam deployments. It helps you to gain better visibility and valuable business insights.

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