James/Melissa



	I am also using ListServ 14.5...  I have had the auto restart on for

sometime.  Problem is that the server is now getting the occasional WMI

error...  I have done a search and found all the log files that are >100MB

and renamed them.  This is a bit draconian, but I want to see if it really

solves the problem.  During the process I also found some index files that

were >100MB.  I have changed the more active lists from Monthly to weekly.

I am waiting to see if this solves the problem.



	In the meantime, if I change a list from monthly to weekly, does the

system continue reindexing the previous logs?





-------------------------------------------------

Curtis E. Stevens

Director, Standards & Features Technology

3355 Michelson Dr. #100

Office: 1-1041

Irvine, Ca. 92612

Phone: 949-672-7933

Cell: 949-307-5050

E-Mail: [log in to unmask]



Remember, you may only be blamed for something if you are actually doing

something.



-----Original Message-----

From: LISTSERV site administrators' forum

[mailto:[log in to unmask]] On Behalf Of James Morrill

Sent: Friday, October 07, 2011 7:40 AM

To: [log in to unmask]

Subject: Re: Heap Error



We had this re-indexing issue for a while and solved it by changing some of

our big lists from Notebook= Monthly to Notebook= Weekly.



-- 

  James Morrill  office: HL 11, 785-532-4909   www-personal.ksu.edu/~james



      If you want to be a leader with a large following, just obey the

                speed limit on a winding, two-lane road.



On Thu, 6 Oct 2011, Liam Kelly wrote:



>> I am getting "Error 8 from HeapAlloc() for 379908678 bytes"  during a 

>> reindexing operation.  The list is average sized.  What is this 

>> indicating?

>

> It's a memory allocation failure.  When you say the list is 'average 

> sized', what does that mean?  What is the total size of the archive 

> for this list, and what is the single largest archive file for it?

>

> In nearly all cases, a HeapAlloc failure is an actual memory or user 

> quota issue, but I've seen one case where it was caused by messages 

> with corrupt

> base64 data.  If that's the case, you would see MIME parser errors in 

> the LISTSERV log immediately prior to the crash.

>

> --

> Liam Kelly

> Senior Consulting Analyst

> L-Soft international

> [log in to unmask]

>

> Interested in other L-Soft products?  See what else we have to offer 

> here <http://www.lsoft.com/products/products.asp>

> archives at <http://www.lsoft.com/news/newsletter-us.asp>

>

> ############################

>

> To unsubscribe from the LSTSRV-L list:

> write to: mailto:[log in to unmask]

> or click the following link:

> http://peach.ease.lsoft.com/scripts/wa.exe?SUBED1=LSTSRV-L&A=1

>



############################



To unsubscribe from the LSTSRV-L list:

write to: mailto:[log in to unmask]

or click the following link:

http://peach.ease.lsoft.com/scripts/wa.exe?SUBED1=LSTSRV-L&A=1



############################



To unsubscribe from the LSTSRV-L list:

write to: mailto:[log in to unmask]

or click the following link:

http://peach.ease.lsoft.com/scripts/wa.exe?SUBED1=LSTSRV-L&A=1