BusinessObjects Board

reporter error

building reports desktopintelligence
#1

When selecting universe in the BO reporter, I receive following error. Someone a clue?

1 processor x86 Family 15 Model 0 Stepping 0
Windows 2000 Workstation v5.1 build 2600 (Service Pack 2)
Physical Total/Avail: 1.039.852 Kb / 458.684 Kb
Temp directory C:\DOCUME~1\HR\LOCALS~1\Temp\ (8.370.800 Kb available)
‘???’ video card
1280 x 1024 in true color

Unhandled Exception
Code: c0000005
Description: EXCEPTION_ACCESS_VIOLATION

Call stack:

Module at 0x24260000: C:\Program Files\Business Objects\BusinessObjects Enterprise 6\bin\kagtux.dll v 65.10.0.1011 [French (France)]
address: 0x24280893
address: 0x2428168b
address: 0x242819f4
address: 0x24281cd2
address: 0x242686e0
[Moderator Edit – rest of dump , since it adds no value to the discussion]

keizersoz (BOB member since 2005-12-14)

#2

hello

No need to cut / past all dump of your error, or send it by attchment.

About you trouble, no miracle, which BO release are you using ? Have you checked your database / system /release are supported by BusinessObjects. Is it a particular computer or all one ?

bernard timbal :fr: (BOB member since 2003-05-26)

#3

Try deleting the local copy of the universe / .unw files of the universe you are trying to work with, on either the server or your PC.

I am 99.999% sure that it’s having trouble overwriting the universe that you want; that’s almost always the workaround.

You may not be able to delete it - sometimes a WIQT process will lock it up - you’ll have to kill WIQTs until it’s released.

Not sure the underlying cause; used to be that BO was trying to do a “partial import” and updating the file, not sure if that still holds.

B.

bdouglas :switzerland: (BOB member since 2002-08-29)

#4

I deleted the universe from:
-local_path and
-local_path\repository folder

and still it always appears again in local_path\repository folder. I just don’t get how this is possible?

Moreover I keep on getting same error

keizersoz (BOB member since 2005-12-14)

#5

I recommend doing a search on turning on Designer tracing* - see if you can trap the error that Designer is throwing, sometimes that’s the best way.

Good luck!
B.

  • involves bo_trace.ini and some environmental vars - my bo_trace.ini looks like this:

active = true;
importance = ‘<<’;
size = 100000;
keep = true;

bdouglas :switzerland: (BOB member since 2002-08-29)

#6

I recommend doing a Search using keyword c0000005 – you may find some past discussions and workarounds that might help you in this case.

Here’s one such past discussion.

Anita Craig :us: (BOB member since 2002-06-17)