8

I am trying to see the full errors of my application page but the only thing displayed is "Sorry, something went wrong". I tried setting this:

<customErrors mode="Off" />
<compilation batch="false" debug="true">
<SafeMode CallStack="true".... />

In these locations:

C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\TEMPLATE\LAYOUTS\web.config
C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\CONFIG\web.config

After performing an iisreset there is no affect. What else do I need to do? My page is in a subfolder of LAYOUTS.

17

Every change you make in that config files have no effect on the web application. You have to go the web.config file that is generated once the web application is created.

So edit the web.config file in C:\inetpub\wwwroot\wss\VirtualDirectories\your port number and modify the parameters you have indicated in that web.config file:

  • customErrors mode must be "Off"
  • compilation debug must be "true"
  • SafeMode CallStack must be "true"

The 'your port number' piece of path is the port you assigned when you created the Web Application in the Central Administration

7

I solved this problem editing this file: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\TEMPLATE\LAYOUTS\web.config

  • How? What did you do to the web.config file? – Phil Greer Aug 6 '14 at 17:23
  • 1
    That worked for me xristian. I set: <compilation batch="false" debug="true" batchTimeout="600" maxBatchSize="10000" maxBatchGeneratedFileSize="10000" /> and <customErrors mode="Off" /> – Andez Sep 30 '14 at 13:05
  • This solution solve my problem. – Juan Pablo Pussacq Laborde Mar 21 '19 at 19:57
3

I had to change both web.config files:

  • C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\TEMPLATE\LAYOUTS\web.config

  • C:\inetpub\wwwroot\wss\VirtualDirectories\{your port number}

Only then it is showing detailed error message

0

The config file under LAYOUTS affects the files under layouts, the one in virtualdirectories.. the rest.

So ... what page is failing? Is it under /_layouts/ or is it not? There you have your answer.

(granted there are a few more edgecases but let's not confuse the main point)

0

In my case, have an ashx handler deployed to _vti_bin in SharePoint 2016. Needed to also update the web.config in the ISAPI folder:

c:\program files\common files\microsoft shared\web server extensions\16\ISAPI

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.