Winforms Project – Unspecified error (Exception from HRESULT: 0×80004005 (E_FAIL))

We’ve been recently working on a Win Forms projects for the first time in a long time. Whilst working through the security and trying to implement Client Application Services following this we ran into a problem. By right clicking on the User Interface Project, then selecting “Properties”, then clicking the “Services Tab”, we got the following error, “Unspecified error (Exception from HRESULT: 0×80004005 (E_FAIL))”.  We are using Visual Studio 2010 Ultimate, with .Net 4.0 Targeting.

Solution:-

We deleted the existing UI project and recreated it , added back our source code and presto it all worked again. My guess is the project file had become corrupted in some form.

We’re now up and running again, implementing our security providers and locking down our application.

Advertisements

SharePoint 2010 Error TaxonomyPicker.ascx

I love having a Development Environment I can simply return to a known snapshotted point, but it seems so long between new set ups that you forget some of the gotcha’s that you fixed when you initially set it up. This is one of those really frustrating ones that seems to appear on a lot of servers in the wild and one I’d completely forgotten about until today when I had to fix it again.

I got the following critical error :-

Web Controls Critical 7043 Load control template file /_controltemplates/TaxonomyPicker.ascx failed: Could not load type ‘Microsoft.SharePoint.Portal.WebControls.TaxonomyPicker’ from assembly ‘Microsoft.SharePoint.Portal, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c’.

The fix for this is simple, open the TaxonomyPicker.ascx control which is in the hive under ControlTemplates (the full path is usually C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\CONTROLTEMPLATES) and take a look at the top of this file:-

<%@ Control className="TaxonomyPickerControl" Language="C#" Inherits="Microsoft.SharePoint.Portal.WebControls.TaxonomyPicker,Microsoft.SharePoint.Portal, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %>

Highlighted in this snippet is the , which is the html encoding for a comma (,), by adding an actual comma and a space after it this issue is fixed, so this line should look as below:-

<%@ Control className="TaxonomyPickerControl" Language="C#" Inherits="Microsoft.SharePoint.Portal.WebControls.TaxonomyPicker, Microsoft.SharePoint.Portal, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %>

Thats it fixed, the error is gone, if only all critical errors that appeared were that easy to fix.

Configuring SQL Report Server 2008 SP1

When configuring a SQL 2008 SP1 reporting server I got this error, “The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel”  when I trying to view the http://servername/Reports url. This appeared a bit odd as I wasn’t trying to connect via SSL to the site.

 

image

Luckily the fix here was an easy one, I simply had to alter the “rsreportserver.config” file and make the following change.

From:

 
<Add Key="SecureConnectionLevel" Value="2"/>

To:

 
<Add Key="SecureConnectionLevel" Value="0"/>

Which resolved the issue and displayed the page.

image

 

There is more detail on this here. This basically means that this will need to be revisited again when it comes time to enable reporting services out to the web via an SSL.

Slipstreaming SQL 2008 Sp1

If you try installing SQL 2008 RTM on either Windows 7, Vista Sp2 or XP Sp3 you will find that install fails. There is a really easy fix for this by simply slipstreaming Sp1 with the RTM image by following these instructions here.

In terms of the actual problem I’m not sure of what the exact cause is here although I suspect it’s related to this issue with MSXML.

In Place Server 2000 Upgrades

As part of a MOSS implementation I’m currently working we need to include one of those intranet applications that every company seems to have, one of those legacy web apps that nobody seems to know how it works, but it’s mission critical running on a beige box, running on Server 2000. Well I’ve just been working to migrate on of these stunning applications for a client. We tried moving it but it was becoming painful as this had several MCSE 2000 Database, and access database in it.

We decided that best way to deal with this was to move it to a Virtual Machine using p2v, which once it got the drivers sorted, worked like a breeze. The problem we had was that we couldn’t upgrade it directly to Server 2003 R2 Service Pack 2. We have worked out that you need to Install Server 2003 without R2 and with no slipstreamed Service Packs to get the in place upgrade working. At this point we had all sorts of issues, we kept getting the error ”Unable to copy ac6639k5.sys to C:\$WIN_NT$.~BT\”. We originally thought this was a corrupt ISO of Server 2003 so we downloaded it again, same problem again. I found this post which describes a similar issue with an XP sp2 to sp3 upgrade. I followed this fix and it worked a treat and the server is now upgraded to Server 2003.

The fix is so simple it’s not funny, when the Windows upgrade complains it can’t copy the file, select skip file and press escape to stop the reboot, go back onto the C:\ and look for the “C:\$WIN_NT$.~BT\” or equivalent directory where you will find the file “unsupdrv.inf” simply look for the header for the randomly named file which in my case was “ac6639k5” and leave the headers in place and simply delete the line below the headers. Once you reboot the upgrade will proceed painlessly.

The only additional step that was required post install was to re-enable the IIS services and the application ran seamlessly, and yet another beige box bites the dust.

Installing Telerik MOSS Editor

I’ve been working for a client where they have decided to implement the Telerik MOSS RadEditor. The editor definitely makes some great advancements against the default editor that comes out of the box with Sharepoint. Probably in my rush to get this installed and operation I missed some steps, so I thought I’d run through some of my experiences in getting this working.

  1. Download and install the ASP.Net Ajax Extensions from here this will need to be installed on all front end servers, although I’d recommend doing this on all servers in a farm in case there’s a need to redeploy servers later.
  2. Enable Ajax on all the Sharepoint front end servers. Again I’d recommend doing this to all servers. The instructions can be found on Mike Ammerlaan’s blog, here. A word of warning here these steps are pretty messy, and involve manually editing the web.config in several places. I’d strongly recommend that there is a backup copy of the web.config made before you start changing this file so that you can easily roll back in case something goes wrong, especially in production environments. You may also want to consider writing a Nant or MSBuild script to repeat these steps, especially if you are deploying into a large farm environment.
  3. Once the first 2 steps are completed the rest of the installation is pretty straight forward by adding the solution to the server in your farm which contains Central Admin. Simply follow the steps on Telerik’s site here.
  4. One last step that isn’t documented is to do an IISRESET following the deployment of the solution. Not sure exactly why but I couldn’t get it working without this magic last step.

VS 2008 Support for WSS in VSeWSS version 1.2!

The Sharepoint Team Blog have just announced Version 1.2 of the Visual Studio Extensions for WSS, which now supports Visual Studio 2008. This new version is only work with VS 2008, so if you’re still working with VS 2005 you will need to stick with Ver1.1.

Version 1.2 can be downloaded from here.