Developer OneNote

Category: Windows

  • Run IIS in 32-bit mode on a 64 bit machine

    IIS 7 / 7.5 / 8

    On IIS 7 / 7.5 / 8,  configure website or web application to run under 32 bit mode can be configured by opening a command prompt and typing following command and press ENTER.

    %windir%system32inetsrvappcmd set config -section:applicationPools -applicationPoolDefaults.enable32BitAppOnWin64:true

    You can achieve the same goal in IIS Manager by opening the ‘Advanced Settings’ on the application pool binded to the website/web application you want to run under 32 bit mode and change “Enable 32-bit Applications” to True

    Enable 32 bit applications in IIS 7

    Click okay and now the web application or website you configured will run under 64-bit mode always.

    IIS 6

    For IIS6 on Windows Server 2003, configure ASP.NET to run in 32 bit mode on a 64 bit windows server.open a command prompt and type following command and press ENTER.

    cscript //nologo %SYSTEMDRIVE%InetPubAdminScriptsadsutil.vbs set w3svc/AppPools/Enable32bitAppOnWin64 1

    In IIS 6, you cannot run one Application Pool in 32-bit and others in 64-bit. But you can do this on IIS 7 and later as Enable32BitAppOnWin64 can be configured per application pool since IIS 7.  

  • How Can I Uninstall IE9

    IE9 Uninstalling is done via Windows Update control panel.  Select the view installed updates and then uninstall IE9 via the context menu.

    If you want to uninstall IE9 just because of degraded performance when viewing websites, you can try to turn off GPU rendering which might workaround the performance issue.

    1. In Internet Options, select the Advanced tab,
    2. Under Accelerated graphics, check the Use software rendering instead of GPU rendering checkbox.
    3. Click Apply then OK.
    4. Restart IE9

    (more…)

  • Hyper-V VM Slow on Windows Server 2008 R2

    I recently upgraded my virtual machine hosting server from Window Server 2008 to Windows Server 2008 R2. There are some noticeable performance drop, especially on virtual machines that handles big log files, the automation script execution time can take 200% or more than it was in a VMHOST with Windows Server 2008.

    I have done some testing and the performance downgrade seem introduced by the new power management system in windows server 2008 R2. There are 3 build in power plan in Windows Server 2008 R2

    • Balanced (recommended)
    • High Performance
    • Power Saver

    The default power plan in Windows Server 2008 R2 is Balanced. After I change Power Plan to High Performance and the performance downgrade issue does no occur any more. My guess is when power plan is set to balance, applications might not full utilize all available hardware resources.

    You can also checkout this post for Set the power configuration to High Performance in scripts.

  • Windows Server Features or Role Services required by this product are not enabled

     

    When you install Office Web Apps on windows 7 that has Sharepoint 2010, you will see following error message

    Setup is unable to proceed due to the following error(s):
    Windows Server Features or Role Services required by this product are not enabled.
    For a complete list, refer to the link below. For the list of pre-requisites needed to install the product please refer to:
    http://go.microsoft.com/fwlink/?LinkId=106209
    Correct the issue(s) listed above and re-run setup.
    You can install all required prerequisites for this product by selecting the ‘Install software prerequisites’ option in the splash screen. See Help for more information.

    Solution

    This is because Office Web Apps can only be installed on a server operation system.  Office Web Apps can only be installed on Windows 2008 Server x64 SP2 or R2 now. Also keep in mind Office Web App can only be installed after SharePoint Foundation 2010 or SharePoint server 2010 is installed.

  • Install PowerShell From Command Line

    To install PowerShell on Windows Server 2008 R2 or Hyper-V Server 2008 R2, following features needs to be installed.

    1. NetFx2-ServerCore
    2. NetFx3-ServerCore
    3. MicrosoftWindowsPowerShell

    Because Powershell is built on DotNet framework, DotNet 2.0 and 3.5  has to be installed prior to PowerShell installation.

    To install PowerShell from command line, run following from elevated command prompt

    DISM.exe /online /enable-feature /featurename:NetFx2-ServerCore DISM.exe /online /enable-feature /featurename:NetFx3-ServerCore DISM.exe /online /enable-feature /featurename:MicrosoftWindowsPowerShell

    Or run following command if it’s an 64bit machine

    DISM.exe /online /enable-feature /featurename:NetFx2-ServerCore-WOW64 
    DISM.exe /online /enable-feature /featurename:NetFx3-ServerCore-WOW64 
    DISM.exe /online /enable-feature /featurename:MicrosoftWindowsPowerShell-WOW64 

  • Enable DotNet 3.5 from command line

    To enable DotNet 3.5 from command line, run following from elevated command prompt

    dism.exe /online /enable-feature /featurename:NetFx3

  • Windows Live Essentials Setup fails

    When setting up Windows Live Essentials, the setup installer might fail with one of following error code.

    0x80070643

    Solution: See Error 0×80070643 When Install Windows Live Essentials

    0x80040609

    Solution: Turn on Windows Firewall

    0x8104000b Source WaitForCatalog

    Solution:

  • Windows Live Essentials Beta is released

    Windows Live Essentials Beta is released

    Today Microsoft announces releasing the Windows Live Essentials Beta, which include new versions of Messenger, Photo Gallery, Movie Maker, Sync, Live Writer and more   You can download it from http://explore.live.com/windows-live-essentials-beta.  You can read more about the new features here or watch the video. I also had a post for Windows Live Writer 4 new features, check it out. (more…)

  • WordPress 3.0 Cannot Export

    WordPress 3.0 is finally released with some great new features.

    I just upgraded my site to 3.0 today. The upgrade was smooth, however, I find that export doesn’t work any more. When I try to push export button to download posts xml file locally, I get following error.

    Warning: Illegal offset type in isset or empty in /home/content/22/5401722/html/wp-includes/taxonomy.php on line 176
    Warning: Cannot modify header information – headers already sent by (output started at /home/content/22/5401722/html/wp-includes/taxonomy.php:176) in /home/content/22/5401722/html/wp-admin/includes/export.php on line44
    Warning: Cannot modify header information – headers already sent by (output started at /home/content/22/5401722/html/wp-includes/taxonomy.php:176) in /home/content/22/5401722/html/wp-admin/includes/export.php on line45
    Warning: Cannot modify header information – headers already sent by (output started at /home/content/22/5401722/html/wp-includes/taxonomy.php:176) in /home/content/22/5401722/html/wp-admin/includes/export.php on line46

    WordPress FAQ suggests checking spaces in wp-config.php and remove blank spaces before <?php tag or after ?> tag, I try and it does not help.

    After trying deactivate on every single plug-in, I figure out it’s the plug-in Simple Tags that breaks WordPress 3.0 new export feature. Before Simple Tags owner releasing a fix, you can temp workaround this issue by deactivating Simple Tags plugin. After that, you will be able to get exported xml file to save.

  • Manual Uninstall Windows Desktop Search

    Here is how to uninstall Windows Desktop Search (WDS) as it is not visible in add-remove programs

    Manual uninstall Windows Desktop Search 3

    1. Click on the Start Menu, then Run.
    2. Type cmd in the box and click OK. This will bring up the command line.
    3. Type the following and press enter

      %windir%$NtUninstallKB917013$spuninstspuninst.exe /q /promptrestart

    4. A box will now appear to confirm the WDS has been uninstalled and asks you to restart. Once you have restarted the PC WDS will be gone.

    (more…)