none
Coming up with run time error when we browse the webaplication

    Question

  • Coming up with run time error when we browse the webaplication. Below is the error 


    • Edited by SravanC Thursday, March 14, 2019 8:04 AM
    Wednesday, March 13, 2019 12:00 PM

Answers

All replies

  • Hi SravanC,

    Have you created a Root site collection for the web application?

    If you have created a Root site collection, you should be able to access the site collection via "http://servername/".

    As this error is general, please check ULS log files to find more information. The default path of ULS log files is: C:\Program Files\Common Files\microsoft shared\Web Server Extensions\14\LOGS.

    About how to check ULS log in SharePoint 2010, you can refer to:

    http://habaneroconsulting.com/insights/get-the-real-sharepoint-error-using-the-uls-logs#.Vu-JwOJ96M8  

    Thanks,

    Wendy


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    SharePoint Server 2019 has been released, you can click here to download it.
    Click here to learn new features. Visit the dedicated forum to share, explore and talk to experts about SharePoint Server 2019.

    Thursday, March 14, 2019 2:58 AM
    Moderator
  • Hi Wendy,

    I have got the below information from event viewer. Please let me know what we can do here... 

    Log Name:      Application
    Source:        ASP.NET 2.0.50727.0
    Date:          3/14/2019 2:35:12 AM
    Event ID:      1310
    Task Category: Web Event
    Level:         Warning
    Keywords:      Classic
    User:          N/A

    Description:
    Event code: 3007 
    Event message: A compilation error has occurred. 
    Event time: 3/14/2019 2:35:12 AM 
    Event time (UTC): 3/14/2019 7:35:12 AM 
    Event ID: 38bd2f0d43604acc82e39b62660e8580 
    Event sequence: 3 
    Event occurrence: 1 
    Event detail code: 0 
     
    Application information: 
        Application domain: /LM/W3SVC/559465467/ROOT-6-131970225073937154 
        Trust level: WSS_Minimal 
        Application Virtual Path: / 
        Application Path: C:\inetpub\wwwroot\wss\VirtualDirectories\Portal-80\ 
        Machine name: 
    Process information: 
        Process ID: 5568 
        Process name: w3wp.exe 
        Account name: 
     
    Exception information: 
        Exception type: HttpCompileException 
        Exception message: (0): error CS0016: Could not write to output file 'c:\Windows\Microsoft.NET\Framework64\v2.0.50727\Temporary ASP.NET Files\root\93f85277\cd874025\bg-BG\App_GlobalResources.yxgo8qu2.resources.dll' -- 'The directory name is invalid. ' 
     
    Request information: 
        Request URL:  
        Request path: / 
        User host address: 127.0.0.1 
        User:  
        Is authenticated: False 
        Authentication Type:  
        Thread account name: 
     
    Thread information: 
        Thread ID: 16 
        Thread account name: 
        Is impersonating: False 
        Stack trace:    at System.Web.Compilation.AssemblyBuilder.Compile()
       at System.Web.Compilation.BuildProvidersCompiler.PerformBuild()
       at System.Web.Compilation.CodeDirectoryCompiler.GetCodeDirectoryAssembly(VirtualPath virtualDir, CodeDirectoryType dirType, String assemblyName, StringSet excludedSubdirectories, Boolean isDirectoryAllowed)
       at System.Web.Compilation.BuildManager.CompileCodeDirectory(VirtualPath virtualDir, CodeDirectoryType dirType, String assemblyName, StringSet excludedSubdirectories)
       at System.Web.Compilation.BuildManager.EnsureTopLevelFilesCompiled()
       at System.Web.Hosting.HostingEnvironment.Initialize(ApplicationManager appManager, IApplicationHost appHost, IConfigMapPathFactory configMapPathFactory, HostingEnvironmentParameters hostingParameters)
     
     
    Custom event details: 

    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="ASP.NET 2.0.50727.0" />
        <EventID Qualifiers="32768">1310</EventID>
        <Level>3</Level>
        <Task>3</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2019-03-14T07:35:12.000000000Z" />
        <EventRecordID>1254146</EventRecordID>
        <Channel>Application</Channel>
        <Computer></Computer>
        <Security />
      </System>
      <EventData>
        <Data>3007</Data>
        <Data>A compilation error has occurred.</Data>
        <Data>3/14/2019 2:35:12 AM</Data>
        <Data>3/14/2019 7:35:12 AM</Data>
        <Data>38bd2f0d43604acc82e39b62660e8580</Data>
        <Data>3</Data>
        <Data>1</Data>
        <Data>0</Data>
        <Data>/LM/W3SVC/559465467/ROOT-6-131970225073937154</Data>
        <Data>WSS_Minimal</Data>
        <Data>/</Data>
        <Data>C:\inetpub\wwwroot\wss\VirtualDirectories\Portal-80\</Data>
        <Data></Data>
        <Data>
        </Data>
        <Data>5568</Data>
        <Data>w3wp.exe</Data>
        <Data>ENT\sp2010suserapps</Data>
        <Data>HttpCompileException</Data>
        <Data>(0): error CS0016: Could not write to output file 'c:\Windows\Microsoft.NET\Framework64\v2.0.50727\Temporary ASP.NET Files\root\93f85277\cd874025\bg-BG\App_GlobalResources.yxgo8qu2.resources.dll' -- 'The directory name is invalid. '</Data>
        <Data>http://dles450/</Data>
        <Data>/</Data>
        <Data>127.0.0.1</Data>
        <Data>
        </Data>
        <Data>False</Data>
        <Data>
        </Data>
        <Data></Data>
        <Data>16</Data>
        <Data></Data>
        <Data>False</Data>
        <Data>   at System.Web.Compilation.AssemblyBuilder.Compile()
       at System.Web.Compilation.BuildProvidersCompiler.PerformBuild()
       at System.Web.Compilation.CodeDirectoryCompiler.GetCodeDirectoryAssembly(VirtualPath virtualDir, CodeDirectoryType dirType, String assemblyName, StringSet excludedSubdirectories, Boolean isDirectoryAllowed)
       at System.Web.Compilation.BuildManager.CompileCodeDirectory(VirtualPath virtualDir, CodeDirectoryType dirType, String assemblyName, StringSet excludedSubdirectories)
       at System.Web.Compilation.BuildManager.EnsureTopLevelFilesCompiled()
       at System.Web.Hosting.HostingEnvironment.Initialize(ApplicationManager appManager, IApplicationHost appHost, IConfigMapPathFactory configMapPathFactory, HostingEnvironmentParameters hostingParameters)
    </Data>
      </EventData>
    </Event>





    Event code: 3007 
    Event message: A compilation error has occurred. 
    Event time: 3/14/2019 2:35:12 AM 
    Event time (UTC): 3/14/2019 7:35:12 AM 
    Event ID: 38bd2f0d43604acc82e39b62660e8580 
    Event sequence: 3 
    Event occurrence: 1 
    Event detail code: 0 
     
    Application information: 
        Application domain: /LM/W3SVC/559465467/ROOT-6-131970225073937154 
        Trust level: WSS_Minimal 
        Application Virtual Path: / 
        Application Path: C:\inetpub\wwwroot\wss\VirtualDirectories\Portal-80\ 
        Machine name: 
    Process information: 
        Process ID: 5568 
        Process name: w3wp.exe 
        Account name:  
     
    Exception information: 
        Exception type: HttpCompileException 
        Exception message: (0): error CS0016: Could not write to output file 'c:\Windows\Microsoft.NET\Framework64\v2.0.50727\Temporary ASP.NET Files\root\93f85277\cd874025\bg-BG\App_GlobalResources.yxgo8qu2.resources.dll' -- 'The directory name is invalid. ' 
     
    Request information: 
        Request URL: 
        Request path: / 
        User host address: 127.0.0.1 
        User:  
        Is authenticated: False 
        Authentication Type:  
        Thread account name: 
     
    Thread information: 
        Thread ID: 16 
        Thread account name:  
        Is impersonating: False 
        Stack trace:    at System.Web.Compilation.AssemblyBuilder.Compile()
       at System.Web.Compilation.BuildProvidersCompiler.PerformBuild()
       at System.Web.Compilation.CodeDirectoryCompiler.GetCodeDirectoryAssembly(VirtualPath virtualDir, CodeDirectoryType dirType, String assemblyName, StringSet excludedSubdirectories, Boolean isDirectoryAllowed)
       at System.Web.Compilation.BuildManager.CompileCodeDirectory(VirtualPath virtualDir, CodeDirectoryType dirType, String assemblyName, StringSet excludedSubdirectories)
       at System.Web.Compilation.BuildManager.EnsureTopLevelFilesCompiled()
       at System.Web.Hosting.HostingEnvironment.Initialize(ApplicationManager appManager, IApplicationHost appHost, IConfigMapPathFactory configMapPathFactory, HostingEnvironmentParameters hostingParameters)
     
     
    Custom event details: 

    Thursday, March 14, 2019 7:46 AM
  • Hi SravanC,

    Please go to Temp folder location of Asp.net files and delete all the files from that folder as the following steps:

    1. Stop an IIS using the command iisreset /stop
    2. Navigate to the Folder c:\Windows\Microsoft.NET\Framework64\v2.0.50727\Temporary ASP.NET Files
    3. Delete all the files inside the Temporary ASP.NET Files (don't delete the Temporary ASP.NET Files folder itself!)
    4. Start the IIS using the command iisreset /start.

    There are two blogs/threads about this similar issue for your reference:

    https://stackoverflow.com/questions/21984217/sharepoint-server-2013-error-the-directory-name-is-invalid

    https://thesharepointfarm.com/2014/07/sharepoint-asp-net-compilation-errors-cs0016/

    Thanks,

    Wendy


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    SharePoint Server 2019 has been released, you can click here to download it.
    Click here to learn new features. Visit the dedicated forum to share, explore and talk to experts about SharePoint Server 2019.

    • Marked as answer by SravanC Monday, March 18, 2019 10:24 AM
    Thursday, March 14, 2019 9:30 AM
    Moderator
  • Hi Wendy,

    Thank you for the response and answer. 

    It worked in the Server ( not with regular admin account. it worked with farm account ) after executing above steps you have mentioned.

    But in the local machine it is coming up with access denied for both farm account and admin account as well. 

    Thursday, March 14, 2019 12:18 PM
  • Hi Wendy,

    Did you have a chance to look in to my above email. Thank you 

    Friday, March 15, 2019 4:24 AM
  • Hi SravanC,

    Did you mean for "local machine"? Is it a client machine?

    How many servers did you have in your farm? If there are more than one SharePoint server, please do the same steps on all servers.

    Also please try to clear the browser cache on the local machine, then test again.

    If this issue still exists, please check ULS files to check if there are messages about this new error.

    Thanks,

    Wendy


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    SharePoint Server 2019 has been released, you can click here to download it.
    Click here to learn new features. Visit the dedicated forum to share, explore and talk to experts about SharePoint Server 2019.

    Friday, March 15, 2019 6:58 AM
    Moderator
  • Hi Wendy,

    Thank you for the response. 

    It is my local machine ie.. client machine 

    3 servers in Farm.

    yes tried after clearing the cache same issue in the client machine

    it is access denied regular message popping up how to generate correlation id from this message to check it in ULS logs? 

    ANd noticed that   there is one group which is part of farm administrators group there this admin account is not placed where as in other farm this account admin placed for them i did not face any issue. 

    so I believe then since this account is not part of this group in the farm administrator area in this server. getting access denied error. 

    • Edited by SravanC Friday, March 15, 2019 8:51 AM
    Friday, March 15, 2019 8:41 AM
  • Hi Wendy,

    Did you have a chance to look in to above email? 

    Monday, March 18, 2019 9:14 AM
  • Hi Wendy,

    No issue after adding our local admins account in to farm group issue got resolved 

    Thank you very much for your assistance on this issue. 

    Monday, March 18, 2019 10:25 AM
  • Hi SravanC,

    Thanks for your feedback. I am glad to hear this issue has been fixed.:)

    Regards,

    Wendy



    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    SharePoint Server 2019 has been released, you can click here to download it.
    Click here to learn new features. Visit the dedicated forum to share, explore and talk to experts about SharePoint Server 2019.

    Tuesday, March 19, 2019 12:46 AM
    Moderator