IIS Internal Server Error – SharePoint/ASP.Net

I came across an issue at a client I was at and I was banging my head against the wall for a while. So I thought I should share. I was developing an HTTPModule that was being added to the web.config through a SharePoint feature. This part was working fine then all of a sudden the site starting throwing “500 Internal Server Error” messages. So I figured ok, I’ll just check Event Viewer for the machine. What did I find, nothing out of the ordinary. I tried a few other things including completely removing my HTTPModule and still no dice. So I tried resetting IIS, rebooting the machine, none of it worked. So I figured I would double check and make sure the module was removed.

So I went into IIS and selected the web site that I was working with. I then double clicked on the Modules option and was presented with an error “Cannot read configuration file because it exceeds the maximum file size”. So after a quick search on Bing I found that apparently ASP.Net has a limitation that the web.config file cannot exceed 250 KB. So I checked my config file and it was 257 KB. So I trimmed out some duplicated lines caused by another web.config modification from a feature and then the site came back up. So for anyone out there, hopefully this is helpful.

SharePointlandia Demo and Amazon EC2

I decided this week to change my demo from running on my laptop with its limited RAM and move it to Amazon’s cloud. Amazon has a pretty sweet setup where you can pay by the hour for the server time that you need. I now have a server that can handle the requirements of SharePoint 2013 without as many headaches as I had with my laptop. I looked at using cloudshare when I was prepping my demo for SharePoint Saturday Utah but I didn’t feel like paying that much for a whole month when I only needed the server to be running for a few hours.

I have the server setup after some fun oauth issues in SharePoint 2013. Now I have the fun part of transferring my demo content to this new server.

For those that are thinking of trying to run SharePoint 2013 on your own laptop. If you only have 8GB of RAM or less do not go there. You can get it working but all of the required pieces on one machine is too much. In order to do my last demo I had to turn off a bunch of services to free up memory. I had to severely trim the services for Search and the sad part was that my presentation was on search. So I had it crawl the content I needed then I turned off the crawler and indexer to free up the memory. Luckily no-one asked for live search results or changes. Now with this server that I can turn on whenever I want and only pay for the time that it is running I no longer have this problem. I love technology.