Does anyone see the following after their arserver is started:
Authentication failed () ARERR - 623 AR System Approval server terminated -- fatal error encountered (ARAPPNOTE 4501) In the aruser.log, I see the following: <USER> <TID: 0000000015> <RPC ID: 0000000005> <Queue: Prv:390624> <Client-RPC: 390624 > <USER: Remedy Application Service> /* Fri Feb 09 2007 15:44:40.1588 */ LOGIN Remedy Application Service <USER> <TID: 0000000015> <RPC ID: 0000000010> <Queue: Prv:390624> <Client-RPC: 390624 > <USER: Remedy Application Service> /* Fri Feb 09 2007 15:44:40.1765 */ FIXED GRANT WRITE Remedy Application Service ... <USER> <TID: 0000000015> <RPC ID: 0000004584> <Queue: Prv:390624> <Client-RPC: 390624 > <USER: Remedy Application Service> /* Fri Feb 09 2007 15:45:28.0596 */ LOGIN FAILED Remedy Application Service (password) The queue 390624 is specifically set up for the approval server. Environment Specifics: Solaris 9 ARServer Version 7.0.01 patch 001 200701111654 Plug-In Server Version 7.0.01 200609271856 Approval Server Version 7.0.01 200609271856 Background Info/thoughts: - in the 7.x series of arserver, a user-defined password is required before the 'Remedy Application Service' account will function - approval server 7.x + was moved from a standalone daemon to a plugin - my guess is that there is some legacy code in arapprov.so that attempts to use the 'secret' password that the 'Remedy Application Service' account is set to when it is not defined - despite the failed authentication shown above, the approval server functions as it should (handles all detail/sig actions; reads the approval server config settings; etc) Thanks, Axton Grams _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
