micasad not starting for OES2 services

  • 7006558
  • 03-Aug-2010
  • 27-Apr-2012


Novell Open Enterprise Server 2 (OES 2) Linux Support Pack 2


rcmicasad start would report that it had started successfully, but when then doing a rcmicasad status, it would report unused.

As there are several OES services that store their credentials in CASA (AFP in this case), it was preventing those services from starting.

Further investigation revealed that the customer had attempted to install ZCM and a newer version of Mono (2.0.1) that was not part of the SLES10/OES2 channel.


The newer version of Mono (not installed via the OES channel) was preventing CASA from starting. As they were not using ZCM, it was removed and the version of Mono was restored to the latest available via the OES2 update channel (1.2.2 as opposed to 2.0.1 at the time of this writing). At that point we were able to start micasad, fix the credential, and get AFP running.