A few years ago we moved SP 2013 Central Administration to another box. Now we moved it back to original box (on a 2 wfe Farm) because box has hardware issues and needs to be replaced. The web config file is coming up with errors.
**Server Error in '/' Application.
Runtime Error
Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed.
Details: To enable the details of this specific error message to be viewable on the local server machine, please create a tag within a "web.config" configuration file located in the root directory of the current web application. This tag should then have its "mode" attribute set to "RemoteOnly". To enable the details to be viewable on remote machines, please set "mode" to "Off".
Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's configuration tag to point to a custom error page URL.
Can I delete all files in virtual directory of this web config and have SharePoint wizard remake it? Is that a viable solution?
Related
I am supporting a classic asp application developed by another developer. This application will be public facing. Before making it public our network team ran a Security Scan and found some issues. One of the issue mentioned by them is as follows:
Fix Microsoft IIS ISAPI Extension Enumerate Root Web Server Directory Vulnerability
and they provided following steps to resolve this:
You can configure IIS 7 to check for the existence of a file before returning an error message.
Go to Handler Mappings
For all enabled IISAPI mappings, Edit ->
Request Restrictions -> Check 'Invoke handler only if request is
mapped to: File'
Disable all unused mappings.
This will address the
following issue: Microsoft IIS ISAPI Extension Enumerate Root Web
Server Directory Vulnerability (HTTP-IIS- 0013).
I am not familiar with Classic ASP but I checked Handler mapping and tried the steps mentioned above. Following are my questions:
Is there an easy way to identify handlers which are not being used?
there are 50+ handlers do I need to click each one of those to invoke handler only if request is mapped to: File
Can this all be handled from Web.config?
Instead of changing the mappings you should be able to turn off detailed error messages for remote users.
In IIS manager select your website, click on error pages, edit feature settings, choose detailed errors for local requests and custom error pages for remote requests.
I have been running DNN 7 on Azure using some store module that we have grown out of. We are in the process of moving our store to nopCommerce. But since we have so much content, other than the store on the DNN site, we would to explore keeping the DNN site and setting up a virtual directory with nopCommerce and run them both under the same domain name.
I have configured the virtual directory MyDNNPortal.AzwureWebSites.net/store to point to the physical folder "site_nopCommerce" and checked the "application" checkbox.
DNN works fine, but when trying to navigate to MyDNNPortal.AzwureWebSites.net/store, I get the following error:
"The page cannot be displayed because an internal server error has occurred."
This error is just those words in black on a white screen. It is not the typical IIS error.
I have customErrors set to off in both the DNN app and the nopCommerce app. I have the show detailed errors option checked in the Azure config for the DNN website. But that is the only error I get.
If I go to the LogFiles folder via FTP, there is an errorpage000001.htm page that sheds some more light:
HTTP Error 500.19 - Internal Server Error
The requested page cannot be accessed because the related configuration data for the page is invalid.
Error Code 0x80070003
Config Error
Cannot read configuration file
Config File
\\?\D:\home\site\_nopCommerce\web.config
Requested URL
http://mywebsite:80/store
Physical Path
D:\home\site\_nopCommerce
Any ideas? Is this structure possible (running nopCommerce in a virtual directory within a DNN site)?
I've seen this error on my localhost and then add IIS_USERS permissions to fix...but I am not aware of the ability or need to configure those types of permissions on Azure.
I am using Windows 2008 R2 with IIS 7.5 and have mapped the source of my website to a network drive. When I do, the below error occurs. When pointing to the local c: drive the website works.
Error Summary
HTTP Error 500.19 - Internal Server Error
The requested page cannot be accessed because the related configuration data for the page is invalid.
Detailed Error Information
Module IIS Web Core
Notification Unknown
Handler Not yet determined
Error Code 0x80070003
Config Error Cannot read configuration file
Config File \\?\H:\ExcelAutomation\1.0\src\docs\web.config
Requested URL http://vmwws085381.msad.ms.com:80/index.html
Physical Path
Logon Method Not yet determined
Logon User Not yet determined
Config Source
-1:
0:
The solution for me was to open up IIS, click on my site, and under Advanced Settings change the physical path to the network share like \\server\share\.. instead of using the mapped drive.
Original source that helped me arrive to this solution is here: http://forums.iis.net/t/1157959.aspx
Another cause is not having the URL Rewrite Module installed if your web-app references this in the associated Web.config file – this is detailed in this Stack Overflow Question
The IIS server and the server with the shared folder must each have an account with the exact same username and password. Make sure this account has "Read & Execute", "List folder contents", and "Read" access to the shared folder.
Connect within IIS using UNC. (E.g., add a virtual directory to the site; enter an Alias; enter the physical path as \servername\foldername; click "Connect As..."; choose "Specific User"; click "Set..."; enter the user name and password referenced in step 1.) Current versions of IIS do not support mapped drives. Don't waste your time trying to make them work.
Also, make a big mental (or written) note for yourself and other administrators: If you ever change the password for that account, do it on both servers and within the IIS connection.
For someone who is getting this error on your local system, it can happen when you share code across multiple servers or copy an existing project to a new location and it's virtual directory path still refers to an older path.
This happened to me as I was sharing a project on a Google drive and was accessing it from 2 different systems. (I know, Should've used version control system)
Solution:
Right click on the project >> Web >> Create virtual directory
It will probably show a prompt. Select Yes and you are done.
The main reason behind this error is the physical path i.e web site folder cannot be under the users folder, desktop folder, or any related folder. If it's there, move it or place it on other drive and try again.
I have created an asp.net web application on my local machine and I am deploying it to sharepoint. For that I am refereing the following
Deploying ASP.NET Web Applications in the Windows SharePoint Services 3.0 _layouts Folder
[http://msdn.microsoft.com/en-us/library/cc297200.aspx]
Its works perfect on my local machine but when I was trying to deploy the same on clients machine it was giving me the "An unexpected error has occurred." Error.
The scenario is, There is not visual studio install on my clients machine so what I was doing is I simply copying my solution folder in 12'hives LAYOUT folder along with the bin folder. Then when I was try to access it by hitting the URL
http://[machineName]/_layouts/[MyCustomFolder]/default.aspx it was giving me the error mention above.
Can anyone help me to solve this issue..?
Thanks in advance..
Sachin
Unexpected error might be anything, You need to see what is the root cause of the Error,
Open the Web.Config file of the IIS SharePoint WebSite
Search for the CallStack and change it to CallStack="true"
Search for the CustomError and change it to CustomError="Off"
Browse the page you will get to know the actual issue that causes the error
You yourself can rectify it , it might be as simple as missing dll
Try to watch the logfiles, set logging level to maximum to be sure you see what sharepoint says about your page.
To do that, if you have access to the server:
open SharePoint Central Admin
go to Operations tab, select "Diagnostic logging"
select category 'All' and change the trace log level to 'Verbose', save changes
reset IIS server (for the purpose of a clean experiment)
open \\server\c$\Program Files\Common Files\Microsoft Shared\web server extensions\12
logs and order by modification date
try to load your webpage in /_layouts folder, see the error again
open the newest logfile you can see and search for [MyCustomFolder] name
Then post the error message here.
An unexpected error can have multiple reasons.
Go to C:\inetpub\wwwroot\wss\VirtualDirectories\80
Open Web.Config
Change
<SafeMode MaxControls=”200″ CallStack=”false”
to
<SafeMode MaxControls=”200″ CallStack=”true”
Turn off custom errors
<customErrors mode=”Off”/>
I know that is an old question but for me the fix was to stop and start again the SharePoint Web Application from IIS.
I have classic ASP running on IIS 7.
Even though I configured the ASP "Debugging Properties" to "Send Errors to Browser = True", the web app REFUSES to send errors to the browser and continues to send a 500 internal server error.
My browser has "Show Friendly HTTP Error Messages" unchecked.
Failed Request Tracing is installed (not sure if that's related)
Happens both on web pages loaded locally on the server and remotely
The App Pool is integrated (not sure if that matters)
Any ideas?
Try :
Internet Information Services (IIS) Manager —> Default Web Site —> Click Error Pages properties and select Detail errors
I was having the same issue with a Classic ASP app running in a subfolder of a site. I had enabled detailed errors and the 500 was still showing. My resolution was to enable parent paths in the ASP section in IIS for the site as the application was referencing the parent folder using "../":
I had this occuring on a Classic ASP application running in a subfolder of a site. The solution was:
IIS > Click into your Site > Click into your Application folder > Error Pages > Edit Feature Settings > set to: Detailed Errors
IIS Manager >> double click the ASP icon to open the ASP page. Expand the Debugging Properties node and set Send Errors To Browser to True.
Refer : http://www.chestysoft.com/asp-error-messages.asp
If your website is configured to connect to the physical path of the website as a specific user, instaed of using pass-through authentication, you may get this error if there is a permissions error with this user. It may also be necessary to restart the Windows Process Activation Service and then restart IIS.
If you are hosting the project in a shared environment then you can use the following snippet to view the errors.
<configuration>
<system.webServer>
<httpErrors errorMode="Detailed" />
</system.webServer>
<system.web>
<customErrors mode="Off" />
<compilation debug="true" />
</system.web>
Refer this URL for complete information http://blogs.iis.net/rickbarber/working-past-500-internal-server-error
Hope it helps someone
I had a 500 error with an ASP Classic application I had just installed on a new server (Windows 2019). Every URL on the application returned 500, no matter what. But no errors were being shown in the Windows event log, and despite configuring detailed errors, as mentioned in several the other answers here, no specific error was being displayed in the browser.
The only clue was in the IIS logs, which showed the HTTP status code as 500, and the IIS substatus code as 19. So a 500.19 error.
That led me to
and the specific issue I was having was answered by the second part of this section:
https://learn.microsoft.com/en-us/troubleshoot/iis/http-error-500-19-webpage#hresult-code-0x80070005
which says:
Don't configure the website to use UNC pass-through authentication to
access the remote UNC share. Instead, specify a user account that has
the appropriate permissions to access the remote UNC share.
and (this is the part I needed to do):
Grant the Read permission to the IIS_IUSRS group for the
ApplicationHost.config or Web.config file. To do it, follow these
steps:
In Windows Explorer, locate the folder that contains the
ApplicationHost.config file that is associated with the website, or
locate the virtual directories or the application directories that
contain the Web.config file that is associated with the website.
Note
The Web.config file may not be in the virtual directories or the
application directories in IIS. Even in this situation, you have to
follow these steps.
Right-click the folder that contains the ApplicationHost.config file,
or right-click the virtual or application directories that may contain
the Web.config file.
Select Properties.
Select the Security tab, and then Select Edit.
Select Add.
In the Enter the object names to select box, type
\IIS_IUSRS, select Check Names, and then select OK.
Note
is a placeholder for the computer name.
Select the Read check box, and then select OK.
In the Properties dialog box for the folder, select OK.
Note
Make sure that the folder properties are inherited by the
ApplicationHost.config and Web.config files so that IIS_IUSRS has the
Read permission for those files.