I have an anoying error that keeps coming up and I have no idea what it is. I have checked the in built help…guess what, can’t find anything about it!!
I get the error when running a report in Deski (XI R2), but only if it is a large report that takes a long time (like an hour or more). If I schedule the report in infoview it runs fine, but run it ‘manually’ in Deski and it brings up the error.
The error is:
“Error During SQL Execution: (DA0003)”
and the details say:
“Exception: CS, Job already in use”
and that’s it, nothing else. It’s really beginning to anoy me now so any help would be greatly appreciated.
This is usually a caused by a timeout of some sort. We’re seeing it now too, but not for everyone.
I’ve seen this as a firewall issue before as well. The BO environment doesn’t tell the client that it’s doing anything. So, the client thinks the server is dead and drops the connection resulting in the useless error message you are gettting.
It’s not exactly a BO problem. You likely have something else (firewall or proxy) that is dropping your session after an hour. The problem is that the BO software doesn’t send a keep-alive back to the desktop. So the firewall or proxy thinks your session is dead and deletes it.
You need to talk to your infrastructre team and see what’s in place.
I have spoken to our IT dept and we don’t have a proxy or a firewall within our LAN, my desktop client is going straight to the server.
Secondly to answer Vidhi - I have run the reports on the schedular through infoview (my understanding is that that runs the report on the server??) and it works fine.
But when i open the report in DeskI on server/local machine and try to refresh it ,it throws the same error “Job Already in use”.
I have migrated this report from BO5.1 to BOXI. On BO5.1 ,it works fine and refresh also but not on BOXI.
We are also getting this message almost for all ZABO reports which takes more than 5 minutes. It seems like firewall/network issue, but it wasn’t happening in 6.5. I have a case opened with BO but so far no resoluion. We are on SP1 MHF1. We have so far tested this with SP2 and it seems to have resolved,but we are not ready to move to SP2 in production.
In case of IE6 by default internet explorers send/receive timeout is indefinite time.
In case of IE7 by default the internet explorers send/receive timeout is 30 sec. Thats why in case of IE7 we are getting the issue. We can not change this default send/receive timeout thru code in case of IE7.But we can modify the registry manually for the same.
Please refer following site for the description: support.microsoft.com/support/kb/articles/Q176/4/20.ASP Make the following registry changes in the registry. 1. Add a ReceiveTimeout DWORD value with a data value of ()*1000 in the following registry key: HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet Settings For example, if you want the timeout duration to be 8 minutes, set the ReceiveTimeout data value to 480000 (<480>*1000).
The IE 7 problem is when you run Webi reports, but i`m using deski to run the reports.
And my case a bit different from all above situations. When i run a query using a universe, some times it runs and some times i get this error.
I too had run into this issue. We have an F5 and if I bypassed it, then the queries worked. The F5 has two timeout settings, the first one had no effect. The second one, the TCP IP idle time had to be set to 60 minutes. This is both a security risk and uses F5 resources, so I have asked BO to enhance the product to keep alive the TCP session while running jobs.
Thanks for your reply.
Can you tell me how to set/check time out for F5.
Please make clear what do you mean by F5.
Also mine is a migration project, where the report works well in 6.5 and after migration it runs through scheduler and only problem is when i open the report in deski for manual refresh.
F5 is hardware that provides load balancing on the network. We have 4 Bus Obj servers. The users type in the URL which sends them to the F5, which then rotates among the 4 servers (if one server goes down it will bypass it). Our network team manages the hardware and had to reset the TCP/IP timeout specifically for our Business Objects URL. I hope this helps.
In case of IE6 by default internet explorers send/receive timeout is indefinite time.
In case of IE7 by default the internet explorers send/receive timeout is 30 sec. Thats why in case of IE7 we are getting the issue. We can not change this default send/receive timeout thru code in case of IE7.But we can modify the registry manually for the same.
Please refer following site for the description: support.microsoft.com/support/kb/articles/Q176/4/20.ASP Make the following registry changes in the registry. 1. Add a ReceiveTimeout DWORD value with a data value of ()*1000 in the following registry key: HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet Settings For example, if you want the timeout duration to be 8 minutes, set the ReceiveTimeout data value to 480000 (<480>*1000).
Error at executing long query that takes more than 30 minutes from Desktop
Intelligence (DeskI) 3-tier mode
Error: “Error during sql execution: (DA0003)” followed by “Exception: CS,
Job already in use”
Reproducing the Issue
Configure Java application (e.g. InfoViewApp, AnalyticalReporting) and
BusinessObjects Enterpirse servers’ session timeout settings not to expire
in less than 60 minutes.
Start DeskI 3-tier mode and run a query that takes more than 30
minutes.
When execution time reaches 30 minutes, DeskI gets the error.
Resolution
Edit \AnalyticalReporting\WEB-INF\classes\wstk_bridge.xml (Note
varies depending on Java application server).
Find string “”.
Find string “”, which corresponds end tag to the element found
at step 2.
Insert “<async_methods>” element like below (Note class name in <impl
…> element below is abbreviated. Do not edit actual class name in the
element).
I have a user who started getting this error recently. She is running Deski and gets the error within 30 seconds of refreshing the data. Other users running the same report the same way do not get the error. Using her profile on other work stations I do not get the error. Using my profile on her work station I get the error. I have re-installed BOXI 2 SP4 w/ Fix Pack 4.1 and removed all Oracle from her system. Any guidance on this?
I received this back from our corporate BO team:
Usually we get the error message “Error During SQL Execution: (DA0003) -
CS, Job already in use” in case of timeout problems with Internet
Explorer 7 (which is installed with Windows XP):
“By design, Internet Explorer imposes a time-out limit for the server
to return data. The time-out limit is five minutes for versions 4.0 and
4.01 and is 60 minutes for versions 5.x and 6. Also, the time-out limit
is 30 seconds for Windows Internet Explorer 7. As a result, Internet
Explorer does not wait endlessly for the server to come back with data
when the server has a problem.” (also refer to http://support.microsoft.com/kb/181050)
The BusinessObjects Desktop Intelligence client is connecting to the
server using an HTTP protocol which uses the network settings in the
Internet Explorer. Please also refer to the last chapter of http://knet2.int.kn/index.php?id=4387 (Increase Session Timeout Settings in Internet Explorer
In some cases it might happen that you receive a session timeout when refreshing a report in full client or infoview. In order to resolve this error please ask your local IT to increase the session timeout settings in Internet Explorer. This can be achieved by doing the following:
Open the windows registry editor: (Click START >>> RUN >>> REGEDIT)
Add a ReceiveTimeout DWORD value with a decimal data value of 3600000 in the following registry key:
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet Settings
This value sets the default timeout to sixty minutes in Internet Explorer.
For further details please click here to read corresponding support page at Microsoft Techsupport
) and adjust the ReceiveTimeout
parameter according to the instructions.
Probably it makes sense to forward this information to your
infrastructure team to migrate this out to our users.
What if this change don’t take effect - I have increased RecieveTimeout to 3600000 (decimal) but exactly after 30 minutes I get Job already in use error in 3-tier DeskI. Can anyone tell my why?
so any help would be greatly appreciated.
(BOB member since 2002-06-25)
(BOB member since 2007-04-09)
(BOB member since 2007-04-09)