endpoint.tv Screencast - Configuring Services with Endpoints | endpoint.tv

buffcessna

Aaron,

I did this screencast and am getting a weird error when I try to run this.

System.InvalidOperationException: Cannot load the X.509 certificate identity specified in the configuration.
   at System.ServiceModel.Description.ConfigLoader.LoadIdentity(IdentityElement element)
   at System.ServiceModel.Description.ConfigLoader.LoadServiceDescription(ServiceHostBase host, ServiceDescription description, ServiceElement serviceElement, Action`1 addBaseAddress)
   at System.ServiceModel.ServiceHostBase.LoadConfigurationSectionInternal(ConfigLoader configLoader, ServiceDescription description, ServiceElement serviceSection)
   at System.ServiceModel.ServiceHostBase.LoadConfigurationSectionInternal(ConfigLoader configLoader, ServiceDescription description, String configurationName)
   at System.ServiceModel.ServiceHostBase.ApplyConfiguration()
   at System.ServiceModel.ServiceHostBase.InitializeDescription(UriSchemeKeyedCollection baseAddresses)
   at System.ServiceModel.ServiceHost.InitializeDescription(Type serviceType, UriSchemeKeyedCollection baseAddresses)
   at System.ServiceModel.ServiceHost..ctor(Type serviceType, Uri[] baseAddresses)
   at Microsoft.Tools.SvcHost.ServiceHostHelper.CreateServiceHost(Type type, ServiceKind kind)
   at Microsoft.Tools.SvcHost.ServiceHostHelper.OpenService(ServiceInfo info)

Don't know what the deal is. Any help to this noob would be greatly appreciated.

Shane

cliff.simpkins

I think I've actually seen this before (I'm more a WF person than WCF) - check your binding; it sounds like you're using WsHttp, which will try to layer on WS-Security. Try changing that to a non-WS setting, or check the other binding options to see if it's specifying the use of a x509 cert in it somewhere.

ArnoudBM

In reply to buffcessna

#Oct 1st, 2008 @ 12:09 PM

Same here. I fixed it by removing the <certificateReference> elements. (The original example from the first screencast didn't have it)

But in this screencast, Aaron has in fact these settings in the app.config, so still not sure how his example works.

.NetRebel

I have found something similar. Seems each time I create a named pipes endpoint, I get the above <certificateRefernce> elements auto included in the app.config. Deleting seems to address the issue.

sreekanthv

In reply to .NetRebel

#Nov 9th, 2008 @ 11:10 AM

Here is a quick tutorial on how to get your certificate store working for WCF:

http://www.codeplex.com/WCFSecurity/Wiki/View.aspx?title=How%20To%20-%20Create%20and%20Install%20Temporary%20Certificates%20in%20WCF%20for%20Message%20Security%20During%20Development

It worked for me.

GW

It's the endpoint wizard. If you create the endpoints manually, the certificate references are not created.

scenicohio

I am new to WCF... I am getting the same error in my service... Tried deleting the endpoints configured thru the wizard, didnot work.

Any Ideas how to make it work?

haridasabhavana

In reply to scenicohio

#Feb 8th @ 8:19 PM

I got the same problem.
The Visual Studi inserts an identity element autmatically after each binding
Just comment this identity node and it will start working again.

Csabi

Hi!

When i try to create named pipe endpoint, i'm getting the following error: "Invalid URI: The hostname could not be parsed.". When i'm writing net.tcp instead of net.pipe, there is no error.

Any ideas?
Thx!