TomCat Errors caused by Dashboards(?)

[Former Member]

SAP Enterprise BOE 4.1 SP5 Update 3 and Dashboards 4.1 SP5 update 3

We have some dashboards which are using the older queries built directly in QAAWS and newer ones which are using Web Services built via Webi.

Our TomCat error logs are filled with the below message (80mb in 12 hours). Is there a way of narrowing down what dashboard/report is causing this problem? I am assuming that this error is caused by a Dashboard query specifying incorrect credentials?

Caused by: com.crystaldecisions.sdk.exception.SDKServerException: Enterprise authentication could not log you on. Please make sure your logon information is correct. (FWB 00008)

cause:com.crystaldecisions.enterprise.ocaframework.idl.OCA.oca_abuse: IDL:img.seagatesoftware.com/OCA/oca_abuse:3.2
detail:Enterprise authentication could not log you on. Please make sure your logon information is correct. (FWB 00008)

The server supplied the following details: OCA_Abuse exception 10496 at [.\exceptionmapper.cpp : 67]  42040 {}
...Enterprise authentication could not log you on. Please make sure your logon information is correct. (FWB 00008)

at com.crystaldecisions.sdk.exception.SDKServerException.map(SDKServerException.java:99)
at com.crystaldecisions.sdk.exception.SDKException.map(SDKException.java:124)
at com.crystaldecisions.sdk.occa.security.internal.LogonService.doUserLogon(LogonService.java:920)
at com.crystaldecisions.sdk.occa.security.internal.LogonService.doUserLogon(LogonService.java:805)
at com.crystaldecisions.sdk.occa.security.internal.LogonService.userLogon(LogonService.java:210)
at com.crystaldecisions.sdk.occa.security.internal.SecurityMgr.userLogon(SecurityMgr.java:166)
at com.crystaldecisions.sdk.framework.internal.SessionMgr.logon_aroundBody0(SessionMgr.java:454)
at com.crystaldecisions.sdk.framework.internal.SessionMgr.logon_aroundBody1$advice(SessionMgr.java:512)
at com.crystaldecisions.sdk.framework.internal.SessionMgr.logon(SessionMgr.java:1)
... 27 more

[former_member194862]

Hi Joe,

It may not be related with the dashboard as when we get the error in tomcat log i.e. Enterprise authentication could not log on so the web service wont refresh with the data but in your case I think you get the data.

It could be an issue with some users trying to log in abrupty.If you get the data in the dashboard then there wont be any errors w.r.t. dashboards.

Regards,

Amit