SharePoint enable debugging - Debugger must be enabled in web.config error

Modify the web.config file usually located 
C:\inetpub\wwwroot\wss\VirtualDirectories\80

<configuration>
  <SharePoint>
    <SafeModeCallStack="true" />
  </SharePoint>
  <system.web>
    <customErrorsmode="Off" />
    <compilationdebug="true" />
  </system.web>
</configuration>

Comments

Post a Comment

Popular posts from this blog

Export Data from AX 2012 - using DIXF (Data Migration Framework)

Importing is a well known task using DIXF, but at times we do need to export as well and then import it back in AX 2012. The export task can be done with the help of this information. https://technet.microsoft.com/en-us/library/dn144987.aspx Define the format of your source data Open  Data Import/Export Framework  >  Setup  >  Source data formats . Click  New , enter a name and a description, and then select  AX  from the  Type  list. Define a processing group to export data from Microsoft Dynamics AX Change the company to  CEU . In  Data Import/Export Framework , click  Common  >  Processing group , and then click  New  to create a new processing group. Set the group name to  Export-Cust  and add a description. Click  Entities  to select the entities to include in the processing group. In the  Select entities for processing group  form, click  New , and then, for an entity name, select  Customer . In the  Source data format  fiel
Read more

The virtual path maps to another application, which is not allowed

Image
During the development we came across this issue, which wasted a lot of our precious time. So I decided to share its solution with everyone. We have Project and Sub-Project Structure i.e. we have a root project and several sub-projects. The ROOT Project is entitled as TEMS8 and all other subprojects have been configured as per the image below. (Click on the image for large size) Now after setting up everything on a new Machine, we came across the Error as The virtual path maps to another application, which is not allowed Finally after investigation, we figured out that we have created multiple virtual directories which mainly causes the issue. For instance, we have another virtual directory created for DATADEF which is inside the virtual directory of TEMS8. So this was the main issue. The resolution was to remove the DATADEF Virtual Directory. Everything worked out perfectly, once we removed the inner virtual directory. We should not have something like this image below  W
Read more