Hello, 

Recently I notices that few and few agents are reporting back to ther server. I have a enviroment of 1178 machines and now only about 419 machines are reporting. 

I updated to the new agents and also udpated my server after attempting new proivsions and reviewing machines.  I have notices this message when it attempts to provision machines but I am not sure were to turn with this issue.  I put in a ticket with KACE support and then stated it was my network. Kace can see everything on the network and there is nothing blocking the computer to communicate with the server.

I have a physical unit.

The unit has been upgraded to 5.4SP1

Agents are the new 5.4.10

I noted this common them from the provisioning menu:

IP Address: 10.200.32.187
MAC Address: unknown 
Host Name (from DNS): 10.200.32.187
Suspected OS (from scan): Windows
Action: Agent Install
Provisioning Status: failed
K1000 Agent Installed: No
Error Category: No Error
 
Record Created: 02/27/2013 14:21:23
Record Last Modified: 02/27/2013 14:21:23
 
Provisioning Log



  [02/27/13 02:19:49 PM] Begin provisioning...
  [02/27/13 02:19:49 PM] Executing Windows platform provisioning. 
  [02/27/13 02:19:49 PM] Probing tcp ports for accessibility. 
  [02/27/13 02:19:49 PM] Port 139 [netbios-ssn] open 
  [02/27/13 02:19:49 PM] Port 445 [microsoft-ds] open 

  STEP 1: CONNECT TCP/SSH - SUCCESSFUL

  [02/27/13 02:19:52 PM] Executing remote communications:

      Initializing RPC
      Connecting to ADMIN$
      Copying service file
      Disconnecting ADMIN$
      Connecting to IPC$

  STEP 2: AUTHENTICATION - SUCCESSFUL

      Opening pipe to service
      IN: pipe_open(\pipe\KBRemoteService, 2)
      Sending commands
      Commands: //MRC-CP-K1000/client/agent_provisioning/windows_platform/agent_msi_provision.bat MRC-CP-K1000 client ampagent-5.4.10622-x86.msi MRC-CP-K1000
      Sending login credentials
      Login: VUHL.ROOT.MRC.LOCAL\mtm83
      [MSGCODE: 000] Begin agent_msi_provision.bat processing.
      [MSGCODE: 064] Detected 64-bit platform.
      [MSGCODE: 014] K1000 Agent is already installed.
      [MSGCODE: 100] End agent_msi_provision.bat processing.
      Removing service (Exit code: 0)
      ERROR: on_pipe_error - NT_STATUS_PIPE_DISCONNECTED
      OpenService - NT_STATUS_OK
      StopService - NT_STATUS_OK
      DeleteService - NT_STATUS_OK
      CloseServiceHandle - NT_STATUS_OK
      CloseSCMHandle - NT_STATUS_OK
      Connecting to ADMIN$
      Deleting service file
      Disconnecting ADMIN$

  STEP 3: PUSH SCRIPT\PROVISIONING - FAILED

  [02/27/13 02:19:52 PM] End of remote communications. 
  [02/27/13 02:19:52 PM] End provisioning run.

 

Any help or anything to try to fix this issue would be greatly appreciated!

Answer Summary:
Cancel
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Community Chosen Answer

1

Are you trying to provision new systems or update the ones that already have an agent?  From what you posted, it looks like the latter.

If they already have an agent, the provisioning task will fail because it checks to see if there is an agent installed.

How to enable automatic agent upgrades once you have uploaded the new agent kbin file to the K1000:

Settings>K1000 Agent>Agent Updates from KACE>Enabled

Also check the box for "Update Broken Agents".

PLEASE NOTE: If you have multiple organizations, you will need to do this for each one.

 

Answered 02/27/2013 by: jknox
Red Belt

  • I say this because this is in the debug log you provided: [MSGCODE: 014] K1000 Agent is already installed.
  • I have already done what you suggested for the new agents but my numbers of communicates are still dropping. I am getting this message on other machines in large numbers as well


    + Provisioning Target Info

    IP Address: 10.200.32.122
    MAC Address: unknown
    Host Name (from DNS): 10.200.32.122
    Suspected OS (from scan): Windows
    Action: Agent Install
    Provisioning Status: failed
    K1000 Agent Installed: No
    Error Category: AGENT related failure.
    Error: MSI_ERROR_CODES

    Record Created: 02/27/2013 14:47:29
    Record Last Modified: 02/27/2013 14:47:29

    Provisioning Log

    [02/27/13 02:40:41 PM] Begin provisioning...
    [02/27/13 02:40:41 PM] Executing Windows platform provisioning.
    [02/27/13 02:40:41 PM] Probing tcp ports for accessibility.
    [02/27/13 02:40:41 PM] Port 139 [netbios-ssn] open
    [02/27/13 02:40:41 PM] Port 445 [microsoft-ds] open

    STEP 1: CONNECT TCP/SSH - SUCCESSFUL

    [02/27/13 02:42:15 PM] Executing remote communications:

    Initializing RPC
    Connecting to ADMIN$
    Copying service file
    Disconnecting ADMIN$
    Connecting to IPC$

    STEP 2: AUTHENTICATION - SUCCESSFUL

    Opening pipe to service
    Sending commands
    Sending login credentials
    Begin agent_msi_provision.bat processing.
    Detected 64-bit platform.
    Executing MSI installer.

    C:\Windows\TEMP>start /wait msiexec.exe /qn /l*v C:\Windows\TEMP\ampmsi.log /i \\MRC-CP-K1000\client\agent_provisioning\windows_platform\ampagent-5.4.10622-x86.msi HOST=MRC-CP-K1000
    .....
    C:\Windows\TEMP>echo off
    MSI Info: [ERROR_INSTALL_FAILURE] A fatal error occurred during installation.
    K1000 Agent is not installed.
    AMP is not connected.
    KUID value detected.
    K1000 agent KUID: 33E84E7A-FC27-46D2-9237-C51B57C8CF3C
    End agent_msi_provision.bat processing.
    Removing service (Exit code: 0)
    Connecting to ADMIN$
    Deleting service file
    Disconnecting ADMIN$

    STEP 3: PUSH SCRIPT\PROVISIONING - FAILED

    [02/27/13 02:42:15 PM] End of remote communications.
    [02/27/13 02:42:15 PM] End provisioning run.
Please log in to comment

Answers

0
I just had this same behavior as mmeyer reported experiencing with provisioning of a new machine. I figured out that our FortiClient VPN software was somehow preventing it from installing.  I removed FortiClient, provisioned PCs, and then re-installed FortiClient and this seemed to work!

~Alicia
Answered 07/02/2014 by: awingren
Eighth Degree Black Belt

Please log in to comment
0

This is a bit confusing. The first log you provided you were trying to provision an alresdy provisioned machine, which fails (as designed).

The second log is a failed provision of an unprovisioned machine. Yet the questions states that you are having problems with agetns connection. If mahcines arent provisioned they wont connect so is the problem that you cant provision (as all your posted references outline) or that agents that are provisioned arent connecting (if so posting amp logs might help from those agents). Either way you are probably going to need to open a ticket with support.

Answered 02/27/2013 by: jdornan
Red Belt

  • Basically I am having both issues. I have a number of machines that will not provision and I have a large number(over 700 machines that will not check in). I have opened a ticket with support this afternoon to attempt to address the issue. I will pull the amp logs when I get in the office tomorrow. Thanks for everyone that is checking in and commenting.
Please log in to comment
Answer this question or Comment on this question for clarity