James, Did you attempt to startup the server with the startup logs turned on? You will need to add the -t switch to the startup in the armonitor.conf file and restart the server. Add -t just before the -i switch so it should read like:
"InstallDir\arserver.exe" -t -i "etc etc etc... The startup logs that will be then generated in the bin directory of the AR System installation may tell you where the startup crashes.. I am not sure if this is documented on the current releases but this used to be an undocumented feature. Remove the -t flag later when you do not require it.. Having got the startup log you will know at what point the server crashes.. Cheers Joe ________________________________ From: jham36 <jha...@gmail.com> To: arslist@ARSLIST.ORG Sent: Tuesday, July 28, 2009 4:23:53 PM Subject: Re: Error Starting Server After 7.5 patch 2 upgrade We don't use BMC support anymore. We have US based support now from a BMC partner. I am trying to determine if they are better or not. On Jul 28, 4:19 pm, patrick zandi <remedy...@gmail.com> wrote: 3rd nation support ? On Tue, Jul 28, 2009 at 3:31 PM, jham36 <jha...@gmail.com> wrote: That did not seem to work. The Windows Application log started showing errors about the SQL database not being available. I do not see these errors when I remove that "\" What happens without the "\" is that the server cache builds up to about 477 MB, then crashes. The Windows Application log shows: Faulting application arserver.exe, version 7.5.0.2, faulting module arserver.exe, version 7.5.0.2, fault address 0x0015cdf0. Anyone have any other ideas? This is just a test server, so I can wipe it out if needed. I was hoping to find a solution in case we encountered this in production. James On Jul 28, 2:57 pm, jham36 <jha...@gmail.com> wrote: I don't have the "\" at the end of that entry. I added it in and the server is doing something now. It is taking much longer to start and normally would have crashed by now. I did notice that the server cache does not seem to be building up like it usually does. The arserver.exe process (on Windows) is only using 14 MB of memory. I will wait and see what happens. Thanks, James On Jul 28, 2:36 pm, LJ Longwing <lj.longw...@gmail.com> wrote: I have come across this before...I forget if it was a lack of \ or a \ where one didn't belong, but my issue resides around (7.1) when running the installer and the path I provide for remedy like I said, either didn't have a \ or had one...I forget....but my armonitor.cfg is supposed to look like this "E:\Remedy\AR System\arserver.exe" -i "E:\Remedy\AR System" -l "C:\Program Files\Common Files\AR System\Licenses\<server>" -m But when I have the problem it looks like this "E:\Remedy\AR System\arserver.exe" -i "E:\Remedy\AR System\" -l "C:\Program Files\Common Files\AR System\Licenses\<server>" -m All I did was get rid of the \ at the end of the -i parameter and it worked fine....I consider this a bug in the installer but have never bothered to report it. -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of jham36 Sent: Tuesday, July 28, 2009 12:27 PM To: arsl...@arslist.org Subject: Error Starting Server After 7.5 patch 2 upgrade Listers, I upgraded our test environment from ARS 7.5 patch 1 to 7.5 patch 2 last week. The installer failed when trying to restart the arserver towards the end of the install. The only error I can see in the armonitor log file is: Failure occurred during execl() (ARERR 33) The install log does not show any errors until it fails to restart the server. I have verified that the armonitor.cfg file looks correct and even restored a backup copy just to make sure. Support has been unable to make any progress on this issue. Thanks, James _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor:rmisoluti...@verizon.net ARSlist: "Where the Answers Are"
