rbServer Error
I get this error every once in a while and would like to know how to
code for the exception to terminate the rbServer application. Not
always with the same report.
Sometimes the rbServer will stop without an error or at least it is not
responding to the port.
Is it happening in the rbReportTemplateVolume where I could trap the error?
Thanks,
David C. Allen
-
2005-01-12T10:19:15.911
Processing request for report Report Files\Usage\Member Usage
by Contract Range EExternalException, External exception C0000006
seError
0
{AE38D431-FA58-417A-A8C0-0F869E492EE7}
-
2005-01-12T10:19:15.911
Session End
seInformation
0
{AE38D431-FA58-417A-A8C0-0F869E492EE7}
-
2005-01-12T10:19:15.921
External exception C0000006
seError
0
-
2005-01-12T10:19:15.941
RB Server Stopped
seInformation
0
-
code for the exception to terminate the rbServer application. Not
always with the same report.
Sometimes the rbServer will stop without an error or at least it is not
responding to the port.
Is it happening in the rbReportTemplateVolume where I could trap the error?
Thanks,
David C. Allen
-
2005-01-12T10:19:15.911
Processing request for report Report Files\Usage\Member Usage
by Contract Range EExternalException, External exception C0000006
seError
0
{AE38D431-FA58-417A-A8C0-0F869E492EE7}
-
2005-01-12T10:19:15.911
Session End
seInformation
0
{AE38D431-FA58-417A-A8C0-0F869E492EE7}
-
2005-01-12T10:19:15.921
External exception C0000006
seError
0
-
2005-01-12T10:19:15.941
RB Server Stopped
seInformation
0
-
This discussion has been closed.
Comments
According to the log, the error occurred while procession a request for the
report indicated by the following path...
Report Files\Usage\Member Usage by Contract Range
The exception thrown was...
EExternalException, External exception C0000006
Unfortunately that does not provide us with much information.
Try running the server application as a standard windows .exe - under the
Delphi debugger. Configure the debugger to break on Delphi exceptions. You
might also add RBuilder\Source to the library path.
--
Nard Moseley
Digital Metaphors Corporation
www.digital-metaphors.com
Best regards,
Nard Moseley
Digital Metaphors
www.digital-metaphors.com
everyone in awhile and not always with the same report. After the
server is re-started the report works just fine. So, I'm thinking that
something with the server after some time has passed. Sometimes the
same server will need to be re-start more than once in a day.
Since there are 4 servers using different ports, but the same area for
the temp files, could there be a problem with one of files already
having a name the server is trying to use? When using the
templateVolume to do a full report (not incremental), it will always get
an access violation when doing the same report with a different prompt
value. And this has to do with the temp file already existing.
I've boosted the BDE settings and made sure not much was running on
the box, so I've run out of areas that I can have an effect on the
servers. Just looking for where the server may run into problems so I
trap the exceptions and repair.
Dave
I recommend that you avoid using the BDE altogether.
-----------------------------------------------
Tech Tip: RB Server and the BDE
-----------------------------------------------
Question
--------
Why do I get the following error when accessing my report server with
several clients: "EDBEngineError, Insufficient memory for this operation"?
Answer:
-------
For simplicity, the RB Server demos use the BDE and paradox tables.
However, in actual use, the BDE is a poor choice for multi-thread server
applications. If you search Google Groups you can find many references to
this topic.
The BDE's legacy architecture was never designed to support running many
concurrent sessions on a single machine. Each BDE session requires too much
memory overhead. Depending upon your machine's resources and the
configuration of the BDE you will eventually run out memory when too many
client sessions are created on the server.
REcommendation from Mike Leftwich on our Server newsgroup:
-----------------------------------------------------------
Any time you run multiple simultaneous sessions of the BDE, you
need to bump up the SHAREDMEMSIZE setting in the BDE Administrator. The
default is 2048 (2MB), but you should bump it up to at least 4096. I keep
mine set at 8192. I also bump up my MAXBUFSIZE to 8192 and MEMSIZE to 16
(MB), but if you're low on memory I don't think these are absolutely
necessary. You can find these settings in the BDE Administrator on the
Configuration tab under System/INIT.
--
Nard Moseley
Digital Metaphors Corporation
www.digital-metaphors.com
Best regards,
Nard Moseley
Digital Metaphors
www.digital-metaphors.com