TrueSight Server Automation (TSSA) Patch analysis job fails with error 'BLPAT3206 - Failed to create agent-side analysis directory'

SCENARIO #1:
Live browsing the target would randomly throw the following error:
Encryption configuration error;//target-hostname



<patch analysis job log>

target,Error,<date> <time>,"Error while running pre-analysis on server: target01,Error: BLPAT3206 - Failed to create agent-side analysis directory: //target//<stagedirectory>/<stagefile>.
Check the following: network access to host, proxy configuration, disk space and read/write permissions of the directory on the host. (Caused By: JNI fileExists '//target//<stagedirectory>/<stagefile>' failed:: Encryption configuration error)"

SCENARIO #2:

<patch analysis job log>

target,Error,<date> <time>,"Error while running pre-analysis on server: target01,Error: BLPAT3206 - Failed to create agent-side analysis directory: //target//<stagedirectory>/<stagefile>.
Check the following: network access to host, proxy configuration, disk space and read/write permissions of the directory on the host. (Caused By: JNI fileExists '//target//<stagedirectory>/<stagefile>' failed:: Permission denied)"

SCENARIO #3:
Live browse works fine.

<patch analysis job log>

Error while running pre-analysis on server: <Targetservername>,Error: BLPAT3206 - Failed to create agent-side analysis directory: //target/<stagedirectory>/<stagefile>. Check the following: network access to host, proxy configuration, disk space and read/write permissions of the directory on the host. (Caused By: JNI fileExists '//target/<stagedirectory>/<stagefile>' failed:: Connection timed out)

SCENARIO #4:

<patch analysis job log>

Error while running pre-analysis on server: <Targetservername>,Error: BLPAT3206 - Failed to create agent-side analysis directory: //target/<stagedirectory>/<stagefile>.
Check the following: network access to host, proxy configuration, disk space and read/write permissions of the directory on the host. (Caused By: JNI fileExists '//target/<stagedirectory>/<stagefile>' failed:: No authorization to access host)

SCENARIO #5:

<patch analysis job log>

Error while running pre-analysis on server: <Targetservername>,Error: BLPAT3206 - Failed to create agent-side analysis directory: //target/<stagedirectory>/<stagefile>. Check the following: network access to host, proxy configuration, disk space and read/write permissions of the directory on the host. (Caused By: JNI fileExists '//target/<stagedirectory>/<stagefile>' failed:: SOCKS server reports general failure) ...

SCENARIO #6:

<patch analysis job log>

TARGET,Error,"18 Nov, 2021 4:36:54 PM","Error while running pre-analysis on server: TARGET,Error: BLPAT3206 - Failed to create agent-side analysis directory: //TARGET/C/Program Files/BMC Software/BladeLogic/RSCD/tmp/WindowsCatalog_133551_209_TARGET. Check the following: network access to host, proxy configuration, disk space and read/write permissions of the directory on the host. (Caused By: JNI fileExists '//TARGET/C/Program Files/BMC Software/BladeLogic/RSCD/tmp/WindowsCatalog_133551_209_TARGET' failed:: Login not allowed for user)" ...

SCENARIO #7:

<patch analysis job log>

MY-TARGET,Error,12/17/2024 15:35:57,"Error while running pre-analysis on server: MY-TARGET,Error: BLPAT3206 - Failed to create agent-side analysis directory: //MY-TARGET/C/Program Files/BMC Software/BladeLogic/RSCD/tmp/WindowsCatalog_10453_164_MY-TARGET.
 Check the following: network access to host, proxy configuration, disk space and read/write permissions of the directory on the host. (Caused By: JNI mkdirs of '//MY-TARGET/C/Program Files/BMC Software/BladeLogic/RSCD/tmp/WindowsCatalog_10453_164_MY-TARGET' failed: : Invalid argument)"

NOTE: Please check out the TSSA RSCD Agent Connectivity Troubleshooting Guide for more details on troubleshooting this kind of issues.

SCENARIO #1:

• Add/increase timeout setting in 'secure' file on the impacted target servers:
• rscd:port=4750:protocol=5:tls_mode=encryption_only:encryption=tls:timeout=90

SCENARIO #2:

• Check 'rscd.log' on the target covering the time of error.

• Make sure that the BSA role is mapped to a local user account on the target that can copy files to the target. 

• Right click on the target server >> select "Run Custom Command" >> select "Agent Information" and make sure that the agent is mapped to an appropriate admin user account

• It might give an error if any issues such as below, which can be rectified by re-opening the console with "Run as Administrator"

SCENARIO #3:

• Make sure the firewall is open from appserver/jobserver -> proxy server (if in use) -> target server

• Check if any timeout is set on the proxy server. If yes, increase the timeout and retest the use case

SCENARIO #4:

• Make sure the ACLs on the target server is correct and allows the connection from the source (appserver/socks proxy)
• Refer article - KA000266955

SCENARIO #5:

• Make sure that the target RSCD agent port is reachable from the SOCKS proxy

• Refer the article - KA000252205

SCENARIO #6:

• Make sure that the user account being used for RSCD agent mapping exists with appropriate permission
• The error generally suggests that the user account used for mapping does not exist
• Refer - KA000321629

SCENARIO #7:

- The error indicates that the target staging folder was running out of disk space. Thus make sure to cleanup disk space with agent cleanup and try again.
- In case of Windows server, 20G is recommended on 'C' drive as the minimum