Another copy of the Approval Server is already running
Page 1 of 1
Another copy of the Approval Server is already running
On ARSystem startup I see the following output:
Action Request System Approval Server initializing.
Starting AR System Approval Server
Action Request System(R) Approval Server Version 5.01.00.00
Remedy, a BMC Software company. Copyright (c) 1999 - 2003 BMC Software, Inc. All rights reserved.
Another copy of the Approval Server is already running or the Application Dispatcher is in use (ARAPPERR 4582)
started Thu Feb 26 12:51:18 2004 by pid 18022
AR System Approval Server terminated -- fatal error encountered (ARAPPNOTE 4501)
Action Request System Approval Server initialization is complete.
Action Request System Approval Server initializing.
Starting AR System Approval Server
Action Request System(R) Approval Server Version 5.01.00.00
Remedy, a BMC Software company. Copyright (c) 1999 - 2003 BMC Software, Inc. All rights reserved.
Another copy of the Approval Server is already running or the Application Dispatcher is in use (ARAPPERR 4582)
started Thu Feb 26 12:51:18 2004 by pid 18022
AR System Approval Server terminated -- fatal error encountered (ARAPPNOTE 4501)
Action Request System Approval Server initialization is complete.
giby.varghese@gmail.com- Posts : 107
Points : 222
Reputation : 3
Join date : 2009-11-11
Re: Another copy of the Approval Server is already running
A couple of things could be the issue, but both related to the location of the ar.cfg file.
First check the armonitor.cfg file to be sure that the -i in the arservapd process is the same as the arserver
install directory -- example:
/<approval server install dir>/bin/arservapd -s infodev2 -i <arserver install dir>
By default, it will look for the conf directory one level below whatever is specified in the -i parameter.
Next, make sure the briesvc.sh script is also pointing to that same directory structure. You will have to edit this
script using vi.
Obviously, there could be other issues resulting in this error -- but these two are the ones we found and once
resolved, the issue went away.
First check the armonitor.cfg file to be sure that the -i in the arservapd process is the same as the arserver
install directory -- example:
/<approval server install dir>/bin/arservapd -s infodev2 -i <arserver install dir>
By default, it will look for the conf directory one level below whatever is specified in the -i parameter.
Next, make sure the briesvc.sh script is also pointing to that same directory structure. You will have to edit this
script using vi.
Obviously, there could be other issues resulting in this error -- but these two are the ones we found and once
resolved, the issue went away.
giby.varghese@gmail.com- Posts : 107
Points : 222
Reputation : 3
Join date : 2009-11-11
Similar topics
» When connecting Remedy User to a server using a specified AR TCP Port, query menus fail with: ARERR [90] Cannot establish a network connection to the AR System server : test.Remedy.COM : RPC: Program not registered.
» How to Clean the wrong server name from Workflow.
» Invalid or pre 6.0 AR Server license file. - [ARERR 466]
» What are the procedures to Upgrade and Migrate AR Server on a Windows platform with Oracle?
» When User or Admin Tools try to connect to the server an ARERR 90 is received with the message RPC: Program not registered.
» How to Clean the wrong server name from Workflow.
» Invalid or pre 6.0 AR Server license file. - [ARERR 466]
» What are the procedures to Upgrade and Migrate AR Server on a Windows platform with Oracle?
» When User or Admin Tools try to connect to the server an ARERR 90 is received with the message RPC: Program not registered.
Page 1 of 1
Permissions in this forum:
You cannot reply to topics in this forum