There is a small section at the end of section 5 of the newest AIM*Historian installation guide (B0193YM Rev E) that describes a procedure that may solve your problem. Here it is : Modifying the Login Profile If you plan to configure multiple instances on the AIM*Historian server, raise the limit of file descriptors to avoid problems with the server programs not having enough descriptors to handle messages from several instances simultaneously. As a general guide to setting the appropriate limit, a limit of 300 can handle 14 instances. To increase the limit for Bourne shell: Modify /etc/profile to insert the line: ulimit -n <new number> For example: ulimit -n 300 To increase the limit for a C shell: Modify the .cshrc file to insert the line: limit descriptors <new number> For example: limit descriptors 300 Add also a line in go_AIMHISTORIAN ulimit -n 300 Good luck -----Original Message----- From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On Behalf Of Ken.E.Moore@xxxxxxxxxxx Sent: Friday, September 10, 2004 10:12 AM To: foxboro@xxxxxxxxxxxxx Subject: Re: [foxboro] Aim*Historian Startup He's running a 51B, so there isn't any "Start>Settings>Control Panel> AIM*API" What would be the solaris solution? Ken Moore "Losure, Nancy" <NLosure@xxxxxxx>@freelists.org on 09/10/2004 08:32:07 AM Please respond to foxboro@xxxxxxxxxxxxx Sent by: foxboro-bounce@xxxxxxxxxxxxx To: <foxboro@xxxxxxxxxxxxx> cc: Subject: Re: [foxboro] Aim*Historian Startup Ashley: Go to the apisvr and check the "start on reboot" box. The best way to get there is Start>Settings>Control Panel> AIM*API. This is a feeeeeeture that is not well explained in the manual. Good luck. Nancy S. Losure, Ph.D. Staff Engineer, Plant Technical Services Kerr McGee Chemical, LLC 662-343-2059 -----Original Message----- From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On Behalf Of Ashley Davey Sent: Friday, September 10, 2004 1:11 AM To: foxboro@xxxxxxxxxxxxx Subject: [foxboro] Aim*Historian Startup Hello All, =20 We have Aim*Historian Version 3.02 running on an AW51B with I/A Version 6.3. =20 The historian has 4 instances all configured to "start up on reboot". However, the instances do not start up completely.=20 If using "Historian Manager" and one looks at the "Processes" it can be seen that of the 5 processes per instance=20 =20 HistReceive, Archiver and Repack - Start on reboot and Reduce_Rtps and Histmain - Do NOT start on reboot. =20 Is there any setting, script, etc that I can change to ensure that ALL the processes start on ReBoot? When started from Historian Manager they will run until the next ReBoot. =20 Thanks =20 Ashley Davey Systems Engineer African Products (Pty) Ltd Gauteng Republic of South Africa Tel : +27 11 458 5342 Fax : +27 11 458 5343 Mobile: +27 83 4535169 =20 =20 _______________________________________________________________________ This mailing list is neither sponsored nor endorsed by Invensys Process Systems (formerly The Foxboro Company). Use the info you obtain here at your own risks. Read http://www.thecassandraproject.org/disclaimer.html =20 foxboro mailing list: //www.freelists.org/list/foxboro to subscribe: = mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Djoin to unsubscribe: = mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Dleave =20 _______________________________________________________________________ This mailing list is neither sponsored nor endorsed by Invensys Process Systems (formerly The Foxboro Company). Use the info you obtain here at your own risks. Read http://www.thecassandraproject.org/disclaimer.html foxboro mailing list: //www.freelists.org/list/foxboro to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave __ This email has been scanned for Viruses and Spam. For more information please contact your local Information Security representative. ______________________________________________________________________ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email ______________________________________________________________________ _______________________________________________________________________ This mailing list is neither sponsored nor endorsed by Invensys Process Systems (formerly The Foxboro Company). Use the info you obtain here at your own risks. Read http://www.thecassandraproject.org/disclaimer.html foxboro mailing list: //www.freelists.org/list/foxboro to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave _______________________________________________________________________ This mailing list is neither sponsored nor endorsed by Invensys Process Systems (formerly The Foxboro Company). Use the info you obtain here at your own risks. Read http://www.thecassandraproject.org/disclaimer.html foxboro mailing list: //www.freelists.org/list/foxboro to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave