Tried that, but there seems to always be yet one more form to be deleted by the 
installer.
Was wondering if there was a quicker way around this issue than re-running the 
install over and over again and waiting at which point it is going to fail next.

Jiri

-----Original Message-----
From: Action Request System discussion list(ARSList) 
[mailto:[email protected]] On Behalf Of Grooms, Frederick W
Sent: 25 October 2010 15:14
To: [email protected]
Subject: Re: Getting malloc error on server when running AIS 7.6.03 installation

What if you delete the workflow for the form yourself (in small chunks) ahead 
of time?

Fred

-----Original Message-----
From: Action Request System discussion list(ARSList) 
[mailto:[email protected]] On Behalf Of Jiri Pospisil
Sent: Sunday, October 24, 2010 7:58 AM
To: [email protected]
Subject: Getting malloc error on server when running AIS 7.6.03 installation

++++++++++++++++++++++++++++++++++++++++++++++++++++++
Please Read The Disclaimer At The Bottom Of This Email
++++++++++++++++++++++++++++++++++++++++++++++++++++++

Hi,

I am trying to run Atrium 7.6.03 installation on our test server, but it keeps 
failing with malloc on the server.
After looking at the generated log files, it seems the installer fails when it 
attempts deleting some of the old forms that have lots of workflow associated.
I tried to delete the form using the development studio and got the malloc 
again.
What seems to be happening is that the server keeps issuing delete commands to 
the database for all related workflow, but does not commit until all items are 
deleted. At the same time the size of the arsystem.exe process starts growing 
rapidly and eventually reaches 3GB at which point the server fails, before it 
managed to delete all related items.

Anybody seen this and can suggest a way around this? What worries me is that I 
got similar error when trying to install ITSM 7.6.03.

Environment
Microsoft Server 2003, SP2
MS SQL 2005 database (remote)
Memory on server 8GB (with 3GB switch enabled)
AR System version 7.6.03
AIE version 7.6.0 patch 001 

Thanks

Jiri Pospisil
LCH.Clearnet 



*************************************************************************************************

This email is intended for the named recipient(s) only. Its contents are 
confidential and may only be retained by the named recipient(s) and may only be 
copied or disclosed with the consent of LCH.Clearnet Limited and/or 
LCH.Clearnet SA.   If you are not an intended recipient please delete this 
e-mail and notify [email protected].
LCH.Clearnet Limited, LCH.Clearnet SA and each other member of the LCH.Clearnet 
Group accept no liability, including liability for negligence, in respect of 
any statement in this email.
The contents of this email are subject to contract in all cases, and 
LCH.Clearnet Limited and/or LCH.Clearnet SA makes no contractual commitment 
save where confirmed by hard copy.  
Cet e-mail et toutes les pièces jointes (ci-après le "message") sont 
confidentiels et établis à l'intention exclusive de ses destinataires. Toute 
utilisation de ce message non conforme à sa destination, toute diffusion ou 
toute publication, est interdite, sauf autorisation expresse de LCH.Clearnet 
Limited et/ou LCH.Clearnet SA. Si ce message vous a été adressé par erreur, 
merci de le détruire et d'en avertir immédiatement [email protected].
LCH.Clearnet Limited, LCH.Clearnet SA et les autres entités du groupe 
LCH.Clearnet Group, ne peuvent en aucun cas être tenues responsables au titre 
de ce message à moins qu’il n’ait fait l’objet d’un contrat signé.
LCH.Clearnet Limited, Registered Office: Aldgate House, 33 Aldgate High Street, 
London EC3N 1EA.    Recognised as a Clearing House under the Financial Services 
& Markets Act 2000. Reg in England No.25932 
Telephone: +44 20 7426 7000              Internet: http://www.lchclearnet.com
LCH.Clearnet SA, Siège Social, 18 rue du Quatre Septembre, 75002 Paris, Chambre 
de Compensation conformément au Code Monétaire et Financier.

*************************************************************************************************

Reply via email to