Yes! We are also facing the same problem, working with BO tech support and they send me a HOTFIX but of no use error exist and still ticket is open.
This problem is nothing to do with proxy, some thing with WISession Manager parameter (say Session timeout = 5400 sec). Normally, if ZABO users opens a session and keep it inactive, which exceed session timeout limit, then user try to refresh, ZABO throws this error.
You are right that this error comes due to inactive session but its not true practically.As in our case the error is coming within 10-15 minutes in a new session.
If it would have been the inactive session case then it would have been a diffrent case but in this case we are getting the error in a few minutes in a new session.
error is coming within 10-15 minutes in a new session.
what is your session timeout ? anyway.
In your first post you referred two errors
I am getting DA0005 and DA0003 error
Exception: CS, Unexpected behaviour related to DA0003, what is DA0005 then? If you give some details, that may be helpful to investigate. And also explain when users are getting these error ex: while refreshing the report? or while opening the session?.
Yes I remember that in first post I referred to DA0003 and DA0005 and must feel strange on listening that both the error message are having the same details i.e. Exception: CS, Unexpected behaviour.
The users are getting the error while refreshing the reports. Moreover they are able to refresh some other report using the same session that means the session does not expire.They can also create a small report using the existing session. Sometimes when the users get the error they close the BO window and try in other session and then they are able to refresh the report fine but its sometimes and not always.
Hope this gives you some more details regarding the problem.
Does your .rkey file name (ZABO key) having any special characters like dots?, If so, delete the key( with dots) and import new .rkey. file (without dots) then refresh the report. At the same time tell me about your web server (IIS or Apache/Tomcat) and your URL for ZABO download.
The main cause of this issue is Connection Timeout. As ZABO connects through webserver so whenever the connection at the webserver timesout ZABO throws this error.
Try increasing timeout to a reasonable value. Do not over increase it as this can result in lingering sessions when users do not logout correctly.
coming to my knowledge about this issue, i see that this error is given by CS:connectionserver(I believe), so researching in the inter process communication between connectionserver and sessiontimeout will probably give a solution.
Hello, i’m new to the forum. I’m an end user of business objects zabo version 6.5 with service pack 4 and i keep getting the DA003 error as soon as i try to refresh a query. i can create small queries off the same universe and they run fine. It just seems to affect the larger queries i try to run. it just started about a week or so ago. i’ve added the keep alive timeout and server info timeout to 60 minutes in the interent explorer registry and still get the same error. i read in this post about somehow changing the timeout of the webserver but not sure how to do that. i have a vista machine with ie7. i appreciate any help.