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!

Error scanning agent for ServerName



  • I have upgraded BuildMaster from 3.6 to 4.0.8 and now I am receiving "Error scanning agent for SERVERNAME" error messages page.

    I was using IIS-hosted (SOAP) and they I have run the agent installer to update the service. It has updated correctly and changed the application pool to 4.0. On server/environment page it shows:

    Status - Outdated
    Hosted - Yes (an agent is installed on the remote server)

    If I type the agent.asmx url, in the browser, it shows the service correctly.

    I have tried to update the agent and even restart the agent. The status does not change. After few minutes, I received a message of "Errors were reported in the error log.", at the top of BM, and the "Error scanning agent for ServerName" in detail message.

    How can I receive an outdated message if I just updated the service?

    Here is the exception information:

    Logged 1/14/2014 4:20:19 PM
    Message Error scanning agent for SERVERNAME (2)
    Stack Trace at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
    at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost)
    at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, FileOptions options, String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost)
    at System.IO.File.InternalReadAllBytes(String path, Boolean checkHost)
    at Inedo.BuildMaster.Extensibility.Agents.Soap.SoapAgent.<Inedo.BuildMaster.Extensibility.Agents.IHostedAgent.Update>b__c(ExtendedFileEntryInfo e)
    at System.Linq.Enumerable.WhereSelectEnumerableIterator2.MoveNext() at System.Linq.Enumerable.<ConcatIterator>d__711.MoveNext()
    at System.Linq.Buffer1..ctor(IEnumerable1 source)
    at System.Linq.Enumerable.ToArray[TSource](IEnumerable`1 source)
    at Inedo.BuildMaster.Extensibility.Agents.Soap.SoapAgent.Inedo.BuildMaster.Extensibility.Agents.IHostedAgent.Update(IHostedAgentContext context, Byte[] coreAssemblyZip)
    at Inedo.BuildMaster.Windows.ServiceApplication.AgentUpdater.CheckServer(Servers server)
    Close

    And the assembly versions:

    Core Assembly Versions
    BuildMaster 4.0.8.31
    BuildMaster.Extensibility 4.0.8.31
    BuildMaster.Web.Controls 4.0.8.31
    BuildMaster.Web.RemoteAgentWebApplication 4.0.8.31
    BuildMasterCore 4.0.8.31
    BuildMasterExtensions 4.0.8.31
    ICSharpCode.SharpZipLib 0.86.0.518
    InedoLib 58.1.0.0
    Menees.DiffUtils 2.0.2.0
    Renci.SshNet 2013.4.7.0



  • It's possible there are missing extensions on the remote server - you can manually copy them over directory from the X:\BuildMaster\Extensions installation directory directly to the X:\Agent\Extensions directory and restart the agent.

    However, the error indicates "Message Error scanning agent for SERVERNAME (2)", is SERVERNAME (2) a different server? If so, try disabling (edit server > mark inactive) that server and restart the BuildMaster server to force an update.



  • Hi Tod,

    Yes, SERVERNAME is another server. This server is where the files will be deployed. I just installed the agent here.

    From origination server, I had to updated everything manually. It seems that is everything OK after the update. Do I have to start any other specif service? For times to times the origination server tries to scan this external server to check the agent status and here where the issue is.

    I have tried your suggestions but they did not work.

    Thanks



  • Hi Tod,

    I could fix this problem and now all my servers are have their agents up to date.

    I had to remove everything from buildmaster from the server. I have uninstalled buildmasters agent, from Programs and Features, deleted BuildMaster website, application pool and the agent files from BuildMaster directory.

    Then, I have run the agent installer again in the server.

    Now, the status shows "Ready" and I am not receiving those "Error scanning agent for..." anymore.

    This is just a heads up, but it seems that the agent installer is not updating the existing agents in the server.

    Thanks


Log in to reply
 

Inedo Website HomeSupport HomeCode of ConductForums GuideDocumentation