SharePoint Experts, Information Architects, Expert Witness

SICG provides a broad array of business and technology consulting from architecture to design to deployment of global systems with a focus on surfacing data in the enterprise. We focus on the "How", not just the possible. Contact me direct: or call 704-873-8846 x704.

Search This Blog

Wednesday, February 24, 2010

The binding at system.serviceModel/bindings/basicHttpBinding does not have a configured binding named

Odd message you might encounter using WCF bindings in Visual Studio 2008; I came up with this one and took awhile to figure out what it was exactly - to save you some time. This error occurs when your are trying to debug a WCF Service project - when you attach to the process, a pop up box appears with the Binding name and the nice message "error" shown next to it. Clicking on this will display a better message in a window below - this starts out with:

The binding at system.serviceModel/bindings/basicHttpBinding does not have a configured binding named ''.

This occurs when the 'bindingConfiguration=""' tag is set on your binding in the App.config file of the WCF Service. If you look at the detail of the error, it will indicate the line number, etc. in the file .dll.config - this is a copy of the App.Config file so you map one to one. If not using it simply remove it and the error will go away.

Saturday, February 20, 2010

How to fix AG_E_UNKNOWN_ERROR in Silverlight Control

This one stumped me when I first started out on Silverlight and in searching for answers, had much difficulty in finding an actual answer; I'd forgotten to post this at the time but...

The problem with this error is that it is simply telling you there is something wrong with the XAML code - personally, they could have made it easier but that is another story. It is usually that the target control cannot be located from the XAML.

First, double check the way you are defining the xmlns for the control - by default this is:


This should also include the assembly name as:


The other is to check your Control Template TargetType - be sure that the CLASS name is specified:

If nether of the above help, the problem is in the XAML sytax - comment out as much as possible then introduce new elements one at a time until you determine the cause.

Monday, February 15, 2010

Silverlight WrapPanel and DockPanel

As we all know, Silverlight incorporated into SharePoint is an excellent way to update the UI and provide very lightweight controls.

However, like most folks (so I've found), the WrapPanel and DockPanel namespaces can be difficult to find for a beginner. WrapPanels are so necessary for SharePoint's pages and web parts and DockPanel is cool for app development.

I stumbled on this (as everyone else) then did the usual searching...I did find some posts but the examples were incomplete and some, including one from Microsoft that are incorrect (on CodePlex!).

To access this control, you have to do the following:

First, make sure that a) You have Silverlight 3 (or 4) installed and b) that you have downloaded and installed the Silverlight Toolkit from CodePlex.

Next, in your Silverlight project, add a Reference to System.Windows.Controls.Toolkit (I usually include System.Windows.Controls too).

Now in your control, you add the Namespace for the Toolkit with the other name spaces as so:

<usercontrol x:class="SomeControl.MainPage">



Now you can add your control:

<controls:wrappanel x:name="AWrapPanel" horizontalalignment="Left" scrollviewer.horizontalscrollbarvisibility="Auto" scrollviewer.verticalscrollbarvisibility="Auto" verticalalignment="Top" width="200" />

Have fun!

Wednesday, February 10, 2010

Service Application Failure in SharePoint 2010

I've seen a number of posts on this - just to save some folks time, I'm reposting:

During the SharePoint 2010 installation, you may encounter an error when first setting up the central administration similar to this:

The service application proxy "User Profile Service Application" could not be provisioned because of the following error....

To fix, download the Hotfix from Microsoft:

Note: this is also known as KB976462

Unfortunately, the settings will be off in your installation so to be on the safe side, you have to completely uninstall SharePoint from the web server. When complete, you must also go to SQL Server and delete all of the databases that were created (alas, 2010 does not remove them automatically with an uninstall).

Office Server 2010 Configuration Error "errorData"

When connecting to the Database during the installation of SharePoint, you might come across this:

"An error has occurred while validating the configuration settings. An exception of type System.ArgumentNullException was thrown. Additional exception information: The errorData argument cannot be null or zero length.

Parameter name: errorData"

Like all of you, I googled and binged my way to figure out what was wrong - however, none of them saved me.

DON'T worry! This error only means that SharePoint cannto connect to the database.

If you look into the event log, you'll see the error:

"Unkown SQL Exception 53 occurred. Addtional error information from SQL Server is included below.

A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error 40 - Could not open a connecto SQL Server)"

Here's the checklist for fixing the problem - after each of these, try to connect:

1) Verify you can connect to the database using DataSources (Start > Administrative Tools > Data Sources (ODBC)) - setup a new System DSN and supply server name, etc. however when you go to connect, be sure that "Connect to SQL Server to obtain..." is NOT checked. Also, click on Client Configuration to check that TCP/IP is selected and the correct port is set (or set to Auto).

SIDE NOTE: Using the Datasource setup is the way to set a different port than the standard 1433.

2) On the SQL Server, verify using the SQL Server Configuration Manager - for each Named Pipes is enabled as a protocol for the SQL Native Client 10.0 Configuration and under the SQL Server Network Configuration.

3) On the SQL Server, verify that the SQL Agent and SQL Browser services are running and set to Automatic (Start > Administrative Tools > Services). If they are not started, start them.

4) On the SQL Server, check the services themselves and ensure that the account used for running the SQL Server is correct and in the Local Administrators group on all servers. In my case, the SQL Browser service was running as Local System - I changed that to the correct account and rebooted.

5) Last - and this was my environment - using VM's with DHCP addresses, I added the SQL Server to the HOSTS file (c:\windows\system32\drivers\etc\hosts).

Opening Firewall Ports for SQL Server 2008

Installing SQL Server 2008 requires opening a number of ports for applications like SharePoint to use it. Having searched a bit myself, here's the Microsoft instuctions:

While dated, the script still works - paste the commands into a command file (.bat or .cmd) and run from the command line.

Tuesday, February 9, 2010

Unable to install SharePoint 2010 due to SQL 2008 Version

You might encounter an error when you attempt to install SharePoint Foundation or Server 2010 using SQL Server 2008. In the message displayed, you'll see a link to Microsoft - this is the Hotfix page where you can register for the hotfix and Microsoft will email it to you.

Be aware however that you will get two hotfix files - password protected Zip files that extract an executable - to save you sometime, only the patch file 398850_intl_x64_zip.exe is necessary. In over ten installs, the other patch, 381569_intl_x64_zip.exe will not run; it fails when starting setup.