Sign In with your
Trend Micro Account
Need Help?
Need More Help?

Create a technical support case if you need further support.

"Error 1606.Could not access network location %APPDATA%\" appears when deploying Core Protection Module (CPM) for Endpoints

    • Updated:
    • 22 Oct 2014
    • Product/Version:
    • Core Protection Module 10.5
    • Core Protection Module 10.6
    • Endpoint Security Platform 8.0
    • Endpoint Security Platform 8.1
    • Endpoint Security Platform 8.2
    • Platform:
    • Windows 2003 Enterprise
    • Windows 2003 Enterprise 64-bit
    • Windows 2003 Standard
    • Windows 2003 Standard 64-bit
    • Windows 2008 Enterprise
    • Windows 2008 Enterprise 64-bit
    • Windows 2008 Server R2
    • Windows 2008 Standard
    • Windows 2008 Standard 64-bit
    • Windows 7 32-bit
    • Windows 7 64-bit
    • Windows Vista 32-bit
    • Windows Vista 64-bit
Summary
When deploying the fixlet Core Protection Module component to Endpoints using "Core Protection Module - Endpoint Deploy (Version 10.6 Service Pack 2)", you get the “Failed” status. The %WINDOWS%\OfcMSI.log file shows the following error :
“Error 1606.Could not access network location %APPDATA%\.
MSI (s) (94:F8) [15:29:40:923]: Product: Trend Micro OfficeScan Client -- Error 1606.Could not access network location %APPDATA%\.“
Details
Public
This error indicates that the AppData registry variable of the target endpoint was changed from “%USERPROFILE%\AppData\Roaming" to "%APPDATA%\". The possible reason why it was changed is explained in the Microsost (MS) article Error message when you install a program: "Error 1606. Could not access network location <common administrative tools>. All users\".
To resolve the issue:
  1. Log in to the target endpoint.
  2. Open the Registry Editor (regedit.exe).
  3. Set the value of "AppData" to "%USERPROFILE%\AppData\Roaming" in the following registries:
    • HKEY_USERS\.DEFAULT\Software\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders\
    • HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders\
  4. Redeploy the fixlet "Core Protection Module - Endpoint Deploy (Version 10.6 Service Pack 2)” to verify if the fixlet status is “Success” or “Fail”.
If the issue persists, collect the following:
  1. CPM Install Logs.
    • %WINDOWS%\CPM*.log
    • %WINDOWS%\OFC*.log
    • %WINDOWS%\ClnExtor.log
    • %WINDOWS%\System32\TmInstall.log
    • %WINDOWS%\setupapi.log
  2. Diagnostic Logs
    • Fixlet "TROUBLESHOOTING: Run BES Client Diagnostics" 
    • Fixlet "Core Protection Module - Execute CPM Case Diagnostic Tool (CDT)" (for upgrade deployment failure)
    • Case Diagnostic Tool - Standalone (for fresh installation)
  3. Process Monitor Logs (Sysinternals Tool) captured during CPM Endpoint Deployment.
Premium
Internal
Rating:
Category:
Troubleshoot; Deploy; Install; Upgrade
Solution Id:
1105529
Feedback
Did this article help you?

Thank you for your feedback!

To help us improve the quality of this article, please leave your email here so we can clarify further your feedback, if neccessary:
We will not send you spam or share your email address.

*This form is automated system. General questions, technical, sales, and product-related issues submitted through this form will not be answered.

If you need additional help, you may try to contact the support team. Contact Support


To help us improve the quality of this article, please leave your email here so we can clarify further your feedback, if neccessary:
We will not send you spam or share your email address.

*This form is automated system. General questions, technical, sales, and product-related issues submitted through this form will not be answered.


Need More Help?

Create a technical support case if you need further support.