ALLOC COUNT 1  Expected aaaa  Allocated bbbb  Ln: ccc ddddd=<p>This panic is raised by  <code class="ApiItem">RHeap::__DbgMarkCheck()</code>  and   <span class="stripedlink"><code class="ApiItem">User::__DbgMarkCheck()</code></span> when the current number of allocated heap cells is not as expected.  </p><p><code>aaa</code> is the expected number of heap cells.</p><p><code>  bbb</code> is the allocated number of heap cells.</p><p><code>  ccc</code> is a line number; typically the source statement line containing the call to <code>__DbgMarkCheck()</code>.</p><p><code>  ddddd</code> is a file name; typically the file containing the source statement containing the call to <code>__DbgMarkCheck()</code>.</p>

ALLOC: nnnnnnnn=<p>This panic is raised by the <code class="ApiItem">RHeap::__DbgMarkEnd()</code>  and <span class="stripedlink"><code class="ApiItem">User::__DbgMarkEnd()</code></span> when the number of heap cells at the current nested level is not as  expected.  </p><p>nnnnnnnn is the hexadecimal pointer to the first orphaned heap cell.</p>

CMdaAudioOutputStream 0=<p>An attempt was made to change the audio stream player's properties while still writing to the stream.</p>

CMdaAudioOutputStream 2=<p>Not currently used.</p>

CMdaAudioOutputStream 4=<p>An attempt was made to set the audio stream player's volume to an invalid value.</p>

CMdaAudioOutputStream 6=<p>An attempt was made to access the stream before opening it.</p>

CMdaAudioOutputStream 8=<p>An attempt was made to open the stream when it is already open.</p>

CMdaAudioOutputStream 10=<p>An attempt was made to set the client's priority to an invalid value.</p>

CMdaAudioOutputStream 12=<p><code>CMdaAudioOutputStream::Open()</code> was called with an incorrect audio package type&#0160;&#8212;  it must be of type <code>TMdaAudioDataSettings</code>.</p>

BAFL 1=<p><i>This panic is raised in debug builds only.</i></p><p>This panic is raised by <span class="stripedlink"><code class="ApiItem">RResourceFile::ReadL()</code></span>, when the length of the resource is greater than the maximum length of the target descriptor</p>

BAFL 2=<p>Out of range index passed to <code>RIncrMatcherBase::FirstMatchingIndex()</code></p>

BAFL 3=<p>Maximum length passed to <code>RTextBuf::SetMaxLengthL()</code> was &lt;=0</p>

BAFL 4=<p>This panic is raised by the <code>Read...()</code>  member functions and the <code>Advance()</code>  member function of <span class="stripedlink"><code class="ApiItem">TResourceReader</code></span>, when the current position  in the resource buffer is moved  beyond the end of the buffer.</p>

BAFL 5=<p>This panic is raised by <span class="stripedlink"><code class="ApiItem">TResourceReader::Rewind()</code></span>, when the current position  in the resource buffer is moved before the start of the buffer.</p>

BAFL 6=<p>Unused</p>

BAFL 7=<p>Unused</p>

BAFL 8=<p>Unused</p>

BAFL 9=<p>Unused</p>

BAFL 10=<p>Unused</p>

BAFL 11=<p>Unused</p>

BAFL 12=<p>Unused</p>

BAFL 13=<p>Unused</p>

BAFL 14=<p>No path specified in sound info passed to <code>CBaSystemSoundArray::SetSoundL()</code></p>

BAFL 15=<p><i>This panic is raised in debug builds only.</i></p><p>This panic is raised by <span class="stripedlink"><code class="ApiItem">TResourceReader::ReadTPtrC16()</code></span>, when it detects that the alignment of Unicode strings within the  resource is incorrect, i.e. the buffer is of an incorrect length for reading  a Unicode string.</p>

BAFL 16=<p>Unsupported old resource file format</p>

BAFL 17=<p>No system sound category set for new system sound</p>

BAFL 18=<p>Invalid system sound priority set</p>

BAFL 19=<p>NULL UID passed to <code>CBaNamedPlugins::IndexOfUid()</code></p>

BAFL 20=<p>Bad resource file format found when constructing a <code>CBaNamedPlugins</code> object.</p>

BAFL 21=<p>The array position at which the text representing the choice of no plug-in is to  be inserted, is invalid. The panic is raised by <code>CBaNamedPlugins::ConstructL()</code>.</p>

BAFL 22=<p>An invalid comparison algorithm or no comparison algorithm supplied when sorting the plug-in names in the implementation of <code>CBaNamedPlugins::ConstructL()</code>.</p>

BAFL 23=<p>Unused.</p>

BITGDI 1=<p>No graphics device specified for use with <code>CFbsBitGc</code></p>

BITGDI 2=<p>Unused</p>

BITGDI 3=<p>No font selected</p>

BITGDI 4=<p>Sprite cancelled when no sprite is set</p>

BITGDI 5=<p>Unused</p>

BITGDI 6=<p>Unused</p>

BITGDI 7=<p>Unused</p>

BITGDI 8=<p>Unused</p>

BITGDI 9=<p>Invalid display mode</p>

BITGDI 10=<p>Invalid clipping region</p>

BITGDI 11=<p>Invalid window handle</p>

BITGDI 12=<p>Invalid font</p>

BITGDI 13=<p>Invalid bitmap</p>

BITGDI 14=<p>Co-ordinates out of range</p>

BITGDI 15=<p>Unused</p>

BITGDI 16=<p>Bad parameter used while filling a polygon</p>

BITGDI 17=<p>Invalid zero-sized parameter</p>

BITGDI 18=<p>Unused</p>

BITGDI 19=<p>Unused</p>

C32-fault 0=<p>Failed to install active scheduler or error running the  scheduler.</p>

C32-fault 1=<p>Failed to create server</p>

C32-fault 2=<p>Failed to start server</p>

C32-fault 3=<p>Could not allocate a Clean Up Stack.</p>

C32-fault 4=<p>API or function call not implemented yet.</p>

C32-fault 5=<p>Reference counting error</p>

C32-fault 6=<p>NULL pointer passed to API.</p>

C32-fault 7=<p>Unable to allocate global timer, commonly caused by a memory  allocation failure.</p>

CESockIniData 0=<p>Section name exceeded maximum length</p>

CESockIniData 1=<p>Variable name exceeded maximum length</p>

CHWComm 0=<p>Bad descriptor passed by client.</p>

CHWComm 1=<p><code>cancel()</code> method called without calling the  respective API first. I.e. an attempt was made to cancel an operation that was  not started.</p>

CHWComm 2=<p>Incorrect usage of an API for the current DTE/DCE  role.</p>

CHWComm 3=<p>Internal error caused by the notification count being  negative.</p>

CInSock 0=<p>Connectionless socket used when connected type required</p>

CInSock 1=<p>Attempt to send or receive on socket already in use</p>

Clock-client 0=<p>Clock is already constructed</p>

Clock-client 1=<p>Clock is already constructed</p>

Clock-client 2=<p>Clock is already constructed</p>

Clock-client 3=<p>Clock is not full constructed</p>

Clock-client 4=<p>Clock is not full constructed</p>

Clock-client 5=<p>Clock is not full constructed</p>

Clock-client 6=<p>Clock is not full constructed</p>

Clock-client 7=<p>Clock is not full constructed</p>

Clock-client 8=<p>Clock is not full constructed</p>

Clock-client 9=<p>Clock is not full constructed</p>

Clock-client 10=<p>Clock is not full constructed</p>

Clock-client 11=<p>Clock is not full constructed</p>

Clock-client 12=<p>Clock is not full constructed</p>

Clock-client 13=<p>Clock is not full constructed</p>

Clock-client 14=<p>Clock is not full constructed</p>

Clock-client 15=<p>Clock is not full constructed</p>

Clock-client 16=<p>Clock is not full constructed</p>

Clock-client 17=<p>Incorrect number of additions</p>

Clock-client 18=<p>Incorrect number of additions</p>

Clock-client 20=<p>No more additions expected</p>

Clock-client 21=<p>Too few text sections</p>

Clock-client 22=<p>Too few hands</p>

Clock-client 23=<p>Too few hand features</p>

Clock-client 24=<p>Invalid rectangle parameters</p>

Clock-client 25=<p>Internal error</p>

Clock-client 26=<p>Internal error</p>

Clock-client 27=<p>Internal error</p>

Clock-client 28=<p>Internal error</p>

Clock-client 29=<p>Internal error</p>

Clock-client 30=<p>Internal error</p>

Clock-client 31=<p>Internal error</p>

Clock-client 32=<p>Internal error</p>

Clock-client 33=<p>Internal error</p>

Clock-client 34=<p>Internal error</p>

Clock-client 35=<p>Internal error</p>

Clock-client 36=<p>Internal error</p>

Clock-client 37=<p>Clock is not full constructed</p>

Clock-client 38=<p>Clock is not full constructed</p>

Clock-client 39=<p>Clock is not full constructed</p>

Clock-client 44=<p>Internal error</p>

Clock-client 45=<p>Internal error</p>

Clock-client 46=<p>Internal error</p>

CommsDbServer 1=<p><code>CCommsDbTableView::InsertRecord()</code> called when  <code>InsertRecord()</code> or <code>UpdateRecord()</code> has already been  made.</p>

CommsDbServer 2=<p><code>CCommsDbTableView::UpdateRecord()</code> called when  <code>InsertRecord()</code> or <code>UpdateRecord()</code> has already been  made.</p>

CommsDbServer 3=<p><code>CCommsDbTableView::DeleteRecord()</code> called when a  previous call to <code>InsertRecord()</code> or <code>UpdateRecord()</code> has  been made</p>

CommsDbServer 4=<p><code>CCommsDbTableView::PutRecordChanges()</code> called  without previous call to <code>InsertRecord()</code> or  <code>UpdateRecord()</code></p>

CommsDbServer 5=<p><code>CCommsDbTableView::CancelRecordChanges()</code> called  without previous call to <code>InsertRecord()</code> or  <code>UpdateRecord()</code></p>

CommsDbServer 6=<p><code>CCommsDbTableView::GotoFirstRecord()</code> called while  an operation involved in inserting or updating a record is still outstanding,  or when the view has been closed.</p>

CommsDbServer 7=<p><code>CCommsDbTableView::GotoNextRecord()</code> called while  an operation involved in inserting or updating a record is still outstanding,  or when the view has been closed.</p>

CommsDbServer 8=<p><code>CCommsDbTableView::GotoPreviousRecord()</code> called  while an operation involved in inserting or updating a record is still  outstanding, or when the view has been closed.</p>

CommsDbServer 10=<p>Attempt made to read from a column before either  <code>PutRecordChanges()</code> or <code>CancelRecordChanges()</code> has been  called to complete a record insertion or update  operation.</p>

CommsDbServer 12=<p>Attempt is made to write to a column without calling  <code>CCommsDbTableView::InsertRecord()</code> or  <code>CCommsDbTableView::UpdateRecord()</code></p>

CommsDbServer 13=<p>Attempt to write to table ID column with  <code>CCommsDbTableView::WriteUintL()</code>.</p>

CommsDbServer 14=<p><code>CCommDbOverrideSettings::GetLongDesOverride()</code>  called with too small <code>aValue</code> buffer.</p>

Comm server 0=<p>Write request made when request already in progress.</p>

Comm server 1=<p>Read request made when request already in progress.</p>

Comm server 2=<p>Break request made when request already in progress.</p>

Comm server 3=<p>Invalid port handle passed by client.</p>

Comm server 4=<p>Bad descriptor passed by client.</p>

Comm server 5=<p><code>RComm::SetConfig()</code> call made when another request  already in progress.</p>

Comm server 6=<p><code>RComm::SetSignals()</code> call made when another request  already in progress.</p>

Comm server 7=<p><code>RComm::ResetBuffers()</code> call made when another  request already in progress.</p>

Comm server 8=<p><code>RComm::ReceiveBufferLength()</code> call made when  another request already in progress.</p>

Comm server 9=<p>Cannot have two outstanding  <code>RComm::NotifySignalChange()</code> requests from the same client.</p>

Comm server 10=<p>Cannot have two outstanding  <code>RComm::NotifyFlowControlChange()</code> requests from the same  client.</p>

Comm server 11=<p>Cannot have two outstanding  <code>RComm::NotifyConfigChange()</code> requests from the same client.</p>

Comm server 12=<p>Cannot have two outstanding <code>RComm::NotifyBreak()</code>  requests from the same client.</p>

Comm server 13=<p>Cannot have two outstanding  <code>RComm::NotifyDataAvailable()</code> requests from the same client.</p>

Comm server 14=<p>Cannot have two outstanding  <code>RComm::NotifyOutputEmpty()</code> requests from the same client. </p>

Comm server 15=<p>Thread size is negative.</p>

Comm server 16=<p>Minimum heap size is too small.</p>

Comm server 17=<p>Maximum heap size is less than minimum heap size.</p>

Comm server 18=<p>Wrong client session for set access request.</p>

Comm server 19=<p>Client must close object before setting comm access.</p>

CONARC 0=<p><code>CCnaScanningConverterFinder::NextL()</code> called before <code>FindAllConvL()</code></p>

CONARC 1=<p>Attempt to scan unknown drive</p>

CONARC 2=<p>File error while attempting to restore converter information </p>

CONARC 3=<p><code>CCnaScanningCnfFinder::NextL()</code> called before <code>FindAllCnfL()</code></p>

CONARC 4=<p>Unused</p>

CONE 1=<p>  Environment start up error   </p>

CONE 2=<p>  Environment already exists   </p>

CONE 3=<p>  App UI cannot be created   </p>

CONE 4=<p>  Control cannot be found in the control stack   </p>

CONE 5=<p>  Environment caught unexpected leave   </p>

CONE 6=<p>  Non-leaving function CCoeControl::Draw() leaves during a redraw  operation  </p>

CONE 7=<p>  Environment found file server resources had not been freed   </p>

CONE 8=<p>  Environment found window server resources had not been freed   </p>

CONE 9=<p>  Environment failed to handle window server event   </p>

CONE 10=<p>  The control already owns a window   </p>

CONE 11=<p>  The control cannot close the window as it does not own one   </p>

CONE 12=<p>  <code>CCoeControl::ComponentControl()</code> has been called, but  the control is not a container   </p>

CONE 13=<p>  Environment cannot find the resource file in order to delete it   </p>

CONE 14=<p>  Environment cannot find the specified resource in any resource file  </p>

CONE 15=<p>  A NULL resource file name was passed to  <code>CCoeEnv::AddResourceFileL()</code>  </p>

CONE 16=<p>  Resource is wrong length to be read as Unicode string   </p>

CONE 17=<p>  Internal control set up error   </p>

CONE 18=<p>  Attempted to add NULL observer   </p>

CONE 19=<p>  Attempted to remove NULL observer   </p>

CONE 20=<p>  Attempted to set up NULL FEP   </p>

CONE 21=<p>  Observer has already been added   </p>

CONE 22=<p>  Unused   </p>

CONE 23=<p>  Unused   </p>

CONE 24=<p>  FEP could not be loaded due to set-up problem   </p>

CONE 25=<p>  Unused   </p>

CONE 26=<p>  Unused   </p>

CONE 27=<p>  NULL GC passed to <code>CCoeEnv::SwapSystemGc()</code>  </p>

CONE 28=<p>  Resource file has not been freed   </p>

CONE 29=<p>  No view server session present   </p>

CONE 30=<p>  Specified view could not be found   </p>

CONE 31=<p>  NULL UID passed to <code>CCoeStatic::CCoeStatic()</code>  </p>

CONE 32=<p>  Duplicate UID passed to <code>CCoeStatic::CCoeStatic()</code>  </p>

CONE 33=<p>  Attempt to use <code>CoeSoundPlayer</code> without an environment   </p>

CONE 34=<p>  Unused   </p>

CONE 35=<p>  Unused   </p>

CONE 36=<p>  Open handles were found during application shutdown   </p>

CONE 37=<p>  Unexpected view server event   </p>

CONE 38=<p>  View observer not found   </p>

CONE 39=<p>  View notification observer already exists   </p>

CONE 40=<p>  Embedded app UI is not NULL   </p>

CONE 41=<p>  Embedded app UI is not NULL   </p>

CONE 42=<p>  Embedded app UI is not NULL   </p>

CONE 43=<p>  Embedded app UI is not NULL   </p>

CONE 44=<p>  Control being destroyed is still on the control stack   </p>

CONE 45=<p>  Focus observer notification is not pending   </p>

CONE 46=<p>  The handle for the current Window Server Redraw event is invalid   </p>

CONE 47=<p>  No longer used   </p>

CONE 48=<p>  No longer used   </p>

CONE 49=<p>  The control parent-child hierarchy has become circular   </p>

CONE 50=<p>  A control's parent has been set to something other than NULL or  itself prior to being added to the control stack   </p>

CONE 51=<p>  Two controls with the same ID exist   </p>

CONE 52=<p>  An attempt was made to add an item to a control array which does  not exist   </p>

CONE 53=<p>  No longer used   </p>

CONE 54=<p>  No longer used   </p>

CONE 55=<p>  No longer used   </p>

CONE 56=<p>  No longer used   </p>

CONE 57=<p>  An error occured while notifying the central repository of a FEP  change   </p>

E32USER-CBase 1=<p>  This panic is raised by the <code>Set()</code> member function of  <code>CAsyncCallBack</code>, if this active object is already active when the  function is called.   </p>

E32USER-CBase 2=<p>  <i>This panic is raised in debug builds only.</i>  </p>  <p>  This panic is raised by the <code>Call()</code> member function of  <code>CAsyncOneShot</code> if the active object has not already been added to  the active scheduler.   </p>

E32USER-CBase 3=<p>  This panic is raised during construction of a dynamic buffer (a  <span class="stripedlink"><code class="ApiItem">CBufFlat</code></span> or a <span class="stripedlink"><code class="ApiItem">CBufSeg</code></span>) when the value  of the granularity passed to the constructors is negative.   </p>

E32USER-CBase 4=<p>  This panic is raised when reading from a dynamic buffer (a  <span class="stripedlink"><code class="ApiItem">CBufFlat</code></span> or a <span class="stripedlink"><code class="ApiItem">CBufSeg</code></span>) using the  <code>Read()</code> member function. It is caused by attempting to read beyond  the end of the buffer.   </p>

E32USER-CBase 5=<p>  This panic is raised when writing to a dynamic buffer (a  <span class="stripedlink"><code class="ApiItem">CBufFlat</code></span> or a <span class="stripedlink"><code class="ApiItem">CBufSeg</code></span>) using the  <code>Write()</code> member function. It is caused by attempting to write  beyond the end of the buffer.   </p>

E32USER-CBase 6=<p>  This panic is raised when reading from a dynamic buffer (a  <span class="stripedlink"><code class="ApiItem">CBufFlat</code></span> or a <span class="stripedlink"><code class="ApiItem">CBufSeg</code></span>) using the  <code>Read()</code> member function. It is caused by specifying a negative  length for the amount of data to be read   </p>

E32USER-CBase 7=<p>  This panic is raised when writing to a dynamic buffer (a  <span class="stripedlink"><code class="ApiItem">CBufFlat</code></span> or a <span class="stripedlink"><code class="ApiItem">CBufSeg</code></span>) using the  <code>Write()</code> member function. It is caused by specifying a negative  length for the amount of data to be written.   </p>

E32USER-CBase 8=<p>  This panic is raised when inserting data into a dynamic buffer (a  <span class="stripedlink"><code class="ApiItem">CBufFlat</code></span> or a <span class="stripedlink"><code class="ApiItem">CBufSeg</code></span>) using the  <code>InsertL()</code> member function or when inserting an uninitialized  region into the dynamic buffer using the <code>ExpandL()</code> member  function. It is caused by passing a negative length value to these functions.   </p>

E32USER-CBase 9=<p>  This panic is raised when inserting data into a dynamic buffer (a  <span class="stripedlink"><code class="ApiItem">CBufFlat</code></span> or a <span class="stripedlink"><code class="ApiItem">CBufSeg</code></span>) using the  <code>InsertL()</code> member function. It is caused when the variant of  <code>InsertL()</code> which takes a pointer to <code>TAny</code>, is passed a  NULL pointer value.   </p>

E32USER-CBase 10=<p>  This panic is raised when specifying the minimum amount of space  which a flat dynamic buffer (a <span class="stripedlink"><code class="ApiItem">CBufFlat</code></span>) should occupy  using the <code>SetReserveL()</code> member function. It is caused when the  size value passed to the function is negative.   </p>

E32USER-CBase 11=<p>  This panic is raised when specifying the minimum amount of space  which a flat dynamic buffer (a <span class="stripedlink"><code class="ApiItem">CBufFlat</code></span>) should occupy  using the <code>SetReserveL()</code> member function. It is caused when the  size value passed to the function is less than the current size of the buffer.   </p>

E32USER-CBase 12=<p>  This panic is raised by the <code>Delete()</code>,  <code>Ptr()</code>, <code>BackPtr()</code> member functions of a flat dynamic  buffer (a <span class="stripedlink"><code class="ApiItem">CBufFlat</code></span>); the panic can also be raised by  <code>InsertL()</code> and <code>ExpandL()</code>. It is caused when the  position value passed to these functions is either negative or represents a  position beyond the end of the current buffer.   </p>

E32USER-CBase 13=<p>  This panic is raised by the <code>Delete()</code> member function  of a flat dynamic buffer (a <span class="stripedlink"><code class="ApiItem">CBufFlat</code></span>). It is caused when  the combination of position and length values passed to the function implies an  attempt to delete data beyond the end of the flat buffer.   </p>

E32USER-CBase 14=<p>  This panic is raised by the <code>Delete()</code>,  <code>Ptr()</code>, <code>BackPtr()</code> member functions of a segmented  dynamic buffer (a <span class="stripedlink"><code class="ApiItem">CBufSeg</code></span>); the panic can also be raised  by <code>InsertL()</code> and <code>ExpandL()</code>. It is caused when the  position value passed to these functions is either negative or represents a  position beyond the end of the current buffer.   </p>

E32USER-CBase 15=<p>  This panic is raised by the Delete() member function of a segmented  dynamic buffer (a <span class="stripedlink"><code class="ApiItem">CBufSeg</code></span>). It is caused when the  combination of position and length values passed to the function implies an  attempt to delete data beyond the end of the segmented buffer.   </p>

E32USER-CBase 16=<p>  <i>This panic is raised in debug builds only.</i>  </p>  <p>  This panic is raised by the <code>InsertL()</code>,  <code>Delete()</code>, <code>Ptr()</code> and <code>BackPtr()</code> member  functions as implemented for segmented buffers (<span class="stripedlink"><code class="ApiItem">CBufSeg</code></span>),  when the offset within a segment, where data is to be inserted or removed, is  greater than the buffer granularity.   </p>

E32USER-CBase 17=<p>  This panic is raised by the constructors of arrays of fixed length  objects as represented, for example, by the classes  <span class="stripedlink"><code class="ApiItem">CArrayFixFlat</code></span>, <span class="stripedlink"><code class="ApiItem">CArrayFixSeg</code></span> and  <code class="ApiItem">CArrayFixFlat&lt;TAny&gt;</code>. It is caused when the record  length is either negative or zero.   </p>  <p>  The record length is either explicitly specified as in the case of  the <code class="ApiItem">CArrayFixFlat&lt;TAny&gt;</code> class or is implied by the  length of the template class as in the case of the  <span class="stripedlink"><code class="ApiItem">CArrayFixFlat</code></span> class.   </p>

E32USER-CBase 18=<p>  This panic is raised by the constructors of arrays of fixed length  objects as represented, for example, by the classes:  <span class="stripedlink"><code class="ApiItem">CArrayFixFlat</code></span> and <span class="stripedlink"><code class="ApiItem">CArrayFixSeg</code></span>. It is  caused when the granularity passed to the constructors is either negative or  zero.   </p>

E32USER-CBase 19=<p>  This panic is raised by the constructors of arrays of variable  length objects as represented, for example, by the classes:  <span class="stripedlink"><code class="ApiItem">CArrayVarFlat</code></span> and <span class="stripedlink"><code class="ApiItem">CArrayVarSeg</code></span>. It is  caused when the granularity passed to the constructors is either negative or  zero.   </p>

E32USER-CBase 20=<p>  This panic is raised by the constructors of packed arrays as  represented, for example, by the class <span class="stripedlink"><code class="ApiItem">CArrayPakFlat</code></span>. It  is caused when the granularity passed to the constructors is either negative or  zero.   </p>

E32USER-CBase 21=<p>  This panic is raised by any operation which accesses an element of  an array by explicit reference to an index number, for example, the  <code>Delete()</code>, <code>InsertL()</code> and <code>At()</code> member  functions or the operator <code>Operator[]</code>. It is caused by specifying  an index value which is either negative or is greater than or equal to the  number of objects currently within the array.   </p>

E32USER-CBase 22=<p>  This panic is raised when deleting contiguous elements from an  array of fixed length objects (derived from <span class="stripedlink"><code class="ApiItem">CArrayFixBase</code></span>)  using the <code>Delete()</code> member function. It is caused by specifying the  number of contiguous elements as a zero or negative value.   </p>

E32USER-CBase 23=<p>  This panic is raised when inserting contiguous elements into an  array of fixed length objects (derived from <span class="stripedlink"><code class="ApiItem">CArrayFixBase</code></span>)  using the <code>InsertL()</code> member function. It is caused by specifying  the number of contiguous elements as a zero or negative value.   </p>

E32USER-CBase 24=<p>  This panic is raised when resizing an array of fixed length objects  (derived from <span class="stripedlink"><code class="ApiItem">CArrayFixBase</code></span>) using the  <code>ResizeL()</code> member function. It is caused by specifying the number  of contiguous elements as a zero or negative value.   </p>

E32USER-CBase 25=<p>  This panic is raised when deleting contiguous elements from an  array of variable length objects (derived from  <span class="stripedlink"><code class="ApiItem">CArrayVarBase</code></span>) using the <code>Delete()</code> member  function. It is caused by specifying the number of contiguous elements as a  zero or negative value.   </p>

E32USER-CBase 26=<p>  This panic is raised when deleting contiguous elements from a  packed array (derived from <span class="stripedlink"><code class="ApiItem">CArrayPakBase</code></span>) using the  <code>Delete()</code> member function. It is caused by specifying the number of  contiguous elements as a zero or negative value.   </p>

E32USER-CBase 27=<p>  This panic is raised when reserving space in flat arrays of fixed  length objects, (the  <span class="stripedlink"><code class="ApiItem">CArrayFixFlat</code></span>,<code class="ApiItem">CArrayFixFlat&lt;TAny&gt;</code>  and <span class="stripedlink"><code class="ApiItem">CArrayPtrFlat</code></span> classes ) using the  <code>SetReserveL()</code> member function. It is caused by specifying the  number of elements, for which space is to be reserved, as less than the current  number of elements in the array.   </p>

E32USER-CBase 28=<p>  This panic is raised when inserting or appending replicated  elements to the arrays of fixed length objects  <span class="stripedlink"><code class="ApiItem">CArrayFixFlat</code></span> and <span class="stripedlink"><code class="ApiItem">CArrayFixSeg</code></span> using  the <code>InsertL()</code> or <code>AppendL()</code> functions. It is caused by  specifying the number of replicas as negative or zero.   </p>

E32USER-CBase 29=<p>  This panic is raised when deleting elements from a fixed length,  variable length or packed array (derived from  <span class="stripedlink"><code class="ApiItem">CArrayFixBase</code></span>, <span class="stripedlink"><code class="ApiItem">CArrayVarBase</code></span> and  <span class="stripedlink"><code class="ApiItem">CArrayPakBase</code></span>) using the <code>Delete()</code> function.  It is caused when the specification of the position of the first element to be  deleted and the number of contiguous elements to be deleted refers to elements  which are outside the bounds of the array.   </p>

E32USER-CBase 30=<p>  This panic is raised when inserting into, appending onto, expanding  or extending a variable length array or a packed array (i.e. arrays derived  from <span class="stripedlink"><code class="ApiItem">CArrayVar</code></span> or <span class="stripedlink"><code class="ApiItem">CArrayPak</code></span>) using  the <code>InsertL()</code>, <code>AppendL()</code>, <code>ExpandL()</code> or  <code>ExtendL()</code> functions respectively. It is caused by specifying the  length of the element as a negative value.   </p>

E32USER-CBase 33=<p>  This panic is raised by the destructor of a  <span class="stripedlink"><code class="ApiItem">CObject</code></span>. It is caused, if an attempt is made to delete the  <span class="stripedlink"><code class="ApiItem">CObject</code></span> when the reference count is not zero.   </p>

E32USER-CBase 34=<p>  This panic is raised by the <code>Close()</code> member function of  a <span class="stripedlink"><code class="ApiItem">CObject</code></span>. It is caused, if the reference count is  negative.   </p>

E32USER-CBase 35=<p>  This panic is raised by the <code>Remove()</code> member function  of an object container, a <span class="stripedlink"><code class="ApiItem">CObjectCon</code></span>. It is caused when  the <span class="stripedlink"><code class="ApiItem">CObject</code></span> to be removed from the container is not  contained by the container.   </p>

E32USER-CBase 36=<p>  This panic is raised by the <code>Remove()</code> member function  of a container index, a <span class="stripedlink"><code class="ApiItem">CObjectConIx</code></span>. It is caused when  the object container, a <span class="stripedlink"><code class="ApiItem">CObjectCon</code></span>, to be removed from the  index is not contained by the index.   </p>

E32USER-CBase 37=<p>  This panic is raised by the <code>Remove()</code> member function  of an object index, a <span class="stripedlink"><code class="ApiItem">CObjectIx</code></span>. It is caused when the  handle passed to the <code>Remove()</code> function does not represent a  <span class="stripedlink"><code class="ApiItem">CObject</code></span> known to the object index.   </p>

E32USER-CBase 38=<p>  This panic is raised by the <code>At()</code>,  <code>FindByName()</code> and <code>FindByFullName()</code> member functions of  an object container, a <span class="stripedlink"><code class="ApiItem">CObjectCon</code></span>. It is caused when the  unique ID as derived from the handle is not the same as the unique ID held by  the object container.   </p>

E32USER-CBase 39=<p>  This panic is raised by the <code>At()</code> member function of an  object container, a <span class="stripedlink"><code class="ApiItem">CObjectCon</code></span>. It is caused when the  index represented by the handle is outside the permitted range. In effect, the  handle is bad.   </p>

E32USER-CBase 40=<p>  This panic is raised by the destructor of an active object, a  <span class="stripedlink"><code class="ApiItem">CActive</code></span>. It is caused by an attempt to delete the active  object while it still has a request outstanding.   </p>

E32USER-CBase 41=<p>  This panic is raised by the <code>Add()</code> member function of  an active scheduler, a <span class="stripedlink"><code class="ApiItem">CActiveScheduler</code></span>. It is caused by  an attempt to add an active object to the active scheduler when it has already  been added to the active scheduler   </p>

E32USER-CBase 42=<p>  This panic is raised by the <code>SetActive()</code> member  function of an active object, a <span class="stripedlink"><code class="ApiItem">CActive</code></span>. It is caused by  an attempt to flag the active object as active when it is already active, i.e.  a request is still outstanding.   </p>

E32USER-CBase 43=<p>  This panic is raised by the <code>Install()</code> member function  of an active scheduler, a <span class="stripedlink"><code class="ApiItem">CActiveScheduler</code></span>. It is caused  by attempting to install this active scheduler as the current active scheduler  when there is already a current active scheduler; i.e. an active scheduler has  already been installed.   </p>

E32USER-CBase 44=<p>  This panic is raised by calls to the <code>Start()</code>,  <code>Stop()</code> and <code>Add()</code> member functions of an active  scheduler, a <span class="stripedlink"><code class="ApiItem">CActiveScheduler</code></span> when the thread does not  have an installed active scheduler.  </p>

E32USER-CBase 45=<p>  This panic is raised by the <code>Stop()</code> member function of  an active scheduler, a <span class="stripedlink"><code class="ApiItem">CActiveScheduler</code></span>. Calling  <code>Stop()</code> terminates the wait loop started by the most recent call to  <code>Start()</code>. The panic is caused by a call to <code>Stop()</code>  which is not matched by a corresponding call to <code>Start()</code>.   </p>

E32USER-CBase 46=<p>  This panic is raised by an active scheduler, a  <span class="stripedlink"><code class="ApiItem">CActiveScheduler</code></span>. It is caused by a stray signal.   </p>

E32USER-CBase 47=<p>  This panic is raised by the <code>Error()</code> virtual member  function of an active scheduler, a <span class="stripedlink"><code class="ApiItem">CActiveScheduler</code></span>. This  function is called when an active object&#8217;s <code>RunL()</code> function leaves.  Applications always replace the <code>Error()</code> function in a class  derived from <code>CActiveScheduler</code>; the default behaviour provided by  <code>CActiveScheduler</code> raises this panic.   </p>

E32USER-CBase 48=<p>  This panic is raised by the <code>Add()</code> member function of  an active scheduler, a <span class="stripedlink"><code class="ApiItem">CActiveScheduler</code></span>, when a NULL  pointer is passed to the function.   </p>

E32USER-CBase 49=<p>  This panic is raised by the <code>SetActive()</code> and  <code>Deque()</code> member functions of an active object, a  <span class="stripedlink"><code class="ApiItem">CActive</code></span>. It is raised if the active object has not been  added to the active scheduler.   </p>

E32USER-CBase 50=<p>  This panic is raised by the <code>SetPriority()</code> member  function of an active object, a <span class="stripedlink"><code class="ApiItem">CActive</code></span>. It is caused by  an attempt to change the priority of the active object while it is active, i.e.  while a request is outstanding).   </p>

E32USER-CBase 51=<p>  This panic is raised by the <code>At()</code>, <code>After()</code>  and <code>Lock()</code> member functions of the <span class="stripedlink"><code class="ApiItem">CTimer</code></span>  active object. It is caused by an attempt to request a timer event when the  <code>CTimer</code> active object has not been added to the active scheduler.   </p>

E32USER-CBase 52=<p>  This panic is raised by the <code>Start()</code> member function of  the periodic timer active object, a <span class="stripedlink"><code class="ApiItem">CPeriodic</code></span>, when a  negative time interval is passed to the function.   </p>

E32USER-CBase 53=<p>  This panic is raised by the <code>Start()</code> member function of  the periodic timer active object, a <span class="stripedlink"><code class="ApiItem">CPeriodic</code></span>, when a  negative delay time interval is passed to the function.   </p>

E32USER-CBase 54=<p>  This panic is raised by the <code>RunL()</code> member function of  the <code class="ApiItem">CServer</code> active object base class responsible for  handling asynchronous requests from a client thread when the client passes a  negative function code in <code class="ApiItem">RMessage</code>. The only negative  values permitted are RMessage::EConnect and RMessage::EDisConnect.   </p>

E32USER-CBase 55=<p>  This panic is raised by the <code>Start()</code> member function of  the <code class="ApiItem">CServer</code> active object base class responsible for  handling asynchronous requests from a client thread. It is caused by the server  having no name.   </p>

E32USER-CBase 56=<p>  This panic is raised by the <code>New()</code> and  <code>NewL()</code> member functions of <code>CBitMapAllocator</code> when a  negative or zero size is passed to them.   </p>

E32USER-CBase 57=<p>  This panic is raised by the <code>Free(TInt aPos)</code> member  function of <code>CBitMapAllocator</code> when a position value is passed which  is out of bounds.   </p>

E32USER-CBase 58=<p>  This panic is raised by the <code>IsFree(TInt aPos)</code> member  function of <code>CBitMapAllocator</code> when a position value is passed which  is out of bounds.   </p>

E32USER-CBase 59=<p>  This panic is raised by the <code>AllocFromTopFrom(TInt  aPos)</code> member function of <code>CBitMapAllocator</code> when a position  value is passed which is out of bounds.   </p>

E32USER-CBase 62=<p>  This panic is raised by the <code>AllocAt()</code> member function  of <code>CBitMapAllocator</code> when the implied position has already been  allocated.   </p>

E32USER-CBase 63=<p>  This panic is raised as a result of a call to the  <code>Pop()</code> and <code>PopAndDestroy()</code> static member functions of  the <span class="stripedlink"><code class="ApiItem">CleanupStack</code></span> class. The panic occurs when TRAPs have  been nested and an attempt is made to pop too many items from the cleanup stack  for the current nest level.   </p>

E32USER-CBase 64=<p>  This panic is raised as a result of a call to the  <code>Pop()</code> and <code>PopAndDestroy()</code> static member functions of  the <span class="stripedlink"><code class="ApiItem">CleanupStack</code></span> class. The panic occurs when attempt is  made to pop more items from the cleanup stack than are on the cleanup stack.   </p>

E32USER-CBase 65=<p>  The panic is raised as a result of a call to the <code>Pop()</code>  and <code>PopAndDestroy()</code> static member functions of the  <code>CleanupStack</code> class. The panic occurs when an attempt is made to  pop more items from the cleanup stack than are on the cleanup stack.   </p>

E32USER-CBase 66=<p>  This panic is raised if an attempt is being made to insert a  cleanup item into a position on the cleanup stack reserved for marking the  current <span class="stripedlink"><code class="ApiItem">TRAP</code></span> nest level. In practice this  error occurs if the call to <span class="stripedlink"><code class="ApiItem">CleanupStack::PushL()</code></span> happens  when there has been no call to <code>TRAP()</code>.   </p>

E32USER-CBase 67=<p>  This panic is raised when building a <code>TCleanupStackItem</code>  which is to be added to the cleanup stack. The building of the  <code>TCleanupStackItem</code> needs a <span class="stripedlink"><code class="ApiItem">TCleanupItem</code></span> and  this has been constructed with a NULL cleanup operation (a  <span class="stripedlink"><code class="ApiItem">TCleanupOperation</code></span>).   </p>

E32USER-CBase 68=<p>  This panic is raised if there are no free slots available on the  cleanup stack to insert a cleanup item   </p>

E32USER-CBase 69=<p>  This panic is raised if no trap handler has been installed. In  practice, this occurs if <span class="stripedlink"><code class="ApiItem">CTrapCleanup</code></span><code>::New()</code>  has not been called before using the cleanup stack.   </p>

E32USER-CBase 70=<p>  This panic is raised as a result of a call to the versions of the  <code>Pop()</code> and <code>PopAndDestroy()</code> static member functions of  the <span class="stripedlink"><code class="ApiItem">CleanupStack</code></span> class which take an explicit count of the  items to be popped. The panic is caused by passing a negative value for the  number of items to be popped.   </p>

E32USER-CBase 71=<p>  This panic is raised when <span class="stripedlink"><code class="ApiItem">TRAP</code></span>s have been nested and an attempt is made to  exit from a <span class="stripedlink"><code class="ApiItem">TRAP</code></span> nest level before all the  cleanup items belonging to that level have been popped off the cleanup stack.   </p>  <p>  There must be the same number of items on the cleanup stack on  entering a <span class="stripedlink"><code class="ApiItem">TRAP</code></span> harness as there is on  exiting. In other words, anything that is pushed onto the cleanup stack inside  a <span class="stripedlink"><code class="ApiItem">TRAP</code></span> harness must be popped off before  leaving the harness.   </p>  <p>  For example, the following code avoids this panic when  <code>FooLC()</code> does not leave, by explicitly popping <code>pointer</code>  before the end of the harness:   </p>  <p class="CodeBlock"><code>TRAPD(error,&nbsp;pointer&nbsp;=&nbsp;FooLC();&nbsp;CleanupStack::Pop(pointer));</code></p>  <p>  See also <span class="stripedlink">How to use TRAP</span>.   </p>

E32USER-CBase 72=<p>  This panic is raised by the constructor of the circular buffer base  class, a <span class="stripedlink"><code class="ApiItem">CCirBufBase</code></span>, when the size value passed is zero  or negative.   </p>

E32USER-CBase 73=<p>  This panic is raised by a call to the <code>SetLengthL()</code>  member function of of the circular buffer base class, a  <span class="stripedlink"><code class="ApiItem">CCirBufBase</code></span>, by passing a length value which is zero or  negative.   </p>

E32USER-CBase 74=<p>  This panic is raised by a call to the <code>Add()</code> member  function of a circular buffer, a <span class="stripedlink"><code class="ApiItem">CCirBuf</code></span> when the pointer  to the item to be added is NULL.   </p>

E32USER-CBase 75=<p>  This panic is raised by a call to the <code>Add()</code> member  function of a circular buffer, a <span class="stripedlink"><code class="ApiItem">CCirBuf</code></span> when the number  of items to be added is zero or negative   </p>

E32USER-CBase 76=<p>  This panic is raised by a call to the <code>Remove()</code> member  function of a circular buffer, a <span class="stripedlink"><code class="ApiItem">CCirBuf</code></span> when the number  of items to be removed is zero or negative.   </p>

E32USER-CBase 89=<p>  Introduced in 6.0: This panic is raised by call to the  <code>Replace()</code> member function of <span class="stripedlink"><code class="ApiItem">CActiveScheduler</code></span>  when the replacement active scheduler is the same as the existing active  scheduler.   </p>

E32USER-CBase 90=<p>  Introduced in 6.0: The panic is raised as a result of a call to the  <code>Pop()</code> and <code>PopAndDestroy()</code> static member functions of  the <code>CleanupStack</code> class. The panic occurs when an the item to be  popped is not the expected item.   </p>

E32USER-CBase 91=<p>  This panic is raised by  <span class="stripedlink"><code class="ApiItem">CActiveSchedulerWait::Start()</code></span> when the  <span class="stripedlink"><code class="ApiItem">CActiveSchedulerWait</code></span> object has already been started.   </p>

E32USER-CBase 92=<p>  This panic is raised by  <span class="stripedlink"><code class="ApiItem">CActiveSchedulerWait::AsyncStop()</code></span> and  <span class="stripedlink"><code class="ApiItem">CActiveSchedulerWait::CanStopNow()</code></span> when the  <span class="stripedlink"><code class="ApiItem">CActiveSchedulerWait</code></span> object has not been started.   </p>

E32USER-CBase 93=<p>  This panic is raised during construction of a  <span class="stripedlink"><code class="ApiItem">CAsyncOneShot</code></span> if the attempt to open a handle to the  current thread fails.   </p>

E32USER-CBase 94=<p>  Not used.   </p>

E32USER-CBase 95=<p>  This panic is raised on calls to the default implementations of  functions: <span class="stripedlink"><code class="ApiItem">CPolicyServer::CustomSecurityCheckL()</code></span> and  <span class="stripedlink"><code class="ApiItem">CPolicyServer::CustomFailureActionL()</code></span>.   </p>  <p>  The class <span class="stripedlink"><code class="ApiItem">CPolicyServer</code></span> is intended to be  derived from, and these functions in particular need to be re-implemented in a  derived class. This panic is a symptom of a failure to provide a derived class.  </p>

E32USER-CBase 96=<p>  <i>This panic is raised in debug builds only.</i>  </p>  <p>  It is raised by the protected <span class="stripedlink"><code class="ApiItem">CPolicyServer</code></span>  constructor, if the first element pointed to by the <code>iRanges</code> member  of the <code class="ApiItem">TPolicy</code>  <code>aPolicy</code> parameter does not  have a value of 0; i.e. if <code>aPolicy</code>'s  <code class="ApiItem">TPolicy::iRanges</code><code>[0]</code> is not 0.   </p>

E32USER-CBase 97=<p>  <i>This panic is raised in debug builds only.</i>  </p>  <p>  It is raised by the protected <span class="stripedlink"><code class="ApiItem">CPolicyServer</code></span>  constructor, if the value of each element of the <code>iRanges</code> member of  the <code class="ApiItem">TPolicy</code>  <code>aPolicy</code> parameter is not greater  than the value of the previous element.   </p>  <p>  See also <code class="ApiItem">TPolicy::iRanges</code>.   </p>

E32USER-CBase 98=<p>  <i>This panic is raised in debug builds only.</i>  </p>  <p>  It is raised by the protected <span class="stripedlink"><code class="ApiItem">CPolicyServer</code></span>  constructor, if the value of every element in the <code>iElementsIndex</code>  member of the <code class="ApiItem">TPolicy</code>  <code>aPolicy</code> parameter is  not valid.   </p>  <p>  Elements of <code>iElementsIndex</code> are invalid if their values  are either:   </p>  <ul>  <li>  <p>  less than <code>ESpecialCaseHardLimit</code>  </p>  </li>  </ul>  <p>  or   </p>  <ul>  <li>  <p>  greater than <code>ESpecialCaseLimit</code>  </p>  </li>  </ul>  <p>  See also <code class="ApiItem">TPolicy::iElementsIndex</code> and  <span class="stripedlink"><code class="ApiItem">CPolicyServer::TSpecialCase</code></span>.   </p>

E32USER-CBase 99=<p>  <i>This panic is raised in debug builds only.</i>  </p>  <p>  It is raised by the protected <span class="stripedlink"><code class="ApiItem">CPolicyServer</code></span>  constructor, if the value of the <code>iOnConnect</code> member of the  <code class="ApiItem">TPolicy</code>  <code>aPolicy</code> parameter is not valid.   </p>  <p>  The <code>iOnConnect</code> member is invalid if its value is  either:   </p>  <ul>  <li>  <p>  less than <code>ESpecialCaseHardLimit</code>  </p>  </li>  </ul>  <p>  or   </p>  <ul>  <li>  <p>  greater than <code>ESpecialCaseLimit</code>  </p>  </li>  </ul>  <p>  See also <code class="ApiItem">TPolicy::iOnConnect</code> and  <span class="stripedlink"><code class="ApiItem">CPolicyServer::TSpecialCase</code></span>.   </p>

E32USER-CBase 100=<p>  This panic is raised if <code class="ApiItem">CPolicyServer::iPolicy</code>  is found to be invalid for some unknown reason.   </p>  <p>  If you run the server in debug mode, it is likely that the server  will panic with one of the panic codes in the range 96 to 99 inclusive. These  are described above.   </p>  <p>  See <span class="stripedlink"><code class="ApiItem">CPolicyServer</code></span> for information about what  constitutes a valid policy.   </p>

E32USER-CBase 101=<p>  This panic is raised when the value returned by the  <span class="stripedlink"><code class="ApiItem">CPolicyServer::CustomSecurityCheckL()</code></span> and  <span class="stripedlink"><code class="ApiItem">CPolicyServer::CustomFailureActionL()</code></span> functions is  invalid.   </p>  <p>  The <span class="stripedlink"><code class="ApiItem">CPolicyServer::TCustomResult</code></span> enum defines  the valid set of return values.   </p>

E32USER-CBase 102=<p>  <i>This panic is raised in debug builds only.</i>  </p>  <p>  It is raised by the protected <span class="stripedlink"><code class="ApiItem">CPolicyServer</code></span>  constructor, if the value of the <code>iRangeCount</code> member of the  <code class="ApiItem">TPolicy</code>  <code>aPolicy</code> parameter is not greater than  0. A value of 0 implies that no policies have been passed to the policy server.  It is a requirement that at least one policy be passed to the policy server.   </p>

E32USER-CBase 103=<p>  This panic is raised by the policy server framework if a message  fails a policy check, whether custom or not.   </p>

E32USER-CBase 104=<p>  <i>This panic is raised in debug builds only.</i>  </p>  <p>  It is raised by a number of <span class="stripedlink"><code class="ApiItem">CObjectIx</code></span> member  functions if the object's data becomes inconsistent.   </p>

eSock fault 0=<p>Socket server initiation error</p>

eSock fault 1=<p>No comms server available</p>

eSock fault 2=<p>Unused</p>

eSock fault 3=<p>Failed to install active scheduler</p>

eSock fault 4=<p>Failed to create Sockets Server</p>

eSock fault 5=<p>Failed to start Sockets Server</p>

eSock fault 6=<p>Unused</p>

eSock fault 7=<p>Unused</p>

eSock fault 8=<p>Call made to unimplemented  <code>CProtocolBase::NewSAPL()</code></p>

eSock fault 9=<p>Call made to unimplemented  <code>CProtocolBase::NewHostResolverL()</code></p>

eSock fault 10=<p>Call made to unimplemented  <code>CProtocolBase::NewServiceResolverL()</code></p>

eSock fault 11=<p>Call made to unimplemented  <code>CProtocolBase::NewNetDatabaseL()</code></p>

eSock fault 12=<p>Unused</p>

eSock fault 13=<p>Unused</p>

eSock fault 14=<p>Unused</p>

eSock fault 15=<p>Error in internal state</p>

eSock fault 16=<p>Read attempted when already attempting</p>

eSock fault 17=<p>Write attempted when already attempting</p>

eSock fault 18=<p>Connect attempted when already attempting</p>

eSock fault 19=<p>Close attempted when already attempting</p>

eSock fault 20=<p>Ioctl attempted when already attempting</p>

eSock fault 21=<p>Unused</p>

eSock fault 22=<p>Error in accepted connection queuing</p>

eSock fault 23=<p>Unused</p>

eSock fault 24=<p>Failed to delete socket</p>

eSock fault 25=<p>Unused</p>

eSock fault 26=<p>Internal session maintenance error</p>

eSock fault 27=<p>Unused</p>

eSock panic 0=<p>Failed to create Sockets Server</p>

eSock panic 1=<p>Failed to start Sockets Server</p>

eSock panic 2=<p>Unused</p>

eSock panic 3=<p>Unused</p>

ESock 0=<p>  Unknown socket  </p>

ESock 1=<p>  Unused  </p>

ESock 2=<p>  Connection request made while already attempting to connect  </p>

ESock 3=<p>  Read request made while already attempting to read  </p>

ESock 4=<p>  Send request made while already attempting to send  </p>

ESock 5=<p>  Close request made while already attempting to close  </p>

ESock 6=<p>  Shutdown request made while already attempting to shutdown  </p>

ESock 7=<p>  Accept request made while already attempting to accept  </p>

ESock 8=<p>  Ioctl request made while already attempting to perform Ioctl  </p>

ESock 9=<p>  Can't use <code>RSocket::SendTo()</code> on connection-orientated  sockets  </p>

ESock 10=<p>  Can't use <code>RSocket::ListenL()</code> on connectionless sockets  </p>

ESock 11=<p>  Listen request made while already attempting to listen  </p>

ESock 12=<p>  Can't use <code>RSocket::Accept()</code> if not listening  </p>

ESock 13=<p>  Failed to accept  </p>

ESock 14=<p>  Descriptor parameter error  </p>

ESock 15=<p>  A request was made of an <code>RHostResolver</code>,  <code>RServiceResolver</code>, or <code>RNetDatabase</code> when an  asynchronous request was already pending.  </p>

ESock 16=<p>  Unused  </p>

ESock 17=<p>  No socket in use  </p>

ESock 18=<p>  Unused  </p>

ESock 19=<p>  <code>RHostResolver::Next()</code> called without initial  resolution request  </p>

ESock 20=<p>  Socket not set up to connect  </p>

Etel Server 0=<p>The subsession handle is not recognised by the server.</p>

Etel Server 1=<p>An attempt to read or write across the client-server boundary  has failed. This usually indicates that the descriptor sent is incorrectly  formatted.</p>

Etel Server 2=<p>The message type- sent by the client- is not  recognised by the server.</p>

Etel Server 3=<p>Client code has attempted to re-post an asynchronous request  before the original request has completed.</p>

Etel Server 4=<p>The client has attempted to open a sub-session without first  opening its parent object. </p>

Etel Server 5=<p>The client has attempted to use a zero length  descriptor.</p>

Etel Server 6=<p>The size field of a descriptor indicates that it contains a  negative amount of data.</p>

Etel Server 7=<p>Not used.</p>

Etel Server 8=<p>Client failed to call <code>Open()</code>.</p>

Etel Server 9=<p>Client failed to call <code>Open()</code>.</p>

Etel Server 10=<p>Client code request to access an element outside the array  range.</p>

Etel Server 11=<p>The <code>Open()</code> function has been called twice by the  same sub-session.</p>

Etel Server 12=<p>The client has passed a bad phone call type.</p>

Etel Server 13=<p>The client has specified a bad name for a phone line or phone  call object.</p>

FBSCLI 1=<p>  No connection has been made to the font and bitmap server.  </p>

FBSCLI 2=<p>  Attempted to pass a command to the font and bitmap server, but no  connection has been made.  </p>

FBSCLI 3=<p>  Not used.  </p>

FBSCLI 4=<p>  Not used.  </p>

FBSCLI 5=<p>  Not used.  </p>

FBSCLI 6=<p>  Internal typeface store error: the list of accessed fonts  (<code>CTypefaceStore::iFontAccess</code>) is inconsistent with the font cache  (<code>CFbsTypefaceStore::iTwipsCache</code>).  </p>

FBSCLI 7=<p>  The typeface store was unable to create a font due to a NULL font  handle or address.  </p>

FBSCLI 8=<p>  Attempted to access a NULL font pointer (debug builds only).  </p>

FBSCLI 9=<p>  Invalid bitmap format (debug builds only).  </p>

FBSCLI 10=<p>  Invalid bitmap display mode (<span class="stripedlink"><code class="ApiItem">TDisplayMode</code></span>).   </p>

FBSCLI 11=<p>  Invalid bitmap compression value  (<span class="stripedlink"><code class="ApiItem">TBitmapfileCompression</code></span>), or an unsupported operation was  attempted on a compressed bitmap.  </p>

FBSCLI 12=<p>  Bitmap decompression error (debug builds only).  </p>

FBSCLI 13=<p>  Memory addressing error.  </p>

FBSCLI 14=<p>  Either the display mode of the destination bitmap is not  <code>EColor256</code>, or the two bitmaps are different sizes in  <span class="stripedlink"><code class="ApiItem">CFbsColor256BitmapUtil::CopyBitmap()</code></span>.  </p>

FBSCLI 15=<p>  An error occurred when constructing a hardware bitmap (debug builds  only).  </p>

FBSCLI 16=<p>  Not used.  </p>

FBSCLI 17=<p>  Memory alignment error in a bitmap loaded from ROM.  </p>

FBSCLI 18=<p>  Not used.  </p>

FBSCLI 19=<p>  New display mode not supported by  <code>CBitwiseBitmap::ChangeDisplayMode()</code> (debug builds only).  </p>

FBSCLI 20=<p>  New display mode not supported by  <code>CBitwiseBitmap::ChangeDisplayMode()</code> (debug builds only).  </p>

FBSCLI 21=<p>  When swapping a bitmap's width and height, the size of the new  bitmap would exceed the amount of memory allocated.  </p>

FBSCLI 22=<p>  <code>CFbsBitmap::LockHeap()</code> has not been called prior to  calling <code>CFbsBitmap::DataAddress()</code> (debug builds only).  </p>

FSCLIENT panic 0=<p>  This panic is raised by:   </p>  <ul>  <li>  <p>  the <code>TDriveUnit(TInt aDrive)</code> variant of the  <span class="stripedlink"><code class="ApiItem">TDriveUnit</code></span> constructor,   </p>  </li>  <li>  <p>  the <code>(TInt aDrive)</code> variant of the  <span class="stripedlink"><code class="ApiItem">TDriveUnit</code></span> assignment operator   </p>  </li>  </ul>  <p>  when the specified drive number is greater than or equal to  <code>KMaxDrives</code>, i.e. 26.   </p>

FSCLIENT panic 1=<p>  This panic is raised by:   </p>  <ul>  <li>  <p>  the <code>TDriveUnit(const TDesC&amp; aDriveText)</code>  variant of the <span class="stripedlink"><code class="ApiItem">TDriveUnit</code></span> constructor,   </p>  </li>  <li>  <p>  the <code>(const TDesC&amp; aDriveText)</code> variant of the  <span class="stripedlink"><code class="ApiItem">TDriveUnit</code></span> assignment operator   </p>  </li>  </ul>  <p>  when the specified drive letter is invalid, i.e. does not  correspond to a drive number.   </p>

FSCLIENT panic 2=<p>  This panic is raised when searching for the next file using  <span class="stripedlink"><code class="ApiItem">TFindFile::Find()</code></span> or  <span class="stripedlink"><code class="ApiItem">TFindFile::FindWild()</code></span> before the initial call specifying  the search method.   </p>  <p>  Calls to <span class="stripedlink"><code class="ApiItem">TFindFile::Find()</code></span> cannot be made  until an initial call has been made to either of:   </p>  <ul>  <li>  <p>  <span class="stripedlink"><code class="ApiItem">TFindFile::FindByDir()</code></span>  </p>  </li>  <li>  <p>  <span class="stripedlink"><code class="ApiItem">TFindFile::FindByPath()</code></span>  </p>  </li>  </ul>  <p>  Calls to <span class="stripedlink"><code class="ApiItem">TFindFile::FindWild()</code></span> cannot be made  until an initial call has been made to either of:   </p>  <ul>  <li>  <p>  <span class="stripedlink"><code class="ApiItem">TFindFile::FindWildByDir()</code></span>  </p>  </li>  <li>  <p>  <span class="stripedlink"><code class="ApiItem">TFindFile::FindWildByPath()</code></span>  </p>  </li>  </ul>

FSCLIENT panic 3=<p>  <em>Not used.</em>  </p>

FSCLIENT panic 4=<p>  <em>Not used.</em>  </p>

FSCLIENT panic 5=<p>  This panic is raised by a call to  <span class="stripedlink"><code class="ApiItem">TFileText::Seek()</code></span> when the seek mode passed to the  function is neither <span class="stripedlink"><code class="ApiItem">TSeek</code></span><code>::ESeekStart</code> nor  <span class="stripedlink"><code class="ApiItem">TSeek</code></span><code>::ESeekEnd</code>.   </p>

FSCLIENT panic 6=<p>  <em>Not used.</em>  </p>

FSCLIENT panic 7=<p>  <em>Not used.</em>  </p>

FSCLIENT panic 8=<p>  <em>Not used.</em>  </p>

FSCLIENT panic 9=<p>  <em>Not used.</em>  </p>

FSCLIENT panic 10=<p>  This panic is raised by the <span class="stripedlink"><code class="ApiItem">CFileMan</code></span>  implementation when the operation to be run is undefined.   </p>

FSCLIENT panic 11=<p>  This panic is raised by  <span class="stripedlink"><code class="ApiItem">CFileBase::CurrentEntry()</code></span> if there is no current entry.   </p>

FSCLIENT panic 12=<p>  The value returned by the file management observer functions:   </p>  <ul>  <li>  <p>  <span class="stripedlink"><code class="ApiItem">MFileManObserver::NotifyFileManStarted()</code></span>  </p>  </li>  <li>  <p>  <span class="stripedlink"><code class="ApiItem">MFileManObserver::NotifyFileManEnded()</code></span>  </p>  </li>  <li>  <p>  <span class="stripedlink"><code class="ApiItem">MFileManObserver::NotifyFileManOperation()</code></span>  </p>  </li>  </ul>  <p>  is not a valid <span class="stripedlink"><code class="ApiItem">MFileManObserver::TControl</code></span> enum  value.   </p>

FSCLIENT panic 13=<p>  <em>Not used.</em>  </p>

FSCLIENT panic 14=<p>  <em>Not used.</em>  </p>

FSCLIENT panic 15=<p>  <i>This panic is raised in debug builds only.</i>  </p>  <p>  This panic is raised in a call to  <span class="stripedlink"><code class="ApiItem">CDirScan::SetScanDataL()</code></span> when the path does not contain at  least one '\' character.   </p>

FSCLIENT panic 16=<p>  <em>Not used.</em>  </p>

FSCLIENT panic 17=<p>  This panic is raised by <span class="stripedlink"><code class="ApiItem">RFile::Lock()</code></span> when the  number of bytes defining the region to be locked is either zero or negative.   </p>

FSCLIENT panic 18=<p>  This panic is raised by <span class="stripedlink"><code class="ApiItem">RFile::UnLock()</code></span> when  the number of bytes defining the region to be unlocked is either zero or  negative.   </p>

FSCLIENT panic 19=<p>  All variants of the <span class="stripedlink"><code class="ApiItem">RFile::Read()</code></span> and  <span class="stripedlink"><code class="ApiItem">RFile::Write()</code></span> functions take an argument denoting an  offset value, in bytes, from the start of a file; the panic is raised by these  functions when the offset value is negative.   </p>

FSCLIENT panic 20=<p>  This panic is raised by <span class="stripedlink"><code class="ApiItem">RFile::SetSize()</code></span> when  the argument denoting the size of the new file is negative.   </p>

FSCLIENT panic 21=<p>  This panic is raised by <span class="stripedlink"><code class="ApiItem">RFile::SetAtt()</code></span> and  <span class="stripedlink"><code class="ApiItem">RFile::Set()</code></span> when the same attribute bit is set in both  the bitmask that indicates the file attributes to be set and the bitmask that  indicates the attributes to be cleared.   </p>

FSCLIENT panic 22=<p>  The panic is raised by the <code>[]</code> operator of  <span class="stripedlink"><code class="ApiItem">TEntryArray</code></span>, when the index value passed to the operator  is greater than or equal to the number of elements in the array.   </p>

FSCLIENT panic 23=<p>  This panic is raised by <span class="stripedlink"><code class="ApiItem">CDir::Sort()</code></span> when the  method of sorting, as defined by the single function argument, is none of the  entries:   </p>  <ul>  <li>  <p>  <span class="stripedlink"><code class="ApiItem">TEntryKey</code></span><code>::ESortNone</code>  </p>  </li>  <li>  <p>  <span class="stripedlink"><code class="ApiItem">TEntryKey</code></span><code>::ESortByDate</code>  </p>  </li>  <li>  <p>  <span class="stripedlink"><code class="ApiItem">TEntryKey</code></span><code>::ESortBySize</code>  </p>  </li>  <li>  <p>  <span class="stripedlink"><code class="ApiItem">TEntryKey</code></span><code>::ESortByExt</code>  </p>  </li>  <li>  <p>  <span class="stripedlink"><code class="ApiItem">TEntryKey</code></span><code>::ESortByUid</code>  </p>  </li>  <li>  <p>  <span class="stripedlink"><code class="ApiItem">TEntryKey</code></span><code>::ESortByName</code>  </p>  </li>  </ul>

FSCLIENT panic 24=<p>  This panic is raised by the <span class="stripedlink"><code class="ApiItem">TParsePtr</code></span>  constructor that takes a reference to a filename, when the name cannot be  parsed.   </p>

FSCLIENT panic 25=<p>  This panic is raised by the <span class="stripedlink"><code class="ApiItem">TParsePtrC</code></span>  constructor that takes a const reference to a filename, when the name cannot be  parsed.   </p>

FSCLIENT panic 26=<p>  This panic is raised by <span class="stripedlink"><code class="ApiItem">RFs::ReadFileSection()</code></span>  when the specified number of bytes to be read from the file is greater than the  maximum length of the target descriptor.   </p>

FSCLIENT panic 27=<p>  <i>This panic is raised in debug builds only.</i>  </p>  <p>  This panic is raised by the <code class="ApiItem">RFile::Write(const  TDesC8&amp;,TInt)</code> variant when the specified length is greater than  the length of the source descriptor.   </p>

IMAPServer 0=<p>  Session logic, which relates to the set up and management of an  individual session to an IMAP server  </p>

IMAPServer 1=<p>  Session logic, which relates to the set up and management of an  individual session to an IMAP server  </p>

IMAPServer 2=<p>  Session logic, which relates to the set up and management of an  individual session to an IMAP server  </p>

IMAPServer 3=<p>  Session logic, which relates to the set up and management of an  individual session to an IMAP server  </p>

IMAPServer 4=<p>  Session logic, which relates to the set up and management of an  individual session to an IMAP server  </p>

IMAPServer 5=<p>  Session logic, which relates to the set up and management of an  individual session to an IMAP server  </p>

IMAPServer 6=<p>  Session logic, which relates to the set up and management of an  individual session to an IMAP server  </p>

IMAPServer 7=<p>  Session logic, which relates to the set up and management of an  individual session to an IMAP server  </p>

IMAPServer 8=<p>  Session logic, which relates to the set up and management of an  individual session to an IMAP server  </p>

IMAPServer 9=<p>  Session logic, which relates to the set up and management of an  individual session to an IMAP server  </p>

IMAPServer 10=<p>  Session logic, which relates to the set up and management of an  individual session to an IMAP server  </p>

IMAPServer 11=<p>  Session logic, which relates to the set up and management of an  individual session to an IMAP server  </p>

IMAPServer 12=<p>  Session logic, which relates to the set up and management of an  individual session to an IMAP server  </p>

IMAPServer 13=<p>  Session logic, which relates to the set up and management of an  individual session to an IMAP server  </p>

IMAPServer 14=<p>  Session logic, which relates to the set up and management of an  individual session to an IMAP server  </p>

IMAPServer 15=<p>  Session logic, which relates to the set up and management of an  individual session to an IMAP server  </p>

IMAPServer 16=<p>  Session logic, which relates to the set up and management of an  individual session to an IMAP server  </p>

IMAPServer 17=<p>  Session logic, which relates to the set up and management of an  individual session to an IMAP server  </p>

IMAPServer 18=<p>  Session logic, which relates to the set up and management of an  individual session to an IMAP server  </p>

IMAPServer 19=<p>  Session logic, which relates to the set up and management of an  individual session to an IMAP server  </p>

IMAPServer 20=<p>  Session logic, which relates to the set up and management of an  individual session to an IMAP server  </p>

IMAPServer 21=<p>  Session logic, which relates to the set up and management of an  individual session to an IMAP server  </p>

IMAPServer 22=<p>  Session logic, which relates to the set up and management of an  individual session to an IMAP server  </p>

IMAPServer 23=<p>  Session logic, which relates to the set up and management of an  individual session to an IMAP server  </p>

IMAPServer 24=<p>  Session logic, which relates to the set up and management of an  individual session to an IMAP server  </p>

IMAPServer 25=<p>  Session logic, which relates to the set up and management of an  individual session to an IMAP server  </p>

IMAPServer 26=<p>  Session logic, which relates to the set up and management of an  individual session to an IMAP server  </p>

IMAPServer 27=<p>  Session logic, which relates to the set up and management of an  individual session to an IMAP server  </p>

IMAPServer 28=<p>  Session logic, which relates to the set up and management of an  individual session to an IMAP server  </p>

IMAPServer 29=<p>  Session logic, which relates to the set up and management of an  individual session to an IMAP server  </p>

IMAPServer 30=<p>  Session logic, which relates to the set up and management of an  individual session to an IMAP server  </p>

IMAPServer 31=<p>  Session logic, which relates to the set up and management of an  individual session to an IMAP server  </p>

IMAPServer 32=<p>  Session logic, which relates to the set up and management of an  individual session to an IMAP server  </p>

IMAPServer 33=<p>  Session logic, which relates to the set up and management of an  individual session to an IMAP server  </p>

IMAPServer 34=<p>  Session logic, which relates to the set up and management of an  individual session to an IMAP server  </p>

IMAPServer 35=<p>  Session logic, which relates to the set up and management of an  individual session to an IMAP server  </p>

IMAPServer 36=<p>  Session logic, which relates to the set up and management of an  individual session to an IMAP server  </p>

IMAPServer 37=<p>  Session logic, which relates to the set up and management of an  individual session to an IMAP server  </p>

IMAPServer 38=<p>  Session logic, which relates to the set up and management of an  individual session to an IMAP server  </p>

IMAPServer 39=<p>  Session logic, which relates to the set up and management of an  individual session to an IMAP server  </p>

IMAPServer 40=<p>  Session logic, which relates to the set up and management of an  individual session to an IMAP server  </p>

IMAPServer 41=<p>  Session logic, which relates to the set up and management of an  individual session to an IMAP server  </p>

IMAPServer 42=<p>  Session logic, which relates to the set up and management of an  individual session to an IMAP server  </p>

IMAPServer 43=<p>  Session logic, which relates to the set up and management of an  individual session to an IMAP server  </p>

IMAPServer 44=<p>  Session logic, which relates to the set up and management of an  individual session to an IMAP server  </p>

IMAPServer 45=<p>  Session logic, which relates to the set up and management of an  individual session to an IMAP server  </p>

IMAPServer 46=<p>  Session logic, which relates to the set up and management of an  individual session to an IMAP server  </p>

IMAPServer 47=<p>  Session logic, which relates to the set up and management of an  individual session to an IMAP server  </p>

IMAPServer 48=<p>  Session logic, which relates to the set up and management of an  individual session to an IMAP server  </p>

IMAPServer 49=<p>  Session logic, which relates to the set up and management of an  individual session to an IMAP server  </p>

IMAPServer 50=<p>  Session logic, which relates to the set up and management of an  individual session to an IMAP server  </p>

IMAPServer 51=<p>  Session logic, which relates to the set up and management of an  individual session to an IMAP server  </p>

IMAPServer 52=<p>  Session logic, which relates to the set up and management of an  individual session to an IMAP server  </p>

IMAPServer 53=<p>  Session logic, which relates to the set up and management of an  individual session to an IMAP server  </p>

IMAPServer 54=<p>  Session logic, which relates to the set up and management of an  individual session to an IMAP server  </p>

IMAPServer 55=<p>  Session logic, which relates to the set up and management of an  individual session to an IMAP server  </p>

IMAPServer 56=<p>  Session logic, which relates to the set up and management of an  individual session to an IMAP server  </p>

IMAPServer 57=<p>  Session logic, which relates to the set up and management of an  individual session to an IMAP server  </p>

IMAPServer 58=<p>  Session logic, which relates to the set up and management of an  individual session to an IMAP server  </p>

IMAPServer 59=<p>  Session logic, which relates to the set up and management of an  individual session to an IMAP server  </p>

IMAPServer 60=<p>  Session logic, which relates to the set up and management of an  individual session to an IMAP server  </p>

IMAPServer 61=<p>  Session logic, which relates to the set up and management of an  individual session to an IMAP server  </p>

IMAPServer 62=<p>  Session logic, which relates to the set up and management of an  individual session to an IMAP server  </p>

IMAPServer 63=<p>  Session logic, which relates to the set up and management of an  individual session to an IMAP server  </p>

IMAPServer 64=<p>  Session logic, which relates to the set up and management of an  individual session to an IMAP server  </p>

IMAPServer 65=<p>  Session logic, which relates to the set up and management of an  individual session to an IMAP server  </p>

IMAPServer 66=<p>  Session logic, which relates to the set up and management of an  individual session to an IMAP server  </p>

IMAPServer 67=<p>  Session logic, which relates to the set up and management of an  individual session to an IMAP server  </p>

IMAPServer 68=<p>  Session logic, which relates to the set up and management of an  individual session to an IMAP server  </p>

IMAPServer 69=<p>  Session logic, which relates to the set up and management of an  individual session to an IMAP server  </p>

IMAPServer 70=<p>  Session logic, which relates to the set up and management of an  individual session to an IMAP server  </p>

IMAPServer 71=<p>  Session logic, which relates to the set up and management of an  individual session to an IMAP server  </p>

IMAPServer 72=<p>  Session logic, which relates to the set up and management of an  individual session to an IMAP server  </p>

IMAPServer 73=<p>  Session logic, which relates to the set up and management of an  individual session to an IMAP server  </p>

IMAPServer 74=<p>  Session logic, which relates to the set up and management of an  individual session to an IMAP server  </p>

IMAPServer 75=<p>  Session logic, which relates to the set up and management of an  individual session to an IMAP server  </p>

IMAPServer 76=<p>  Session logic, which relates to the set up and management of an  individual session to an IMAP server  </p>

IMAPServer 77=<p>  Session logic, which relates to the set up and management of an  individual session to an IMAP server  </p>

IMAPServer 78=<p>  Session logic, which relates to the set up and management of an  individual session to an IMAP server  </p>

IMAPServer 79=<p>  Session logic, which relates to the set up and management of an  individual session to an IMAP server  </p>

IMAPServer 80=<p>  Session logic, which relates to the set up and management of an  individual session to an IMAP server  </p>

IMAPServer 81=<p>  Session logic, which relates to the set up and management of an  individual session to an IMAP server  </p>

IMAPServer 82=<p>  Session logic, which relates to the set up and management of an  individual session to an IMAP server  </p>

IMAPServer 83=<p>  Session logic, which relates to the set up and management of an  individual session to an IMAP server  </p>

IMAPServer 84=<p>  Session logic, which relates to the set up and management of an  individual session to an IMAP server  </p>

IMAPServer 85=<p>  Session logic, which relates to the set up and management of an  individual session to an IMAP server  </p>

IMAPServer 86=<p>  Session logic, which relates to the set up and management of an  individual session to an IMAP server  </p>

IMAPServer 87=<p>  Session logic, which relates to the set up and management of an  individual session to an IMAP server  </p>

IMAPServer 88=<p>  Session logic, which relates to the set up and management of an  individual session to an IMAP server  </p>

IMAPServer 89=<p>  Session logic, which relates to the set up and management of an  individual session to an IMAP server  </p>

IMAPServer 90=<p>  Session logic, which relates to the set up and management of an  individual session to an IMAP server  </p>

IMAPServer 91=<p>  Session logic, which relates to the set up and management of an  individual session to an IMAP server  </p>

IMAPServer 92=<p>  Session logic, which relates to the set up and management of an  individual session to an IMAP server  </p>

IMAPServer 93=<p>  Session logic, which relates to the set up and management of an  individual session to an IMAP server  </p>

IMAPServer 94=<p>  Session logic, which relates to the set up and management of an  individual session to an IMAP server  </p>

IMAPServer 95=<p>  Session logic, which relates to the set up and management of an  individual session to an IMAP server  </p>

IMAPServer 96=<p>  Session logic, which relates to the set up and management of an  individual session to an IMAP server  </p>

IMAPServer 97=<p>  Session logic, which relates to the set up and management of an  individual session to an IMAP server  </p>

IMAPServer 98=<p>  Session logic, which relates to the set up and management of an  individual session to an IMAP server  </p>

IMAPServer 99=<p>  Session logic, which relates to the set up and management of an  individual session to an IMAP server  </p>

IMAPServer 100=<p>  Session logic, which relates to the set up and management of an  individual session to an IMAP server  </p>

IMAPServer 101=<p>  Session logic, which relates to the set up and management of an  individual session to an IMAP server  </p>

IMAPServer 102=<p>  Session logic, which relates to the set up and management of an  individual session to an IMAP server  </p>

IMAPServer 103=<p>  Session logic, which relates to the set up and management of an  individual session to an IMAP server  </p>

IMAPServer 104=<p>  Session logic, which relates to the set up and management of an  individual session to an IMAP server  </p>

IMAPServer 105=<p>  Session logic, which relates to the set up and management of an  individual session to an IMAP server  </p>

IMAPServer 106=<p>  Session logic, which relates to the set up and management of an  individual session to an IMAP server  </p>

IMAPServer 107=<p>  Session logic, which relates to the set up and management of an  individual session to an IMAP server  </p>

IMAPServer 108=<p>  Session logic, which relates to the set up and management of an  individual session to an IMAP server  </p>

IMAPServer 109=<p>  Session logic, which relates to the set up and management of an  individual session to an IMAP server  </p>

IMAPServer 110=<p>  Session logic, which relates to the set up and management of an  individual session to an IMAP server  </p>

IMAPServer 111=<p>  Session logic, which relates to the set up and management of an  individual session to an IMAP server  </p>

IMAPServer 112=<p>  Session logic, which relates to the set up and management of an  individual session to an IMAP server  </p>

IMAPServer 113=<p>  Session logic, which relates to the set up and management of an  individual session to an IMAP server  </p>

IMAPServer 114=<p>  Session logic, which relates to the set up and management of an  individual session to an IMAP server  </p>

IMAPServer 115=<p>  Session logic, which relates to the set up and management of an  individual session to an IMAP server  </p>

IMAPServer 116=<p>  Session logic, which relates to the set up and management of an  individual session to an IMAP server  </p>

IMAPServer 117=<p>  Session logic, which relates to the set up and management of an  individual session to an IMAP server  </p>

IMAPServer 118=<p>  Session logic, which relates to the set up and management of an  individual session to an IMAP server  </p>

IMAPServer 119=<p>  Session logic, which relates to the set up and management of an  individual session to an IMAP server  </p>

IMAPServer 120=<p>  Session logic, which relates to the set up and management of an  individual session to an IMAP server  </p>