Error Creating MSE EndPoint

Feb 5, 2009 at 3:43 PM
Edited Feb 5, 2009 at 3:48 PM
Hello -

I am setting up MSE for a client, and learning MSE as I go. I have two Runtime Servers, one internal and one in an external DMZ, with the Catalog Service running on the internal app server.

I have applied a custom wsHttpBinding to one of the external endpoints using Message Security with UserName Credentials, and a customer policy using the SqlMembership and Role Provider. I followed the instructions as in the Security Guide posted here on CodePlex.

When starting the service I am getting the following error:

mseTraceSrc Start: 1 : RuntimeManager:ConfigureEndpoints for externalServer
mseTraceSrc Start: 1 : VirtualServiceHostFactory.CreateServiceHost
mseTraceSrc Error: 0 : Error Creating MSE Endpoint: http://externalServer/Externals The tag 'EndpointSecurityElement' does not exist in XML namespace 'clr-namespace:Microsoft.MSE.Behaviors.Security.Configuration;assembly=Microsoft.MSE.Behaviors.Security'. Line '1' Position '592'.
mseTraceSrc Stop: 2 : VirtualServiceHostFactory.CreateServiceHost
mseTraceSrc Error: 0 : Failed to create listener for [http://externalServer/Externals] with reason [Error Creating MSE Endpoint: http://externalServer/Externals]

Any information on this error would be appreciated.

Also, Does the Runtime Service need to be restarted everytime a change to an endpoint or policy pertaining to an endpoint is modified?




Feb 5, 2009 at 8:19 PM
Be sure you've downloaded the souce code for the security guide, compiled, and dropped the assemblies in the installation folder of the runtime server that will be using this behavior.

Also of note, after copying the assembly to the proper location, you'll keep getting this error until you restart the runtime server service... this is the normal behavior for .net (

There is no need to restart the runtime service when making changes in the management tool.  The system has logic to know what endpoints and runtimes are impacted by a change in the repository and will automatically tear down and re-create the appropriate endpoints.  Note, however, that with the current CodePlex release there are a few issues that would cause the notifications not to propogate through the system.  The following post has a little more information:

Our next release has significant changes to the eventing/notification logic to ensure it is more reliable.