Getting Intermittent Execution permission cannot be acquired error

Question

I hope I can explain the issue as I am more of a business/end user than a SharePoint expert. We are running a SharePoint intranet (MOSS 2007) within a Citrix environment. On intermittent occasions, we are receiving the error that I will post at the end of this message. This is happening intermittently and we simply can not reproduce the error.

 

100% of the time, we perform an IISReset on the SharePoint server and that resolves the problem. I actually have a scheduled task to run each morning to reset IIS, but the error still occurs on occasion. (again, once the error happens, if i reset IIS, it comes back up).

 

Has anyone ever run into this issue? Any comments or suggestions? Here is the error message:

 Execution permission cannot be acquired.

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.Security.Policy.PolicyException: Execution permission cannot be acquired.

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Stack Trace:

[PolicyException: Execution permission cannot be acquired.]    System.Security.SecurityManager.ResolvePolicy(Evidence evidence, PermissionSet reqdPset, PermissionSet optPset, PermissionSet denyPset, PermissionSet& denied, Boolean checkExecutionPermission) +7604136    System.Security.SecurityManager.ResolvePolicy(Evidence evidence, PermissionSet reqdPset, PermissionSet optPset, PermissionSet denyPset, PermissionSet& denied, Int32& securitySpecialFlags, Boolean checkExecutionPermission) +57   [FileLoadException: Could not load file or assembly 'msvcm80, Version=8.0.50727.3053, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. Failed to grant permission to execute. (Exception from HRESULT: 0x80131418)]    <CrtImplementationDetails>.DoDllLanguageSupportValidation() +0    <CrtImplementationDetails>.LanguageSupport._Initialize(LanguageSupport* ) +112    <CrtImplementationDetails>.LanguageSupport.Initialize(LanguageSupport* ) +96   [ModuleLoadException: The C++ module failed to load. ]    <CrtImplementationDetails>.ThrowModuleLoadException(String errorMessage, Exception innerException) +38    <CrtImplementationDetails>.ThrowModuleLoadException(String , Exception ) +0    <CrtImplementationDetails>.LanguageSupport.Initialize(LanguageSupport* ) +146    .cctor() +31   [TypeInitializationException: The type initializer for '<Module>' threw an exception.]    System.Runtime.CompilerServices.RuntimeHelpers._RunClassConstructor(IntPtr type) +0    System.Runtime.CompilerServices.RuntimeHelpers.RunClassConstructor(RuntimeTypeHandle type) +4    System.Reflection.RuntimeConstructorInfo.Invoke(BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture) +141    System.Reflection.ConstructorInfo.Invoke(Object[] parameters) +17    Microsoft.SharePoint.Administration.SPAutoSerializingObject.GetInstanceFromType(Type type) +291    Microsoft.SharePoint.Administration.SPPersistedObject.GetInstance(XmlNode xml, Guid classId) +263    Microsoft.SharePoint.Administration.SPFileSystemCache.FetchObjectFromFileSystem(Guid id) +1375    Microsoft.SharePoint.Administration.SPFileSystemCache.GetValue(Guid id) +85    Microsoft.SharePoint.Administration.SPCache`2.get_Item(K key) +92    Microsoft.SharePoint.Administration.SPConfigurationDatabase.GetObject(Guid id, Boolean checkInMemoryCache) +162    Microsoft.SharePoint.Administration.SPConfigurationDatabase.GetObject(Guid id) +62    Microsoft.SharePoint.Administration.SPAutoSerializingObject.DeserializeBasicObject(XmlElement xmlValue) +5591    Microsoft.SharePoint.Administration.SPAutoSerializingObject.SetStateXml(XmlNodeList childNodes) +823    Microsoft.SharePoint.Administration.SPAutoSerializingObject.SetStateXml(XmlDocument value) +85    Microsoft.SharePoint.Administration.SPPersistedObject.Initialize(SPConfigurationDatabase configurationDatabase, Guid id, Guid parentId, String name, SPObjectStatus status, Int64 version, XmlDocument state) +563    Microsoft.SharePoint.Administration.SPFileSystemCache.FetchObjectFromFileSystem(Guid id) +1375    Microsoft.SharePoint.Administration.SPFileSystemCache.GetValue(Guid id) +85    Microsoft.SharePoint.Administration.SPCache`2.get_Item(K key) +92    Microsoft.SharePoint.Administration.SPConfigurationDatabase.GetObject(Guid id, Boolean checkInMemoryCache) +162    Microsoft.SharePoint.Administration.SPConfigurationDatabase.GetObject(Guid id) +62    Microsoft.SharePoint.Administration.SPAutoSerializingObject.DeserializeBasicObject(XmlElement xmlValue) +5591    Microsoft.SharePoint.Administration.SPAutoSerializingObject.DeserializeBasicObject(XmlElement xmlValue) +2041    Microsoft.SharePoint.Administration.SPAutoSerializingObject.SetStateXml(XmlNodeList childNodes) +823    Microsoft.SharePoint.Administration.SPAutoSerializingObject.SetStateXml(XmlDocument value) +85    Microsoft.SharePoint.Administration.SPAutoSerializingObject.DeserializeBasicObject(XmlElement xmlValue) +607    Microsoft.SharePoint.Administration.SPAutoSerializingObject.SetStateXml(XmlNodeList childNodes) +823    Microsoft.SharePoint.Administration.SPAutoSerializingObject.SetStateXml(XmlDocument value) +85    Microsoft.SharePoint.Administration.SPPersistedObject.Initialize(SPConfigurationDatabase configurationDatabase, Guid id, Guid parentId, String name, SPObjectStatus status, Int64 version, XmlDocument state) +563    Microsoft.SharePoint.Administration.SPFileSystemCache.FetchObjectFromFileSystem(Guid id) +1375    Microsoft.SharePoint.Administration.SPFileSystemCache.GetValue(Guid id) +85    Microsoft.SharePoint.Administration.SPCache`2.get_Item(K key) +92    Microsoft.SharePoint.Administration.SPConfigurationDatabase.GetObject(Guid id, Boolean checkInMemoryCache) +162    Microsoft.SharePoint.Administration.SPConfigurationDatabase.GetObject(Guid id) +62    Microsoft.SharePoint.Administration.SPPersistedObjectCollection`1.get_BackingList() +993    Microsoft.SharePoint.Administration.SPPersistedObjectCollection`1.GetEnumerator() +62    Microsoft.SharePoint.Administration.SPWebApplication.AcquireAlternateUrlCache(SPFarm farm) +161    Microsoft.SharePoint.Administration.SPWebApplication.Lookup(SPFarm farm, Uri requestUri, Boolean fallbackToHttpContext, SPAlternateUrl& alternateUrl, SiteMapInfo& hostHeaderSiteInfo, Boolean& lookupRequiredContext) +1491    Microsoft.SharePoint.ApplicationRuntime.SPRequestModule.EnsureInitialize(HttpRequest request) +692    Microsoft.SharePoint.ApplicationRuntime.SPRequestModule.BeginRequestHandler(Object oSender, EventArgs ea) +2347    System.Web.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +68    System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +75

Version Information: Microsoft .NET Framework Version:2.0.50727.3603; ASP.NET Version:2.0.50727.3601

 

 

 

Answer 1

I have exactly the same problem on two different customers SharePoint 2007 Servers. Something causes the application pool of the customers portals to crash during the night and leaves the app pool down. We have the same workaround in place: a scheduled iisreset that brings up all application pools again. This cannot be the answer though ...

Answer 2

I've encountered the same problem and the work around of recycling the apppool works. That said it's worth noting that I have to web apps sharing the same app pool and the problem was just noticed after a user altered permissions...perhaps just a coincidence but I figured I would add this to the collective. I'll post back anything else I find on a true solution vs. workaround

Answer 3

Not certain but I may be on to something. In reviewing the logs I noticed a correlation of the error time to the execution of my search service and a series of denials by the app pool identity. Perhaps this is all coincidence but was worth a shot to change the recycle time of the app pool to after the search ran. As of this post the reoccurrence has exceeded the established pattern of roughly 24 hours.

For those who are doing a scheduled IIS reset I'd suggest trying a change of the app pool recycle settings to auto recycle after the search service completes. For me this was roughly 4AM.

 

Answer 4

So Much for my being on to something....The error came back...I've opened up a support case with MS...Will post back any resolution.

Answer 5

Anything back from MS? I also get excatly the same callstack.
From the callstack, it somehow seems to be related to the on-Disk-Cache of Shrepoint ...

Answer 6

So... Latest updates on this... case# 110080649903929....

 

After being a ping pong ball, bouncing from SharePoint to IIS support, somehow feeling like they were too busy pointing the finger at each other as to placing blame or fault, I took matters into my own hand and solved the problem by rebuilding the node.

 

I realize this was extreme and I'm likely to see a repeat but Microsoft was just not helping. They were suggesting I resync the entire farm, a move I've executed twice with marginal results in the testing lab. I say marginal because there was downtime involved. In my case I couldn’t have the down time.

 

Since I have my farm WFE in a MS NLB I simply added a third node and removed the second node. No downtime, things have been working for a week now.

 

Answer 7

ARG!  My problem has returned.

Answer 8

I have this issue too in one of the SharePoint farms I am currently responsible for.  Except that my error message is slightly different: Could not load file or assembly 'msvcm80, Version=8.0.50727.4053 <- note the minor build number of the msvcm80.dll.

If you go into c:\windows\winSxS\ and search it and its subdirectories for msvcm80.dll, what do you find?  I found several versions of this dll, all in folders that have names that include either amd or x86 and the full version number of the dll along with other gunk - very long folder names.  I think SharePoint is using the latest version of the versions in this folder.  One thing you can try is this update, http://www.microsoft.com/downloads/en/details.aspx?familyid=fb01abe6-9099-4544-9aec-0ac13f19bc50&displaylang=en, because it deploys msvcm80.dll v8.0.50727.5592.   I'm hoping, although I have no proof yet, that this newer version won't have the issue that the .3053 and .4053 versions do.

Do you have any details about what the interaction is with the Search service?  Can you reproduce the issue on demand by having the search service timer jobs run at just the right time?

---

Sr. Consultant, Magenic [Microsoft Gold Partner] | MCITP SP2010, MCTS, MCSE, MCDBA, MCAD, CAPM | Webmaster, Chicago SharePoint User Group - www.cspug.org | INETA Community Champion, 3Q2010

Answer 9

I've got a solution to your problem here: http://support.microsoft.com/kb/2481343

Hope it helps! Good luck!