Baffling Error in VS2008 with VSeWSS

A colleague and I were both encountering a baffling error today when trying to use VSeWSS 1.3CTP features (such as WSP View or Deploy) within Visual Studio 2008 on a newly built VM running Windows Server 2008 and MOSS 2007 Enterprise Edition.  Neither of us had encountered this problem running VSeWSS 1.3CTP under Windows Server 2003.

The error we were receiving was..

Error 1
Error parsing Solution. Error: System.ServiceModel.ProtocolException
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: ‘<html>
        <title>Object reference not set to an instance of an object.</title>
         body {font-family:"Verdana";font-weight:normal;font-size: .7em;color:black;}
         p {font-family:"Verdana";font-weight:normal;color:black;margin-top: -5px}
         b {font-family:"Verdana";font-weight:bold;color:black;margin-top: -5px}
         H1 { font-family:"Verdana";font-weight:normal;font-size:18pt;color:red }
         H2 { font-family:"Verdana";font-weight:normal;font-size:14pt;color:maroon }
         pre {font-family:"Lucida Console";font-size: .9em}
         .marker {font-weight: bold; color: black;text-decoration: none;}
         .version {color: gray;}
         .error {margin-bottom: 10px;}
         .expandable { text-decoration:underline; font-weight:bold; color:navy; cursor:hand; }
    <body bgcolor="white">
            <span><H1>Server Error in ‘/’ Application.<hr width=100% size=1 color=silver></H1>
            <h2> <i’.

Log file written to: C:\Users\developer\AppData\Roaming\Microsoft\VSeWSS 1.3\VSeWSS1.3.log  0 0 

Hitting Google and Bing found nothing helpful nor was there anything related in MSDN or TechNet. With a little more digging I think it is caused by a problem in the .NET Framework installation or possibly the VSeWSS 1.3 CTP installation (can be sure which though). To fix the problem you need to register the script maps for WCF under .NET 3.0 as it seems WCF is used by VSeWSS to communicate with its special web application. For some reason I can’t understand it was done in the server 2003 install but not in 2008. Script maps can be registered using the ServiceModelReg.exe utility under the .NET 3.0 framework folder ( I ran with the -i option and it fixed the problem.


Leave a comment

Filed under Microsoft Office Sharepoint Server 2007

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s