I have an SLM problem that so far has proved unsolvable. I'm open to ideas. And before you say "turn on plugin logging" I'll just go ahead and say I have - repeatedly - and there's nothing useful regardless of the log level in the logs.
Here are the facts thus far: Problem/Symptom: When trying to create a new service target this error is encountered: "ARERR [8939] The AR System Plug-In server is not responding. Cannot connect to the system at this time. Contact your AR System Administrator for assistance." Filter logging indicates this error happens in filter SLM:ConfigDataSource:JoinFormSubmitModifyMergeCallSLASetupFilterAPI action 1 - ie, when the filter API with the plugin name REMEDY.ARF.SLASETUP is called. The following information is everything we know about the issue: 1.) This is AR Server v 7.1 patch 001 for Solaris running IM 7.03, CMDB 2.1, Assignment Engine, Email Engine, Patch 9002 (task templates). 2.) Approval server is NOT running on this server (this was a problem with previous versions of ARS/SLA that has this problem - a shared object file had to be replaced - see #3)). 3.) We have updated the file libardbcQuery.so as requested by support. 4.) We've verified paths/permissions to all products referenced in the ar.conf, armonitor.conf, etc - they all appear to be correct. 5.) We are running multiple logical solaris servers on one physical server. All of these are configured to have their own IP's, DNS name, etc. 6.) We are not running portmapper. The server in question is configured to use ARS port 7800 and plugin port 7801. These ports are open to the machine and all users on our LAN. However, the connection between the AR Server and the database is only allowed through the firewall on port 7800. 7.) There are other identical AR server/application instances running on each logical server (see #5). These all have this same problem as well. However, each is configured to use different ports. 8.) No errors are received during the startup process of the server. 9.) Support had us comment out the plugin server from the armonitor.conf file and start it manually after the server was up from the console and make the error occur in the user tool - no errors were received at the console. The thing just plain doesn't work - and there's no log information and nothing else to go on to explain why this is happening. William Rentfrow, Principal Consultant [EMAIL PROTECTED] C 701-306-6157 O 952-432-0227 _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
