Group items tagged

Apparently, the reason I was recieving the Internal Server error message was that I had installed SQL Server 2008, after installing Visual Studio 2010, and because of this it corrupted the IIS Machine level configuration files ("If you install VS2010 and then install VS2008 and VS2008 SP1, the configuration files for ASP.NET in IIS only include about 1/2 of the correct .Net 4.0 configuration sections." read more here).

"Restore or repair the database"

"Exception: System.UnauthorizedAccessException Message: Access to the registry key 'Global' is denied. Source: mscorlib"

Loaded our internal dev site and received the titled error. Apparently this happens sometimes when running DotNet 3.0 or 3.5 WCF features on a DotNet 4.0 framework.

In this post I will show you how to troubleshoot Web Resource related problems and how to deal with them.

Useful code snippet to log what is causing IIS site shutdowns. BOOM

If Visual Studio 2008 shuts down unexpectedly for you, follow these instructions to download the hotfix.

"The installation program does not detect the mode IIS 6 is currently running and set the x64 component up if the OS is 64-bit. This can cause the following error: "Attempted to load a 64-bit assembly on a 32-bit platform. Use ReflectionOnlyLoad() instead if trying to load for reflection purposes." In order to fix this manually, replace the system.data.sqlite.dll in the bin folder of your site with the file provided on this page."

Instructions for converting sitecore web site to Visual Studio Web Application are in this doc

Instructions for converting sitecore web site to Visual Studio Web Application are in this doc

"The Controls Collection Cannot Be Modified Because the Control Contains Code Blocks"

WFFM Assembly issues when on Sitecore 6.3+

BlueScreenView scans all your minidump files created during 'blue screen of death' crashes, and displays the information about all crashes in one table. For each crash, BlueScreenView displays the minidump filename, the date/time of the crash, the basic crash information displayed in the blue screen (Bug Check Code and 4 parameters), and the details of the driver or module that possibly caused the crash (filename, product name, file description, and file version). For each crash displayed in the upper pane, you can view the details of the device drivers loaded during the crash in the lower pane. BlueScreenView also mark the drivers that their addresses found in the crash stack, so you can easily locate the suspected drivers that possibly caused the crash.