Is this project is followed by the team

Jan 18, 2008 at 7:54 AM
Hi, I amwondering if this project is active and somebody can help us run or respond to our queries
Developer
Jan 18, 2008 at 2:28 PM
Hi,
Were you able to pass beyond the port issue that you mentioned in your post. Please let me know how can I help.

Jan 18, 2008 at 6:10 PM
No Sir, I still can not pass beoynd it. I requested also on how to activate logging or trace to try to find a hint
Developer
Jan 21, 2008 at 3:31 PM
Please look in the configuration file Microsoft.MSE.Runtime.exe.config for the location of the log files.

<sharedListeners>
<add initializeData="c:\temp\logs\mse_runtime.svclog"
type="System.Diagnostics.XmlWriterTraceListener" name="xml" />
<add initializeData="c:\temp\logs\mse_runtime.txt"
type="System.Diagnostics.TextWriterTraceListener" name="txt"/>
</sharedListeners>

Normally it is c:\temp\logs. If that folder exists then you need to look for the two log files i.e. mseruntime.svclog, mseruntime.txt. Otherwise create this folder and then restart MSE Runtime and the log files will show up. You can control what is logged from the <system.diagnostics> section of Microsoft.MSE.Runtime.exe.config file.
Jan 22, 2008 at 11:24 AM
Directory exist, restarted the MSE but still no files are showing
Jan 22, 2008 at 11:25 AM
Also, I clicked on the link you provided, I get the following message dispalyed
"The wiki page 'Microsoft.MSE.Runtime.exe.config' does not exist"
Developer
Jan 24, 2008 at 4:55 PM
Can you complete the following steps and let me know the results:
1. Stop "MSE Runtime" service
2. Open a command prompt and start the use the following command line "Microsoft.MSE.Runtime.exe /c".

This will run the MSE Runtime service in command line mode and you will be able to see if anything is going wrong there. Can you then post what you see in the command prompt?
Jan 28, 2008 at 8:49 PM
Hi, I didn't reeive an alert when you responded, its by aident I visited the project site and read your post. Anyway, all o a sudden, I rebooted my mahine, started to see logs (2 files) in temp/logs. I saw an error indicating that "Name" can not start with the "2". My mahine name is 200332b. So I started everything rom scrath to see where in the appliation doesn't accept machine names that starts with numbers. I discovered that if the url in the endpoint starts with a number (which is my case), in the import new service wizard, it refuses to proceed and doesn't suceed the process. I hanged from 200332b to loalhost:8090/myService and the import operation went through and all config are in place.
However, still, when clicking on the "Browse" button i get page can not be displayed. I opened the log file and saw the following messages (This is the log since I started mse run time servie until I tried to browse the endpoint - I will do it in 2 posts becasue only 10000 aracters allowed in the post)

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 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
mseTraceSrc Start: 1 : MseEndpointHostFactory:RefreshBrokersCache
mseTraceSrc Start: 1 : MseEndpointHostFactory:RefreshBrokersCache
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 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
mseTraceSrc Start: 1 : MseEndpointHostFactory:RefreshBrokersCache
mseTraceSrc Start: 1 : MseEndpointHostFactory:RefreshBrokersCache
mseTraceSrc Start: 1 : MseRuntimeManager.ConfigureEndpoints for200332b
mseTraceSrc Start: 1 : MseEndpointHostFactory.CreateServiceHost
mseTraceSrc Warning: 0 : Instrumentation not properly configured.

System.InvalidOperationException: The requested Performance Counter is not a custom counter, it has to be initialized as ReadOnly.
at System.Diagnostics.PerformanceCounter.Initialize()
at System.Diagnostics.PerformanceCounter.set_RawValue(Int64 value)
at Microsoft.MSE.Runtime.Instrumentation.InstrumentationHelper.CreateMseRuntimeInstanceCounters(String instanceMode, String mseRuntimeName)
mseTraceSrc Start: 1 : MseEndpointHost.ctor
mseTraceSrc Stop: 2 : MseEndpointHost.ctor
mseTraceSrc Start: 1 : MseEndpointHost.Start
mseTraceSrc Start: 1 : MseEndpointHost.CreateDescription
mseTraceSrc Stop: 2 : MseEndpointHost.CreateDescription
mseTraceSrc Start: 1 : MseEndpointHost.ApplyConfiguration
mseTraceSrc Stop: 2 : MseEndpointHost.ApplyConfiguration
mseTraceSrc Stop: 2 : MseEndpointHost.Start
mseTraceSrc Stop: 2 : MseEndpointHostFactory.CreateServiceHost
mseTraceSrc Start: 1 : MseEndpointHost.InitializeRuntime
mseTraceSrc Error: 0 : Error in InitializeRuntime: Service '' has zero application (non-infrastructure) endpoints. This might be because no configuration file was found for your application, or because no service element matching the service name could be found in the configuration file, or because no endpoints were defined in the service element.
mseTraceSrc Stop: 2 : MseEndpointHost.InitializeRuntime
mseTraceSrc Information: 0 : Listening on http://200332b:8090/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
mseTraceSrc Start: 1 : MseEndpointHostFactory:RefreshBrokersCache
mseTraceSrc Start: 1 : MseEndpointHostFactory:RefreshBrokersCache
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 Stop: 2 : MseEndpointHost.CreateDescription
mseTraceSrc Start: 1 : MseEndpointHost.ApplyConfiguration
mseTraceSrc Stop: 2 : MseEndpointHost.ApplyConfiguration
mseTraceSrc Stop: 2 : MseEndpointHost.Start
mseTraceSrc Stop: 2 : MseEndpointHostFactory.CreateServiceHost
mseTraceSrc Start: 1 : MseEndpointHost.InitializeRuntime
mseTraceSrc Error: 0 : Error in InitializeRuntime: Service '' has zero application (non-infrastructure) endpoints. This might be because no configuration file was found for your application, or because no service element matching the service name could be found in the configuration file, or because no endpoints were defined in the service element.
mseTraceSrc Stop: 2 : MseEndpointHost.InitializeRuntime
mseTraceSrc Information: 0 : Listening on http://localhost:8090/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
mseTraceSrc Start: 1 : MseEndpointHostFactory:RefreshBrokersCache
mseTraceSrc Start: 1 : MseEndpointHostFactory:RefreshBrokersCache
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://localhost:8090/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_8090_myService'/wsdl:portType@name='200332b_8090_myServiceSoap' for endpoint http://localhost:8090/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_8090_myService'/wsdl:portType@name='200332b_8090_myServiceSoap' resolving endpoint http://localhost:8090/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://localhost:8090/myService Error in CreateDescription for MSE endpoint: http://localhost:8090/myService
mseTraceSrc Stop: 2 : MseEndpointHostFactory.CreateServiceHost
mseTraceSrc Error: 0 : Failed to create listener for http://localhost:8090/myService with reason Error Creating MSE Endpoint: http://localhost:8090/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
mseTraceSrc Start: 1 : MseEndpointHostFactory:RefreshBrokersCache
mseTraceSrc Start: 1 : MseEndpointHostFactory:RefreshBrokersCache
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://localhost:8090/myService:
mseTraceSrc Error: 0 : MseEndpointResolver: Cannot import wsdl:portType
Detail: Name cannot begin with the '2' character, hexadecimal value 0x32.
Parameter name: name


Jan 28, 2008 at 8:50 PM
XPath to Error Source: //wsdl:definitions@targetNamespace='http://services.microsoft.com/2006-07/ServicePlatform/MSE6/BasicHttp (Soap12)/200332b_8090_myService'/wsdl:portType@name='200332b_8090_myServiceSoap' for endpoint http://localhost:8090/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_8090_myService'/wsdl:portType@name='200332b_8090_myServiceSoap' resolving endpoint http://localhost:8090/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://localhost:8090/myService Error in CreateDescription for MSE endpoint: http://localhost:8090/myService
mseTraceSrc Stop: 2 : MseEndpointHostFactory.CreateServiceHost
mseTraceSrc Error: 0 : Failed to create listener for http://localhost:8090/myService with reason Error Creating MSE Endpoint: http://localhost:8090/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
Jan 29, 2008 at 12:56 AM
Please do the following:
1. Stop the Runtime Service by going Adminstrative Tools->Services
2. Open a command prompt and run the following command: "InstallUtil.exe /i Microsoft.MSE.Runtime"
3. Restart the MSE Runtime service by going Adminstrative Tools->Services

Let me know how things go after that.
Jan 29, 2008 at 5:28 PM
Hi, I tried "InstallUtil.exe /i Microsoft.MSE.Runtime", got error indicating that install can not find Microsoft.MSE.Runtime.dll
Changed the command to
C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\InstallUtil.exe /i "C:\Program Files\Microsoft Managed Services Engine\Microsoft.MSE.Runtime.exe"

The install process exited wuth the rror "The specified service already exists
--------------------Log on the screen---------------------------------------------------
Microsoft (R) .NET Framework Installation utility Version 2.0.50727.832
Copyright (c) Microsoft Corporation. All rights reserved.


Running a transacted installation.

Beginning the Install phase of the installation.
See the contents of the log file for the C:\Program Files\Microsoft Managed Services Engine\Microsoft.MSE.Runtime.exe assembly's progress.
The file is located at C:\Program Files\Microsoft Managed Services Engine\Microsoft.MSE.Runtime.InstallLog.
Installing assembly 'C:\Program Files\Microsoft Managed Services Engine\Microsoft.MSE.Runtime.exe'.
Affected parameters are:
logtoconsole =
assemblypath = C:\Program Files\Microsoft Managed Services Engine\Microsoft.MSE.Runtime.exe
i =
logfile = C:\Program Files\Microsoft Managed Services Engine\Microsoft.MSE.Runtime.InstallLog
Installing service RuntimeServer...
Creating EventLog source RuntimeServer in log Application...

An exception occurred during the Install phase.
System.ComponentModel.Win32Exception: The specified service already exists

The Rollback phase of the installation is beginning.
See the contents of the log file for the C:\Program Files\Microsoft Managed Services Engine\Microsoft.MSE.Runtime.exe assembly's progress.
The file is located at C:\Program Files\Microsoft Managed Services Engine\Microsoft.MSE.Runtime.InstallLog.
Rolling back assembly 'C:\Program Files\Microsoft Managed Services Engine\Microsoft.MSE.Runtime.exe'.
Affected parameters are:
logtoconsole =
assemblypath = C:\Program Files\Microsoft Managed Services Engine\Microsoft.MSE.Runtime.exe
i =
logfile = C:\Program Files\Microsoft Managed Services Engine\Microsoft.MSE.Runtime.InstallLog
Restoring event log to previous state for source RuntimeServer.

The Rollback phase completed successfully.

The transacted install has completed.
The installation failed, and the rollback has been performed.

C:\>
--------------------------End log-----------------------------

I restarted MSE service, nothing has changed
Jan 31, 2008 at 7:29 AM
Hi, any news?
Developer
Jan 31, 2008 at 2:50 PM
I just noticed something in the logs that you posted in your Mon at 3:49 PM message i.e.:

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

Do you have any endpoints associated with the Runtime server - 200332b?
Jan 31, 2008 at 5:12 PM
Yes, I was following the 30 minutes walkthrough.
Feb 7, 2008 at 2:10 PM
Hi, I saw a thread indicating that runtime server should have the same name of the host in the endpoint.
I gave it a go but always MSE is not able to function correctly.
Any news from your side?
Thanks
Developer
Feb 7, 2008 at 8:07 PM
Please see the updated reply to the thread you are referring to. It is possible to have the runtime server be a different name than the host machine it is running on.

Also, in the error logs you provided, although your "myServce" endpoint is assigned to a Runtime, the service endpoint hosts no operations:

mseTraceSrc Start: 1 : MseEndpointHost.InitializeRuntime
mseTraceSrc Error: 0 : Error in InitializeRuntime: Service '' has zero application (non-infrastructure) endpoints. This might be because no configuration file was found for your application, or because no service element matching the service name could be found in the configuration file, or because no endpoints were defined in the service element.
mseTraceSrc Stop: 2 : MseEndpointHost.InitializeRuntime
mseTraceSrc Information: 0 : Listening on http://localhost:8090/myService
mseTraceSrc Stop: 2 : MseRuntimeManager.ConfigureEndpoints for200332b

Go to one of the operations (AddIntegers), under the Endpoints list, click the Add button and select the "myService" endpoint and be sure to select the Is Active and Is Published fields.



eliassal wrote:
Hi, I saw a thread indicating that runtime server should have the same name of the host in the endpoint.
I gave it a go but always MSE is not able to function correctly.
Any news from your side?
Thanks

Feb 8, 2008 at 4:30 PM
Dear Botto, mySservice has both operations assigned to
Developer
Feb 11, 2008 at 7:02 PM
Please double check to make sure the operations are marked as published. If they are not published, you will still receive this error since the service has no operations to expose in the WSDL. There are two things to check.

1) make sure the version of the operation in myService is published.
select the 1.0.0.0 node under AddIntegers, and verify the Published checkbox is checked.

2) make sure your service (myService), publishes the operation.
select the AddIntegers node, select the myService endpoint listed in the Endpoints list for AddIntegers, click the Modify button.
verify the published radio button for version 1.0.0.0 is enabled and is selected. if it is greyed out (disabled) then double check step #1.

Also, just to be clear what problems we are solving since there have been a few different things going on:
Please verify my above steps
Stop the MSE Runtime Service
Delete the log files
Start the MSE Runtime Service
Post the contents of the log and what your current issue is to a NEW discussion thread.

I'd like to make sure we are helping to solve whatever issues you are currently experiencing.

Thanks,

let us know how it goes.


eliassal wrote:
Dear Botto, mySservice has both operations assigned to

Feb 12, 2008 at 7:23 AM
I will post the log to a new thread. Yes, all operations have "Published" checkbox checked and assigned to the endpoint.