I ended up with this error again under some uncertain circumstances (still convinced this has some connection with the crl downloads) and I ended up opening a PSS case. Here is the scoop - the problem is addressed in the following upcoming hotfix rollups for SP2:
- MIIS KB 936306
- ILM KB 938014
- IIFP KB 938015
These KB articles are still private and thus currently only available through PSS. The workaround is to just not execute the run profile from Identity Manager as the BAIL only occurs when executing the run profile through the UI. Here is some detail on the problem from PSS:
It’s important to note that this is a problem in the UI refresh and doesn’t have any effect on the MA run. It is caused by some scenarios where we have a NULL pointer in C++, not a NULL result set from a SQL query.
You may notice this error if you have SP2 for MIIS or ILM 2007 installed and you're executing run profiles from Identity Manager. The error only occurs when the UI attempts to refresh the run statistics and the problem is sporadic at best. Closing the UI while the error is occurring will allow the run to complete without issue.
Thanks to PSS for following up on this one!
Link to 1dent1ty cHa0s: MIIS SP2/ILM 2007 Timeouts, Out of Memory Errors and the Dreaded BAIL: MMS
Posts
5 comments:
I'm getting a very similar error during the export of an ADAM MA. So, it could be a real GUI error not related to your CRL issue.
Thanks for posting this by the way. I had a hard time deciding if I had a real problem or not. I don't ;-)
Is this fix only applicable if you are using SQL 2005 for your back end?
I'm not sure if the version of SQL matters here or not. If you're seeing the problem then I'd go ahead and apply the hotfix.
I was just asking this, because I was told that this fix is needed for SQL 2005. I am not experiencing this problem at this time with SQL 2000, but we are going to be upgrading to 2005 very shortly.
In that case, I would apply the fix prior to upgrading to 2005.
Post a Comment
Post a Comment