Share via

Cisco AnyConnect Installation Failed 1603 Fatal Error via SCCM

Muhammad Amir Minhat 1 Reputation point
2021-11-10T02:44:59.023+00:00

Hi,

I have tried to deploy a Cisco AnyConnect Secure Mobility Client via Microsoft SCCM. After deployment, it shows an error code 1603 Fatal Error.

On the client PC, we can see from the Software Center status "Past due - will be retried"

The installer is in msi format. And we can manually install the same installer with no issue. This problem only occur when we try pushing from the SCCM.

I have tried engage with Cisco but no error logs can be seen from the Vendor Diagnostic Tool. It is like something is restricting the installation on the client side.

Does anybody have the same problem? Appreciate the response.

Microsoft Security | Intune | Configuration Manager | Other
0 comments

5 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Rosales, Jose 0 Reputation points
    2023-03-24T18:57:47.0133333+00:00

    I've ran across that. In my case, there were old registry keys that were not removed. We pushed the SCCM package (MSI) to a user and it gave that error. I had a remote session with the user and saw that she did not have the old version anymore, and when running the package manually, it gave the 0x643(1603) error. I searched the registry for "Cisco AnyConnect" and found that there was still a registry key on the machine referring to the old version. I deleted it and I was able to install the software package manually with no error. So you might have to script your install to remove keys for versions that you have used in your environment after uninstalling the application. The key that I had to delete was "HKEY_CLASSES_ROOT\Installer\Products\1C011CEEC5BBD774F8F76E87F1ABF281".

    Was this answer helpful?

    0 comments
  2. Agusti Grau 6 Reputation points
    2021-11-12T10:22:01.557+00:00

    If the deployment is configured to be silent, maybe the installation process are asking for an user interaction.

    Can you try to add "/q" to the commandline

    Was this answer helpful?

    0 comments
  3. Limitless Technology 40,106 Reputation points
    2021-11-12T09:19:20.277+00:00

    Hi there,

    Error 1603 generally occurs due to installation errors or corruption of the setup during installation or uninstallation although there are many other reasons too. Here are some of the ways to fix the problem :

    Close Background Software
    Check the Software Is not Already Installed
    Check That There’s Enough Hard Drive Space for the Program
    Open the Program Install and Uninstall Troubleshooter
    Erase Temporary Files From the Windows Temp Folder
    Restart the Windows Installer Service
    Edit the NtfsDisable8dot3NameCreation Registry Value
    Grant Full Control Permission to Installation Drive

    --If the reply is helpful, please Upvote and Accept it as an answer--

    Was this answer helpful?

    0 comments
  4. Amandayou-MSFT 11,166 Reputation points
    2021-11-11T06:39:09.627+00:00

    Hi @Muhammad Amir Minhat ,

    The 1603 error code is mostly returned when any action fails during an installation, and most commonly it indicates that one of the custom actions in the MSI failed.

    It could occur when a file is being used which this MSI needs in order to finish installation. Or when you have a pending reboot.

    Agree with EswarKoneti, about command line syntax for MSI, here is the example of .msi application, we could refer to it to install it:
    https://learn.microsoft.com/en-us/mem/configmgr/apps/get-started/create-and-deploy-an-application

    We also could take a look at AppIntentEval.log, AppDiscovery.log, and AppEnforce.logs on the device in c:\windows\ccm\logs\ to start troubleshooting why the installation is failing.

    If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    Was this answer helpful?

    0 comments
  5. KONETI ESWARARAJU 2,206 Reputation points MVP Volunteer Moderator
    2021-11-10T03:21:03.823+00:00

    What is your command line syntax for MSI?
    Did you add log verbose switch to capture more details that will help you to reveal the reason for the failure?
    The following will the usual syntax for any msi along with log capture.

    msiexec /i "filename.msi" /L*V "foldertostorelog\filename.log"

    Thanks,
    Eswar
    www.eskonr.com

    Was this answer helpful?

    0 comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.