If your EIE instance is connecting to an SQL server, make sure there is no limit on the number of user connections to the SQL server.. There is an issue with EIE I have seen when used with the SQL link, that it leaves an open connection every time a schedule is run, thus opening a new connection at every schedule... If this is your problem, to avoid it have a windows batch file to stop the EIE service after the run of the schedule and start it just before the schedule kicks in... Use the windows scheduled tasks to achieve this and the net stop or net start to stop or start services in your batch file..
Joe D'Souza -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] Behalf Of Eli Schilling Sent: Friday, December 21, 2007 2:45 PM To: arslist@ARSLIST.ORG Subject: Re: EIE Schedules not working ** The service is up and running. The normal log files aren't being updated/created. however, I have a nifty debug log file that, in broken-record-fashion, has been telling me: ---------------------------------------------------------------------------- -- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of strauss Sent: Friday, December 21, 2007 11:40 AM To: arslist@ARSLIST.ORG Subject: Re: EIE Schedules not working ** I assume that the Windows service instance that you selected for the exchange to run on - like EIE [servername(server port)] - 001 -or- BMC AIE [servername(server port)] - 001 is in fact running. If the service is not running (and they install as Manual Startup) then you will never have the exchange run on the schedule you defined in the EIE/AIE console until you start the service. The normal log file is in the \Remedy\Apps\EIE\servername-port\service\log -or- BMC Software\BMC Atrium Integration Engine\servername-port\service\log directory. The debug logs are in the service\debug directory Careful of the debug logs - in EIE they were managed from the eie.cfg file and behaved for me. In AIE, they are managed from the console, not the eie.cfg file, and will grow until you have no more physical file space in a hurry if you are processing a lot of data. I never had a problem with them in EIE, but as soon as I upgraded to AIE they got out of control in a week. Christopher Strauss, Ph.D. Call Tracking Administration Manager University of North Texas Computing & IT Center http://itsm.unt.edu/ ---------------------------------------------------------------------------- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Eli Schilling Sent: Friday, December 21, 2007 1:14 PM To: arslist@ARSLIST.ORG Subject: EIE Schedules not working ** Hey everyone, happy friday! (Sorry, no humor in this message) I have a strange issue whereby my scheduled exchanges in EIE aren't running. If I kick them off manually it works fine but when I schedule them nothing happens. I enabled logging and scheduled the job serveral times. The scheduled time came and went and not even a log file was created. Since EIE isn't cool like the Recon Engine (having its own job history console) and since there aren't any events in the system logs I'm not sure where to start. Version: EIE 7.01 SQL 2005 Windows Server 2003 AR Server 7.01 (all applications are 7.0.02 patch 005) Thanks in advance! No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.5.516 / Virus Database: 269.17.6/1192 - Release Date: 12/21/2007 1:17 PM _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
