Have you ever wanted detailed errors to be returned from your Sharepoint Application Pages? Selecting "Detailed Errors" in IIS will not do it alone. In addition, you need to do the additional step below.
Open the web.config at "C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\LAYOUTS\web.config"
Change <customErrors mode="On" /> to <customErrors mode="Off" /> under the system.web node
There are no notes on this topic
Have you ever had an Internal 500 error when you open Sharepoint Central Admin?
Step 1, is to enable failed request tracking for the Central Admin Site. This is done by opening IIS, clicking on the Central Admin Site, and choosing Failed Request Tracking.
Step 2, is to open Central Admin again, and view the failed request log.
Step 3, in my case, the Sharepoint14Module was causing an issue. "Module 'Sharepoint14Module' could not be found' was the message.
Step 4, the message in step 3 pointed me to the ApplicationHost.config file. Sure enough, that module was pointed to an App Pool that did not exist.
Step 5, change the App Pool to a valid App Pool, and save the ApplicationHost.confg file.
All should be well, assuming your issue was due to a module error.
The key to this post, is that failed request tracking saved the day. I was not getting anything in the Sharepoint log, or the IIS log at all. By enabling failed request tracking, I was able to pinpoint the error that was really happening, and fix it.
Have you ever tried to allow uses to download a file, for instance a .dmg file, but your users could not do so? This happens because the .dmg file type is not defined in the MIME Type Settings in IIS.
- Open IIS
- Click on the site affected.
- Click "Mime Types"
- Click "Add"
- Enter ".dmg" in the file extension text box (no quotes)
- Enter "file/download" in the MIME type text box (no quotes)
- Click "OK" and you are done. Your users will now be ble to download .dmg files from your web server.
These instructions are for IIS version 7
When deploying a feature in SharePoint 2007, Visual Studio 2008, you get the odd and vague error "Object Reference Not Set To An Instance Of An Object" error.
The solution that worked for me, was to change th "Load User Profile" to "true", in the Advanced Settings of the Cetnral Admin App Pool. Mine was set to false by default.
I have no idea why this works.
I was trying to debug a SharePoint 2007 feature, in Visual Studio 2008, on IIS 7, and was getting the "unable to start debugging on the web server the web server is not configured correctly" error. I seen many posts on this but what worked for me is documented below.
Open up you site in IIS.
Right click on the site, and choose Properties.
Click ".Net Compilation"
Under "Behavior", click Debug and set to True.
Now you can debug from Visual Studio
There are no notes on this topic.
Have you ever wanted to disable redirection for certain pages in IIS 7?
1. Create an empty file called Index.html in the ROOT directory for which you want to redirect.
2. Now go to Content View, select Index.html, and choose HTTP Redirection
3. Set the URL for where you want requests to redirected.
4. Now you are good to go. Any request that comes in using the default document will be redirected, and any request that comes in to a specific URL will not be redirected. This comes in handy if you have a Sitmap HTTP Handler.
No notes apply to this topic.