In the service target definition, what qualification do you have for "Stop When" on SLM2?
Single Sign On (SSO) for BMC Remedy AR System and ITSM
We haven't run across any such problem however this may be a bit difficult to diagnose without some additional information, one of which Danny suggested. Key pieces of information would include SLM version, patches applied, the Stop When qualification of SLA2, supporting logs and possibly more. To expedite a resolution, I would suggest logging a Support call with BMC.
I think the problem is not relating to SLA2's "Stop When" condition. After getting into the details of the problem I realized that the SLA1 & SL2 are no long existing in the systems i.e. they have been deleted. However, for the given SLM they are still showing as related when they don't exists (the SLAs where deleted after the SLM was closed). So I guess, I need to associate the newly created SLAs and that should solve the problem. There is still one caveat, the SLM's status is marked as close. So under such a situation what should one do as it is reflecting wrong status for the reports.
Any help will be highly appreciated.