I would check your EPiServer scheduler configuration. It looks like it can't remote to the EPiServer instance when trying to run scheduled jobs so is throwing the exception.
Try stopping the scheduler service first to see if that stops the logs getting entered and work from there.
Ps the file you want to examine is C:\Program Files\EPiServer\Shared\Services\Scheduler Service\EPiServer.SchedulerService.Sites.xml
I think the logging feature for the Scheduler also works for CMS 6. See:
http://www.epinova.no/blog/Tore-Gjerdrum/dates/2010/11/enable-debugging-in-episerver-scheduler/
It might give you some more information about the problem.
Best Regards,
Steve Celius
Below is the log from the scheduler (on the internal test environment)
I have also included the WCF-configuration in web.config.
And episerver-log is still being filled up...
Alf
[2011-01-07 14:45:45UTC] #INF# ********************************************************
[2011-01-07 14:45:45UTC] #INF# * EPiServer Scheduler Service running in SVCDEBUG mode
[2011-01-07 14:45:45UTC] #INF# ********************************************************
[2011-01-07 14:45:45UTC] #INF# <configuration> \ <system.runtime.remoting> \ <customErrors mode="On|Off|RemoteOnly" /> setting in .config may prevent full exception details from being returned by remoting framework
[2011-01-07 14:45:45UTC] #INF# RegisterChannel
[2011-01-07 14:45:45UTC] #INF# Testing service connection
[2011-01-07 14:45:45UTC] #INF# Enumerating Registered Services types:
[2011-01-07 14:45:45UTC] #INF# type='EPiServer.Scheduler.External, EPiServer.SchedulerSvc'; objectUri=Service.rem; mode=SingleCall
[2011-01-07 14:45:45UTC] #INF# Probing connection:
[2011-01-07 14:45:45UTC] #INF# PING!
[2011-01-07 14:45:45UTC] #INF# PONG!
[2011-01-07 14:45:45UTC] #INF# Connection OK
[2011-01-07 14:45:45UTC] #INF# Loaded queue with 1 sites:
[2011-01-07 14:45:45UTC] #INF# [_LM_W3SVC_2_ROOT] http://gpn-test:81/
[2011-01-07 14:45:45UTC] #INF# Service started - begin accepting connections
[2011-01-07 14:45:45UTC] #INF# [_LM_W3SVC_2_ROOT] Site listener started
[2011-01-07 14:45:45UTC] #INF# [_LM_W3SVC_2_ROOT] Failed calling site (Attempting to deserialize an empty stream.)
[2011-01-07 14:46:45UTC] #INF# [_LM_W3SVC_2_ROOT] Failed calling site (Attempting to deserialize an empty stream.)
[2011-01-07 14:47:27UTC] #INF# [_LM_W3SVC_2_ROOT] Site changed status to Online
[2011-01-07 14:47:45UTC] #INF# 10s warning - due time is 7. januar 2011 14:38:01
[2011-01-07 14:47:45UTC] #INF# [_LM_W3SVC_2_ROOT] New scheduled job 07.01.2011 14:38:01 (8de3f2b0-6e12-4716-a6f9-736f7e2f8944)
[2011-01-07 14:47:55UTC] #INF# [_LM_W3SVC_2_ROOT] Execute job 8de3f2b0-6e12-4716-a6f9-736f7e2f8944
[2011-01-07 14:47:56UTC] #INF# [_LM_W3SVC_2_ROOT] New scheduled job 07.01.2011 14:48:56 (8de3f2b0-6e12-4716-a6f9-736f7e2f8944)
[2011-01-07 14:48:56UTC] #INF# [_LM_W3SVC_2_ROOT] No new scheduled jobs, currently waiting for 07.01.2011 14:48:56 (8de3f2b0-6e12-4716-a6f9-736f7e2f8944)
[2011-01-07 14:48:56UTC] #INF# [_LM_W3SVC_2_ROOT] Execute job 8de3f2b0-6e12-4716-a6f9-736f7e2f8944
[2011-01-07 14:48:56UTC] #INF# [_LM_W3SVC_2_ROOT] New scheduled job 07.01.2011 14:49:56 (8de3f2b0-6e12-4716-a6f9-736f7e2f8944)
[2011-01-07 14:49:56UTC] #INF# [_LM_W3SVC_2_ROOT] No new scheduled jobs, currently waiting for 07.01.2011 14:49:56 (8de3f2b0-6e12-4716-a6f9-736f7e2f8944)
[2011-01-07 14:49:56UTC] #INF# [_LM_W3SVC_2_ROOT] Execute job 8de3f2b0-6e12-4716-a6f9-736f7e2f8944
<system.serviceModel>
<client>
</client>
<bindings>
<customBinding>
<binding name="RemoteEventsBinding">
<binaryMessageEncoding/>
<udpTransport multicast="True"/>
</binding>
</customBinding>
</bindings>
<extensions>
<bindingElementExtensions>
<add name="udpTransport" type="Microsoft.ServiceModel.Samples.UdpTransportElement, EPiServer.Events"/>
</bindingElementExtensions>
</extensions>
<services>
<service name="EPiServer.Events.Remote.EventReplication"/>
</services>
<behaviors>
<serviceBehaviors>
<behavior name="DebugServiceBehaviour">
<serviceDebug includeExceptionDetailInFaults="true"/>
</behavior>
</serviceBehaviors>
</behaviors>
</system.serviceModel>
What we ended up doing was to hide the warning instead of fixing it. We added the following to EpiServerLog.config:
<logger name="Microsoft.Samples.Runtime.Remoting.Channels.Pipe.DBG" additivity="false">
<level value="Error" />
</logger>
Every minute an entry gets added to the log file, and I have not so far been able to stop it.
2011-01-07 09:47:50,764 WARN [PipeServerChannel.ServerMain] Microsoft.Samples.Runtime.Remoting.Channels.Pipe.PipeServerChannel.ServerMain - 18.3.1 Scheduler error: Terminating client connection: Error reading from pipe 7116: error 109
This happens in all our environments (dev, test, production), so I suspect it has something to do with the configuration.
We are running EPiServer CMS 6 on Windows Server 2008 R2 and under .NET 4 runtime in a single server setup.