Hi,
I am back with that pesky failed-modification-via-web-services error thrown when doing an Export on the FIM MA. I had others which related to conflicting rules and violations of regular expressions in allowed values, I was able to solve them, but is left with one which I think might be a bug in the FIM Portal or procedures in the FIM Portal DB.
This one is specifically related to the Proxy Address Collection attribute in the FIM Portal. When an user object is exported for the very first time, there is no problem, the proxy Address Collection attribute is populated properly with all the related email aliases.
When a change occurs on the user's email addresses, and this attribute needs updating, the failed-modification-via-web-services error is thrown on export to the FIM Portal. This only happens when there are multiple ADDs and Deletes. This is reflected in the error detail, see below extract:
Fault Reason: The endpoint could not dispatch the request.\r\n\r\nFault Details: <DispatchRequestFailures xmlns="http://schemas.microsoft.com/2006/11/ResourceManagement" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"><DispatchRequestAdministratorDetails><FailureMessage>Exception: Other
Stack Trace: Microsoft.ResourceManagement.WebServices.Exceptions.UnwillingToPerformException: Other ---> System.Data.SqlClient.SqlException: Reraised Error 2627, Level 14, State 1, Procedure DoEvaluateRequestInner, Line 1073, Message: Violation of PRIMARY KEY constraint 'PK__#BC8F171__5330D077BAE9F047'. Cannot insert duplicate key in object 'dbo.@transitionOutApplicableRuleBuffer'. The duplicate key value is (13520, 34810, 147).
In the FIM Portal, the request object remains in the validating state.
A scenario in our company which leads to this is for example when a lady marries and takes on her husbands surname, the relevant email addresses and aliases also needs changing. The graphic below shows this
My current workaround for this is:
1. Manually update the Proxy Address Collection in the FIM Portal
2. Do DI on FIM MA
3. Do DS on FIM MA
4. Do E on FIM MA, this now exports the other changes to the user object in t eh FIM Portal.
I have also played around with adding addresses in the FIM Portal, and found that if only 1 Add or Delete remains, it also works. The Proxy Address Collection is used in no Set criteria or any other SRs which could cause a conflict. I also did an export of everything in the FIM Portal and found nothing else that point to either a conflict or other error.
My dev environment is the same
What I want to know is:
1. Has anyone else picked up this particular problem, will only see it if you export to the Proxy Address Collection attribute in the FIM Portal and have changes on this attribute in the AD.
2. Does this look like a bug and should be reported through PSS
This is driving us up the wall, and we battle with this now for a long time. This error requires a lot of manual intervention in the operations of FIM
I have posted on this subject before, but not specifically on the attribute mentioned here.
Any help or advice is appreciated.
Thanks
Johan Marais
P.S. I had to remove the images illustrating the multiple deletes and adds. Can post them when requested
JkM6228