Short Tom Blog

Exception from HRESULT: 0x80041054

Issue

Following a fairly innocent reboot of all my SharePoint farm servers, all SharePoint site content was not displayed and I go the following error message.

Interestingly though, all the content under /_layouts/ was displayed with no issues. This made me think there must have been an issue with the content databases rather than the SharePoint servers themselves.

Reason

After much investigation (crawling through logs and internet searches), I determined (with the help of Matt Groves) that the SharePoint aware anti-virus (Symantec 5.1 for SharePoint) had stopped and left the VirusStatus code for the master page and several page layouts in anti-virus limbo.

When a virus is detected or when the service that connects SharePoint to the antivirus scan engine becomes unavailable, the antivirus scanner sets the VirusStatus code to a non-zero and non-null value. This makes SharePoint believe the files have a virus and won’t display it (pretty disastrous when its the master page!).

The scan engine became unavailable because the temporary licence for the Symantec 5.1 for SharePoint had expired. I believe the reboot stopped the scan engines from running, the license may have expired days or weeks ago.

You may also have an issue if you remove your SharePoint aware anti-virus.

Solution

Run the following SQL Query against your content database(s) to determine if they have have files stuck in AV limbo

SELECT * FROM Docs

WHERE (VirusStatus > 0) AND (VirusStatus IS NOT NULL)

(see http://support.microsoft.com/kb/928169 for more detail)

This will return all files which SharePoint believes are viruses.

Enable your SharePoint aware anti-virus (I did this by applying a new license code to all the SharePoint servers). If you’ve uninstalled it, reinstall your AV, fix the content and follow products recommended removal process.
Run a manual AV scan on SharePoint using your SharePoint aware AV.
Run the SQL Query again to make sure no virus items are returned. if they are, run your manual scan again and try and determine if you have a virus.

SharePoint 2007 Visio Shapes

A while back now I created a Visio Stencil full of MOSS 2007 Shapes. I have since added extra shapes. It now includes the following servers, plus the ability to create your own servers from the individual shapes.

MOSS 2007 servers
WSS V3 Servers
Virtual MOSS 2007 Server
VM Host Server
ISA Server
Search Server
SQL 2005 & 2008 Server
SPS 2003 Server

Download SharePoint 2007 Visio Stencil

Work will begin soon on the SP2010 Visio shape set. Watch this space.

My New Blog

Hello,

Welcome to my new blog.

This is my second blog as my previous blog at sharepointblogs.com died for the second time in a year.

RIP Stop Collaborate and Listen

Watch this space for interesting information on Sharepoint, Music and Technology.

Cheers,

Tom

Visual Studio 2008 WSS extension 1.3 on Windows Server 2008

I installed Visual Studio 2008 Extensions Version 1.3 CTP (VSeWSSv13_AMD64_Build-433.exe available from here) on my Windows Server 2008 with MOSS 2007 and IIS 7. The Visual Studio extensions gives you the solution generator used to create list and site definitions.

When I tried to open the Solution Generator, I got the following Error:

Error 2 The content type text/html; charset=utf-8 of the response message does not match the content type of the binding (text/xml; charset=utf-8). If using a custom encoder, be sure that the IsContentTypeSupported method is implemented properly. The first 1024 bytes of the response were: '<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">

<html xmlns="http://www.w3.org/1999/xhtml">

<head>

<title>IIS 7.0 Detailed Error - 500.0 - Internal Server Error</title>

<style type="text/css">

<!--

body{margin:0;font-size:.7em;font-family:Verdana,Arial,Helvetica,sans-serif;background:#CBE1EF;}

code{margin:0;color:#006600;font-size:1.1em;font-weight:bold;}

.config_source code{font-size:.8em;color:#000000;}

pre{margin:0;font-size:1.4em;word-wrap:break-word;}

ul,ol{margin:10px 0 10px 40px;}

ul.first,ol.first{margin-top:5px;}

fieldset{padding:0 15px 10px 15px;}

.summary-container fieldset{padding-bottom:5px;margin-top:4px;}

legend.no-expand-all{padding:2px 15px 4px 10px;margin:0 0 0 -12px;}

legend{color:#333333;padding:4px 15px 4px 10px;margin:4px 0 8px -12px;_margin-top:0px;

border-top:1px solid #EDEDED;border-left:1px solid #EDEDED;border-right:1px solid #969696;

border-bottom:1px solid #969696;background:#E7ECF0;font-weight:bold;f'. 0 0

Following some Googling (or should that be Binging) The reason was because Visual Studio 2008 Extensions Version 1.3 CTP uses WCF in the deployment process and you cannot run WCF in IIS 7 unless you do the WCF HTTP Activation, and the default configuration of Windows server 2008 doesn't provide this, so you can do WCF HTTP Activation by following these steps:

Go to the start menu Text box and type: Programs and Features.
Click on Turn Windows features on or off on the left panel

Click On Features --> Add Features:
Check HTTP Activation Check box under WCF Activation:
Install the Feature