"illegal access to the viewer please use a valid url" when open the webi report in BI Launch pad

[Former Member]

Hi Exports,

We have done a migration project from 3.x to 4.1 sp4. After the migration when trying to open the webi report, we are getting the below error

"illegal access to the viewer please use a valid url"

We got some KBA from the SAP notes, but non of this have solve the error. This error occur multiple times even though after restarting the SIA (Server Intelligence Agent). At the time of restarting the SIA the reports are working fine for several hours, then again we are getting this issue for all the webi reports when trying to open it.

There is no issue with the licence key. It is a valid one.

Is there any workaround solution?

Regards,

Raja

[former_member185603 · Accepted solution]

What is the specs of your server?

[Former Member · Accepted solution]

Thanks for the response Mr. Jawahar Konduru.

OS: Windows Server 2012 R2 Standard

Ram: 32GB

System type: 64 bit Operating System

Processor: Intel(R) Xeon(R) CPU E5-2643 0 @ 3.30 GHz

these are the specs of the server..

[former_member182521 · Accepted solution]

If the issue is not related to Licence key anymore, We can confirm that this is related to your system which is running out of resources. You may need to size your system and scale it appropriately (Horizantal/Vertical). You may need to go from a standalone to a clustered environment.

Thanks

Mani

[Former Member · Accepted solution]

Thank you Manikandan Elumalai. After doing sizing, it seems working fine till now..

If we face this issue again, I will come back..

Thanks,

Raja S

[Former Member]

Hi Raja,

In which mode you are opening the webi report (Applet mode/ Html mode/ Desktop mode)?
Is Webi Processing server running and enabled?
What is the Java version you are using?
Change the Webi mode to Html open the report and check if you are able to view it (BI Launchpad -> Preferences -> Web Intelligence).

Regards,
Medha

[Former Member]

Hi Medha Mehta,

Thanks for your response. It seems the issue has been solved by doing sizing..

[Former Member]

Thanks Raja... glad to know that the issue is resolved.

~Medha