Visual Styles search error

[DannyC]

Was there a publicly available solution to this error?
viewtopic.php?t=2441

I have a client getting the same error and have spent a couple of hours deleting user profile, setting up new profile, ensuring just 1 session of Jiwa is running.

Would love to know the trick to get this resolved

[Scott.Pearce]

1. In the RDP client settings (before connecting), go to the Experience tab.
2. Make sure Visual styles (sometimes labeled "Themes" or "Visual themes") is checked/enabled (i.e. you may need to force a speed instead of using "Detect connection quality automatically").
3. Reconnect and try the operation again.

I think what could be happening is poor network performance is resulting in "Visual Styles" being switch off during an RDP session to save bandwidth, and this causes an error because components we use require visual styles to be always on.

[Mike.Sheen]

I should point out that the original issue was never resolved - the poster created a helpdesk ticket with the same issue as their post, and was asked for details on that ticket also on how to repro the issue and they never responded, so the ticket was auto-closed after 2 weeks.

Whether or not they worked it out, we do not know. Scott's guidance looks promising, however.

[Scott.Pearce]

I should add that if you are not using RDP, then try this:

1. Right-click on the desktop -> Personalize (or Appearance settings).
2. Choose a modern theme (e.g. any NON-Classic/NON-high-contrast theme).
3. Restart Jiwa and try the operation again.

[DannyC]

I should point out that the original issue was never resolved - the poster created a helpdesk ticket with the same issue as their post, and was asked for details on that ticket also on how to repro the issue and they never responded, so the ticket was auto-closed after 2 weeks.

I've asked my client to check their RDP settings so hopefully that's it.

As an aside, I do recall getting this issue a couple of years back for someone else and Scott's answer sort of tickles the memory a bit.

EDIT: Yep - it was the RDP setting.