Follow on thread Is this project is followed by the team

Topics: Usage Scenarios, Technical Questions
Feb 12, 2008 at 8:26 AM
Hi Botto, as I said all operations have "Published" checkbox checked, here is the log after restarting MSE

mseTraceSrc Start: 1 : MseRuntimeManager.ConfigureEndpoints for200332b
mseTraceSrc Warning: 0 : No Endpoints assigned to MSE Runtime[
200332b] in Catalog net.pipe://localhost/ServiceCatalog/Pipe - No Endpoints will be configured
mseTraceSrc Stop: 2 : MseRuntimeManager.ConfigureEndpoints for200332b
mseTraceSrc Error: 0 : Notification Uri for MSE Runtime200332b is undefined.This MSE Runtime won't be able to receive catalog notifications
Developer
Feb 12, 2008 at 4:39 PM
Thanks for posting your log file. The error you are reporting can be caused by the name of the runtime server not matching the name listed in the service catalog. When the runtime is starting it asks the catalog what endpoints it should host. As another thread indicates the default behavior of the MSE requires a Runtime Server to be registered based on the host machine name where the Runtime is executing.

Please double check that the name appearing under Runtime Servers in the management console is exactly "200332b" (without the quotes). Please verify there are no leading or trailing spaces.



eliassal wrote:
Hi Botto, as I said all operations have "Published" checkbox checked, here is the log after restarting MSE

mseTraceSrc Start: 1 : MseRuntimeManager.ConfigureEndpoints for200332b
mseTraceSrc Warning: 0 : No Endpoints assigned to MSE Runtime[
200332b] in Catalog net.pipe://localhost/ServiceCatalog/Pipe - No Endpoints will be configured
mseTraceSrc Stop: 2 : MseRuntimeManager.ConfigureEndpoints for200332b
mseTraceSrc Error: 0 : Notification Uri for MSE Runtime200332b is undefined.This MSE Runtime won't be able to receive catalog notifications


Feb 12, 2008 at 5:37 PM
Do you mean that I should have
net.pipe://200332b/ServiceCatalog/Pipe instead of net.pipe://localhost/ServiceCatalog/Pipe so that matches the runtime server name.
If yes, I have already changed the runtime server to localhost instead of 200332b and got the same error.

I will give it another go by changing as you reuqtested and let you know
Feb 12, 2008 at 8:22 PM
Here is the Runtime server configuration (I did following your response:
Name : 200332b
Catalog URI : net.pipe://200332b/ServiceCatalog/Pipe
Catalog Binding : Netnamedpipe
Notification URI : http://200332b:8060/scEvents
Notification Binding : BasicHttp(Soap11)
Messenger and broker check boxes checked
Hosted EPs : 200332b:8085/myService


The endpoint Config :
Name : 200332b:8085/myService
Binding : BasicHttp(Soap12)
Service Name : 200332b8085myService
Operation exposed : AddDoubles:1.0.0.0 and AddIntegers:1.0.0.0

Both operations are active and published.

I restarted the MSE and catalog service, here is the log :

mseTraceSrc Start: 1 : MseRuntimeManager.ConfigureEndpoints for200332b
mseTraceSrc Start: 1 : MseEndpointHostFactory.CreateServiceHost
mseTraceSrc Start: 1 : MseEndpointHost.ctor
mseTraceSrc Stop: 2 : MseEndpointHost.ctor
mseTraceSrc Start: 1 : MseEndpointHost.Start
mseTraceSrc Start: 1 : MseEndpointHost.CreateDescription
mseTraceSrc Warning: 0 : MseEndpointResolver: Error(s) whilst importing Contract for http://200332b:8085/myService:
mseTraceSrc Error: 0 : MseEndpointResolver: Cannot import wsdl:portType
Detail: Name cannot begin with the '2' character, hexadecimal value 0x32.
Parameter name: name
XPath to Error Source: //wsdl:definitions@targetNamespace='http://services.microsoft.com/2006-07/ServicePlatform/MSE6/BasicHttp (Soap12)/200332b_8085_myService'/wsdl:portType@name='200332b_8085_myServiceSoap' for endpoint http://200332b:8085/myService
mseTraceSrc Warning: 0 : MseEndpointResolver: Unexpected exception Error Cannot import wsdl:portType
Detail: Name cannot begin with the '2' character, hexadecimal value 0x32.
Parameter name: name
XPath to Error Source: //wsdl:definitions@targetNamespace='http://services.microsoft.com/2006-07/ServicePlatform/MSE6/BasicHttp (Soap12)/200332b_8085_myService'/wsdl:portType@name='200332b_8085_myServiceSoap' resolving endpoint http://200332b:8085/myService

mseTraceSrc Error: 0 : Error creating description: Unable to Resolve Endpoint
mseTraceSrc Stop: 2 : MseEndpointHost.CreateDescription
mseTraceSrc Stop: 2 : MseEndpointHost.Start
mseTraceSrc Error: 0 : Error Creating MSE Endpoint: http://200332b:8085/myService Error in CreateDescription for MSE endpoint: http://200332b:8085/myService
mseTraceSrc Stop: 2 : MseEndpointHostFactory.CreateServiceHost
mseTraceSrc Error: 0 : Failed to create listener for http://200332b:8085/myService with reason Error Creating MSE Endpoint: http://200332b:8085/myService
mseTraceSrc Stop: 2 : MseRuntimeManager.ConfigureEndpoints for200332b
mseTraceSrc Information: 0 : 200332b: Registered for Event EndpointsUpdated
mseTraceSrc Information: 0 : 200332b: Registered for Event EndpointPolicyUpdated
mseTraceSrc Information: 0 : 200332b: Registered for Event ServiceDefinitionUpdated
mseTraceSrc Information: 0 : 200332b: Registered for Event ServicePolicyUpdated
mseTraceSrc Information: 0 : 200332b: Registered for Event OperationsUpdated

Developer
Feb 12, 2008 at 11:55 PM
Ok, this is progress. The Runtime is properly accessing the catalog and identifying what endpoints it needs to construct, but there is an issue constructing the endpoint when the machine name starts with a numeric value... which I think you were trying to point out in your original post... :)

Let me dig into this and see what I find. In the mean time, if you have a system with a machine name that doesn't start with a number, you ought to have success finishing the walkthrough.

Thanks for reporting your experience and working with us.


eliassal wrote:
Here is the Runtime server configuration (I did following your response:
Name : 200332b
Catalog URI : net.pipe://200332b/ServiceCatalog/Pipe
Catalog Binding : Netnamedpipe
Notification URI : http://200332b:8060/scEvents
Notification Binding : BasicHttp(Soap11)
Messenger and broker check boxes checked
Hosted EPs : 200332b:8085/myService


The endpoint Config :
Name : 200332b:8085/myService
Binding : BasicHttp(Soap12)
Service Name : 200332b8085myService
Operation exposed : AddDoubles:1.0.0.0 and AddIntegers:1.0.0.0

Both operations are active and published.

I restarted the MSE and catalog service, here is the log :

mseTraceSrc Start: 1 : MseRuntimeManager.ConfigureEndpoints for200332b
mseTraceSrc Start: 1 : MseEndpointHostFactory.CreateServiceHost
mseTraceSrc Start: 1 : MseEndpointHost.ctor
mseTraceSrc Stop: 2 : MseEndpointHost.ctor
mseTraceSrc Start: 1 : MseEndpointHost.Start
mseTraceSrc Start: 1 : MseEndpointHost.CreateDescription
mseTraceSrc Warning: 0 : MseEndpointResolver: Error(s) whilst importing Contract for http://200332b:8085/myService:
mseTraceSrc Error: 0 : MseEndpointResolver: Cannot import wsdl:portType
Detail: Name cannot begin with the '2' character, hexadecimal value 0x32.
Parameter name: name
XPath to Error Source: //wsdl:definitions@targetNamespace='http://services.microsoft.com/2006-07/ServicePlatform/MSE6/BasicHttp (Soap12)/200332b_8085_myService'/wsdl:portType@name='200332b_8085_myServiceSoap' for endpoint http://200332b:8085/myService
mseTraceSrc Warning: 0 : MseEndpointResolver: Unexpected exception Error Cannot import wsdl:portType
Detail: Name cannot begin with the '2' character, hexadecimal value 0x32.
Parameter name: name
XPath to Error Source: //wsdl:definitions@targetNamespace='http://services.microsoft.com/2006-07/ServicePlatform/MSE6/BasicHttp (Soap12)/200332b_8085_myService'/wsdl:portType@name='200332b_8085_myServiceSoap' resolving endpoint http://200332b:8085/myService

mseTraceSrc Error: 0 : Error creating description: Unable to Resolve Endpoint
mseTraceSrc Stop: 2 : MseEndpointHost.CreateDescription
mseTraceSrc Stop: 2 : MseEndpointHost.Start
mseTraceSrc Error: 0 : Error Creating MSE Endpoint: http://200332b:8085/myService Error in CreateDescription for MSE endpoint: http://200332b:8085/myService
mseTraceSrc Stop: 2 : MseEndpointHostFactory.CreateServiceHost
mseTraceSrc Error: 0 : Failed to create listener for http://200332b:8085/myService with reason Error Creating MSE Endpoint: http://200332b:8085/myService
mseTraceSrc Stop: 2 : MseRuntimeManager.ConfigureEndpoints for200332b
mseTraceSrc Information: 0 : 200332b: Registered for Event EndpointsUpdated
mseTraceSrc Information: 0 : 200332b: Registered for Event EndpointPolicyUpdated
mseTraceSrc Information: 0 : 200332b: Registered for Event ServiceDefinitionUpdated
mseTraceSrc Information: 0 : 200332b: Registered for Event ServicePolicyUpdated
mseTraceSrc Information: 0 : 200332b: Registered for Event OperationsUpdated



Developer
Feb 13, 2008 at 2:05 AM
In looking at the configuration of the myService endpoint you provided, I see the name you have provided for the Service Name is "200332b8085myService". Change that to "myService" and you should be all set.

The W3 standard for WSDL requires values for name attributes to start with a letter. If you dig into the Catalog you'll see we use the value provided in the service name field as part of the name for the WSDL PortType.



botto wrote:
Ok, this is progress. The Runtime is properly accessing the catalog and identifying what endpoints it needs to construct, but there is an issue constructing the endpoint when the machine name starts with a numeric value... which I think you were trying to point out in your original post... :)

Let me dig into this and see what I find. In the mean time, if you have a system with a machine name that doesn't start with a number, you ought to have success finishing the walkthrough.

Thanks for reporting your experience and working with us.


eliassal wrote:
Here is the Runtime server configuration (I did following your response:
Name : 200332b
Catalog URI : net.pipe://200332b/ServiceCatalog/Pipe
Catalog Binding : Netnamedpipe
Notification URI : http://200332b:8060/scEvents
Notification Binding : BasicHttp(Soap11)
Messenger and broker check boxes checked
Hosted EPs : 200332b:8085/myService


The endpoint Config :
Name : 200332b:8085/myService
Binding : BasicHttp(Soap12)
Service Name : 200332b8085myService
Operation exposed : AddDoubles:1.0.0.0 and AddIntegers:1.0.0.0

Both operations are active and published.

I restarted the MSE and catalog service, here is the log :

mseTraceSrc Start: 1 : MseRuntimeManager.ConfigureEndpoints for200332b
mseTraceSrc Start: 1 : MseEndpointHostFactory.CreateServiceHost
mseTraceSrc Start: 1 : MseEndpointHost.ctor
mseTraceSrc Stop: 2 : MseEndpointHost.ctor
mseTraceSrc Start: 1 : MseEndpointHost.Start
mseTraceSrc Start: 1 : MseEndpointHost.CreateDescription
mseTraceSrc Warning: 0 : MseEndpointResolver: Error(s) whilst importing Contract for http://200332b:8085/myService:
mseTraceSrc Error: 0 : MseEndpointResolver: Cannot import wsdl:portType
Detail: Name cannot begin with the '2' character, hexadecimal value 0x32.
Parameter name: name
XPath to Error Source: //wsdl:definitions@targetNamespace='http://services.microsoft.com/2006-07/ServicePlatform/MSE6/BasicHttp (Soap12)/200332b_8085_myService'/wsdl:portType@name='200332b_8085_myServiceSoap' for endpoint http://200332b:8085/myService
mseTraceSrc Warning: 0 : MseEndpointResolver: Unexpected exception Error Cannot import wsdl:portType
Detail: Name cannot begin with the '2' character, hexadecimal value 0x32.
Parameter name: name
XPath to Error Source: //wsdl:definitions@targetNamespace='http://services.microsoft.com/2006-07/ServicePlatform/MSE6/BasicHttp (Soap12)/200332b_8085_myService'/wsdl:portType@name='200332b_8085_myServiceSoap' resolving endpoint http://200332b:8085/myService

mseTraceSrc Error: 0 : Error creating description: Unable to Resolve Endpoint
mseTraceSrc Stop: 2 : MseEndpointHost.CreateDescription
mseTraceSrc Stop: 2 : MseEndpointHost.Start
mseTraceSrc Error: 0 : Error Creating MSE Endpoint: http://200332b:8085/myService Error in CreateDescription for MSE endpoint: http://200332b:8085/myService
mseTraceSrc Stop: 2 : MseEndpointHostFactory.CreateServiceHost
mseTraceSrc Error: 0 : Failed to create listener for http://200332b:8085/myService with reason Error Creating MSE Endpoint: http://200332b:8085/myService
mseTraceSrc Stop: 2 : MseRuntimeManager.ConfigureEndpoints for200332b
mseTraceSrc Information: 0 : 200332b: Registered for Event EndpointsUpdated
mseTraceSrc Information: 0 : 200332b: Registered for Event EndpointPolicyUpdated
mseTraceSrc Information: 0 : 200332b: Registered for Event ServiceDefinitionUpdated
mseTraceSrc Information: 0 : 200332b: Registered for Event ServicePolicyUpdated
mseTraceSrc Information: 0 : 200332b: Registered for Event OperationsUpdated




Developer
Feb 13, 2008 at 2:10 AM
And to be clear, I see that the value of the Service Name in your case is the default value supplied by the MSE.

We'll track this as a known issue so in a future release we can provide a default that avoids this problem.



botto wrote:
In looking at the configuration of the myService endpoint you provided, I see the name you have provided for the Service Name is "200332b8085myService". Change that to "myService" and you should be all set.

The W3 standard for WSDL requires values for name attributes to start with a letter. If you dig into the Catalog you'll see we use the value provided in the service name field as part of the name for the WSDL PortType.



botto wrote:
Ok, this is progress. The Runtime is properly accessing the catalog and identifying what endpoints it needs to construct, but there is an issue constructing the endpoint when the machine name starts with a numeric value... which I think you were trying to point out in your original post... :)

Let me dig into this and see what I find. In the mean time, if you have a system with a machine name that doesn't start with a number, you ought to have success finishing the walkthrough.

Thanks for reporting your experience and working with us.


eliassal wrote:
Here is the Runtime server configuration (I did following your response:
Name : 200332b
Catalog URI : net.pipe://200332b/ServiceCatalog/Pipe
Catalog Binding : Netnamedpipe
Notification URI : http://200332b:8060/scEvents
Notification Binding : BasicHttp(Soap11)
Messenger and broker check boxes checked
Hosted EPs : 200332b:8085/myService


The endpoint Config :
Name : 200332b:8085/myService
Binding : BasicHttp(Soap12)
Service Name : 200332b8085myService
Operation exposed : AddDoubles:1.0.0.0 and AddIntegers:1.0.0.0

Both operations are active and published.

I restarted the MSE and catalog service, here is the log :

mseTraceSrc Start: 1 : MseRuntimeManager.ConfigureEndpoints for200332b
mseTraceSrc Start: 1 : MseEndpointHostFactory.CreateServiceHost
mseTraceSrc Start: 1 : MseEndpointHost.ctor
mseTraceSrc Stop: 2 : MseEndpointHost.ctor
mseTraceSrc Start: 1 : MseEndpointHost.Start
mseTraceSrc Start: 1 : MseEndpointHost.CreateDescription
mseTraceSrc Warning: 0 : MseEndpointResolver: Error(s) whilst importing Contract for http://200332b:8085/myService:
mseTraceSrc Error: 0 : MseEndpointResolver: Cannot import wsdl:portType
Detail: Name cannot begin with the '2' character, hexadecimal value 0x32.
Parameter name: name
XPath to Error Source: //wsdl:definitions@targetNamespace='http://services.microsoft.com/2006-07/ServicePlatform/MSE6/BasicHttp (Soap12)/200332b_8085_myService'/wsdl:portType@name='200332b_8085_myServiceSoap' for endpoint http://200332b:8085/myService
mseTraceSrc Warning: 0 : MseEndpointResolver: Unexpected exception Error Cannot import wsdl:portType
Detail: Name cannot begin with the '2' character, hexadecimal value 0x32.
Parameter name: name
XPath to Error Source: //wsdl:definitions@targetNamespace='http://services.microsoft.com/2006-07/ServicePlatform/MSE6/BasicHttp (Soap12)/200332b_8085_myService'/wsdl:portType@name='200332b_8085_myServiceSoap' resolving endpoint http://200332b:8085/myService

mseTraceSrc Error: 0 : Error creating description: Unable to Resolve Endpoint
mseTraceSrc Stop: 2 : MseEndpointHost.CreateDescription
mseTraceSrc Stop: 2 : MseEndpointHost.Start
mseTraceSrc Error: 0 : Error Creating MSE Endpoint: http://200332b:8085/myService Error in CreateDescription for MSE endpoint: http://200332b:8085/myService
mseTraceSrc Stop: 2 : MseEndpointHostFactory.CreateServiceHost
mseTraceSrc Error: 0 : Failed to create listener for http://200332b:8085/myService with reason Error Creating MSE Endpoint: http://200332b:8085/myService
mseTraceSrc Stop: 2 : MseRuntimeManager.ConfigureEndpoints for200332b
mseTraceSrc Information: 0 : 200332b: Registered for Event EndpointsUpdated
mseTraceSrc Information: 0 : 200332b: Registered for Event EndpointPolicyUpdated
mseTraceSrc Information: 0 : 200332b: Registered for Event ServiceDefinitionUpdated
mseTraceSrc Information: 0 : 200332b: Registered for Event ServicePolicyUpdated
mseTraceSrc Information: 0 : 200332b: Registered for Event OperationsUpdated





Feb 13, 2008 at 8:32 AM
Yeeeeeeeeeeeeeeeees, changed the Service name to myService instead of 200332b_8085myService and I was able to browse the service. Thanks for your help.
2 questions, you indicated "dig in the catalog", how can I do this. It seems to me that it is balck box, unless you mean downloading the source files, correct me if I am mistaken.
2nd, you said "try another machine". Is it possible to setup MSE in a distributed environment? what I mean can I do a setup for components on other machines without the need to setup a new sqlexperess, either using the existing MSE DB on the first machine or any other SQL server.

Thanks again
Developer
Feb 13, 2008 at 7:50 PM
Correct, I am referring to the Catalog source code that is available as a download.

At this time we do not have specific guidance on setting up the various topologies supported by the MSE. You can definitely have multiple runtime servers all pointing to one or more Service Catalogs, and the service catalog(s) can also reside on a different machine from the MSE database.

We are working on providing this guidance so more of you can try out these scenarios and help provide additional feedback. In the meantime we hope you enjoy exploring and understanding the MSE capabilities.


eliassal wrote:
Yeeeeeeeeeeeeeeeees, changed the Service name to myService instead of 200332b_8085myService and I was able to browse the service. Thanks for your help.
2 questions, you indicated "dig in the catalog", how can I do this. It seems to me that it is balck box, unless you mean downloading the source files, correct me if I am mistaken.
2nd, you said "try another machine". Is it possible to setup MSE in a distributed environment? what I mean can I do a setup for components on other machines without the need to setup a new sqlexperess, either using the existing MSE DB on the first machine or any other SQL server.

Thanks again