Monthly Archives: January 2014

SharePoint, x64, and “The list cannot be displayed in Datasheet view…” issues

So there we were, shiny new installs of Office 2013 x64 (with all three colors!) rolled out to our enterprise.  All was good in the world until we received a phone call from operations asking a seemingly simple question:  “Why can’t I see my SharePoint lists in Datasheet view?”. 
What the…???

The Error

The list cannot be displayed in datasheet view for one or more of the following reasons:

SharePoint Error Datasheet


The Root Cause

SharePoint 2010 (Enterprise or Foundation) lists do not work well with 64bit versions of Microsoft Office.  This applies to both Office 2010 and Office 2013.


The Solution

You need to install “2007 Office System Driver: Data Connectivity Components” on each client workstation / PC which have a 64bit version of office installed.  This install will put the necessary Active-X components on your workstations to allow SharePoint Datasheets to be used with 64bit versions of office.
Download the install from Microsoft at

VHD Liposuction–How to shrink a dynamic VHD file after reclaiming space

The Problem
You have a 250GB VHD Dynamic VHD file which has eaten too much of your Hyper-V host’s drive space (WSUS Instances come to mind).   You have accessed the virtual machine and deleted/removed the unwanted bloat that occurs over time.  But, you still can’t shrink the .VHD file on the host server.

The Solution

Simply deleting or otherwise removing files from your virtual machine’s drive does not allow the VHD to be shrunk.  You must “Zero Out” the unused sectors so Hyper-V can reclaim the space.


The How To

  1. Download Secure Delete from Microsoft onto the Virtual Machine
    Important: Remember to unzip the file to an easy to access location.
  2. Open a Command Prompt
    Important: Remember to launch as Administrator!
  3. Execute SDelete as follows (where [path] is the located you unzipped the file)
    [PATH]sdelete –c -z
  4. Accept the terms and let it run
  5. Wait….
  6. Shutdown the virtual instance
  7. Launch Hyper-V Manager on the host server
  8. Open up the setting panel for the Hyper-V instance you wish to perform a VHD shrink for.
  9. Select the drive you wish to compact and click Edit
  10. Select Compact and click Finish
  11. Wait…


That is it!  Your done!

WSUS Liposuction–How to reclaim drive space from an out of control WSUS instance.

Windows Server Update Services (WSUS) is a wonderful method of centralizing how your Windows based environment retrieves Microsoft updates.  The benefits range from fine grained control of which updates to deploy to reducing your network bandwidth requirements during patch Tuesday.

There is, however, a dark downside to WSUS:  It will slowly eat up drive space while slowing to a crawl. 


TLDR:  Flag as “Declined” all unneeded WSUS updates (simple eh?)


  1. Launch Windows Server Update Services
    Important: Launch as Administrator!
  2. View All Updates
    Navigate to [Server Name] –> Updates –> All Updates
  3. Right click on the grid heading and show the following columns: “Supersedence”, “Needed Count”, “Installed Count”, “Not Applicable Count”
  4. Set your filters to Approval = “Approved” and Status = “Any”
    Important: Remember to click Refresh
  5. Wait….
    (If you have a lot of Approved updates, this will take awhile!)
  6. Sort by Supersedence and select all updates which have been Superseded.
    What you will find is a *lot* of updates approved for “Install” which have been superseded
    Important:  There are three Supersedence icons.  Do not select the icon with the blue square at the top without reviewing first to verify the update does not apply to your environment!  These are the latest (most current) updates in the Supersedence chain!
  7. Right click and “Decline” the superseded updates
    Important:  You may receive and “Error: Unexpected error”  while WSUS is declining the updates.  Ignore this as it is simply a timeout as WSUS is *very* busy.  You can hit “Reset Server Node” once the declining is complete.  You may want to verify all “Superseded” updates have been “Declined” by repeating steps 4 – 7.
  8. Click Refresh to update the list of updates.
  9. Sort Descending by Not Applicable and navigate to the top most row
  10. You will very likely see many rows that:
    Needed Count = 0
    Installed Count = 0
    Not Applicable Count = [Number of computers WSUS is servicing]
    These are “Approved”  updates which are not needed by your environment.
    Highlight, Right Click, and “Decline” any updates which do not belong to your environment
    Caution! It is recommended you review the updates to verify you are not declining something which may become part of your environment at a future date.
  11. Navigate to Options and select Server Cleanup Wizard
  12. Uncheck all boxes EXCEPT Unneeded Update Files and click Next

  13. Wait….
    (This is actually pretty fast)


That’s it!  Your done.  Now go bask in the glow of your reclaimed drive space!

One Last Note:
If your WSUS server is running as a virtual server on Hyper-V AND you are using dynamic drives, you’ll want to read
VHD Liposuction – How to shrink a dynamic VHD file after reclaiming space