Thanks Joe and Drew for the responses!
________________________________ From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Joe D'Souza Sent: Thursday, September 13, 2007 4:30 PM To: [email protected] Subject: Re: Error log from install- successful install with a lot of failures ok? Since you are saying its a fresh install, I would roll back and install the application again? If that is not a possibility you can manually try importing the def files. I would FTP the files from the path you see on your logs to a local windows machine with the Admin tool installed, and import these def files. Problem with that though is if there were failed .arx files that had to be imported into the forms, you will have to do that manually too. So basically if its a fresh install I would scratch it off and reinstall.. After installing the AR Server though, put the server in a 'Development Cache Mode'. This may eliminate any timeouts caused during the install, thus minimizing such errors. Also make sure you have sufficient data and temp space in your database for the ARSYSTEM database. Cheers Joe -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] Behalf Of Moore, Chris Sent: Thursday, September 13, 2007 4:16 PM To: [email protected] Subject: Error log from install- successful install with a lot of failures ok? ** Hey everyone- Today we installed Incident on a 7.1 server, OS RHEL 5 and DB Oracle 10g. The application successfully installed according to the script, but in the text of the error log we saw a lot of things like the following. Is this something to be concerned about? I logged in and things appear to be ok, but it is a totally un-configured system with no data at all, so I can't test workflow. In a nutshell, there's a lot of red "Failed"s. The entire log is too long to send to the list, but here's an example. Thanks! Chris Moore Results from loading application tms Thu Sep 13 10:03:43 2007 Component tms 1. /opt/remedy/dev001/incident/ar/tms/workflow/en/./tms_deplapp.def: Failed 2. /opt/remedy/dev001/incident/ar/tms/workflow/en/./SHRSHR_menu.def: Success 3. /opt/remedy/dev001/incident/ar/tms/workflow/en/./TMS_menu.def: Failed 4. /opt/remedy/dev001/incident/ar/tms/workflow/en/./INTEG_SHRSHR_APR%Altern ate2.def: Failed 5. /opt/remedy/dev001/incident/ar/tms/workflow/en/./INTEG_SHRSHR_AST%Purcha seLineItem2.def: Failed ...................................... Component Summary tms Successful def files: 3 Failed def files: 60 Skipped status def files : 0 Successful cfg data files: 22 Failed cfg data files: 12 Skipped status cfg data files : 0 Successful sample data files: 0 Failed sample data files: 0 Skipped status sample data files : 0 Worst definition file import rc: 2 Worst config data import rc: 1025 Worst sample data import rc: 0 Worst rc for the component: 1025 Application Summary Successful def files: 3 Failed def files: 60 Skipped status def files : 0 Successful cfg data files: 22 Failed cfg data files: 12 Skipped status cfg data files : 0 Successful sample data files: 0 Failed sample data files: 0 Skipped status sample data files : 0 Worst definition file import rc: 2 Worst config data import rc: 1025 Worst sample data import rc: 0 __20060125_______________________This posting was submitted with HTML in it___ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
