Hi Paul,

>You can enable all the debugging and use their tracing tool to help debug this. In Visual Studio select Tools > WCF Service Configuration Editor and open the server .config file, then go to Diagnostics and click on the link to enable tracing and the link to enable message logging. Save it and do the same with the client (going from memory here, hopefully this at least gets you in the ballpark).
>
>Once tracing is enabled fire up the server and attempt to connect. If you don't already have it, you'll also want the Service Trace Viewer Tool which is included with the Windows SDK (\Program Files\Microsoft SDKs\Windows\v6.0A\bin\SvcTraceViewer.exe). You can fire it up and load the log files. It's actually pretty easy to poke around from there (although there is a ton of information displayed, hopefully you've got a nice high resolution monitor). If you don't have the SDK (or don't want to install it because it's huge), let me know - I can e-mail the file to you if you want.

It appears the exception is thrown with this info.
Process: WebDev.WebServer
Level: Warning
Source: System.ServiceModel
Activity Name: Execute 'System.ServiceModel.Description.ServiceMetadataExtension+IHttpGetMetadata.Get'.

Doesn't the "HttpGetMetadata.Get" have to do with the way it is configured in the web.config file?

Thanks again for your help.
Tim