Pages

Showing posts with label WHS. Show all posts
Showing posts with label WHS. Show all posts

Thursday, 13 October 2011

How to fix the WHS 'cqvsvc.exe' error and Media Center's Console View

Today, I'm a very happy man. Ever since I upgraded my WHS system to Power Pack 3 a couple of years ago, there has been an incredibly annoying glitch related to the WHS Media Center Connector service, and after months of searching I finally stumbled on an answer. Hooray!

The main problem has been that, apart from a brief period when I first installed the Media Center Connector, the Console View tab refuses to work, giving an error message. Also, on the WHS system, looking at the Application section of Event Viewer revealed that a service called Cqvsvc.exe (which is the Console Quick View Service) was generating an error every minute of every day. For nearly two years.

It wasn't causing any system problems or instability as far as I'm aware (the TV Archive service was working perfectly), and my WHS system has been as steady as a rock ever since I built it in 2009.

However, it was incredibly annoying to see these messages, and not to be able to view the Console status in my Media Center PC, which is my secondary living room PC. (I also run Media Center on my main work PC, mainly for recording odd programs via RF from my Virgin Media cable TV box).

I've regularly trawled around various sites and forums looking for an answer, but it came to a head today when I tried to install the WHS Health add-in and it failed with an error relating to the non-existence of health.xml in the WHS C:\inetpub\intranet\health\ directory. Eh?

Turns out this file is where Cqsvc.exe gets its health info from, and so if it doesn't exist, an error is generated.  The specific error I was getting in the Event Viewer was Error 9000, "System.Management.ManagementException", with a further description of "Invalid class"


(On a separate note, it seems from my investigations that there are many different error messages caused by Cqvsvc.exe, and the fix here may well only apply to this particular error, so I can't guarantee results).


The first thing to try if you're having this error is to try and look at the health.xml file. It's located at http://[servername]:55000/health/health.xml  (substitute your WHS server's name for [servername]) - put this into a browser and you should see the file appear. It looks like this:




If instead you get an error message, the chances are that the file hasn't been created, as in my case, due to the Cqvsvc.exe problem.


I found the fix on this thread on the MS Home Server forums (scroll down to a reply from Donald Lu, who appears to be a Microsoft employee - thanks, Donald!). To run it, open Remote Desktop connection to WHS machine, then open a command prompt (press the Windows key and R, then type 'cmd' in the Open box and press Enter).

Now type:

winmgmt /resyncperf

then press Enter. And that's it!


There will be no messages in the command prompt, so just close it. You don't even need to reboot the machine. Now try opening the health.xml file again as described above - it should now be there. And the Media Center Console view should be working, just like this:


I hope this helps anyone who, like me, has been driven to distraction by this problem.

Friday, 15 April 2011

Review: Windows Home Server 2011

I'm a user (and big fan) of the current version of Windows Home Server - it keeps all my documents safe and sound, and has several times saved my bacon when I've managed to trash one of my several Windows installations. So I was looking forward to WHS 2011, and grabbed the RTM from Technet as soon as it appeared. You can read my findings in my review for The Inquirer, but suffice it to say I'm afraid I'll probably be sticking with my existing installation unless someone comes up with a solid, reliable replacement for Drive Extender (there are a couple in the offing, such as Drive Bender and StableBit Drive Pool).








Tuesday, 9 November 2010

How to fix the 'Cannot mount the backup' problem in WHS

Regular readers will know that I'm an ardent fan and user of Windows Home Server (WHS). Last year I built my own system to look after my three PCs, a job that it's done admirably, despite a couple of failed drives (note: never put ancient drives in USB enclosures, it's a false economy!).

But the other day I decided to check some old versions of files using WHS's file and folder restore facility, which temporarily loads a backup set as a Windows volume. The progress window on the WHS console got to 100%, but on the Windows 7 client window it always stopped at 81% before popping up an error message saying 'Cannot mount the backup'. This was very frustrating, as mounting the backups worked fine on my other two PCs, so it obviously wasn't a WHS issue.

WHS can mount backed up partitions as Windows volumes. Sometimes.

Looking around the various WHS forums, I found several suggestions for a fix, none of which worked. Eventually, a post on the We Got Served forums led me to a thread on the Microsoft forums which mentioned a problem with Diskpart. I tried this and it worked first time, although I've no idea why automount was disabled in the first place.

Here's the fix:

  1. Right-click the Command Prompt icon and choose 'Run as administrator'. (Command Prompt is located in All Programs, Accessories).
  2. Type 'diskpart'. After a couple of seconds the prompt will change to 'DISKPART >'.
  3. Type 'automount enable' and press Enter. You should see a confirmation message.
  4. Type 'exit' to quit Diskpart and 'exit' again to quit the command prompt.



Try mounting the backup partition again via the WHS console and it should now work. It seems as though there may be multiple causes for this behaviour, so I'm not guaranteeing it will work for everyone.

Update  20/11/2011: To those who are worried that this problem means that the backups themselves are corrupted, don't panic - the problem is caused by the client PC, not the WHS backups. The backups are perfectly safe and you should still be able to perform a full system restore from the backups, using the WHS client restore disc. The problem discussed here only affects the ability to restore individual files and folders.

Another thing to check if this fix doesn't work is to make sure that nothing is using the Z: drive. In Explorer, click Tools, Disconnect Network Drive. Highlight anything using the Z: drive and click OK. You can also do this from the command line. Type 'net use' to see a list of drive mappings. If Z: is in use, remove it by typing 'net use Z: /delete'. This won't delete data from any drive, it just removes the drive mapping.

Thursday, 9 September 2010

Acer launches new Aspire EasyStore H341 home server

Acer has launched an updated version of the current H340 Windows Home Server box. The new model uses a D410 Atom single-core CPU with Hyperthreading, but otherwise it's pretty much identical. I've written a brief summary over on ZDNet's First Take blog.

Update : Although I requested a review unit of this product, I have now been informed by the PR company that this product will not be launched in the UK. 

Tuesday, 15 June 2010

Intel DH55TC network drivers for Windows Home Server client restore

Windows Home Server is superb, except for one really really annoying aspect. The WinPE-based restore procedure for client PCs doesn't detect the network card on any of my three home PCs, meaning I have to find the driver files and put them on a USB key for WHS to find manually. What's more, the drivers that WHS automatically extracts from the client PCs and stores with each backup image don't work either (not sure why, although the restore CD is based on Vista, whereas all my PCs are Windows 7), and in the case of the Realtek NIC in my Acer Aspire One netbook, even the correct drivers from Acer don't work due to some sort of bug.

I sorted out the Aspire One problem a while ago, thanks to this post on the Microsoft WHS forums, which pointed me to a suitable generic driver on the Realtek website. For the Intel DX48BT2 board in my main desktop PC, it was a little easier, but still a nuisance. And when I built my new media PC with a brand new DH55TC motherboard and onboard Intel Gigagibt NIC, I thought it would surely be supported. Nope.

The problem with Intel NIC drivers is that they are bundled in an installer package, so you can't just download a few versions and try them out. Luckily, the team at DriverPacks.net does this for you, collecting thousands of drivers for every conceivable device. The idea is to use the driver packs for slipstreaming Windows installs, or just to keep everything up to date. I got the latest LAN driver pack, extracted all the Intel driver directories onto a USB key and tried it - success! So if you have a WHS client using this board, here's the step-by-step procedure :

  • Download the latest Windows Vista (x86) driver pack for LAN drivers 
  • Using 7Zip, open the downloaded file and navigate to the x86/L/Intel directory. 
  • Copy the entire contents of the Intel directory to a USB key or CD
  • Boot from the WHS Client Restore CD, and when it doesn't find any network drivers, click 'Install Drivers'
  • Put the USB key into the PC, then click Scan. After a few moments it should say 'Drivers found...'. Click OK and you should now see that it has detected the Intel Gigabit NIC. Now continue the restore as usual.
Update: As Windows Server 'Vail' (the new version of WHS based on Windows Server 2008) uses a very similar restore procedure, this same procedure should work there too. I tried it successfully with my Aspire One netbook)