Service port is not open

Aug 14, 2008 at 5:27 PM
I have my service brokered by MSE working. But after a day, something happened. I just could not connect to it any more. I started getting infamouse "No connection could be made because the target machine actively refused it" exception.

So I set to out find out what is happening to my MSE server. I made sure that Microsoft.MSE.Runtime.ServiceHost.exe is running. I could see the process in the task manager. Next I fired up TcpView to see if port for my endpoint is open. It is not. In fact, I did not see the process at all with any connection. So I created C:\Temp\Logs folder to get the logs. The log showed following:

<E2ETraceEvent xmlns="http://schemas.microsoft.com/2004/06/E2ETraceEvent">
<System xmlns="http://schemas.microsoft.com/2004/06/windows/eventlog/system">
<EventID>524312</EventID>
<Type>3</Type>
<SubType Name="Warning">0</SubType>
<Level>4</Level>
<TimeCreated SystemTime="2008-08-14T17:00:12.0392034Z" />
<Source Name="System.ServiceModel" />
<Correlation ActivityID="{00000000-0000-0000-0000-000000000000}" />
<Execution ProcessName="Microsoft.MSE.Runtime.ServiceHost" ProcessID="6044" ThreadID="1" />
<Channel />
<Computer>...</Computer>
</System>
<ApplicationData>
<TraceData>
<DataItem>
<TraceRecord xmlns="http://schemas.microsoft.com/2004/10/E2ETraceEvent/TraceRecord" Severity="Warning">
<TraceIdentifier>http://msdn.microsoft.com/en-US/library/System.ServiceModel.EvaluationContextNotFound.aspx</TraceIdentifier>
<Description>Configuration evaluation context not found.</Description>
<AppDomain>Microsoft.MSE.Runtime.ServiceHost.exe</AppDomain>
</TraceRecord>
</DataItem>
</TraceData>
</ApplicationData>
</E2ETraceEvent>

I don't know what "Configuration evaluation context not found." mean. Can any one provide any insight into this problem?

Thanks.
Oct 10, 2008 at 5:32 PM
I'm also running into this problem.  Was anyone ever able to provide an explanation?
Developer
Oct 10, 2008 at 8:37 PM
Did you try restarting the service?
There is a text file also in the temp\logs folder. What does that say?
Did you chaneg anything i.e. attach/detach endpoints etc.
Oct 13, 2008 at 2:55 PM
I have been having similar problems, not being able to connect to the service and getting the "No connection could be made because the target machine actively refused it" exception.
I seem to have solved it by restarting the Catalog and Runtime services, making sure that the original WCF services are up and running first.
It would be very helpful to have confirmation on whether restarts of service are necessary when adding endpoints/operations (this would be very limiting).

I also have perhaps a related issue that I can't get the MSE to return WSDL for a newer version of an operation, it keeps showing the original one.


Thanks for your help

Developer
Oct 16, 2008 at 3:48 PM
In the operation view of the management console.  Select the Endpoint you are experiencing this issue with and click Modify.  You'll then be able to select which version of the operation is Published at that endpoint (i.e. made public in the wsdl).
Jan 7, 2009 at 7:44 PM
ensure that the runtime server is hosting your service (MSE Management Console > Runtime Servers > Hosted EPs)