Lotus Domino 8.x Connector Error
Hi, I'm trying to configure the Domino 8.x connector on FIM 2010 Update Rollup 2. .Net 4 and the Notes 8.5 client have been installed as per the technet documentation and the client has been run once successfully. The msi installs fine and I can select it when attempting to create a new MA. I enter details on the Connectivity page (server, user id, password and check for delta import) and click next which is where i get the following error (apologies for hand typing it - actual FIM server is isolated): Dialogue box: "Unable to retrieve configuration parameters from the extension: An error occured in the extensible extension." Event Viewer: Event 6801 ...Notes error: Maximum allowable documents exceeded for a temporary full text index ([Type]=Certifier and [CertificateType]=0) at Domino.IDocumentCollection.FTSearch(String p Query, Int32 IMaxDocs) at Microsoft.IdentityManagement.MA.LotusDomino.NotesClientWrapper.DominoConfig.GetOrganizationalUnit(KeyedCollection `2 configParameters)... <snip> If I OK the dialogue box, I then get: Dialogue box: "Unable to retrieve schema. Error: An anchor attribute defined by the extension must not be of type Reference or Boolean. A multivalued attribute defined by the extension must not be of type Boolean" Event Viewer: Event 6801 ...Object reference not set to an instance of an object at Microsoft.IdentityManagement.MA.LotusDomino.NotesClientWrapper.DominoUtils.DominoSchema(Context context) at Microsoft.IdentityManagement.MA.LotusDomino.NotesClientWrapper.DominoUtils.DominoSchema.GetLotusDominoSchema(Context context)... <snip> I have previously had the 6/7.x client MA working against the same Domino server using the same Notes ID file. I uninstalled the 6.5 client that we were using for that and cleaned up the program files (x86) directory The first error suggests that a database is not indexed, but which database is it referring to on the initial connection? Client would rather index the database than start modifying the server side notes.ini to increase the TEMP_INDEX_MAX_DOC=number setting. Any suggestion greatly appreciated, thanks. Louis
March 19th, 2012 11:59am

OK, after having a look at the notes log files, it appears that it's the default names.nsf for that server that must either: 1) contain less than 5000 objects (default value for TEMP_INDEX_MAX_DOC) 2) be indexed 3) have the value for TEMP_INDEX_MAX_DOC manually set to higher than the number of objects it contains. I don't know what's causing the second error though - unable to rerieve schema. L
Free Windows Admin Tool Kit Click here and download it now
March 19th, 2012 12:22pm

Have you tried adding a full text index to your NAB? It could be a bubble-up error w.r.t. the schema. Also, where in the product documentation does FIM claim to support a Notes 8.x client?
March 19th, 2012 5:14pm

Yep - adding the full text index to the default NAB sorted the first error but I still get the 'Unable to retrieve schema' error. Notes 8.x connector RTM release: here
Free Windows Admin Tool Kit Click here and download it now
March 19th, 2012 6:26pm

Just to clarify (and appeal for help!)Reinstalled the Notes Client (8.5.1 FP3) and the new Notes Connector on the FIM server. Notes server is 8.5.1 FP3. Notes client can connect with no problems. Full text indexing the names.nsf address book cleared the initial error I was getting, but I still get the following error when configuring the Notes MA (on the connection screen): Dialogue box: "Unable to retrieve schema. Error: An anchor attribute defined by the extension must not be of type Reference or Boolean. A multivalued attribute defined by the extension must not be of type Boolean" Event Viewer: Event 6801 Microsoft.MetadirectoryServices.ExtensibleExceptionException--->System.NullReferenceException: Object reference not set to an instance of an object. at Microsoft.IdentityManagement.MA.LotusDomino.NotesClientWrapper.DominoUtils.DominoSchema(Context context) at Microsoft.IdentityManagement.MA.LotusDomino.NotesClientWrapper.DominoUtils.DominoSchema.GetLotusDominoSchema(Context context) at Microsoft.IdentityManagement.MA.LotusDomino.LotusDominoMA.GetSchema(KeyedCollection`2 configParameters) --- End of inner exception stack trace --- at Microsoft.IdentityManagement.MA.LotusDomino.LotusDominoMA.GetSchema(KeyedCollection`2 configParameters) Forefront Identity Manager 4.0.3606.2
March 20th, 2012 6:30am

Lou, You're not alone having this problem, just got the url to this thread from the guy at MS PSS that's handling the case for us. //HenrikHenrik Nilsson, Forefront Identity Manager MVP Blog Twitter My employer - Cortego
Free Windows Admin Tool Kit Click here and download it now
March 22nd, 2012 8:32am

Thanks for the that Henrik. Misery loves company :)
March 22nd, 2012 11:02am

Thanks for the that Henrik. Misery loves company :) Agree! :-) I'll keep you posted on the PSS case progress...Henrik Nilsson, Forefront Identity Manager MVP Blog Twitter My employer - Cortego
Free Windows Admin Tool Kit Click here and download it now
March 22nd, 2012 11:23am

Nothing new really except somebody else have filed a case MS PSS for the same problem and I have an "Easy Assist" session later today with them trying to solve the problem. //HenrikHenrik Nilsson, Forefront Identity Manager MVP Blog Twitter My employer - Cortego
April 2nd, 2012 6:39am

Great news! Weve just succeeded to make the Notes 8.x connector work! :-) 1. It turns out it requires access to Schema.nsf, a database not available by default in Domino but has to be created by for example enabling the LDAP service. This is not documented in the Notes Connector document on Technet. 2. The Schema.nsf generated by Domino when starting the LDAP service doesnt seem to work, probably because of missing mappings required by FIM. We made it work by using Schema.nsf from our production environment (a Schema.nsf not used for years) and I don't have any details on what mappings are required for making this work right now. Unfortunately the exceptions occurred in the connector couldn't say that Schema.nsf isnt available or that the mappings is insufficient or maybe incorrect for use with FIM. //HenrikHenrik Nilsson, Forefront Identity Manager MVP Blog Twitter My employer - Cortego
Free Windows Admin Tool Kit Click here and download it now
April 2nd, 2012 10:33am

Thanks for the update Henrik - sorry it took a while to respond as I've been on leave :-) We found the same thing except that in our case, the schema.nsf that was generated when starting the LDAP service worked for us. Strange that it didn't for you. Hopefully the documentation will get updated soon to explicitly state this as a requirement. Our issue now is that we can't see additional address books - we have 5 in a sub directory that we wish to read from. The old version of the MA allows us to manually enter the path to the nsf file on the server, but the new one does not seem to have this functionality :-( In the meantime, thanks for the assistance :) L
April 17th, 2012 7:24am

Hi Lou! We actually made it work with the generated Schema.nsf the second time we tried. Have you succeded to provision to Domino using this Connector, I believe I have all the attributes required in the correct format and everthing should be set but get an invalid-provisioning-attribute-value exception back on export with a "Required attribute 'UniversalID' is missing" schema validation message. No problems at all found in the connector log... //HenrikHenrik Nilsson, Forefront Identity Manager MVP Blog Twitter My employer - Cortego
Free Windows Admin Tool Kit Click here and download it now
April 17th, 2012 9:41am

We're not doing provisioning to Notes for this client but it is something I'd like to test if I get time. I did notice that UniversalID was not selected by default in the attributes page despite it being required as it is the anchor for the Domino MA. Are you providing a value for it when provisioning? It may be one of those attributes that is actually set by the directory itself but which you have to provide some sort of value for when trying to create an object. I'd be tempted to provide a generated random GUID for provisioning and see whether that works. Can you see other .nsf files in your MA when trying to select partitions? I can only see the default names.nsf file and one other (LargeDirectory.nsf) that doesn't even exist on the designated server. Not sure how the MA enumerates the available address books on the Domino server, but it doesn't seem to be working. On the old version of the MA, I could manually input the path to the other .nsf files and it worked fine. Doesn't look like that's an option with this version :( L
April 17th, 2012 10:09am

Hi Henrik, I'm also stuck with the same error. Do you have any solution? -Pradeesh -Pradeesh Sharma VM
Free Windows Admin Tool Kit Click here and download it now
May 29th, 2012 7:33am

It turned out to be a problem with how the connector reads information from Domino. In our case it couldn't read a newly created Person document until the document was indexed and that didn't happen immidiately therefore we had to use Another solution for provisioning to Domino (Domino Web Service). //HenrikHenrik Nilsson, Forefront Identity Manager MVP Blog Twitter My employer - Cortego
June 1st, 2012 4:20am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics