Are you using both SQLNet v2.x and Net8 on the same DAS machine? I would
like to suggest you to isolate these two if you can…
-----Original Message-----
Hi all,
Oracle 8.0.5
DAS 4.1.2 CSP 14
Windows NT 4.0 w. 130 MB RAM
We are occasionally getting a Fatal Exception error (access
violation)
in BUSOBJ.EXE reported by Dr. Watson when running Doc Agent with the
above configuration. Shutting down DAS and restarting the system
seems to (temporarily) correct the problem, but this is obviously not
a great solution.
No, we do not.
However, I have heard from some others who say that 4.1.4 corrects
this problem. Have not tried it yet, though.
Jason Beard
-------------------------------------------
Are you using both SQLNet v2.x and Net8 on the same DAS machine? I would
like to suggest you to isolate these two if you can…
Oracle 8.0.5
DAS 4.1.2 CSP 14
Windows NT 4.0 w. 130 MB RAM
We are occasionally getting a Fatal Exception error (access
violation)
in BUSOBJ.EXE reported by Dr. Watson when running Doc Agent with the
above configuration. Shutting down DAS and restarting the system
seems to (temporarily) correct the problem, but this is obviously not
a great solution.
I just had the same file sharing problem with OBJECTS.LSI. 4.1.3 corrupted the file and I had to fall back and delete it and rename the OBJECTS.BAK to LSI and it fixed that problem (DAS error: CANNOT ACCESS SECURITY DOMAIN).
I have also installed 4.1.4 to fix the file sharing problem and the reports that collided with each other yesterday did not today. To me it looks like they fixed it. I would suggest getting off of 4.1.2 and going to 4.1.4.
However, I have heard from some others who say that 4.1.4 corrects
this problem. Have not tried it yet, though.
Jason Beard
-------------------------------------------
Are you using both SQLNet v2.x and Net8 on the same DAS machine? I would
like to suggest you to isolate these two if you can…
Oracle 8.0.5
DAS 4.1.2 CSP 14
Windows NT 4.0 w. 130 MB RAM
We are occasionally getting a Fatal Exception error (access
violation)
in BUSOBJ.EXE reported by Dr. Watson when running Doc Agent with the
above configuration. Shutting down DAS and restarting the system
seems to (temporarily) correct the problem, but this is obviously not
a great solution.
Jason,
You may want to consider not showing the Dr. Watson msg.(Dr. Watson
options). This will continue writing the errors in the log file, and
not creating a number of screens each one taking some amount of RAM,
eventually disabling the NTserver.
Out of curiosity would you like to share you DR.Watson log?
We had a similar problem, Reports ran OK on DAS, but the errors kept
on coming. Pointing to BO returning control to DAS.
good luck. daniel
btw. BusinessObjects tech support came out with nothing.
even after showing the program calling sequence.
Wonder if BO developers know.