- Products
- Learn
- Local User Groups
- Partners
- More
Step Into the Future of
AI-Powered Cyber Security
The State of Ransomware Q1 2026
Key Trends and Their Impact
AI Security Masters E8:
Claude Mythos: New Era in Cyber Security
Blueprint Architecture for Securing
The AI Factory & AI Data Center
Call For Papers
Your Expertise. Our Stage
CheckMates Go:
CheckMates Fest
Hello!
I have a problem with the CVPND daemon on a VSX R80.40 cluster after updating JHF Take from 77 to 78.
The VS4 has Mobile Access blade enabled and SNX portal configured, which is not available after update.
1.On both nodes of the VSX cluster, the cpwd_admin list command shows the following outputs:
VSX-1:
VSX-2:
2.After starting the debug of CVPND daemon, the following logs are displayed in cvpnd.elg:
Line 14197: [30 Sep 15:44:06][CONF_READ] [CVPN_INFO] CvpnIS::SetDataReader::getField: Obtain the field: 'citrixStrictTicketEnforcement'
Line 14198: [30 Sep 15:44:06][CONF_READ] [CVPN_ERROR] CvpnIS::SetDataReader::getField: Could not obtain the field: citrixStrictTicketEnforcement
Line 14199: [30 Sep 15:44:06][ANY] Exception: SetDataReader::getField: Could not obtain the requested field - field name is: citrixStrictTicketEnforcement
Line 14200: [30 Sep 15:44:06] Exception: SetDataReader::getField: Could not obtain the requested field - field name is: citrixStrictTicketEnforcement - CVPND aborting
'
3.What is the reason for these messages?
Hello Ardenvil,
Fix for this issue will be part of the next jumbo release.
In the meantime please test if the following procedure help resolve the issue:
---
1. Connect to command line on VSX Gateway.
2. Log in to Expert mode.
3. For each involved Virtual System:
4. Backup the current cvpnd_internal_settings.C file in the context of the involved Virtual System:
[Expert@HostName:0]# vsenv <VSID>
[Expert@HostName:<VSID>]# cp $CVPNDIR/conf/cvpnd_internal_settings.C $CVPNDIR/conf/cvpnd_internal_settings.C_bck
5. Copy the cvpnd_internal_settings.C file from the context of VS0 (VSX Gateway itself) to the context of the involved Virtual System:
[Expert@HostName:<VSID>]# cp $CVPNDIR/conf/cvpnd_internal_settings.C $CVPNDIR/CTX/CTX<VSID>/conf/cvpnd_internal_settings.C
for example: cp $CVPNDIR/conf/cvpnd_internal_settings.C $CVPNDIR/CTX/CTX00002>/conf/cvpnd_internal_settings.C
Assign the required permissions to the copied file in the context of the involved Virtual System:
[Expert@HostName:<VSID>]# chmod 640 $CVPNDIR/CTX/CTX<VSID>/conf/cvpnd_internal_settings.C
Restart Mobile Access services:
[Expert@HostName:<VSID>]# cvpnrestart
This fix is included in R80.40 Jumbo Ongoing take 83.
Do you have a Citrix application published in Mobile portal?
No.
I've got exactly the same issue since Take 78 on VSX, and opened a TAC case for some days but no news for now.
The same issue at our customers - Take 78 kills MAB, it seems. Also TAC case open but no solution yet...
Hello Ardenvil,
Fix for this issue will be part of the next jumbo release.
In the meantime please test if the following procedure help resolve the issue:
---
1. Connect to command line on VSX Gateway.
2. Log in to Expert mode.
3. For each involved Virtual System:
4. Backup the current cvpnd_internal_settings.C file in the context of the involved Virtual System:
[Expert@HostName:0]# vsenv <VSID>
[Expert@HostName:<VSID>]# cp $CVPNDIR/conf/cvpnd_internal_settings.C $CVPNDIR/conf/cvpnd_internal_settings.C_bck
5. Copy the cvpnd_internal_settings.C file from the context of VS0 (VSX Gateway itself) to the context of the involved Virtual System:
[Expert@HostName:<VSID>]# cp $CVPNDIR/conf/cvpnd_internal_settings.C $CVPNDIR/CTX/CTX<VSID>/conf/cvpnd_internal_settings.C
for example: cp $CVPNDIR/conf/cvpnd_internal_settings.C $CVPNDIR/CTX/CTX00002>/conf/cvpnd_internal_settings.C
Assign the required permissions to the copied file in the context of the involved Virtual System:
[Expert@HostName:<VSID>]# chmod 640 $CVPNDIR/CTX/CTX<VSID>/conf/cvpnd_internal_settings.C
Restart Mobile Access services:
[Expert@HostName:<VSID>]# cvpnrestart
Hello, Eakselrod!
Thanks for your help, but unfortunately I cannot test your suggested procedure. Because I already reverted the VSX cluster using the snapshot taken before the JHF Take 78 update and now the MAB blade is working again.
This fix is included in R80.40 Jumbo Ongoing take 83.
sk169877 was published about this issue.
Leaderboard
Epsum factorial non deposit quid pro quo hic escorol.
| User | Count |
|---|---|
| 29 | |
| 12 | |
| 12 | |
| 8 | |
| 8 | |
| 7 | |
| 7 | |
| 6 | |
| 6 | |
| 5 |
Tue 12 May 2026 @ 10:00 AM (CEST)
The Cloud Architects Series: Check Point Cloud Firewall delivered as a serviceWed 13 May 2026 @ 11:00 AM (EDT)
TechTalk: The State of Ransomware Q1 2026: Key Trends and Their ImpactThu 14 May 2026 @ 07:00 PM (EEST)
Under the Hood: Presentando Check Point Cloud Firewall como ServicioTue 12 May 2026 @ 10:00 AM (CEST)
The Cloud Architects Series: Check Point Cloud Firewall delivered as a serviceTue 19 May 2026 @ 06:00 PM (IDT)
AI Security Masters E8 - Claude Mythos: New Era in Cyber SecurityAbout CheckMates
Learn Check Point
Advanced Learning
YOU DESERVE THE BEST SECURITY