05-11-2022 11:17 AM
We just started deploying AnyConnect 4.10.05095 and we're running into a problem with M1 Macs. One of the connection profiles is for our higher security VPN which does a posture check using OPSWAT. When Intel Macs use this profile, it works just fine. When M1 Mac use this profile they get the following error message, "Posture Assessment Failed": Unable to load the CSD library". These same users don't run into a problem when installing 4.10.01075. It apparently gives the error message with 4.10.04071 as well.
Has anyone else run into this problem?
Solved! Go to Solution.
05-11-2022 06:56 PM
This is most likely a compatibility issue between AnyConnect image and HostScan package on the headend. Take a look at the following table from the AnyConnect release notes.
You need at least HostScan 4.10.02086 configured on the headend if you have AnyConnect 4.10.2086 or later.
05-11-2022 12:57 PM
Followup - I had the user run DART, and I see this entry:
2022-05-11 15:20:59.833840-0400 0x17b0 Default 0x0 581 0 Cisco AnyConnect Secure Mobility Client: (libvpncommon.dylib) [com.cisco.anyconnect.vpn:acvpnui] Function: STLoadLibrary File: ../../vpn/Common/Utility/Win/HModuleMgr.cpp Line: 148 Invoked Function: dlopen Return Code: 0 (0x00000000) Description: dlopen(/Users/USERNAME//.cisco/vpn/cache/lib64_appid/libcsd.dylib, 0x0001): tried: '/Users/USERNAME//.cisco/vpn/cache/lib64_appid/libcsd.dylib' (mach-o file, but is an incompatible architecture (have 'x86_64', need 'arm64e')), '/Users/USERNAME/.cisco/vpn/cache/lib64_appid/libcsd.dylib' (mach-o file, but is an incompatible architecture (have 'x86_64', need 'arm64e'))
05-11-2022 06:56 PM
This is most likely a compatibility issue between AnyConnect image and HostScan package on the headend. Take a look at the following table from the AnyConnect release notes.
You need at least HostScan 4.10.02086 configured on the headend if you have AnyConnect 4.10.2086 or later.
12-31-2022 08:58 AM
Thanks for the solution, we also had a problem with the library on the study laptop, we could not figure out how to solve this problem.
05-12-2022 09:22 AM
Thank you - that turned out to be the problem. I had read the release notes, but clearly did not understand the third column - I thought that had to do with the client. Our network engineers made the update and we're good now.
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: