visual styles-related operation error

[Riyaz]

Hi There

When adding Jiwa as work resource, it works well but keep getting this error sometimes, especially when you click on search on SO maintenance , PO maintenance etc , pls see attachment

[Riyaz]

Hi There

Can you pls let me know on this, critical now

[Mike.Sheen]

Hi There

Can you pls let me know on this, critical now

If you want a response, particularly a timely one, you need to at least provide us with enough information to begin to troubleshoot.

You didn't even tell us the version of Jiwa you're using.

And I can see from the screenshot you have controls on that form that are not standard, so a plugin is involved and you didn't even mention that, let alone supply it.

And you didn't provide any steps to reproduce the error.

I really don't see how you expected anyone reading your post to be able to offer any help at all.

[Riyaz]

Hi Nike

Standard jiwa latest release, no plugins, installed on azure server and locally accesssd as work resources or remote app. Hope this helps

[Riyaz]

Pls ignore the screenshot I also tested this with Jiwa Demo

[Mike.Sheen]

Ok, next time how about not confusing the issue and posting irrelevant screenshots then.

You said:

When adding Jiwa as work resource, it works well but keep getting this error

What does that mean exactly- adding Jiwa as a work resource?

How about you give me a list of steps that I can follow in demo data that will see me get the same error.

[Riyaz]

Hi Mike
Screenshot is still valid, don’t think it’s relevant to plugins.

Hence I tried with standard Jiwa also and I could replicate it.

Pls see below steps to replicate

1: setup windows server 2022 on azure

2; install Jiwa

3; add Jiwa as a remote app

4: setup vpn to access the server

5: download Jiwa client as remote app

6: open Jiwa, it will work fine except for search pop up windows like debtor search

Pls let me know if you have any more questions

[Mike.Sheen]

You had already created a support ticket on our helpdesk for this issue before you made this forum post - I can see support are assisting you there.

Not a good idea to have two different teams working the same problem independently.