Sharepoint

Hey,
This morning we received a odd compilation error on our SharePoint 2013 installation. A server error occurred with the following details:

Event code: 3007
Event message: A compilation error has occurred.
Exception information:
    Exception type: HttpCompileException
    Exception message: (0): error CS0016: Could not write to output file 'c:\Windows\Microsoft.NET\Framework64\v4.0.30319\Temporary ASP.NET Files\root\2becfef8\314e6676\pt-PT\App_GlobalResources.resources.dll' -- 'The directory name is invalid. '

A reboot of the box fixed the issue but I was wondering if anyone knew what caused the error in the first place. I check all permissions on the 'Temporary ASP.NET Files' folder and they seemed fine. We are updated to the October CU update (15.0.4551.1001) running on Server 2012.

Server Specs:
2x Intel Xeon L5639 @ 2.13ghz
72gb


Any help will be much appreciated.
ENSFCAdminAsked:
Who is Participating?
 
Rainer JeschorConnect With a Mentor Commented:
Hi,
during compilation the windows temp folder is also used, therefore you should check that permissions as well.
http://support.microsoft.com/kb/825791

Another reason could be that multiple IIS / ASP.NET worker processes try to do the same and therefore conflicting each other (I have seen this once in my life - a very rare condition).

HTH
Rainer
0
 
Mohammed KhawajaManager - Infrastructure:  Information TechnologyCommented:
What account does your Application Pool Identity is running under?  Does this account have required privileges to c:\Windows\Microsoft.NET\Framework64\v4.0.30319\Temporary ASP.NET Files\ location?  Have you changed the Application Pool Identity account which might the cause of the issue?
0
 
ENSFCAdminAuthor Commented:
Application Pool Identity : <Domain name>\sp_PortalAppPool.
Like I said did check permissions. Same app pool account since creation. Since it wasw a domain account checked for password expired/locked account but the account seemed fine.
0
 
ENSFCAdminAuthor Commented:
A bug in the SharePoint Code must have results in an IIS process clash. The error has not repeated.

Many Thanks.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.