Skip to main content

miis: attribute not defined as source exception

i ran into this error recently which the fine folks @ mmsug@yahoogroups.com helped me clear up. i didn't find but one reference while googling. even though the reference was right, it made so sense to me. no surprise right? here's the error:
Microsoft.MetadirectoryServices.AttributeNotDefinedAsSourceException: Attribute "myAttribute" is not declared as a dependency. at Microsoft.MetadirectoryServices.Impl.MVEntryImpl.get_Item(String attributeName) at Mms_ManagementAgent_CCI_MA.MAExtensionObject.MapAttributesForExport(String FlowRuleName, MVEntry mventry, CSEntry csentry)
i was goofing around with this sample code. the only thing i did was wrap an additional logic to check myAttribute to see if it needed to be processed at all. basically if myAttribute is marked to a value of "A" then do not process the user object under any circumstances. it seems the problem is that i didn't bother to include myAttribute as part of the flow going through the rule extension. i was flowing employeeStatus to userAccountControl but didn't bother to include myAttribute. in identity manager, i needed to ctrl-click both attributes exported through the rule extension into userAccountControl. that took care of it. :)
Labels:

Comments

  1. Nasal Crooner3/1/07, 11:08 AM

    that helped..
    thanks!! :)

    ReplyDelete
  2. Marcus Oh3/1/07, 4:08 PM

    great! glad it helped!

    ReplyDelete
  3. Anonymous8/19/09, 11:21 AM

    I had the same error in an OnPremise MA using dirsync and was getting the error on the "MailNickname" attribute--even though I had a flow rule for it. By removing MailNickname from the flow and from the attributes selected for the OnPremise MA, the error went away.

    ReplyDelete

Post a Comment

Popular posts from this blog

using preloadpkgonsite.exe to stage compressed copies to child site distribution points

UPDATE: john marcum sent me a kind email to let me know about a problem he ran into with preloadpkgonsite.exe in the new SCCM Toolkit V2 where under certain conditions, packages will not uncompress.  if you are using the v2 toolkit, PLEASE read this blog post before proceeding.   here’s a scenario that came up on the mssms@lists.myitforum.com mailing list. when confronted with a situation of large packages and wan links, it’s generally best to get the data to the other location without going over the wire. in this case, 75gb. :/ the “how” you get the files there is really not the most important thing to worry about. once they’re there and moved to the appropriate location, preloadpkgonsite.exe is required to install the compressed source files. once done, a status message goes back to the parent server which should stop the upstream server from copying the package source files over the wan to the child site. anyway, if it’s a relatively small amount of packages, you can
11 comments
more »

How to Identify Applications Using Your Domain Controller

Problem Everyone has been through it. We've all had to retire or replace a domain controller at some point in our checkered collective experiences. While AD provides very intelligent high availability, some applications are just plain dumb. They do not observe site awareness or participate in locating a domain controller. All they want is the name or IP of one domain controller which gets hardcoded in a configuration file somewhere, deeply embedded in some file folder or setting that you are never going to find. How do you look at a DC and decide which applications might be doing it? Packet trace? Logs? Shut it down and wait for screaming? It seems very tedious and nearly impossible. Potential Solution Obviously I wouldn't even bother posting this if I hadn't run across something interesting. :) I ran across something in draftcalled Domain Controller Isolation. Since it's in draft, I don't know that it's published yet. HOWEVER, the concept is based off
3 comments
more »

sccm: content hash fails to match

back in 2008, I wrote up a little thing about how distribution manager fails to send a package to a distribution point . even though a lot of what I wrote that for was the failure of packages to get delivered to child sites, the result was pretty much the same. when the client tries to run the advertisement with an old package, the result was a failure because of content mismatch. I went through an ordeal recently capturing these exact kinds of failures and corrected quite a number of problems with these packages. the resulting blog post is my effort to capture how these problems were resolved. if nothing else, it's a basic checklist of things you can use.   DETECTION status messages take a look at your status messages. this has to be the easiest way to determine where these problems exist. unfortunately, it requires that a client is already experiencing problems. there are client logs you can examine as well such as cas, but I wasn't even sure I was going to have enough m
3 comments
more »