Welcome to the Inedo Forums! Check out the Forums Guide for help getting started.

If you are experiencing any issues with the forum software, please visit the Contact Form on our website and let us know!

Execute database scripts on disk - Error at longer queries



  • Good morning,

    We have had a strange problem lately with the execute database scripts on disk step in BuildMaster. We had some scripts that took 45+ minutes and when the script finished BuildMaster gave an error.

    The message shown in the log is as follows:

    An unhandled exception occurred while executing this action: System.NullReferenceException: Object reference not set to an instance of an object.
       at Inedo.BuildMaster.Extensibility.Agents.Tcp.TcpAgent.Inedo.BuildMaster.Extensibility.Agents.IRemoteCommandExecuter.ExecuteCommand(RemoteActionBase action, String commandName, String[] commandArgs)
       at Inedo.BuildMaster.Extensibility.Actions.RemoteActionBase.ExecuteRemoteCommand(String name, String[] args)
       at Inedo.BuildMaster.Extensibility.Actions.ProviderBasedAction`1.Execute()
       at Inedo.BuildMaster.Extensibility.Actions.ActionBase.ExecuteInternal(IActionExecutionContext context, ExtensionConfigurerBase extensionConfigurer, Boolean resumeNextOnError, Boolean logErrorsAsWarnings)
    

    When we go look in the global error logs of BuildMaster we can however find another error log:

    Logged:
    14/09/2016 11:43:07
    Level:
    Error Error
    Category:
    Agent Updates
    Message:
    Error scanning agent for DKVACCSRVM003 (9)
    Details:
    at Inedo.BuildMaster.Extensibility.Agents.Tcp.TcpAgent.GetAgentStatusInternal(IHostedAgentContext context)
    at Inedo.BuildMaster.Windows.ServiceApplication.AgentUpdater.CheckServer(Servers server)
    
    Does anybody have a clue of how we can fix or prevent this?
    
    Thank you in advance and have a nice day!
    
    Kind regards,
    
    Nick
    

    Product: BuildMaster
    Version: 4.9.10



  • I suspect the two messages are unrelated... but unfortunately it's really hard to know what would cause the first problem. 99% of the time, especially over long-running things like this, it's a result of problematic network connections.

    The new Inedo Agents (available in v5) are a bit more resilient to this.



Inedo Website HomeSupport HomeCode of ConductForums GuideDocumentation