I’ll be so glad if anyone can help me resolve my peculiar situation for resolving the above error?
I have ran the DESKI reports from various workstations and even directly on the BO Server and it still returns the same error "ERROR DURING SQL EXECUTION (DA0003). Details show EXCEPTION CS: JOB ALREADY IN USE.
I have scanned previous posted resolution on the forum for the error but the closest resolution to it was what was posted by Asnair on Oct 22nd 2007. It goes thus:
“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.”
My situation here is that I do not have any F5 hardware as I do not have a cluster so I do not know where and how to “Reset the TCP/IP timeout specifically for our Business Objects URL” as stated.
I have a single BO Server (On Windows 2003 Server) with 4 CPU that has its repository on an Oracle database server (On Unix).
The same error we got yesterday when we update the Universe and try to schedule the reports;Somehow the reports are not updating the changes in the universe automatically, so we opened the reports save it again and run the reports, then they are working fine.
Please refer to the following link for the solution.
this problem seems to be prevalent if you are using IE7 and the timeout problem. If you add a ReceiveTimeout DWORD with a new timer value in the registry. It works
We get the same error when using user defined objects (udo).
However the udo file has been migrated from 6.5 to Xi (by mearly copying from one folder to the next).
Reports work fine if not using udo’s.