We have recently received an Agent update on our K1000 appliance and now when we are trying to provision this agent we are getting the message ' MSI Info: [ERROR_INSTALL_PACKAGE_INVALID] This installation package could not be opened. Contact the application vendor to verify that this is a valid Windows Installer package.'

The msi and zip do exist in the location mentioned in the batch script. 

Log below. Same error occurs for 32 and 64bit machines.

Any ideas?

 [04/27/15 01:48:17 PM] Executing Windows platform provisioning. 


  STEP 1: CONNECT TCP/SSH - SUCCESSFUL


  [04/27/15 01:48:33 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(\KBRemoteService, 7216990)

      Sending commands

      Commands: //k1100.xxxx/client/agent_provisioning/windows_platform/agent_msi_provision.bat k1100.xxxx client ampagent-6.3.306-x86.zip k1100.xxxx

      Sending login credentials

      Login: xxxx\administrator

      [MSGCODE: 000] Begin agent_msi_provision.bat processing.

      [MSGCODE: 032] Detected 32-bit platform.

      [MSGCODE: 015] Executing MSI installer.

      

      C:\Windows\TEMP>start /wait msiexec.exe /qn /l*v C:\Windows\TEMP\ampmsi.log /i \\xxx\client\agent_provisioning\windows_platform\ampagent-6.3.306-x86.zip HOST=xxxx.xxxx

      

      C:\Windows\TEMP>echo off

      MSI Info: [ERROR_INSTALL_PACKAGE_INVALID] This installation package could not be opened. Contact the application vendor to verify that this is a valid Windows Installer package.

      [MSGCODE: 002] K1000 Agent is not installed.

      [MSGCODE: 092] AMP is not connected.

      ERROR: The system was unable to find the specified registry key or value.

      [MSGCODE: 095] KUID value not written by MSI installer.

      [MSGCODE: 100] End agent_msi_provision.bat processing.

      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


  [04/27/15 01:48:33 PM] End of remote communications. 

  [04/27/15 01:48:33 PM] End provisioning run.
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Answers

0
[07/31/15 11:31:34 AM] Begin provisioning...

  [07/31/15 11:31:34 AM] Executing Windows platform provisioning. 


  STEP 1: CONNECT TCP/SSH - SUCCESSFUL


  [07/31/15 11:31:50 AM] 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(\KBRemoteService, 7216990)

      Sending commands

      Commands: //xxx.xxxxxx.com/client/agent_provisioning/windows_platform/agent_msi_provision.bat xxx.xxxxxx.com client ampagent-6.3.314-x86.zip xxx.xxxxxx.com

      Sending login credentials

      Login: xxx-PC\administrator

      [MSGCODE: 000] Begin agent_msi_provision.bat processing.

      [MSGCODE: 064] Detected 64-bit platform.

      [MSGCODE: 015] Executing MSI installer.

      

      C:\Windows\TEMP>start /wait msiexec.exe /qn /l*v C:\Windows\TEMP\ampmsi.log /i \\xxx.xxxxxx.com\client\agent_provisioning\windows_platform\ampagent-6.3.314-x86.zip HOST=xxx.xxxxxx.com

      

      C:\Windows\TEMP>echo off

      MSI Info: [ERROR_INSTALL_PACKAGE_INVALID] This installation package could not be opened. Contact the application vendor to verify that this is a valid Windows Installer package.

      [MSGCODE: 002] K1000 Agent is not installed.

      [MSGCODE: 092] AMP is not connected.

      Fout: Het systeem kan de opgegeven registersleutel of -waarde niet vinden.

      [MSGCODE: 095] KUID value not written by MSI installer.

      [MSGCODE: 100] End agent_msi_provision.bat processing.

      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


  [07/31/15 11:31:50 AM] End of remote communications. 

  [07/31/15 11:31:50 AM] End provisioning run.
Answered 07/31/2015 by: RPSadmin
White Belt

Please log in to comment
0
At the bottom of the Provision Agent is Alternate Download Location. Try also entering the IP address of the KBOX server there. I have seen that work when for some reason, DNS won't resolve. 
Answered 04/27/2015 by: nshah
Red Belt

  • Thanks nshah, I tried this but unfortunately this did not help. Strange as the IP address did not save each time I went back into the provision agent screen.
Please log in to comment
0
Did you check the language version? I had to run the setlang.vbs script on the agent msi before it would work, even though I used the gpo provisioning tool.
Answered 04/27/2015 by: tpr
Fifth Degree Brown Belt

  • Thanks tpr, tried this but the same issue still occurred.
Please log in to comment
0
Ok, I have now got this working. Noticed there was an Agent update (I was using 6.3.306) to version 6.3.314. Applied this on the KBOX and I'm now able to provision successfully.

Thanks Guys.
Answered 04/28/2015 by: pegasus
Senior White Belt

  • Excellent. Planning to update to that soon.
  • I can confirm the update to 6.3.314 resolved this issue.
    • i have also the same issue ,updating to 6.3.314 did not help
Please log in to comment
Answer this question or Comment on this question for clarity