Provisioning from K2000 v.7 fails msiexec; can't open log file
K2000, version 7.x
Trying to do a test provisioning on this new, not-yet-in-production version 7 of the K1000, to a fresh Win10 box, and I'm getting the error below. Yes, "aculocal\westz" is a domain admin; I've also tried a local admin, with pretty much the same error but without the detail on the "ERROR_INSTALL_LOG FAILURE" line. When I tried the msiexec command manually from the Command Line, I got an error about not finding the log file, and I found that I couldn't create a file in C:\WINDOWS\TEMP, until I closed the Command line window and reopened it with Run As Administrator, which time the agent installed successfully. I uninstalled it, and tried again from the K1000, and keep getting this error:
STEP 2: AUTHENTICATION - SUCCESSFUL
Opening pipe to service
IN: pipe_open(\KBRemoteService, 7098287)
Sending commands
Commands: //jakin.acu.edu/client/agent_provisioning/windows_platform/agent_msi_provision.bat jakin.acu.edu client ampagent-7.0.763-x86.msi jakin.acu.edu
Sending login credentials
Login: ACULOCAL\westz
[MSGCODE: 000] Begin agent_msi_provision.bat processing.
[MSGCODE: 064] Detected 64-bit platform.
[MSGCODE: 015] Executing MSI installer.
%s
C:\Windows\TEMP>start /wait msiexec.exe /qn /l*v C:\Windows\TEMP\ampmsi.log /i "\\jakin.acu.edu\client\agent_provisioning\windows_platform\ampagent-7.0.763-x86.msi" HOST=jakin.acu.edu
%s
C:\Windows\TEMP>echo off
MSI Info: [ERROR_INSTALL_LOG_FAILURE] There was an error opening installation log file. Verify that the specified log file location exists and is writable.
[MSGCODE: 002] K1000 Agent is not installed.
[MSGCODE: 092] AMP is not connected.
[MSGCODE: 093] KUID value detected.
K1000 agent KUID: CA98FA46-E3E6-482C-BE4C-B5CDE02B0D87
[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
Opening pipe to service
IN: pipe_open(\KBRemoteService, 7098287)
Sending commands
Commands: //jakin.acu.edu/client/agent_provisioning/windows_platform/agent_msi_provision.bat jakin.acu.edu client ampagent-7.0.763-x86.msi jakin.acu.edu
Sending login credentials
Login: ACULOCAL\westz
[MSGCODE: 000] Begin agent_msi_provision.bat processing.
[MSGCODE: 064] Detected 64-bit platform.
[MSGCODE: 015] Executing MSI installer.
%s
C:\Windows\TEMP>start /wait msiexec.exe /qn /l*v C:\Windows\TEMP\ampmsi.log /i "\\jakin.acu.edu\client\agent_provisioning\windows_platform\ampagent-7.0.763-x86.msi" HOST=jakin.acu.edu
%s
C:\Windows\TEMP>echo off
MSI Info: [ERROR_INSTALL_LOG_FAILURE] There was an error opening installation log file. Verify that the specified log file location exists and is writable.
[MSGCODE: 002] K1000 Agent is not installed.
[MSGCODE: 092] AMP is not connected.
[MSGCODE: 093] KUID value detected.
K1000 agent KUID: CA98FA46-E3E6-482C-BE4C-B5CDE02B0D87
[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
[12/14/16 07:49:41 AM] End of remote communications.
[12/14/16 07:49:41 AM] End provisioning run.
Deleting service file
Disconnecting ADMIN$
STEP 3: PUSH SCRIPT\PROVISIONING - FAILED
[12/14/16 07:49:41 AM] End of remote communications.
[12/14/16 07:49:41 AM] End provisioning run.
1 Comment
[ + ] Show comment
-
btw, what are the %s lines in the above code? - kentwest 7 years ago
Answers (2)
Answer Summary:
Please log in to answer
Posted by:
rileyz
7 years ago
Posted by:
kentwest
7 years ago
Ah, rileyz put me onto the path of finding a solution.
My Win10 client PC has three (relevant) accounts:
- the built-in Administrator account (disabled by default)
- a local admin account
- a domain account which had been added to the local Administrators group
When using KACE credentials set up to use the last two accounts, the provisioning fails. But when I enabled and used the built-in Administrator account, the provisioning works.
Now all I have to do is figure out how to use the local admin account instead of the built-in Administrator account, but at least I'm on the right track now.
Thanks, rileyz!
--
Kent
Comments:
-
I have been having the same issue, expect my domain admin got farther than the built-in Administrator account.
I needed to enable this registry for the built-in Admin to get to the same error as the domain admin.
http://www.itninja.com/blog/view/nt-status-access-denied-error-while-provisioning-k1000-agent-on-win-vista-win-7-win8-win-2012
What's weird is before upgrading to v7.0 the built-in Admin worked for me. - troyr 7 years ago-
if you use the "update agents" and put labels in that it works without problems - SMal.tmcc 7 years ago
-
That broke 20% of our computers (uninstalled agents). I've been trying to use the scheduled provisioning to re-install the agent on the broken ones. - troyr 7 years ago
-
that sucks, sorry to hear that. I have had 0 failures using the update method. The only problem I ran into is my 2012r2 servers with beta version 7.0.744 will not update to 7.0.763 - SMal.tmcc 7 years ago