All geek questions in one place

CruiseControl CommunicationsException Object Reference Error

In CruiseControl version 1.6.7981.1, I get the error message below from the event viewer, which causes the ccservice to stop. Work on this, I still enter the build window and start ccservice manually. It seems that this is happening sporadically, and I'm not sure what causes it, and I do not find any information about this error in the documentation and cruisecontrol.net website. If anyone knows or can point me in the right direction related to this error will be appreciated?

.NET Runtime version 2.0.50727.5466 - Fatal Execution Engine Error 80131506 2013-07-17 21:56:51,621 [MyProjectBuildNodes] ERROR CruiseControl.NET [(null)] - INTERNAL ERROR: Object reference not set to an instance of an object. ---------- ThoughtWorks.CruiseControl.Remote.CommunicationsException: Object reference not set to an instance of an object. at ThoughtWorks.CruiseControl.Remote.RemotingConnection.SendMessage(String action, ServerRequest request) at ThoughtWorks.CruiseControl.Remote.CruiseServerClient.GetProjectStatus() at ThoughtWorks.CruiseControl.Core.Triggers.ProjectTrigger.GetCurrentProjectStatus() at ThoughtWorks.CruiseControl.Core.Triggers.ProjectTrigger.Fire() at ThoughtWorks.CruiseControl.Core.Triggers.MultipleTrigger.Fire() at ThoughtWorks.CruiseControl.Core.ProjectIntegrator.PollTriggers() at ThoughtWorks.CruiseControl.Core.ProjectIntegrator.Integrate() at ThoughtWorks.CruiseControl.Core.ProjectIntegrator.Run() ----------
+4
source share
2 answers

After further study, the following are solutions to this problem:

  • Install the .NET Framework.
  • Install the application that will lead to the error ".NET Runtime version 2.0.50727.5466 - Fatal Execution Engine Error 80131506". We identified this through eventviewer and our application log.
  • Install the update for the host of your virtual machine if your server is running on a virtual machine. This is thought to be a known issue.

We considered all the options, and option 3 worked for us. It seems that this problem is caused by unexpected behavior on the virtual machine monitor when installed in Software Monitor mode.

+2
source

One reason for this exception is the inconsistent build version of CCNet Service and WebDashboard, or any other client that is connected to the CCNet service (for example, TrayApp, etc.).

You can also upgrade all involved parts of CCNet to the latest version 1.8.x.

+2
source

Source: https://habr.com/ru/post/1492145/

More articles:


All Articles