Archive for the ‘Windows 2008’ Category

How to fix “HTTP Error 403.14 – Forbidden The Web server is configured to not list the contents of this directory”

Wednesday, May 19th, 2010

We had a fresh install of Windows 2008 and Visual Studio 2010 on a developers machine that was getting this error when trying to access a MVC 2.0 .Net 4.0 website hosted locally on IIS7. Various fixes talk about making sure there is a default document, and also about turning on directory browsing, but neither of those work. (MVC 2.0 does not need a default document specified).

The issue was that .Net framework 4.0 had not installed correctly, so here is what you need to do to fix it.

1.) Run a command prompt as Administrator.

2.) Copy and paste the following text “C:\Windows\Microsoft.NET\Framework64\v4.0.30319\aspnet_regiis.exe -i”

This is assuming that you have already installed MVC 2.0 And .Net Framework 4.0 , but not in the correct order.

How to fix the “Key management services (KMS) host could not be located in domain name system (DNS) – 0×8007232B – MAK – KMS” issue

Monday, May 10th, 2010

When you try to activate a volume licence version of Windows 2008 Server (Windows 7 as well), you may get the following message.

Key management services (KMS) host could not be located in domain name system (DNS) – 0×8007232B – MAK – KMS

This is due to some changes made with the way Volume licence activations are done at Microsoft.

The way to fix this is as follows:

1.) Go into Control panel.

2.) Click on system(or System and maintenance depending on your control panel view).

3.) Click on change product key and enter your Volume licence key.

You should now be able to activate Windows!

How to fix Error TF84037 with Microsoft Excel Team Foundation AddIn

Monday, March 8th, 2010

We had a user who was trying to create a New List using the Team Excell AddIn, but she would get the following error each time “TF84037: There was a problem initialisinng the Microsoft Excel Team Foundation AddIn . Re-installing the Team Foundation Client may be required.

A re-install of the client was not a good idea, so I did some research and found that “.NET Programmability Support“  need to be installed for Excel.

To fix this in Windows XP/Windows Server 2003 do the following:

1. Close Excel and other Office programs.

2. Open Control panel

3.  In Add/Remove programs, locate your Office application and select it.

4.  Click on the ‘Change’ button

5.  Select ‘Add or Remove features’ and click ‘next’

6.  Select ‘Choose advanced customization of applications’ and click ‘next’

7.  In the tree view, expand ‘Microsoft Office Excel’ and make sure the .NET Programmability Support option is set to ‘run from my computer’.

8.  Click ‘update’.

For Windows Vista, Windows 7 and Windows 2008 Server, do the following:

1. Close Excel and other Office programs.

2. Open Control panel

3.  In Programs and Features , locate your Office application and right click it.

4.  Click on the ‘Change’ button

5.  Select ‘Add or Remove features’ and click “continue”

6.  In the tree view, expand ‘Microsoft Office Excel’ and make sure the .NET Programmability Support option is set to ‘run from my computer’.

7.  Click ‘continue’.

You should now be able to run the Excel Addin!

How to fix the Event ID 521 “Volume Shadow copy operation failed for backup volumes with following error code ’2155348129′ ” error when you try to backup a Windows 2008 server with Windows Backup

Thursday, February 25th, 2010

I was trying to do a single backup of Windows 2008 server using the built in Windows Backup program, but no matter what settings I chose, or where I backed it up to, it would always fail with the following error in the event log - Event ID 521 ” Volume Shadow copy operation failed for backup volumes with following error code ’2155348129′ ”

I decided to check the disk and found that there was an OEM partition installed and that it was set to active. I then right clicked on the C: drive partition and set that to active.

After this the backup worked fine. The problem with it is that in order for Volume Shadow copy to work, the partition with the operating system  has to be set as active.

How to fix the “Error: Failed to retrieve directory listing” in Filezilla server

Friday, February 19th, 2010

I was using the Filezilla client to connect to a Filezilla server on the LAN the other day, and I could not get a directory listing of the FTP server and I would have the following error “Error: Failed to retrieve directory listing” . I had opened port 21 on the firewall of the FTP server, but still could not get access.

I had to do the steps below, and after this I got access and a directory listing right away.

  • Open Windows Firewall under Control Panel.
  • If using Vista, click “Change Settings”
  • Select the “Exceptions” tab.
  • Click “Add program…”
  • Do NOT select “FileZilla Server Interface” from the list, instead click on “Browse…”
  • Locate the directory you installed FileZilla Server to (normally “C:\Program Files\FileZilla Server\”)
  • Double click or select “FileZilla server.exe” and press open (Once again, NOT “FileZilla Server Interface.exe”)
  • Select “FileZilla server.exe” from the list and click “Ok”
  • Verify that “FileZilla server.exe” is added to the exceptions list and that it has a check mark in the box next to it
  • Press “Ok” to close the window
  • How to fix “Validation of viewstate MAC failed. If this application is hosted by a Web Farm or cluster, ensure that configuration specifies the same validationKey and validation algorithm. AutoGenerate cannot be used in a cluster”

    Wednesday, August 19th, 2009

    We were testing the deployment of a website onto 2 load balanced IIS 7 servers the other day, and the sites were loading fine. the next morning one of the testers was reporting an erorr on the website that said     ”Validation of viewstate MAC failed. If this application is hosted by a Web Farm or cluster, ensure that <machineKey> configuration specifies the same validationKey and validation algorithm. AutoGenerate cannot be used in a cluster”   . We looked at the error and realised that we need to create a static machinekey and add it into the web.config of both our IIS7 web servers to fix the issue.

    We did this, but when we refreshed the page, we were still getting the same error on the website. We tried hitting the sites in new browsers and they loaded fine. What we realised was that becuase we hadn’t shut down the browser, it was still using the old machine key, and as it didn’t match the autogenerated one on the webserver that the browser was hitting, we would get this error.

    The steps to fix this are as follows:

    1. Generate a new static machinekey and enter it into both web.config files.

    2. Open a new browser window to test.

     

    Here is a sample machinekey entry for your web.config file

    <?xml version=”1.0″?>

    <configuration>

        <appSettings/>
        <connectionStrings/>
        <system.web>

            <machineKey validationKey=’3AE041467624C0947FE562E2DBE6122B532FBC4AA9845AE3D82EC6AC473104EA40A27F8E89BADDAEE44B1F7582FC47299B674ED1FD2DDE1368710504EB2C54C1′ decryptionKey=’2FC79A393A5A463F82D38828F43ED7D030C418B448C9E76C’ validation=’SHA1′/>

        </system.web>
    </configuration>

    How to add the Bluetooth stack to Windows 2008

    Sunday, June 21st, 2009

    I bought a cheap Bluetooth dongle the other day for my desktop PC so that I could talk to my Nokia phone and also to my Lego Mindstorms controller. After plugging in the dongle, it could not detect a driver which I thought may have been an issue, but seeing as it said it worked with Windows Vista, I thought it just  may have worked.

    I did some research and found this website that had information and a Bluetooth stack available. I have a copy of this file that you can download from the link below.

    Here are the steps to install the Bluetooth stack.

    1. Download the modified Microsoft Bluetooth Stack x64 Drivers and unzip it to your local hard drive.

    2. Go into device manager , right click on the “Unknown Device“  and choose “Update Driver Software

    3. On the “How do you want to search for driver software” dialog, select “Browse my computer for driver software”

    4. On the “Browse for driver software on your computer” dialog, click the “Browse” button and browse to the folder which contains the unzipped copy of the Microsoft  Bluetooth Stack drivers you downloaded previously.

    5. Click “Next”, and follow the instructions to complete the driver update and repeat for any other Unknown Devices.

    How to install “Nokia PC Suite” on Windows 2008

    Sunday, June 21st, 2009

    I am running Windows 2008 as a desktop OS for development purposes, and as a result, sometimes software won’t install when it does and OS check. I tried to install Nokia PC Suite version 7.1 the other day, but it kept coming back and saying “This operating system is not supported. Installation will not continue!“. The way around this is to the following.
    1. Right click on the Nokia PC Suite .exe file and choose properties.

    2. Click on the Compatibility tab.

    3. Tick the box that says “Run this program in Compatibility mode for: ” and select Windows XP (Service Pack 2)

    Run the .exe file again and the software should then install with no problems

    How to fix the “cannot connect to the virtual machine because the authentication certificate is expired or invalid” when trying to connect to a Windows Hyper-V virtual machine

    Monday, May 11th, 2009

    I tried to log in to a Hyper-V hosted Windows 2008 server today that hadn’t been rebooted in over 3 months. I got the following error  “cannot connect to the virtual machine because the authentication certificate is expired or invalid”.

    The quickest way to fix this is to apply the KB967902 patch from Microsoft which can be found below. This patch will also be applied as a Windows update.

    http://www.microsoft.com/downloads/details.aspx?FamilyID=289c831c-9142-4c00-bacd-6c1924ff0ecc&displaylang=en

    How to fix Event id 1111 TermServDevices printers not mapping in terminal server issue

    Friday, February 13th, 2009

    A common problem when using a terminal server, or remotely connecting to a Windows XP or Vista desktop is that the system you are connecting to does not have the required drivers installed for you to be able to print locally. Each time you log in, the system event log will contain 1111  errors that are related to TermServDevices for each local printer that does not have drivers installed on the local system.

    The simplest way to fix this is to download and run the Terminal Server Printer Redirection Wizard Tool  located here . When you run the tool, it searches the event log of the remote desktop for 1111 events, then asks you to install drivers for each printer that you wish to. The best thing to do is to run it on the remote desktop and download the drivers to a location on this same remote desktop for ease of installation.