i’m having a desktop intelligence report (with 2 data providers, 1 freehand sql and a universe based one) that works perfectly fine. when i change the settings of the report to “refresh on open” and want to save the report, desktop intelligence crashes.
i am experiencing this problem on two machines with separate desktop intelligence installations, so i guess there’s a problem with the report.
the exception that is thrown is the infamous Unhandled Exception with Code: c0000005
1 processor x Family 15 Model 0 Stepping 0
Windows 2000 Workstation v5.1 build 2600 (S)
Physical Total/Avail: 1.047.788 Kb / 621.400 Kb
Temp directory C:\DOKUME~1\wadl\LOKALE~1\Temp\ (1 Kb available)
'Unknown' video card
1280 x 1024 in true color
------------------------------------------------------------------
Unhandled Exception
Code: c0000005
Description: EXCEPTION_ACCESS_VIOLATION
what seems strange to me is the low number of memory that’s available in the temp folder (“1 Kb available”). i am an administrator on the machine with no quotas, there are 20+ gb free on the hard disk.
any suggestions (except rebuilding the report from scratch)?
I tried the option of
refresh, get data, then turn on rfesh on open then save.
It was working fine. Then i made some changes to the report. added a graph to it. Now i want to simulate the same graph for another condition. NOw i copied the graph, pasted it and then tried to use filter using (Menu -> Format -> filters)
As soon as i click on Format from the Menu, UEE occurs.
We have had the same problem back to release 6.1a and BOBJ said it was a known bug. We ended up purging the data providers turning off the refresh when open and publishing empty, training the report viewer to hit refresh 1st thing.
Iam getting the same error. But i get the error when i click on Tools\Options even before i open the report. Also, if i log onto a different server, and click on Tools\Options, the dialog box is visible and working fine.
I assume that the installation is not a problem since the option is working for a different login.
When the Stack error is being displayed, copy the temporary folder path.
Clear all the contents in the temporary folder path and its parent and log in again.
Take a look at this item in the CHF file … Problem ID # ADAPT00576142. There is a bug that causes the crash when saving, after the data is purged from the data provider(s). That fix worked for me.
Where do i find this CHF file, or other infoe on the errror ADAPT00576142 ?
I get the same “Saving Error”.
1 processor x Family 15 Model 0 Stepping 0
Windows 2000 Server (Terminal Server) v5.0 build 2195 (S)
Physical Total/Avail: 2.097.151 Kb / 1.952.232 KbTemp directory C:\DOCUME~1\bhoeller\LOCALS~1\Temp\5\ (1 Kb available)
‘Unknown’ video card
1280 x 1024 with 65536 colors
When loggin in to DeskI please ensure to check wheter you want to connect to your server directly ({servername}) or via the J2EE Portal ({servername} (J2EE Portal)). The latter is usually set to default when calling DeskI from InfoView.
We recieved this error when refreshing a report and this solved the issue.
The same applies when you are missing free-hand SQL or Stored Procedures in the drop down for other data sources.
We are still getting this error directly from/in Deski (accessing Deski directly, NOT using Infoview).
Anyone else getting this error (“U n h a n d l e d E x c e p t i o n C o d e : c 0 0 0 0 0 0 5. E X C E P T I O N _ A C C E S S _ V I O L A T I O N” )??
I did try the workaround module, and it DID WORK!!
However, I have a couple questions regarding this workaround & temporary solution (for the Deski “Save as” aborting/crashing problem).
Question 1: In order to solve the “Save as” Abort problem, does the module have to be saved within EACH AND EVERY BO REPORT within the Repository??
If so, then, while this IS a workaround solution, this is also NOT a very practical one. As we have over 1500 Reports that are retrieved & used throughout our enterprise. This means I have to open 1500 Reports and save the module within each one individually. Umm, sorry but I don’t think so…
Question 2: Instead of doing the above (ie. WITHOUT having to manually open each and every Report in Repository to load/save this module), is there instead a way to have BOXI “automatically” load & run this module (in deski) for/in each newly opened deski session?
I just found another possible workaround option for the abort problem!!
When doing a “Save as”, once the dialog window pops up click on the “Options” button.
Once the “Options” window pops up, there’s a section toward the bottom of the window called “Options for current document”. Within this section there is a text box there called “Write Reservation Password:”.
Does anyone know the purpose of this text box OR has anyone tried using it? I’m thinking that maybe this textbox could be used to bypass the problem of a user being aborted due to him/her NOT having “Write” Rights to the Destination Root.
Has anyone tried or tested this yet (regarding the abort problem)??
(BOB member since 2005-03-15)
(BOB member since 2005-11-10)
(BOB member since 2006-03-15)
(BOB member since 2006-06-07)
(BOB member since 2004-08-23)
Umm, sorry but I don’t think so… 
(BOB member since 2006-10-03)