- Products
- Learn
- Local User Groups
- Partners
- More
Scaling Check Point Automation with Arodonata
7 October @ 5pm CET / 11am EDT
AI Security Masters
LGTM: Bypassing an LLM Build Gate
When Prompt Injection Fails
What's New in Check Point SASE
The State of Ransomware Q2 2026:
This Quarter's Trends, and Their Impact on Your Defenses
CheckMates Go:
Half is Not Enough
Hi all -
I have one vm for policy management, and one for smartevent/logging. upgraded both from r80.40 -> r81. Both upgrades were error-free, and both are working fine independently.
The only issue i'm currently having is when I'm connected with dashboard to the policy management vm, i can't view logs from the log server - "smartlog is initializing" changes to "smartlog is not active" after a few minutes. This of course worked fine in 80.40.
Pointing dashboard directly to the log server works fine for viewing logs, but it's nice to highlight a specific rule and see the logs for only that rule.
I've reset SIC, and installed the database on the log server.
Any thoughts would be appreciated.
thanks.
Hi,
The issue is known and Installing R81 JHF T42 should resolve the issue.
Hi
Have you tried simply to stop and start the Security Management Server machine?
There are several SKs for this issue, depending on the root cause:
HTH
Tal
@Dror_Aharony for additional assistance
Hi @D_TK
Would you be able to share your solution please to this issue?
I just happen to have exactly the same problem and can't seem to find a fix.
Kind Regards,
Eli
I applied JHA 42 for R81 and it resolved the issue.
Hello,
It seems to be a bug, i've had the same problem on three differente servers after upgrade to R81. Solution is documented here :
Regards
R81 JHF T42 should resolve the issue.
Hi,
The issue is known and Installing R81 JHF T42 should resolve the issue.
FYI,
we have just completed an upgrade of the smartcenter server from R80.40 to R81, Mgmt server has JHF T44, upgrade was an export database, import to new VM, logs servers are still running R80.40 and we had the same issue
following the steps in sk175223 fixed it
We've had the same issue and opened a SR.
It was fixed by the procedure mentioned in sk175223.
Have run into this issue a couple of times - sk175223 is now part of my R81 upgrade process notes.
P.S. Have only seen this when doing in-place upgrade via blink. Migrations have been issue free.
I did a clean R81 installation and imported the old database. The issue occures also in this scenario (did it twice and both times the same issue).
Leaderboard
Epsum factorial non deposit quid pro quo hic escorol.
| User | Count |
|---|---|
| 33 | |
| 8 | |
| 6 | |
| 5 | |
| 5 | |
| 4 | |
| 4 | |
| 4 | |
| 4 | |
| 3 |
Thu 01 Oct 2026 @ 05:00 PM (CEST)
Under the Hood: Check Point WAF | Preventing minus-zero-day attacksTue 06 Oct 2026 @ 12:00 PM (ACDT)
Rethinking Network Security for the AI Era : Session 2 - From User, to Branch and Campus APACTue 06 Oct 2026 @ 03:00 PM (CEST)
Rethinking Network Security for the AI Era : Session 2 - From User, to Branch and Campus EMEAThu 01 Oct 2026 @ 05:00 PM (CEST)
Under the Hood: Check Point WAF | Preventing minus-zero-day attacksTue 06 Oct 2026 @ 12:00 PM (ACDT)
Rethinking Network Security for the AI Era : Session 2 - From User, to Branch and Campus APACTue 06 Oct 2026 @ 03:00 PM (CEST)
Rethinking Network Security for the AI Era : Session 2 - From User, to Branch and Campus EMEATue 06 Oct 2026 @ 02:00 PM (EDT)
Rethinking Network Security for the AI Era : Session 2 - From User, to Branch and Campus AMERAbout CheckMates
Learn Check Point
Advanced Learning
YOU DESERVE THE BEST SECURITY