This error occurs when a 32bit application attempts to access a 64 bit .NET library which is not authorized by default in Windows 2008 R2 since it is a 64bit OS.
Run the following commands from an administrator command prompt to enable the .NET 32 bit libraries to be accessible via your IIS 7.5 web server :
- cscript %SYSTEMDRIVE%\inetpub\adminscripts\adsutil.vbs SET W3SVC/AppPools/Enable32bitAppOnWin64 1
- %SYSTEMROOT%\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis.exe -i 3.
Your 32bit application should now work on your 64bit server.
I don’t know about anyone else, but I get tried of doing this in the registry, so I thought it might be interesting to just do this via PowerShell:
New-ItemProperty HKLM:\System\CurrentControlSet\Control\Lsa -Name “DisableLoopbackCheck” -Value “1″ -PropertyType dword
Things are definitely changing…people have always deemed the SharePoint certifications easy to get through… Well, for all of you who wanted it to be harder to obtain… Microsoft heard you… Check out what it takes now:
|Step||Title||Optional Training||Required Exams|
|1||Installing and Configuring Windows Server 2012|
|2||Administering Windows Server 2012|
|3||Configuring Advanced Windows Server 2012 Services|
|4||Core Solutions of Microsoft SharePoint Server 2013|
|5||Advanced Solutions of Microsoft SharePoint Server 2013|
Luckily, if you’re already SharePoint 2010 certified, you’ll only have to take three exams:
|Step||Title||Optional training||Required exam|
|1||Upgrading Your Skills to MCSA Windows Server 2012||417||417|
|2||Core Solutions of Microsoft SharePoint Server 2013||331||331|
|3||Advanced Solutions of Microsoft SharePoint Server 2013||N/A||332|
This MCSE certification requires you to show continued ability to perform in your chosen solution area by completing a recertification exam every three years.
For more information, check out http://www.microsoft.com/learning/en/us/mcse-sharepoint-certification.aspx
Remember when it was just one test to become a MCP, just 2 to become MCITP, and no re-certification every 3 years? Those were the days. =)
Start studying people… 😉
On Dec 29, 2011, Microsoft released a security update KB2656356 / MS11-100 (http://technet.microsoft.com/en-us/security/bulletin/ms11-100) for ASP.NET to address a potential Denial of Service vulnerability.
In the update, they introduced a limit to the number of data elements on an ASP.NET form. The default limit is 1000 data elements which can be easily met by complex 3rd party or custom webparts
Exceeding the limit will cause a ThrowIfMaxHttpCollectionKeysExceeded error.
After applying the patch, forms that exceed the limit will generate the following error (in ULS Log) attempting to configure/manipulate the webparts attributes :
System.Web.HttpException: The URL-encoded form data is not valid. —> System.InvalidOperationException: Operation is not valid due to the current state of the object.
at System.Web.HttpValueCollection.FillFromEncodedBytes(Byte bytes, Encoding encoding)
Add the following to the web.config of all web front end servers in your farm:
<add key=”aspnet:MaxHttpCollectionKeys” value=”10000″></add>
After the above is added, your various webparts should begin functioning normally.