Smartconsole R81.10 Where Used not working

[Jonathan]

Hi,

Upgraded MGMT from R80.20 to R81.10 and installed new SmartConsole R81.10.

Everything went smoothly, by now, when using "Where used..." and double-clicking one of the result, it doesn't jump to the relevant rule.

It just brings me to the relevant policy tab and that's it.

Anyone had such an experience?

[G_W_Albrecht]

Did you install Build 407 SmartConsole https://sc1.checkpoint.com/documents/Jumbo_HFA/R81.10_SC/R81.10/Build_404.htm?Highlight=where%20used

and GA Jumbo 66 https://sc1.checkpoint.com/documents/Jumbo_HFA/R81.10/R81.10/Take_66.htm?tocpath=_____4 ?

[Jonathan]

yes and yes

[Nik_Bloemers]

Seems to be a known issue in build 407 of SmartConsole. I was told a new release with the fix was planned for end of July, but nothing yet sadly.

[Jonathan]

Do you have any SK about it?

Funny thing that a colleague of mine also installed it and it's working fine on his workstation

[Nik_Bloemers]

No it was somewhere on the Community forums here. I believe it was the thread about the build 407 SC release itself.

[Max_Frankl]

Hi,

I tried replicating your issue. Upgraded a MGMT with 80.20 to 81.10 and I'm using the build 407.
I cannot reproduce the issue. The "Where used" feature works for me..

It takes me to the exact policy i double click on..

I noticed you wrote that it works fine for your colleague? 

Maybe try reinstalling the smart console? 

[the_rock]

I have build 407 installed on 3 machines and not an issue on any of them. I think your suggestion makes sense.

[Jonathan]

Already tried to remove all previous versions, restarting my computer and installing again, but same issue 😞

I guess something on my workstation is causing it but have no idea what.

Is the SmartConsole Java based? Maybe it's a java issue...

[G_W_Albrecht]

Could be a .NET issue.

[Marcel_Gramalla · Accepted solution]

It's kinda confirmed by Check Point already: New GA SmartConsole (Build #407) for R81.10 is ava... - Check Point CheckMates

We also have the issue. For some reason the filter is enabled on the policy and therefore it's not working. If you disable the filter it will work again.

[Jonathan]

Genius!!!

What a stupid little bug/feature 😵

Thanks a bunch Marcel!