Tuesday, September 20, 2011

Windows 8–Day 2

The Windows task Manager in Windows 8 is completely revamped. I like the new look of the task manager. It is very intuitive and a single place to go to to debug all the issues. The task manager itself consists of 7 main areas:

  • Processes
  • Performance
  • App History
  • Startup
  • Users
  • Details
  • Services

The Processes tab nicely explains what applications and background processes are running. It also gives a graphical view of the current CPU, Memory, Disk & Network usage of each of the process. Right clicking each process gives you the ability to end the process, create dump file and look at the properties:


The Performance tab gives you more details on the CPU, Memory, Disk and Networking usage. You can also launch resource monitor from the link at the bottom of this screen.


The App History tab is completely new and is for tracking the performance of the Metro Styled applications.


The startup tab give the information about the applications which are started during system startup. You can disable the unneeded ones by right clicking the application.


The Users tab gives you an idea about the users logged into the system and also the resources used by each of the users.


The details table gives you information about the applications which are running.


The Services tab gives you an idea about the currently installed services on the system.


Monday, September 19, 2011

Windows 8–Day 1

I recently installed Windows 8 DEV preview and so far it’s been a nice operating system to play around with.  I will try to document my findings as I use this new Operating System more frequently. After installing the Windows 8 OS with Developer tools, 64 bit version, I was trying to install Office 2010. The moment I ran the installer, it complained about 32 bit office components.  Something like:  “You cannot install the 64-bit version of Office 2010 because you have 32-bit Office products installed”. This was because of Microsoft PowerPoint Viewer which is 32 bit. I had to uninstall Power Point viewer to get Office 2010 installed. Power Point Viewer was installed by default. After installing Office 2010, the tools should be available to you:


Next, the one thing I don’t like at all is the restart option. In Windows 7, you could click Start –> Shutdown. But with Windows 8 , you will need to hover over the start button –> settings which would bring up the popup kinda thing on the right where you can restart the machine.


More later…..

Saturday, August 13, 2011

Secure Token Service related error 800703fa

While configuring SharePoint 2010 Farms, sometimes while using Claims Authentication the below error used to popup every morning on the front end servers. The strange thing is that it would disappear after an application pool recycle.

Retrieving the COM class factory for component with CLSID {080D0D78-F421-11D0-A36E-00C04FB950DC} failed due to the following error: 800703fa.

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.ServiceModel.FaultException`1[[System.ServiceModel.ExceptionDetail, System.ServiceModel, Version=, Culture=neutral, PublicKeyToken=b77a5c561934e089]]: Retrieving the COM class factory for component with CLSID {080D0D78-F421-11D0-A36E-00C04FB950DC} failed due to the following error: 800703fa.

If you look at the Stack trace, it becomes clear that the error is related to the WCF Service and in this case, it was related to the Secure Token Service (STS) application. To fix this error, open up IIS and navigate to the application pools section. In that are open the SecureTokenServiceApplication pool account and modify the “Load User Profile” property in advanced settings.

By default this property is set to False, change it to True and this should fix the error.


SharePoint 2010 Disable Mobile Page Redirect

When deploying SharePoint Farms, it is very important to consider the mobile aspects of using SharePoint also. Sometimes, it is very easy to miss this aspect. Out of the box, SharePoint 2010 provides few basic mobile pages. When you browse from a mobile, then you will be redirected to a different page rather than the regular publishing/wiki page you would see. You will be redirected to a page in layouts folder: /_layouts/mobile/mblwp.aspx.

If you are using a custom branded page for SharePoint 2010, then you may not want the users not to redirect to the out of the mobile page when browsing from their mobile.  The easiest and supported way to do this is to add a web.config entry for the respective web application. The below entry needs to be added under the node <system.web>:

   1:  <browserCaps>

   2:   <result type="System.Web.Mobile.MobileCapabilities, System.Web.Mobile, Version=, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"/>

   3:   <filter>isMobileDevice=false</filter>

   4:  </browserCaps> 

There are other ways to change this setting, specifically modifying the compat.browser file in the “App_Browsers” folder located in the application’s virtual directory. In here, you can disable the setting for a specific mobile. For example, to disable the redirect on IPhone, you would modify the isMobileDevice setting to false. By default it is set to true:

   1:  <!-- iPhone Safari Browser -->

   2:      <!-- sample UA "Mozilla/5.0 (iPhone; U; CPU iPhone OS 2_0 like Mac OS X; ja-jp) AppleWebKit/525.18.1 (KHTML, like Gecko) Version/3.1.1 Mobile/5A345 Safari/525.20" -->

   3:      <browser id="iPhoneSafari" parentID="AppleSafari">

   4:          <identification>

   5:              <userAgent match="iPhone" />

   6:              <userAgent match="Mobile" /> 

   7:          </identification>

   8:          <capabilities>

   9:              <capability name="isMobileDevice"                    value="true" />

  10:              <capability name="canInitiateVoiceCall"              value="true" />

  11:              <capability name="optimumPageWeight"                 value="1500" />

  12:              <capability name="requiresViewportMetaTag"           value="true" />

  13:              <capability name="supportsTouchScreen"               value="true" />

  14:              <capability name="telephoneNumberDetectionDisabled"  value="true" />

  15:          </capabilities>

  16:      </browser>