Please note that VisualCron support is not actively monitoring this community forum. Please use our contact page for contacting the VisualCron support directly.


ErikC
  •  ErikC
  • Free support Topic Starter
2015-05-20T06:01:33Z
Hi,

Today i checked the log_server📅.txt file in the VC\log folder and there are a lot of errors in there:

5/20/2015 12:00:00 AM	Err	ClientError: The communication object, System.ServiceModel.Channels.ServiceChannel, cannot be used for communication because it has been Aborted.: 
Server stack trace: 
   at System.ServiceModel.Channels.CommunicationObject.ThrowIfDisposedOrNotOpen()
   at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)
   at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)
   at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)

Exception rethrown at [0]: 
   at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
   at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
   at CommServer.Classes.WCF.IWCFServiceCallback.OnSent(Message message)
   at CommServer.Classes.WCF.WCFConnection.Send(Message message)

and
5/20/2015 12:00:00 AM	Err	GetExitCodeResult->error: System.NullReferenceException: Object reference not set to an instance of an object.
   at VisualCronService.ExitCodeAPI.GetExitCodeResult(String strCollectionId, Int32 intExitCode) in C:\sourcefiles\code\VisualCronService\Jobs\ExitCodes\apiExitCode.vb:line 267

These errors are there every few miliseconds filling up the log. It started the 15th of May.

I will restart the whole server today to see if the errors continue....

to be continued

Regards,
Erik
Uses Visualcron since 2006.
Sponsor
Forum information
Support
2015-05-20T06:44:15Z
The first error might be just a logging issue as we log this error when someone disconnects in 7.6.3. However, client to server connection is buggy in this version.

About the exit code error it is not a serious one. It just cannot find the specified exit code. We will handle this better though in the future.
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
ErikC
  •  ErikC
  • Free support Topic Starter
2015-05-20T08:50:35Z
After a server reboot the errors are gone.

I'll try to upgrage in the near feauture to a higher version.

Regards,
Erik
Uses Visualcron since 2006.
Scroll to Top