How to determine if dependencies are coming from the replication share or the SMA appliance (4294220)

When using replication shares, it may become necessary to determine if dependencies are being copied from the replication share to the local agent.  Some of those might include:

• Failed patch dependency downloads ("Handshake Failed" errors)
• Failed scripts from the SMA (Systems Management Appliance, former K1000)
• Failed managed installations from the SMA
• Successful tests when using "Failover to SMA" on the Replication Share

There are multiple situations which may require to verify exactly what happens when files are copying from the replication share to the agent.  It is possible to use logs to review what happened. 

It is possible to review the logs to obtain the answers to dependencies and replication shares.  

Please note that for the KACE SMA version 6.4.x and older (former K1000) it is necessary to enable debugging in order to see full details for dependency download; version 7.x and newer have debugging enabled by default. For more information on enabling debugging on version 6.4.x and older, please see: How to enable debug logs on the KACE K1000 Client versions 6.4.x and below

Having debugging enabled, perform the problematic task (run patch schedule, script, managed install, or task that is causing an issue).  Once the task has completed, proceed to review the logs.

To review the logs on the local test system:

1. Go to C:\ProgramData\Quest\KACE\user
2. Open the KAgent.txt log with Notepad or any other similar text reader
3. Scroll down to the bottom for the most recent time stamp.
4. Scroll up a little at a time until you see signs of the task -OR- use Find (ctrl+f) to locate certain terms
1. Example search terms in this situation:  Failing, Failing Over to SMA location, Downloading dependency, Downloading dependency from alternate location, or DownloadSMBFile.

Below are some examples of actual log lines for different situations:

• Failed to download dependency from replication share example:  [2016-01-18.13:15:30][runkbot:DownloadDependency      ] Downloading dependency from alternate location [smb://admin:xxxxxx@TXReplication/KACE Replication/repl2/kbots/32/setdebug.bat.2ff8eb769d3709a1c699538ae9523877]

[2016-01-18.13:15:33][runkbot:DownloadSMBFile         ] DownloadSMBFile: unable to copy file from: '\\TXReplication\KACE Replication/repl2/kbots/32/setdebug.bat.2ff8eb769d3709a1c699538ae9523877' to: 'C:\ProgramData\Quest\KACE\kbots_cache\packages\kbots\32\setdebug.bat': (53) The network path was not found.

• Failing over to the SMA example:  [2016-01-18.13:15:33][runkbot:DownloadDependency      ] Downloading dependency from alternate location [smb://admin:xxxxxx@TXReplication/KACE Replication/repl2/kbots/32/setdebug.bat.2ff8eb769d3709a1c699538ae9523877] - Failed

[2016-01-18.13:15:33][runkbot:DownloadDependency      ] Failing Over to KBOX location [http://k1000/packages/kbots/32/setdebug.bat.2ff8eb769d3709a1c699538ae9523877]

• Successful download of dependency from replication share example:  [2016-01-18.11:28:14][pluginPatching:DownloadFile ] DownloadFile: Downloaded C:\Program Files (x86)\Quest\KACE\winsecuritydefinitions.ospx from smb://admin:xxxxxx@TXReplication/KACE Replication/repl2/patches/winsecuritydefinitions.ospx.83295227793f5bc7ae6171db7f1444c7 Download speed: 172234 bytes/second

If there are any issues analyzing the logs, please use Using the KACE Agent Toolkit (KAT) to capture the logs and Contact Support for additional assistance.